Networked system of intelligent lighting devices with sharing of processing resources of the devices with other entities
US-2015382433-A1 · Dec 31, 2015 · US
US9960928B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9960928-B1 |
| Application number | US-201213543769-A |
| Country | US |
| Kind code | B1 |
| Filing date | Jul 6, 2012 |
| Priority date | Jul 7, 2011 |
| Publication date | May 1, 2018 |
| Grant date | May 1, 2018 |
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.
A method is provided in one example embodiment and includes establishing a connection between a client and a messaging fabric of a conductor element associated with a video system; creating a plurality of nodes for system management events; and receiving a subscription request for a particular one of the system management events. The particular subscription request and system management event is authenticated and authorized by use of an identifier associated with the particular subscription request and system management event.
Opening claim text (preview).
What is claimed is: 1. A method implemented by a conductor element, the method comprising: establishing a connection between a client and a messaging fabric of the conductor element, which is associated with a video system; receiving a subscription request for a system management event, wherein the subscription request is authenticated and authorized by use of a first identifier of the client; receiving from a service the system management event at a publish-subscribe Extensible Messaging and Presence Protocol (XMPP) node managed by the conductor element; authenticating and authorizing the system management event using a second identifier of the service; and forwarding the system management event to the client, based on the first identifier. 2. The method of claim 1 , wherein the XMPP node is configured based on an event severity level. 3. The method of claim 1 , further comprising: forwarding the system management event to a collection node. 4. The method of claim 1 , further comprising: storing the system management event in a persistent storage; and querying the system management event. 5. The method of claim 1 , further comprising: forwarding the system management event to a collection node that forwards the system management event based on a subscription. 6. The method of claim 1 , further comprising: providing a filter at the XMPP node as part of a subscription to limit an event from notifying the client. 7. The method of claim 1 , further comprising: providing a filter at an event generator as part of a subscription to limit an event from notifying the XMPP node. 8. The method of claim 1 , wherein the system management event is received from an application, and the client is to perform one or more load-balancing operations based on the system management event. 9. Logic, encoded in one or more non-transitory media, that includes instructions for execution and, when executed by a processor, is operable to perform operations comprising: establishing a connection between a client and a messaging fabric of a conductor element associated with a video system; receiving a subscription request for a system management event, wherein the subscription request is authenticated and authorized by use of a first identifier of the client; receiving from a service the system management event at a publish-subscribe Extensible Messaging and Presence Protocol (XMPP) node managed by the conductor element; authenticating and authorizing the system management event using a second identifier of the service; and forwarding the system management event to the client, based on the first identifier. 10. The logic of claim 9 , the operations further comprising: forwarding the system management event to a collection node. 11. The logic of claim 9 , the operations further comprising: storing the system management event in a persistent storage; and querying the system management event. 12. The logic of claim 9 , the operations further comprising: forwarding the system management event to a collection node that forwards the system management event based on a subscription. 13. The logic of claim 9 , the operations further comprising: providing a filter at the XMPP node as part of a subscription to limit an event from notifying the client. 14. The logic of claim 9 , wherein the system management event is received to perform one or more load-balancing operations. 15. A conductor element, comprising: a memory element configured to store instructions; and a processor coupled to the memory element, wherein the apparatus is configured to establish a connection between a client and a messaging fabric of the conductor element, which is associated with a video system; receive a subscription request for a system management event, wherein the subscription request is authenticated and authorized by use of a first identifier of the client, receive from a service the system management event at a publish-subscribe Extensible Messaging and Presence Protocol (XMPP) node managed by the conductor element, authenticate and authorize the system management event using a second identifier of the service, and forward the system management event to the client, based on the first identifier. 16. The conductor element of claim 15 , wherein the XMPP node is configured based on an event severity level. 17. The conductor element of claim 15 , wherein the apparatus is further configured to flag the system management event as persistent such that the system management event is stored in a persistent storage. 18. The conductor element of claim 15 , wherein the apparatus is further configured to forward the system management event to a collection node that forwards the system management event based on a subscription. 19. The conductor element of claim 15 , wherein the conductor element creates a node based on a service or a system management event. 20. The conductor element of claim 15 , wherein the conductor element receives from the client a specification of a filter.
Audio/video appliances · CPC title
Controlling appliance services of a home automation network by calling their functionalities (arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station; in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom H04Q9/00) · CPC title
Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks · CPC title
having fewer capabilities than the client, e.g. thin client having less processing power or no tuning capabilities · CPC title
{Providing} Remote input by a user located remotely from the client device, e.g. at work · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.