Network technology interworking via user programmable event-action profiles

Patent metadata

Field	Value
Publication number	US-9893937-B2
Application number	US-201313864781-A
Country	US
Kind code	B2
Filing date	Apr 17, 2013
Priority date	Apr 17, 2013
Publication date	Feb 13, 2018
Grant date	Feb 13, 2018

Abstract

The disclosure is directed to configuring an internetworking of a first network and a second network. Data representing one or more network events is received at a network element, data representing one or more actions to be performed by the second network in response to detection of the one or more events on the first network is received at the network element, and a mapping of the one or more network events to the one or more actions is stored by the network element.

First claim

What is claimed is:

1. A method of configuring an internetworking of a first network and a second network, comprising: receiving, at a network element, data representing one or more network events in the first network in a first packet network protocol associated with the first network; receiving, at the network element, data representing one or more actions to be performed by the second network in response to detection of the one or more events in the first network in a second packet network protocol associated with the second network, wherein the first packet network protocol is different from the second packet network protocol; and storing, by the network element, a mapping of the one or more network events in the first network to the one or more actions in the second network to achieve the internetworking of packet network protocols of the first network and the second network, wherein the internetworking comprises a combination of OAM (Operations, Administration, and Management) plane internetworking and control plane internetworking, and wherein the first packet network protocol and the second packet network protocol each comprise one of a Spanning Tree Protocol, Rapid Spanning Tree Protocol, Provider Backbone Bridge Traffic Engineering, Multiprotocol Label Switching/Multiprotocol Label Switching Transport Profile, and G.8032.

2. The method of claim 1 , further comprising: detecting one of the one or more events on the first network; determining a corresponding action to perform on the second network based on the detected event and the mapping; and performing the corresponding action on the second network.

3. The method of claim 1 , wherein the first network and the second network implement different types of network protocols.

4. The method of claim 1 , wherein the first network and the second network implement a same type of network protocol.

5. The method of claim 1 , wherein the first network is a packet network.

6. The method of claim 1 , wherein the second network is a packet network.

7. The method of claim 1 , wherein the one or more actions are actions that translate the one or more events into corresponding events on the second network.

8. The method of claim 1 , wherein the data representing the one or more events is received from a user, a remote server, or a network controller.

9. The method of claim 1 , wherein the data representing the one or more actions is received from a user, a remote server, or a network controller.

10. The method of claim 1 , wherein the data representing the one or more events is received from a user via a user interface of the network element.

11. The method of claim 1 , wherein the data representing the one or more actions is received from a user via a user interface of the network element.

12. The method of claim 1 , wherein the mapping is generated by a user indicating which of the one or more actions maps to the one or more network events.

13. The method of claim 1 , wherein the mapping is a table comprising the one or more network events, one or more interfaces associated with the one or more network events, the one or more actions, and one or more interfaces associated with the one or more actions.

14. The method of claim 1 , wherein the network element is a desktop computer, a server, a node, a router, a switch, a bridge, a hub, a proxy, or other network device coupled to and configured to pass data to another network element.

15. The method of claim 5 , wherein the packet network is a Spanning Tree Protocol (STP) network, a Provider Backbone Bridge Traffic Engineering (PBB-TE) network, a Multiprotocol Label Switching/Multiprotocol Label Switching Transport Profile (MPLS/MPLS-TP) network, or a G.8032 network.

16. The method of claim 6 , wherein the packet network is a Spanning Tree Protocol (STP) network, a Provider Backbone Bridge Traffic Engineering (PBB-TE) network, a Multiprotocol Label Switching/Multiprotocol Label Switching Transport Profile (MPLS/MPLS-TP) network, or a G.8032 network.

17. The method of claim 13 , wherein the one or more interfaces associated with the one or more network events are one or more interfaces between the network element and a network element on the second network.

18. The method of claim 13 , wherein the one or more interfaces associated with the one or more actions are one or more interfaces between the network element and a network element on the second network.

19. An apparatus for configuring an internetworking of a first network and a second network, comprising: logic configured to receive, at a network element, data representing one or more network events in the first network in a first packet network protocol associated with the first network; logic configured to receive, at the network element, data representing one or more actions to be performed by the second network in response to detection of the one or more events in the first network in a second packet network protocol associated with the second network, wherein the first packet network protocol is different from the second packet network protocol; and logic configured to store, by the network element, a mapping of the one or more network events in the first network to the one or more actions in the second network to achieve the internetworking of packet network protocols of the first network and the second network, wherein each of the logics comprises one of hardware and a combination of hardware and software, wherein the internetworking comprises a combination of OAM (Operations, Administration, and Management) plane internetworking and control plane internetworking, and wherein the first packet network protocol and the second packet network protocol each comprise one of a Spanning Tree Protocol, Rapid Spanning Tree Protocol, Provider Backbone Bridge Traffic Engineering, Multiprotocol Label Switching/Multiprotocol Label Switching Transport Profile, and G.8032.

20. The apparatus of claim 19 , further comprising: logic configured to detect one of the one or more events on the first network; logic configured to determine a corresponding action to perform on the second network based on the detected event and the mapping; and logic configured to perform the corresponding action on the second network.

21. The apparatus of claim 19 , wherein the first network and the second network implement different types of network protocols.

22. The apparatus of claim 19 , wherein the first network and the second network implement a same type of network protocol.

23. The apparatus of claim 19 , wherein the one or more actions are actions that translate the one or more events into corresponding events on the second network.

24. The apparatus of claim 19 , wherein the data representing the one or more events is received from a user via a user interface of the network element.

25. The apparatus of claim 19 , wherein the data representing the one or more actions is received from a user via a user interface of the network element.

26. The apparatus of claim 19 , wherein the mapping is generated by a user indicating which of the one or more actions maps to the one or more network events.

27. A network element configured to interwork a first network and a second network, comprising: a communications interface configured to receive data representing one or more network events in the first network in a first packet network protocol associated with the first network; the communica

Assignees

• Ciena Corp

Inventors

• Holness Marc
• Chen Wei Chiuan
• Jadav Asheesh

Classifications

• H04L41/0816 Primary

  the condition being an adaptation, e.g. in response to network events · CPC title

• H04L41/06

  Management of faults, events, alarms or notifications · CPC title

• H04L41/40

  using virtualisation of network functions or resources, e.g. SDN or NFV entities · CPC title

• H04L41/0895

  Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title