WO2003001397A1 - Procede et appareil d'approvisionnement d'une voie de communication - Google Patents

Procede et appareil d'approvisionnement d'une voie de communication Download PDF

Info

Publication number
WO2003001397A1
WO2003001397A1 PCT/US2002/020083 US0220083W WO03001397A1 WO 2003001397 A1 WO2003001397 A1 WO 2003001397A1 US 0220083 W US0220083 W US 0220083W WO 03001397 A1 WO03001397 A1 WO 03001397A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network element
provisioning
node
circuit
Prior art date
Application number
PCT/US2002/020083
Other languages
English (en)
Inventor
Alex Machinsky
Daniel Wang
Erik Johnson
Keith Bemer
Original Assignee
Elematics, Inc.
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 Elematics, Inc. filed Critical Elematics, Inc.
Priority to CA002451042A priority Critical patent/CA2451042A1/fr
Publication of WO2003001397A1 publication Critical patent/WO2003001397A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/822—Collecting or measuring resource availability data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/10—Routing in connection-oriented networks, e.g. X.25 or ATM
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/306—Route determination based on the nature of the carried application
    • H04L45/3065—Route determination based on the nature of the carried application for real time traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/726—Reserving resources in multiple paths to be used simultaneously
    • H04L47/728—Reserving resources in multiple paths to be used simultaneously for backup paths
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/74—Admission control; Resource allocation measures in reaction to resource unavailability
    • H04L47/745—Reaction in network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/74—Admission control; Resource allocation measures in reaction to resource unavailability
    • H04L47/746—Reaction triggered by a failure

Definitions

  • the present invention relates generally to the field of communication systems, and more particularly, to methods and apparatus for provisioning a communication path for a communication systems.
  • the first group comprises open peering in, for example, Internet exchanges.
  • the second group comprises private, bilateral peering relationships.
  • Both types of peering often require the participants to over-provision capacity and negotiate each capacity transaction on a case-by-case basis.
  • a network service provider interested in entering into a peering agreement must acquire enough capacity to handle spikes in their demand (i.e. spikes in customer traffic) if they are to avoid paying extra for the extra capacity necessary to carry the added customer traffic. Further, they are in danger of a degradation in the quality of service (QoS) provided during those peek times if their demand exceeds the available capacity.
  • QoS quality of service
  • Such over-provisioning often results in portions of the network sitting idle for the majority of the time (i.e. the time between the spikes), which is disadvantageous and costly.
  • typical Internet peering agreements require lengthy and complicated agreements that are disadvantageous for a variety of reasons. For example, it may be difficult to anticipate future needs prior to or during formation of the contract. Such agreements may also be prohibitively expensive and time consuming.
  • GMPLS Generalized Multi- Protocol Label Switching protocol
  • MPLS Multi-Protocol Label Switching
  • OIF Optical Internetworking Forum
  • UNI optical User Network Interface
  • NNI Network-to-Network Interface
  • the present invention enables and facilitates real-time provisioning of circuits or other communication paths across multi-carrier, multi- vendor networks.
  • the networks may include optical and/or non-optical components, and may operate using different technologies, protocols, network elements, etc.
  • the present invention provides a signaling control plane that may be integrated with existing network infrastructure and operations support systems (OSS) to facilitate provisioning of circuits between network elements.
  • the signaling control plane may mediate communications between a data plane having one or more network elements and a management plane having various network management applications.
  • the present invention allows for rapid set-up and teardown of circuits and other communication paths between end-user requested endpoints or network elements.
  • the present invention allows unified provisioning of circuits and inventory control over managed network elements, even when the network elements are from different vendors.
  • the present invention allows a unified interface to a management plane for the network elements.
  • a method for facilitating provisioning of a circuit between a first network element and a second network element may include receiving a request to establish a circuit between a first network element and a second network element in a network, the first network element being associated with a first provisioning node that forms part of a signaling control plane for the network, and the second network element being associated with a second provisioning node that forms part of the signaling control plane for the network; determining an available circuit between the first network element and the second network element; and providing commands for the first provisioning node and the second provisioning node regarding provisioning of the available circuit between the first network element and the second network element.
  • a method for facilitating provisioning of a circuit between a first network element and a second network element may include receiving a request to establish a circuit between a first network element in a first network and a second network element in a second network, the first network element being associated with a first provisioning node that forms part of a first signaling control plane for the first network, and the second network element being associated with a second provisioning node that forms part of a second signaling control plane for the second network; providing a notification indicative of the request; determining at least a portion of an available circuit between the first network element and the second network element, the portion of the available circuit including the first network element; and providing at least one command to the first provisioning node for provisioning of the portion of the available circuit.
  • a method for facilitating provisioning of a circuit between a first network element and a second network element may include receiving a first notification indicative of a request to establish a circuit between a first network element in a first network and a second network element in a second network, wherein the notification is received from a first signaling control plane associated with the first network and indicates a bridge element connected to the first network; identifying the second network; identifying a second signaling control plane, the second signaling control plane being associated with the second network; providing a second notification indicative of the request to the second signaling control plane; receiving from the second signaling control plane data indicative of a bridge element connected to the second network; determining an available circuit between the bridge element connected to the first network and the bridge element connected to the second network; and providing commands for the first provisioning the available circuit.
  • a method for facilitating provisioning of a circuit between a first network element and a second network element may include determining at least one operational characteristic of a first network element in a first network; providing information indicative of the operational characteristic to a device associated with the first network, wherein the device forms part of a signaling control plane for the first network; receiving a request to establish a requested circuit between the first network element and a second network element, wherein the second network element is associated with a provisioning node; providing data indicative of the request to the device; receiving information from the device indicative of a first command for the first network element for use in provisioning an available circuit between the first network element and the second network element; and providing data indicative of the first command to the first network element.
  • a method for facilitating provisioning of a circuit between a first network element and a second network element may include receiving a request to establish a circuit between a first network element and a second network element, the first network element being associated with a first provisioning node that forms part of a signaling control plane, and the second network element being associated with a second provisioning node that forms part of the signaling control plane; determining an available circuit between the first network element and the second network element; and providing commands for the first network element and the second network element regarding provisioning of the available circuit between the first network element and the second network element.
  • a system for establishing a circuit between network elements may include a first plurality of provisioning nodes associated with a first network, wherein each of the first plurality of provisioning nodes is associated with a respective network element contained in the first network and operative to inventory the respective network element; and a first node controller in communication with each of the first plurality of provisioning nodes and operative to receive information from each of the first plurality of provisioning nodes regarding inventory of network elements included in the first network; receive a request for provisioning a requested circuit, wherein the request identifies at least one network element in the first network to be used in the requested circuit; determine an available circuit in the first network that involves the first network element and forms at least a portion of the requested circuit; determine a one of the first plurality of provisioning nodes associated with the first network element; provide at least one command to the one of the first plurality of provisioning nodes associated with the first network element regarding provisioning of the available circuit.
  • a system for establishing a circuit between network elements might include a signaling control plane associated with a network that includes a first plurality of network elements, wherein the signaling control plane includes a first plurality of provisioning nodes and a first node controller, wherein each of the first plurality of provisioning nodes is associated with a different one of the first plurality of network elements and is in communication with the node controller, and wherein the signaling control plane is operative to determine an inventory of at least one capability of each of the first plurality of network elements; receive a request to provision a circuit that includes at least one of the first plurality of network elements; determine an available circuit that is formable using at least one of the first plurality of network elements and that satisfies at least a portion of the request; send commands to the at least one of the first plurality of network elements to facilitate establishment of the available circuit.
  • an apparatus for facilitating provisioning of a circuit between a first network element and a second network element may include means for obtaining a request to establish a circuit between a first network element and a second network element in a network, the first network element being associated with a first provisioning node that forms part of a signaling control plane for the network, and the second network element being associated with a second provisioning node that forms part of the signaling control plane for the network; means for identifying an available circuit between the first network element and the second network element; and means for sending commands for the first provisioning node and the second provisioning node regarding provisioning of the available circuit between the first network element and the second network element.
  • an apparatus for facilitating provisioning of a circuit between a first network element and a second network element may include means for obtaining a request to establish a circuit between a first network element in a first network and a second network element in a second network, the first network element being associated with a first provisioning node that forms part of a first signaling control plane for the first network, and the second network element being associated with a second provisioning node that forms part of a second signaling control plane for the second network; means for sending a notification indicative of the request; means for identifying at least a portion of an available circuit between the first network element and the second network element, the portion of the available circuit including the first network element; and means for sending at least one command to the first provisioning node for provisioning of the portion of the available circuit.
  • an apparatus for facilitating provisioning of a circuit between a first network element and a second network element may include means for obtaining a first notification indicative of a request to establish a circuit between a first network element in a first network and a second network element in a second network, wherein the notification is received from a first signaling control plane associated with the first network and indicates a bridge element connected to the first network; means for determining the second network; means for determining a second signaling control plane, the second signaling control plane being associated with the second network; means for sending a second notification indicative of the request to the second signaling control plane; means for obtaining from the second signaling control plane data indicative of a bridge element connected to the second network; means for identifying an available circuit between the bridge element connected to the first network and the bridge element connected to the second network; and means for sending commands for the first provisioning the available circuit.
  • an apparatus for facilitating provisioning of a circuit between a first network element and a second network element may include means for identifying at least one operational characteristic of a first network element in a first network; means for sending information indicative of the operational characteristic to a device associated with the first network, wherein the device forms part of a signaling control plane for the first network; means for obtaining a request to establish a requested circuit between the first network element and a second network element, wherein the second network element is associated with a provisioning node; means for sending data indicative of the request to the device; means for obtaining information from the device indicative of a first command for the first network element for use in provisioning an available circuit between the first network element and the second network element; and means for sending data indicative of the first command to the first network element.
  • an apparatus for facilitating provisioning of a circuit between a first network element and a second network element may include means for obtaining a request to establish a circuit between a first network element and a second network element, the first network element being associated with a first provisioning node that forms part of a signaling control plane, and the second network element being associated with a second provisioning node that forms part of the signaling control plane; means for identifying an available circuit between the first network element and the second network element; and means for sending commands for the first network element and the second network element regarding provisioning of the available circuit between the first network element and the second network element.
  • a computer program in a computer readable medium for facilitating provisioning of a circuit between a first network element and a second network element may include first instructions for obtaining a request to establish a circuit between a first network element and a second network element in a network, the first network element being associated with a first provisioning node that forms part of a signaling control plane for the network, and the second network element being associated with a second provisioning node that forms part of the signaling control plane for the network; second instructions for identifying an available circuit between the first network element and the second network element; and third instructions for sending commands for the first provisioning node and the second provisioning node regarding provisioning of the available circuit between the first network element and the second network element.
  • a computer program in a computer readable medium for facilitating provisioning of a circuit between a first network element and a second network element may include first instructions for obtaining a request to establish a circuit between a first network element in a first network and a second network element in a second network, the first network element being associated with a first provisioning node that forms part of a first signaling control plane for the first network, and the second network element being associated with a second provisioning node that forms part of a second signaling control plane for the second network; second instructions for sending a notification indicative of the request; third instructions for identifying at least a portion of an available circuit between the first network element and the second network element, the portion of the available circuit including the first network element; and fourth instructions for sending at least one command to the first provisioning node for provisioning of the portion of the available circuit.
  • a computer program in a computer readable medium for facilitating provisioning of a circuit between a first network element and a second network element may include first instructions for obtaining a first notification indicative of a request to establish a circuit between a first network element in a first network and a second network element in a second network, wherein the notification is received from a first signaling control plane associated with the first network and indicates a bridge element connected to the first network; second instructions for determining the second network; third instructions for determining a second signaling control plane, the second signaling control plane being associated with the second network; fourth instructions for sending a second t notification indicative of the request to the second signaling control plane; fifth instructions for obtaining from the second signaling control plane data indicative of a bridge element connected to the second network; fifth instructions for identifying an available circuit between the bridge element connected to the first network and the bridge element connected to the second network; and sixth instructions for sending commands for the first provisioning the available circuit.
  • a computer program in a computer readable medium for facilitating provisioning of a circuit between a first network element and a second network element may include first instructions for identifying at least one operational characteristic of a first network element in a first network; second instructions for sending information indicative of the operational characteristic to a device associated with the first network, wherein the device forms part of a signaling control plane for the first network; third instructions for obtaining a request to establish a requested circuit between the first network element and a second network element, wherein the second network element is associated with a provisioning node; fourth instructions for sending data indicative of the request to the device; fifth instructions for obtaining information from the device indicative of a first command for the first network element for use in provisioning an available circuit between the first network element and the second network element; and sixth instructions for sending data indicative of the first command to the first network element.
  • a computer program in a computer readable medium for facilitating provisioning of a circuit between a first network element and a second network element may include first instructions for obtaining a request to establish a circuit between a first network element and a second network element, the first network element being associated with a first provisioning node that forms part of a signaling control plane, and the second network element being associated with a second provisioning node that forms part of the signaling control plane; second instructions for identifying an available circuit between the first network element and the second network element; and third instructions for sending commands for the first network element and the second network element regarding provisioning of the available circuit between the first network element and the second network element.
  • Figure 1 A is a block diagram of a representation of components of a system in accordance with the present invention.
  • Figure IB is a block diagram of another representation of components of a system in accordance with the present invention.
  • Figure 2 is a block diagram of a representative management plane, signaling control plane, and a data plane formed by or used with IPNs, INCs and nodes;
  • FIG. 3 is a block diagram of a representative IPN of Figure 1 or Figure 2;
  • Figure 4 is a block diagram of a representative INC of Figure 1 or Figure 2;
  • FIG. 5 is a bock diagram overview of a Dense Wave Division Multiplexing (DWDM) system that may be used with or in the systems of Figures 1 and 2;
  • DWDM Dense Wave Division Multiplexing
  • Figure 6 is a tabular representation of a record used by or in the databases used in the systems of Figures 1A and Figure IB;
  • Figures 7A, 7B and 7C are a flowchart of a first embodiment of a method in accordance with the present invention for provisioning a circuit or other communication path;
  • Figures 8 A, 8B and 8C are a flowchart of a second embodiment in accordance with the present invention for provisioning a circuit or other communication path;
  • Figure 9 is a block diagram of a network configuration that may be employed for testing a circuit or other communication path provisioned according to the methods of the present invention.
  • FIGS. 10A, 10B and IOC are block diagrams that depict a representative manner in which provisioning a circuit or other communication path in accordance with the present invention may affect various layers of the network.
  • a network node may be or include one or more optical or non-optical switches, routers, cross-connects, DWDM equipment, gateways, hosts, applications, computers or computer systems, of other types of devices.
  • a provisioned communication path may last only as long as needed for a specific data transmission or may last an indefinite period of time.
  • the methods and apparatus of the present invention help address many economic and technical difficulties, including, but not limited to: poor price segmentation amongst a carrier's customers that leads to poor provisioning systems/processes; over-provisioning of circuits or other communication paths as a solution for demand management; inability to make capacity available to all who need it around the clock; slow development or deployment of high-bandwidth network applications due to the inability to allocate optical capacity in real time.
  • Some embodiments of this invention involve creating the signaling and mediation necessary to allow a router (e.g., a CiscoTM router) to signal a request for additional peering capacity to the software management system controlling the physical layer (i.e.
  • layer 1 of the OSI model of the peering partner's network to allow for better, faster traffic flow, or special capacity for special types of traffic.
  • requests often are placed by network engineers in response to alarms from the network that indicate congestion or packet loss, or based on network design applications that analyze historical network data and provide forecasts for future demand.
  • This present invention allows actual networks, as opposed to engineers and network planers, to automatically request and provision capacity between networks. This type of dynamic provisioning can dramatically reduce network congestion and enable a more responsive optimization and management of optical and routed networks.
  • a communications system 100 may include various computer, data or other communication networks or network domainslOl, 102 and 103, various nodes or network elements 1 10, 111, 112, 113, 114 and 115, various intelligent provisioning nodes (IPN) 120, 121, 122, 123, 124, 125 and 128, at least one intelligent node controller (INC) 130, a database or other resource 131, and one or more customers 140 and 141.
  • the database or other resource 131 may be included in or form part of the INC 130.
  • the network elements 110 and 111 may form a data plane of components in or for the network 101 while the IPNs 120, 121 and the INC 130 may form part of or be included in a signaling control plane for the network 101.
  • a realm of INC control will be referred to as an INC domain while a collection of one or more INC domains may make up a signaling control plane.
  • more than one INC may be used in or as part of signaling control plane, as will be discussed in more detail below.
  • more than one domain INC may exist in or as part of a signaling control plane, also as will be discussed in more detail below.
  • an IPN and/or an INC may be implemented on or by a computer, server, computer system, etc.
  • more than one IPN may be implemented on or by a computer, server, computer system, etc.
  • intelligent provisioning node, intelligent node controller, network element, data plane, management plan, signaling control plane, and user network interface are used for convenience only and no specific limitations are implied or intended by the used of such terms.
  • some or all of the network of IPNs 120, 121, 122, 123, 124, 125 and 128 may form a signaling control plane 150 for the networks 101, 102, 103, as will be discussed in more detail below.
  • the INC 130 also may be included in or form part of the signaling control plane 150 and provide control plane communications for all of the IPNs within its domain.
  • an INC or a signaling control plane may be connected to or in communication with a management plane.
  • the management plane may provide additional monitoring and management functionality for networks, network elements, etc.
  • an IPN may provide command set translation between a particular vendor's equipment and a signaling control plane command set.
  • An IPN may be configured with the necessary "personality package” or other software, interface, data, etc. specific to a network element under its control.
  • the interface between an IPN and a network element may be vendor specific and in some cases may be TL 1, CORBA or GSMP.
  • the interface may allow the IPN to discover and maintain topology, inventory, alarm, capability, and configuration information (collectively referred to herein as “inventory” information or “operational characteristic” information) regarding the network element as well as to issue provisioning commands to the network element.
  • the IPN may provide some or all of this information to an INC.
  • the IPN also may translate network element specific information into a protocol or other format useable or recognizable by an INC.
  • the IPN may develop and maintain a virtual representation or model of the network element for use in provisioning a circuit.
  • An IPN may receive provisioning commands from an INC, translate these commands into specific commands appropriate to the network element(s) under the IPN's control, and execute the commands on the network element.
  • the IPN provides network element or node control.
  • an IPN may be responsible for the management and control of its associated network element or some or all of the capabilities or operational characteristics or features of the associated network element.
  • the IPN may, collectively with its associated network element, perform security mechanisms such that access to the network element is screened.
  • only a subset of the facilities on the network element may be controlled by the IPN (or an associated signaling control plane) while the rest of the facilities or capabilities of the network element are controlled by the other systems or devices.
  • network service providers may request that only a specified number of ports be made available for control by an IPN or signaling control plane. More specifically, a given service provider may only make ten percent of the ports on a network element (e.g., the node 110) available for use by IPN or signaling control plane.
  • the network element may effectively be partitioned so that the IPN and/or signaling control plane only recognizes the identified ports as existing on the network element and is allowed to use only the identified ports in provisioning a circuit that includes the network element.
  • inventory information gathered by the IPN regarding the network element may be limited to the identified ports and not other ports available on the network element.
  • the INC 130 may maintain or include a topology database or other resource for its domain such that rapid path provisioning can be accomplished when service requests are received.
  • the INC 130 may retain inventory information regarding one or more network elements provided to it by one or more IPNs associated with the network elements, as well as manually entered configuration information such as link definitions and link attributes.
  • the new, corrected, or repaired IPN (which may be implemented in software) may discover the resources from or for its associated network element(s) and forward the information to the INC 130.
  • the INC 130 may correlate the new information with previously known information such that links or attributes will not need to be reentered. Thus, localized IPN outages may be recovered with minimal user intervention and down time.
  • the INC 130 may provide routing options for service requests and may issue commands to one or more IPNs in its domain once a specific path is determined or chosen for service establishment to fulfill the service request by configuring or controlling nodes or other network elements.
  • INCs may use IP-based secured INC to INC signaling to query each other for network resource availability and to coordinate provisioning of services between each other.
  • an INC may support INC to INC communications in order to facilitate inter-domain path selection and provisioning of services between network elements in different networks.
  • an INC may be a control element of a network domain.
  • the INC will communicate with all IPNs within the domain and may be responsible for maintaining all topology/inventory, usage, alarm, performance monitoring statistics, and service inventory information for the domain.
  • An INC resource e.g., the database 131) may be segmented into a resource inventory database and a service inventory database.
  • the resource inventory database may track and retain information for or regarding the domain such as: hardware inventory for controlled network elements, listing of ports and port types for network elements, listing of optical links and link attributes, listing of cross-connects and circuits provisioned, topology information regarding the relationship between network elements , operational characteristics of the network elements, etc.
  • the service inventory database may track and retain the following domain information: provisioned services, attributes of provisioned services, path information for provisioned services, establishment and disconnect time for provisioned services, cost metric totals for each service, performance monitoring information for each service, etc.
  • a signaling control plane may be or provide the control of a network and may include one or more INCs that maintain topology and capability (also referred to as operational characteristic) information for network elements in their respective domains (e.g., subsets of the network). Signaling between the INCs may be used to broker provisioning transactions between domains in the network.
  • a signaling control plane is capable of signaling, or being in communication with, one or more nodes (e.g., network elements) to configure or provision a circuit or other communication path between two network elements that may be in the same or in different domains.
  • the signaling control plane 150 may signal or communicate with one or more of the nodes 110, 111, 112, 113, 114 and 115 to form circuits among or across the networks 101, 102, 103 or other networks not illustrated in Figure 1 A.
  • a signaling control plane may allow accurate inventory of network elements controlled by the signaling control plane and set up rules/polices that govern under what terms circuits may be provisioned using one or more of the network elements. Provisioning requests may be provided to the signaling control plane by a customer, an operator using a console as part of a network management system, another signaling control plane, an INC in another signaling control plane, etc. If the provisioning request meets the rules/policies configured by the signaling control plane, the requested circuit may be provisioned automatically.
  • the signaling control plane may provide unified management for physical resources in a one or more networks.
  • the networks may include network elements provided by different vendors or utilize different technologies.
  • a signaling control plane may determine routes for services through a managed network or group of network elements, account for available and used inventory, manage protection switching and restoration for managed network elements or domains, etc.
  • a signaling control plane can provide the signaling mechanisms to network elements managed by the signaling control plane. The signaling mechanisms may affect configuration changes in the managed network elements to provide services as well as necessary logic.
  • a signaling control plane may provide a unified interface from the managed network elements to various management plane applications (e.g., network management system (NMS) applications, element management system (EMS) applications, operations support systems (OSS) applications).
  • NMS network management system
  • EMS element management system
  • OSS operations support systems
  • one or more of the networks 101, 102, 103 may be, include or represent optical networks, non-optical networks, router networks, long- haul networks, metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), etc.
  • the different networks or domains 101, 102, 103 may run on different protocols (e.g. IP, Ethernet, ATM), may have equipment from different vendors (e.g., Cisco, Corvis, CIENA, Extreme Networks) and may be owned and operated by different carriers (e.g., Sprint, Verizon, etc.).
  • one or more of the networks or domains 101, 102, 103 might be or include some or all of the Internet, the World Wide Web, or some other public or private computer, cable, telephone, client/server, peer-to-peer, or communications network or intranet.
  • the networks 101, 102, 103 illustrated in Figure 1A are meant only to be generally representative of cable, computer, telephone, peer-to-peer or other communication networks for purposes of elaboration and explanation of the present invention and other devices, networks, etc. may be used, configured, etc. without departing from the scope of the present invention.
  • a network also can include other public and/or private wide area networks, local area networks, wireless networks, data communication networks or connections, intranets, routers, satellite links, microwave links, cellular or telephone networks, radio links, fiber optic transmission lines, optical circuits, ISDN lines, TI lines, DSL, etc.
  • Each of the networks 101, 102, 103 comprises multiple nodes (also referred to as network elements).
  • the network 101 includes the nodes 110 and 111
  • the network 102 includes the nodes 112 and 113
  • the network 103 includes the nodes 114 and 115.
  • a network may include more than two nodes.
  • a node or network element may represent optical or non-optical switches, routers, cross-connects, DWDM equipment, transport equipment, etc.
  • each of the nodes 110, 111, 112, 113, 114, and 115 is in communication with at least one other node.
  • the communication protocol and technology may differ between different node connections depending on the nature of the nodes involved (i.e. vendor, configuration, etc.).
  • connections between nodes may occur within a single network, while others occur across multiple networks. Connections between nodes in different networks may occur, for example, at public or private peering points, collocation facilities, etc. It should also be noted that nodes depicted in a first network (e.g., the network 101) may be of a different model, vendor, type, etc. as compared to those nodes depicted in a second network (e.g., the network 102). In some instances, multiple connections may exist between two nodes. For example, if the nodes 111 and 112 are optical switches, they may be connected by three OC-12s links.
  • Each of the nodes 110, 111, 112, 113, 114 and 115 interfaces with at least one of the IPNs 120, 121, 122, 123, 124, 125 and/or 128.
  • an IPN may be a separate network element from a node, but in some embodiments one or more IPNs may be integrated with one or more existing nodes.
  • an IPN may represent a software process for controlling and managing a network element. Mutliple IPN applications may then operate on the same IPN machine or device for managing and controlling multiple network elements.
  • the IPNs 120 and 121 may be implemented by two IPN applications operating on the same device.
  • Each network element may have one IPN application associated with it and in some embodiments an IPN application or process may be integrated with or into the network element (e.g., operating or running on the network element).
  • an IPN application or process may be integrated with or into the network element (e.g., operating or running on the network element).
  • each network element is illustrated as being connected to a separate IPN device that is operating an IPN application to manage the network element.
  • each of the nodes 110, 111, 112, 113, 114, 115 is in communication with a separate IPN.
  • the node 110 (also referred to as network element 110) is in communication with the IPN 120, the node 111 is in communication with the IPN 121, etc.
  • more than one node may be in communication with a single IPN (e.g.
  • IPN if the IPN is operating more than one IPN application to support multiple nodes), and/or more than one IPN may be connected to a single node.
  • an IPN while not required, in some embodiments an IPN also may be in communication with another IPN. Some of these connections may take place across different networks (e.g. IPN 121 and IPN 122). In some instances, an IPN may be connected to more than one other IPN, or not connected to an IPN at all (e.g. only connected to the INC and a node). Further discussion and description of an IPN is provided below.
  • Each of the IPNs 120, 121, 122, 123, 124, 125 also is in communication with the INC 130.
  • the INC 130 may interface with IPNs deployed in its domain via IP- based connectivity. As depicted in Figure 1A, the INC 130 does not effectively reside in any one network, but instead sits above all the networks. However, in some embodiments the INC 130 may actually reside in or be associated with a given network. Further, although Figure 1A depicts only one INC 130, more than one INC may exist.
  • the IPNs 110, 111, 120 and 121 for the network elements within the networks 101 may be in communication with one INC, while the IPNs 112, 113, 122 and 123 for the network elements in the network 102 may be in communication with a second or different INC.
  • the multiple INCs associated with the different networks may be in communication with each other or with a "master" INC, as will be discussed in more detail below.
  • each network may have its own associated INC that may communicate with INCs associated with other networks for provisioning circuits between nodes in the different networks, as will be discussed in more detail below.
  • the INC 130 maintains or includes the database 131.
  • the database 131 may include or contain information relating to the topology and capability of each of the networks 101, 102, 103 involved in the system 100.
  • the database 131 may be used to calculate paths for circuits within the involved networks. The endpoints of such paths may be within one network, or in different networks.
  • the database 131 may be used to calculate or otherwise determine a path between the node 110 in the network 101 and the node 114 in the network 103.
  • the database 131 may be internal to the INC 130 and/or be part of the INC 130.
  • the database 131 may be a real time database to support quick provisioning of circuits.
  • the customers 140, 141 may be in communication with the networks 101 and 103, respectively.
  • the customers may be or include carriers, Internet service providers (ISPs), corporations, individuals with desktop computers, LANs, WANs, etc.
  • ISPs Internet service providers
  • the customers 140 and 141 are represented as networks of nodes.
  • the customer 140 may represent a gigabit Ethernet corporate LAN, an IP router network, etc.
  • customers may also be in direct communication with at least one IPN, for example an IPN that is associated with a node.
  • the customer 140 is in communication with the IPN 120.
  • an IPN may be associated with a customer.
  • the customer 141 is in communication with IPN 128.
  • at least one customer may be in direct communication with the INC.
  • customers may be directly connected to each other, for example at a private peering point.
  • there may be no difference between customers and nodes.
  • the node 110 may be a customer, requesting a circuit be provisioned to, for example, the node 113.
  • a network of interconnected IPNs may form a signaling control plane, such as the signaling control plane 150 for the interconnected networks 101, 102, 103.
  • This control plane is capable of signaling at least one node in each of the networks for the configuration and provision of circuits that may cut across multiple networks.
  • a signaling control plane may utilize in-band or out-of band signaling.
  • a signaling control plane may interact with a network of optical switches using a separate IP control channel (out-of-band).
  • the signaling control plane may utilize e.g. unused SONET overhead bytes, or may make use of MPLS labels in a network of label-switched routers.
  • the signaling control plane may make use of a combination of in-band and out-of-band signaling.
  • each of the localized IPNs 120, 121, 122, 123, 124, 125 may perform a self-discovery process according to or during which information related to local network topology and capability is discovered, including information regarding capabilities of nodes associated with the IPNs 120, 121, 122, 123, 124, 125, information regarding connections between nodes within a network as well as cross- connections to nodes in other networks, etc. Inventory of the local network topology and capability for a node is stored locally at the IPN associated with the node and, in some embodiments, the IPN may provide or upload some or all of the information to the INC 130.
  • an IPN may communicate directly with a network element and construct a model or virtual representation of the network element.
  • the model provides a generic representation of the network element that can be stored in and used by the IPN.
  • An IPN may query a network element to determine the make, model, installed software releases, capabilities, configuration, connections, etc. (referred to herein as "inventory” or “operational characteristic” information) for the network element.
  • the network element may be capable of reporting to the IPN the facilities and capabilities the network element has as well as its configuration and/or other information.
  • the model or virtual representation of a network element inventoried by an IPN may be created in a generic fashion or consistent fashion across a domain or a signaling control plane.
  • a signaling control plane that includes the IPNs can manage and manipulate the network elements independent of the differences between the network elements.
  • an INC that receives information from an IPN regarding a network element can receive the information in a format or protocol that is independent of the vendor that supplied the network element, the type of network element, etc.
  • the INC for a domain can then store and use topology and capability information for network elements that is also in a format or protocol that is independent of the vendor that supplied the network element, the type of network element, etc.
  • a network element's associated IPN will covert any provisioning commands for the network element received by the IPN from the INC into commands suitable for the specific network element, thereby allowing a generic and consistent command set or format to be used for communications between the IPN and the INC. From the information provided by one or more IPNs, an INC can see and determine the resources available for provisioning a circuit in a vendor neutral manner and let the IPN(s) handle conversion of commands from the INC into vendor specific formats.
  • a request for the provisioning of a circuit is received by an IPN from a customer (which can be a node).
  • the IPN 120 may receive a request to provision a communication path from the node 110, the customer 140, etc.
  • a request from the node 110 to the IPN 110 may request that a communication path be provisioned between the node 110 and the node 115.
  • an IPN may receive a request directly from the customer, from a component in a management plane (e.g., an operator using a network management system application and requesting a circuit via a console), via a node, etc.
  • a request may include information relating to the circuit that is to be provisioned, e.g., addresses for the origination and destination of the circuit (e.g. IP addresses), the capacity required, the quality of service required, etc.
  • addresses for the origination and destination of the circuit e.g. IP addresses
  • the capacity required e.g. 1 MB
  • the quality of service required e.g. 1 MB
  • the IPN operating in conjunction with other IPNs and, in some embodiments, with the INC 130 and the database 131, may determines a path over which the requested circuit may be provisioned. The determined path may cut across multiple networks, or may be entirely within one network.
  • a first network may not have enough capacity to provision a requested circuit on its own, but may be able to provision dynamically a circuit across a peering partner's network to satisfy the request.
  • signaling commands may be sent from the IPNs to the appropriate network nodes, thereby configuring the nodes to set up a circuit along the determined path.
  • the circuit or other communication path may be tested and, based on successful testing, may be provisioned to the customer or other requester of the circuit.
  • the circuit is torn down, and the network segments used to make up the circuit are returned to inventory for future provisioning.
  • a communications system 160 may the include the computer, data or other communication networks or network domainslOl, 102 and 103, the nodes or network elements 110, 111, 112, 113, 114 and 115, the intelligent provisioning nodes (IPN) 120, 121, 122, 123, 124, 125 and 128, and the one or more customers 140 and 141 as previously discussed above.
  • the network 101 may have an associated INC 162 in connection with the IPNs 120 and 121.
  • the network 102 may have an associated INC 164 in connection with the IPNs 122 and 123 and the network 103 may have an associated INC 166 in communication with the IPNs 124 and 125.
  • the network 101 forms a domain for the INC 164
  • the network 101 forms a domain for the network 102
  • the network 103 forms a domain for the INC 168.
  • the INC 164 may be in communication with the INCs 162 and 166. Segmenting the IPNs 120 and 121, 122 and 123, and 124 and 125 across the INCs 162, 164 and 166, respectively, may reduce the management and performance burdens for any one INC and may allow enhance security measures to be used in the system 160. For example, the INC 162 may not be allowed or able to send provisioning commands to the IPNs 122, 123, 124 or 125 and may not receive or have inventory information for the network elements 112, 113, 114 and 115. In addition, changes in the network 102 and 103 and/or the network elements 112, 113, 114 and 115 do not need to be communicated to the INC 162.
  • Each of the INCs 162, 164, 166 may maintain topology and capability information for each of the network elements in its respective domain (e.g., the network elements 110 and 111 for the INC 162) but may not store such information for network elements outside its domain. Signaling between INCs may be used to broker provisioning transactions between network elements in different domains. The INCs may use security mechanisms to ensure that no proprietary information passes inappropriately to another network, as well as business/policy mechanisms to determine whether a request circuit should be provisioned.
  • the INC 162 may be in communication with, or include, a database or other resource 168.
  • the INC 164 may be in communication with, or include, a database or other resource 170 and the INC 166 may be in communication with, or include, a database or other resource 172.
  • the network elements 110 and 111 may form a data plane of components in or for the network 101 while the IPNs 120, 121 and the INC 162 may form part of or be included in a signaling control plane for the network 101.
  • the network elements 112 and 113 may form a data plane of components in or for the network 102 while the IPNs 122, 123 and the INC 164 may form part of or be included in a signaling control plane for the network 102.
  • the network elements 114 and 115 may form a data plane of components in or for the network 103 while the IPNs 124, 125 and the INC 166 may form part of or be included in a signaling control plane for the network 103.
  • the IPNs 120, 121, 122, 123, 124 and 125, along with the INCs 162, 164 and 166, may form a signaling control plane 180 for the network elements 110, 111, 112, 113, 114 and 115.
  • an INC or a signaling control plane may be connected to or in communication with a management plane.
  • the management plane may provide additional monitoring and management functionality for networks, network elements, etc. managed by the INC or the signaling control plane.
  • an IPN may be configured with the necessary "personality package” or other software, data, etc. specific to a network element under its control.
  • the IPN may be able to discover and maintain topology, inventory, alarm and configuration information for the network element as well as to issue provisioning commands to the network element.
  • the IPN also may translate network element specific information into a protocol or other format useable or recognizable by an INC.
  • the IPN 120 may determine inventory information for the network element 110 and provide such inventory information to the INC 162.
  • the INC 162 may store the inventory information in the database 168 or in a database internal to the INC 162.
  • the IPN 122 may inventory the network element 112 and provide the inventory information for the network element 112 to the INC 164.
  • the IPN 120 may perform a self-discovery process according to or during which information related to the network element 110 and upload or send such information to the INC 168.
  • the IPN 120 may communicate directly with the network element 110 and construct a model or virtual representation of the network element 110.
  • the model can provide a generic representation of the network element 110 that is independent of the vendor that created the network element.
  • a signaling control plane that includes multiple IPNs may form models of the IPNs' associated network elements in a consistent format and manner, regardless of differences (e.g., different types of equipment, different vendors supplying the network elements, different configurations of the network elements) in the network elements.
  • an IPN may receive provisioning commands from an INC, translate these commands into specific commands appropriate to its associated network element and execute the command on the network element.
  • the IPN provides network element or node control that allows provisioning of a circuit as instructed by the INC.
  • an IPN may be responsible for the management and control of its associated network element or some or all of the capabilities or features of the associated network element.
  • the IPN 120 may receive provisioning commands from the INC 162 for the network element 110 to configure circuits in or across the network 101.
  • the IPN 122 may receive provisioning commands from the INC 164 for the network element 112 as part of provisioning a circuit in or across the network 102.
  • one or more INCs may be used to provision a circuit between network elements in different networks.
  • the IPN 120 may receive a request for the provisioning of a circuit may between the network element 110 and the network element 113.
  • the IPN 120 may forward the request to the INC 162.
  • the INC 162 may determine that such a circuit will require a communication path through or via the network 102 and may forward the request to the INC 164.
  • the INC 162 and the INC 164 acting and communicating together may determine that the requested circuit will require a communication path using the network elements 110, 111, 112 and 113 (e.g., network elements in addition to the network elements designated in the request).
  • the INC 162 may send provisioning commands to the IPNs 120 and 121 relative to the network elements 110 and 111, respectively.
  • the INC 164 may send provisioning commands to the IPNs 112 and 113 relative to the network elements 112 and 113 respectively.
  • the IPNs 120, 121, 122, 123 may send the appropriate commands to the network elements 110, 111, 112, 113, respectively, to create the desired circuit. That is, the IPN 120 sends the appropriate command to the network element 110, the IPN 121 sends the appropriate command to the network element 111, etc. to establish the desired circuit between the network elements 110 and 111.
  • provisioning commands sent by an INC to an IPN regarding a network element may use a format or protocol that is vendor independent. The IPN may then convert the command into a vendor specific command for the network element and send the converted command to the network element.
  • the IPN 120 may receive a request for the provisioning of a circuit may between the network element 110 and the network element 115.
  • the IPN 120 may forward the request to the INC 162.
  • the INC 162 may not know what network the network element 115 is in and, as a result, may forward the request to the INC 164.
  • the INC 164 may be able to determine (e.g., by querying a database or network management system) that the network element 115 is in the network 103 and may forward the request to the INC 166. Communications between the INCs 162, 164 and 166 may commence to identify the needed network elements to create the desired circuit.
  • Various levels of security might be used for the communications across different INC domains to protect and secure proprietary network information.
  • the INC 164 acts as a sort of "master” INC for the INCs 162 and 166 and the network 102 acts as a sort of backbone network for circuits provisioned between a network element in the network 101 and a network element in the network 103.
  • a master INC for a backbone network may be used to facilitate provisioning of circuit between network elements in different regional or localized networks.
  • Each of the regional or localized networks may have its own INC that is in communication with the master INC.
  • each of the regional or localized networks may be connected to the backbone network via one or more network elements (herein referred to as "bridge elements").
  • the network element 111 and/or the network element 112 may operate as a bridge element to connect the networks 101 and 102.
  • the network element 113 and/or the network element 114 may operate as a bridge element to connect the networks 114 and 115.
  • INC to INC signaling may be used to determine if the requested circuit can be established and/or the location of the end point (e.g., the domain containing the network element forming the end point).
  • an INC receiving a request to provision a circuit between a first network element in the INCs domain and a second network element outside of it's domain may send all or part of a request to the master INC.
  • the master INC may identify a network or domain that includes the second network element and provide some or all of the request to an INC or signaling control plane associated with such network.
  • the master INC may coordinate provisioning of the circuit between the two network elements, which may include provisioning a portion of the circuit across a backbone network managed by the master INC.
  • the master INC may query other INCs to determine which domain the second network element is in.
  • the master INC may keep or have access to a database or other resource that maintains information regarding the location or network affiliation of network elements or that can determine such information on behalf of the master INC.
  • FIG. 2 an illustration of a representative system 200 that includes a management plane, signaling plane, and data plane is provided.
  • the system includes a data plane 202, a signaling control plane 204 and a management plane 206.
  • a data plane, signaling control plane and a management plane may form part of a network.
  • the data plane 202, a signaling control plane 204 and the management plane 206 may form part of or be included in the network 102.
  • a set of network elements and links between the network elements may form a data plane.
  • the nodes or network elements 112 and 113 and the link between them may form a data plane 202.
  • Network elements in the data plane may communicate with or be connected to other network elements (e.g., the node 112 is in communication with the node 111).
  • the IPNs 122, 123 associated with the nodes 112, 113 in the data plane 202, along with the INC 164, may comprise some or all of a signaling control plane 204 for the data plane 202.
  • the signaling control plane 204 (particularly the INC 164) may communicate with the management plane 206.
  • the signaling control plane 204 may mediate communication between the management plane 206 and the data plane 202 (e.g., between the management plane 206 and network elements in the data plane 202).
  • the signaling control plane 204 may determine routes for services through a managed domain of network elements.
  • the signaling control plane 204 can provide the signaling mechanisms to the network elements in the domain.
  • the signaling mechanisms may affect configuration changes in the managed network elements to provide services.
  • a signaling control plane may provide a unified interface from the managed network elements to various applications in the management plane 206.
  • the management plane 206 may include or comprise various applications and software processes and may be used to facilitate maintenance, control and operation of a network (which may include one or more domains monitored by an INC or a signaling control plane).
  • the management plane 206 may be implemented by one or more high performance servers or computer systems that may interface with other systems to provide overall network management.
  • the management plane 206 may comprise or include various applications and software processes to conduct, for example billing, troubleshooting, order management, etc.
  • an element management system (EMS) module 132 may be included in the management plane.
  • the EMS module 132 may communicate with network elements directly or via the signaling control plane 204.
  • a network element in a network is packaged with an EMS module which allows or provides control of the basic operation of the network element (e.g., setting up cross connects, receiving alarms).
  • An EMS module in a management plane may control, or facilitate control of, multiple network elements of the same type (e.g., the same type of router).
  • the EMS module 132 in the management plane 206 may allow or provide for the complete control of one or more network elements.
  • the control of a network element provided by the EMS module 132 may be more complete than the control of the network element provided by an IPN or a signaling control plane. That is, there may be functions of capabilities or aspects of a network element that cannot be, or are not allowed to be, controlled by an IPN associated with the network element.
  • the EMS module 132 may be used to provide and manage control of such capabilities or aspects of the network element.
  • the management plane 206 may include a network management system (NMS) module 134 and/or an operations support systems (OSS) module 136.
  • the NMS module 134 may be connected to or in communication with the EMS module 132 and/or the OSS module 136.
  • Each of the modules 132, 134, and/or 136 may include or represent multiple applications, each of which handles different needs of the management plane 206 or provides different functionality to the management plane 206.
  • the OSS module 136 may facilitate or allow communication with a network element and may communicate with the NMS module 134 and/or the EMS module 132.
  • the OSS module 136 may include one or more applications that handle network planning/design, order management, service level agreement management, billing, etc.
  • the NMS module 134 may operate "above" the EMS module 132 and provide control over a network (as opposed to just the equipment of a single vendor). For example, once a service for a network is designed, the service may be passed to an NMS module, which may then determine how to implement the service in the network and pass appropriate commands to the appropriate EMS modules to control or configure different portions of the network.
  • an IPN may be implemented by or on a computer, server, computer system, etc.
  • a computer, server, computer system, etc. may include a processor, one or more communication ports or hardware interfaces, one or more input devices (e.g., mouse, keyboard), one or more output devices (e.g., display, printer), and/or a data storage device or memory (e.g., hard drive, RAM, ROM).
  • IPN software processes and elements may be resident and operating or operational on the computer, server, computer system, etc., as described in more detail below.
  • the software may be stored on the data storage device and may include a control program, software modules, interfaces, etc. for operating the device, performing IPN functions, allowing the device to operate an IPN application, etc.
  • the control program may control the processor and the processor preferably performs instructions of the control program.
  • the control program may include program elements that may be necessary, such as an operating system, a database management system, and device drivers.
  • the IPN 300 can be implemented as software or a collection of software processes or elements.
  • an IPN (e.g., the IPN 120) may comprise an IPN application operating on a device.
  • an IPN application may reside and operate on a network element associated with the network element.
  • multiple IPN applications representing or implementing multiple IPNs (e.g., the IPNS 122 and 123) may operate on a single device.
  • the IPN 300 may include a network element driver 302 that allows the IPN to communicate or interface with a network element (e.g., the node 110) or an interface operating on the network element.
  • the network element driver 302 may be vendor specific or include a vendor specific component to allow the IPN 300 to communicate with a specific vendor's hardware. Different IPNs communicating with network elements from different vendors may have different network element drivers.
  • the IPN 300 also may include one or more software interfaces 304 that allow the IPN to communicate using standard interfaces (e.g., Tl-1, SNMP, XML, CORBA).
  • the network element driver 302 will facilitate communications between the software interface(s) 304 for the IPN 300 and the network element.
  • the IPN 300 also may include a virtual interface adapter 306 that may translate or parse information or communications exchanged between the network element and the IPN 300 from vendor specific formats or protocols used by the network element and the formats, protocols or information model used by the IPN
  • the network element may send an alarm to the IPN 300 indicated the occurrence of a fiber pull on the network element.
  • the virtual interface adapter 306 will translate the alarm information received from the network element into the information model used by the IPN 300.
  • the IPN 300 also may include a virtual network element model or inventory
  • the model or inventory 308 may represent an abstracted model of the network element.
  • the model or inventory 308 may be built, maintained, and updated by the IPN 300 to reflect the current state of the network element (e.g., inventory, resources, services associated with the network element) and may be formatted in a vendor abstracted model for use by a signaling control plane.
  • the IPN 300 may include one or more functional modules 310 that represent one or more functions that a signaling control plane that includes the IPN 300 may support or implement, including, but not limited to, inventory discovery and management of network elements.
  • a signaling connectivity module may allow the IPN 300 to transmit and receive messages across a signaling control plane (e.g., to other IPNs, to an INC).
  • a fault management module may provide functionality to monitor and manage faults generated within a data plane (e.g., by a network element) such as alarm correlation, alarm filtering, root cause analysis, etc.
  • a performance monitoring module may handle receiving and correlating of information relating to performance monitoring (e.g., SONET PM) from a data plane regarding provisioned services. For example, a provisioned circuit may span three "hops". The performance monitoring module may monitor all performance management data generated from the data plane regarding the circuit and correlate it as necessary.
  • a test and maintenance module may allow the IPN 300 or a signaling control plane to interact with test equipment that may exist in a network to facilitate testing of components or circuits.
  • a signaling control plane may configure specific network elements to establish a circuit and direct test equipment to perform tests on the circuit.
  • modules may allow a signaling control plane to assume some of the roles and functions traditionally handling by a management plane.
  • the signaling control plane may take over some or all of the functions of an EMS module operating in the management plane.
  • the IPN 300 may include a security engine 312 that represents one or more security mechanisms utilized by the IPN 300 to protect proprietary network information.
  • the security mechanisms may include encryption, policy directives indicating which entities are capable of receiving, or permitted to receive, certain information regarding certain actions, etc.
  • the IPN 300 may include an interface 314 to an INC (e.g., the INC 130) that allows or facilitates communication between the IPN 300 and the INC.
  • the IPN 300 may provide information regarding the network element to the INC via the interface 300.
  • the IPN 300 may receive commands from the INC via the interface 300.
  • the IPN 300 may include a user network interface (UNI) 316 that provides a UNI standard compliant interface through which customer devices that support the UNI standard may communicate with or signal directly to the IPN 300.
  • UNI user network interface
  • an INC may be implemented by or on a computer, server, computer system, etc.
  • a computer, server, computer system, etc. may include a processor, one or more communication ports or hardware interfaces, one or more input devices (e.g., mouse, keyboard), one or more output devices (e.g., display, printer), and/or a data storage device or memory (e.g., hard drive, RAM, ROM).
  • Software e.g., INC software processes and elements
  • the software may be stored on the data storage device and may include a control program, software modules, interfaces, etc. for operating the device, performing INC functions, allowing the device to operate an INC application, etc.
  • the control program may control the processor and the processor preferably performs instructions of the control program.
  • the control program may include program elements that may be necessary, such as an operating system, a database management system, and device drivers.
  • the INC 350 can be implemented as software or a collection of software processes or elements.
  • an INC may comprise an INC application operating on a device.
  • the INC 350 may include one or more IPN interfaces 352 that allow the INC 350 to communicate with IPNs.
  • the interface 352 for the INC 350 may communicate with the interface 314 on the IPN 300.
  • the INC 350 may include a database 354 for storing information.
  • the database may include information regarding the topology and capabilities of one or more network elements provided by IPNs. If the INC 350 is representative of the INC 130 of Figure 1, the database 354 may be or include the database 131 illustrated in Figure 1.
  • the INC 350 may include one or more functional modules 356 that represent one or more functions that a signaling control plane that includes the INC 350 may support or implement, including, but not limited to, inventory discovery and management of network elements. Providing such functions in a modular architecture facilitates the addition or subtraction of a given function based on the needs of the network and the signaling control plane.
  • a signaling connectivity module may allow the INC 350 to transmit and receive messages across a signaling control plane (e.g., to other IPNs and/or INCs).
  • a fault management module may provide functionality to monitor and manage faults generated within a data plane (e.g., by a network element) such as alarm correlation, alarm filtering, root cause analysis, etc.
  • a performance monitoring module may handle receiving and correlating of information relating to performance monitoring (e.g., SONET PM) from a data plane regarding provisioned services. For example, a provisioned circuit may span three "hops" The performance monitoring module may monitor all performance management data generated from the data plane regarding the circuit and correlate it as necessary.
  • a test and maintenance module may allow the INC 350 or a signaling control plane to interact with test equipment that may exist in a network to facilitate testing of components or circuits.
  • a signaling control plane may configure specific network elements to establish a circuit and direct test equipment to perform tests on the circuit.
  • functional modules included in an INC or used by an INC may allow a signaling control plane to assume some of the roles and functions traditionally handling by a management plane.
  • the signaling control plane may take over some or all of the functions of an EMS module operating in the management plane.
  • the INC 350 may include a security engine 358 that represents one or more security mechanisms utilized by the INC 358 to protect proprietary network information.
  • the security mechanisms may include encryption, policy directives indicating which entities are capable of receiving, or permitted to receive, certain information regarding certain actions, etc.
  • the security engine 358 also may be responsible for providing security for the transfer of information across INC domains or between INCs. This may include determining which INCs are considered "trusted", how much and which information can be provided, etc.
  • the INC 350 may include an interface 360 that may allow the INC 350 to communicate with other INCs. For example, the INC 350 may communicate requests for circuits to other INCs or other INC domains using the interface 360.
  • the INC 350 may include a command interface 362 that allows the INC 350 to translate information or communications sent to, and received from, management systems or other components (e.g., the EMS 132 of Figure 2) in a management control plane (e.g., the management control plane 204 of Figure 2).
  • the information or communications may be sent or received by the INC via one or more interfaces 364.
  • the INC 350 may use a UNI, NNI or GMPLS interface to communicate with a device, application, or other INC so that the device, application or other INC can sent a request to the INC 350 to provision a circuit.
  • the INC 350 may use a TL-1 or CORBA interface to communicate with a management plane.
  • the interface 362 may be used to translate communications sent by the INC 350 for one of the interfaces 364 and/or communications received via one of the interfaces 364.
  • a typical DWDM system may include an optical switch 400 having twelve transmission and reception ports 401, 402, 403, 404, 405, 406, 406, 408,409, 410, 411 and 412.
  • the DWDM system 300 may include an optical switch 500 having twelve transmission and reception ports 501, 502, 503, 504, 505, 506, 506, 508, 509, 510, 511 and 512. Since optical connections are typically unidirectional, it is necessary to utilize two links for bi-directional communication.
  • each port is typically comprised of a transmitter (T) and a receiver (R).
  • the optical switches 400 and 500 may be components connected to and inventoried by an IPN.
  • provisioning of a circuit may include inventorying and/or managing individual wavelengths used by optical switches such as the optical switches 400, 500.
  • the ports 401, 402, 403, 404, 405, 406, 406, 408,409, 410, 411 and 412 on the optical switch 400 are connected to DWDM equipment or devices 520, 521, 522.
  • the ports 501, 502, 503, 504, 505, 506, 506, 508, 509, 510, 511, 512 on the optical switch 500 are connected to DWDM equipment or devices 530, 531, 532.
  • the DWDM equipment or devices 520, 521, 522, 530, 531, 532 may function to "multiplex" many optical signals together for transmission on a single fiber optical link 551, 552, 553, 554, 555, 556, 557 or 558 and "de-multiplex" these signals for individual switching. Groups of the single fiber optical links 551, 552, 553, 554, 555, 556, 557, 558 are then variously bundled together in link bundles by the devices 572, 573. It is common for multiple optical links to be so bundled when they are planted in order to save on infrastructure costs. However, this bundling can be problematic when, for example, a link bundle is damaged (e.g.
  • the resource may contain or include current inventory and connection information related to the links between network nodes available to the system, and is typically maintained by an INC.
  • the resource may be implemented using in-memory and/or real time database technology, similar to that offered by companies such as TimesTen, Inc. Such database technology offers the high levels of performance necessary to accomplish the provisioning of circuits in very short time periods (e.g., 50 mis).
  • the resource, or portions of it may be replicated across multiple locations within one or multiple networks for easier access.
  • a resource may form part of or be included in an IPN (e.g., as the database 354 in the INC 350).
  • a resource may be populated using a variety of techniques, including self-discovery, multicast requests, etc.
  • each IPN performs a self-discovery process in order to collect network topology and capability information related to the links and network elements that are local to the IPN, including links between networks, nodes, etc. Further, changes in network topology, such as the addition or deletion of network nodes or modification of a node (e.g., changing or addition of a new port card in a switch), may trigger a self-discovery process.
  • Each IPN forwards this information to one or more INCs (e.g., the INC 130) for storage in the resource (e.g., the resource 131).
  • INCs e.g., the INC 130
  • Information stored in the resource may be analyzed in order to create a centralized map of the entire network available to the system.
  • an IPN may be able to detect, receive or capture a report database change signal generated by a network element. The IPN may then update its database or model of the network element and forward information to an INC regarding the change to the network element.
  • Figure 6 illustrates examples of two records 620 and 622 that may be stored in the resource 131. Included in each record is a node ID 624 that identifies a network node. For example, the node ID may be an IP address. Associated with each node ID is a number of port IDs 626 that identify individual ports on the node.
  • the protocol field 628 identifies the data protocol (encapsulation method) run over the port, for example SONET, Gigabit Ethernet, etc.
  • the bandwidth field 630 identifies the bandwidth of the connection associated with the port, for example T-3, OC-12, etc.
  • the link bundle in which a given link between nodes resides it may be necessary to track the link bundle in which a given link between nodes resides. For example, in embodiments where the system determines two paths for a given request (one for use, one for back-up), it may be advantageous if the two paths do not include links in the same link bundles. In this manner, should an entire link bundle become damaged (e.g. cut by a back-hoe), the second determined path should not be affected.
  • the Shared Risk Link Group (SRLG) addressing scheme may be implemented to accomplish this.
  • the resource 131 may track a number of other parameters related to connections within and across the networks involved. These parameters may reflect both technical concerns as well as business concerns. Some of the parameters may be automatically discovered via a self-discovery process, while others may be manually entered and associated with a given connection. Such parameters may include those a customer may request or included in a request to provision a circuit or connection, such as, for example, endpoints for the connection (e.g., IP addresses), bandwidth for the connection (e.g., OC-12), security for the connection, protocol for the connection (e.g., IP), and/or a term of the connection (e.g., one hour). In some embodiments, the customer or other requester also may designate or specify some performance related constraints.
  • endpoints for the connection e.g., IP addresses
  • bandwidth for the connection e.g., OC-12
  • security for the connection e.g., protocol for the connection (e.g., IP)
  • a term of the connection e.g., one hour
  • performance metrics/constraints may include latency, failover flexibility, packet loss, bit error rate, number of hops for a connection, etc.
  • additional ' constraints may include constraints on resources or capabilities that may be required for a connection to be established. These constraints may be invisible to the customer, and may include, for example, available wavelength(s), wavelength conversion, device compatibility (at client, metro, core, etc.), mux/demux speed and availability, MPLS capabilities, OSS links, alarms, scheduling, network percentage fulfillment, etc.
  • parameters associated with technical constraints that may be related to a connection may be stored in the resource 131 as well, such as, for example: power, polarization, type of fiber, amplification mechanism, etc.
  • IPNs In order to keep the information stored in the resource 131 as up-to-date as possible, periodic self-discovery updates may be performed by IPNs. Updates may be received from the IPNs, through other applications, by network operators, etc. Further, changes in a network, such as added or subtracted nodes, ports, etc. may trigger a self-discovery process by one or more IPNs so that changes in network topology may be reflected in the resource 131 in a timely manner. In some embodiments, data stored by one or more INCs, IPNs, network elements, etc. may be compared for accuracy and consistency as part of an audit process
  • the information stored in the resource 131 may be kept confidential so that, for example, competing network service providers are not given visibility into each other's networks.
  • an entity that operates and maintains the network of IPNs and INC(s) may be a "carrier-neutral" entity, providing the service to any/all qualifying network service providers.
  • each network may maintain a separate INC containing information related only to the given network.
  • some or all of the information stored in or by the resource 131 may also, or instead, be stored at the IPN level.
  • various levels of hierarchical layers with regard to the nodes, IPNs and INCs may be implemented.
  • the present invention may function with no centralized control (e.g., no INC 130 or resource 131), with all decision-making happening in a distributed manner by IPNs.
  • the present invention may employ a single master INC to control the multiple INCs, thereby creating three levels of signaling control: (1) IPNs, (2) INCs, and (3) master INC. It should be noted that additional layers of signaling control may be implemented.
  • FIG. 7A, 7B and 7C a flow chart 700 is shown which represents the operation of a first embodiment of the present invention.
  • the particular arrangement of elements in the flow chart 700 is not meant to imply a fixed order to the steps; embodiments of the present invention can be practiced in any order that is practicable.
  • the method 700 is particularly well suited for determining and provisioning a circuited in a centralized manner.
  • Processing for the method 700 begins at a step 701.
  • an application, router, desktop, node, customer, network element, etc. sends a request to a local IPN requesting provisioning of a circuit or other communication path.
  • a request for a circuit is sent by a customer or other device or application and received by an IPN.
  • the customer 140 may transmit a request for a circuit to the IPN 120.
  • the customer 140 may represent, for example, a network of IP routers, where the request is sent from an IP router that acts as a border for the network of routers.
  • the customer 140 may represent a desktop computer from with a request may be initiated e.g.
  • the request may be a web-based request, where a customer logs onto a Web page and enters a request via the Web page.
  • the network administrator of a data center may log onto a Web page and request an additional optical circuit be provisioned between the data center and, for example, a second data center.
  • a request may include information related to the circuit that is to be provisioned. This information may include addresses (e.g., IP addresses, BGP addressees) of the endpoints (e.g., ingress node, egress node) of the circuit .
  • addresses e.g., IP addresses, BGP addressees
  • the request may include varying levels of specificity regarding the endpoints of the requested circuit. For example, the request may specify which ports on the switches should be used, what wavelength should be used, etc. Further, a request may include the bandwidth required (e.g. OC-12, OC-3), the term desired (e.g.
  • a request will typically also include other parameters with which the provisioned circuit must comply. These parameters may comprise technical requirements, security requirements, business requirements, etc. For example, the request may specify a required quality of service (QoS), acceptable costs, redundancy requirements, etc.
  • QoS quality of service
  • An example request is illustrated in record 703 of Figure 7 A for a circuit to be provisioned between an ingress node identified as "132.53.521.3" and an egress node identified as "145.234.5.3".
  • a customer may specify acceptable parameters in the request, or the customer may have defined default parameters.
  • the customer may register a profile where the profile defines a number of default values for the various parameters. The customer's profile may be accessed when a request is received from the customer. In this way, the customer is not required to indicate all the parameters desired in every request.
  • sets of default parameters associated with each application may be maintained by an IPN, an INC, the resource 131 or other entity or device. For example, if a request is received for a circuit that is to be used for video conferencing, the INC 130 may access a set of default parameters that must typically be met for a video conferencing application to function properly.
  • the sending of the request may be triggered in a number of ways.
  • a request may be triggered manually, for example, by a network administrator operating the border IP router.
  • an application running on or in conjunction with the border IP router may trigger a request.
  • heavy traffic levels may cause congestion along certain routes associated with the network of IP routers (and networks to which it is connected).
  • An application may be developed that automatically launches a request for additional bandwidth along a given route when e.g. traffic or congestion levels exceed certain threshold parameters.
  • layer three-type activity e.g. at the IP layer
  • a local IPN receives the request sent during the step 701.
  • the customer 140 may have a direct connection (e.g., an IP connection) to the IPN 120 over which a request from the customer 140 can be sent to the IPN 120.
  • a customer may send the request to a network node, for example, the node 110. The request would then be forwarded from the node 110 to the IPN 120 for processing. In other embodiments, the request may instead be sent by the customer 140 directly to the INC 130, bypassing the IPN 120 all together.
  • a determination is made regarding whether a direct connection is available between the ingress node and the egress node.
  • the IPN 120 may first determine whether a direct connection exists between the egress node specified in the request and the ingress node to which the IPN 120 is in communication. Information related to local node reachability and capability is typically available to the IPN 120. For example, a link state database may be maintained at the node 110 (or at the IPN 120). Such a database would contain information related to all the connections from the node 110. The IPN 120 compares the parameters specified in the request to the parameters associated with the connections currently available in order to determine whether any available connections satisfy the parameters of the request. If the result of the step 706 is that a direct connection exists between the ingress node and the egress node, the method 700 proceeds to a step 708. If no such connection exists, the method 700 proceeds to a step 710.
  • the local IPN if a direct connection is available between the egress node and the ingress node, the local IPN immediately reserves the direct connection and provisions it for the customer. During the step 710, without a direct connection to the egress node specified in the request, the local IPN sends the request to an INC (e.g., the INC 130) for additional processing.
  • an INC e.g., the INC 130
  • the INC that receives the request from the local IPN queries the resource 131 (which may be internal to or part of the INC) for at least one path from the ingress to the egress node specified in the request.
  • the resource 131 maintains information relating to the topology and capability of the networks and nodes involved in the inventive system. Based on this information, the INC is able to compute a path through at least one of the involved networks to connect the ingress and egress nodes specified in the request. Path calculation may be based on such protocols as Open Shortest Path First (OSPF), Intermediate System to Intermediate System (ISIS), etc.
  • OSPF Open Shortest Path First
  • ISIS Intermediate System to Intermediate System
  • the resource 131 may contain varying amounts of additional information regarding the connections available to the system.
  • the resource 131 may contain enough current information for the INC to determine a path form the ingress to the egress node that meets all of the requirements set forth in the request.
  • the resource 131 only may contain enough information for the INC to determine at least one path between the egress and ingress node without being able to verify that the path(s) fulfill the other parameters specified in the request. In such cases, it is necessary for the INC to signal each of the nodes in the path in order to determine whether the path meets the parameters of the request.
  • step 714 if the INC determines that no paths exist between the ingress and egress nodes designated in the request, then the method 700 proceeds to a step 716. If the INC determines that at least one path does exist between the ingress and egress nodes designated in the request, then the method continues to a step 718.
  • a failure message may be sent to the customer or other requester, indicating that the system currently cannot fulfill the request.
  • the INC retrieves information relating to the determined path(s) from the resource 131.
  • the retrieved information may include node addresses, port IDs, wavelengths, etc.
  • the INC may retrieve at least two paths for a request.
  • the request may specify that at least two paths must be determined for protection purposes.
  • An example response to the request is illustrated in record 719 of Figure 7 A, which lists two paths for a circuit to be provisioned between an ingress node identified as "132.53.521.3" and an egress node identified as "145.234.5.3". One of the paths includes a node identified as "124.43.3.6" while the second path includes a node identified as "273.87.23.4".
  • the INC transmits resource reservation command to each node (IPN) in communication path(s)determined between the ingress and egress nodes specified in the request.
  • a resource reservation command instructs the receiving node to reserve requested resources for the customers use.
  • the command may include the port ID, wavelength, bandwidth, etc. that must be reserved for use in the determined path.
  • reserve resource commands also may be sent to nodes that make up protection paths as well.
  • IPNs #1, #2,...N receive resource reservation command and queries link state database for resource availability.
  • Each of the IPNs that make up the determined communication path(s) receives the resource reservation command from the INC and determines whether the requested resources are available by querying a link state database.
  • the steps 722A, 722B, 722C, etc. may not be necessary if, for example, the resource 131 contains enough current information about the link states in each node.
  • steps 724A, 724B, 724C,...724N if the resources associated with an IPN specified in the resource reservation command are not available, then the method proceeds to a step 726. If, on the other hand, the resources specified in the resource reservation command are available, then the method 700 proceeds to steps 728A, 728b and 728C.
  • the IPN may signal the INC to select an alternate path for that network segment, or for the entire path. If such an alternate path exists, then processing proceeds as before. If no such path exists, than the INC signals the customer that a path cannot be provisioned at that time, and processing ends.
  • the IPN signals a successful resource reservation to the INC, indicating, for example, that the resources are available, and any additional information regarding the resources necessary, such as port ID, wavelength, etc.
  • Example resource reservations that may be sent to the INC are illustrated in records 729 A, 729B and 729C of Figure 7B, each of which identifies a specific switch and a port of the switch that has been reserved.
  • the INC issues a provisioning command, instructing the IPNs to provision the determined communication path.
  • steps 732A, 732B, 732C,...732N IPNs #1, #2,...N execute provisioning commands received from the INC and signal completion to the INC.
  • the INC receives provision completion signals from the appropriate IPNs and signals the IPNs to test the communication path.
  • the step 734 may be optional in some embodiments of the method 700.
  • the appropriate IPNs test the provisioned communication path. Testing of a provisioned communication path is described in further detail below.
  • the step 736 may be optional in some embodiments of the method 700.
  • the INC transmits a provisioning command to a protection circuit. That is, in some embodiments the system may determine more than one path for the entire initial path or portions of it depending on the level of protection specified in the request. In those cases where the initial path that is provisioned fails testing, the protection path may be provisioned instead. In some embodiments, additional error detection steps may be taken to determine, for example, which links in the connection are responsible for the failing, which links may be provisioned to route around the failure etc.
  • the step 740 may be optional in some embodiments of the method 700.
  • the provisioned circuit or communication path may be handed off to the customer or requestor or is otherwise provided for use.
  • the provisioned circuit or communication path may be monitored for failure or quality of service degradation.
  • the step 744 may be optional in some embodiments of the method 700.
  • the INC signals each IPN to release the resources that make up each segment of the circuit.
  • the individual IPNs may track circuit terms and release resources automatically.
  • FIG. 8A, 8B and 8C where a flow chart 800 is shown which represents the operation of a second embodiment of the present invention.
  • the particular arrangement of elements in the flow chart 800 is not meant to imply a fixed order to the steps; embodiments of the present invention can be practiced in any order that is practicable.
  • the method 800 is particularly well suited for determining and provisioning a circuit in a distributed manner.
  • Processing for the method 800 begins at a step 801.
  • an application, router, desktop, node, customer, network element, etc. sends a request to a local IPN requesting provisioning of a circuit or other communication path.
  • the step 802 is similar to the step 702 previously discussed above.
  • a local IPN receives the request.
  • the step 804 is similar to the step 704 previously discussed above.
  • the step 806 is similar to the step 706 previously discussed above. If the result of the step 806 is that a direct connection exists between the ingress node and the egress node, the method 800 proceeds to a step 808. If no such connection exists, the method 800 proceeds to a step 810.
  • step 808 if a direct connection is available between the egress node and the ingress node, the local IPN immediately reserves the direct connection and provisions it for the customer.
  • the step 808 is similar to the step 708 previously discussed above.
  • the local IPN sends the request to an IPN associated with the egress node.
  • steps 812A and 812B link state databases are queried for connections that fulfill the parameters specified in the request.
  • the letters "A” and “B” next to step numbers refers to the same step happening in different nodes, IPNs, etc.
  • IPNs etc.
  • Each IPN queries its associated link state database to determine whether any direct connections are available that meet the parameters set forth in the request. For example, a request may specify an amount of bandwidth, term, security, etc. The query is performed to determine whether any connections currently available fulfill those requirements.
  • steps 814A and 814B if there is not at least one such connection that fulfills the parameters specified in the request, then the method 800 proceeds to a step 816. If there is at least one such connection, then the method 800 proceeds to a step 818. During the step 816, if no direct connection to either the ingress or egress node exists that fulfills the requirements set forth in the request, then the customer or other requester is sent a failure notice indicating that their request cannot be met. In some embodiments, additional programming may determine whether a connection that is currently set up may be torn down in favor of the current request.
  • connection identifier(s) associated with connections that fulfill request parameters are retrieved by the ingress and egress IPNs, respectively.
  • each IPN transmits a reserve resource command to its associated node in order to reserve the connections associated with the retrieved connection identifiers.
  • steps 822A and 822B having identified the connections that fulfill the requirements set forth in the request, IDs associated with the IPNs that form the opposite ends of those connections are determined. This information may be retrieved from the link state database.
  • the request is then sent only to those IPNs that reside on the opposite side of the connections that fulfill the requirements set forth in the request. Such IPNs receive the request during steps 826A and 826B.
  • each IPN that receives the request first determines whether the same request was already received from an IPN in the egress/ingress request tree. If it was, that means that the IPN that received both now has a complete path from ingress to egress node that fulfills the requirements set forth in the request. If the request was not also received from the egress/ingress request tree, then the method 800 continues to steps 830A, 830B. If the request was also received from the egress/ingress request tree, then the method 800 proceeds to a step 834.
  • Each request includes a "time to live" value that is set when the request is created.
  • the time-to-live value may represent a time after which the request is no longer valid. In this manner, the inventive system can control the spread of requests through the interconnected networks. If the request has timed out, then the method 800 proceeds to step 832 where the method 800 ends. If the request has not timed out, then the method 800 proceeds to steps 812A, 812B.
  • step 834 information related to the complete path is next sent to the customer for approval. If the customer does not approve of the path, then the method 800 proceeds to a step 838. If the customer does approve of the path, then the method 800 proceeds to a step 840. During the step 838, if the customer does not approve the determined connection or path, then the method 838 may attempt to determine another connection that the customer may approve as described above.
  • step 840 if a customer approval is received for the path, then a provision command is sent to every IPN in the path, instructing the IPNs to provision the circuit specified in the path.
  • the step 840 is similar to the step 740 previously discussed above.
  • a step 842 the provisioned communication path is tested.
  • the step 842 is similar to the step 736 previously described above.
  • a step 844 a determination is made regarding whether or not the test conducted during the step 842 is successful.
  • the step 844 is similar to the step 738 previously discussed above. If the test is not successful, then the method 800 proceeds to a step 846. If the test is successful, then the method 800 proceeds to step a 848.
  • the method 800 may determine more than one path for the entire initial path or portions of it depending on the level of protection specified in the request. In those cases where the initial path that is provisioned fails testing, the protection path may be provisioned instead during a step 846. In some embodiments, additional error detection steps may be taken to determine e.g. which links in the connection are responsible for the failing, which links may be provisioned to route around the failure etc.
  • the provisioned circuit or communication path may be handed off to the customer or requestor or is otherwise provided for use.
  • the step 848 is similar to the step 742 previously discussed above.
  • the provisioned circuit or communication path may be monitored for failure or quality of service degradation.
  • the step 850 may be optional in some embodiments of the method 800.
  • the step 850 is similar to the step 744 previously discussed above.
  • the step 852 is similar to the step 746 previously discussed above.
  • each IPN releases the resources that make up each segment of the circuit.
  • the individual IPNs may track circuit terms and release resources automatically.
  • an IPN in addition to a signaling connection, may have a data connection to its corresponding node.
  • IPNs may test circuits set up or provisioned by the methods and apparatus of the inventive system.
  • An IPN 902 is connected to a node 904 via signaling a connection 910 and a data connection 912.
  • an IPN 906 is connected to a node 908 via a signaling connection 914 and a data connection 916.
  • the nodes 904 and 908 are connected to each other via a data connection 918.
  • the IPNs 902 and 906 are connected to each other via signaling a connection 920.
  • data connection 918 may not be a direct connection, but may include a number of intermediate segments.
  • the IPN 902 may configure the node 904 to transmit data to the node 908 over the data connection 918. This configuration may take place over the signaling connection 910. To test the connection between the nodes 904 and 908, the IPN 902 may signal the IPN 906 over the signaling connection 920, informing the node 906 that the node 904 is about to send a test data transmission. The IPN 902 may then transmit a data signal to the node 904 over the data connection 912 that is to be switched to the node 906. If the node 906 receives the data signal, then the signal is switched to the IPN 906 via the data connection 916.
  • the IPN 906 Upon receiving the data signal, the IPN 906 informs the IPN 902 via the signaling connection 920 that the data transmission was successfully received. If the IPN 902 does not receive the confirmation signal from the IPN 906 within a set time period, then the IPN 902 concludes that the data transmission was not received, and the test of the connection failed.
  • Figures 10A, 10B and IOC a representative depiction of how the methods and apparatus of the present invention may affects different layers of a network is illustrated.
  • the nodes that accommodate routing and/or switching typically operate at up to the third layer (the network layer) of the
  • IP International Standard Organization's Open System Interconnect
  • a very common network layer protocol is the IP protocol, which forms a significant portion of all traffic in communication networks today, and accommodates the routing of individual IP datagrams in a connectionless environment.
  • IP IP
  • all nodes could support layer 3, but this is inefficient due to the high cost of operation associated per interface port.
  • equipment is available that only operate at up to layer 2 (the datalink layer, e.g., SONET/SDH or Ethernet), or even only layer 1 (e.g., DWDM). Due to the lack of good management tools, the equipment can currently switch (or route) data on only one layer. Cooperation between the layers to efficiently switch/route data is currently impossible.
  • a SONET node can only switch SONET frames (it cannot simultaneously switch wavelengths or route IP datagrams), an IP router can only route IP datagrams, even if this IP router operates with SONET as a datalink layer.
  • Layer 1 switching can currently be accommodated solely in the electrical domain (for example in current LANs across coaxial cable), a combination of the photonic and electrical domain, and solely in the photonic domain (for example, with MEMS technology).
  • layer 2 protocols that provide the framing to enable the transfer of the data across the physical medium, these protocols include SONET/SDH and Ethernet.
  • the third layer, the network layer is responsible for the routing of data in the network; one example is the IP protocol.
  • a switch/router managed by an IPN could accommodate any combination of these protocols, and it is the IPNs responsibility to ensure that a connection's agreed upon requirements will not be affected by any translations in a node. Together with this, it is also the IPNs responsibility to program the switch to enable it to effectively translate data between any layers to enable the transmission between networks that operate using different protocols.
  • Figure 10A depicts the interface between each layer of a switch 950 and its managing IPN 952. Also depicted is the path of data through a switch if no translation is required. Without any electrical conversion it is currently impossible to extract the data from an optical signal, this capability may be available in the future. In this case a node is only capable of layer 1 switching. The moment a node is able to receive an electrical signal or convert an incoming photonic signal to its electronic form, it is able to extract the layer 3 data, which enables it to encapsulate and transfer it using a different datalink (layer 2) protocol.
  • layer 2 datalink
  • the IPN 952 can efficiently manage the switch 950. Instead of hard- provisioning the interfaces, the IPN 952 is able to initiate translations between different network layers based upon criteria that can range from cost to utilization.
  • the cost may, for example, be a price associated per interface where translation at the network layer is the most expensive and that at the physical layer the cheapest.
  • FIG. 10B An example of the above is depicted in Figure 10B.
  • the layer 1 protocol remained the same while the layer 2 protocol is changed to enable communication between the interconnected networks.
  • the reason for this translation may be caused by high utilization on one interface, or an increase in cost associated with it.
  • the IPN will in this case first map the connection requirements to make the connections across the different datalink layers equivalent in their quality of service, and then proceeds with the programming of the fabric to accommodate this conversion.
  • FIG 10B shows the flexibility introduced with the usage of a managing IPN.
  • the managing IPN 1003 was able to set up a datalink layer connection between the first switch 1002 and the second switch 104, as well as the second switch 1004 and the third switch 1006, while managing the translation at the second switch 1004 to enable the data transfer between these two connections.
  • the IPN 1003 used its intelligence to determine the cheapest connection based on all the cost parameters.
  • the managing IPN 1051 was able to set up a physical layer connection through the first switch 1052 and the third switch 1056, while managing the translation of the data in the second switch 1054.
  • FIG. IOC Another possible conversion is depicted in Figure IOC.
  • the data link layer needs to remain the same while the data needs to be sent across different physical layer for the switches 1102, 1104, 1106.
  • the IPN 1108 (or one of the other IPN 1110, 1112 if the IPN 1108 is not the managing IPN for the switch 1104 and/or the switch 1106) will consider the properties of both the photonic and electrical domains to provide the requestor with its requested quality of service.
  • the IPN 1108 will also program the switch fabric to enable this translation to occur dynamically.
  • an IPN may act as a link between applications requesting circuits and layers 1, 2, 3 of a network.
  • the methods and apparatus of the present invention may utilize a combination of in-band and out-of-band signaling and can manage QoS issues for many connections, e.g., IP transmissions by provisioning connections and by, redirecting IP traffic flows (e.g. MPLS) to the connections in order to divert the traffic flows from congested areas of the network.
  • IP traffic flows e.g. MPLS
  • the present invention allows select applications to request guaranteed QoS by provision on-demand circuits while other traffic uses shared pipes with, for example, RSVP and diffserv. Signaling between networks and IPNs (e.g. handshakes) may take place in advance to and during transaction setup and provisioning.
  • the methods and apparatus of the present invention may be utilized to dynamically allocate connections, e.g. legacy SONET rings, by enabling edge nodes with IPNs and/or to update router MPLS and BGP tables through IPN updates.
  • the methods and apparatus of the present invention allow for or facilitate the dynamic concatenation of network segments from multiple service providers for failures and maintenance cutovers.
  • the methods and apparatus of the present invention may be utilized to eliminating as many L3 and L2 transactions in order to reduce the cost of routing and switching in the network.
  • the methods of the present invention may be embodied as a computer program developed using an object oriented language that allows the modeling of complex systems with modular objects to create abstractions that are representative of real world, physical objects and their interrelationships.
  • object oriented language that allows the modeling of complex systems with modular objects to create abstractions that are representative of real world, physical objects and their interrelationships.
  • the invention as described herein could be implemented in many different ways using a wide range of programming techniques as well as general-purpose hardware systems or dedicated controllers, computers, processors, etc.
  • many, if not all, of the steps for the methods described above are optional or can be combined or performed in one or more alternative orders or sequences without departing from the scope of the present invention and the claims should not be construed as being limited to any particular order or sequence, unless specifically indicated.
  • Each of the methods described above can be performed on a single computer, computer system, microprocessor, etc.
  • two or more of the steps in each of the methods described above could be performed on two or more different computers, computer systems, microprocessors, etc., some or all of which may be locally or remotely configured.
  • the methods can be implemented in any sort or implementation of computer software, program, sets of instructions, code, ASIC, or specially designed chips, logic gates, or other hardware structured to directly effect or implement such software, programs, sets of instructions or code.
  • the computer software, program, sets of instructions or code can be storable, writeable, or savable on any computer usable or readable media or other program storage device or media such as a floppy or other magnetic or optical disk, magnetic or optical tape, CD- ROM, DVD, punch cards, paper tape, hard disk drive, ZipTM disk, flash or optical memory card, microprocessor, solid state memory device, RAM, EPROM, or ROM.

Landscapes

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

Abstract

La présente invention permet et facilite l'approvisionnement en temps réel de circuits ou d'autres voies de communication à travers des réseaux à multiporteuses, à multivendeurs. Dans un réseau présentant des éléments réseau, chaque élément réseau est associé à un noeud d'approvisionnement intelligent qui peut inventorier l'élément réseau pour déterminer la topologie, les capacités et les connexions de l'élément réseau. Le noeud d'approvisionnement intelligent peut faire partie d'un plan de contrôle de signalisation qui peut gérer des éléments réseau pour approvisionner un circuit entre des éléments réseau.
PCT/US2002/020083 2001-06-22 2002-06-21 Procede et appareil d'approvisionnement d'une voie de communication WO2003001397A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CA002451042A CA2451042A1 (fr) 2001-06-22 2002-06-21 Procede et appareil d'approvisionnement d'une voie de communication

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US30052701P 2001-06-22 2001-06-22
US60/300,527 2001-06-22

Publications (1)

Publication Number Publication Date
WO2003001397A1 true WO2003001397A1 (fr) 2003-01-03

Family

ID=23159471

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2002/020083 WO2003001397A1 (fr) 2001-06-22 2002-06-21 Procede et appareil d'approvisionnement d'une voie de communication

Country Status (2)

Country Link
CA (1) CA2451042A1 (fr)
WO (1) WO2003001397A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011032595A1 (fr) 2009-09-18 2011-03-24 Nokia Siemens Networks Gmbh & Co. Kg Contrôleur de réseau virtuel
WO2015067827A1 (fr) * 2013-11-06 2015-05-14 Telefonica, S.A. Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur
CN107134124A (zh) * 2017-05-03 2017-09-05 杭州西力智能科技股份有限公司 宽带载波通信模块载波芯片抄表接口统一管理控制方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5935209A (en) * 1996-09-09 1999-08-10 Next Level Communications System and method for managing fiber-to-the-curb network elements
US20010033551A1 (en) * 1993-11-30 2001-10-25 British Telecommunications Communications network management
US20020019866A1 (en) * 2000-08-09 2002-02-14 Linzy Richard J. System and method for monitoring and maintaining a communication network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010033551A1 (en) * 1993-11-30 2001-10-25 British Telecommunications Communications network management
US5935209A (en) * 1996-09-09 1999-08-10 Next Level Communications System and method for managing fiber-to-the-curb network elements
US20020019866A1 (en) * 2000-08-09 2002-02-14 Linzy Richard J. System and method for monitoring and maintaining a communication network

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011032595A1 (fr) 2009-09-18 2011-03-24 Nokia Siemens Networks Gmbh & Co. Kg Contrôleur de réseau virtuel
US9537730B2 (en) 2009-09-18 2017-01-03 Nokia Solutions And Networks Gmbh & Co. Kg Virtual network controller
EP2478667B1 (fr) * 2009-09-18 2019-11-27 Nokia Solutions and Networks GmbH & Co. KG Contrôleur de réseau virtuel
WO2015067827A1 (fr) * 2013-11-06 2015-05-14 Telefonica, S.A. Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur
CN107134124A (zh) * 2017-05-03 2017-09-05 杭州西力智能科技股份有限公司 宽带载波通信模块载波芯片抄表接口统一管理控制方法

Also Published As

Publication number Publication date
CA2451042A1 (fr) 2003-01-03

Similar Documents

Publication Publication Date Title
US6757297B1 (en) Method and apparatus for dynamic configuration and checking of network connections via out-of-band monitoring
US9672121B2 (en) Methods and systems for automatically rerouting logical circuit data
US20020143929A1 (en) Method and system for collection and storage of traffic data from heterogeneous network elements in a computer network
US8812665B2 (en) Monitoring for and responding to quality of service events in a multi-layered communication system
US20020143928A1 (en) Method and system for collection and storage of traffic data in a computer network
US8345537B2 (en) Methods and systems for automatically rerouting logical circuit data from a logical circuit failure to a dedicated backup circuit in a data network
US20040213221A1 (en) System and method for soft bandwidth
US7609623B2 (en) Method and system for automatically rerouting data from an overbalanced logical circuit in a data network
US7275192B2 (en) Method and system for on demand selective rerouting of logical circuit data in a data network
US20020143926A1 (en) Method and system for collecting traffic data in a computer network
US20020141342A1 (en) Method and system for automatically directing data in a computer network
US20090279551A1 (en) Vertical integration of network management for ethernet and the optical transport
US20020143927A1 (en) Method and system for configuring a network element in a computer network
US20020141351A1 (en) Method and system for validating network transformation instructions
WO2003001397A1 (fr) Procede et appareil d'approvisionnement d'une voie de communication
Chadha et al. PECAN: Policy-enabled configuration across networks
KR20010083904A (ko) 통신 네트워크에서의 경로선택 관리
WO2007084597A2 (fr) Système, réseau et procédés pour fournir des circuits optiques dans un environnement multiréseau à plusieurs fournisseurs
KR20010080170A (ko) 통신 네트워크에서의 종단 관리
Liu et al. On the tradeoffs between path computation efficiency and information abstraction in optical mesh networks
KR101006804B1 (ko) Ａｔｍ 망관리시스템에서의 소프트-ｐｖｃ정보 관리방법
McGuire et al. Architecting the Automatically Switched Transport Network: ITU-T Control Plane Recommendation Framework
Interface S tandards S tandar
Fogliata et al. Role of network management in network restoration and resilience.
Berde et al. An Experience on Implementing Network Management for a GMPLS Network

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 2451042

Country of ref document: CA

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP