Using path computation element communication protocol (PCEP) as a signalling protocol during dynamic service provision in networks
The subject matter described herein includes using a path computation element communication protocol (PCEP) as a signaling protocol during dynamic service provisioning in networks. According to one aspect of the subject matter described herein, a network uses a hard state point-to-point protocol as a signaling protocol during dynamic service provisioning in a control plane of the network. In one implementation, the point-to-point protocol is a path computation element communication protocol (PCEP).
1. A network, comprising:
a network element comprising a control plane;
a management plane;
a path computation client (PCC); and
a remote path computation element (PCE);
wherein a hard state point-to-point protocol is used as a management protocol to communicate management messages in the management plane, wherein the management messages contain service configuration parameters to be dynamically applied to a service interface of the network element for generalized multi-protocol label switching (GMPLS) controlled dynamic service provisioning in said control plane of said network element;
wherein said hard state point-to-point protocol comprises a PCE communication protocol (PCEP) by which the PCC communicates the service configuration parameters to the remote PCE for outsourcing a path selection function to the remote PCE;
wherein said PCEP protocol allows the service configuration parameters to be signaled to the PCE, and paths produced by the PCE to be signaled back to the PCC;
wherein the PCEP protocol is used as a signaling protocol to signal one or more service release requests, service modification requests, or service reroute requests around non-responsive controllers of nodes using the PCEP protocol as a signaling protocol; and
wherein the network is adapted to perform service management of services according to service provisioning signaling patterns comprising:
a one-way end to end pattern starting on a service ingress node via transit nodes to a service egress node;
a two way end to end pattern starting on a service ingress node via transit nodes to a service egress node and then back in reverse direction via the transit nodes to the service ingress node;
a one-way end to end pattern starting from a service egress node via transit nodes to a service ingress node;
a two way pattern starting from a transit node in either or both directions via transit nodes to a service ingress node and/or service egress node;
a pattern wherein signaling is scoped to a path segment;
a pattern wherein signaling is scoped to an arbitrary subset of nodes; and
a star-n-spoke pattern;
wherein a single entity signals service configuration parameters to each node individually and in an arbitrary order.
2. The network according to claim 1 , wherein a plurality of service reconfigurations are performed incrementally in said network, with each incremental service modification signaled in a separate message.
3. The network according to claim 1 , wherein said network is a circuit-switched transport network.
4. A method for dynamic service provisioning in a network, said network comprising a control plane, a management plane, a path computation client (PCC) and a remote path computation element (PCE), the method comprising:
communicating management messages in the management plane using a hard state point-to-point protocol as a management protocol, wherein the management messages contain service configuration parameters to be dynamically applied to a service interface of the network element for generalized multi-protocol label switching (GMPLS) controlled dynamic service provisioning in the control plane of said network, wherein said hard state point-to-point protocol comprises a PCE communication protocol (PCEP);
outsourcing, by said PCC, a path selection function to said remote PCE upon signaling the service configuration parameters to the remote PCE using the PCEP protocol as a signaling protocol;
signaling the service configuration parameters to said PCE;
signaling back paths produced by PCE to said PCC;
signaling one or more service release requests, service modification requests, or service reroute requests around non-responsive controllers of nodes using the PCEP protocol as a signaling protocol; and
managing services according to service provisioning signaling patterns comprising:
a one-way end to end pattern starting on a service ingress node via transit nodes to a service egress node;
a two way end to end pattern starting on a service ingress node via transit nodes to a service egress node and then back in reverse direction via the transit nodes to the service ingress node;
a one-way end to end pattern starting from a service egress node via transit nodes to a service ingress node;
a two way pattern starting from a transit node in either or both directions via transit nodes to a service ingress node and/or service egress node;
a pattern wherein signaling is scoped to a path segment;
a pattern wherein signaling is scoped to an arbitrary subset of nodes; and
a star-n-spoke pattern;
wherein a single entity signals service configuration parameters to each node individually and in an arbitrary order.