WO2022262964A1

WO2022262964A1 - Escalation and reporting of failures and conflicts in intent-based networking

Info

Publication number: WO2022262964A1
Application number: PCT/EP2021/066182
Authority: WO
Inventors: Gábor HANNÁK; Péter SZILÁGYI; Lajos Bajzik
Original assignee: Nokia Technologies Oy
Priority date: 2021-06-16
Filing date: 2021-06-16
Publication date: 2022-12-22

Abstract

I n an intent-based network having a hierarchical control architecture, intents are processed by control calls by a higher layer control entity to lower layer control entities via a specified interface, based on insight transmitted from the lower layer to the higher layer via the specified interface. For each intent, the control calls are annotated with an identification of the intent, and pieces of the insight determined to be relevant are annotated with the identification. By a lower layer control entity, a report is initialized for a given intent, the report containing pieces of the insight associated with the lower layer control entity and the identification of the given intent. The report is routed to the higher layer control entity which called the lower layer control entity by the control calls annotated with the identification, the report is merged and augmented with pieces of the insight associated with the higher layer control entity and the identification, this is repeated up to and including the top layer, and the report is output from the top layer.

Description

ESCALATI ON AND REPORTI NG OF FAI LURES AND CONFLI CTS I N I NTENT-

BASED NETWORKI NG

TECHNI CAL FI ELD

At least some example embodiments relate to intent-based network management and, in particular, to escalation and reporting of failures and conflicts in intent-based networking.

BACKGROUND

I ntent is a certain type of policy that does not explicitly prescribe control actions for the given network to execute but instead defines the desired state of the network or the mode of network operation. It is inherent to the network to a) translate the intent to a set of actions and rules so as to fulfill/assure the intent policy, e.g. considering both its current state and its environment, b) determine whether the intent has or has not been fulfilled/assured. An intent-based network is a network that is capable of interpreting intents and is equipped with the intelligence to take steps towards fulfilling/assuring them .

LI ST OF ABBREVIATIONS

API Application Programm ing I nterface

E2E End-to-end

I D Identifier

I M I ntent Manager

RAN Radio Access Network

SUMMARY

The network is trusted with fulfilling the intent autonomously and automatically, by deriving control actions and control loops in a context- aware and dynam ic manner. However, intents cannot be always fulfilled/assured, e.g., because two or more intents conflict, or due to lack of sufficient resources in the network. I ntents conflict if, in the given state of the system , the fulfillment/assurance of one intent hinders/negatively affects the fulfillment of one or more other intents. This can happen, e.g. , due to inconsistent parameter adj ustm ents efforts, or the lack of some resource for both intents, but sufficient for either of them . On the other hand, failure of an intent independently of other intents may happen because of, e.g. , insufficient resources, a service or link failure, etc.

It is crucial that such failures, e.g. the inability to fulfill one or m ore intents, are reported to the operator, presented in an understandable way, and are traceable to their root causes, so that the network operator can take necessary m easures, e.g., adapting the active intent(s) , or stocking up on network resources.

At least som e example em bodiments aim at enabling tracing, storing, and/or presenting intent related information, e.g., state, involved entities and services, activated policies, measurements, etc., towards the network operator/engineer.

According to at least some example em bodim ents, this is achieved by a method, system and non-transitory com puter-readable storage m edium as specified by the appended claim s.

At least som e exam ple em bodiments are suitable for escalating and exposing to the operator failures and conflicts from any hierarchy level associated with intent fulfillm ent/assurance.

I n the following exam ple embodiments and example implem entations will be described with reference to the accompanying drawings.

BRI EF DESCRI PTI ON OF THE DRAW I NGS Fig. 1 shows a schematic diagram illustrating an example of a hierarchical architecture of an intent-based network in which at least some example embodiments are implementable.

Fig. 2 shows a schematic diagram illustrating a layer-based working procedure.

Fig. 3 shows a flowchart illustrating a process of escalation and reporting of failures/ conflicts in intent-based networking according to at least some example embodiments.

Fig. 4 shows a flowchart illustrating a first method of escalation and reporting of failures/ conflicts in intent-based networking according to at least some example embodiments.

Fig. 5 shows a flowchart illustrating a first option of a second method of escalation and reporting of failures/ conflicts in intent-based networking according to at least some example embodiments.

Fig. 6 shows a flowchart illustrating a second option of the second method of escalation and reporting of failures/ conflicts in intent-based networking according to at least some example embodiments.

Fig. 7 shows a schematic diagram illustrating stacktrace request down- propagation and stacktrace report generation and up-propagation according to at least some example embodiments.

Fig. 8 shows a schematic diagram illustrating stacktrace report generation at layer n according to at least some example embodiments.

Fig. 9 shows a schematic block diagram illustrating a configuration of a control unit as an example of plural control units in which at least some example embodiments are implementable. DESCRIPTION OF THE EMBODIMENTS

Before describing example embodiments and example implementations, the structure of an intent-based network will be described with reference to Fig.

1 which illustrates an example of a hierarchical architecture of an intent- based network in which at least some example embodiments are implementable. It is to be noted that a hierarchical control architecture to which at least some example embodiments are applicable is not limited to that shown in Fig. 1 .

In general, an intent-based network to which at least some example embodiments are applicable is assumed to have a hierarchical control architecture with control entities which implement network subfunctions. These are controlled, control other entities, and receive the necessary insight for the inner logic over well-defined APIs.

In the example shown in Fig. 1 , a top layer entity called E2E Intent Manager (IM) receives intent(s) from an intent producer (e.g., network operator) and ingests them. Given that the intent passes syntax and validation checks, the Intent Manager translates the intent to a second lower layer API calls to, e.g., sub-intents, domain or subdomain controller configurations, dynamically based on received insight such as network state/ context, and adapts it accordingly. The next lower layer entities (e.g., sub-intent managers, domain controllers; IM (RAN), IM (Trans.), IM (Core) in Fig. 1 ) monitor the next lower layer through insight (measurements, reports, data), and translate the API calls from the upper layer to delegated API calls to the next lower layer (e.g., subdomain controllers, network resources) given the insight from the lower layer. This procedure is propagated down the hierarchy in a recursive manner.

Similarly, necessary insight (e.g., measurements, reports, data) from one layer is being collected, aggregated, and routed towards the next upper layer to feed its decision making, i.e., analytics, control actions, control loops, and policies.

Fig. 2 illustrates the layer-based working procedure is illustrated in Figure 2. Entities of two successive (neighboring upper-lower) layers send/receive control/insight via a well-defined API.

At least some example embodiments propose a method for tracing, storing, and/or presenting intent related information, e.g., state, involved entities and services, activated policies, measurements, etc., towards the network operator/engineer. As a consequence, a special case of the method is suitable for escalating and exposing to the operator failures and conflicts from any hierarchy level associated with intent fulfillment/assurance.

According to at least some example embodiments, (south/downward) control API calls are annotated with the intent or the set of intents that induced it; and (north/upward) transmitted pieces of insight are annotated with the intent or set of intents for whose fulfillment/assurance the piece of insight is relevant.

Without loss of generality, it is assumed that intents received by a top layer entity of the intent-based network are uniquely identified by an intent ID (e.g., an integer). For example, the intent ID is allocated by the top layer entity itself.

The process shown in Fig. 3 is for use in an intent-based network which processes intents and has a hierarchical control architecture comprising a top layer, one or more intermediate layers and a lowest layer. The one or more intermediate layers are layers located between the top layer and the lowest layer.

Each of the top, intermediate and lowest layers comprises one or more control entities which implement functions (e.g., sub-functions) of the intent-based network.

In the example of Fig. 1 , the control entity of the top layer is the E2E IM, the control entities of the intermediate layer are IM (RAN), IM (Trans.) and IM (Core), and the control entities of the lowest layer are (Sub) Domain Controller (RAN), (Sub) Domain Controller (Trans.) and (Sub) Domain Controller (Core).

Further, in the intent-based network to which the process of Fig. 3 is applicable, intents are processed by control calls by a control entity of a higher layer in the hierarchical control architecture to one or more control entities of a lower layer in the hierarchical control architecture, via a specified interface.

In the example of Fig. 1 , higher layer control entity E2E IM translates an intent to control calls to at least one of lower layer control entities IM (RAN), IM (Trans.) and IM (Trans.) via domain intent API layer.

Further, in the example of Fig. 1 , higher layer control entities IM (RAN), IM (Trans.) and IM (Trans.) translate the control calls from the E2E IM to control calls to at least one of lower layer control entities (Sub) Domain Controller (RAN), (Sub) Domain Controller (Trans.) and (Sub) Domain Controller (Core) via (Sub)Domain Controller API layer.

Further, in the intent-based network to which the process of Fig. 3 is applicable, the control calls are based on insight transmitted from one or more control entities of the lower layer to the control entity of the higher layer via the specified interface. In the example of Fig. 1 , lower layer control entities IM (RAN), IM (Trans.) and IM (Trans.) transmit insight via domain intent API layer.

Further, in the example of Fig. 1 , lower layer control entities (Sub) Domain Controller (RAN), (Sub) Domain Controller (Trans.) and (Sub) Domain Controller (Core) transmit insight (e.g., context data) via (Sub)Domain Controller API layer.

Further, in the intent-based network to which the process of Fig. 3 is applicable, the higher layer is the top layer or a layer of the one or more intermediate layers, and the lower layer is a neighboring layer of the higher layer and is a layer of the one or more intermediate layers or the lowest layer.

For example, the process of Fig. 3 starts when an intent or set of intents is input to the intent-based network.

Then, for each intent or set of intents processed by the intent-based network, the control calls are annotated (S301 ) with an identification of the intent or set of intents. As described above, it is assumed that intents received by the top layer entity of the intent-based network are uniquely identified by an intent ID (e.g., an integer). For example, the intent ID is allocated by the top layer entity itself. According to at least some example embodiments, step S301 is performed by the control entity of the higher layer doing the control calls.

Further, it is determined whether pieces of the insight is relevant for the intent or set of intents and the pieces of the insight which have been determined to be relevant are annotated with the identification of the intent or set of intents (S303). According to at least some example embodiments, step S303 is performed by a control entity of the lower layer transmitting the insight to the control entity of the higher layer which called the control entity of the lower layer.

In step S305, for a given intent or set of intents processed by the intent- based network, e.g. upon a request received from the control entity of the higher layer or in case the given intent is associated with a failure, conflict or inconsistency occurring in the intent-based network, a control entity of the lower layer initializes a report for the given intent or set of intents, the report containing pieces of the insight associated with the status or context of the control entity of the lower layer and with the identification of the given intent or set of intents.

In step S307, the report is routed to the control entity of the higher layer which called the control entity of the lower layer by the control calls annotated with the identification of the given intent or set of intents.

In step S309, the report is merged and augmented with pieces of the insight associated with the status or context of the control entity of the higher layer and with the identification of the given intent or set of intents.

In step S311 it is checked whether or not the current higher layer is the top layer. In case the current higher layer is not the top layer, the process returns to step S307. Otherwise, the process advances to step S313 in which the report is output from the top layer. Then, the process ends.

As illustrated in Fig. 3, the routing in step S307 to the next upper layer and the merging and augmenting at this next upper layer in step S309 are repeated up to and including the top layer.

According to a second option of a second method which will be described in more detail below, in step S305, the report is initialized by the control entity of the lower layer in case it detects a failure, conflict, or inconsistency that occurs with respect to the given intent or set of intents. According to a first method and a first option of the second method, which will be described in more detail below, in step S305, the report is initialized by the control entity of the lower layer upon receiving a request for the report from the control entity of the higher layer.

According to the first method and the first option of the second method, which will be described in more detail below, the request for the report is generated by the control entity of the higher layer and is routed to the control entity of the lower layer based on the control calls annotated with the identification of the given intent or set of intents, wherein the routing is repeated until the lower layer becomes the lowest layer.

According to the second method which will be described in more detail below, the request is generated by the control entity of the higher layer in case it detects a failure, conflict, or inconsistency that occurs with respect to the given intent or set of intents.

According to the first method which will be described in more detail below, the request is generated by the control entity of the higher layer upon receiving a trigger associated with the identification of the given intent or set of intents, to collect data regarding the given intent or set of intents.

Further, in the first method and the first option of the second method, the merging and augmenting in step S309 comprises merging the report with one or more reports received from others of the one or more control entities of the lower layer.

In the following, overviews of example embodiments of the first and second methods will be described by referring to Figs. 4 to 6. Fig. 4 shows a flowchart illustrating the first method of escalation and reporting of failures/ conflicts in intent-based networking according to at least some example embodiments.

The first method comprises (i) dissemination (S403, S405) of a Stacktrace Request 401 associated with one or more active (given) intents (I ntent_l D(s)) from a top layer entity 40 (e.g. E2E IM of Fig. 1 ) recursively towards lower layers 41 in the control hierarchy of the intent-based network, (ii) initialization (S407) of a Stacktrace Report at lowest layers 42 of the hierarchy with contextual information (e.g. pieces of the insight associated with the status or context of the control entity of the lower layer) on the given intent(s), and (iii) routing (S407) the Stacktrace Reports to the next higher layer 43, where they are merged and augmented (S409) with contextual information of that layer (e.g. pieces of the insight associated with the status or context of the control entity of the higher layer), and again routed (S409) towards the higher layers 43 of the control hierarchy of the intent-based network. This upward merge-augment-route mechanism results in a Stacktrace Report 411 at the top layer of Intent Manager 40, which includes all necessary information related to the given intent(s) in an ordered manner, and can easily be interpreted by the human expert, or delegated for further (automatic) processing.

Fig. 5 shows a flowchart illustrating the first option of the second method of escalation and reporting of failures/ conflicts in intent-based networking according to at least some example embodiments.

In case of failures, conflicts, or inconsistencies that occur during the automated fulfilment/assurance of an intent (S501 ), a slightly modified method, the second method, is proposed.

According to the first option of the second method, a Stacktrace Request is generated (S503) within one of the lower layer control entities referred to as layer n entity 50 in Fig. 5. The layer n is a layer below the top layer on which intent manager 40 resides.

Similar to the first method, the first option of the second method comprises (i) dissemination (S503, S505) of the Stacktrace Request associated with the intent recursively towards lower layers 51 in the control hierarchy of the intent-based network, (ii) initialization (S507) of a Stacktrace Report at lowest layers 52 of the hierarchy with contextual information (e.g. pieces of the insight associated with the status or context of the control entity of the lower layer) on the given intent(s), and (iii) routing (S507) the Stacktrace Reports to the next higher layer 53, where they are merged and augmented (S509) with contextual information of that layer (e.g. pieces of the insight associated with the status or context of the control entity of the higher layer), and again routed (S509) towards the higher layers 53 of the control hierarchy of the intent-based network. This upward merge-augment-route mechanism results in a Stacktrace Report 511 at the top layer of Intent Manager 40, which includes all necessary information related to the intent.

Fig. 6 shows a flowchart illustrating the second option of the second method of escalation and reporting of failures/ conflicts in intent-based networking according to at least some example embodiments.

According to the second option of the second method, the Stacktrace Request phase is skipped and a Stacktrace Report is initialized (S603) within that very control entity (layer n entity 60), with contextual information (e.g. pieces of the insight associated with the status or context of the control entity of the lower layer) related to the intent(s) whose fulfillment/assurance encountered the failure. Then, the Stacktrace Report is being propagated (S605) to higher layers 61 of the hierarchy, and at every layer the Stacktrace Report is augmented (S605) with contextual information (e.g. pieces of the insight associated with the status or context of the control entity of the higher layer) available to that layer's entity. This upward merge-augment-route mechanism results in a Stacktrace Report 607 at the top layer of Intent Manager 40, which includes all necessary information related to the intent.

According to at least some example embodiments, the top layer entity 40 (e.g. the Intent Manager) will acquire insight down to the full or necessary technical depth regarding the fulfillment/assurance of one or more intents, and in case of failures/ conflicts/inconsistencies, using the Stacktrace Report the human expert (operator, engineer) is able to trace back the problem to the root cause.

In the following, example embodiments of the first and second methods will be described in more detail by referring to Figs. 4 to 8.

According to at least some example embodiments, steps of the first method are:

1 . Stacktrace Request Trigger: A Stacktrace Request Trigger is received by the top layer Intent Manager 40 and is, e.g., a manual request by the operator/engineer, a periodic request, an event-based trigger, a request by a network or analytics function, etc. The Stacktrace Request Trigger is associated with a specific intent or set of intents and embodies a request to the Intent Manager 40 to collect data/insight regarding that very intent. The intent is identified by the IntenMD.

2. Stacktrace Request Diffusion: The top layer Intent Manager 40 (Layer 0) sends a Stacktrace Request (S403 in Fig. 4) to those lower layer entities 41 (one layer below, Layer 1 ) which are associated with the fulfillment/assurance of IntenMD, i.e., to those entities to which it has issued API calls annotated with the given IntenMD.

This downward diffusion is propagated (S405, S701 , S703, S705) recursively down the hierarchy up to all layers (Layers 2, 3, ...), where API calls are annotated with the given IntenMD. 3. Stacktrace Report Initialization: For each intent there is a set of lowest layer entities 42 which do not issue API calls annotated with the IntenM D further down. For example, the lowest layer entities 42 are entities of layer N1 , N2,...

It is noted that layers N1 , N2,... can be different for different branches in the hierarchy. It is further noted that it is possible that there are even lower layer entities that issue API calls related to the given intent, but these API calls are not annotated by IntenMD, as illustrated in Fig. 7.

The lowest layer entities of the intent (in Fig. 7, layer N1 entity) do not propagate the Stacktrace Request further down to lower layers, but initialize (S407, S711 ) a data structure called Stacktrace Report (of Layer N1 , N2,

...) for IntenMD. The Stacktrace Report(s) contains insight (measurements, data, reports) associated with the status/ context of the specific entity (of Layer N1 , N2, ...) and with the IntenMD.

Optionally, according to at least some example embodiments, if an entity serves multiple intents in an interdependent way, e.g., if at least one API call it issues downward plays a role in the fulfillment/assurance of a combination of multiple intents, it extends the Stacktrace Report with insight (measurements, data, reports) associated with those interdependent intents too.

4. Stacktrace Report Escalation: After the Stacktrace Report(s) has/have been initialized, they are transmitted (S407, S711 ) to the next higher layer entity 43 (Layer N 1 - 1 , N2-1 , ...) from which the Stacktrace Request was received.

According to at least some example embodiments, this (next higher layer) entity 43 (e.g. layer n entity) receives multiple Stacktrace Reports from layer n+ 1 entities, depending on to which entities it has issued API calls associated with the Intent D.

Fig. 8 illustrates Stacktrace Report generation at layer n entity 81 using Stacktrace Report(s) 801 from layer n+ 1 entities 80 and insigth(s) 805 received from layer n+ 1 entities 80.

In particular, according to at least some example embodiments, the layer n entity 81 merges (S803) the received Stacktrace Reports 801 , while also collecting insight (measurements, data, reports) 805 associated with its own status/ context and with the IntentJ D (S807), and appends (S809) this to a layer n Stacktrace Report 811 , propagated to layer n-1 entity 82.

The Stacktrace Report(s) are recursively merged, augmented, and propagated (S713, S715) up the hierarchy towards the top layer (Layer 0)

I ntent Manager 40.

Due to communication failures (e.g., broken/irresponsive network components, timeouts, link failures, delayed communication), it is possible that Stacktrace Reports from some lower-layer entities are not received (or Stacktrace Requests have not been transmitted successfully beforehand). According to at least some example embodiments, this is handled by standard techniques. For example, during the Stacktrace Report merge phase the higher-layer entity inserts a report about the fact that the Stacktrace Report has not been received (or that the Stacktrace Request has not been transmitted successfully beforehand), including timestamps, entity identifiers, etc. According to at least some example embodiments, retransmission of the Stacktrace Request is also attempted in an effort to improve response rates.

5. Stacktrace Report Completion: When the top layer (Layer 0) Intent Manager 40 has received all Stacktrace Reports, has merged and augmented them with its own contextual insight into a layer 0 Stacktrace Report 411 , the Stacktrace Report 411 is ready to be saved, presented, or processed otherwise.

Optionally, according to at least some example embodiments, in steps 3 and 4 of the first method, if an entity serves multiple intents in an interdependent way (e.g., an API call it issues towards a next lower layer entity plays a role in the fulfillment/assurance of a combination of multiple intents), it extends the Stacktrace Report with insight (measurements, data, reports) associated with those interdependent intents.

At least some example embodiments of the second method are adopted in case a failure or conflict or similar inconsistency event in the intent-based network occurs in one of the control entities, e.g., a layer n entity, in form of an error or warning which cannot be handled by that very control entity.

According to the first option of the second method, the entity at which the warning or failure occurred sends Stacktrace Request(s) to those next lower layer entities which are associated with the lntent_ID(s) that caused warning/failure/inconsistency. Then, steps 3 to 5 of the first method follow.

According to the second option of the second method, the entity at which the warning/failure/inconsistency occurred initializes the Stacktrace Report with (i) the lntent_I D(s) associated with those API calls which resulted in the warning or failure, (ii) insight (measurements, data, reports) associated with its own status/ context. Then, the Stacktrace Report is propagated upward similar to above-described step 4 of the first method, and completed similar to above-described step 5 of the first method.

Now reference is made to Fig. 9 illustrating a simplified block diagram of a control unit 90 as an example of plural control units 90 that are suitable for use in practicing at least some example embodiments. According to an implementation example, the method of Fig. 3 is implemented by the control units 90. The control unit 90 comprises processing resources (e.g. processing circuitry) 91 , memory resources (e.g. memory circuitry) 92 and interfaces (e.g. interface circuitry) 93, which are coupled via a wired or wireless connection 14.

According to an example implementation, the memory resources 92 are of any type suitable to the local technical environment and are implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The processing resources 91 are of any type suitable to the local technical environment, and include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi core processor architecture, as non-limiting examples.

According to an example implementation, the memory resources 92 comprise one or more non-transitory computer-readable storage media which store one or more programs that when executed by the processing resources 91 cause the control unit 90 to function as control entity of the higher or lower layer in the intent-based network.

Further, as used in this application, the term "circuitry" refers to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)) , software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.

This definition of "circuitry" applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware. The term "circuitry" would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in server, a cellular network device, or other network device.

According to at least some example embodiments, a system for use in an intent-based network is provided, wherein the intent-based network processes intents and has a hierarchical control architecture which comprises a top layer, one or more intermediate layers and a lowest layer, wherein the one or more intermediate layers are layers located between the top layer and the lowest layer, wherein each of the top, intermediate and lowest layers comprises one or more control entities which implement functions of the intent-based network, wherein intents are processed by control calls by a control entity of a higher layer in the hierarchical control architecture to one or more control entities of a lower layer in the hierarchical control architecture, via a specified interface, wherein the control calls are based on insight transmitted from one or more control entities of the lower layer to the control entity of the higher layer via the specified interface, wherein the higher layer is the top layer or a layer of the one or more intermediate layers, wherein the lower layer is a neighboring layer of the higher layer and is a layer of the one or more intermediate layers or the lowest layer, the system comprising: for each intent or set of intents processed by the intent-based network: means for annotating the control calls with an identification of the intent or set of intents; and means for determining whether pieces of the insight is relevant for the intent or set of intents and annotating the pieces of the insight which have been determined to be relevant with the identification of the intent or set of intents; means for initializing, by a control entity of the lower layer, a report for a given intent or set of intents processed by the intent-based network, the report containing pieces of the insight associated with the status or context of the control entity of the lower layer and with the identification of the given intent or set of intents; means for routing the report to the control entity of the higher layer which called the control entity of the lower layer by the control calls annotated with the identification of the given intent or set of intents; means for merging and augmenting the report with pieces of the insight associated with the status or context of the control entity of the higher layer and with the identification of the given intent or set of intents, wherein the routing to the next upper layer and merging and augmenting at this next upper layer are repeated up to and including the top layer; and means for outputting the report from the top layer.

According to at least some example embodiments, the pieces of the insight associated with the status or context of the control entity contain pieces of insight associated with an identification of at least one other intent served by the control entity in an interdependent way. According to at least some example embodiments, when the report has been merged and augmented by the control entity of the top layer, the report is saved, presented, or processed otherwise.

According to at least some example embodiments, the report is initialized by the control entity of the lower layer in case it detects a failure, conflict, or inconsistency that occurs with respect to the given intent or set of intents.

According to at least some example embodiments, the report is initialized by the control entity of the lower layer upon receiving a request for the report from the control entity of the higher layer.

According to at least some example embodiments, the lower layer is the lowest layer.

According to at least some example embodiments, the system further comprises: means for generating a request for the report by the control entity of the higher layer; and means for routing the request to the control entity of the lower layer based on the control calls annotated with the identification of the given intent or set of intents, wherein the routing is repeated until the lower layer becomes the lowest layer.

According to at least some example embodiments, the request is generated by the control entity of the higher layer in case it detects a failure, conflict, or inconsistency that occurs with respect to the given intent or set of intents.

According to at least some example embodiments, the request is generated by the control entity of the higher layer upon receiving a trigger associated with the identification of the given intent or set of intents, to collect data regarding the given intent or set of intents.

According to at least some example embodiments, the higher layer is the top layer.

According to at least some example embodiments, the means for merging and augmenting comprises means for merging the report with one or more reports received from others of the one or more control entities of the lower layer.

According to at least some example embodiments, the lowest layer is a layer whose one or more control entities issue control calls related to the given intent or set of intents that are not annotated with the identification of the given intent or set of intents.

It is to be understood that the above description is illustrative and is not to be construed as limiting. Various modifications and applications may occur to those skilled in the art without departing from the true spirit and scope as defined by the appended claims.

Claims

1. A method for use in an intent-based network, wherein the intent-based network processes intents and has a hierarchical control architecture which comprises a top layer, one or more intermediate layers and a lowest layer, wherein the one or more intermediate layers are layers located between the top layer and the lowest layer, wherein each of the top, intermediate and lowest layers comprises one or more control entities which implement functions of the intent-based network, wherein intents are processed by control calls by a control entity of a higher layer in the hierarchical control architecture to one or more control entities of a lower layer in the hierarchical control architecture, via a specified interface, wherein the control calls are based on insight transmitted from one or more control entities of the lower layer to the control entity of the higher layer via the specified interface, wherein the higher layer is the top layer or a layer of the one or more intermediate layers, wherein the lower layer is a neighboring layer of the higher layer and is a layer of the one or more intermediate layers or the lowest layer, the method comprising: for each intent or set of intents processed by the intent-based network: annotating the control calls with an identification of the intent or set of intents; and determining whether pieces of the insight is relevant for the intent or set of intents and annotating the pieces of the insight which have been determined to be relevant with the identification of the intent or set of intents; initializing, by a control entity of the lower layer, a report for a given intent or set of intents processed by the intent-based network, the report containing pieces of the insight associated with the status or context of the control entity of the lower layer and with the identification of the given intent or set of intents; routing the report to the control entity of the higher layer which called the control entity of the lower layer by the control calls annotated with the identification of the given intent or set of intents; merging and augmenting the report with pieces of the insight associated with the status or context of the control entity of the higher layer and with the identification of the given intent or set of intents, wherein the routing to the next upper layer and merging and augmenting at this next upper layer are repeated up to and including the top layer; and outputting the report from the top layer.

2. The method of claim 1 , wherein the pieces of the insight associated with the status or context of the control entity contain pieces of insight associated with an identification of at least one other intent served by the control entity in an interdependent way.

3. The method of claim 1 or 2, wherein when the report has been merged and augmented by the control entity of the top layer, the report is saved, presented, or processed otherwise.

4. The method of any one of claims 1 to 3, wherein the report is initialized by the control entity of the lower layer in case it detects a failure, conflict, or inconsistency that occurs with respect to the given intent or set of intents.

5. The method of any one of claims 1 to 3, wherein the report is initialized by the control entity of the lower layer upon receiving a request for the report from the control entity of the higher layer.

6. The method of claim 5, wherein the lower layer is the lowest layer.

7. The method of any one of claims 1 to 3, further comprising: generating a request for the report by the control entity of the higher layer; and routing the request to the control entity of the lower layer based on the control calls annotated with the identification of the given intent or set of intents, wherein the routing is repeated until the lower layer becomes the lowest layer.

8. The method of claim 7, wherein the request is generated by the control entity of the higher layer in case it detects a failure, conflict, or inconsistency that occurs with respect to the given intent or set of intents.

9. The method of claim 7, wherein the request is generated by the control entity of the higher layer upon receiving a trigger associated with the identification of the given intent or set of intents, to collect data regarding the given intent or set of intents.

10. The method of claim 9, wherein the higher layer is the top layer.

11 . The method of any one of claims 7 to 10, wherein the merging and augmenting comprises merging the report with one or more reports received from others of the one or more control entities of the lower layer.

12. The method of any one of claims 1 to 11 , wherein the lowest layer is a layer whose one or more control entities issue control calls related to the given intent or set of intents that are not annotated with the identification of the given intent or set of intents.

13. A non-transitory computer-readable storage medium storing a program for an intent-based network, wherein the intent-based network processes intents and has a hierarchical control architecture which comprises a top layer, one or more intermediate layers and a lowest layer, wherein the one or more intermediate layers are layers located between the top layer and the lowest layer, wherein each of the top, intermediate and lowest layers comprises one or more control entities which implement functions of the intent-based network, wherein intents are processed by control calls by a control entity of a higher layer in the hierarchical control architecture to one or more control entities of a lower layer in the hierarchical control architecture, via a specified interface, wherein the control calls are based on insight transmitted from one or more control entities of the lower layer to the control entity of the higher layer via the specified interface, wherein the higher layer is the top layer or a layer of the one or more intermediate layers, wherein the lower layer is a neighboring layer of the higher layer and is a layer of the one or more intermediate layers or the lowest layer, wherein the program, when executed by a computer, causes the computer to perform : for each intent or set of intents processed by the intent-based network: annotating the control calls with an identification of the intent or set of intents; and determining whether pieces of the insight is relevant for the intent or set of intents and annotating the pieces of the insight which have been determined to be relevant with the identification of the intent or set of intents; initializing, by a control entity of the lower layer, a report for a given intent or set of intents processed by the intent-based network, the report containing pieces of the insight associated with the status or context of the control entity of the lower layer and with the identification of the given intent or set of intents; routing the report to the control entity of the higher layer which called the control entity of the lower layer by the control calls annotated with the identification of the given intent or set of intents; merging and augmenting the report with pieces of the insight associated with the status or context of the control entity of the higher layer and with the identification of the given intent or set of intents, wherein the routing to the next upper layer and merging and augmenting at this next upper layer are repeated up to and including the top layer; and outputting the report from the top layer.

14. A system for use in an intent-based network, wherein the intent-based network processes intents and has a hierarchical control architecture which comprises a top layer, one or more intermediate layers and a lowest layer, wherein the one or more intermediate layers are layers located between the top layer and the lowest layer, wherein each of the top, intermediate and lowest layers comprises one or more control entities which implement functions of the intent-based network, wherein intents are processed by control calls by a control entity of a higher layer in the hierarchical control architecture to one or more control entities of a lower layer in the hierarchical control architecture, via a specified interface, wherein the control calls are based on insight transmitted from one or more control entities of the lower layer to the control entity of the higher layer via the specified interface, wherein the higher layer is the top layer or a layer of the one or more intermediate layers, wherein the lower layer is a neighboring layer of the higher layer and is a layer of the one or more intermediate layers or the lowest layer, the system comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the system at least to: for each intent or set of intents processed by the intent-based network: annotate the control calls with an identification of the intent or set of intents; and determine whether pieces of the insight is relevant for the intent or set of intents and annotate the pieces of the insight which have been determined to be relevant with the identification of the intent or set of intents; initialize, by a control entity of the lower layer, a report for a given intent or set of intents processed by the intent-based network, the report containing pieces of the insight associated with the status or context of the control entity of the lower layer and with the identification of the given intent or set of intents; route the report to the control entity of the higher layer which called the control entity of the lower layer by the control calls annotated with the identification of the given intent or set of intents; merge and augment the report with pieces of the insight associated with the status or context of the control entity of the higher layer and with the identification of the given intent or set of intents, wherein the routing to the next upper layer and merging and augmenting at this next upper layer are repeated up to and including the top layer; and output the report from the top layer.

15. The system of claim 14, wherein the pieces of the insight associated with the status or context of the control entity contain pieces of insight associated with an identification of at least one other intent served by the control entity in an interdependent way.

16. The system of claim 14 or 15, wherein when the report has been merged and augmented by the control entity of the top layer, the report is saved, presented, or processed otherwise.

17. The system of any one of claims 14 to 16, wherein the report is initialized by the control entity of the lower layer in case it detects a failure, conflict, or inconsistency that occurs with respect to the given intent or set of intents.

18. The system of any one of claims 14 to 16, wherein the report is initialized by the control entity of the lower layer upon receiving a request for the report from the control entity of the higher layer.

19. The system of claim 18, wherein the lower layer is the lowest layer.

20. The system of any one of claims 14 to 16, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the system further to: generate a request for the report by the control entity of the higher layer; and route the request to the control entity of the lower layer based on the control calls annotated with the identification of the given intent or set of intents, wherein the routing is repeated until the lower layer becomes the lowest layer.

21 . The system of claim 20, wherein the request is generated by the control entity of the higher layer in case it detects a failure, conflict, or inconsistency that occurs with respect to the given intent or set of intents.

22. The system of claim 20, wherein the request is generated by the control entity of the higher layer upon receiving a trigger associated with the identification of the given intent or set of intents, to collect data regarding the given intent or set of intents.

23. The system of claim 22, wherein the higher layer is the top layer.

24. The system of any one of claims 20 to 23, wherein to merge and augment the at least one memory and the computer program code are configured to, with the at least one processor, cause the system to merge the report with one or more reports received from others of the one or more control entities of the lower layer.

25. The system of any one of claims 14 to 24, wherein the lowest layer is a layer whose one or more control entities issue control calls related to the given intent or set of intents that are not annotated with the identification of the given intent or set of intents.