Abstract:
A messaging data structure (700) for accessing data in an identity-centric manner, An identity may be a user, a group of users, or an organization. Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services accessible by many applications. The data is stored in accordance with a schema that is recognized by number of different applications and the data service. The messaging data structure (700) includes fields that identify the target data object to be operated upon using an identity field (701), a schema field (703), and an instance identifier field (704). In addition, the desired operation (707) is specified. Thus, the target data objet is operated on in an identity-centric manner.
Abstract:
Architecture for a scalable, pluggable multi-party, and distributed multimedia conferencing. A centralized policy and control conferencing component allows the seamless plug-in of different distributed media components (e.g., data, audio/video, messaging) to accommodate client participation in a conference session. The centralized conference control component includes the following: a conference notification service for accepting subscriptions to the conference state and notifying subscribers about changes to that state; a conference policy and roster control service for storing and manipulating conference policy and rosters; a security service for user authorization/authentication based on user identity information; a scheduling service for conference scheduling; an allocation service for allocating the most available media component(s) for a conference session; and, an MCU management service for conference policy and roster management of the distributed media components.
Abstract:
Architecture for a scalable, pluggable multi-party, and distributed multi media conferencing. A centralized policy and control conferencing component allows the seamless plug-in of different distributed media components (e.g., data, audio/video, messaging) to accommodate client participation in a conf erence session. The centralized conference control component includes the fo llowing: a conference notification service for accepting subscriptions to th e conference state and notifying subscribers about changes to that state; a conference policy and roster control service for storing and manipulating co nference policy and rosters; a security service for user authorization/authe ntication based on user identity information; a scheduling service for confe rence scheduling; an allocation service for allocating the most available me dia component(s) for a conference session; and, an MCU management service fo r conference policy and roster management of the distributed media component s.
Abstract:
Architecture for a scalable, pluggable multi-party, and distributed multimedia conferencing. A centralized policy and control conferencing component allows the seamless plug-in of different distributed media components (e.g., data, audio/video, messaging) to accommodate client participation in a conference session. The centralized conference control component includes the following: a conference notification service for accepting subscriptions to the conference state and notifying subscribers about changes to that state; a conference policy and roster control service for storing and manipulating conference policy and rosters; a security service for user authorization/authentication based on user identity information; a scheduling service for conference scheduling; an allocation service for allocating the most available media component(s) for a conference session; and, an MCU management service for conference policy and roster management of the distributed media components.
Abstract:
A model for accessing data in an identity-centric manner. An identity may be a user, a group of users, or an organization. Instead of data being maintained on an application-by-application basis, the data associated with a particular identity is stored by one or more data services accessible by many applications. The data is stored in accordance with a schema that is recognized by a number of different applications and the data service. When a user is to perform an operation on the identity's data, the corresponding application generates a message that has a structure that is recognized by the data service. The message represents a request to perform an operation on the data structure corresponding to the identity. The data service receives and interprets the message. If authorized, the data service then performs the operation.
Abstract:
A schema-based notification platform (500) that provides regularized notification handling (506) including user control and normalization of the operation of policies across different information types and contexts. Information-service schemas and services (503) are combined to build a content-sensitive and context-sensitive information service to communicate information to recipient devices (508) of users that subscribe to those services. An information agent service (504) collects the information, and based on various criteria, determines if, when, and how to send and render the information, and to which subscribing client device or devices.
Abstract:
Directly operating on data structures in a generic manner regardless of the type of data structure being operated upon and without requiring dedicated executable code for manipulating data structures of the particular data type. A common set of commands (e.g -. insert, delete, replace, update, query) are recognized that may be used to operate on data structures (210, 220, 230, 240) of a number of different data types. A navigation module (250) accesses a request to execute one of the common command methods on at least an identified portion of an identified data structure (210, 220, 230, 240). Then, the navigation module (250) accesses a navigation assistance module (260) to access a set of rules associated with the particular data type, the set of rules allowing the navigation module (250) to find the portion of the data structure (210, 220, 230, 240) that is to be operated on. If appropriate, the command operation is then executed on the identified portion of the data structure (210, 220, 230, 240).
Abstract:
Authorizing a requesting entity to have a server perform a particular action in a manner that is at least partially independent of the underlying target data structure. An authorization station maintains a number of role templates (310) that each define basic access permissions with respect to a number of command methods. The authorization station also maintains a number of role definitions (350) that each define access permissions for specific requesting entities by using one or more of the role templates (310). When the authorization station receives a request from the requesting entity, the authorization station then identifies the appropriate role definition (350). Using this role definition (350), the authorization station determines access permissions for the requesting entity with respect to the requested action.