Architecture
NRAC maintains its own model of the network of interest. More precisely, it is up to the application to "teach" NRAC about the network by calling certain functions to create network resources, resource consumers, and events. Table 1 lists the typical correspondence between NRAC constructs and actual network constructs.
Table 1: NRAC–Network Construct Correspondence
| NRAC Abstract Construct | Actual Network Construct |
|---|---|
| Network | Network (a container for the other types of objects) |
| Resource | Node or link |
| Consumer | Traffic (connection, flow, LSP, etc.) |
| Event | Failure of a node or link |
However, NRAC does not require these relationships (e.g., NRAC could be used to model something non network-related such as the progressively increasing use of air traffic corridors by airlines). NRAC knows only that within a specific context, certain resources exist, and that certain resources are to be used by certain consumers, under specific conditions (the events). This "algebra" of NRAC expresses the only relationship provided for between the three types of objects.
NRAC can maintain multiple networks simultaneously on behalf of the application, as each set of objects is maintained within a specific network context. The network can be thought of as a container for resources, consumers, and events. Objects within separate containers do not interact with each other.