US20150012652A1 - Method and Apparatus for Open Management of Multi-Media Services - Google Patents
Method and Apparatus for Open Management of Multi-Media Services Download PDFInfo
- Publication number
- US20150012652A1 US20150012652A1 US14/493,761 US201414493761A US2015012652A1 US 20150012652 A1 US20150012652 A1 US 20150012652A1 US 201414493761 A US201414493761 A US 201414493761A US 2015012652 A1 US2015012652 A1 US 2015012652A1
- Authority
- US
- United States
- Prior art keywords
- service
- management
- services
- registry
- portal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G06F17/30557—
-
- G06F17/30867—
-
- G06F17/30964—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- H04W4/003—
Definitions
- a client-subscriber may subscribe to any of the services published in the commercial services repository 66 .
- the commercial services repository 66 stores a template/definition for each service offered.
- the template outlines the basic structure of the service, and an operator may personalize the service depending upon the subscriber needs (for example by adding trigger-based events or actions as will be described in more detail below). It is also important to note that a subscriber may also personalize aspects of a service by provisioning the subscriber-profile preferences component.
- the resulting personalized service is referred to hereinafter as an activation of the service.
- the subscriber invocation of an activated service generates an ‘instance’ of the Service or SC.
- Each Service/SC instance has a life cycle.
- SLA Service Level Agreement
- An SP could use an SLA to satisfy many purposes, including to find a trusted SP, capable of providing a service with the given SLA, to monitor a service for its compliance with the expected SLA and to take corrective actions, based on real-time deltas, or to analyze real-time SLA trends, taking into account historical trends, and to enable architecture planning decisions.
Abstract
An architecture which permits externalized management of services includes a number of management service capability (MSC) definitions. Each operator may associate a management service capability with a Service/Service Capability for managing various aspects of the Service/Service Capability. An interface enables a variety of different management systems to utilize a common MSC structure, independent of the information models, transport mechanisms and management interface of the system using the MSC. With such an arrangement, management related integration costs associated with integrating and bundling complex multi-media services is significantly reduced.
Description
- This application is a continuation of U.S. patent application Ser. No. 10/944,565 filed Sep. 17, 2004, which claims priority under 35 U.S.C. §1.119(e) to U.S. Provisional Patent Application No. 60/549,505 filed Mar. 2, 2004.
- This invention relates generally to the field of services and more particularly to a method and apparatus for externalizing management service capabilities in a services oriented architecture (SOA).
- Multi-telecom supporting domains such as Optical, Switching, Wireless, and Voice and data over IP depend upon a set of different information models, protocols and interfaces for their management. As a consequence, Carriers, Service Providers (SPs) and Large Enterprises incur high ‘integration taxes’ and operation expenses (OpEx) to create, update, validate, integrate, deploy, activate and maintain the management interfaces, protocols and information models. For example, present day management of connectivity functionality is partially supported through the use of multi-proprietary and conventional management Application Programming Interfaces (APIs), protocols and information models, such as Simple Network Management Protocol (SNMP), TeleManagement Forum (TMF) 814, etc. The multi-entry management points associated with the APIs may compromise the integrity, maintainability and effectiveness of the management solution.
- The complexity of such a system further frustrates the ability of the system to provide rapid integration and management of end to end services. In addition, it is difficult to perform fast and reliable service deployment, delivery and activation as well as fast service restoration and recovery, and effective and reliable problem notification mechanisms in such a system. As the number and complexity of service offerings continues to increase, the problem of providing reliable and robust service delivery and service management increases.
- According to one aspect of the invention, a system includes a database management system (referred herein as database) comprising of management service capability (MSC) templates/definitions/descriptions. A registry is coupled to the database for tracking instances of MSCs, whose object-oriented representations are stored in the database. A portal is provided for interfacing a services operator to the registry. A cluster server is provided for executing instances of MSCs, and a gateway is coupled with the portal and the server, the gateway having an API enabling direct interaction between the operator and instances of MSCs.
- According to another aspect of the invention, a method for operator management of a service provided in a network including the steps of selecting a management service capability from among a set of management service capabilities defined in a database, personalizing the management service capability (SC) according to needs of the subscriber, generating a management service capability instance and associating it to a subscribed Service/SC ; and executing the management service capability instance to manage the lifecycle of associated service/service capability instances.
-
FIG. 1 is a block diagram of an exemplary service management externalization architecture in which the present invention may be implemented; -
FIG. 2 is a block diagram provided for illustrating a variety of exemplary components that may be included in registries and repositories of the aggregated service oriented architecture ofFIG. 1 ; -
FIG. 3 is a flow diagram provided to illustrate several exemplary steps that may be performed when associating a management service capability with a Service/Service Capability; and -
FIG. 4 is a logical embodiment of a service architecture in which the present invention may be used. - Referring now to
FIG. 1 , a managementservice externalization architecture 10 in which the present invention may be used, includes afunctional component 20 which is used to control the delivery and deployment of one or more services or SCs to one or more registries, SEs, and NEs.Information content 30 is a repository of information records, resource models and operation models that are related to the services.Information delivery 40 includes a variety of protocols that may be used to deliver the information content to thefunctional components 20. Several embodiments of a service architecture such as that shown inFIG. 1 are described in co-pending patent application Ser. No. ______ filed ______, attorney docket number 120-442, by Fiszman et al, entitled “METHOD AND APPARATUS FOR ENABLING DYNAMIC SELF-HEALING OF MULTI-MEDIA SERVICES,” (hereinafter Fiszman) incorporated herein by reference. - The Service Operations Center (SOC) of
FIG. 1 is designed using an efficient, robust and low cost architecture which enables a variety of heterogeneous services from various different service providers to be made available to subscribers. For the purposes of this application, a ‘service’ is an aggregation of service capabilities, communication & non-communication services, and logic (i.e., control) that is self-managed as an autonomous unit and delivered with a service level agreement to a consumer (i.e., the subscriber who pays for the service, and the associated end-users, who request/consume/invoke the service). A service has an interface with a set of externalized representations and bindings to a set of programming languages (e.g., Java, C++, and C), and protocols (e.g. SOAP, SIP) with different transport bindings. - One or more service capabilities may be associated with a service. For the purposes of this application, a ‘service capability’ is a function provided by an entity (a Service Element (SE) or Network Element (NE)) which implements a discrete set of functions in a service provider's network. Zero or more of these functions may be inter-worked to enable the development, execution and management of services. A ‘service capability instance’ is an active instantiation of a Service Capability, which has been deployed and activated within a service provider's network.
- A Service Level Objective (SLO) maps to a set of performance measurements across a set of Service Capabilities or Services and associated instances. A Service Level Agreement (SLA) is an agreement, executed by or with a Service Provider (SP), defining a selected set of SLOs. Thus, a Service represents an entity consumed by subscribers and managed by the Service Operations Center (SOC).
- As mentioned above, the
functional component 20 is used to manage services delivered to the consumer, and may be implemented in hardware, software, or a combination thereof.Functional component 20 includes aportal 12, which allows Service Operations Center (SOC) operators to update and retrieve the information stored in theInformation Content 30, as well as providing access to different Services, SCs, andMSCs 18. In one embodiment of the invention, the portal has a generic Application Programming Interface (API) which permits operators using various different protocols for managing services across boundaries (e.g., among different Service Providers). The portal may be accessed by, for example, Operational Support Systems (OSS), Business Support Systems (BSS) and Network Managements Systems (NMS), as well as being an interface for Operations/IT personnel (i.e. operators) whom execute externalized management operations. - The functional components also include WSDL and ebXML Universal Description Discovery and Integration (UDDI) based
registries 14. The WSDL and ebXMLUDDI registries 14 include Service/Service capability descriptions and binding templates, for linking services to the subscribers. The W3C/OASIS standards include a number of Service Definitions which define services available to the subscriber. According to one aspect of the present invention, it is proposed to augment the W3C/OASIS standard Service Definition offerings to include a number of Management Service Definitions, each to be associated with a service available to a subscriber. The Management Service Definitions may define management functionality associated with, for example, Service Level Agreement (SLA) and Quality of Experience (QoE) operations, fulfillment operations (including commissioning, provisioning, and activation operations as well as invocations of TeleManagement Forum (TMF)-based management processes published in ebXML registries), billing and charging related operations, service validation operations, service life cycle operations (including service deployment, service activation, status change and notifications), as well as Information Content access operations. - An Open Service Access (OSA)/Parlay/ParlayX Service Capability Gateway 16 provides access to a Service Capability entity or to a Service Capability naming facility, such as a Service Capability Registry (SCR). According to one aspect of the invention, the OSA/Parlay gateway also provides access to Management Services Capabilities (MSCs) provided in the system. Each MSC instance is an instantiation of a management service capability associated with a service/SC instance consumed by a subscriber. The MSC can be directly accessed by an operator via the portal, thereby externalizing the operations used to manage any one of a variety of aspects of the services. For example, an MSC can be used to manage OSA/Parlay SCs (e.g., Presence, Availability, Session-Control aspects) for a subscriber. As will be described later herein, externalizing management service capabilities effectively abstracts the complexity of existing services' north bound interfaces to OSS, BSS, and NMS by providing a simple generic point of entry for all aspects of service management. With such an arrangement, service automation may be performed in a cost effective manner. As will be described in more detail below, one advantage of providing management services in this manner is that it permits externalization of an SLA framework within Service Management.
-
Functional components 20 also includemanagement Agent component 21. As described in detail in Fiszman et al., Management Agent (MA)component 21 includes a hierarchy of cooperating Management Agents (MAs). The hierarchy of cooperating MAs uses common information models and protocols to automate service assurance, restoration and recovery, while facilitating integration of heterogeneous and multi-sourced services. The MAs are used by Service or Service Capability Instances to monitor SLA and QoE (Quality of Experience) compliance and to perform actions when SLA violations or Service/SC failures occur. The hierarchical nature of the MAs also facilitate scaling and an extensible management architecture, thereby significantly reducing the TCO and OpEx for Carriers, Service Providers, and Large Enterprises. - In accordance with one aspect of the invention, the Management Agents fulfill and monitor the Services/SCs and associated instances, detect alarms and performance degradations. An MA may, for example, interact with a Management Services Capability (MSC) that is responsible for the fulfillment and assurance of service level objectives defined in a subscriber's SLA with an SP. An example of a Management Service Capability (MSC) and MA interaction will be described later herein.
- According to one embodiment of the invention,
functional component 20 also includes aLife Cycle Manger 22. TheLife Cycle Manager 22 is responsible for posting and removing the service definitions and extensions to the appropriate Web-based registries. In addition, according to one aspect of the invention, the Life Cycle Manager is also responsible for the installation, commissioning, configuration and activation of Management Service Capabilities, as well as posting them in the Web-based registries. - As mentioned above, the service
management externalization architecture 10 also includesinformation content 30 which is accessible by any of the SCs and associated instances, including the MSC and associated instances. Making the information content available via a Management Service Capability effectively externalizes the information content, making it directly available to the operator. Certain information content that would be advantageously externalized and made available to the MSC/operator includes information records 32 related to service instances behavior (e.g., fault, subscribed and measured SLA & SLO, and billing) information, information models associated with subscribers, SLA & SLOs, Service and Service capability aggregation hierarchies, including service topology and supporting network, logical and physical topologies. In addition, the architecture permits a set ofoperation models 36 to be invoked, using protocols and transports identified in theInformation Delivery domain 40. The operations could be used to access information records, information models and workflows that invoke the accounting, fault, performance, configuration, restoration and recovery operations. - Referring now to
FIG. 2 , an exemplary embodiment of the services architecture ofFIG. 1 is shown. A Service Operations Center (SOC) 20 is shown to include portal 12, which provides access to the SOC by a variety of client agents 50 a-50 d, each of which may use a variety of services including management services of the present invention. The clients may communicate with the portal 12 using any one of variety of protocols, including Simple Object Access Protocol (SOAP), Session Initiated Protocol (SIP), or other protocols known in the art. - A client-subscriber may subscribe to any of the services published in the
commercial services repository 66. In general, thecommercial services repository 66 stores a template/definition for each service offered. The template outlines the basic structure of the service, and an operator may personalize the service depending upon the subscriber needs (for example by adding trigger-based events or actions as will be described in more detail below). It is also important to note that a subscriber may also personalize aspects of a service by provisioning the subscriber-profile preferences component. The resulting personalized service is referred to hereinafter as an activation of the service. The subscriber invocation of an activated service generates an ‘instance’ of the Service or SC. Each Service/SC instance has a life cycle. TheLife Cycle manager 64 registers the Service/SC with the UDDI or ebXML registries. An entry in the UDDI registry includes, for each Service/SC, a Service/SC description, a binding template (indicating the service endpoints) and Uniform Resource Locators (URLs) associated with the services. Each UDDI entry has a UDDI key which maps a service definition logical identifier to the Service/SC. The Portal provides logical to physical mapping for the Service/SC instances, including the related MSC instances responsible for managing the Service/SC instances' life-cycles. - The portal 12 communicates with
Externalization servers 70 either directly (using SOAP messaging, or alternatively via an Application Programming Interface (API) to agateway 80. In one embodiment, thegateway 80 operates using the OSA/Parlay API & protocols, although this is not a requirement of the invention and other API & protocols may be readily substituted herein. - Thus the API gateway includes logic for communicating with one or more servers shown as
block 70 inFIG. 2 as a group of Externalization Servers (ES). Each Externalization Server supports Services/Service Capabilities provided under different protocols and technologies. For example, the Externalization servers (i.e.,J2EE Web Server 72, aJ2SE Server 74, and a C++ server 76) support Web Service (WS) APIs, Parlay-X APIs, and OSA south-bound APIs. - According to one embodiment of the invention, any of the
externalization servers 70 relays requests/responses to the gateway's Management Service Capability (MSC). A MSC may be represented as an object having associated therewith a variety of functions/methods and attributes/structure. One example of an object oriented model which may be used to represent a MSC and associated instances in the Content Repository is a Common Information Model (CIM), developed by the Distributed Management Task Force (DMTF). CIM is one standard for the exchange of management information in a platform-independent and technology-neutral way, streamlining integration and reducing costs by enabling end-to-end multi-vendor interoperability in management systems. The CIM also includes a number of standard models (data schema) for Systems, Applications, Networks and Device and other components, expressed in ‘mof’ language. This standardization enables applications from different developers on different platforms to describe management data in a standard way so that it may be shared among a variety of management applications. A compiler, which acts as a WBEM client compiles the mof code, and loads it into a WBEM server. The compiler may produce other output, including skeleton code for providers and user documentation. - One version of the CIM is provided by the Web-Based Enterprise Management (WBEM) standard. WBEM is a set of management and Internet standard technologies developed to unify the management of enterprise computing environments. The DMTF has developed a core set of standards that make up WBEM, which includes the Common Information Model. Although the below description will describe an architecture which uses CIM-WBEM objects, the present invention is not limited to any particular type of object format, and thus any other object oriented model (such as TMF SID) may alternatively be substituted herein.
- In an embodiment where the CIM-WBEM objects are used to represent MSCs, a CIM modeling construct such as a CIM Service object may be used to model a Management Service or Management Service Capability as a subclass of it. Actions required to solve a service affecting problems could be modeled using the CIM_PolicySet (i.e., using events-conditions-actions).
- Each WBEM Server that implements an MSC may include the following components: a CIM Object Manager (CIMOM) broker, related providers and service capability recovery logic, forming a 2 layers hierarchy with other DMTF CIM WBEM-based management agents that run on SC hosts or Service Elements (SEs). The MSC providers (i.e., resource adaptors) can be implemented using the Java Connector Architecture (JCA). In such an arrangement an MSC would consist of a CIMOM broker, related providers and service capability recovery logic, forming a 2 layers hierarchy with other DMTF CIM WBEM-based management agents that run on SC hosts or Service Elements (SEs).
- As mentioned above, according to one aspect of the service architecture, a Service Element (e.g., an S-CSCF service element) hosts a number of service capability instances. A Service Capability instance performs specific actions to address a service request from a user, satisfy specific SLA performance requirements (for example, response time, setup time, packet loss), send an event to a local Management Agent to notify it of, for example, alarm events, state changes and configuration changes.
- The MSC may be provided to manage one or more hosted SCs (e.g., S-CSCF, Presence, Availability, and Mobility SCs and associated instances) and may also exchange information with sibling gateways, managed SCs, and upper Management Agents or systems (i.e., SLA-based Apps, NMSs, OSSs, BSSs). The interface to the MSC can be externalized using, for example, CORBA, SOAP and a set of transport bindings, including HTTP/HTTPS/SSL, RMI, JMS, IIOP. Alternatively, any other protocol which enables communication with a service may be substituted herein, and thus the present invention is not limited to a specific protocol.
- The
Service Operation Center 20 ofFIG. 2 operates generally as follows. A SP publishes one or more Services/Service Capability templates in theCommercial Services Repository 66. Subscriber/clients request accesses to the services, which are deployed by theLife Cycle Manager 64 using theregistries 60 and 62. Service/Service Capability instances for the subscriber are generated and executed by theExternalization servers Externalization Server 72. TheExternalization Server 72 may communicate directly with the Service/SC instances, associated MAs, via thegateway 80. In addition, direct access to the MSC is provided by to the operator viaportal 52. With such an architecture, management capabilities may be modularized and externalized, thereby providing a low cost, scalable, robust and reliable method of managing services from heterogeneous SPs. - Referring now to
FIG. 3 , an example of how an MSC may be used to control Services/SCs will be shown and described. In particular, an example of the externalization of Service Level Agreement (SLA) management will be described, although it will be appreciated that the below techniques may be easily applied to the management of other service characteristics, and the present invention is not limited merely to the externalization of SLA management. - As mentioned above, a Service Level Agreement (SLA) is a service contract between a service subscriber and a service provider, which defines the performance aspects to be guaranteed during the delivery and consumption of a service. In addition it defines ranges for subjective expectations of a service, such as Quality of Experience (QoE) which could be partially mapped to a set of related connectivity parameters and specific network elements used in delivering a service (e.g., types of Codecs, and service impacting parameters such as packet loss, response time, and so on).
- An SLA plays a fundamental information role in all the management operations to be externalized. The SLA associated with a service/service instance consists of 2 main parts: the expected (i.e., signed-in/agreed/binding technical) SLA that represents the objective and subjective performance metrics (QoE, QoS, BW, response time, packet loss, etc) and the real-time (dynamic) SLA that represents a snapshot of SLA compliance or deltas relative to the expected SLA.
- An SP could use an SLA to satisfy many purposes, including to find a trusted SP, capable of providing a service with the given SLA, to monitor a service for its compliance with the expected SLA and to take corrective actions, based on real-time deltas, or to analyze real-time SLA trends, taking into account historical trends, and to enable architecture planning decisions.
- An SLA definition could be modeled using 1st order (Boolean) logic to represent the set of conditions required to trigger actions (e.g., an event or to perform SLA related measurements during a specified period). For example, it should be possible to express any combination of conditions types to trigger an action, such as:
- IF ((cond1 AND cond2) OR (cond3 AND !cond4))
- AND (SC_y_congestion greaterThan x%) THEN action
- Typical conditions that may be used to trigger an action for SLA management may include performance parameter range conditions, performance threshold conditions, temporal conditions or cost related conditions.
- A triggered action could by any type of service response including execution of a specific task, the collection of data associated with a recognized condition, etc. For example typical actions that may be performed in response to a trigger include invoking externalized management operations captured in a WSDL representation, invoking specific management processes captured in a ebXML representation, searching a service capability, using a service capability naming facility, accessing a specific management information about a related service capability instance, invoking a function of a management service capability (MSC) hosted in a Parlay/OSA Gateway or by a lookup in a Service Capability Naming Facility, accessing the MSC and invoking a management function or sending an event (e.g., notification) to interested parties [where an event could be modeled, for example, leveraging the DMTF CIM Indications documented in DSP0107]. The above list is exemplary and not exhaustive, and it is appreciated that many other types of service responses are included within the scope of the present invention.
- An SLA definition could be stored as part of the
Content Information domain 30, shown inFIG. 1 (SLA Model 34). An MSC could access the SLA definition and instances associated with Service or SC instances as well as information about MAs associated with them. The MSC SLA management object could be modeled using the DMTF CIM or TMF SID-based specifications, as described above. - In addition to SLA management, the present invention provides a structure for external management of a variety of service aspects. For example the present invention may be used to query & navigate a service, its instances, and information models, including expected SLA, real-time SLA, and historical SLAs per service instance. SQL-like syntax could be used to implement the query paradigm. In addition, the present invention may be used to add filters to a query to narrow its response scope, Publish/Subscribe Event per service instance to perform assurance activities (e.g., monitor, measure, diagnosis, trigger restoration and recovery actions) and perform transactional fulfillment of Service and Service Capability to bind a subscriber to a given SLA, and to perform the required service provisioning, bulk-configuration and activation. In addition, MSCs may be used to store and retrieve information content of Services, SCs and instances, perform Set and Get operations on SCs and SEs, and discover the state of specific Service/SC and associated instances. In addition, the discussed operations could have a scope attribute to be able to state the domains to which they will apply, as well as the ability to state a transactional behavior option on or off. These operations could also be modeled and captured as part of the Information Content domain, and thereby be modularized and made available for use by a variety of heterogeneous SPs.
- One advantage of externalizing management in the above manner is that it enables reduction of the OpEx and TCO for Carriers, SPs and Large Enterprises by supporting a single point of entry and open API for Fulfillment, Assurance and Billing, as well as enabling open API integration with NMS, OSS and BSS. In essence, management functions are modularized, enabling the core structure of the management service to be used by many applications, independent of the interface, protocol, transport mechanism or information models associated with the applications using the management service.
- Referring now to
FIG. 3 , a flow diagram illustrating exemplary steps that may be performed to build an externalized MSC using the present invention is shown. Atstep 80, the operator selects one of the management services in the Commercial Services Repository 66 (FIG. 2 ). The management services may include SLA and QoE assurance management operations, fulfillment operations, billing and charging related operations, service validation operations, service Life Cycle operations, and Information content access operations, and other similar services. The MSC is added to theWeb Registry 14, and an MSC object is built in the Content Repository. As mentioned above, the MSC object could be implemented based on the DMTF CIM WBEM paradigm. Atstep 82 the SP defines the scope and attributes of the MSC object, for example by identifying selected events, conditions, thresholds, actions, etc. for the management function. The selected events, actions, etc., may be used to control the hierarchy of Management Agents associated with the MSC. The MSC object executes, atstep 84, for the Life Cycle of the associated Service/SC. - Referring now to
FIG. 4 , an alternative embodiment of the present invention illustrates a logical block diagram of a Services Operations Center (SOC) is provided for the purposes of illustrating one method of providing open management in a service environment. AService Provider 100 may host one ormore operators 104. Each of the operators may use the Web registries to access Services/Service Capabilities, including Management Service Capabilities. Logical addresses from the SP are translated into physical addresses in theWeb Registries 140. - A
Carrier 120, stores a variety of services, including management services. For example, the carrier may store SLA management service such asSLA App 124. As mentioned above thegateway 160 provides an interface between the SP and the various Service/SC, MSC and associated instances. According to one aspect of the invention, the Gateway may include a MSC API which interfaces the SP to Management Service Capabilities. Shown logically positioned between thegateway 160 and theservice instances Resource Adaptors 162. In one embodiment, the Resource Adaptors are used to link Information Content to the Service/SC/MSC and instances. A Service Capability Register (SCR) 150 provides a direct interface between the various management applications (e.g., NMS, OSS, BSS) and the associated MSCs. Such an arrangement enables open management of Services, through the externalization of management services available in Web Registries, an MSC OSA/Parlay API, and a SCR. - Accordingly, an architecture which enables the externalization of management services for use by a variety of heterogeneous service applications is provided. Such an arrangement provides a number of benefits to carriers and SPs, including the ability to enable effective service management with reduced OpEx and TCO, rapidly integrate and manage end to end services and to deploy, deliver, and activate services in a reliable manner. The result is a low cost, robust and reliable service offering environment, which can be easily scaled to support a variety of heterogeneous service offerings.
- The above description and figures have included various process steps and components that are illustrative of operations that are performed by the present invention. However, although certain components and steps have been described, it is understood that the descriptions are representative only, other functional delineations or additional steps and components can be added by one of skill in the art, and thus the present invention should not be limited to the specific embodiments disclosed. In addition it is understood that the various representational elements may be implemented in hardware, software or a combination thereof.
- While the invention is described through the above exemplary embodiments, it will be understood by those of ordinary skill in the art that modification to and variation of the illustrated embodiments may be made without departing from the inventive concepts herein disclosed. Accordingly, the invention should not be viewed as limited except by the scope and spirit of the appended claims.
Claims (23)
1. A system for managing services provided by a communication network, the system comprising:
at least one database configured to maintain information defining a plurality of service capabilities, each service capability being associated with a respective protocol, at least some of the service capabilities being user service capabilities which can be used in combination to provide user service instances for providing services to users of the communication network, and at least some of the service capabilities being management service capabilities which can be used in combination to provide a management service instances for management of the user services;
at least one registry coupled to the database and configured for tracking the service instances;
at least one portal coupled to the at least one registry and configured for interfacing at least one operator to the at least one registry;
at least one externalization server coupled to the at least one portal and configured for executing the service instances; and
at least one application programming interface (API) coupled to the at least one portal and the at least one externalization server, the API being configured to enable access to service instances executing on the at least one externalization server by at least one client coupled to the API via the at least one portal.
2. The system of claim 1 , wherein the API is configured to translate a plurality of respective protocols used by clients into respective protocols associated with respective service capabilities to be accessed by the respective clients.
3. The system of claim 2 , wherein respective clients are coupled to the communication network via the at least one portal and respective clients communicate with the at least one portal using the respective protocols.
4. The system of claim 3 , wherein respective clients are coupled to the at least one API via the at least one portal and respective clients communicate with the at least one API via the at least one portal using the respective protocols.
5. The system of claim 3 , wherein the at least one portal uses Simple Object Access Protocol (SOAP) messaging to communicate with the at least one externalization server.
6. The system of claim 1 , wherein the at least one portal is configured with logical to physical mappings for the service instances.
7. The system of claim 1 , wherein the at least one registry stores service descriptions and service capability descriptions.
8. The system of claim 1 , wherein the at least one registry stores binding templates associated with service instances.
9. The system of claim 1 , wherein the at least one registry stores Universal Resource Locators (URLs) associated with service instances.
10. The system of claim 1 , wherein the at least one registry comprises at least one (Universal Description Discovery and Integration (UDDI) registry.
11. The system of claim 1 , wherein the at least one registry comprises at least one electronic business Extensible Markup Language (ebXML) registry.
12. The system of claim 1 , wherein the at least one registry comprises at least one Web Services Description Language (WSDL) registry.
13. The system of claim 1 , comprising at least one life cycle manager configured to register services with the at least one registry based on service definitions obtained from the at least one database.
14. The system of claim 1 , wherein the at least one API is provided by at least one Open Service Access (OSA) Parlay gateway.
15. The system of claim 2 , wherein at least one management service capability uses a Distributed Management Task Force Common Information Model Web Based Enterprise Management (DMTF CIMWBEM) protocol.
16. The system of claim 1 wherein the management service capabilities comprise fulfillment service operations.
17. The system of claim 1 wherein the management service capabilities comprise assurance service operations.
18. The system of claim 1 wherein the management service capabilities comprise billing service operations.
19. The system of claim 1 wherein the management service capabilities comprise Service Level Agreement (SLA) compliance operations.
20. The system of claim 1 , wherein the management service capabilities comprise query operations configured for querying information content of the system.
21. The system of claim 1 , wherein the management service capabilities comprise filtering operations.
22. The system of claim 1 , wherein the management services comprise event subscription operations.
23. The system of claim 1 , wherein the management services comprise information retrieval capabilities.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/493,761 US20150012652A1 (en) | 2004-03-02 | 2014-09-23 | Method and Apparatus for Open Management of Multi-Media Services |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US54950504P | 2004-03-02 | 2004-03-02 | |
US10/944,565 US8862570B1 (en) | 2004-03-02 | 2004-09-17 | Method and apparatus for open management of multi-media services |
US14/493,761 US20150012652A1 (en) | 2004-03-02 | 2014-09-23 | Method and Apparatus for Open Management of Multi-Media Services |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/944,565 Continuation US8862570B1 (en) | 2004-03-02 | 2004-09-17 | Method and apparatus for open management of multi-media services |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150012652A1 true US20150012652A1 (en) | 2015-01-08 |
Family
ID=51661227
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/944,565 Expired - Fee Related US8862570B1 (en) | 2004-03-02 | 2004-09-17 | Method and apparatus for open management of multi-media services |
US14/493,761 Abandoned US20150012652A1 (en) | 2004-03-02 | 2014-09-23 | Method and Apparatus for Open Management of Multi-Media Services |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/944,565 Expired - Fee Related US8862570B1 (en) | 2004-03-02 | 2004-09-17 | Method and apparatus for open management of multi-media services |
Country Status (1)
Country | Link |
---|---|
US (2) | US8862570B1 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TW201511504A (en) * | 2013-06-11 | 2015-03-16 | Cyan Inc | Network management systems and methods |
US9900725B2 (en) * | 2015-07-29 | 2018-02-20 | Intel Corporation | Technologies for an automated application exchange in wireless networks |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020019886A1 (en) * | 2000-06-07 | 2002-02-14 | Sanghvi Ashvinkumar J. | Event consumers for an event management system |
US20030033379A1 (en) * | 2001-07-20 | 2003-02-13 | Lemur Networks | Intelligent central directory for soft configuration of IP services |
US20040236633A1 (en) * | 2003-05-05 | 2004-11-25 | Knauerhase Robert C. | Management and arbitration of mobile service discovery |
US20050044197A1 (en) * | 2003-08-18 | 2005-02-24 | Sun Microsystems.Inc. | Structured methodology and design patterns for web services |
US20070011322A1 (en) * | 2003-09-30 | 2007-01-11 | Corrado Moiso | Method and system for providing access to web services |
Family Cites Families (56)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2810171B2 (en) | 1989-12-18 | 1998-10-15 | 株式会社日立製作所 | Network system and network management method applying the same |
US5740357A (en) | 1990-04-26 | 1998-04-14 | Digital Equipment Corporation | Generic fault management of a computer system |
US5414812A (en) | 1992-03-27 | 1995-05-09 | International Business Machines Corporation | System for using object-oriented hierarchical representation to implement a configuration database for a layered computer network communications subsystem |
DE69410447T2 (en) | 1993-02-23 | 1998-10-08 | British Telecomm | EVENT CORRELATION |
EP0818103B1 (en) | 1995-03-30 | 2004-02-25 | Azure Solutions Limited | Detecting possible fraudulent communications usage |
JP3137009B2 (en) | 1996-10-25 | 2001-02-19 | 日本電気株式会社 | Network multi-tier management system |
US6012152A (en) | 1996-11-27 | 2000-01-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Software fault management system |
US5826239A (en) * | 1996-12-17 | 1998-10-20 | Hewlett-Packard Company | Distributed workflow resource management system and method |
US7515697B2 (en) | 1997-08-29 | 2009-04-07 | Arbinet-Thexchange, Inc. | Method and a system for settlement of trading accounts |
US6425005B1 (en) * | 1997-10-06 | 2002-07-23 | Mci Worldcom, Inc. | Method and apparatus for managing local resources at service nodes in an intelligent network |
US6170011B1 (en) | 1998-09-11 | 2001-01-02 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for determining and initiating interaction directionality within a multimedia communication center |
US6230312B1 (en) | 1998-10-02 | 2001-05-08 | Microsoft Corporation | Automatic detection of per-unit location constraints |
US6487665B1 (en) | 1998-11-30 | 2002-11-26 | Microsoft Corporation | Object security boundaries |
US6286031B1 (en) | 1999-01-21 | 2001-09-04 | Jerry Richard Waese | Scalable multimedia distribution method using client pull to retrieve objects in a client-specific multimedia list |
US6340977B1 (en) | 1999-05-07 | 2002-01-22 | Philip Lui | System and method for dynamic assistance in software applications using behavior and host application models |
US6584508B1 (en) | 1999-07-13 | 2003-06-24 | Networks Associates Technology, Inc. | Advanced data guard having independently wrapped components |
US6718486B1 (en) | 2000-01-26 | 2004-04-06 | David E. Lovejoy | Fault monitor for restarting failed instances of the fault monitor |
US6370573B1 (en) | 1999-08-31 | 2002-04-09 | Accenture Llp | System, method and article of manufacture for managing an environment of a development architecture framework |
US6813278B1 (en) | 1999-11-30 | 2004-11-02 | Accenture Llp | Process for submitting and handling a service request in a local service management system |
US6571285B1 (en) | 1999-12-23 | 2003-05-27 | Accenture Llp | Providing an integrated service assurance environment for a network |
US20010027470A1 (en) * | 2000-01-11 | 2001-10-04 | Friedemann Ulmer | System, method and computer program product for providing a remote support service |
US6845396B1 (en) | 2000-02-25 | 2005-01-18 | Navic Systems, Inc. | Method and system for content deployment and activation |
US6912532B2 (en) | 2000-05-22 | 2005-06-28 | Benjamin H. Andersen | Multi-level multiplexor system for networked browser |
US6922685B2 (en) * | 2000-05-22 | 2005-07-26 | Mci, Inc. | Method and system for managing partitioned data resources |
US7043160B1 (en) | 2000-08-28 | 2006-05-09 | Nortel Networks Limited | Method, system and signal for carrying overhead information in a transport network employing photonic switching nodes |
US6725048B2 (en) | 2000-09-22 | 2004-04-20 | Ericsson Inc. | Traffic congestion management when providing realtime information to service providers |
US6934756B2 (en) | 2000-11-01 | 2005-08-23 | International Business Machines Corporation | Conversational networking via transport, coding and control conversational protocols |
US20020068545A1 (en) | 2000-11-06 | 2002-06-06 | Johnson Oyama | Method and apparatus for coordinating charging for services provided in a multimedia session |
US7383191B1 (en) | 2000-11-28 | 2008-06-03 | International Business Machines Corporation | Method and system for predicting causes of network service outages using time domain correlation |
US7568001B2 (en) | 2001-01-30 | 2009-07-28 | Intervoice, Inc. | Escalated handling of non-realtime communications |
US7330717B2 (en) | 2001-02-23 | 2008-02-12 | Lucent Technologies Inc. | Rule-based system and method for managing the provisioning of user applications on limited-resource and/or wireless devices |
US6820055B2 (en) | 2001-04-26 | 2004-11-16 | Speche Communications | Systems and methods for automated audio transcription, translation, and transfer with text display software for manipulating the text |
US7007063B2 (en) | 2001-05-24 | 2006-02-28 | International Business Machines Corporation | Server side program interface to service logic execution environment |
US20030041139A1 (en) * | 2001-08-14 | 2003-02-27 | Smartpipes, Incorporated | Event management for a remote network policy management system |
US6823382B2 (en) | 2001-08-20 | 2004-11-23 | Altaworks Corporation | Monitoring and control engine for multi-tiered service-level management of distributed web-application servers |
DE10161064A1 (en) | 2001-12-12 | 2003-07-03 | Siemens Ag | System and method for communication between software applications, in particular MES applications |
US7099879B2 (en) | 2001-12-21 | 2006-08-29 | Hewlett-Packard Development Company, L.P. | Real-time monitoring of service performance through the use of relational database calculation clusters |
US7603469B2 (en) | 2002-01-15 | 2009-10-13 | International Business Machines Corporation | Provisioning aggregated services in a distributed computing environment |
US9087319B2 (en) | 2002-03-11 | 2015-07-21 | Oracle America, Inc. | System and method for designing, developing and implementing internet service provider architectures |
AU2003226128A1 (en) | 2002-03-27 | 2003-10-13 | First Virtual Communications | System and method for traversing firewalls with protocol communications |
US7221945B2 (en) | 2002-05-03 | 2007-05-22 | Leapstone Systems, Inc. | System and method for establishing and controlling access to network resources |
US7974295B2 (en) | 2002-07-16 | 2011-07-05 | Nokia Corporation | Optimized routing between communication networks |
JP4013701B2 (en) | 2002-08-28 | 2007-11-28 | 日本電気株式会社 | Mobile communication system, operation control method thereof, node used therefor, and radio control apparatus |
BR0304946A (en) * | 2002-10-16 | 2004-08-31 | Xerox Corp | Method and apparatus to enable distributed subscription services, automated maintenance of supplies, implementation of device-independent service, including device model agent, add-on component, method and apparatus for low-cost embedded platform for side device, enabling of distributed services and platform integrated server for the autonomous provision of device services |
US20040156394A1 (en) | 2003-02-10 | 2004-08-12 | Ilkka Westman | Handling of user identity |
GB2398458B (en) | 2003-02-15 | 2005-05-25 | Ericsson Telefon Ab L M | Conversational bearer negotiation |
US7826353B2 (en) | 2003-05-05 | 2010-11-02 | Nokia Corporation | Method, system and network element for authorizing a data transmission |
US7461385B2 (en) | 2003-05-06 | 2008-12-02 | Qad Corporation | Method for establishing a new user interface via an intermingled user interface |
US7287179B2 (en) | 2003-05-15 | 2007-10-23 | International Business Machines Corporation | Autonomic failover of grid-based services |
EP2270622B1 (en) | 2003-06-05 | 2016-08-24 | Intertrust Technologies Corporation | Interoperable systems and methods for peer-to-peer service orchestration |
US8046461B2 (en) | 2003-06-27 | 2011-10-25 | International Business Machines Corporation | Methods, systems and program products for delivery of web services using categorical contracts |
US7746849B2 (en) | 2003-07-30 | 2010-06-29 | Nortel Networds Limited | Providing packet-based multimedia services via a circuit bearer |
CA2534448C (en) | 2003-08-14 | 2009-10-27 | Telcordia Technologies, Inc. | Auto-ip traffic optimization in mobile telecommunications systems |
US7359373B2 (en) | 2003-10-17 | 2008-04-15 | Nokia Corporation | System, apparatus, and method for establishing circuit-switched communications via packet-switched network signaling |
US7092707B2 (en) | 2004-02-13 | 2006-08-15 | Telcordia Technologies, Inc. | Service impact analysis and alert handling in telecommunications systems |
GB2431067B (en) | 2005-10-07 | 2008-05-07 | Cramer Systems Ltd | Telecommunications service management |
-
2004
- 2004-09-17 US US10/944,565 patent/US8862570B1/en not_active Expired - Fee Related
-
2014
- 2014-09-23 US US14/493,761 patent/US20150012652A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020019886A1 (en) * | 2000-06-07 | 2002-02-14 | Sanghvi Ashvinkumar J. | Event consumers for an event management system |
US20030033379A1 (en) * | 2001-07-20 | 2003-02-13 | Lemur Networks | Intelligent central directory for soft configuration of IP services |
US20040236633A1 (en) * | 2003-05-05 | 2004-11-25 | Knauerhase Robert C. | Management and arbitration of mobile service discovery |
US20050044197A1 (en) * | 2003-08-18 | 2005-02-24 | Sun Microsystems.Inc. | Structured methodology and design patterns for web services |
US20070011322A1 (en) * | 2003-09-30 | 2007-01-11 | Corrado Moiso | Method and system for providing access to web services |
Also Published As
Publication number | Publication date |
---|---|
US8862570B1 (en) | 2014-10-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7580994B1 (en) | Method and apparatus for enabling dynamic self-healing of multi-media services | |
US7701859B2 (en) | Method and apparatus for identifying problem causes in a multi-node system | |
Papazoglou et al. | Service oriented architectures: approaches, technologies and research issues | |
Papazoglou et al. | Web services management: a survey | |
Sahai et al. | Automated SLA monitoring for web services | |
Debusmann et al. | SLA-driven management of distributed systems using the common information model | |
US7533301B2 (en) | High level operational support system | |
US20010052006A1 (en) | Method for computer internet remote management of a telecommunication network element | |
WO2005106666A1 (en) | A system and method for modeling and dynamically deploying services into a distributed networking architecture | |
US20150012652A1 (en) | Method and Apparatus for Open Management of Multi-Media Services | |
Overeinder et al. | Web service access management for integration with agent systems | |
Liu et al. | Management of service-oriented systems | |
Keeney et al. | Ontology-based semantics for composable autonomic elements | |
Nair et al. | ‘CloudCop’: Putting network-admin on cloud nine towards Cloud Computing for Network Monitoring | |
Vianna et al. | Investigating web services composition applied to network management | |
Lin et al. | A web services status monitoring technology for distributed system management in the cloud | |
Kotsopoulos et al. | A SOA-based information management model for Next-Generation Network | |
Martin-Flatin et al. | Web services for integrated management: A case study | |
Wegdam et al. | Using message reflection in a management architecture for CORBA | |
Sundaram et al. | Design and implementation of WBEM-based network management system for inter-as traffic engineering | |
Kumar et al. | Moving from data modeling to process modeling in cim | |
Flehmig et al. | Design and integration of sla monitoring and negotiation capabilities | |
Pras et al. | What Can Web Services Bring To Integrated Management? | |
Kocan et al. | The SCF: A framework for application enablement service composition | |
Sahai et al. | A Data Model Based on Service and Process Abstractions for Management of Systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: RPX CLEARINGHOUSE LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROCKSTAR CONSORTIUM US LP;ROCKSTAR CONSORTIUM LLC;BOCKSTAR TECHNOLOGIES LLC;AND OTHERS;REEL/FRAME:034924/0779 Effective date: 20150128 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |