US9088518B2 - Web services and telecom network management unification - Google Patents

Web services and telecom network management unification Download PDF

Info

Publication number
US9088518B2
US9088518B2 US11/627,354 US62735407A US9088518B2 US 9088518 B2 US9088518 B2 US 9088518B2 US 62735407 A US62735407 A US 62735407A US 9088518 B2 US9088518 B2 US 9088518B2
Authority
US
United States
Prior art keywords
service
model
entity
ism
soam
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.)
Expired - Fee Related, expires
Application number
US11/627,354
Other languages
English (en)
Other versions
US20080183850A1 (en
Inventor
Sujoy Basu
Gerald William Winsor
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hewlett Packard Development Co LP
Original Assignee
Hewlett Packard Development Co LP
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hewlett Packard Development Co LP filed Critical Hewlett Packard Development Co LP
Priority to US11/627,354 priority Critical patent/US9088518B2/en
Assigned to HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P. reassignment HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WINSOR, GERALD WILLIAM, BASU, SUJOY
Priority to PCT/US2008/000932 priority patent/WO2008091663A1/fr
Priority to EP08724784.7A priority patent/EP2106647B1/fr
Publication of US20080183850A1 publication Critical patent/US20080183850A1/en
Priority to US14/736,937 priority patent/US9736009B2/en
Application granted granted Critical
Publication of US9088518B2 publication Critical patent/US9088518B2/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • 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
    • 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/022—Multivendor or multi-standard integration
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • Telecom service providers recruit third party independent software vendors (ISVs) to deliver services to run on the telecommunication network infrastructure, both within and outside the Telecom service provider domain.
  • Telecom service providers need to be aware of how service outages affect their subscriber base consuming or registered to use the affected services.
  • Some solutions such as a Hewlett-Packard (HP) Service Delivery Platform (SDP), use a Service-Oriented Architecture (SOA) to deploy new services rapidly within the Telecom service provider infrastructure by reusing common services leveraging third party-provided services.
  • SOA Service-Oriented Architecture
  • the Telecom Network Operations Center (NOC) needs to be alerted about fault and performance issues at the SOA level so that potential “end-user service outages” can be addressed quickly.
  • Telecom NOC staff monitor separate platforms, e.g., separate computer systems, in order to manage web services and telecom networks.
  • FIG. 1 is a high level functional block diagram of a system useable in conjunction with an embodiment
  • FIG. 2 is a high level block diagram of a mapping according to an embodiment
  • FIG. 3 is a high level process flow diagram of a portion of operation according to an embodiment
  • FIG. 4 is a high level process flow diagram of another portion of operation according to an embodiment
  • FIG. 5 is an example message sequence diagram of message flow according to an embodiment
  • FIG. 6 is a high level process flow diagram of a portion of operation according to another embodiment
  • FIG. 7 is a high level process flow diagram of another portion of operation according to another embodiment.
  • FIG. 8 is an example message sequence diagram of message flow according to another embodiment.
  • FIG. 1 depicts a high level functional block diagram of a combined telecom network and web service management system 100 (‘combined system’) in conjunction with which an embodiment may be used to advantage.
  • Combined system 100 comprises a telecom fault management (TFM) component 102 communicatively coupled with a service oriented architecture manager (SOAM) 104 .
  • TFM is the Integrated Services Management product available from Hewlett-Packard (HP) Company of Palo Alto, Calif.
  • ISM 102 comprises a shared information and data model (SID) component 106 comprising an abstract representation of entities in a managed telecom network environment.
  • SID 106 comprises representations of entities of the managed telecom network, as well as, attributes, constraints, and relationships of the represented entities.
  • the particular SID 106 of a particular ISM 102 is an instantiation of the information model using specific data repository and access protocols and specifies a schema according to which data is stored and further specifies rules for manipulating the data.
  • SOAM 104 comprises a service model 108 representing the dependencies of different business processes on a Web service 110 and the inter-dependencies of Web services.
  • An example SOAM is the OPENVIEW SOA MANAGER available from HP.
  • SOAM 114 discovers services through a Web service registry, such as the Systinet registry, which adheres to the Universal Description, Discovery and Integration (UDDI) protocol. Web services may also be specified explicitly using a user interface or by creating a configuration file accessible by SOAM 114 .
  • UDDI Universal Description, Discovery and Integration
  • SOAM 104 generates a Resource Description Framework (RDF) model 112 representation, i.e., an external model representation, of service model 108 and ISM 102 imports the RDF graph into SID 106 .
  • RDF Resource Description Framework
  • the RDF family of specifications from the World Wide Web Consortium provide a lightweight ontology for the exchange of knowledge in the Web.
  • RDF captures the knowledge in a set of triples, each consisting of subject, predicate and object.
  • XML provides a common notation for representing RDF triples, although it is not the only notation that can be used.
  • RDF model 112 captures information in service model 108 of SOAM. In at least some embodiments, RDF model 112 captures the same information as in service model 108 .
  • ISM 102 is able to obtain updated information for a Web service 110 from SOAM 104 , and more particularly, information from service model 108 converted into the RDF model.
  • SOAM 104 generates and transmits an alert signal 114 to ISM 102 in response to an update of status information for a particular Web service 110 .
  • the alert is generated within SOAM 104 by a monitoring engine based on metrics provided from the Web services and threshold values, e.g., performance thresholds, set by the operator on those metrics.
  • SOAM 104 generates and transmits alert signal 114 responsive to an update of status information from a particular web service 110 .
  • alert signal 114 provides updated information to ISM 102 corresponding to updated information for service model 108 which caused the fault to be generated.
  • ISM 102 requests an update (update request 116 ) from service model 108 of information in SID 106 corresponding to imported RDF model 112 .
  • alert signal 114 comprises information identifying a particular web service 110 in service model 108 causing the alert signal and ISM 102 transmits update request 116 comprising information based on the representation of the particular identified Web service 110 to the service model.
  • SOAM 104 responsive to receipt of update request 116 from ISM 102 , SOAM 104 generates and transmits an update 118 specifying updated information for service model 108 . For example, if ISM 102 and SOAM 104 have not communicated for a period of time such that RDF model 112 imported into SID 106 are out of date, the ISM may transmit an update request 116 to the SOAM. In some embodiments, SOAM 104 generates and transmits an update 118 specifying updated information specific to the particular web service 110 which caused the generation of alert signal 114 .
  • alerts generated by web service(s) 110 managed by SOAM 104 are provided to SID 106 and ISM 102 for presentation, e.g., via a display, to a user of the ISM, i.e., a single interface such as a telecom network management system may be used to interact with both telecom networks and web services.
  • alert 114 comprises the updated information specific to the particular web service 110 which caused the generation of alert signal 114 .
  • ISM 102 may transmit a clear alert signal to SOAM 104 .
  • the ISM may clear, e.g., reset, the fault in the corresponding entity in SID 106 . Clearing the fault in SID 106 may then cause generation and transmission, e.g., by ISM 102 , of a clear alert message to SOAM 104 and the corresponding entity in service model 108 and/or web service 110 .
  • the clear alert message may be generated from ISM 102 as part of execution of a rule in rule set 120 .
  • FIG. 1 depicts a single web service 110 ; however, in some embodiments, more than one web service may be present.
  • Software that is accessible over a computer network and which provides specific functionality and supports interaction with other software entities on computers connected to the network may be regarded as a web service.
  • web services may follow standards in order to allow better tooling support from vendors. In at least one other embodiment, web services may not follow and/or may follow a select set of standards.
  • the interfaces to web services may be according to Representational State Transfer (REST) or Simple Object Access Protocol (SOAP) specifications, or other conventions agreed among web service designers.
  • REST Representational State Transfer
  • SOAP Simple Object Access Protocol
  • a shipping company may have implemented a business service to match vehicle drivers to package pickup requests received by the shipping company.
  • the business service may access a location mapping web service which responds to a pickup request comprising a given location of the package and a given location of the nearest available driver by generating map images of the requested destination and route, and turn-by-turn directions.
  • SOAM 104 generates service model 108 based on discovering one or more Web service(s) 110 managed by the SOAM.
  • Service model 108 represents web service(s) 110 discovered by SOAM 104 as managed entities and the dependencies of business services on the Web services, e.g., the dependency of the package and driver matching service on the location mapping Web service in the above example, and inter-dependency of Web services are represented in the service model.
  • Service model 108 entities managed by SOAM 104 differ from SID 106 entities managed by ISM 102 .
  • Service model 108 is a service model in an internal representation of SOAM 104 , or in a language such as a Service Modeling Language (SML).
  • SID 106 is a service model in the Shared Information and Data (SID) model, standardized in the Telecom Management Forum.
  • RDF model 112 represents service model 108 entities corresponding to web service(s) 110 as a set of triples, e.g., a subject-predicate-object expression.
  • a particular web service 110 entity in service model 108 may comprise a name attribute such as “Name” and a unique identifier attribute such as “UniqueIdentifier.”
  • a particular web service 110 entity comprises a name attribute and a unique identifier attribute and additionally a fault attribute such as “Fault.”
  • a particular web service 110 entity comprises a service attribute, e.g., a response time, a throughput value, and other performance-related values.
  • the service attribute may be compared to a threshold value by SOAM 104 in determining whether a service differs from a particular performance threshold, e.g., whether the service meets or exceeds a threshold, whether the service is below a given threshold, etc.
  • ISM 102 applies a rule set 120 to RDF model 112 entities in order to import (represent) the service model entities in the SID.
  • a web service 110 entity from service model 108 may be represented as a resource entity in SID 106 and a business process from the service model may be represented as a service in the SID.
  • FIG. 2 depicts a high-level mapping of attributes between service model 108 entities and SID 106 entities. As depicted, optional attributes may be mapped, e.g., a fault attribute. For example, the above-described particular web service 110 entities attributes may be mapped as follows:
  • Rule set 120 comprises one or more rules applied by ISM 102 to entities of RDF model 112 during importation into SID 106 .
  • the mapping specified in the above tables may be implemented in at least some embodiments using the following rules:
  • Rule 1 (?W rdf:type SOAManager:WebService), (?W rdf:type SID:Resource), (?W SOAManager:hasName ?N), ⁇ (?W SID:hasCommonName ?N), (?W SOAManager:hasUniqueIdentifier ?I) (?W SID:hasEntityIdentification ?I)
  • Rule 1A (?W rdf:type SOAManager:WebService), (?W rdf:type SID:Resource), (?W SOAManager:hasName ?N), ⁇ (?W SID:hasCommonName ?N), (?W SOAManager:hasUniqueIdentifier ?I), (?W SID:hasEntityIdentification ?I) (?W SOAManager:hasFault ?F) (?W SID:hasFault ?F) (?W SID:hasFault ?F)
  • Rules 1 and 1 A indicate the mapping (indicated by the arrow) from service model 108 (left-hand side) to SID 106 (right-hand side).
  • a variable “?W” is bound to a web service 110 in service model 108 and the variables “?N” and “?I” are bound respectively to the name and UniqueIdentifier attributes of a web service entity in the service model.
  • ISM 102 transforms the entity to SID 106 by creating a resource entity and setting the commonName and EntityIdentification attributes to the values bound to the “?N” and “?I” variables, respectively.
  • web service 110 entity comprises a fault attribute
  • rule 1 A preserves the fault attribute in the transformation and importation into SID 106 .
  • variable “?F” is bound to the fault attribute and during transformation, ISM 102 sets the fault attribute of the SID 106 entity to the value bound to the “?F” variable.
  • a function is specified using a web ontology language (OWL), i.e., a markup language used for specifying data by representing the meanings of terms using vocabularies and relationships between terms in a manner suitable for processing by a processor, to identify the particular web service via the SID 106 entity corresponding to the particular web service.
  • OWL web ontology language
  • ISM 102 comprises information specifying services to which a particular telecom network user is subscribed, e.g., the shipping company and/or the shipping company employee subscribing to a package and driver matching service
  • an example function to be applied to SID 106 to determine the subscriptions of the telecom network user is as follows:
  • the above function specification identifies the function and the resources applicable to the function in SID 106 .
  • SOAM 104 maintains, in service model 108 , dependency information regarding composite services reliant on underlying web service(s) 110 . If an underlying web service 110 generates an alert, based on the dependency information in service model 108 , the alert may be propagated to all composite services which depend on the web service. Based on the generated and propagated alert, SOAM 104 alerts (alert signal 114 ) ISM 102 to a fault.
  • an additional rule of rule set 120 may be applied to SID 106 to generate an alert for presentation to a telecom network user and/or a telecom network operator based on the following rule:
  • ISM 102 applies Rule 2 to SID 106 based on receipt of an alert 114 from SOAM 104 and generates, for example, a service outage announcement. That is, the telecom network management system is able to generate an alert to a user based on occurrence of a fault in the web service management system.
  • FIG. 3 depicts a high level process flow diagram of a portion 300 of operation of SOAM 104 according to an embodiment.
  • the process flow starts at service discovery 302 wherein SOAM 104 determines services available and generates service model 108 based on web services and business processes.
  • the flow proceeds to RDF generation 304 wherein SOAM 104 generates RDF model 112 based on service model 108 and transmits the RDF model to ISM 102 .
  • the flow proceeds to wait function 306 .
  • the flow proceeds to alert generation 308 wherein SOAM 104 generates and transmits an alert signal 114 to ISM 102 .
  • the generated alert comprises information of an entity, e.g., the entity causing the fault generation and/or entities dependent thereon, in the service model corresponding to an entity in SID 106 .
  • the flow returns to wait function 306 .
  • ISM 102 may request an update of information in SID 106 corresponding to service model 108 entities. Responsive to receipt of an update request from ISM 102 , the flow proceeds to update generation 310 wherein SOAM 104 generates update information based on service model 108 and transmits update 118 to ISM 102 . The flow returns to wait function 306 .
  • FIG. 4 depicts a high level process flow diagram of a portion 400 of operation of ISM 102 according to an embodiment.
  • the process flow starts at RDF model import 402 wherein ISM 102 imports RDF model 108 responsive to receipt of same from SOAM 104 .
  • the flow proceeds to wait function 404 .
  • the flow proceeds to alert generation 406 wherein ISM 102 updates SID 106 and generates an alert for presentation to a user, e.g., by display on a monitor to a user, by transmission to a user via audio, video, and/or haptic feedback mechanisms.
  • the alert received by ISM 102 comprises information of an entity, e.g., the entity causing the fault generation and/or entities dependent thereon, in the service model corresponding to an entity in SID 106 .
  • ISM 102 may request an update of information in SID 106 corresponding to service model 108 entities.
  • the flow proceeds to update request 408 (dashed line) wherein ISM 102 requests updated information from the SOAM based on the received alert signal.
  • the flow returns to wait function 404 .
  • ISM 102 Responsive to receipt of update 118 from SOAM 104 , ISM 102 updates SID 106 .
  • FIG. 5 depicts a message sequence diagram of message flow 500 according to an embodiment. Time proceeds downward along the page.
  • SOAM 104 discovers web service 110 (sequence 502 ) and generates service model 108 .
  • SOAM 104 generates and transmits (sequence 504 ) RDF model 112 to ISM 102 .
  • ISM 102 imports (sequence 506 ) the RDF model to SID 106 .
  • web service 110 At a later time, web service 110 generates a fault and transmits (sequence 508 ) an alert to SOAM 104 . Responsive to the alert from web service 110 , SOAM 104 generates and transmits alert signal 114 (sequence 510 ) to ISM 102 .
  • the generated alert comprises information of an entity, e.g., the entity causing the fault generation and/or entities dependent thereon, in the service model corresponding to an entity in SID 106 .
  • the generated alert comprises information to enable ISM 102 to update the corresponding entity/ies in SID 106 .
  • ISM 102 imports (sequence 512 ) the updated information into SID 106 and generates and transmits an alert to a user.
  • FIG. 6 depicts a high level process flow diagram of a portion 600 of operation of SOAM 104 according to an embodiment.
  • the process flow starts at service discovery 602 wherein SOAM 104 determines services available and generates service model 108 based on web services and business processes.
  • the flow proceeds to RDF generation 604 wherein SOAM 104 generates RDF model 112 based on service model 108 and transmits the RDF model to ISM 102 .
  • the flow proceeds to wait function 606 .
  • the flow proceeds to alert generation 608 wherein SOAM 104 generates and transmits an alert signal 114 to ISM 102 .
  • the flow returns to wait function 606 .
  • the flow proceeds to update generation 610 wherein SOAM 104 generates update information based on service model 108 and transmits update 118 to ISM 102 .
  • the flow returns to wait function 606 .
  • FIG. 7 depicts a high level process flow diagram of a portion 700 of operation of ISM 102 according to an embodiment.
  • the process flow starts at RDF model import 702 wherein ISM 102 imports RDF model 108 responsive to receipt of same from SOAM 104 .
  • the flow proceeds to wait function 704 .
  • the flow proceeds to update request 706 wherein ISM 102 requests updated information from the SOAM based on the received alert signal.
  • the flow returns to wait function 704 .
  • ISM 102 updates SID 106 and generates an alert for presentation to a user, e.g., by display on a monitor to a user, by transmission to a user via audio, video, and/or haptic feedback mechanisms.
  • FIG. 8 depicts a message sequence diagram of message flow 800 according to an embodiment. Time proceeds downward along the page.
  • SOAM 104 discovers web service 110 (sequence 802 ) and generates service model 108 .
  • SOAM 104 generates and transmits (sequence 804 ) RDF model 112 to ISM 102 .
  • ISM 102 imports (sequence 806 ) the RDF model to SID 106 .
  • web service 110 At a later time, web service 110 generates a fault and transmits (sequence 808 ) an alert to SOAM 104 . Responsive to the alert from web service 110 , SOAM 104 generates and transmits alert signal 114 (sequence 810 ) to ISM 102 . Responsive to receipt of alert signal 114 , ISM 102 requests (sequence 812 ) updated information from SOAM 104 based on the alert signal. Responsive to receipt of the update request from ISM 102 , SOAM 104 transmits (sequence 814 ) updated information from service model 108 to ISM 102 . Responsive to receipt of the updated information from SOAM 104 , ISM 102 imports (sequence 816 ) the updated information into SID 106 and generates and transmits an alert to a user.
  • Some or all of the operations, functions, and methods set forth in this application may be performed by one or more computer programs including instructions and stored on a memory or other type of computer-readable storage medium.
  • the one or more computer programs may be executed by a processor to perform the operations, functions, and methods.
  • Examples of the operations, functions, and methods include but are not limited exporting an external model representation of at least one entity of a service model of a service oriented architecture manager; importing the exported external model representation of the at least one entity as a network management data model entity of a network manager; and subscribing, by the network manager, to subsequent updates of the at least one entity.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)
US11/627,354 2007-01-25 2007-01-25 Web services and telecom network management unification Expired - Fee Related US9088518B2 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US11/627,354 US9088518B2 (en) 2007-01-25 2007-01-25 Web services and telecom network management unification
PCT/US2008/000932 WO2008091663A1 (fr) 2007-01-25 2008-01-23 Unification de services web et d'une gestion de réseau de télécommunication
EP08724784.7A EP2106647B1 (fr) 2007-01-25 2008-01-23 Unification de services web et d'une gestion de réseau de télécommunication
US14/736,937 US9736009B2 (en) 2007-01-25 2015-06-11 Web services and telecom network management unification

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US11/627,354 US9088518B2 (en) 2007-01-25 2007-01-25 Web services and telecom network management unification

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/736,937 Continuation US9736009B2 (en) 2007-01-25 2015-06-11 Web services and telecom network management unification

Publications (2)

Publication Number Publication Date
US20080183850A1 US20080183850A1 (en) 2008-07-31
US9088518B2 true US9088518B2 (en) 2015-07-21

Family

ID=39644813

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/627,354 Expired - Fee Related US9088518B2 (en) 2007-01-25 2007-01-25 Web services and telecom network management unification
US14/736,937 Active 2027-02-05 US9736009B2 (en) 2007-01-25 2015-06-11 Web services and telecom network management unification

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/736,937 Active 2027-02-05 US9736009B2 (en) 2007-01-25 2015-06-11 Web services and telecom network management unification

Country Status (3)

Country Link
US (2) US9088518B2 (fr)
EP (1) EP2106647B1 (fr)
WO (1) WO2008091663A1 (fr)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9213526B1 (en) * 2006-07-19 2015-12-15 Red Hat, Inc. Service oriented architecture (SOA) modeling
US8782542B2 (en) 2006-07-19 2014-07-15 Red Hat, Inc. Display and management of a service composition candidate inventory
US9841951B2 (en) 2006-07-19 2017-12-12 Red Hat, Inc. Management of SOA service model
US20080201338A1 (en) * 2007-02-16 2008-08-21 Microsoft Corporation Rest for entities
US20080201234A1 (en) * 2007-02-16 2008-08-21 Microsoft Corporation Live entities internet store service
US20090210400A1 (en) * 2008-02-15 2009-08-20 Microsoft Corporation Translating Identifier in Request into Data Structure
US8316347B2 (en) * 2008-12-05 2012-11-20 International Business Machines Corporation Architecture view generation method and system
US8332813B2 (en) * 2008-12-11 2012-12-11 International Business Machines Corporation Service re-factoring method and system
US8224869B2 (en) 2008-12-16 2012-07-17 International Business Machines Corporation Re-establishing traceability method and system
US20100161371A1 (en) * 2008-12-22 2010-06-24 Murray Robert Cantor Governance Enactment
US8825745B2 (en) 2010-07-11 2014-09-02 Microsoft Corporation URL-facilitated access to spreadsheet elements
US8478766B1 (en) * 2011-02-02 2013-07-02 Comindware Ltd. Unified data architecture for business process management
US9825908B2 (en) * 2013-12-11 2017-11-21 At&T Intellectual Property I, L.P. System and method to monitor and manage imperfect or compromised software
EP3201764A1 (fr) 2014-09-29 2017-08-09 Hewlett-Packard Enterprise Development LP Fourniture d'un service
WO2017129248A1 (fr) * 2016-01-28 2017-08-03 Hewlett Packard Enterprise Development Lp Orchestration de service
US11196643B2 (en) 2018-04-04 2021-12-07 Hewlett Packard Enterprise Development Lp State transitions for a set of services
US11281491B2 (en) 2018-11-21 2022-03-22 Hewlett Packard Enterprise Development Lp Execution of services concurrently
US11455202B2 (en) * 2020-09-03 2022-09-27 International Business Machines Corporation Real-time fault localization detection and notification

Citations (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6336138B1 (en) * 1998-08-25 2002-01-01 Hewlett-Packard Company Template-driven approach for generating models on network services
US20020104068A1 (en) * 2000-11-03 2002-08-01 Stephen Barrett Software development process
US20030145096A1 (en) * 2002-01-29 2003-07-31 International Business Machines Corporation Method and device for delivering information through a distributed information system
US20030208533A1 (en) * 2002-04-25 2003-11-06 Digital Evolution Method and apparatus for managing web services within a computer network system
US20040093381A1 (en) * 2002-05-28 2004-05-13 Hodges Donna Kay Service-oriented architecture systems and methods
US20040122693A1 (en) * 2002-12-23 2004-06-24 Michael Hatscher Community builder
US20040139151A1 (en) * 2002-12-17 2004-07-15 International Business Machines Corporation Apparatus and method for selecting a web service in response to a request from a client device
US20040249645A1 (en) * 2003-06-05 2004-12-09 International Business Machines Corporation Method and apparatus for generating it level executable solution artifacts from the operational specification of a business
US20050027871A1 (en) * 2003-06-05 2005-02-03 William Bradley Interoperable systems and methods for peer-to-peer service orchestration
US20050050311A1 (en) * 2003-08-28 2005-03-03 International Business Machines Corporation Pluggable state meta-data processors based on meta information modeling in a service oriented architecture
US20050050141A1 (en) * 2003-08-28 2005-03-03 International Business Machines Corporation Method and apparatus for generating service oriented state data and meta-data using meta information modeling
US20050066058A1 (en) * 2003-08-28 2005-03-24 International Business Machines Corporation Gateway for service oriented state
US20050144226A1 (en) * 2003-11-10 2005-06-30 Churchill Software Services Systems and methods for modeling and generating reusable application component frameworks, and automated assembly of service-oriented applications from existing applications
US20050278270A1 (en) * 2004-06-14 2005-12-15 Hewlett-Packard Development Company, L.P. Data services handler
US20060031441A1 (en) * 2004-04-30 2006-02-09 International Business Machines Corporation Dynamic extension of network-accessible services
US20060064483A1 (en) * 2004-09-23 2006-03-23 Patel Rikin S System and method for service response monitoring
US20060080289A1 (en) * 2004-10-11 2006-04-13 Frank Brunswig Service-oriented architecture for accessing reports in legacy systems
US20060106842A1 (en) * 2004-11-17 2006-05-18 Diament Judah M Method and apparatus for dynamic middleware assembly
US20060143229A1 (en) * 2004-12-28 2006-06-29 International Business Machines Corporation Method and system for dynamic creation of service flows
US7072960B2 (en) * 2002-06-10 2006-07-04 Hewlett-Packard Development Company, L.P. Generating automated mappings of service demands to server capacities in a distributed computer system
US20070073769A1 (en) * 2005-09-28 2007-03-29 Baikov Chavdar S Method and system for generating a web services meta model on the java stack
WO2007093498A1 (fr) 2006-02-14 2007-08-23 International Business Machines Corporation Passerelle de service pour la mise en oeuvre d'une architecture orientée vers les services, à configuration dispersée et à échelle variable
US7281018B1 (en) * 2004-05-26 2007-10-09 Microsoft Corporation Form template data source change
US20080031481A1 (en) 2006-05-30 2008-02-07 Knowles Electronics, Llc Personal listening device
US20080071816A1 (en) * 2006-09-18 2008-03-20 Turnriver Llc Transmission of server-based system events to web service clients
US20080127047A1 (en) * 2006-10-31 2008-05-29 Liang-Jie Zhang Method and Apparatus for Service-Oriented Architecture Process Decomposition And Service Modeling
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
US7493302B2 (en) * 2006-06-26 2009-02-17 International Business Machines Corporation Federated transaction path and service level agreement monitoring across service oriented application partner domains

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6173311B1 (en) * 1997-02-13 2001-01-09 Pointcast, Inc. Apparatus, method and article of manufacture for servicing client requests on a network
US7349980B1 (en) * 2003-01-24 2008-03-25 Blue Titan Software, Inc. Network publish/subscribe system incorporating Web services network routing architecture
US20060031481A1 (en) * 2004-05-21 2006-02-09 Bea Systems, Inc. Service oriented architecture with monitoring
US8868779B2 (en) * 2004-06-15 2014-10-21 Accenture Global Services Limited Method and apparatus to accomplish peer-to-peer application data routing between service consumers and service providers within a service oriented architecture
US20060184380A1 (en) * 2005-02-15 2006-08-17 Samsung Electronics Co., Ltd. XML-based resource data structures and networks managed by XML-based resource data structures
US20070169199A1 (en) * 2005-09-09 2007-07-19 Forum Systems, Inc. Web service vulnerability metadata exchange system

Patent Citations (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6336138B1 (en) * 1998-08-25 2002-01-01 Hewlett-Packard Company Template-driven approach for generating models on network services
US20020104068A1 (en) * 2000-11-03 2002-08-01 Stephen Barrett Software development process
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
US20030145096A1 (en) * 2002-01-29 2003-07-31 International Business Machines Corporation Method and device for delivering information through a distributed information system
US20030208533A1 (en) * 2002-04-25 2003-11-06 Digital Evolution Method and apparatus for managing web services within a computer network system
US7801976B2 (en) * 2002-05-28 2010-09-21 At&T Intellectual Property I, L.P. Service-oriented architecture systems and methods
US20040093381A1 (en) * 2002-05-28 2004-05-13 Hodges Donna Kay Service-oriented architecture systems and methods
US7072960B2 (en) * 2002-06-10 2006-07-04 Hewlett-Packard Development Company, L.P. Generating automated mappings of service demands to server capacities in a distributed computer system
US20040139151A1 (en) * 2002-12-17 2004-07-15 International Business Machines Corporation Apparatus and method for selecting a web service in response to a request from a client device
US20040122693A1 (en) * 2002-12-23 2004-06-24 Michael Hatscher Community builder
US20050027871A1 (en) * 2003-06-05 2005-02-03 William Bradley Interoperable systems and methods for peer-to-peer service orchestration
US20040249645A1 (en) * 2003-06-05 2004-12-09 International Business Machines Corporation Method and apparatus for generating it level executable solution artifacts from the operational specification of a business
US20050066058A1 (en) * 2003-08-28 2005-03-24 International Business Machines Corporation Gateway for service oriented state
US20050050141A1 (en) * 2003-08-28 2005-03-03 International Business Machines Corporation Method and apparatus for generating service oriented state data and meta-data using meta information modeling
US20050050311A1 (en) * 2003-08-28 2005-03-03 International Business Machines Corporation Pluggable state meta-data processors based on meta information modeling in a service oriented architecture
US20050144226A1 (en) * 2003-11-10 2005-06-30 Churchill Software Services Systems and methods for modeling and generating reusable application component frameworks, and automated assembly of service-oriented applications from existing applications
US20060031441A1 (en) * 2004-04-30 2006-02-09 International Business Machines Corporation Dynamic extension of network-accessible services
US7281018B1 (en) * 2004-05-26 2007-10-09 Microsoft Corporation Form template data source change
US20050278270A1 (en) * 2004-06-14 2005-12-15 Hewlett-Packard Development Company, L.P. Data services handler
US20060064483A1 (en) * 2004-09-23 2006-03-23 Patel Rikin S System and method for service response monitoring
US20060080289A1 (en) * 2004-10-11 2006-04-13 Frank Brunswig Service-oriented architecture for accessing reports in legacy systems
US20060106842A1 (en) * 2004-11-17 2006-05-18 Diament Judah M Method and apparatus for dynamic middleware assembly
US20060143229A1 (en) * 2004-12-28 2006-06-29 International Business Machines Corporation Method and system for dynamic creation of service flows
US20070073769A1 (en) * 2005-09-28 2007-03-29 Baikov Chavdar S Method and system for generating a web services meta model on the java stack
WO2007093498A1 (fr) 2006-02-14 2007-08-23 International Business Machines Corporation Passerelle de service pour la mise en oeuvre d'une architecture orientée vers les services, à configuration dispersée et à échelle variable
US20080031481A1 (en) 2006-05-30 2008-02-07 Knowles Electronics, Llc Personal listening device
US7493302B2 (en) * 2006-06-26 2009-02-17 International Business Machines Corporation Federated transaction path and service level agreement monitoring across service oriented application partner domains
US20080071816A1 (en) * 2006-09-18 2008-03-20 Turnriver Llc Transmission of server-based system events to web service clients
US20080127047A1 (en) * 2006-10-31 2008-05-29 Liang-Jie Zhang Method and Apparatus for Service-Oriented Architecture Process Decomposition And Service Modeling

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Hiroshi Wada et al-"A Service-Oriented Design Framework for Secure Network Applications"-COMPSAC '06 vol. 1-Sep. 2006-pp. 359-368.

Also Published As

Publication number Publication date
US20150280962A1 (en) 2015-10-01
US9736009B2 (en) 2017-08-15
WO2008091663A1 (fr) 2008-07-31
EP2106647A1 (fr) 2009-10-07
US20080183850A1 (en) 2008-07-31
EP2106647A4 (fr) 2015-10-07
EP2106647B1 (fr) 2020-02-26

Similar Documents

Publication Publication Date Title
US9088518B2 (en) Web services and telecom network management unification
CN109246251B (zh) 一种微服务调用方法、装置、系统、设备及可读存储介质
US11743699B2 (en) Method of discovering services provided by a network repository function
US10693746B2 (en) Instrumentation and monitoring of service level agreement (SLA) and service policy enforcement
US7454496B2 (en) Method for monitoring data resources of a data processing network
US7673029B2 (en) Grid automation bus to integrate management frameworks for dynamic grid management
US7533301B2 (en) High level operational support system
CN110636093B (zh) 微服务注册和发现方法、设备、存储介质以及微服务系统
US8683545B2 (en) Federating policies from multiple policy providers
US20070162567A1 (en) Managing network-enabled devices
US20110179007A1 (en) Systems and methods for web service architectures
Inzinger et al. Generic event‐based monitoring and adaptation methodology for heterogeneous distributed systems
US7984128B2 (en) System and method for discovering managed information technology resources
US8230448B2 (en) Methods, systems and computer program products for web service interaction with a resource management system
US20100064184A1 (en) Web Service Management
US20080162690A1 (en) Application Management System
WO2022141287A1 (fr) Procédé et appareil de gestion de données, procédé et appareil d'interrogation de données, système de maillage de service, et dispositif informatique
US20040230943A1 (en) System and method for managing information technology resources
US20040237042A1 (en) System and method for collectively managing information technology resources
Keeney et al. Ontology-based semantics for composable autonomic elements
WO2022032487A1 (fr) Appareil et procédés de coordination d'accès à des informations d'analyse dans des réseaux de communication
CN115208764B (zh) 一种基于资源池的请求响应方法、装置及其介质
Ma et al. The Study and Application of System Integration Based on ESB for Enterprise Group
US20230412466A1 (en) Managing cloud-native virtual network functions
Quirolgico et al. Deriving knowledge for the knowledge plane

Legal Events

Date Code Title Description
AS Assignment

Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BASU, SUJOY;WINSOR, GERALD WILLIAM;REEL/FRAME:018946/0387;SIGNING DATES FROM 20070206 TO 20070214

Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BASU, SUJOY;WINSOR, GERALD WILLIAM;SIGNING DATES FROM 20070206 TO 20070214;REEL/FRAME:018946/0387

XAS Not any more in us assignment database

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BASU, SUJOY;WINSOR, GERALD WILLIAM;SIGNING DATES FROM 20070206 TO 20070214;REEL/FRAME:018946/0445

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551)

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20230721