SYSTEM AND METHOD FOR PROVIDING A MESSAGE AND AN EVENT BASED VIDEO SERVICES CONTROL PLANE

• US 20130013688A1
• Filed: 07/06/2012
• Published: 01/10/2013
• Est. Priority Date: 07/07/2011
• Status: Abandoned Application

• Current Assignee: NDS Limited (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Wang, Qi, Li, Jerry Liansuo, Pope, Nick George, Andreasen, Flemming S., You, Guangxin, She, Zhidong
• Application Number:
  US13/543,692
• Publication Number:
  US 20130013688A1
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

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; defining a service having a set of features using a set of interfaces associated with an Extensible Messaging and Presence Protocol (XMPP); assigning a plurality of XML namespaces for the set of features of the service; assigning an identifier to the service; and registering the service in a service directory in order to create a mapping between the XML namespaces and the identifier.

Claims

1. A method, comprising:

establishing a connection between a client and a messaging fabric of a conductor element associated with a video system;

defining a service having a set of features using a set of interfaces associated with an Extensible Messaging and Presence Protocol (XMPP);

assigning a plurality of XML namespaces for the set of features of the service;

assigning an identifier to the service; and

registering the service in a service directory in order to create a mapping between the XML namespaces and the identifier.

2. The method of claim 1, wherein the service exposes non-XMPP-based features to be accessed by other protocols.

3. The method of claim 1, further comprising:

registering non-XMPP-based features in the service directory using a uniform resource locator (URL).

4. The method of claim 1, wherein the service is invoked by a device in order to support a particular feature of the video system.

5. The method of claim 1, further comprising:

accessing a protocol namespace in the service directory;

retrieving a particular identifier associated with a particular service; and

communicating a message using a messaging infrastructure of the conductor element.

6. The method of claim 1, wherein a virtual service identifier is defined for a particular service.

7. The method of claim 1, further comprising:

receiving a message associated with a particular service; and

evaluating a service policy in the service directory to determine permissions associated with messaging for the particular service.

8. The method of claim 7, wherein the service policy includes matching criteria used to determine whether a particular client is permitted to send messages to the particular service.

9. The method of claim 7, further comprising:

evaluating which groups are associated with a particular client that sent the message, wherein the service policy includes group permissions associated with a plurality of clients.

10. The method of claim 1, further comprising:

providing a plurality of virtual services to the client using multiple service instances for each of the plurality of virtual services such that they appear as a single virtual service to the client.

11. The method of claim 10, further comprising:

providing service routing to route messages to specific instances of a particular one of the plurality of virtual services.

12. The method of claim 1, further comprising:

registering a protocol namespace in the service directory;

assigning a virtual service identifier for the protocol namespace; and

routing messages addressed to the virtual service identifier to a particular one of a plurality of service instances.

13. 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;

defining a service having a set of features using a set of interfaces associated with an Extensible Messaging and Presence Protocol (XMPP);

assigning a plurality of XML namespaces for the set of features of the service;

assigning an identifier to the service; and

registering the service in a service directory in order to create a mapping between the XML namespaces and the identifier.

14. The logic of claim 13, wherein the service exposes non-XMPP-based features to be accessed by other protocols.

15. The logic of claim 13, the operations further comprising:

registering non-XMPP-based features in the service directory using a uniform resource locator (URL).

16. The logic of claim 13, wherein the service is invoked by a device in order to support a particular feature of the video system.

17. The logic of claim 13, the operations further comprising:

accessing a protocol namespace in the service directory;

retrieving a particular identifier associated with a particular service; and

communicating a message using a messaging infrastructure of the conductor element.

18. An apparatus, comprising:

a memory element configured to store instructions;

a processor coupled to the memory element; and

a conductor element, wherein the apparatus is configured to;

establish a connection between a client and a messaging fabric of a conductor element associated with a video system;

define a service having a set of features using a set of interfaces associated with an Extensible Messaging and Presence Protocol (XMPP);

assign a plurality of XML namespaces for the set of features of the service;

assign an identifier to the service; and

register the service in a service directory in order to create a mapping between the XML namespaces and the identifier.

19. The apparatus of claim 18, wherein the service is invoked by a device in order to support a particular feature of the video system.

20. The apparatus of claim 18, wherein the apparatus is further configured to:

receive a message associated with a particular service; and

evaluate a service policy in the service directory to determine permissions associated with messaging for the particular service, wherein the service policy includes matching criteria used to determine whether a particular client is permitted to send messages to the particular service.