Communications network control plane process
US-2024406074-A1 · Dec 5, 2024 · US
US9509573B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9509573-B2 |
| Application number | US-201114234673-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 4, 2011 |
| Priority date | Aug 4, 2011 |
| Publication date | Nov 29, 2016 |
| Grant date | Nov 29, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Federation systems and methods for information technology service management are disclosed. An example method includes interfacing with each of the autonomous operational models. The method also includes providing a single point of access for client visibility across each of the autonomous operational models.
Opening claim text (preview).
The invention claimed is: 1. A federation method for information technology service management, the method comprising: interfacing with each of autonomous operational models for a client infrastructure, the autonomous operational models having independent information technology service providers; providing, on a client interface, a single point of access visibility across the autonomous operational models; changing the client infrastructure in response to a change command and feedback from the autonomous operational models; and reporting, on the client interface, changes that have been made on the client infrastructure and changes that need to be done. 2. The method of claim 1 , further comprising providing end-to-end visibility between the autonomous operational models to services spanning across the autonomous operational models. 3. The method of claim 1 , further comprising supporting inter-process flow across the autonomous operational models. 4. The method of claim 1 , further comprising supporting multiple service provider interconnects for the autonomous operational models. 5. The method of claim 1 , further comprising supporting different programmatic and data transport platforms for the autonomous operational models. 6. The method of claim 1 , further comprising supporting process-to-process flows for the autonomous operational models. 7. The method of claim 1 , further comprising supporting full process framework-to-process flows for the autonomous operational models. 8. The method of claim 1 , further comprising supporting multi-provider interconnects for the autonomous operational models. 9. The method of claim 7 , further comprising providing a viability layer to a third-party portal. 10. A federation system for information technology service management, the system comprising: an integration layer to provide interoperability among autonomous operational models for a client infrastructure, the autonomous operational models having independent information technology service providers; a client interface to provide single point of access visibility across the autonomous operational models and to show a report of changes that have been made to the client infrastructure and changes that need to be done; and a processor to change the client infrastructure in response to a change command and feedback from the autonomous operational models. 11. The system of claim 10 , wherein the integration layer has a federation bus to pass data bidirectionally between the autonomous operational models. 12. The system of claim 10 , wherein the integration layer has an aggregation layer to provide integrated views into all forms of data from the autonomous operational models. 13. The system of claim 10 , wherein the client interface provides visibility into lifecycle operations of the autonomous operational models. 14. The system of claim 10 , further comprising northbound/southbound API/Web Services interfaces to establish electronic API and Web Services interfaces for the federation. 15. The system of claim 14 , wherein the electronic API and Web Services interfaces expose programmatic and data flow functions.
Customer relationship management · CPC title
Delegation of network management function, e.g. customer network management [CNM] · CPC title
Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title
Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components · CPC title
Grid computing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.