US 12,009,964 B2
Multi-domain orchestration
Balázs Peter Gerö, Budapest (HU); János Harmatos, Budapest (HU); Dávid Jocha, Budapest (HU); Balázs Sonkoly, Budapest (HU); and Róbert Szabó, Budapest (HU)
Assigned to Telefonaktiebolaget LM Ericsson (publ), Stockholm (SE)
Appl. No. 17/436,779
Filed by Telefonaktiebolaget LM Ericsson (publ), Stockholm (SE)
PCT Filed Mar. 29, 2019, PCT No. PCT/IB2019/052618
§ 371(c)(1), (2) Date Sep. 7, 2021,
PCT Pub. No. WO2020/201808, PCT Pub. Date Oct. 8, 2020.
Prior Publication US 2022/0014418 A1, Jan. 13, 2022
Int. Cl. G06F 15/173 (2006.01); G06F 16/22 (2019.01); H04L 41/042 (2022.01); H04L 41/0803 (2022.01)
CPC H04L 41/042 (2013.01) [G06F 16/2255 (2019.01); H04L 41/0803 (2013.01)] 15 Claims
OG exemplary drawing
 
1. A method for multi-domain orchestration, the method performed by a first orchestrator for a first domain, the method comprising:
receiving an inbound orchestration request that requests orchestration of one or more inbound targets and that includes one or more records that either indicate an ancestry of each of the one or more inbound targets or indicate an ancestry of the inbound orchestration request;
based on the ancestry of each of the one or more inbound targets or the ancestry of the inbound orchestration request as indicated by the one or more records included in the inbound orchestration request, evaluating whether or not to send from the first domain to a second domain an outbound orchestration request that requests orchestration of an outbound target, wherein the outbound target is one of, or is a descendant of at least one of, the one or more inbound targets;
sending or not sending the outbound orchestration request from the first domain to the second domain depending on the evaluating;
maintaining a stored record at the first orchestrator for each pending outbound target that is pending with respect to the second domain, wherein the stored record for a pending outbound target indicates an ancestry of the pending outbound target as of when the first orchestrator requested the second domain to orchestrate the pending outbound target; and
deciding to not send the outbound orchestration request to the second domain responsive to determining that each of multiple blocking conditions is met, wherein the blocking conditions include:
a stored record is maintained at the first orchestrator for a pending outbound target that is pending with respect to the second domain and that is of the same type as the outbound target; and
the ancestry of the pending outbound target that is of the same type as the outbound target at least partially overlaps with the ancestry of at least one of the one or more inbound targets.