694 results about "Multiple version" patented technology

Methods and apparatuses to enable the development, deployment and update of composite applications on mobile devices. In one embodiment, a method processor in a mobile device uses a workflow engine to load modules for execution according to a workflow that specifies the execution flow directions based on the outcomes of the modules. Detached object managers can be used to manage locally data that are checked out from data sources. A object manager can maintain multiple versions of the data locally, receive changes, submit changes, and / or detect conflicts. Conflicts can be resolved over time. Using a check-out check-in model, different devices can work on the same data without having to synchronize with a server sequentially. Data and workflow can be packaged together for transmission over a sometime connected network (e.g., via email) such that a method processor does not have to wait for response if the network connection is not available.

A method for controlling the interoperation of a plurality of software applications and resources includes intercepting communications from a first application to a second application or resource, directing the communication to a context management system, generating a candidate list of contexts for the communication, evaluating the candidate list according to at least one policy defined for these contexts to identify the resultant action and namespace for the communication, and performing the action as defined by the policies within the identified namespace. The method further includes tracking one or more versions of the second application, as well as tracking an evolution of application and / or resource names. The method further includes identifying one or more operations associated with a context on the candidate list, and executing the identified operations prior to a further communication.

A system and method for electronic file management includes an object-oriented file management database, a volume manager, and a coherency manager. The volume manager manages electronic files and metadata relating to the files of one or more volumes. Each volume may include folders, files, and / or other digital content. The file management system may also automatically manage versions of electronic files. This version management may be based on opening, saving, and changing of files. A user interface facilitates user interaction with the file management system. The user interface may enable a user to view, within the file management system, one or more versions of the electronic files.

In a MIMO system the signals transmitted from the various antennas are processed so as to improve the ability of the receiver to extract them from the received signal even in the face of some correlation. More specifically the number of bit streams that is transmitted simultaneously is adjusted, e.g., reduced, depending on the level of correlation, while multiple versions of each bit stream, variously weighted, are transmitted simultaneously. The variously weighted versions are combined to produced one combined weighted signal. The receiver processes the received signals in the same manner as it would have had all the signals reaching the receive antennas been uncorrelated. The weight vectors may be determined by the forward channel transmitter using the channel properties of the forward link which are made known to the transmitter of the forward link by being transmitted from the receiver of the forward link by the transmitter of the reverse link or the weight vectors may be determined by the forward channel transmitter using the channel properties of the forward link and the determined weight vectors are made known to the transmitter of the forward link by being transmitted from the receiver of the forward link by the transmitter of the reverse link. The channel properties used to determine the weight vectors may include the channel response from the transmitter to the receiver and the covariance matrix of noise and interference measured at the receiver.

A method and apparatus are disclosed for per-service flow protection and restoration of data in one or more packet networks. The disclosed protection and restoration techniques allow traffic to be prioritized and protected from the aggregate level down to a micro-flow level. Thus, protection can be limited to those services that are fault sensitive. Protected data is duplicated over a primary path and one or more backup data paths. Following a link failure, protected data can be quickly and efficiently restored without significant service interruption. A received packet is classified at each end point based on information in a header portion of the packet, using one or more rules that determine whether the received packet should be protected. At an ingress node, if the packet classification determines that the received packet should be protected, then the received packet is transmitted on at least two paths. At an egress node, if the packet classification determines that the received packet is protected, then multiple versions of the received packet are expected and only one version of the received packet is transmitted.

A cost oriented profiler (COP) mechanism that analyzes the behavior of input application source code with regard to the software total cost of ownership (TCO). The cost analysis tool provided by the mechanism analyzes the behavior of the source code and generates a cost report with indications as to the portions of the source code that have the most impact on the TCO of the application. Based on simulations and by comparing multiple versions of the source code, the COP mechanism determines if a particular change to the source code will increase or decrease software TCO. Behavior analysis, including static and dynamic analysis of the source code, is used to generate one or more code recommendations to reduce the TCO.

Multiple different versions of the same multimedia content are available to a multimedia server. An annotation server maintains annotations corresponding to the multimedia content, each such annotation corresponding to each of the different versions of the multimedia content.

A method and system for synchronizing multiple versions of multimedia objects is provided. Each multimedia object may be identified by a unique identifier. In addition, a history graph may be generated and maintained for each object, where the history graph includes nodes that store unique identifiers and whose vectors describe the relationship between the multimedia objects. Metadata may be used to describe the transformations of objects.

In accordance with the present invention, a media content management application that allows a user to customize, assemble, distribute, and track one or more versions of media content based on semantic criteria is provided.

The present invention includes systems and methods for the controlled deployment of software in a web-based environment where multiple versions of a single application are supported to provide field experience of various versions before general deployment. The systems and methods of the invention support backwards compatibility, which allows older versions of the same software to be accessed concurrently with newer (revised) versions. Likewise, data item opaqueness is supported whereby data items not recognized by a software level or tier are not rejected but are passed on to another tier or level where they may be recognized.

Techniques for delivering content to an end user device are disclosed. A policy server performs an ingest process in which multiple versions of a content object are created. The multiple versions of the content object are associated with a single network identifier which can be distributed to publishers of the content object. When the content object is requested using the single network identifier, the policy server determines a preferred version and delivery orchestration scheme from among the multiple versions for delivery to an end user device based on several criteria. The policy server may thereafter orchestrate delivery of the preferred version of the content object to the end user device. The single network identifier may be associated with an edge location in a content delivery network (CDN) and the policy server may orchestrate delivery in cooperation with servers at the CDN edge location.

Converting document formatted for use on servers to and from documents formatted for use on small devices, including synchronizing two or more versions of the document. A user may edit documents formatted for use on small devices and the documents may be synchronized with documents on the server to keep the documents up to date. In one embodiment, an n-way merge process may restore document formatting, styles and / or data features that may have been lost from one or more documents when converting from an office format to a small device format. In one embodiment, the server may provide an office productivity environment, and the documents on the server may be office documents.

A network wherein a generator is communicatively coupled to an update store or repository employs an update package container or catalog (UPC) that may be used to save information, using an XML format. The UPC may comprise update packages for one or more devices, and one or more transitions of versions for each device. The UPC may also comprise metadata information and security information associated with each the update packages. The complete update packages and associated metadata may be incorporated into an UPC, or external references to the update packages may be provided.

An exemplary adaptive Hypertext Transfer Protocol (“HTTP”) media streaming system may be configured to stream a media program from an HTTP media streaming server subsystem to a client device during an adaptive HTTP media streaming session in which predefined segments of the media program are progressively downloaded from the HTTP media streaming server subsystem to the client device by way of a network connection. For each next predefined segment of the media program to be downloaded, the server subsystem may dynamically select, based on one or more of the exemplary factors disclosed herein, a version of the next predefined segment of the media program from a plurality of versions of the next predefined segment of the media program and download the selected version of the next predefined segment of the media program to the client device. Corresponding methods and systems are also disclosed.

A Source Code Author Identifier (SCAI) automates the process of manually running a comparison to identify changes between versions of a source code file and associates identified changes with the author who made the change. After a developer identifies a segment of code in a first file, wherein the first file as a newer version of a second file, SCAI compares the segment of code in the first file to a corresponding segment of code in the second file. SCAI identifies the author of the first file whenever a difference is detected between the segment of code in the first file and the corresponding segment of code in the second file. SCAI displays the author of the first file next to the detected difference between the segment of code from the first file and the corresponding segment of code from the second file. SCAI can repeat the comparison across a plurality of versions of the file, comparing each version with the previously created version.

For two or more versions of a video with different spatial, temporal or SNR resolution, scalability can be achieved by generating a base layer and an enhancement layer. When a version of a video is available that has higher color bit depth than can be displayed, a common solution is tone mapping. A more efficient compression method is proposed for the case where the two or more versions with different color bit depth use different color encoding. The present invention is based on joint inter-layer prediction among the available color channels. Thus, color bit depth scalability can also be used where the two or more versions with different color bit depth use different color encoding. In this case the inter-layer prediction is a joint prediction based on all color components. Prediction may also include color space conversion and gamma correction.

Methods, systems, and computer program products for improving installation of software packages using a directory (such as a Lightweight Directory Access Protocol, or "LDAP", directory). A model and framework are described, where the objects of the data model may be uncoupled from the framework, allowing individual objects to be separately stored and retrieved in the directory is association with access rights or privileges. Multiple versions of each object may therefore be created and stored, and may be easily retrieved using the built-in mechanisms of the directory, when access rights which are appropriate for a particular requester are known. Optionally, built-in authentication mechanisms of the directory may be used to authenticate the requester.

An apparatus comprises a plurality of nodes interconnected as peers in a peer-to-peer network. At least some nodes are configured to update an object, thereby generating a plurality of versions of the object. Any of the plurality of nodes is configured to detect a conflict between a first version and a second version of the plurality of versions, and any of the plurality of nodes is configured to provide an indication of a resolution of the conflict to other ones of the plurality of nodes. Each version may be identified by a version descriptor that includes a version identifier (ID) and a parent version ID. If the version is the result of a conflict resolution, the version descriptor may also include a resolved version ID identifying the losing version. The resolved version ID may be used to prevent the raising of the same conflict after it has been resolved.

The present invention is directed towards systems and methods for determining the performance of a plurality of versions of a given advertisement. The method of the present invention comprises retrieving a first version of an advertisement and associated click through data, and retrieving a second version of the advertisement and associated click through data. A clickability score is calculated for the first version of the advertisement using the click through data associated with the first version, and a clickability score is calculated for the second version of the advertisement using the click through data associated with the second version. A difference in clickability scores is determined between the first and second advertisement. The clickability score associated with the first version of the advertisement is modified based upon the difference in clickability scores.

Rich-media applications are designed and created via the Internet. A host computer system, containing processes for creating rich-media applications, is accessed from a remote user computer system via an Internet connection. User account information and rich-media component specifications are uploaded via the established Internet connection for a specific user account. Rich-media applications are created, deleted, or modified in a user account via the established Internet connection. Rich-media components are added to, modified in, or deleted from scenes of a rich-media application based on information contained in user requests. After creation, the rich-media application is viewed or saved on the host computer system, or downloaded to the user computer system via the established Internet connection. In addition, the host process monitors the available computer and network resources and determines the particular component, scene, and application versions, if multiple versions exist, that most closely match the available resources.

A database may facilitate zero-downtime upgrades by concurrently maintaining multiple editions of database objects for use by both pre-upgrade and post-upgrade clients of a database application. Operations performed within the database are associated with an edition based on, for example, an initiating client or transaction. When an operation references an object or data, the database automatically performs the operation using the object or data associated with the edition with which the operation is itself associated. The database may determine the associated edition without explicit identification of the associated edition in a query or in code. Thus, no client or stored procedure code changes are necessary to reflect a new edition added during an update. Data changes in one edition may be automatically and immediately propagated to the other edition through the use of cross-edition triggers, thereby allowing both pre-upgrade and post-upgrade clients to remain fully functional throughout an upgrade.

A relationship management system stores multiple versions of contact information for a particular contact by storing the contact information that is available to all of the users of system that know a particular contact in a firm collection and by storing information about the particular contact that is available to a limited number of users that know the particular contact in one or more user collections. When changes are made to the user collection for a particular contact, the system detects the change, and based upon a number of administrative rules determines whether the change should be contributed to the firm collection. The system may automatically make the corresponding changes to each of the contact files within the firm collection or may recommend to the user whether the change should be promoted, allowing the users to accept or reject the recommendation. Preferably, each user will be provided with a default number of days to accept or reject the recommendation, after which the system may promote the contact information automatically.

An information retrieval system uses phrases to index, retrieve, organize and describe documents. Phrases are identified that predict the presence of other phrases in documents. Documents are the indexed according to their included phrases. Index data for multiple versions or instances of documents is also maintained. Each document instance is associated with a date range and relevance data derived from the document for the date range.

A security module is utilized to improve key management for encrypted files. In particular, multiple cryptographic keys may be used to encrypt multiple versions of a file, or to encrypt multiple separate files within a single encryption group for storage on an untrusted file server. An authorized user may require access to only a single cryptographic key to access the encrypted file or files. To revoke access of a user or to encrypt subsequent versions of a file, a file owner may utilize the security module to generate subsequent or new versions of the cryptographic key based on an asymmetric private key of the file owner. An authorized user may obtain a subsequent or new versions of the cryptographic key from the file owner or by other means. An authorized user may generate previous versions of the current cryptographic key based on an asymmetric public key of the file owner, without further contacting the owner. Accordingly, a single cryptographic key may be used to manage a group of files encrypted with the same key, or to manage multiple versions of a single file.

Multiple versions of a runtime system, such as a software emulation application that emulates a legacy hardware architecture, are allowed to co-exist in the memory of a new hardware architecture. The operating system software of the new hardware architecture reads configuration data from a database or table to decide which version of the runtime system is desirable for an application program or game that is being loaded or is currently running, and, if a match is found, only that runtime system is invoked. To reduce storage footprint, the different versions of the runtime system may be stored using “differential patching” techniques. In this configuration, the operating system will always launch the same basic runtime system binary, but it will select a different differential patch to apply at run-time based on the title as determined during the database lookup. In this fashion, future changes to the runtime system to correct software bugs, incompatibility issues, and the like only need to be tested for the relevant target application programs or games.

A method and system providing a distributed filesystem and distributed filesystem protocol utilizing a version-controlled filesystem with two-way differential transfer across a network is disclosed. A remote client interacts with a distributed file server across a network. Files having more than one version are maintained as version-controlled files having a literal base and at least one delta section. The client maintains a local cache of files from the distributed server that are utilized. If a later version of a file is transferred across a network, the transfer may include only the required delta sections.

A process for determining the compatibility of two or more versions of a single serialized class of objects residing on a data processing system is disclosed. The process is completed in a series of steps. First, two or more versions of the class are inputted into a process environment of the data processing system. Following this, each version of the class is divided into a serialized stream of elements. Finally, the stream of elements of one version of the class are compared with the stream of elements of another version of the class to find incompatible differences between the versions.

An apparatus for keeping several versions of a file includes a memory and an overwriting unit coupled to the memory. An initial version of the file is stored in a first area of the memory, and a current version is stored in a second area of the memory, the current version resulting from a modification of the initial version. The overwriting unit substitutes the current version for the initial version in response to a validation signal. The validation signal is produced after the current version has been permanently stored.