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:
A model for accessing data in an identity-centric manner. An identity (310) maybe 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 (511 through 518) accessible by many applications (320). The data is stored in accordance with a schema that is recognized by a number of different applications and hte data service (511 through 518). When a user is to perform an operatio on the identity's (310 data, the corresponding application (320) generates a message (531) that has a structure that is recognized by the data service (511 through 518). The message (531) represents a request to perform an operation on the data structure corresponding to the identity (310). The data service (511 through 518) receives and itnerprets the message. If authorized, the data service (511 through 518) then performs the operation.
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:
A computer-implemented conferencing system, comprising: a plurality of" contendd servers comprising a conferencing pool, wherein each of the plurality of frontend servers comprises at least one processing unit; a storage device that stores a 10 conference database, wherein the conference database includes information about at least one conference provisioned on at least one frontend server of the conFerencing pool, and wherein the conference database further includes presence information and registration information corresponding to the at least one provisioned conference; and at least one load balancer component that balances session load among the plurality of 15 the frontend servers comprising the conferencing pool. COMPONENT 104 MEDIA MEDIA MEDIA COMPONENT, COMPONENTS COMPONENTN 1- 106 CLIENT CLIENT, --- CLIENTm
Abstract:
A messaging data structure 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. The messaging data structure includes fields that identify the target data object to be operated upon using an identity field, a schema field, and an instance identifier field. In addition, the desired operation is specified. Thus, the target data object 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:
Se describe una arquitectura para una conferencia multimedia escalable, de partes múltiples conectable, y distribuida. Una política centralizada y componente de conferencia de control permiten la conexión uniforme de diferentes componentes de medios distribuidos (por ejemplo, datos, audio/vídeo, transmisión de mensajes) para acomodar participación de cliente en una sesión de conferencia. El componente de control de conferencia centralizado incluye lo siguiente: un servicio de notificación de conferencia para aceptar suscripciones al estado de conferencia y notificar a los suscriptores sobre cambios a ese estado; una política de conferencia y servicio de control de lista para almacenar y manipular política de conferencia y listas; un servicio de seguridad para autorización/autentificación de usuario basado en información de identidad de usuario; un servicio de programación para programación de conferencia; un servicio de distribución para distribuir el componente(s) de medios más disponible para una sesión de conferencia; y, un servicio de manejo de MCU para política de conferencia y manejo de lista de los componentes de medios distribuidos.
Abstract:
A model for accessing data in an identity-centric manner. An identity (310) maybe 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 (511 through 518) accessible by many applications (320). The data is stored in accordance with a schema that is recognized by a number of different applications and hte data service (511 through 518). When a user is to perform an operatio on the identity's (310 data, the corresponding application (320) generates a message (531) that has a structure that is recognized by the data service (511 through 518). The message (531) represents a request to perform an operation on the data structure corresponding to the identity (310). The data service (511 through 518) receives and itnerprets the message. If authorized, the data service (511 through 518) then performs the operation.