Back to results
US 2019/0356559 A1Published application
Multi-Domain Orchestrator Assisted Path Computation Entity (PCE) Endpoint Resolution
AssigneeTelefonaktiebolaget LM Ericsson (publ)
InventorsAndrás Kern, Balázs Peter Gerö
Life of this patent
Estimating the term…
Abstract
A multi-provider network infrastructure is described herein where a Multi-Domain Orchestrator (MDO) is configured to assist a Path Computation Entity (PCE) in resolving a placement and location (identifier) of a tunnel path endpoint for a network service.
Claims15
A Multi-Domain Orchestrator (MDO) comprising:
- a processor;
- and,
- a memory that stores processor-executable instructions, wherein the processor interfaces with the memory to execute the processor-executable instructions, whereby the MDO is operable to:
- transmit, to one or more foreign MDOs, service specifications associated with a network service;
- and;
- transmit, to an associated Path Computation Entity (PCE), a connection request to at least calculate a path for a tunnel associated with the network service, wherein the connection request includes (1) an endpoint object which includes a service related description but not an identifier of a physical endpoint associated with the network service, and (2) an Include Route Object (IRO) field which indicates one or more foreign domains through which the tunnel will traverse to the physical endpoint.
3 more elements
-4. (canceled)
A Path Computation Entity (PCE) comprising:
- a processor;
- and,
- a memory that stores processor-executable instructions, wherein the processor interfaces with the memory to execute the processor-executable instructions, whereby the PCE is operable to:
- receive, from an associated Multi-Domain Orchestrator (MDO), a connection request to at least calculate a path for a tunnel associated with a network service, wherein the connection request includes (1) an endpoint object which includes a service related description but not an identifier of a physical endpoint of the network service, and (2) an Include Route Object (IRO) field which indicates one or more foreign domains through which the tunnel will traverse to the physical endpoint;
- determine a next-hop PCE associated with one of the one or more foreign domains;
- construct a Path Computation Element Protocol (PCEP) request which includes the endpoint object and the IRO field associated with the connection request;
- and,
- transmit, to the next-hop PCE, the PCEP request.
5 more elements
-10. (canceled)
A Path Computation Entity (PCE) comprising:
- a processor;
- and,
- a memory that stores processor-executable instructions, wherein the processor interfaces with the memory to execute the processor-executable instructions, whereby the PCE is operable to:
- receive, from a foreign PCE, a Path Computation Element Protocol (PCEP) request to at least calculate a path for a tunnel associated with a network service, wherein the PCEP request includes (1) an endpoint object which includes a service related description but not an identifier of a physical endpoint of the network service, and (2) an Include Route Object (IRO) field which indicates one or more domains through which the tunnel will traverse to the physical endpoint;
- check the PCEP request to determine whether a destination for the tunnel associated with the network service is encoded in a form of the service related descriptor;
- based on the determination that the destination for the tunnel associated with the network service is encoded in a form of the service related descriptor, read the IRO field and determine whether all of the one or more domains are under control of an associated Multi-Domain Orchestrator (MDO);
- and,
- based on the determination that all of the one or more domains are not under control of the associated MDO, determine a next-hop PCE associated with one of the one or more domains, formulate a subsequent PCEP request to at least calculate the path for the tunnel associated with the network service, wherein the subsequent PCEP request includes (1) the endpoint object which includes the service related description but not the identifier of the physical endpoint of the network service, and (2) the IRO field which has been updated and indicates the one or more domains through which the tunnel will traverse to the physical endpoint, and send the subsequent PCEP request to the next-hop PCE.
5 more elements
-14. (canceled)
A Multi-Domain Orchestrator (MDO) comprising:
- a processor;
- and,
- a memory that stores processor-executable instructions, wherein the processor interfaces with the memory to execute the processor-executable instructions, whereby the MDO is operable to:
- receive, from an associated Path Computation Entity (PCE), an endpoint resolution request, wherein the endpoint resolution request includes (1) an endpoint object which includes a service related description but not an identifier of a physical endpoint of a network service, and (2) an Include Route Object (IRO) field which indicates on one or more domains through which a tunnel will traverse to the physical endpoint;
- read the service related descriptor from the endpoint object of the endpoint resolution request;
- look-up a service instance that contains a service element referred to by the service related descriptor;
- check whether there is a service that contains the service element referred by the service related descriptor;
- based on the determination that there is the service that contains the service element referred by the service related descriptor, determine an physical endpoint identifier or another service related descriptor where the physical endpoint resides, construct an endpoint resolution reply including the determined physical endpoint identifier or the another service related descriptor and transmit the endpoint resolution reply to the PCE, and update a service instance configuration to use the tunnel to the physical endpoint.
5 more elements
-22. (canceled)
Dependencies are inferred from the claim text.