METHODS AND APPARATUS FOR MULTI-PROVIDER VIRTUAL NETWORK

SERVICES

Technical Field

Embodiments disclosed herein relate to the provision of services by multiple providers in a virtual network. In particular methods and embodiments described herein allow for the collaboration between a plurality of service providers to provide multi-provider services.

Background

While virtualization and digitalization has moved in industry beyond the initial hype phase, the transformation into the telecommunications industry is still full of challenges. Orchestration and automation tool-chains, as a major enablers of such transformation, are often defined, deployed and specialized for a specific technology and/or service.

With a growing number of virtualized functions there is also growing number of function/service providers. The increasing number of service providers and individual services increases complexity of the industry and the heterogeneity required for different services and offered functionalities.

Benefits of such development comprise easy sharing of interoperable functions as well as having multiple choices to fulfil targeted services. In this respect, the industry is moving towards common eco-systems where a service provider can offer service in its own expertise zone filling the gaps with external eco-system functions. There are related expanding business models also called X as a service (XaaS) where X can stand for one to many functions fulfilling service in one or more segments in a cloud stack.

To enable this multi-provider playground and boost automation benefits, service providers may be able to handle not only the responsibility of their own domain of resources but at a same time may be able to share some dependent resources to fulfill end-2-end service requirements. There are multiple standardization bodies (ETSI, ONAP, NGMN, MEF, IETF, etc.) working on common architecture and concepts (NFV, SDN, 5G) to support such new business models and related growing services.

In order to allow such multi-provider services, automated orchestration between the service providers which can cope with such a large matrix of heterogeneity may be required. The main target here is to define more generic orchestration mechanisms with a focus on agility and flexibility.

Although some service providers do try to follow the recommendations of standardization bodies, they may still have different implementations of orchestration mechanisms which may be optimized for the proprietary functionality of that service provider. In particular, some service providers prefer to manage life-cycles with a local lifecycle management component, which may be optimized for dedicated functions.

New business models have also been introduced where, for instance, a single virtual network function (VNF) can also be offered as a service (VNFaaS). Such a trend further increases granularity and heterogeneity of multi-provider domains.

For multi-provider services therefore, traditionally agreements between the different service providers have been handled on the higher BSS/OSS levels. With a new multi- provider playground complexity such channels become orchestration bottlenecks where loops crossing multiple vertical management layers slow down the orchestration routines.

Current service models therefore do not provide any direct interaction between lifecycle subdomains if they are controlled by different service providers. The only available way is to port functions from one domain into the other domain and provide the orchestration using a single Lifecycle Management (LCM) component controlled by a single service provider. Unfortunately, this can be too slow, too expensive and an inflexible solution. Current industry trends requires more agile and flexible solutions where integration and allocation of resources happens in a few seconds rather than in months. Summary

According to the some embodiments there is provided a method in a first lifecycle management, LCM component, in a virtual network; wherein the virtual network comprises trusted provider configured to provide a decentralised trust system between a plurality of LCM components controlled by different service providers in the virtual network. The method comprises storing a detailed description of one or more local services that the first service provider is capable of providing; generating a local tag representative of the one or more local services, wherein the local tag comprises less detail about the one or more local services than the detailed description; and enrolling with the decentralised trust system using the local tag.

According to some embodiments there is provided a method, in a trusted Lifecycle Management, LCM, component controlled by a trusted provider in a virtual network, wherein the trusted provider is configured to provide a decentralised trust system between a plurality of LCM components controlled by different service providers in the virtual network. The method comprises receiving an enrolment request from a first lifecycle management, LCM, component controlled by a first service provider to enrol the first LCM component with the decentralised trust system; wherein the enrolment request comprises a local tag representative of one or more local services the first service provider is capable of providing; and storing the first LCM component alongside the local tag in a membership record, wherein the membership record comprises entries for each of a plurality of LCM components enrolled on the decentralised trust system.

According to some embodiments there is provided a first lifecycle management, LCM component, in a virtual network; wherein the virtual network comprises trusted provider configured to provide a decentralised trust system between a plurality of LCM components controlled by different service providers in the virtual network. The first LCM component comprises memory configured to store a detailed description of one or more local services that the first service provider is capable of providing. The first LCM component further comprises processing circuitry configured to generate a local tag representative of the one or more local services, wherein the local tag comprises less detail about the one or more local services than the detailed description; and enrol with the decentralised trust system using the local tag. According to some embodiments there is provided a trusted Lifecycle Management, LCM, component controlled by a trusted provider in a virtual network, wherein the trusted provider is configured to provide a decentralised trust system between a plurality of LCM components controlled by different service providers in the virtual network. The trusted LCM component comprises processing circuitry configured to: receive an enrolment request from a first lifecycle management, LCM, component controlled by a first service provider to enrol the first LCM component with the decentralised trust system; wherein the enrolment request comprises a local tag representative of one or more local services the first service provider is capable of providing. The trusted LCM component further comprises a memory configured to store the first LCM component alongside the local tag in a membership record, wherein the membership record comprises entries for each of a plurality of LCM components enrolled on the decentralised trust system.

According to some embodiments there is provided a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method as described above.

According to some embodiments there is provided a computer program product comprising a computer-readable medium with the computer program as described above.

Brief Description of the Drawings

For a better understanding of the present invention, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:-

Figure 1 illustrates a multi-provider ecosystem;

Figure 2 illustrates an example of LCM components as Blockchain peers;

Figure 3 illustrates an example of an LCM component according to some embodiments; Figure 4 illustrates the four main steps of a procedure to establish direct LCM component interactions according to some embodiments;

Figure 5 illustrates an enrolment process according to some embodiments;

Figure 6 illustrates an enrolment process according to some embodiments;

Figure 7 illustrates onboarding of service offerings according to some embodiments;

Figure 8 illustrates smart contract establishment according to some embodiments;

Figure 9 illustrates smart contract establishment according to some embodiments;

Figure 10 illustrates detailed LCM transactions according to some embodiments;

Figure 11 illustrates detailed LCM transactions according to some embodiments;

Figure 12 illustrates an example of direct LCM orchestration;

Figure 13 illustrates an example of direct LCM orchestration;

Figure 14 illustrates a method performed by a first LCM component according to some embodiments;

Figure 15 illustrates a method performed by a trusted LCM component according to some embodiments;

Figure 16 illustrates a method performed by a second LCM component according to some embodiments;

Figure 17 illustrates a first LCM component according to some embodiments;

Figure 18 illustrates an example of the signalling required for an enrolment process according to some embodiments;

Figure 19 illustrates an enrolment process according to some embodiments; Figure 20 illustrates an enrolment process according to some embodiments;

Figure 21 illustrates an example of the signalling required for smart contract establishment according to some embodiments;

Figure 22 illustrates smart contract establishment according to some embodiments;

Figure 23 illustrates smart contract establishment according to some embodiments;

Figure 24 illustrates an example of the signalling performed for providing detailed transactions between LCM components;

Figure 25 illustrates an example of detailed transactions according to some embodiments;

Figure 26 illustrates a first LCM component according to some embodiments;

Figure 27 illustrates a trusted LCM component according to some embodiments;

Figure 28 illustrates a second LCM component according to some embodiments;

Figure 29 illustrates a first LCM component according to some embodiments; Figure 30 illustrates a trusted LCM component according to some embodiments.

Description

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Direct interaction between life-cycle domains may be an important enabler of a multi- provider eco-system. To make such interaction possible, there are many aspects that have to be standardized and unified. One of the major open concerns is still security and lack of trustiness between the service providers on the orchestration levels below BSS/OSS levels. Thus, in current solutions, complex multilayered orchestration interactions may be required even for simple services. There is, as of yet, no existing industry solution for how to directly communicate between life-cycle management domains using agile, simple and flexible orchestration mechanisms.

Figure 1 illustrates a multi-provider ecosystem. In such an ecosystem a single service provider may offer a service which spans different levels of the architecture stack consuming different types of resources. Those resources are Lifecycle Management (LCM) assets which may be used for targeted service fulfilment. Resources can be owned by the different service providers. Infrastructure can also be mashed up and provided by the multiple service providers. Different services and functions can be offered on the top of the infrastructure, and applications built on the top can utilize different services and functions to fulfill required services.

In such a multi-provider ecosystem, each service provider can offer any service, X as a service (XaaS). The service X may then be provided fully by the particular service provider or mashed up with the other service provider(s). For instance service provider A may offer mashup application (AaaS ^A ) that uses infrastructure resources provided by service provider B (laaS ^B ) and network function virtualisation (NFV) eco-system on the top provided by servce provider C (NFVIaaS ^c ). It can also use additional services on the top of the infrastructure provided by service provider D (SaaS ^D ), and additional virtual network functions (VNFs) provided by service provider E as“VNF as a service” (VNFaaS ^E ).

In some embodiments disclosed herein a service provider, in this example service provider C, can be added and deployed on the top of multi-provider NFV eco-system (NFVI) to enable a decentralized trust system between the different service providers, for example a Blockchain system. Every service provider may then directly negotiate shared and dependent resources with other LCM components using smart business contracts. In some embodiments therefore, each Blockchain peer here comprises an LCM component, where each LCM component may be controlled by a different service provider. Blockchain mechanisms may be supported by each LCM node through Blockchain adapter layer components containing toolsets and Blockchain enablers. The Blockchain adapter layer may also interconnect with each LCM component and LCM specific Blockchain interaction functionality. The skilled person will appreciate how such a Blockchain, or other decentralized trust system may be established.

In the example of Figure 1 , the Blockchain network is established by the NFV eco- system provider C (NFVIaaS ^c ) as an additional service, Smart Contract Blockchain as a Service (SCBaaS ^c ). Part of this service may be related toolsets including a software development kit and access applications for a Blockchain network that can be part of each LCM node. LCM Blockchain peers may have committers or/and endorsing capabilities. Figure 2 illustrates the LCM Blockchain peers 200. A committer peer may commit transactions and maintain the ledger and state. An endorsing peer may receive transaction proposals for endorsement, and may respond either granting or denying endorsement. Each LCM component peer may act as either an endorser or committer. The decentralized trust system may comprise ordering service nodes 202 and membership peers nodes 203 which may be provided by the decentralized trust system provider, i.e. service provider C in the example of Figure 1. The decentralized trust system may also comprise a trusted LCM component 201. Ordering nodes 202 may approve channel establishment, include transaction blocks into the ledger and communicate status of the transaction blocks with committer and endorsing peer nodes. Membership nodes 203 may handle memberships of the decentralized trust network, in other words control which LCM components are peers of the decentralized network.

Embodiments described herein may therefore use a consensus based negotiation and a decentralized trust system, for example, Blockchain technology. For example, a smart contract based peer to peer network and LCM consensus based components may be used to enable direct interactions between LCM component peers and to bridge trustless domains. LCM components may use decentralized trust system technologies to empower native LCM routines. Embodiments disclosed herein therefore enable simple, agile and open life-cycle management routines. Embodiments described herein therefore allow for use of the shortest path directly between life-cycle managers belonging to a different function/service providers which avoids slow and complex orchestration negotiations cross the multiple orchestration levels.

Embodiments described herein provide elastic and open solutions for the direct life- cycle management between one or more LCM components. Embodiments described herein make use of a decentralized trust system, for example, of a Blockchain distributed peer to peer network to solve trustless gaps between different service providers. The LCM components for peers with the Blockchain system and they therefore contain data about transactions that have happened on the chain of their interest. Transactions are mutually agreed on a given orchestration assets and signed using public key encryption. Some of these nodes may be unreliable, and therefore the consensus process may need to be reliant.

Some Blockchain systems use smart contract consensus algorithms enabling decentralized life-cycle management. LCM smart contracts contain programs that can store data, make decisions, and indirectly communicate with other contractors via messages. These contracts are established in the Blockchain network by their owners, but their execution is taken care of by the Blockchain network. Hyperleger Fabric™, hosted by The Linux Foundation ^® is an example of such Blockchain system which intends to be a service that manages different assets, agreements and transactions between various organizations, i.e., forms a Blockchain business network. As will be appreciated by the person skilled in the art, such a system may be established by arbitrary service provider for instance by trusted infrastructure provider.

Figure 3 illustrates an example of an LCM component 300 according to some embodiments.

The LCM component may, as described previously, comprise a Blockchain application module 301 comprising an appropriate software development kits (SDK) and keys. The LCM component 300 may also comprise Blockchain peer module 302 configured to act as a committer or endorser peer as appropriate.

The LCM component 300 may also comprise an LCM agent 303 configured to establish smart contracts as will be described in more detail later. The LCM component 300 may also comprise a native LCM module 304 configured to provide any local services which the first service provider is capable of providing. Figure 4 illustrates the four main steps of the procedure to establish direct LCM component interactions between domains controlled by different service providers and responsible lifecycle managers. Step 0 comprises smart contract offerings and Blockchain network enrolment. Step 1 comprises LCM smart contract establishment based on consensus based authorization and LCM provider discovery. Step 2 comprises providing detailed LCM transactions and business contract fulfilment. Step 3 comprises direct LCM orchestration and mashup service fulfilment. For ease of reference we will separate these steps into sections.

Enrollment with the decentralized trust system

Figures 5 and 6 illustrate an example of an enrolment process.

Figure 5 illustrates an enrolment process. The enrolment process is to enrol a first LCM component in a virtualised network such as the network illustrated in Figure 2. As described previously the virtual network comprises a trusted provider configured to provide a decentralised trust system between a plurality of LCM components 200 controlled by different service providers in the virtual network. The decentralised trust system may comprise a Blockchain trust system implemented by the trusted service provider.

As described previously, the LCM component 300 may comprise a first native LCM module 304 and a first LCM agent 303. In the following example some steps are performed by the first LCM agent, and others by the first native LCM module. It will however be appreciated that in some examples, the functionality of these two modules is not physically separated, and all steps may be implemented by the first LCM component in general.

The first LCM component may be controlled by a first service provider and may be capable of providing local services to requesting customers. For example, the first LCM component may be able to route communications between three customer end points, for example points A, B and C in a virtual network. The trusted provider may comprise a trusted LCM component 510. The trusted LCM component may be controlled by the trusted provider and may be configured to provide the decentralized trust system as a service. The trusted LCM component may comprise a Blockchain application module 51 1 and a membership peer module 510.

In step 501 the first native LCM module 304 may on-board its own service offerings. This will be described in more detail in Figure 7. In some examples, as illustrated in Figure 5, onboarding of the service offerings may be performed prior to first service provider enrolment, but it may also be performed in the later stages of the process as per LCM demand. Reservation of the resources for the initial service offerings onboarding can also be part of the separate smart contract in the relationship with the infrastructure provider.

In step 502 the first LCM agent 303 receives an enrolment trigger from the first service provider. The trigger may be a business related intention for fulfilling a targeted application and/or for providing selected service that can be used for any related application. The LCM agent 303 may then process, in step 503, the enrolment trigger against any local LCM enrolment policies and may generate at least one local tag representing at least one local service that the first service provider is capable of providing. For example, as the first service provider is capable of routing traffic between the end points A, B and C, an example of a local tag may be dR: A, B, C, which illustrates that the first service provider is capable of providing a distributed router (dR) between the end points A, B and C. This distributed router example will be used throughout the application. It will however be appreciated that the principles described herein may be applied to any type of service, and that routing of traffic is used as an illustrative example. For example, the first service may be of a completely different type and different level in the cloud stack.

The at least one local tag may also contain further information regarding the local services. For example the at least one local tag may indicate the first service provider’s reputation, service price, modelling and/or relationships with other LCM components.

The first LCM agent 303 may then transmit, in step 504, an enrolment request to the Blockchain application 51 1. The enrolment request may comprise the at least one local tag representing at least one local service that the first service provider is capable of providing. In step 505 the Blockchain application 51 1 receives the enrolment request and forwards it to the membership peer module 512. The membership peer module 512 may then record, in step 506, the at least one local tag in the enrolment request alongside the first LCM component in a membership record. The membership peer module 512 may perform this for any enrolment request it receives and the membership record may therefore comprise a record of which LCM components are enrolled with the decentralised trust system, and a record of what local services that each of those enrolled LCM components are able to provide.

For example, the membership record may comprise a list of LCM components and their associated tags. An example of this is illustrated in table 1.

LCM component Tags

2 ^nd LCM component R: D and E

3 ^rd LCM component R: D and E

4 ^th LCM component dR: C, D and E

5 ^th LCM component R: G, H

6 ^th LCM component dR: F, G, H

7 ^th LCM component R: G, H

8 ^th LCM component R: C, D Table 1 : An example of a membership record where R: indicates a routing service between the following end points, and dR: indicates a distributed routing service between the following end points.

In step 507 the membership peer module 512 confirms to the Blockchain application 51 1 that the first LCM component has been enrolled with the decentralised trust system. This confirmation is then passed on to the first LCM agent by the Blockchain application in step 508. The first LCM agent 303 may then confirm its enrolment with the decentralised trust system to the first service provider in step 509. The enrolment process may therefore be summarized as illustrated in Figure 6. In step 601 the first LCM component receives an enrolment trigger, wherein the enrolment trigger comprises an indication of one or more local services that the first service provider is capable of providing. In step 602, the first LCM component generates an enrolment request comprising one or more local tags representing the one or more local services that the first service provider is capable of providing, and forwards the enrolment request to the trusted LCM component

In step 603, the trusted LCM component records the at least one local tag alongside the first LCM component in the membership record.

In step 604, the trusted LCM component confirms that the first LCM component has been enrolled with the decentralised trust system.

In some examples, the enrolment of the first service provider enrolment may be part of a regular NFVI enrolment as an additional service option depending on the chosen ecosystem establishment solution.

Figure 7 illustrates onboarding of the service and related resource management.

In step 701 the service provider determines whether allocated resources are already available for the onboarding of a new service. If the services are available the method asses to step 702 in which the new service is onboarded using the existing resources.

In step 703 the service provider may then trigger a smart contract enrolment for the fulfilment of a targeted mashup service. The Blockchain network enrolment may then occur in step 704.

If in step 701 the service provider determines that there are not allocated resources already available for the onboarding of the new service, the method passes to step 705 in which the service provider determines whether to use a separate smart contact with other provider to allocate the required resources for the new service. If the service provider decides to use a separate contract in step 705, the service provide may create the separate contract in step 706 with the required infrastructure resource service provider(s). This contract may be established and enrolled in steps 707 and 708. The service provider may then allocate needed resources through that contract and proceed with onboarding of a service and creation of the new contract in step 709 to fulfil a targeted mashup service. If in step 705 the service provider determines not to use a separate smart contract, the service provider may use the same contract for allocation of the resources to perform other engagements with the eco-system and fulfill targeted application fulfilment in step 710.

Smart Contract Establishment

Figures 8 and 9 illustrate smart contract establishment according to some embodiments.

Figure 8 illustrates an example of the signalling required for smart contract establishment according to some embodiments. In step 801 the first LCM agent 303 receives a service request to provide a first service. The first service request may comprise information describing the service required. The first service request may also comprise information relating to contract configuration and policies, constraints and Key Performance Indicators (KPIs) to be fulfilled in providing the first service.

The first LCM agent may then compare the service request to LCM policies in step 802. For example, the LCM policies may restrict the types of service requests that the first LCM component is allowed to use multi-provider services to provide. In these examples, the LCM component 300 may only attempt to provide a multi-provider service if the service request is of a type for which this is deemed allowable by the LCM policies.

LCM policies may also comprise pricing policies, location based policies, and/or any performance related policies. LCM policies may also comprise policies related to external service provider(s) such as contract restrictions, reputation requirements, requested level of shared LCM routines and any other suitable policies.

In step 803 the first LCM agent 303 may then request an indication of the local services available from the native LCM module 304. In step 804 the first LCM agent 303 may receive an indication of the local services from the native LCM module 304.

The first LCM agent 303 then determines, in step 805, whether or not the first service can be fully provided by the first service provider. In some embodiments, the first LCM agent may compare the first service to the one or more local services that the first service provider is capable of providing. In some examples, the first service provider is capable of fully providing the first service, and in these examples, may simply provide the first service as requested. For example if the first service is routing service between end points A and B the first service provider is capable of fully providing the first service. In this example, the first service provider may provide the first service as requested.

In some embodiments, however, in step 805 the first LCM agent 303 may determine that a portion of the first service cannot be provided by the first service provider. For example, the first service may be a distributed router between five end points, for example points A, B, C, D and E in the virtual network. In this example, as the first service provider is only capable of routing traffic between end points A, B and C, the first service provider is not capable of providing the full first service.

Responsive to this determination, the first LCM agent 303 may generate a first tag representative of the portion of the first service that the first service provider cannot provide. Therefore, if the first service comprises a distributed router between the end points A, B, C, D and E, the first LCM component may generate a first tag representing routing traffic between the points D, E and at least one of the points A, B and C. In other words, the first LCM component may generate a first tag representing the gaps in the first service which cannot be provided by the first LCM component. The first tag may therefore be expressed as dR: D, E, A/B/C. This tag indicates the portion of the first service that the first service provider cannot provide.

Similarly to the local tag, the first tag may also comprise information related to the provider reputation, service price and any other information relating to the portion first service that the candidate LCM components to fulfill the portion of the first service may adhere. In some embodiments, the first LCM agent may generate a plurality of first tags representative of the portion of the first service.

The first LCM agent may then transmit a discovery request to the trusted provider comprising the first tag. The trusted provider may then obtain, based on the first tag and the membership record, a list of LCM components comprising a second LCM component controlled by a second service provider, wherein the second service provider is capable of implementing a part of the portion of the first service. For example, the Blockchain application module 51 1 , may receive the discovery request in step 806. The Blockchain application module 51 1 may then transmit a peer query to the membership peer module 512 in step 807. The membership peer module 512 may then cross check the first tag with the entries in the membership record and may compile a list of LCM components in step 808. In other words, the membership peer node may locate at least one entry in the membership record comprising at least one tag which indicates that the associated LCM component is capable of providing at least a part of the service represented by the first tag In some examples, the membership peer module may locate a plurality of LCM components, each capable of providing at least a part of the service represented by the first tag. The list of LCM components therefore comprise candidate LCM components each capable of providing at least a part of the portion of the first service. For example, the list of LCM components for the membership record illustrated in table 1 , may be as follows.

LCM component Tag

2 ^nd LCM component R: D and E

3 ^rd LCM component R: D and E

4 ^th LCM component dR: C, D and E

8 ^th LCM component R: C, D

Table 2: An example of a list of LCM components

The first service provider cannot route traffic between the domain comprising the end points A, B and C and the end points D and/or E. Therefore each of the LCM components listed in table 2 is capable of performing at least part of the portion of the first service that the first service provider is unable to provide. As illustrated, in some examples the list of LCM components comprises more than one LCM component capable of providing the same service. In the above example, the 2 ^nd LCM component the 3 ^rd LCM component are both capable of routing traffic between points D and E. The membership peer module may then transmit the list of LCM components to the Blockchain application module in step 809. The Blockchain application module may then forward the list of LCM components to the first LCM agent in step 810.

In step 81 1 the first LCM agent selects one or more LCM components from the list to provide the first service. In the example illustrated in Table 2, there are a number of candidate LCM components that the first LCM agent may use. For example, the first LCM agent may select only the 4 ^th LCM component, as this is capable of providing the portion of the first service on its own. However, in some examples, the tags in the membership record may comprise further information, such as a list of LCM components that the associated LCM component is willing to collaborate with, or information associated with a price to the requesting LCM component for providing the requested service.

The first LCM agent may therefore analyse all of the information contained in the associated tags and may select, based on this information, which LCM components from the list to use.

By way of example, suppose the first LCM agent selects the 2 ^nd LCM component and 8 ^th LCM component to provide the portion of the first service collaboratively. These selected LCM components may be referred to as contractor LCM components.

The first LCM agent 303 may then transmit a contract request to the Blockchain application module 51 1 comprising one or more of the business model, policies, LCM inputs, and conditions that the 2 ^nd LCM component and 8 ^th LCM component provide the portion of the first service collaboratively on request.

The smart contract may then be processed by the Blockchain application module 51 1 and endorsed by the contractor peers in the membership record.

The smart contract establishment process may therefore be summarised as illustrated in Figure 9.

In step 901 the first LCM component receives the first service request. In step 902 the first LCM component obtains an indication of at least one local service that the first service provider is capable of providing. In step 903 the first LCM component compares the at least one local service to the first service.

In step 904 the LCM component generates a first tag representing a portion of the first service that the first service provider cannot provide and transmits a discovery request to the trusted LCM component comprising the first tag.

In step 905 the trusted LCM component processes the discovery request and generates a list of LCM components each capable of providing a part of the portion of the first service. In step 906 the trusted LCM component transmits the list to the first LCM component.

In step 907 the first LCM component selects one or more LCM components from the list to provide the portion of the first service and transmits a request to establish a transaction protocol, e,g, a smart contract, with the one or more LCM components to the trusted LCM component. The request to establish the transaction protocol may comprise contract policies. Contract policies may for instance indicate how the smart contract should be managed and which resources can be shared, what capabilities can be exchanged, potential requirements from the related business model, artifacts to be shared, pricing models and many other aspects related to the life-cycle management routines. Contract policies may be negotiated with the involved contractor LCM components during the smart contract establishment but also after the smart contract is granted in additional granting loops.

In step 908 the transaction protocol is processed by the decentralised trust system and endorsed by contractors.

After the transaction protocol is endorsed by the involved contractors, the Blockchain application module may transmit the transaction protocol to the ordering service which creates a Blockchain channel using the transaction protocol policies. Once a Blockchain channel is established, channel data may be distributed by the Blockchain application module to all contractor LCM components. Contractor LCM components may store the received information and create an own representation of the Blockchain. At this stage, the Blockchain channel may be enabled for further business LCM transactions as will be described in more detail below. In other words, the established Blockchain channel may be used for private trusted communication in a trustless environment. This way cross service provider LCM engagements can be established directly between grouped lifecycle management nodes using the common channel.

Detailed LCM Transactions

Figures 10 and 11 illustrate detailed LCM transactions in an example embodiment.

In step 1001 the first LCM agent generates a more detailed service request for the first service. For example, the more detailed service request may comprise more detail of the service requirements, model alignments, constraints (for example a constraint on the bandwidth or performance) LCM dependencies and sharing, and/or details regarding LCM access points. An LCM access point is a point where LCM component can be contacted. An access point may be tenant based or even single service based and may only be disclosed in the detailed service request.

Models may comprise for example orchestration models used for LCM routines. The detailed service request may therefore comprise principles of an orchestration model. Model alignments may also comprise business model details on sharing/usage of the resources/services.

The detailed transaction request may then be transmitted to the Blockchain application module 511 in step 1002 which may process the transaction request in step 1003. For example, the Blockchain application module 511 may process the transaction request and send the transaction request to a selected endorsing peer, i.e. one of the contractor LCM components 300 _c , for validation in step 1004.

The contractor LCM components 300c may be structured similarly to the first LCM component 300. For example, the contractor LCM component 300c may comprise a contractor LCM agent 303c and a contractor native LCM module 304c.

In step 1005 the contractor LCM agent 303c processes the request against the LCM policies, and determines whether or not to endorse the transaction request. If the transaction is endorsed, the contractor LCM agent 303c transmits a transaction endorsement to the Blockchain application module 511 in step 1006. The Blockchain application module 51 1 then transmits the endorsed transaction request to the rest of the contractor LCM components for validation. The rest of the contractor LCM components validate the transaction request against their own LCM agent policies, add requested LCM inputs, and validate the transaction request.

Once the Blockchain application module receives endorsements from all contractor LCM components, the transaction is established in step 1007 by the ordering peer module and a new block is generated in the smart contract channel. In other words, the ordering peer module takes care of transaction’s relationships in the smart contract. In some embodiments, the ordering peer module doesn’t have access to the sensitive parts of transaction when creating a new block but rather only subset of publicly available data. The ordering peer module organizes transaction blocks into the ledger and communicates that with committer peer and endorsing peer nodes. In other words, the block data may then be transmitted to all contractor LCM components in the smart contract, in step 1008. After that the contractor LCM components validate the transaction block received from the ordering service and update their ledger and worldstate. In other words, the contractor LCM components 300c store a local copy of the received block data and add it to the locally stored Blockchain.

In some examples a contractor LCM component 300c may suggest some modification to the transaction. Such an update may be generated by the contractor LCM agent 303c and forwarded to all the other contractors in an additional endorsing loop. The Blockchain application module 511 may then wait to receive endorsements from all of the contractor LCM components 300c. It will be appreciated that many iterations of this may occur as different contractor LCM components may suggest different alterations to the transaction.

The process for establishing detailed transactions using the established smart contract can therefore be summarized as illustrated in Figure 11.

In step 1 101 the first LCM component 300 transmits a more detailed service request for the first service to the trusted LCM component as a transaction.

In step 1 102 the transaction is forwarded by the trusted LCM component 510 to the contractor LCM components 300c. In step 1 103, the contractor LCM components 300c receive the transaction request, process it against their own LCM policies, and transmit a transaction endorsement to the trusted LCM component 510.

In step 1 104, the transaction is established by the trusted LCM component 510 and a new block is added to the block chain. The new block data is distributed to the contractor LCM components 300c.

In step 1105 the contractor LCM components 300c store the new block in their local Blockchain for use in later LCM routines.

In the example illustrated in Figure 1 , mashup service provider A may require external LCM resources that provides database functionality provided by the VNFaaS provider- E in order to provide a mashup service. The service provider A can commit transaction(s) related to that business aspect over the smart contract. Both the service providers use infrastructure resources provided by the laaS service provider B so they can commit transactions related to that business aspect involving service provider B in the smart contract. Service provider A can also use security service provided by the SaaS service provider D and can commit transactions related to that business aspect over the smart contract.

In this example therefore the smart contract comprises 4 contractor LCM components, the LCM of service provider A, the LCM component of service provider B, the LCM component of service provider E and the LCM component of service provider D.

By initiating the smart contract presented in this example all of the involved contractor LCM components may use resources from the NFVIaaS service provider C, which in this example also provides Blockchain network service in addition to NFVI services. The relationships established in the smart contract may be agreed in a single transaction or set of individual transactions. For instance, providers A, C, D and E can agree individually with infrastructure provider B on resource allocation using individual transactions, or together in the same transaction.

All used resources in the mashup service example and dependent LCM interactions may be negotiated via the smart contract and related detailed transactions. After the detailed transactions have been established, the service provider A, for instance, will know exactly how to use resources and trigger dependent LCM routines in the VNFaaS provider E in order to get dependent database functions aggregated into the service that has been requested at service provider A. In the same way service provider A can enable the security service provided by the SaaS provider D. The Blockchain can also be updated later on after the real LCM routines has been started. For instance, in the case of some provisioning lack of resources trigger, more resources can be reserved for the targeted service via additional business transaction in the Blockchain.

Direct LCM orchestration and mashup service fulfilment

Once the transaction protocol, or smart contract, has been established and providers has agreed via related set of detailed transactions, on how resources may be shared and how orchestration dependencies may be realized, the real LCM routines can start accordingly.

At this point, contractor LCM components 300c can interact directly utilizing corresponding LCM agents, or interact directly with domain native LCM components via interfaces negotiated in the previous stages. Any contracted service provider may benefit from the established smart contract in the defined business model borders and under defined orchestration policies.

Contracted service providers may for example share LCM provisioning data, or they may trigger dependent LCM routines using exposed LCM access points. An LCM access point is a point where LCM component can be contacted by an authorized entity, e.g. another LCM component. An access point may be tenant based or even single service based and may only be disclosed in the private channel. The level of sharing, including data and LCM interactions, may be predefined by the smart contract and may be controlled by the contracted LCM agents. Any additional openness in that field can create additional values to the rest of contractors. For instance the sharing of provisioning data directly used in the mashup service optimization may bring more business opportunities to the contractor service providers. The established Blockchain, or other decentralized trust system, channels provides direct LCM interaction without having to establish trust by using interactions via multiple orchestration levels, for example using an OSS/BSS bridge, with very limited interaction opportunities and very slow procedures. In example illustrated in Figure 1 , provider A utilizes database access points and capabilities from the provider E. Provider E can in addition provide an interface to trigger scaling workflow routines of the database resources as well as some subset of provisioning data via established trusted channels. Provider A may then combine these functionalities with knowledge of a number of client application users and its own set of provisioning data in order to optimize the targeted mashup service.

A smart contract may have a negotiated life time which may be business specific. In this way the contractor LCM components may utilize the smart contract as long as the relevant business interest exists. In some examples specific transactions may be initialized by a contractor in order to terminate a smart contract. In the termination of the contract the involved contractor LCM components may exchange assets and generate a resulting balance sheet of the related business at any point of time.

Service providers involved in such a mart contract may be a subset of eco-system providers within a common business interest following a common business model. The same contractor LCM components may be involved in many smart contracts and business models at a same time. Thus, a service provider can offer, at a same time, LCM services to other services providers with different business models.

Figures 12 and 13 illustrate an example of direct LCM orchestration in order to provide the first service 1200 according to some embodiments.

In step 1201 the first LCM agent 303 generated the first service request as a mashup service request based on the detailed transactions negotiated with the contractor LCM components. The mashup service request is then transmitted to the first native LCM module 304 in step 1202.

In step 1204 the first native LCM module 304 may then transmit a provision request to a first contractor LCM component 300c ¹ to request that the first contractor LCM component 300c ¹ provide the part of the portion of the first service that was agreed upon during the smart contract negotiations.

Equivalent provision requests may be transmitted to any other contractor LCM components required to fulfill the first service, for example in steps 1204 and 1205. The contractor LCM components may respond to the provision request in steps 1206, 1207 and 1208 and may provide the respective services, 1209, 1210 and 1211 as requested.

In some examples, the contractor LCM components may rely on smart sub-contracts with sub-contractor LCM components to provide the part of the portion of the first service which they offered to the first LCM component. For example, in Figure 12, the contractor LCM component 300c ² has sub-contracted contractor LCM component 300c ¹ to provide a part 1212 of the service 1210.

Returning to the example of the distributed router. For the sake of example suppose the 2 ^nd LCM component and 8 ^th LCM component are selected from the list of LCM components and a valid contract is negotiated. To provide the first service of the distributed router between the five end points A, B, C, D and E the first LCM component may transmit a provisioning request to the 2 ^nd LCM component to provide the service of routing traffic between the end points D and E. Equivalently the first LCM component may transmit a provisioning request to the 8 ^th LCM component to provide the service of routing traffic between the end points C and D.

Due to the previously negotiated smart contract, the 2 ^nd LCM component and 8 ^th LCM component may therefore provide the respective parts of the portion of the first service that the first service provide was unable to provide. The provision of these services may be compensated in some way by protocols negotiated in the smart contract. For example, the first service provider may pay in some way, for example with other services or with monetary compensation, for the 2 ^nd LCM component and the 8 ^th LCM component to provide the relevant services.

The first service provider may provide the service of routing traffic between the end points A, B and C. Therefore together, the first LCM component, 2 ^nd LCM component and 8 ^th LCM component can provide the full first service as requested.

The process of direct LCM orchestration may therefore be summarized as illustrated in Figure 13. In step 1301 the first LCM agent generates a provision request. The provision request may comprise tags describing the service description, model, workflows, configuration and/or another other LCM inputs.

The LCM agent may send the provision request to the first native LCM module which may drive the related workflows in step 1302.

In step 1303, the first native LCM module and the first LCM agent may then use access points negotiated in the smart contract to interact with the contractor LCM components to run the dependent partial LCM routines. The requested service thereby being fulfilled.

Figure 14 illustrates a method performed by the first LCM component according to some embodiments.

In some examples, the first LCM component enrolls with a decentralized trust system, for example a Blockchain trust system, in step 1401.

In step 1402, the first LCM component receives a request for a first service from the first service provider.

In step 1403 the first LCM component determines whether the first service can be fully provided by the first service provider. If the first LCM component determines that the first service can be fully provided by the first service provider, the first service provider provides the service in step 1404.

If in step 1403 the first LCM component determines that the first service cannot be fully provided by the first service provider, the method passes to step 1405

In step 1405 the first LCM component may generate a first tag representing a portion of the first service that the first LCM component cannot provide.

In step 1406 the first LCM component may transmit a discovery request to the trusted LCM component comprising the first tag. The discovery request may therefore indicate to the trusted LCM component which portions of the first service need to be provided by one of the plurality of service providers enrolled with the decentralized trust system. The first tag may comprise information relating to the reputation of the first service provider; a type of the first service; and/or a price associated with the first service.

In step 1407 the first LCM component may then receive, from the trusted LCM component, based on the first tag, a list of LCM components comprising a second LCM component controlled by a second service provider, wherein the second service provider is capable of providing a part of the portion of the first service. In some embodiments, the list may comprise only the second LCM component.

The first LCM component may then select LCM components from the list to provide the first service.

The first LCM component may then in step 1408 utilise the trusted LCM component to establish a transaction protocol, or smart contract, with second LCM component, and with any other LCM components selected from the list. The transaction protocol may comprise a condition that the second LCM component provide the part of the first service on request from the first service provider.

In step 1409 the first LCM component may transmit a provision request to the second LCM component to request that the second LCM component provide the part of the portion of the first service. In examples, where a plurality of LCM components are selected such that the plurality of LCM components are collectively capable of providing the portion of the first service, the first LCM component may transmit provision requests to each of the plurality of LCM components to collectively perform the portion of the first service.

Figure 15 illustrates a method performed by the trusted LCM component, controlled by a trusted service provider, according to some embodiments.

The trusted LCM component is configured to provide a decentralised trust system between a plurality of lifecycle management, LCM, components controlled by different service providers in the virtual network.

In step 1501 , the trusted LCM component receives a discovery request from a first LCM component controlled by a first service provider, wherein the discovery request comprises a first tag associated with a portion of a first service that the first service provider cannot provide.

In step 1502, the trusted LCM component obtains, based on the first tag and a membership record comprising entries for each of the plurality of LCM components enrolled on the decentralised trust system, a list of LCM components comprising a second LCM component controlled by a second service provider, wherein the second service provider is capable of providing a part of the portion of the first service.

In some embodiments, the trusted LCM component may locate at least one entry in the membership record comprising at least one tag which indicates that the associated LCM component is capable of providing at least a part of the service represented by the first tag; and add the at least one entry to the list of LCM components.

In step 1503 the trusted LCM component transmits the list to the first LCM component.

In some embodiments the trusted LCM component establishes a transaction protocol between the first LCM component and the second LCM component wherein the transaction protocol comprises a condition that the second LCM component will provide the part of the portion of the first service upon receiving an provision request from the first LCM component.

In some embodiments the trusted LCM component first enrols the first LCM component on the decentralised trust system. The enrolling may comprise receiving an enrolment request comprising at least one local tag associated with at least one local service that the first service provider is capable of providing; and recording the at least one local tag alongside the first LCM component in the membership record.

Each entry of the membership record may comprise an LCM component associated with at least one tag, wherein the at least one tag represents at least one service that the associated LCM component is capable of providing.

Figure 16 illustrates a method performed by a second LCM component, or a contractor LCM component. In step 1601 the second LCM component establishes a transaction protocol between the second LCM component and a first LCM component, wherein the first LCM component is enrolled with the decentralised trust system. For example, the second LCM component may negotiate detailed LCM transactions with the first LCM component. It will be appreciated that the transaction protocol may be between a plurality of LCM components, all contributing to provide the full first service.

In step 1602, the second LCM component receives a provision request from the first LCM component to provide a part of a portion of a first service.

In step 1603 the second LCM component provides the part of the portion of the first service.

In some embodiments the second LCM component first enrols with the decentralised trust system. For example, the second LCM component may transmit, to the trusted LCM component, an enrolment request comprising a local tag representing at least one local service that the second service provider is capable of providing.

In the embodiments described above local tags are used to describe the services provided by the different service providers. A local tag may indicate a service provider’s reputation, service price, modelling and/or relationships with other LCM components as well as indicate the type of service provided.

Further details about the services may then be determined as illustrated in Figures 10 and 1 1 with the detailed LCM transactions.

However, in some cases, methods of bridging the trust-less domains between service providers may utilise three levels of description of the services that they provide.

For example, in some examples the services provided by a service provider may be described by a local tag, an abstracted description comprising more information than the local tag, and a detailed description comprising more information than the abstracted description. An example of these different descriptions is given in the Section 1 below. An abstracted description may be example comprise a very simple description on capabilities and requirements of a particular service, whereas a tag may only comprise information relating to a type of service.

However, in some embodiments only two levels of description are required, the local tag (which in this case comprises an abstracted description) and the detailed description comprising more information that the local tag.

In some embodiments, as illustrated in Figure 17, therefore the first lifecycle management, LCM component illustrated in Figure 3 may further comprise a Service repository agent 1700. The service repository agent may be configured to store the aforementioned different levels of description in order to provide them, when appropriate, to other nodes in the virtual network.

Again, for the sake of clarity we will separate the method into stages. Firstly, enrolment, then Smart Contract Establishment and finally Detailed LCM transactions. The mashup service fulfilment may be performed as illustrated above in Figures 12 and 13.

Enrolment

Figure 18 illustrates an example of the signalling required for the enrolment process. Similar steps to those illustrated in Figure 5 have been given corresponding reference numerals. In this particular example three levels of service description are utilised.

As described previously with reference to Figure 5, enrolment with the decentralised trust system comprises enrolling the LCM component 300 with the trusted LCM component 510.

For service offerings of the first service provider, the first service provider provides a description of the services to the first LCM Agent 303 in step 1801. The LCM Agent 303 may then analyse the service descriptions in step 1802 and extract detailed descriptions of the services.

The LCM agent may then send the detailed descriptions to the Service repository agent 1700 in step 1803 which stores the detailed descriptions in step 1804. The Service repository agent 1700 may then indicate to the first LCM agent 303 that the detailed description has been stored in step 1805.

The first LCM Agent 303 may then indicate to the first service provider that the new service offering has been processed in step 1806.

The first LCM Agent 303 may then receive an enrolment trigger 502, similarly to as illustrated in Figure 5. In step 503 the LCM agent 303 may then process, the enrolment trigger against any local LCM enrolment policies.

In order to generate the at least one local tag representing at least one local service that the first service provider is capable of providing as described with respect to Figure 5, the steps 1807 to 1812 may be performed by the first LCM component 300.

In step 1807 the first LCM Agent 1807 requests a list of abstracted descriptions of the services descriptions stored in the Service repository agent 1700. In step 1808 the Service repository agent 1700 generates a list of abstracted descriptions from the detailed descriptions that have been previously stored. The level of information included in the abstracted description may be a level of information that the first LCM component 300 may use to establish a smart contract with other LCM components.

In step 1809 the Service repository agent 1700 transmits a list of abstracted service descriptions to the first LCM agent 303. The list of abstracted service descriptions may comprise a list of abstracted descriptions of all services that the first service provider is capable of providing.

In step 1810 the first LCM Agent 303 may then send a request to the Service repository agent 1700 for local tags representing the abstracted service descriptions. The Service repository agent 1700 may then generate the local tags, in step 181 1 and may store them locally with the associated detailed service descriptions and abstracted service descriptions.

In step 1812 the Service repository agent 1700 may transmit the local tags to the first LCM Agent 303. In step 1813 the first LCM Agent 303 may then generate an enrolment request comprising the local tags, and may transmit the enrolment request to the Blockchain application 511 in step 504.

It will be appreciated that in some examples, the first LCM component 300 will not perform steps 1810 to 1812, and instead the local tag may comprise the abstracted descriptions of the services.

The remaining steps are similar to those described with respect to Figure 5. For example, in step 504 the first LCM Agent 303 transmits the enrolment request to the Blockchain application 51 1. The Blockchain application 511 then forwards the enrolment request to the Membership module 512 in step 505. The Membership module may store the local tags (which may or may not comprise abstracted descriptions depending on whether two or three levels of description are being employed) alongside the first service provider in the membership record in step 506.

In step 507 the membership peer module 512 confirms to the Blockchain application 511 that the first LCM component 300 has been enrolled with the decentralised trust system. This confirmation may then be passed on to the first LCM agent 303 by the Blockchain application in step 508.

The enrolment process may therefore be summarized as illustrated in either of Figures 19 or 20.

For the example illustrated in Figure 19 only two levels of service description are provided. For example, the local tag, which is stored in the membership record, in this embodiment comprises an abstracted description of the service.

In step 1901 the first LCM component onboards an own service onto the first LCM agent 303 and provides a detailed service description to the first LCM agent 303.

In step 1902 the first LCM agent 303 sends the detailed description to the Service repository agent 1700 to store. The first LCM component 300 therefore stores a detailed description of one or more local services that the first service provider is capable of providing. In step 1903 the first LCM agent 303 receives local tags, which in this embodiment comprise abstracted descriptions of the services that the first service provider is capable of providing from the Service repository agent 1700, and attaches the local tags to an enrolment request which is transmitted to the Blockchain Application 51 1. The first LCM component 300 therefore generates a local tag representative of the one or more local services, wherein the local tag comprises less detail about the one or more local services than the detailed description, and enrols with the decentralised trust system using the local tag.

For the example illustrated in Figure 20, in step 2001 the first service provider onboards an own service onto the first LCM agent 303 and provides a detailed service description to the first LCM agent 303.

In step 2002 the first LCM agent 303 sends the detailed description to the Service repository agent 1700 to store. The first LCM component 300 therefore stores a detailed description of one or more local services that the first service provider is capable of providing.

In step 2003 the service repository agent 1700 also stores highly abstracted service descriptions mapped to the detailed descriptions, and generates local tags representative of the detailed descriptions and abstracted descriptions. The first LCM component 300 therefore generates an abstracted description of the one or more local services, and stores the abstracted description alongside the detailed description of the one or more local services, wherein the abstracted description comprises more detail about the one or more local services than the local tag and less detail about the one or more local services than the detailed description.

In step 2004 the first LCM Agent 303 receives the local tags representative of the services that the first service provider is capable of providing from the Service repository agent 1700, and attaches the local tags to an enrolment request transmitted to the Blockchain Application 51 1. The first LCM component 300 therefore generates a local tag representative of the one or more local services, wherein the local tag comprises less detail about the one or more local services than the detailed description; and enrols with the decentralised trust system using the local tag. The Blockchain application 51 1 , i.e. the trusted LCM component 510 therefore receives an enrolment request from a first lifecycle management, LCM, component 300 controlled by a first service provider to enrol the first LCM component 300 with the decentralised trust system; wherein the enrolment request comprises a local tag representative of one or more local services the first service provider is capable of providing. The trusted LCM component 510 will therefore, store the first LCM component alongside the local tag in a membership record, wherein the membership record comprises entries for each of a plurality of LCM components enrolled on the decentralised trust system.

Smart Contract Establishment

When a service provider initiates business engagement and smart contract generation it may start service description discovery related to targeted mashup service fulfilment. Service description discovery is enabled by the Service repository agent 1700 being capable of creating blockchain network service description discovery requests, and processing and storing the received responses. Service description discovery procedures use LCM agent and blockchain network mechanisms in the background. Smart contract committers may search for missing service capabilities using one of the proposed service discovery solutions.

Figures 21 to 23 illustrate service discovery and smart contract establishment according to some embodiments.

Figure 21 illustrates an example of the signalling required for smart contract establishment according to some embodiments. Again, similar steps to those illustrated in Figure 8 have been given corresponding reference numerals.

In step 801 the first LCM agent 303 receives a service request to provide a first service. The first service request may comprise information describing the service required.

The first LCM agent 303 may then compare the service request to LCM policies in step 802. For example, the LCM policies may restrict the types of service requests that the first LCM component is allowed to use multi-provider services to provide. In these examples, the LCM component 300 may only attempt to provide a multi-provider service if the service request is of a type for which this is deemed allowable by the LCM policies.

In this example, in step 2101 the first LCM agent 303 requests a set of service descriptions from the Service repository agent 1700. For example the first LCM agent 303 may request information relating only to services of the same service type as the first service request.

In step 2102 the Service repository agent 1700 generates a list of service descriptions according to the received request in step 2101.

In step 2103, the Service repository agent 1700 transmits the list of detailed descriptions to the first LCM Agent.

In step 805 the first LCM agent 303 then determines whether or not the first service can be fully provided by the first service provider and generates a first tag representative of the portion of the first service that the first service provider cannot provide.

In this example step 805 may comprise the steps 2104 to 2107. In step 2104 the first LCM Agent 303 analyses the list of detailed descriptions of services received in step 2103 and identifies gaps in the first service which the first service provider cannot provide. In step 2105 the first LCM Agent 303 sends an indication of these gaps to the Service repository agent 1700 to generate a first tag representative of the gaps.

In step 2106 therefore the Service repository agent 1700 generates a list of at least one first tag representative of the portion of the first service that the first service provider cannot provide. In some examples, similarly to as described above with respect to the local tag, the first tag comprises an abstracted description of the portion of the first service that the first service provider cannot provide. However, in some examples, where three levels of service description is used, the first tag may comprise less information than an abstracted description.

In step 2107 the Service repository agent transmits the at least one first tag to the first LCM agent 303. In step 2108 the first LCM Agent 303 generates a discovery request including the at least one first tag.

In step 806, equivalently to as described in Figure 8, the Blockchain application 51 1 , may receive the discovery request from the first LCM agent 303. The Blockchain application 511 may then transmit a peer query to the membership peer module 512 in step 807. The membership peer module 512 may then cross check the first tag with the entries in the membership record and may compile a list of LCM components in step 808. In other words, the membership peer node may locate at least one entry in the membership record comprising at least one tag which indicates that the associated LCM component is capable of providing at least a part of the service represented by the first tag.

In examples where the first tag comprises an abstracted description of the portion of the first service that method passes on to step 809. However, if the first tag comprises less information, then simply transmitting the tags associated with the candidate LCM components back to the first LCM Agent may not provide enough information for the LCM components to establish a smart contract.

In these examples therefore, the membership peer module may send a request to each of the candidate LCM components for abstracted descriptions of the services associated with the relevant tags in the membership record. The candidate LCM components may then reply with abstracted descriptions which they deem appropriate for the first LCM component. In other words, by only using tags comprising less information that an abstracted description to enrol with the decentralised trust system, the LCM component can retain control of how and to whom abstracted descriptions of services are transmitted. This may be advantageous for services where the LCM component wishes to keep the rights to share descriptions with preferred contractors or provide customized descriptions per request.

In step 808 the membership peer module 512 generates a list of candidate LCM components comprising abstracted descriptions of the services that they provide. As previously described, in some examples the tags stored in the membership record comprise abstracted descriptions, and in some examples the abstracted descriptions are requested from the candidate LCM components. The membership peer module 512 may then transmit the list of LCM components to the Blockchain application 51 1 in step 809. The Blockchain application 51 1 may then forward the list of LCM components to the first LCM agent 303 in step 810.

In step 81 1 the first LCM agent 303 selects one or more LCM components from the list to provide the first service. In some examples, the first LCM component uses the service repository agent 1700 to process service descriptions and prioritize the best matching offers. Selection mechanisms may have multiple prioritization criteria such as matching capabilities and requirements, dependencies, the service provider’s reputation tags, pricing, used models, etc. The query might also include more complex records where some providers can come together as partners providing requested service.

In step 2109 the first LCM Agent 303 sends the selected LCM components and the corresponding abstracted service descriptions to the service repository agent 1700 which stores a local copy of the abstracted service descriptions alongside their corresponding LCM component in step 21 10. In step 211 1 , the service repository agent 1700 confirms that the abstracted service descriptions have been stored.

Once all requirements are fulfilled, the smart contract is committed to the trusted Blockchain network.

The process for establishing a smart contract may therefore be summarized as illustrated in Figures 22 or 23.

For the example illustrated in Figure 22 only two levels of service description are utilised. In other words, the first tag and local tags comprise abstracted descriptions of services.

In step 2201 the first LCM component 300, responsive to a determination that the first service cannot be fully provided by the first service provider, generates a first tag representing a portion of the first service that the first service provider cannot provide.

In step 2202 the first LCM component transmits a discovery request to the trusted provider, wherein the discovery request comprises the first tag. The trusted LCM component may then compare the first tag to the membership record to determine which of the enrolled LCM components are candidate LCM components for performing a part of the portion of the first service. The trusted LCM component therefore receives a discovery request from a first LCM component, wherein the discovery request comprises a first tag associated with a portion of a first service that the first service provider cannot provide; obtains, based on the first tag and the membership record, a list of LCM components controlled by different service providers, wherein each LCM component on the list is capable of providing a part of the portion of the first service; and transmits the list of LCM components to the first LCM component.

In step 2203 the first LCM component receives, from the trusted LCM component list of LCM components each capable of providing a part of the portion of the first service, and selects from the list at least one LCM component for providing the portion of the first service.

In some examples the first LCM component 300 may determine that there are still gaps in the first service which have not been accounted for in the list of LCM components, and may therefore return to step 2202 and send a further discovery request.

The smart contract is then established in step 2204.

In the example illustrated in Figure 23, three levels of service description are utilised, i.e. a local tag, an abstracted description and a detailed description.

In step 2301 the first LCM component, responsive to a determination that the first service cannot be fully provided by the first service provider, generates a first tag representing a portion of the first service that the first service provider cannot provide.

In step 2302 the first LCM component transmits a discovery request to the trusted provider, wherein the discovery request comprises the first tag.

The trusted LCM component may then compare the first tag to the membership record to determine which of the enrolled LCM components are candidate LCM components for performing a part of the portion of the first service. In this example, as three levels of service description are in use in this example, the trusted LCM component may then transit queries to the candidate LCM components to retrieve abstracted descriptions of the services which they can provide in step 2303. The trusted LCM component therefore responsive to receiving the discovery request; retrieves respective abstracted descriptions associated with each of LCM components in the list of LCM components; and transmits the respective abstracted descriptions to the first LCM component

In step 2304 the candidate LCM components transmit abstracted descriptions of the services they can provide to the trusted LCM component. Steps 2303 and 2304 may be performed using the trusted membership channel.

The trusted LCM component may then provide the abstracted descriptions to the first LCM component which can then select from the list of candidate LCM components at least one LCM component for providing the portion of the first service in step 2305. The first LCM component therefore receives abstracted descriptions associated with each respective LCM component in the list of LCM components; and selects an LCM component from the list of LCM components based the received abstracted descriptions.

In some examples the first LCM component 300 may determine that there are still gaps in the first service which have not been accounted for in the list of LCM components, and may therefore return to step 2302 and send a further discovery request.

The smart contract may then be established in step 2306.

Detailed Transactions

Once the smart LCM contract has been established, business transactions and more detailed service information can be exchanged on the established private channels. LCM components acting as transaction committers can process existing service information and determine more detailed transaction requirements and select required services to fulfil that business transaction. For the detailed service description requirements the LCM component may first retrieve detailed descriptions of the services that the first service provider is capable of providing from the service repository agent and then determine the detailed service descriptions of missing services. Contractor LCM components may also request existing information relating to services provided by other contractor LCM components from the local copy of highly abstracted service descriptions in the contractor LCM component’s service repository agent.

Figure 24 illustrates an example of the signalling performed for providing detailed transactions between LCM components.

Transaction LCM component committer, in this example the first LCM component 300, may combine collected service information to trigger a detailed service description discovery, as part of smart contract transaction, by using its service repository agent and LCM agent to communication with the Blockchain framework. Similar steps to those illustrated in Figure 10 have been given similar reference numerals.

In step 1001 , as described above the first LCM agent 303 generates a more detailed service request for the first service. In this example, performing step 1001 comprises the steps 2401 to 2409.

In step 2401 the first LCM agent 303 receives a smart contract transaction request. In step 2402 the first LCM Agent 303 processes the transaction request to generate a new transaction which may stipulate certain requirements of the first LCM component 300.

In step 2403 the first LCM agent 303 transmits a request to the service repository agent 1700 for detailed descriptions of the relevant services the first service provider is capable of providing.

In step 2404 the service repository agent 1700 generates list of detailed descriptions of the relevant services that the first service provider is capable of providing.

In step 2405 the service repository agent 1700 transmits the list of detailed descriptions to the first LCM agent 303.

In step 2406 the first LCM agent 303 transmits a request to the service repository agent 1700 for the abstracted descriptions of the services that the contractor LCM components 300c are capable of providing. The abstracted descriptions were stored in the service repository agent 1700 at the end of the process illustrated in Figure 21. In step 2407 the service repository agent 1700 generates the list of abstracted descriptions and transmits these to the first LCM agent 303.

In step 2409 the first LCM agent 303 then generates a detailed transaction request utilizing the received detailed description of the services that the first service provider is capable of providing and the abstracted descriptions of the services that the contractor LCM components are capable of providing. The detailed transaction request may comprise a request for detailed descriptions of the services that the contractor LCM components are capable of providing.

The detailed transaction request may then be transmitted to the Blockchain application module 51 1 in step 1002 which may process the detailed transaction request in step 1003.

In step 1004 the Blockchain application 51 1 may send the detailed transaction request to a selected endorsing peer, i.e. one of the contractor LCM components 300c, for validation in step 1004. In step 1005 the contractor LCM agent 303c processes the request against the LCM policies, and determines whether or not to endorse the transaction request. In this example step 1005 comprises the steps 2410 to 2414.

In step 2410 the contractor LCM agent 303c processes the detailed transaction request against the LCM smart contract policies. In step 241 1 the contractor LCM agent 303c requests the detailed service descriptions of the relevant services from the contractor LCM component’s service repository agent 1700c.

In step 2412 the service repository agent 1700c generates the list of detailed descriptions as requested in step 241 1 , and sends the detailed descriptions to the contractor LCM agent 303c in step 2413. In step 2414 the contractor LCM agent 303c generates a transaction endorsement comprising the detailed descriptions, and in step 1006 transmits the transaction endorsement to the Blockchain application 51 1.

In step 1007 the transaction is established by the ordering peer module and a new block is generated in the smart contract channel. In step 2415 therefore, the first LCM agent 303 receives the transaction block data update, which comprises the detailed descriptions provided by the contractor LCM component 300c.

In step 2416 the first LCM agent 303 extracts the detailed description information from the receiving data and transmits the detailed descriptions to the service repository agent 1700 in step 2417.

In step 2418 the service repository agent 1700 stores the detailed descriptions of the services that the contractor LCM component 300c is capable of providing, and notifies that first LCM agent 303 that this has been done in step 2419.

As all LCM components involved in the smart contract now how detailed information relating to the services that the other components are capable of providing, the native LCM routines can now be implemented.

Figure 25 is therefore an example summary of a method of providing detailed descriptions of services.

In step 2501 the first LCM component 300 generates a request for detailed descriptions of services provided by contractor LCM components. To do this, the first LCM component 300 may make use of detailed descriptions and abstracted descriptions stored in the service repository agent.

The trusted LCM component 510 may then receive the request from the first LCM component 300 to retrieve detailed descriptions of services the at least one of the LCM components on the list are capable of providing; and may retrieve the detailed descriptions from the at least one of the LCM components on the list.

In step 2502 the request is processed by the contractor LCM component’s repository agent 1700c which generates detailed descriptions of the services provided by the contractor’s service provider and transmits an endorsement of the transaction comprising the detailed descriptions to the first LCM component 300. The contractor LCM component 300c then transmits the endorsement of the transaction to the trusted LCM component 510 which transmits the detailed descriptions to the first LCM component 300.

In step 2503 the first LCM component 300 utilises the received detailed descriptions of the services provided by the contractor LCM component(s) to optimise the end-to- end service fulfilment and LCM routines. Once the smart contract and transactions are validated, real native LCM routines can take place using established direct LCM channels. Such open free exchange of service information via distributed service description repository enables direct and flexible multi-provider service mashups. Simple and fast finding of the correct services opens multiple business opportunities without big cost on complex provider negotiations and multi-layer interactions. With flexible service exposure all involved providers can freely consume other’s services and benefit from more optimized LCM setups.

Figure 26 illustrates a first LCM component 2600 according to some embodiments comprising processing circuitry (or logic) 2601. The processing circuitry 2601 controls the operation of the first LCM component 2600 and can implement the method described herein in relation to a first LCM component 2600. The processing circuitry 2601 can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the first LCM component 2600 in the manner described herein. In particular implementations, the processing circuitry 2601 can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of the method described herein in relation to the first LCM component 2600.

Briefly, the processing circuitry 2601 of the first LCM component 2600 is configured to: receive a service request to provide a first service; responsive to a determination that the first service cannot be fully provided by the first service provider, generate a first tag representing a portion of the first service that the first service provider cannot provide; transmit a discovery request to the trusted LCM component, wherein the discovery request comprises the first tag; receive, from the trusted LCM component based on the first tag, a list of LCM components comprising a second LCM component controlled by a second service provider, wherein the second service provider is capable of providing a part of the portion of the first service; and transmit a provision request to the second LCM component to provide the part of the portion of the first service.

In some embodiments, the first LCM component 2600 may optionally comprise a communications interface 2602. The communications interface 2602 of the first LCM component 2600 can be for use in communicating with other nodes, such as other virtual nodes. For example, the communications interface 2602 of the first LCM component 2600 can be configured to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar. The processing circuitry 2601 of the first LCM component 2600 may be configured to control the communications interface 2602 of the first LCM component 2600 to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar.

Optionally, the first LCM component 2600 may comprise a memory 2603. In some embodiments, the memory 2603 of the first LCM component 2600 can be configured to store program code that can be executed by the processing circuitry 2601 of the first LCM component 2600 to perform the method described herein in relation to the first LCM component 2600. Alternatively or in addition, the memory 2603 of the first LCM component 2600, can be configured to store any requests, resources, information, data, signals, or similar that are described herein. The processing circuitry 2601 of the first LCM component 2600 may be configured to control the memory 2603 of the first LCM component 2600 to store any requests, resources, information, data, signals, or similar that are described herein.

Figure 27 illustrates a trusted LCM component 2700 according to some embodiments comprising processing circuitry (or logic) 2701. The processing circuitry 2701 controls the operation of the trusted LCM component 2700 and can implement the method described herein in relation to a trusted LCM component 2700. The processing circuitry 2701 can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the trusted LCM component 2700 in the manner described herein. In particular implementations, the processing circuitry 2701 can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of the method described herein in relation to the trusted LCM component 2700.

Briefly, the processing circuitry 2701 of the trusted LCM component 2700 is configured to: receive a discovery request from a first LCM component controlled by a first service provider, wherein the discovery request comprises a first tag associated with a portion of a first service that the first service provider cannot provide; obtain, based on the first tag and a membership record comprising entries for each of the plurality of LCM components enrolled on the decentralised trust system, a list of LCM components comprising a second LCM component controlled by a second service provider, wherein the second service provider is capable of providing a part of the portion of the first service; and transmit the list to the first LCM component.

In some embodiments, the trusted LCM component 2700 may optionally comprise a communications interface 2702. The communications interface 2702 of the trusted LCM component 2700 can be for use in communicating with other nodes, such as other virtual nodes. For example, the communications interface 2702 of the trusted LCM component 2700 can be configured to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar. The processing circuitry 2701 of the trusted LCM component 2700 may be configured to control the communications interface 2702 of the trusted LCM component 2700 to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar.

Optionally, the trusted LCM component 2700 may comprise a memory 2703. In some embodiments, the memory 2703 of the trusted LCM component 2700 can be configured to store program code that can be executed by the processing circuitry 2701 of the trusted LCM component 2700 to perform the method described herein in relation to the trusted LCM component 2700. Alternatively or in addition, the memory 2703 of the trusted LCM component 2700, can be configured to store any requests, resources, information, data, signals, or similar that are described herein. The processing circuitry 2701 of the trusted LCM component 2700 may be configured to control the memory 2703 of the trusted LCM component 2700 to store any requests, resources, information, data, signals, or similar that are described herein.

Figure 28 illustrates a second LCM component 2800, or contractor LCM component, according to some embodiments comprising processing circuitry (or logic) 2801. The processing circuitry 2801 controls the operation of the second LCM component 2800 and can implement the method described herein in relation to a second LCM component 2800 or contractor LCM component. The processing circuitry 2801 can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the second LCM component 2800 in the manner described herein. In particular implementations, the processing circuitry 2801 can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of the method described herein in relation to the second LCM component 2800. Briefly, the processing circuitry 2801 of the second LCM component 2800 is configured to: establish a transaction protocol between the second LCM component and a first LCM component, wherein the first LCM component is enrolled with the decentralised trust system; receive a provision request from the first LCM component to provide a part of a portion of a first service; and provide the part of the portion of the first service.

In some embodiments, the second LCM component 2800 may optionally comprise a communications interface 2802. The communications interface 2802 of the second LCM component 2800 can be for use in communicating with other nodes, such as other virtual nodes. For example, the communications interface 2802 of the second LCM component 2800 can be configured to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar. The processing circuitry 2801 of the second LCM component 2800 may be configured to control the communications interface 2802 of the second LCM component 2800 to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar.

Optionally, the second LCM component 2800 may comprise a memory 2803. In some embodiments, the memory 2803 of the second LCM component 2800 can be configured to store program code that can be executed by the processing circuitry 2801 of the second LCM component 2800 to perform the method described herein in relation to the second LCM component 2800. Alternatively or in addition, the memory 2803 of the second LCM component 2800, can be configured to store any requests, resources, information, data, signals, or similar that are described herein. The processing circuitry

2801 of the second LCM component 2800 may be configured to control the memory

2803 of the second LCM component 2800 to store any requests, resources, information, data, signals, or similar that are described herein. Figure 29 illustrates a first LCM component 2900, according to some embodiments comprising processing circuitry (or logic) 2901. The processing circuitry 2901 controls the operation of the first LCM component 2900 and can implement the method described herein in relation to a first LCM component 2900. The processing circuitry 2901 can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the first LCM component 2900 in the manner described herein. In particular implementations, the processing circuitry 2901 can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of the method described herein in relation to the first LCM component 2900, for example a first LCM agent.

Briefly, the processing circuitry 2901 of the first LCM component 2900 is configured to: generate a local tag representative of the one or more local services, wherein the local tag comprises less detail about the one or more local services than a detailed description; and enrol with the decentralised trust system using the local tag.

The first LCM component 2900 may comprise a memory 2903. In some embodiments, the memory 2903 of the first LCM component 2900 can be configured to store program code that can be executed by the processing circuitry 2901 of the first LCM component

2900 to perform the method described herein in relation to the first LCM component 2900. Alternatively or in addition, the memory 2903 of the first LCM component 2900, can be configured to store any requests, resources, information, data, signals, or similar that are described herein. In particular the memory 2903 may be configured to store a detailed description of one or more local services that the first service provider is capable of providing. The processing circuitry 2901 of the first LCM component 2900 may be configured to control the memory 2903 of the first LCM component 2900 to store any requests, resources, information, data, signals, or similar that are described herein.

In some embodiments, the first LCM component 2900 may optionally comprise a communications interface 2902. The communications interface 2902 of the first LCM component 2900 can be for use in communicating with other nodes, such as other virtual nodes. For example, the communications interface 2902 of the first LCM component 2900 can be configured to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar. The processing circuitry

2901 of the first LCM component 2900 may be configured to control the communications interface 2902 of the first LCM component 2900 to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar.

Figure 30 illustrates a trusted LCM component 3000, according to some embodiments comprising processing circuitry (or logic) 3001. The processing circuitry 3001 controls the operation of the trusted LCM component 3000 and can implement the method described herein in relation to a trusted LCM component 3000. The processing circuitry 3001 can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the trusted LCM component 3000 in the manner described herein. In particular implementations, the processing circuitry 3001 can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of the method described herein in relation to the trusted LCM component 3000, for example a Blockchain application.

Briefly, the processing circuitry 3001 of the trusted LCM component 3000 is configured to: receive an enrolment request from a first lifecycle management, LCM, component controlled by a first service provider to enrol the first LCM component with the decentralised trust system; wherein the enrolment request comprises a local tag representative of one or more local services the first service provider is capable of providing.

The trusted LCM component 3000 may comprise a memory 3003. In some embodiments, the memory 3003 of the trusted LCM component 3000 can be configured to store program code that can be executed by the processing circuitry 3001 of the trusted LCM component 3000 to perform the method described herein in relation to the trusted LCM component 3000. Alternatively or in addition, the memory 3003 of the trusted LCM component 3000, can be configured to store any requests, resources, information, data, signals, or similar that are described herein. In particular the memory 3003 may be configured to store the first LCM component alongside the local tag in a membership record, wherein the membership record comprises entries for each of a plurality of LCM components enrolled on the decentralised trust system. . The processing circuitry 3001 of the trusted LCM component 3000 may be configured to control the memory 3003 of the trusted LCM component 3000 to store any requests, resources, information, data, signals, or similar that are described herein.

In some embodiments, the trusted LCM component 3000 may optionally comprise a communications interface 3002. The communications interface 3002 of the trusted LCM component 3000 can be for use in communicating with other nodes, such as other virtual nodes. For example, the communications interface 3002 of the trusted LCM component 3000 can be configured to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar. The processing circuitry 3001 of the trusted LCM component 3000 may be configured to control the communications interface 3002 of the trusted LCM component 3000 to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar.

There is therefore provided methods and apparatus for providing multi-provider services using direct interaction between LCM components. This enables a direct LCM orchestration establishment between function/service providers on the single orchestration level, which avoids complex loops crossing multiple orchestration levels. The embodiments described herein also provide an open solution for negotiation of trustiness in multi-provider LCM environments using compact LCM agent component and utilizing consensus based Blockchain technology.

By using the shortest direct negotiation path via LCM agents, embodiments described herein increase flexibility, simplicity and agility of LCM routines across dependent multi- provider domains. Orchestration takes a few seconds rather than months.

Embodiments disclosed herein use LCM discovery tags for discovery mechanisms, tags such as prioritization tags based on provider’s reputation, service offerings, service price, modeling, relationship and many other LCM aspects.

Embodiments disclosed herein therefore provide a simplified solution of direct orchestration model alignments in runtime.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design many alternative embodiments without departing from the scope of the appended claims. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim,“a” or“an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the claims. Any reference signs in the claims shall not be construed so as to limit their scope.

Section 1

# Router descriptions example #==============================

# -

# Short local tag

# - router_xtype_v3.3_locations_A_B_C

# - # Short abstracted description

# - router_xprovider

properties:

version: v3.3

capabilities:

endpoint:

type: datatypes. router.endpoint.XRouter requirements:

host

# DB descriptions example

#====================

#

# Short local tag

# db cassandra v1.1 locations A B C

# -

# Short abstracted description

# # Note: the following description can also be shorter or

# a bit longer then in the example

# - cassandra_db

properties:

version: v1.1

capabilities:

endpoint:

type: datatypes. db.endpoint.Cassandra

distribution:

type: distributed_x_clusters

locations:

- zone A, segment 2

- zone B, area 1 ,2

- zone C, on demand

data

type: noSQL, decentralized

performance:

transactions: 20000w/s

scalability: up to 50 instances

access:

type: db_port_range, lcmjnterface, monitoringjnterface requirements:

host:

capabilities:

min_cpus: 2

min_mem: 4G

min_storage: 40G

access:

type: db_port_range

security: account_credentials

# -

# Full description

# # Can have some private information available only for contracted group.

# - inputs:

db_credentials:

username:

default: user

token:

default: token

n u m ber_of_cl u sters :

default: 1

number_of_cpus:

default: 2

memory:

default: 4G

storage:

default: 40G

lcm_enabled:

default: false

monitoring_enabled:

default: false

pricingjnputs:

default: {}

cassandra_db

properties:

version:

type: string

default: v1.1

constraints:

- in_range: [0.8, 1.1]

port:

type: integer

default: 9060

constraints: - in_range: [8000,65535]

capabilities:

endpoint:

type: datatypes. db.endpoint.Cassandra

distribution:

type: distributed_x_clusters

locations:

- zone: zone A

area: segment 2

status: active

capabilities:

latency: 10

distance: 100

- zone: zone B

area: area 1 ,2

- zone: zone C

status: inactive

data

type: noSQL

distribution: decentralized

performance:

transactions: 20000w/s

scalability: up to 50 instances

access:

type: db_port_range, lcmjnterface, monitoringjnterface

requirements:

host:

capabilities:

min_cpus: 2

min_mem: 4G

min_storage: 40G

num_cpus: type: integer

default: 2

constraints:

- in_range: [2,100]

price_per_cpu: 2

memory:

type: datatype. mem. Types

default: 4G

constraints:

- in_range: [4,200]

price_per_g: 2

storage:

type: datatype. mem. Types

default: 4G

constraints:

- in_range: [40,400]

price_per_g: 2

access:

type: db_port_range

security: account_credentials

interfaces:

db:

db_url: xprovider.com

enrolment_url: xprovider.com/enrollment/{user} spec: xprovider.com/docs/db/spec/{user} lcm:

lcm_url: xprovider.com/apis/lcm/{user} spec: xprovider.com/docs/db/lcm/spec/{user} monitoring:

data_url: xprovider.com/apis/lcm/{user}

relationships:

hosting_relationship: type: hosted_on

properties:

provider: provider y

agreement_type: free

params: {...}

security_relationship:

type: connected_to

properties:

provider: provider x

agreement_type: base level free

additional_security: additional fee for pro level params: {...}

networking_relationship:

type: connected_to

properties:

provider:

agreement_type: base level free

params: {...}

workflows:

scale_db:

url: {lcm_url}/workflows

description: "This is workflow for scalling db resources ..." spec: {url}/spec

parameters:

name: scale_db

instances: +2

params: {}

update_version:

url: {lcm_url}/workflows

description: "This is workflow for updating db version ..." spec:

parameters:

name: scale db version:

default: v1.1

constraints:

- in_range: [0.8, 1.1]

params: {}

updatejocation:

url: {lcm_url}/workflows

description: "This is workflow for updating active locations ..." spec: {url}/spec

parameters:

name: updatejocation

location:

default: zone A

constraints:

- in_range: [A,C]

status: active

params: {}

reconfigure:

url: {lcm_url}/workflows

description: "This is workflow for db performance re-configuration ..." spec: {url}/spec

parameters:

name: reconfigure_performance

params: {}

# Router descriptions example

#=======================

# -

# Short smart tag

# - router_xtype_v3.3_locations_A_B_C

# Short abstracted description

#

# Note: the following description can also be shorter or

# a bit longer then in the example

# - router_xprovider

properties:

version: v3.3

capabilities:

endpoint:

type: datatypes. router.endpoint.XRouter

locations:

- zone A, segment 2

- zone B, area 1 ,2

- zone C, subarea x,c

links:

latency: 8s

throughput : 10 Gb/s

features: {...}

host:

type :”type-x"

latency: 2s

max_ports: 400

features : {...}

access:

type: router_port_range, lcmjnterface, monitoringjnterface requirements:

host:

capabilities:

min_cpus: 8

min mem: 8G min_storage: 40G

links:

zones: A,B,C

access:

type: router_port_range

security: account_credentials

# -

# Full description

#

# Can have some private information avilable only for contracted group.

# - inputs:

account_credentials:

username:

default: user

token:

default: token

number_of_ports:

default: 50

number_of_cpus:

default: 8

memory:

default: 8G

storage:

default: 40G

lcm_enabled:

default: false

monitoring_enabled:

default: false

pricingjnputs:

default: {}

router_xprovider properties:

version:

type: string

default: v3.3

constraints:

- in_range: [2.8, 3.3]

ports:

type: integer

default: 50

constraints:

- in_range: [50,2000]

capabilities:

endpoint:

type: datatypes. router.endpoint.XRouter locations:

- zone: zone A

area: segment 2

status: active

capabilities:

latency: 8

throughput : 10 Gb/s

distance: 100

traffic_price : 1€/Gb/month reliability: 0.9995

features : [”leased-line”]

- zone: zone B

area: B1 , B2

status: active

capabilities:

latency: 9

throughput : 8 Gb/s

distance: 70

traffic_price : 1.5€/Gb/month reliability: 0.9998 features : [”leased-line”]

- zone: zone C

area: subarea-Cx, subarea-Cz

status: active

capabilities:

latency: 10

throughput : 8 Gb/s

distance: 70

traffic_price : 1.5€/Gb/month

reliability: 0.9993

features : [”leased-line”] security_features: {...}

routing_protocols: {...}

performance:

transactions: 20000w/s

access:

type: router_port_range, lcmjnterface, monitoringjnterface

requirements:

host:

capabilities:

min_cpus: 2

min_mem: 4G

min_storage: 40G

num_cpus:

type: integer

default: 2

constraints:

- in_range: [2,100]

price_per_cpu: 2

memory:

type: datatype. mem. Types

default: 4G

constraints: - in_range: [4,200]

price_per_g: 2

storage:

type: datatype. mem. Types

default: 4G

constraints:

- in_range: [40,400]

price_per_g: 2

access:

type: router_port_range

security: account_credentials

interfaces:

router:

router_url: xprovider.com

enrolment jrl: xprovider.com/enrollment/{user} spec: xprovider.com/docs/router/spec/{user} lcm:

lcm_url: xprovider.com/apis/lcm/{user} spec: xprovider.com/docs/router/lcm/spec/{user} monitoring:

data_url: xprovider.com/apis/lcm/{user}

relationships:

hosting_relationship:

type: hosted_on

properties:

provider: provider y

agreement_type: free, leased-resources params: {...}

networking_relationship:

type: connected_to

properties:

provider: agreement_type: free, leased-lines

params: {...}

workflows:

update_version:

url: {lcm_url}/workflows

description: "This is workflow for updating router version ..." spec:

parameters:

name: update_version

version:

default: v3.3

constraints:

- in_range: [2.8, 3.3]

params: {}

updatejocation:

url: {lcm_url}/workflows

description: "This is workflow for updating active locations ..." spec: {url}/spec

parameters:

name: updatejocation

location:

default: zone A

constraints:

- in_range: [A,C]

status:

default: active

params: {}

configure:

url: {lcm_url}/workflows

description: "This is workflow for router configuration ..." spec: {url}/spec

parameters:

name: configure_performance params: {}

Abbreviation Explanation

AaaSApplication as a Service

BSS Business support system

CDM Cloud Deployment Model

ETSI European Telecommunications Standards Institute laaS Infrastructure as a Service

LCM Life-cycle management

MEF Metro Ethernet Forum

NFV Network Function Virtualization

NFVIaaS NFV Infrastructure as a Service

NGMN Next Generation Mobile Networks

ONAP Open Network Automation Platform

OSS Operations Support Systems

SCBaaS Smart Contract Blockchain as a Service SDN Software-Defined Networking

VNF Virtualized Network Function

VNFaaS VNF as a Service

XaaS ‘X’ as a Service