Abstract: To enable the peer-to-peer synchronization among multiple devices, each device in the peer network keeps track of the changes it makes to any shared data and also keeps track of its own knowledge of the changes made by other devices. When two or more peer devices communicate, they share with each other their information about any changes made to the shared data by them or by other devices. This allows the devices to synchronize with each other to the extent that each of the devices knows what changes have been made by it or by other devices in the peer network.

Abstract: The invention provides discloses a method for data synchronization in a content delivery network. The method includes: a data synchronization client requesting a data synchronization processing manager for obtaining a belonged data synchronization processing agent, establishing a heartbeat connection with the belonged synchronization processing agent to acquire operation status of the belonged data synchronization processing agent; and the data synchronization processing manager scanning a management side database, and if a synchronization task needing to be informed to the data synchronization client is scanned in the management side database, the data synchronization processing manager generating the synchronization task for the corresponding synchronization processing agent in an ability side database. The present invention also provides a system for data synchronization in a content delivery network, a data synchronization processing agent and a data synchronization processing manager.

Abstract: Systems and method for distributing updates on demand to synchronize a remote client database with a source database are provided. A client can request an online update from the database content provider and the database provider can stream database updates to the client over a network connection in real time, or the database content provider can stream database updates to the client at scheduled times based on a licensing agreement with the client. This allows the client database to be kept in synch with the source database without requiring that the database provider generate a set of database updates on physical media and ship the physical media to the client for processing.

Abstract: Methods, computer systems, and computer program products for replicating data are provided. Meta-data and data associated with the meta-data are received at a first data server. A new portion of the data that is not already stored on the first data server is identified. The new portion of the data is stored on a second data server before the meta-data is stored on the second data server.

Abstract: A method switches file server from old file server to new file server which are coupled via a backend network and provides data synchronization. The old file server and new file server are coupled with one or more host computers via a frontend network to direct input/output (I/O) requests from the one or more host computers. The method comprises creating stub files in the new file server, the stub files including stub information indicating location of data in the old file server; switching I/O requests directed to old file server to I/O requests directed to the new file server; checking whether the new file server has any stub files; and, if the new file server has one or more stub files, recalling data corresponding to the one or more stub files from the old file server according to the stub information to replace the one or more stub files.

Abstract: Various methods and systems for performing data deduplication when encrypting data for storage on an untrusted storage system are disclosed. One method involves generating an encryption key for use in encrypting data and generating an identifier for the data. Generation of the encryption key is based upon a hash of the data to be encrypted. Similarly, generation of the identifier is based upon the hash of the data to be generated. For example, the identifier can be generated by hashing the encryption key. The method then involves detecting whether an encrypted copy of the data is already stored by a storage system, based upon the identifier, and selectively encrypting the data, based upon whether the encrypted copy of the data is already stored by the storage system.

Abstract: The present invention is to disclose an IP-based hometown TV program delivery system comprising at least one TV program provider for providing a plurality of channels of TV programs; and at least one agency at a server-end for providing a plurality of digital video contents converted from said corresponding TV programs; characterized in that said agency at a server-end distributes said plurality of digital video contents to authorized users at a client-end via a broadcasting network, wherein each authorized users has subscription to said TV programs so as to get permission for watching and receives from said agency said digital video contents converted from said corresponding TV programs via said broadcasting network.

Abstract: Servers in a network cluster can each store a copy of a data item in local cache, providing read access to these copies through read-only entity beans. The original data item in the database can be updated through a read/write entity bean one of the cluster servers. That cluster server has access to an invalidation target, which contains identification information relating to copies of the data item stored on servers in the cluster. Once the read/write bean updates the data item in the database, an invalidate request can be sent or multicast to all cluster members, or to any read-only bean or server contained in the invalidation target. Each server or read-only bean receiving the request knows to drop any copy of the data item in local cache, and can request a current copy of the data item from the database.

Abstract: A method for synchronizing information shared by a subsystem on-board a mobile platform and a subsystem remote from the mobile platform. The method may involve designating one of the subsystems as a first system having a first database, and designating one of the subsystems as a second system having a second database. The first subsystem may be used to transmit a synchronization request to the second subsystem, with the synchronization request including a synchronization point to be used as a reference for future synchronization operations between the subsystems. The second subsystem may be used to receive the synchronization request and to check the second database for any records that have been created or modified since a previously performed synchronization operation. Information may then be transmitted back to the first subsystem that includes information concerning the new or modified records.

Abstract: A computing device receives a request to perform a Lightweight Directory Access Protocol (“LDAP”) database operation and propagates the request to perform the LDAP database operation to a peer server to test the LDAP database operation at the peer server. The computing device executes an action on a distributed LDAP database based on a result of testing the LDAP database operation at the peer server.

Abstract: A collision detection and data synchronization mechanism operates to expand the speed and capability of distributed applications. The execution environment employs collision detection and data synchronization to distribute data objects to appropriate network nodes to support local processing. The collision detection and data synchronization mechanism defines the set of processes and algorithms used to track distributed data objects and to manage changes to the distributed objects throughout a network of intelligent computing devices. Data and code are distributed to local computing devices necessitating tracking and synchronizing updates. The system and method ensures that data updates received during the course of a local transaction do not unwillingly affect the results of other transactions by notifying the local computing devices of changes to the data that are subject of the transaction.

Abstract: A server computer system generates, for data stored in a transmission source server, index information including a data identification number, a data type, information for the data such as copyright information and an address of a server whereat the data are stored, and transmits only the index information to a hand-held information terminal carried by the owner of the transmission source server, thereby, a data transfer is requested for transferring, to a transmission destination server, data indicating the index information from the hand-held information terminal to the transmission destination server in accordance with the index information held by the hand-held information terminal and an address of the transmission destination server.

Abstract: A first and second peer devices can exchange information about a set of additional peer devices capable of providing one or more portions of one or more files. The first peer device can further communicate with the second peer device regarding specific portions of files available from the second peer device. Additionally, a subset of the set of additional peer devices available for communication can be identified based at least in part on the exchanged information. The first peer device can communicate with one or more of the identified subset of additional peer devices, at least in part, to transmit and/or receive one or more portions of one or more files. In addition, an intermittent communication between the first peer device and at least one of the set of additional peer devices can be established, at least in part, to identify another set of additional peer devices available for communication.

Abstract: Techniques to cross-synchronize data are described. An apparatus may comprise a cross-synchronization component to synchronize multiple data items for different application programs between multiple client devices synchronized using multiple synchronization circuits. The cross-synchronization component may determine whether changes to the multiple data items made at a first client device are propagated to a second client device using consistency information maintained by a consistency group item for a consistency group including the data items. Other embodiments are described and claimed.

Abstract: A peer-to-peer file sharing client with background file sharing is provided in a segmented peer-to-peer file sharing network. Each file sharing participant may designate an amount of bandwidth and/or storage space for background file sharing. Peer-to-peer file sharing clients then share file data and content in the background automatically. The client may participate in additional swarms, in the background, to generally increase the number of peers in file sharing networks, thus increasing the speed of downloading desired files for other users.

Abstract: Synchronization architectures, methods, systems, and computer readable media are described. One exemplary embodiment includes a first software component which is configured to cause retrieval and storage of structured data for a first data class from a first store of the structured data on a device, such as a first data processing system, and is configured to synchronize structured data for the first data class in the first store with structured data of the first data class in a second store on a host, such as a second data processing system. The first software component is separate from an application software which provides a user interface to allow a user to access and edit the structured data. The first software component synchronizes the structured data through a second software component which interfaces with the host and the device and which controls an order of synchronizing and a plurality of data classes including the first data class.

Abstract: According to a first aspect of the present invention there is provided a method of distributing data to peers of a peer-to-peer network to enable those peers to provide data to other peers. The method comprises predefining a minimum number of peers that are required to store a data item, sending the data item to a number of data receiving peers from one or more data servers, determining if the number of data receiving peers that have sufficient storage capacity available to store the data item is less than the predefined minimum number, and, if it is, deleting previously stored data to make sufficient storage capacity available.

Abstract: Techniques for initializing a connection in a peer-to-peer database replication environment. A message is received from an initiator node, indicating that the initiator node will begin replicating changes made to a particular data entity. One or more replicated changes relating to the database entity are received from the initiator node. If an updated instance of the data entity does not currently exist on a target node then one or more load operations are performed to create the updated instance. The stored replicated changes may then be processed against the updated instance of the database entity.

Abstract: An object of the present invention is to manage presence update by publishers that a presentity does not recognize. When the presence server 100 receives status information that indicates a status of presentity A from publisher B (#1), the presence server 100 stores it in the history table 9 and transmits a change notification to a watcher C (#3). Subsequently, the presence server 100 makes an inquiry to presentity A as to whether or not to allow an update by publisher B (#4). When it is allowed (#5, #6), publisher B is added in the allow list 8a of the allow list DB 8 (#7). Also, presence information is generated based on status information retrieved from the history table 9 (#8), is notified to the watcher C and is stored in the presence management DB 2b (#9, #10). When it is denied (#11), publisher B is added in the deny list 8b of the allow list DB 8 (#12). Also, status information received from publisher B is deleted from the history table 9.

Abstract: A directory includes information about various systems (e.g., applications, processes, tasks, objects, services) and data, and may include data ownership information. The directory may define existing systems, corresponding locations by address, and corresponding semantic names. The directory may also specify the role of each system, e.g., a consumer or provider role. The directory may also define a scope of data a provider system can provide. As such, the directory may also include information about whether and how such data is being replicated. When a user requests data, a service may, based on the directory, determine and select an appropriate provider system for the data. The service may further create a subscription process to provide the user a local cache of the requested data. With such directory information, a service can provide data access services that integrate subscription processes.

Abstract: Generating a standby index on a standby database server in a physical log-shipping data replication environment. Embodiments of the invention include providing a primary database server and a standby database server, replicating a primary database and a primary database index from the primary database server to the standby database server, generating a standby index on the standby database server, and cataloging the standby index on the standby database server.

Abstract: The present application provides a storage apparatus for storing data. The storage apparatus comprises storage means for storing data, committing means for committing the availability of a certain storage space to a source device, detecting means for detecting the availability of the certain storage space to produce a detection result, and communication means for informing the source device the detection result, whereby the source device takes corresponding action(s) according to the detection result. In this way, each storage device of a group is bound by its commitment, if it violates its commitment, it risks the loss of its file(s) stored on other members' storage space.

Abstract: Embodiments of the invention are generally related to data processing, and more specifically to retrieving results for a query from one or more devices coupled to a network. A first device may receive an abstract query including logical fields defined by a first data abstraction model and retrieve query results stored in the first device. The query may be sent to one or more other devices via the network. The one or more other devices may be configured to convert the abstract query to local abstract queries including logical fields defined in local data abstraction models. The local queries may be issued against local databases to retrieve additional results for the query.

Abstract: The claimed subject matter is directed to a file system watcher in the presence of different file systems to allow synchronization of replicated files distributed among different file systems without compromising the features of each file system. To synchronize the distributed replications, a platform independent synchronization manager creates a file system watcher for each file system associated with a replication of the file. The file system watcher monitors each object for events affecting the object or the object's constituent files, such as creation, deletion, change and rename. Notifications are sent to the synchronization manager, which consolidates the modifications and updates a locally stored replication, if necessary. The synchronization manager then sends a notification of an update to all other synchronization managers for all replications of the distributed file or folder.

Abstract: A message-based replication system hosted by a first directory server receives update data describing an update to be made to a lightweight directory access protocol (LDAP)-based database that is coupled to the first directory server and determines whether the data is received from an advanced message queuing protocol (AMQP) server. The message-based replication system converts the update data into LDAP data format based on a determination that the update data is received from the AMQP server and updates the database using the LDAP update data. The message-based replication system updates the database using the received update data based on a determination that the update data is not received from the AMQP server, converts the update data into wire level data format, and publishes the wire level update data to the AMQP server to allow a second directory server that subscribes to the AMQP server to obtain data representing the update.

Abstract: A method and apparatus for capturing database system workload and replaying that workload in a database system is provided. According to one aspect, in order to subject a test database system to the same workload to which the production database system actually would be subjected, a database server in the production system captures and records workload that the database server receives from external entities. This captured workload is processed. Processes external to a database server in the test database system send the processed workload to that database server. As a result, the test database system is subjected to the same workload to which the production database system originally was subjected. The foregoing technique permits a database administrator to determine how the production database system will fare if the difference that is present in the test database system is introduced into the production database system.

Abstract: Operating a parallel database server system, where the database server system comprises at least two database servers and one data source. A client identifier is received from a client requesting services from one of said database servers. Information associated with said client is retrieved. The client is allocated to one of said database servers based on the retrieved information.

Abstract: The claimed subject matter provides a system and/or a method that facilitates managing an incoming data communication in connection with unified communications. A unified communications component can employ unified communications for a data communication with at least the following data communication modes: an email data communication mode, a voice data communication mode, and a voicemail data communication mode. A unified rules component can automatically redirect the data communication to a delegate for receipt based upon a universal rule, the universal rule is uniformly applicable to at least two of the email data communication mode, the voice data communication mode, or the voicemail data communication mode.

Abstract: Localization architecture is provided with a scalable server and a client side repository for shared user interface localization, which may be implemented in a client/display target environment. User interface localization repository is maintained server-side as a source for full or partial distribution. Content for user interface localization repository may be received from authorized partners for one or multiple client installations, and is protected against tampering.

Abstract: A method and apparatus for remote searching of data stored on a communication device is provided. The communication device is generally in communication with a server for tracking data associated with the communication device and data associated with a synchronizable computing device, synchronizable with the communication device. An index of data stored at the communication device is maintained at the server, the index for distinguishing the data stored at the communication device from data stored at the synchronizable computing device. A searchable copy of data stored on the communication device cross-referenced to the index is maintained, the searchable copy searchable using search parameter data received from the communication device to produce search results transmittable back to the communication device.

Abstract: An organizational management tool that involves a limited yet expansive amount of interconnectable nodes within a unique network. A node in the context of the present invention is an apparatus such as a computer that communicates with a database server (DBS). The interaction between such nodes complies with a set of functional rules and topological considerations. An apparatus such as a computer that is not connected to the DBS and has an internet access referred to hereinafter as an external node. External nodes are connectable to the system of the invention usually through non-specific communications channels such as regular email connections. Any node can be defined by the administrator as being either senior or junior with respect to another node. This hierarchical feature together with other features dictates specific task flow properties and connectivity characteristics between nodes, as well as data access of nodes to main data base.

Abstract: A multi-tiered replicated process database and corresponding method are disclosed for supporting replication between tiers. The multi-tiered replicated process database comprises a tier one (T1) database server computer including a process history database and a replication service. The replication service includes a set of accumulators. Each accumulator is adapted to render a summary T2 database tag data structure from a set of data values retrieved from the process history database for a specified T1 database tag. The replicated database system also includes a tier two (T2) database server computer comprising a consolidated database that includes process data replicated from a set of T1 database servers. At least a portion of the process data replicated from the set of T1 database servers is summary T2 database tag data rendered by the set of accumulators.

Abstract: Provided are a computer program product, method, and system for migration of metadata and storage management of data in a first storage environment to a second storage environment. A migration request is processed to migrate metadata and storage management of data in a first storage environment to a second storage environment, wherein the first storage environment has a first storage server, a first storage media, and first metadata describing first data objects stored in the first storage media, and wherein the second storage environment has a second storage server, a second storage media, and second metadata for second data objects stored in the second storage media. The first metadata is copied to the second storage environment to incorporate with the second metadata. The first metadata incorporated into the second metadata is modified to indicate first server information used by the second server to communicate with the first server to access the migrated data from the first storage media.

Abstract: A proprietary portable audio player system for protecting digital content copyrights, which includes a proprietary portable audio player, a web access interface, and an online music server. The proprietary portable audio player has a hardware unique device identity. The proprietary portable audio player has a playback token acquirement mode and uses a first transmission medium to link with the online music server to thereby obtain a playback token for a corresponding music file playback. The online music server pre-stores a plurality of music files with compression formats, a plurality of playback tokens, and a mapping table. When a playback token signal from the web access interface is received, the online music server accordingly issues a playback token corresponding to a specific music file, updates the mapping table, and sends the playback token to the proprietary portable audio player through the first transmission medium.

Abstract: A file containing proprietary content can be protected against unauthorized duplication via file sharing between remote computers connected to an Internet swapping service. To this end, the content to be protected is searched on the Internet, at least the hash ID of each data record offered as a search hit is stored, this hash ID is linked to substitute content data, and queries of remote computers for the file to be protected are responded to by offering the modified data record.

Abstract: Systems and methods for synchronization including the use of a global equivalency identification datum or set of datum. A universally unique identification datum may be associated with each independently created associated data set. In some embodiments, a synchronization server software element may be responsible for maintaining synchronization for a plurality of clients, including software elements or devices. A record believed to be new by the software elements may verify that the record is actually new. In some embodiments, verification of the record's newness involves assuming that the local ID is a global identification datum and comparing that datum to the all the sets of datum that the Sync-Server knows about. The synchronization server software element may use a table to hold information for all of the records known to that element. In some embodiments these records may have been deleted in the past.

Abstract: The present invention discloses a centralized backup system for a non-local homogeneous real-time system, comprising a switch (302), and a host (301), an encryptor (303), a PC monitor (304), and a firewall (305) which connect with the switch. The present invention ensures the reliability of the non-local systems and is able to allocate resources flexibly to meet the requirement of the tasks of system in each location different greatly with each other by centralized deployment and centralized management of backup systems in all locations.

Abstract: Various embodiments of the present invention are directed to synchronization utilizing one or more optimizations through the utilization of metadata. For several embodiments of the present invention, one method for optimizing synchronization is to reduce the overhead required for said synchronization by having each peer only tracking changes for itself and other peers within its change community (or communities) (a.k.a., “Intra-Community-Only Change Tracking Optimization”). For certain embodiments of the present invention, another method for optimizing synchronization is to not create synchronization overhead until required. For numerous embodiments of the present invention, yet another method for optimizing synchronization is to minimize redundant use of a partner's unique global ID—a large and cumbersome number—and to instead maintain a table that cross-references each partner (and its unique global ID) with a smaller and much less cumbersome partner key.

Abstract: A distributed peer-to-peer document archival system provides the version-control, security, access control, linking among stored documents and remote access to documents usually associated with centralized storage systems while still providing the simplicity, personalization and robustness to network outages associated with personal and peer-to-peer storage systems.

Abstract: Techniques are described for replicating data from one to one or more heterogeneous data processing or communication devices for the purpose of remote backup, redundancy, content distribution, communications, observations or measurements. In a first phase, the attributes of the data that are modified or created on a device or that are passing through the device are tracked and journaled in volatile or non-volatile storage in real-time. In a second phase, the attributes that match patterns pre-specified in a configuration are used to determine which data to replicate and which modifications to make the devices. In a third phase, the data is replicated. In a preferred embodiment, the described techniques comprise an application that runs on a host device or is embedded in a logic or memory device. The described invention is designed to be transparent for system redundancy and error recovery processes such as error correction, re-transmission on links, and raid configuration.

Abstract: Architecture for restoring nodes. After restoring a node, fix-up occurs to make the node appears as a different node than before the restore operation. The node appears as a new node, which new node knows the data up to a certain point from when the new node had the prior identity. This allows for new changes generated by the new node to flow to the other nodes in the topology, as well as have the changes that the prior identity sent to other nodes flow back to the new node. In other words, the architecture maintains information to create the new node in the topology while maintaining prior data knowledge. Additionally, item level metadata of associated data items is updated to correlate with the updated data items so that changes can be correctly enumerated and applied. This metadata update occurs across scopes of which the data items are included.

Abstract: A system and method for actively validating a network device is provided. Nodes in a network game community are prompted to engage in interrogation and response to facilitate the identification of nodes operating with hacked, modified and non-typical game configurations. In one embodiment, a query is presented to a user's machine which triggers a response, and where the response indicates whether certain data at the user is valid and wherein invalid data is suggestive of illegal community behavior. Functions are triggered and data is queried to determine whether the state of game environment is operating according to known metrics or constraints. Various queries to test user integrity include memory peeks, confirmation of location of functions in memory, memory hashing, profiling of threads operating on the user machine, and combinations thereof.

Abstract: The present invention generally relates to log message processing such that events can be detected and alarms can be generated. For example, log messages are generated by a variety of network platforms (e.g., Windows servers, Linux servers, UNIX servers, databases, workstations, etc.). Often, relatively large numbers of logs are generated from these platforms in different formats. A log manager described herein collects such log data using various protocols (e.g., Syslog, SNMP, SMTP, etc.) to determine events. That is, the log manager may communicate with the network platforms using appropriate protocols to collect log messages therefrom. The log manager may then determine events (e.g., unauthorized access, logins, etc.) from the log data and transfer the events to an event manager. The event manager may analyze the events and determine whether alarms should be generated therefrom.

Abstract: A system and method for dependency management are provided. The system for dependency management, includes a provider object management module managing a provider object that provides information, a consumer object management module managing a consumer object that executes a predetermined task based on the information provided by the provider object, an information object management module managing an information object that manages the provider object and the consumer object based on the information, a dependency storage module storing dependency information between the provider object and the consumer object, and a dependency management module examining dependency between the provider object and the consumer object based on the dependency information that is received from the dependency storage module and controlling activation and deactivation of the provider object and the consumer object according to a result of the dependency examination.

Abstract: A composite storage server employs a plurality of distributed storage sites including a mount site, a source copy site and one ore more copy target sites for executing a storage of volume data within the composite storage server. In operation, a deferred copy target site receives a communication of a source copy complete message from the mount site, the source copy complete message being indicative of the source copy site having a complete copy of the volume data, and detects a transition by the mount site of the host job from an active status to an inactive status subsequent to the communication of the source copy complete message from the mount site. Based on the inactive status of the host job, the deferred copy target site pulls the volume data from a peer distributed storage site having a complete copy of the volume data.

Abstract: An information distribution system is provided with a plurality of information processing devices that are capable of communication with each other via a network, and that store shared information so that the information can be shared by the plurality of information processing devices. The shared information is shared information that has a public release time that is before the current time.

Abstract: Tools and techniques are described for synchronization and collaboration within peer-to-peer and client/server environments. These tools may provide methods that include establishing peer-to-peer relationships between two or more client systems. These relationships enable the client systems to create respective local instances of workspaces, shared between the client systems to allow them to collaborate with one another. The client systems may participate in peer-to-peer synchronization flows with one another, with the synchronization flows representing updates made local to the shared workspaces of the client systems. The methods may also establish establishing a client/server relationship between one of the client systems and a server system. Through this client/server relationship, the client and server systems may participate in client/server synchronization flows, with these flows representing updates made to the local shared workspace at the client system.

Abstract: Multiple computer devices are networked, and each computer device stores a bookmark database. A user can add delete or change bookmarks on any of the computer devices. Alterations made to a bookmark database are stored locally. Every alteration is time stamped. If a bookmark is deleted, it is marked as deleted, but not erased from the local bookmark database. Bookmark databases stored on other computer devices are unaffected by changes made to the bookmark database stored on the local device. In order to update and synchronize all the bookmark databases, the local device receives the data from all the other bookmark databases. Then, the time stamps for each bookmark are compared, and the bookmarks with the most recent time stamps are assembled in a new master bookmark database. The new master bookmark database is then sent to all participating devices in the network.

Abstract: A method replicates data between instances of a distributed database. The method identifies at least two instances of the database at distinct geographic locations. The method tracks changes to the database by storing deltas. Each delta has a row identifier that identifies the piece of data modified, a sequence identifier that specifies the order in which the deltas are applied to the data, and an instance identifier that specifies where the delta was created. The method determines which deltas to send using an egress map that specifies which combinations of row identifier and sequence identifier have been acknowledged as received at other instances. The method builds a transmission matrix that identifies deltas that have not yet been acknowledged as received. The method then transmits deltas identified in the transmission matrix. After receiving acknowledgement that transmitted deltas have been incorporated into databases at other instances, the method updates the egress map.

Abstract: A server computer at a first storage sub-system of a distributed storage system receives from a client a first client request for an object. If the object is not present in the first storage sub-system, the server computer identifies a second storage sub-system of the distributed storage system as having a replica of the requested object, the requested object including content and metadata. The server computer submits an object replication request for the requested object to the second storage sub-system and independently receives the content and metadata of the requested object from the second storage sub-system. The server computer generates a new replica of the object at the first storage sub-system using the received metadata and content and returns the metadata of the new replica of the object to the client.