834 results about "Version management" patented technology

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 multi-node computer system, a software version management system is described having a version manager for ensuring that cluster nodes running completely incompatible software are unable to communicate with each other. The version manager provides a mechanism for determining when nodes in the cluster are running incompatible software and providing a way for determining the exact version of software that each node must run. The version manager provides support for rolling upgrades to enable the version management software to ensure the chosen version of software that runs the cluster stays constant even though the software installed on individual nodes is changing.

A system and related techniques provide a seamless, peer-to-peer file synchronization capability for sharing files, folders, directories or other stored content between machines. According to embodiments of the invention in one regard, a sync engine or other file management logic may be integrated into the operating system or other resources of a user's desktop, laptop, network-enabled cellular device or other computer, client, machine or other hardware. The sync engine may accept user designations of files, folders, directories or other contents which they wish to share, sync or roam between two or more selected machines, on an automatically consistent basis. The sync engine or other control logic may maintain a file system log to record the state of files which have been designated for sharing, to indicate for example whether a transmission of the file has been made, to which target machine or machines it has been transmitted, and other variables regarding the state of file or other content. According to embodiments of the invention in one regard, the sync engine may apply version management logic when files located on a target or destination machine, may, for example, reflect newer or more complete content than the file which is designated for roaming to that machine, or other under conditions. A user may therefore readily and with a comparative minimum of configuration effort select and effectuate the sharing of a set of frequently used or otherwise desired files to an arbitrary set of machines which they own or use, without a need to invoke a remote server or other control or storage to back up and synchronize that content.

A communication apparatus obtains file information indicating all or a part of first and second encrypted pieces obtained by encrypting a plurality of pieces constituting a part of a content and version management information with which it is possible to judge whether the file information has validity and receives, for each of the pieces, one of the first encrypted piece and the second encrypted piece from another communication apparatus, by using the file information. The communication apparatus transmits, to a key server, a request message for requesting decryption keys each being used for decrypting the one of the first encrypted piece and the second encrypted piece received for a different one of the pieces and the version management information of the file information used to obtain the one of the first encrypted piece and the second encrypted piece in correspondence with each of the pieces and receives the decryption keys.

The present invention relates to a fine-granularity files and directory edition management method based on snapshots, belonging to the multi-version document system field. The present invention separates a name space consisting of files and dirnames in a whole file system from an edition space representing the generating periods of different editions, and adopts relatively independent strategies to execute management, forming a hierarchical two-dimensional structure, i.e. forming a hierarchical structure from a root directory to a file in the name space; in the edition space, the editions of files and directory are organized through an index structure chronologically, forming a hierarchical structure in the edition space. The retrieval of the name space adopts an index strategy based on dynamic hash. The retrieval of the edition space adopts an index strategy based on a red-black tree. The directory edition and file edition respectively adopt a red-black tree structure variant aiming at the respective characteristics. The present invention can greatly improve the usability and the performance of the system, and controls the amount of consumption of time and space resulting from the maintenance of historical editions in an acceptable scope.

Network service version management techniques are disclosed. Service access information, which is associated with access to a network service by a network service user, may be destined for a particular version of the network service. A determination is made as to whether a different version of the network service is accessible by the network service user. If so, then a further determination is made as to whether to select the different version of the network service to process the service access information. Any inconsistency between versions of the network service, such as different information requirements, can be handled by transforming received service access information. A replay function may also be provided, to have service access information again processed by the same or a different version of a network service. This function may be useful, for example, where a version of a service is rolled back or for debugging.

The invention provides a software update system and a method. The software update method provided by the invention comprises the following steps: an update strategy module sets an update strategy according to information of a query version management module; the update strategy module checks whether the current version of a client is in line with the update strategy or not after the client logs in a server and returns a check result to the client; the client starts an update execution module to initiate the software update when being in line with the update strategy; and the update execution module downloads an update software package from the server and executes the update. When a fault occurs, the update software package is replaced by a fault repair package, and the software update method can be utilized for realizing the fault repair. The software update process and the fault maintenance process can become simpler and more controllable by setting the update strategy through the software update system and / or the method, and the practical effects are very significant.

An element management system in which: a list of fully-qualified versions of network elements is maintained, and the interface to each network element is managed in accordance with the highest fully-qualified version which is no later than the network element's actual version date, EVEN IF there is also a fully-qualified later version. By specifying a “managed level” which is fully qualified and is guaranteed not to be later than the actual revision of the network element, the possibility of hidden incompatibility is reduced. (Network elements are expected to be backwards compatible, but the addition of features may introduce some hidden forward incompatibility.).

A system and method for automatically updating software components on a running computer system without requiring any interruption of service. A software module is hotpatched by loading a patch into memory and modifying an instruction in the original module to jump to the patch. A coldpatching technique places a coldpatch version of the module on disk for subsequent loading by processes, after hotpatching occurred. The coldpatch has the entry points to its functions at the same relative locations within the module as the hotpatch, which facilitates subsequent hotpatching. A hotpatch and coldpatch are automatically generated by deriving differences between changed and original binary files, and establishing the point to insert the jump. Validation is performed to ensure that the hotpatch is applied to the correct version, and that the coldpatch is replacing the correct version. Version management is also provided to control the number of patches via support rules.

A computer readable medium storing a media editing application for creating media presentations is described. The application includes a graphical user interface (GUI). The GUI has (1) a composite display area for displaying graphical representations of a set of media clips that are part of the composite presentation, (2) a navigation tool including several selectable navigation markers associated with several navigable locations in the composite presentation, and (3) a version management feature for (a) indicating whether each location has been modified, (b) providing an option to create a new version of each location, and (c) providing access to previously-saved versions of each location.

The version management method according to the present invention by a computer system comprises a repository server 2 and a user terminal 1. The repository server 2 executes a procedure that the file to be updated within the user repository 26 are updated by the user terminal 1, a procedure that the files to be updated within the user repository 26 are updated so as to write the files to be updated on the system repository 22, and a procedure that the file to be updated within the system repository 22 are read by the arbitrary user terminal 1.

The invention provides a software-upgrading method. An upgrading platform constructed by the method is independent of software and is independently applied in different products or projects, and when the upgrading platform is in use, a platform client automatically seeks a patch server and acquires a patch package from the patch server; the platform automatically checks the validity of patches, supports breakpoint continuous transmission, completes downloading and verification, and then executes patch-upgrading operation; the patches are automatically downloaded or manually downloaded in the platform according to defined tasks; and automatic upgrading and manual upgrading are executed according to defined tasks. The method has the advantages that the patch package is described by use of description language and analyzed; common compression processing used for the patches is rapid in transmission, safe and reliable, can eliminate the occurrence of network data blockage and other situations, and can discover problems when the patches are downloaded and installed in time; the method solves the problems of software updating, version management of different clients, automatic downloading-updating, and the like, and can meet the upgrading requirements of various types of software in different platforms.

The embodiment of the invention discloses a configuration file management method and system, and the method comprises the steps: building the communication connection between a node in a zookeeper cluster and a client; analyzing a generated configuration file updating instruction, so as to determine that the node, corresponding to the configuration file updating instruction, in the zookeeper cluster as a target node; storing the new configuration file in the target node, and making the backup of the new configuration file in a configuration file database; updating the configuration file of the client connected with the target node after the configuration file stored in the target node changes; obtaining a historical configuration file version corresponding to the target node from the configuration file database after the fault information fed back by the client connected with the target node is received, so as to update the target node and update the configuration file database. According to the embodiment of the invention, the method carries out the synchronization and version management of a configuration file in a distributed system.

Disclosed is a version management device which comprises a file access verification unit that receives a request packet sent from the client and a response packet sent from the server, extracts a processing request and a response result from the packets, and checks if the processing request and the response result match an access pattern corresponding to a file data update processing operation by an application running on the client; a user management unit that manages user information in a format defined for each file access protocol to verify from which user the processing request, included in the request packet from the client, is issued; a version control unit that controls the creation operation of a version management file when it is found that an operation corresponding to processing pattern corresponding to file data update processing by the application running on the client is executed in the file access verification unit; and a setting information management unit that holds operation setting information required by the file access verification unit, the user management unit, and the version control unit for their operation.

A software version management system comprising a host driver and at least one software module. The host driver comprises migration means to start, stop and replace the software modules on a computer system in response to replacement actions. The system is characterized by the software module being a downgradable software module comprising a compatibility database specifying dependencies between different versions of the software module; the migration means further comprising i) at least a status means to retrieve temporal information from the downgradable software module; ii) at least a downgrading means responsive to a replacement action to downgrade the downgradable software module to a particular downgrade version and to the status means, the downgrading means identifying an intermediate version of the downgradable software module; the host driver comprising restarting means responsive to the report of the completion of the intermediate version to load and start the downgrade version of the software module.

The invention discloses a design and configuration integrated system for an intelligent substation, which is technically convenient for information management for the intelligent substation in design, construction, operation and maintenance stages to reduce workload for checking staff. The design and configuration integrated system is arranged in a personal computer which is networked with switches of an electric power designing institute, an intelligent substation construction organization, an electricity authority, an intelligent substation operating maintenance department and a secondary equipment manufacturer. The system is provided with an intelligent substation design drawings module, a configuration management module, a model base module, a drawings management module, a retrieval module, a permission management module, a verification module, a database module and a version management module. Compared with the prior art, the design and configuration integrated system has the advantages that design and configuration are integrated, risks of errors of design and configuration are lowered, design and configuration efficiency of the intelligent substation is improved while an effective secondary data management tool is provided for operation and maintenance, repeated operations are avoided, and workload is greatly reduced for the checking staff.

Efficient differencing and update mechanisms operate directly on the native representation of the data. No irrelevant differences are introduced by the process. The difference reports generated are stated in terms of the basic operations that can be performed on a data tree, thus requiring no additional interpretation, and making it amenable to direct human inspection and understanding. This mechanism can become a central part of any version management system.

The invention relates to a software upgrading system applied in an Android platform terminal; the software upgrading system comprises a server software version information acquisition module, a client software version information acquisition module, a software version comparison module, a downloading module and an installing module, wherein the server software version information acquisition module is used for acquiring a server software version information list; the client software version information acquisition module is used for acquiring a client software version information list; the software version comparison module is used for comparing server software version information and client software version information and generating an upgrading and updating list; the downloading module is used for downloading upgrading packets from a software version management server according to the upgrading and updating list; and the installing module is used for installing the upgrading packets to finish the software upgrading. The invention also discloses a software upgrading method. According to the technical scheme of the invention, software in the Android platform terminal can be upgraded and updated in a centralization and batching manner.

Creating a relational database table that identifies at least one application as belonging to a logical group. All components that belong to the logical group are listed and a unique schema name is created for each component by combining a logical schema name of each component with a designated system name for the component. Each component co-exists in a single database instance.

A computer system comprises a server. The server, in turn, comprises one or more master instances of an operating system (OS). The OS comprises a set of computer program files to operate a computer. The server also includes a version-managing program maintaining the one or more master operating systems. The computer system also includes a number of client computers each of which is configured to operate using one of the one or more master operating systems as read-only files.

A computer-readable recording medium containing an application management program for automatically performing version management to surely manage versions of a client application that communicates with a server application. A communication request monitor acquires a communication request issued from a terminal device to a server, and extracts version information of a client application from the communication request. An upgrade determination unit determines whether the extracted version information shows the latest version, and determines that upgrade is necessary if the version is not the latest version. A setting file transmitter sends the communication request to the server if the upgrade determination unit does not determine that the upgrade is necessary. If the upgrade is necessary, on the contrary, the setting file transmitter discards the communication request and sends the client application setting file for the latest version to the terminal device sending the communication request.

The invention provides a graphical data model managing method based on metadata. The method comprises the steps of utilizing a metadata management tool to collect metadata and set up a metadata base, utilizing a logic data model modeling tool and citing the metadata to set up a logic model, utilizing a physical data model modeling tool to generate a physical model through mapping of the logic model, and generating model data corresponding to a database table. The graphical data model managing method is realized through a graphical interface. The invention further provides a corresponding graphical data model managing system based on metadata. Based on the management and the application of metadata, the method and system manage metadata flexibly according to systems and classification, effectively manage the properties of metadata, integrate metadata and models, utilize data repeatedly, reduce data redundancy, and bring convenience to version management.

The invention provides a terminal equipment remote software version distribution method and system. A version link list is maintained for each set of terminal equipment managed by the system, the terminal equipment programs are supported to be split according to any number of software component types easy to manage, the version link list is established for each type of software component, different software component types have separately independent upgrading lines, and upgrading of all types of software components is not mutually dependent; a group policy mode is utilized, and automatic upgrading after registration of new equipment within group range can be supported; and a software distribution agent side acquires the real version number of the software components through the agreed program interface or system storage data to be matched with the version number recorded in a server side so that authenticity and uniqueness of the version link list can be guaranteed. Fine control and management of terminal equipment remote software distribution and unified version management can be efficiently, safely and conveniently performed.

The invention generally relates to document management, including the management of documents and versions of documents within collaboration and document sharing systems. An access tracking version manager according to the invention allows document versions to be stored and managed in situations where various people have access to different document versions within a document chain.

The embodiment of the invention discloses a software development system and a method and relates to the technical field of computer software development. The invention aims to solve the problem of slow software development progress due to no uniform management in the software development process of the prior art. The technical scheme provided by the invention comprises a creating module, a version management module, a submitting module, a test module and a defect management module, wherein the creating module is arranged at a client and is used for creating a program code; the version management module is arranged at a server and is used for storing the program code created by the creating module; the submitting module is arranged at the client and is used for transmitting the program code created by the creating module to the version management module; the test module is arranged at the client and is used for acquiring the program code from the version management module so as to carry out testing; and the defect management module is arranged at the server and is used for storing a program code defect acquired from the test module. The technical scheme provided by the invention can be used in the technical field of java development.

The invention discloses a data file incremental updating method, a server, a client and a system, which are used for improving the incremental updating efficiency, reducing the complexity of version management, and simplifying an incremental updating process. The data file incremental updating method includes: acquiring a new version of a data file, and acquiring a plurality of file blocks corresponding to the new version of the data file according to the new version of the data file; calculating a new version block proof test value of each file block according to the plurality of file blocks; and writing the new version block proof test value of each file block, and a file name and a download address corresponding to the new version of the data file in a configuration file, and providing the configuration file for a client so as to allow the client to complete incremental updating according to the configuration file.

The invention discloses a version upgrade and backup method for terminal through accessing an USB memory equipment. The upgrade method comprises following procedures: reading data file through accessing the USB memory equipment with data file to trigger the terminal; updating or upgrading through decryption identification before updated or upgraded version is applied. The backup method comprises procedures as follows: accessing the USB memory equipment to the terminal triggered before current data file is generated for the terminal and encrypted. The invention has the advantages of enabling local business configuration management and version management through accessing the USB storage equipment to the USB interface of the terminal when the operator cannot perform remote management for the terminal through other management mode; when the terminal is connected with the remote management system of the operator and is under management status, the terminal can report the status such as report reading, updating, applying and backing up of corresponding file on the USB storage equipment under the mode to the management system for statistics and failure diagnosis in the future.