COMPOSITION

TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to the creation and deployment of services in a network containing network function virtualization infrastructure. Specifically, the disclosure relates to composition by the customer of network services from virtualized resources.

BACKGROUND

[0002] Cloud networks are becoming increasingly intelligent and programmable.

The networks utilize intelligent software systems and applications operating on general- purpose commodity hardware. That transformation decreases capital and operating expenses, while permitting configuration of the networks with less human intervention. At the same time, significant opportunities are created to scale and monetize existing and new intelligent services.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The present disclosure can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:

[0004] FIG. 1 is a block diagram showing a system for composing a network service. [0005] FIG. 2 is a block diagram showing two views of a composition example according to aspects of the present disclosure.

[0006] FIG. 3 is a screen view of a graphical user interface for composing a service according to aspects of the present disclosure.

[0007] FIG. 4 is a flow chart showing a method according to aspects of the present disclosure.

[0008] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

[0009] Web service composition is currently used to create a single Web application by utilizing a variety of different applications inside the single Web application. That is done by means of simple object access protocol (SOAP) APIs from each of the constituent applications. This ultimately has to do with service granularity - which indicates how much functionality a service exposes. A coarse grained service will expose a whole process as a consumable unit, whereas a fine grained service will expose a specific unit of logic from a larger process. Service architects determine what granularity of service works best for a given environment,

[0010] The presently described system enables cloud providers to establish a services ecosystem for facilitating mass marketing of existing and new network services. The system lowers barriers to entry for enterprise customers and small business customers to create new services. [0011] In general, the disclosed intelligent service collects information about resources (users, devices, networks and applications) used to deliver the service and information about the environment in which it operates. It then makes decisions based on that information and domain knowledge which includes adapting and personalizing the service for the users composing and consuming it. The intelligent service receives feedback on its performance and learns.

[0012] The services composition system achieves several important goals. It is a predictive personalized service in that it anticipates a user's needs and proactively takes intelligent actions and recommends valuable and timely personalized information. The system is additionally an adaptive system that learns from past actions of all users and adjusts its behavior to provide superior service quality. Finally, the services composition system is dynamic in that it is robust and is able to survive and self-repair or self-organize itself from possible service interruptions.

[0013] In certain embodiments of the present disclosure, a method is provided for composing a service in a communications network. A plurality of resource models is defined, each resource model describing a behavior of a virtualized network function resources in the communications network. A customer service creation request is received from a customer to create a new network service, the request including a functional description of the new network service. Based on an expert system learning algorithm trained using prior customer service creation requests, one or more of the virtualized network function resources are suggested to the customer for use in composing the new network service. An arrangement of icons is received from the customer via a graphical user interface. The arrangement of icons represents a subset of the virtualized network function resources, and includes representations of

interconnections among the virtualized network function resources. Based on the arrangement of icons and on the behaviors of the subset of the virtualized network function resources, the arrangement of icons is validated as representing a feasible service composition for deployment in the communications network. The service composition is deployed in the communications network for use by the customer.

[0014] In additional embodiments, a computer-readable storage device is provided having stored thereon computer readable instructions for composing a service in a communications network. Execution of the computer readable instructions by a processor causes the processor to perform operations including those described above.

[0015] In another embodiment, a system is provided for composing a service in a communications network. The system comprises a processor resource, an interface connecting the processor resource, and a computer-readable storage device having stored thereon computer readable instructions.

[0016] Execution of the computer readable instructions by the processor resource causes the processor resource to perform operations including those described above.

[0017] The presently disclosed autonomous services composition system 100

(FIG. 1) is an example of an intelligent service. The system 100 creates a ^' services marketplace' that provides a holistic customer experience to create novel services by leveraging advanced tools like recommenders 102 and expert systems and predictors 106, real time customer care collaboration, custom pricing 108 and big data analytics 104. The service composition system includes a mechanism for integrating

applications/services from predefined component modules or resources 110, linking those modules and deploying them where and when they are needed. It is that service linking capability that provides the basic mechanism for defining new applications, managing application lifecycles and implementing elastic services in the composition environment. By rapidly integrating components and sizing those components dynamically, applications can be built to handle varying user loads. By selectively deploying component modules based upon affinity rules, multiple time-critical functions can be directed to share common infrastructure to minimize latency, while high availability can be maintained by directing redundant components to execute on geographically separated servers.

[0018] The presently described services marketplace allows customers, partners, developers, and others to interface and interact with each other and with a broad array of tools, including analytic engines, data, predictive and recommendation tools,

collaboration. The interaction is highly flexible and easily configurable, allowing users to discover, create, simulate, deploy, monitor, and otherwise bring to realization service constructs assembled from service primitives. Those services can range from a straightforward service drawn without change directly and immediately from a catalog to unique and complex service creations resulting from the collaboration of customers, partners, developers and others, and possibly spanning years of joint efforts.

[0019] A model driven approach is used at the heart of the services marketplace to facilitate the creation and management of dynamic service compositions. The approach entails separation of the fundamental composition logic from composition specifications. Because network services are increasingly provided using network function virtualized (NFV) resources, there is a need to model those resources appropriately to facilitate higher layer applications to provide value-added services, such as the disclosed composition environment.

[0020] As shown in FIG. 1, the presently disclosed autonomous services composition system utilizes models of resources 110, services 111 and products 113. Resources can be concatenated to build services. Services can be ordered together with business policies and pricing to form end products. Composition is facilitated by leveraging relationships between services and products to create a final product that entails features from its constituent services/products. Industry standards are used to model the FVs. For example, embodiments utilize the OASIS Topology and

Orchestration Specification for Cloud Applications (TOSCA) modelling specification.

[0021] A product 113 is composed from its constituent virtualized resources 110.

A model is provided for describing each resource. Note that a network function virtualization can be modeled into a default set of features, with an optional set of alternative add-on features.

[0022] A composition example 200, shown in FIG. 2, demonstrates the composition of two products: a network-on-demand product and a managed Internet service product. The managed Internet service product provides Internet connectivity to enterprise customers. At the customer view 210, this is shown as a site office with a customer premises equipment (CPE) 211 connected by a link node 212 to an Internet gateway 220. Drilling down one more level shows a services view 240 including the various possibilities that the customer or network provider operations personnel can see. The link node 212 is further described in terms of an access link, namely the CPE 211 to a point of presence (POP) link 216 via a link node 215, and from the POP 216 to an Internet gateway 220 via a multiprotocol label switching (MPLS) link 217. The access links can come in many varieties, one of which is defined as network-on-demand using virtualized routers. Each of those entities must be modeled in a generic way to allow different levels of service granularity. For example, the CPE has certain characteristics like bandwidth, number of ports, grade of service, etc.

[0023] The disclosed services composition system utilizes an ecosystem populated with an array of NFV models that facilitate interlinking or combining to provide a richer set of value added services. Combining products and services in unique ways that have not been thought of provides opportunities that can be monetized and meet customer needs more holistically. An additional benefit of this is that the process can be self-propelled where vendors and partners are incented to contribute various NFV models using well known standards, such as the OASIS TOSCA modelling language.

[0024] An exemplary graphical user interface 300 for accessing such an ecosystem is shown in FIG. 3. In a widget box 340, the user is provided with models of VNFs that may be selected for representation in a drawing area 310. Upon selection of a particular widget, the user specifies characteristics that are then implemented in the model. For example, a widget 341 representing a site-to-site connection with two end points may be selected. The user specifies characteristics for the connection, including a 100 Mbps bandwidth and endpoints A and B. A representation 342 of the connection is then created in the drawing area.

[0025] The composed service represented in the drawing area 310 may be simulated and tested using the underlying models of the selected V Fs and the specified interconnections. The simulation and testing may be performed either in real time during composition or in response to a discrete request by the customer.

[0026] In another example use case of the described composition system, a set of basic services is requested by a customer: a) data connectivity between two endpoints (e.g. a switched Ethernet service), b) a data ^λ splitter' service that takes data from an endpoint and sends it to two or more endpoints, c) a video anomaly detection service that takes a video stream and sends alarms to an endpoint, and d) a data archiving service. In this example, a small-town bank with a video surveillance camera in the lobby wants to send that video stream to a home office while away from the bank. In the presently disclosed composition environment, the basic connectivity service is configured with the endpoint locations. The customer requires that alerts additionally be sent when something unexpected happens. In the example, that feature can be composed by taking the video output from the data splitter service and piping it into the anomaly detection service. The anomaly detection service is configured to send alerts out. There may also be a need to store the video for six months, in addition receiving the alerts. In each of those cases, the composition environment creates the individual service orders for the basic services, and creates the overall application control that shows how the basic services are stitched together. [0027] The disclosed composition environment uses items from the resource catalog 110, service catalog 111 and product catalog 113, shown in FIG. 1. Each of those network function virtualization (NFV) elements must be modeled before composition can be realized. That modeling may be done by the network provider, by a virtual network function developer or by a third party supplier. In embodiments, an extended version of the TOSCA modeling language is used to model those products. The use of that open source modeling language facilitates rapid service composition in a manner that is verifiable at different stages of the software lifecycle.

[0028] The starting point of composition may be a catalog of third party NFVs.

In embodiments, an ecosystem is created by the network provider for bootstrapping network provider vendors to populate the resource and service catalogs using TOSCA.

[0029] The architectural approach adopted for the presently disclosed

composition environment enables rapid iterative development, an elastic scaling path as utilization grows, and flexibility in terms of evolving requirements and addition of new functionality. The subsystems are designed around a microservice architecture, in which components interoperate via a lightweight distributed message bus. In embodiments, Vert.x™, an open source tool-kit for building reactive applications on the Java® virtual machine platform, is used. The carefully abstracted messaging publish/subscribe interface facilitates extensibility. For example, semantic assistants may be added from the intelligent toolbox. Finally, the cloud-based composition environment cluster can easily scale horizontally to meet elastic demand; subsystem replicas can be deployed in seconds on lightweight containers as utilization requires. [0030] Composition is ultimately a complex data-driven process, using not only an extensive product catalog and asset inventory, but also representations of the domain expertise that goes into building complex composite services. Embodiments of the presently disclosed composition environment use graph database technology to allow natural ways to represent the semantic connections among catalog and inventory items, workflow state, and related domain knowledge. The database is dynamically extensible to accommodate learning throughout the lifecycle, and is continuously available to intelligent agents overseeing and augmenting the composition process.

[0031] The disclosed composition environment must execute the composed order in a FV environment such as AT&T's Domain 2.0 network environment. A ^λ shopping cart' like experience is created, allowing the end customer to discover, create, deploy and watch the service. The composition environment must interoperate with a service design and creation (SD&C) subsystem 150 to fulfil the order. The composition environment also communicates with a range of entities in the NFV environment to monitor the service and present real-time reports in a dashboard using analytics and visualization tools. For example, the composition environment may communicate with various components of an enhanced, control, orchestration, management, policy (ECOMP™) system 160, an AT&T system, including the data collection, analytics, and event (DCAE) engine 161 and active & available inventory (A&AI) subsystem 162 for real-time asset information.

[0032] A natural part of the composition process is to allow the customer to discover services and products that are related. An expert system is needed to suggest or recommend compatible products to guide successful compositions. Another key feature of the disclosed composition environment is designing for collaboration; given that composition is a complex activity often involving many participants, the composition environment has been designed to be a collaborative workspace from the start.

Specifically, a customer may interact with the network provider personnel or third party equipment provider personnel in real time during the composition process, using an interface provided for that purpose. That collaborative arrangement provides for network provider input and other vendor input during the composition process.

[0033] An additional aspect of composition of FV services is the complexity and richness of the workflow. The disclosed composition environment seeks to provide seamless support of the entire composition lifecycle. To make the environment maximally accessible, the user interface is entirely browser-based, leveraging HTML5 technologies like WebGL and WebRTC to enable a powerful and effective user experience. Finally, a Web RTC-based collaboration environment has been provided for customer care needs.

[0034] The border between applications and network functions is becoming blurred in many cases. There are simple V Fs like vRouters (Vyatta ^® from Brocade Communications Systems Inc. and CRS ^® from Cisco Systems Inc., for example).

Beyond that, there are domain name system (DNS) services, lightweight directory access protocol (LDAP) services and a like services which are more application-oriented services. New records must be added when a new tenant is provisioned, which is an application action. [0035] More complex VNFs come with their own databases or rely on an open source relational or non-relational (noSQL) database like Cassandra™, for example. The complex VNFs or chains of VNFs like a CDN subsystem or IMS and EPC subsystems require deep orchestration capabilities, creation orders, network dependencies, relationships and complex actions to be performed.

[0036] Autonomous service composition can be facilitated at various layers of the

OSI stack. In the examples set forth in the present disclosure, it is used to improve the overall end customer experience by addressing from very simple scenarios to complex VFN chaining.

[0037] An example method 400 for composing a service in a communication system is depicted by the flow chart of FIG. 4. A plurality of resource models is initially defined at block 410. Each resource model describes a behavior of a virtualized network function resource in the communications network. The resource models may, for example, be created by network provider vendors and partners, who may have an interest in the service composing system. The models may be created using well known standards such as the TOSCA modelling language.

[0038] A customer service creation request to create a new network service is received from a customer at block 420. The request includes a functional description of the new network service. In embodiments, the request may specify the relevant nodes, the types of connections, and the functions to be performed.

[0039] The system then suggests to the customer, at block 430, one or more of the modeled virtualized network function resources for use in composing the new network service. The suggestion is based on an analysis of the functional description the new network service by an expert system learning algorithm that has been trained using prior customer service creation requests.

[0040] The customer then defines an arrangement of icons representing a subset of the virtualized network function resources, which is received from the customer via a graphical user interface at block 440. The arrangement of icons includes representations of interconnections among the virtualized network function resources. The customer may use the graphical user interface to graphically define the interconnections. The service composition system may assist the customer in arranging the icons using expert system learning algorithm.

[0041] Based on the arrangement of icons and on the behaviors of the subset of the virtualized network function resources, the arrangement of icons is validated at block 450 as representing a feasible service composition for deployment in the communications network. The service composition is then deployed at block 460 in the communications network for use by the customer.

[0042] The hardware and the various network elements discussed above comprise one or more processors, together with input/output capability and computer readable storage devices having computer readable instructions stored thereon that, when executed by the processors, cause the processors to perform various operations. The processors may be dedicated processors, or may be mainframe computers, desktop or laptop computers or any other device or group of devices capable of processing data. The processors are configured using software according to the present disclosure. [0043] Each of the hardware elements also includes memory that functions as a data memory that stores data used during execution of programs in the processors, and is also used as a program work area. The memory may also function as a program memory for storing a program executed in the processors. The program may reside on any tangible, non-volatile computer-readable storage device as computer readable instructions stored thereon for execution by the processor to perform the operations.

[0044] Generally, the processors are configured with program modules that include routines, objects, components, data structures and the like that perform particular tasks or implement particular abstract data types. The term "program" as used herein may connote a single program module or multiple program modules acting in concert. The disclosure may be implemented on a variety of types of computers, including personal computers (PCs), hand-held devices, multi-processor systems, microprocessor- based programmable consumer electronics, network PCs, mini-computers, mainframe computers and the like, and may employ a distributed computing environment, where tasks are performed by remote processing devices that are linked through a

communications network. In a distributed computing environment, modules may be located in both local and remote memory storage devices.

[0045] An exemplary processing module for implementing the methodology above may be stored in a separate memory that is read into a main memory of a processor or a plurality of processors from a computer readable storage device such as a ROM or other type of hard magnetic drive, optical storage, tape or flash memory. In the case of a program stored in a memory media, execution of sequences of instructions in the module causes the processor to perform the process operations described herein. The

embodiments of the present disclosure are not limited to any specific combination of hardware and software.

[0046] The term "computer-readable medium" as employed herein refers to a tangible, non-transitory machine-encoded medium that provides or participates in providing instructions to one or more processors. For example, a computer-readable medium may be one or more optical or magnetic memory disks, flash drives and cards, a read-only memory or a random access memory such as a DRAM, which typically constitutes the main memory. The terms "tangible media" and "non-transitory media" each exclude transitory signals such as propagated signals, which are not tangible and are not non-transitory. Cached information is considered to be stored on a computer- readable medium. Common expedients of computer-readable media are well-known in the art and need not be described in detail here.

[0047] The forgoing detailed description is to be understood as being in every respect illustrative and exemplary, but not restrictive, and the scope of the disclosure herein is not to be determined from the description, but rather from the claims as interpreted according to the full breadth permitted by the patent laws. Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of "including,"

"comprising," or "having" and variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. Unless specified or limited otherwise, the terms "mounted," "connected," "supported," and "coupled" and variations thereof are used broadly and encompass direct and indirect mountings, connections, supports, and couplings. Further, ''connected" and "coupled" are not restricted to physical or mechanical connections or couplings. It is to be understood that various modifications will be implemented by those skilled in the art, without departing from the scope and spirit of the disclosure.