Abstract: A system and a method are disclosed for generating a repository to be used on a client device. The repository is generated based on a repository format supported by the client device, which is identified by analyzing an empty repository created by the client device. The generated repository is configured with metadata that allows an operating system executing on the client device to communicate with the repository. Once generated, the repository is populated with data associated with a user of the client device. The populated repository is transmitted to the client device, where the repository is used by applications for retrieving and storing data.

Abstract: A system and method are disclosed for persisting data received from disparate data sources having different internal schemas. In operation, a data processing engine aggregates related data received from the different data sources and organizes the aggregated data into flexible records. A flexible record is a composite of associated fields aggregated from a set of records received from one or more data sources. Each field associated with a flexible record includes data received from a particular data source and specifies the particular data source as the source of the data. Flexible records are stored in a storage repository, and each flexible record is associated with at least one user who accesses data via a client device.

Abstract: A system and method are disclosed for persisting data received from disparate data sources having different internal schemas. In operation, a data processing engine aggregates related data received from the different data sources and organizes the aggregated data into flexible records. A flexible record is a composite of associated fields aggregated from a set of records received from one or more data sources. Each field associated with a flexible record includes data received from a particular data source and specifies the particular data source as the source of the data. Flexible records are stored in a storage repository, and each flexible record is associated with at least one user who accesses data via a client device.

Abstract: A system and method are disclosed for persisting data received from disparate data sources having different internal schemas. In operation, a data processing engine aggregates related data received from the different data sources and organizes the aggregated data into flexible records. A flexible record is a composite of associated fields aggregated from a set of records received from one or more data sources. Each field associated with a flexible record includes data received from a particular data source and specifies the particular data source as the source of the data. Flexible records are stored in a storage repository, and each flexible record is associated with at least one user who accesses data via a client device.

Abstract: A system and a method are disclosed for generating a repository to be used on a client device. The repository is generated based on a repository format supported by the client device, which is identified by analyzing an empty repository created by the client device. The generated repository is configured with metadata that allows an operating system executing on the client device to communicate with the repository. Once generated, the repository is populated with data associated with a user of the client device. The populated repository is transmitted to the client device, where the repository is used by applications for retrieving and storing data.

Abstract: A system and method are disclosed for persisting data received from disparate data sources having different internal schemas. In operation, a data processing engine aggregates related data received from the different data sources and organizes the aggregated data into flexible records. A flexible record is a composite of associated fields aggregated from a set of records received from one or more data sources. Each field associated with a flexible record includes data received from a particular data source and specifies the particular data source as the source of the data. Flexible records are stored in a storage repository, and each flexible record is associated with at least one user who accesses data via a client device.

Abstract: Hot deployable video management modules maintain a video device management platform by integrating independently developed support for new or updated video devices at runtime. A video device module loader builds a management interface for the new or updated video device associated with the management module based on attributes and operations of the video device defined by an XML descriptor and based on access instructions. The management interface is used to create a video device instance in the management platform for each video device under management. The management platform manages a variety of different types of video devices with a video device management module added as a given video device is added to the management platform or an already managed video device is updated.

Abstract: Hot deployable video management modules maintain a video device management platform by integrating independently developed support for new or updated video devices at runtime. A video device module loader builds a management interface for the new or updated video device associated with the management module based on attributes and operations of the video device defined by an XML descriptor and based on access instructions. The management interface is used to create a video device instance in the management platform for each video device under management. The management platform manages a variety of different types of video devices with a video device management module added as a given video device is added to the management platform or an already managed video device is updated.

Abstract: A video network platform manages video network devices with management applications, such as scheduling, monitoring and diagnostics applications, by representing the devices as interface objects that support a network interface module, and application objects used by the management applications and created by an adapter engine that creates an application object for each corresponding video network device interface object. A network interface module associated with the video network platform invokes the adapter engine to create an application object associated with a device. The application object uses its dynamic attribute query capabilities to build an interface object in the network interface module and thus obtain device attributes such as device address information. The application module populates itself with device information for supporting management applications, thus allowing conventional network interface modules to cooperate with application specific objects.

Abstract: A method and system for visual configuration of a video call represents video devices as graphical icons presented through a user interface. A directed graph relates the graphical icons to represent the configuration of the video devices in the video call and ensures that compatible video devices establish a valid video configuration by prohibiting invalid video call configurations. The user interface interacts with a video network platform that schedules and initiates video calls according to video call configurations. Video device types, identification, and configuration parameters are depicted along with state information for a video call to allow monitoring and correction of failures that may occur.

Abstract: Hot deployable video management modules maintain a video device management platform by integrating independently developed support for new or updated video devices at runtime. A video device module loader builds a management interface for the new or updated video device associated with the management module based on attributes and operations of the video device defined by an XML descriptor and based on access instructions. The management interface is used to create a video device instance in the management platform for each video device under management. The management platform manages a variety of different types of video devices with a video device management module added as a given video device is added to the management platform or an already managed video device is updated.

Abstract: A method and system for visual configuration of a video call represents video devices as graphical icons presented through a user interface. A directed graph relates the graphical icons to represent the configuration of the video devices in the video call and ensures that compatible video devices establish a valid video configuration by prohibiting invalid video call configurations. The user interface interacts with a video network platform that schedules and initiates video calls according to video call configurations. Video device types, identification, and configuration parameters are depicted along with state information for a video call to allow monitoring and correction of failures that may occur.

Abstract: A video network platform manages video network devices with management applications, such as scheduling, monitoring and diagnostics applications, by representing the devices as interface objects that support a network interface module, and application objects used by the management applications and created by an adapter engine that creates an application object for each corresponding video network device interface object. A network interface module associated with the video network platform invokes the adapter engine to create an application object associated with a device. The application object uses its dynamic attribute query capabilities to build an interface object in the network interface module and thus obtain device attributes such as device address information. The application module populates itself with device information for supporting management applications, thus allowing conventional network interface modules to cooperate with application specific objects.

Abstract: A system and method for accessing and managing disparate video network devices supports a user interface with an interface protocol communicating through a management adapter. The management adapter communicates with a device access layer that represents video network devices as objects, such as Management Beans, with a class of objects associated with a type of device. The objects translate communications from the management adapter into a protocol and attributes native to the device to allow the management adapter access to device attributes, which are then available to the user interface via the interface protocol. The device access layer thus establishes a proxy relationship so that video network devices are more easily interacted with and managed by applications communicating through the management adapter by a uniform protocol.