CONTROLLER-TO-CONTROLLER INTERFACE FOR MULTI-LAYER NETWORK ABSTRACTION
A controller at an IP (e.g., client) layer in a multi-layer network can request a network topology map from another controller at an optical (e.g., server) layer in the multi-layer network. The controller at the optical layer of the network can use a layer mapping function and common attributes between the formats used to describe the network topology map at the two layers to generate a common layer abstraction model representing the network topology map stored at the controller at the optical layer of the network. A controller-to-controller interface can translate and/or send the common layer abstraction model to the controller at the IP layer for processing data on the network.
1 . A method, comprising:
sending, from a first network entity at a first layer of a multilayer network, a network topology request to a second network entity that is (1) at a second layer of the multilayer network and (2) configured to translate a network topology in a second layer topology format into a network topology in a third layer topology format, the third layer topology format providing an abstraction of the second layer topology format;
receiving, at the first network entity, an indication of the network topology in the third layer topology format to convert the network topology in the third layer topology format into a network topology in a first layer topology format; and
determining, at the first network entity, at least one path between a first network node and a second network node using information representing the network topology in the first layer topology format.
2 . The method of claim 1 , wherein the third layer topology format is a common link abstraction model (CAM).
3 . The method of claim 1 , wherein determining the at least one path between the first network node and the second network node includes:
determining a fastest path between the first network node and the second network node using the network topology in the first layer topology format.
4 . The method of claim 1 , wherein determining the at least one path between the first network node and the second network node includes:
determining a shortest path between the first network node and the second network node using the network topology in the first layer topology format.
5 . The method of claim 1 , wherein the first network entity is connected to the second network entity without an intervening controller-to-controller interface.
6 . The method of claim 1 , wherein the first layer is a client layer configured to use an internet protocol (IP) layer.
7 . The method of claim 1 , wherein the second layer is a server layer configured to use an optical domain protocol.
8 . The method of claim 1 , wherein the second layer topology format is not readable by the first network entity.
9 . The method of claim 1 , wherein the second network entity is connected between (1) first network entity and (2) the first network node and the second network node.
10 . A first network entity at a first layer of a multilayer network, comprising:
a memory; and
a processor operatively coupled to the memory, the processor configured to:
send a network topology request to a second network entity that is (1) at a second layer of the multilayer network and (2) configured to translate a second network topology into a third network topology, the third network topology providing an abstraction of the second network topology;
receive an indication of the third network topology to convert the third network topology into a first network topology; and
determine at least one path between a first network node and a second network node using information representing the first network topology.
11 . The first network entity of claim 10 , wherein the third layer topology format is a common link abstraction model (CAM), the first layer is a client layer configured to use an internet protocol (IP) layer, and the second layer is a server layer configured to use an optical domain protocol.
12 . The first network entity of claim 10 , wherein the first network entity is connected to the second network entity without an intervening controller-to-controller interface.
13 . The first network entity of claim 10 , wherein the second layer topology format is not readable by the first network entity.
14 . The first network entity of claim 10 , wherein the second network entity is connected between (1) first network entity and (2) the first network node and the second network node.
15 . The first network entity of claim 10 , wherein determining the at least one path between the first network node and the second network node includes:
determining at least one of a shortest path or a fastest path between the first network node and the second network node using the network topology in the first layer topology format.
16 . A non-transitory, processor-readable medium storing code representing instructions to be executed by one or more processors, the instructions comprising code to cause the one or more processors to:
send, from a first network entity at a first layer of a multilayer network, a network topology request to a second network entity that is (1) at a second layer of the multilayer network and (2) configured to translate a network topology in a second layer topology format into a network topology in a third layer topology format;
receive, at the first network entity, an indication of the network topology in the third layer topology format to convert the network topology in the third layer topology format into a network topology in a first layer topology format; and
determine, at the first network entity, at least one path between a first network node and a second network node using information representing the network topology in the first layer topology format.
17 . The non-transitory processor-readable medium of claim 16 , wherein the third layer topology format is a common link abstraction model (CAM), the first layer is a client layer configured to use an internet protocol (IP) layer, and the second layer is a server layer configured to use an optical domain protocol.
18 . The non-transitory processor-readable medium of claim 16 , wherein the first network entity is connected to the second network entity without an intervening controller-to-controller interface.
19 . The non-transitory processor-readable medium of claim 16 , wherein the second layer topology format is not readable by the first network entity.
20 . The non-transitory processor-readable medium of claim 16 , wherein the second network entity is connected between (1) first network entity and (2) the first network node and the second network node.