CN101661388A - Version management system, version management method, synchronous control equipment and synchronous control method - Google Patents
Version management system, version management method, synchronous control equipment and synchronous control method Download PDFInfo
- Publication number
- CN101661388A CN101661388A CN200810135535A CN200810135535A CN101661388A CN 101661388 A CN101661388 A CN 101661388A CN 200810135535 A CN200810135535 A CN 200810135535A CN 200810135535 A CN200810135535 A CN 200810135535A CN 101661388 A CN101661388 A CN 101661388A
- Authority
- CN
- China
- Prior art keywords
- local
- management system
- edition management
- local element
- project
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to a version management system, a version management method, synchronous control equipment and a synchronous control method. The version management system comprises a version management controller, a first synchronous device and a second synchronous device, wherein the first synchronous device receives and transmits a submit request to the version management controller, responds to and processes the submission request, acquires the current version and content of a local element and transmits a first notification about the update of the local element of a local item as well as the current version and content to external equipment; the second synchronous device generates a submission request for updating the local element correspondingly to provide the version management controller in response to a second notification for updating the local element of the local item and the content of the local element which are received from the external equipment, responds to andprocesses the submission request to acquire the current version of the local element and outputs the current vision to the external equipment.
Description
Technical field
The present invention relates to the version management of software scenario in the computer system, relate in particular to common element that the different editions management system managed synchronously.
Background technology
In order to develop extensive and high-quality software solution, the collaboration software exploitation is more and more general in modern software industry.Edition management system is to walk abreast and the favourable instrument of distributed software development.Edition management system generally includes the version management controller.The user can send the request of submitting this document to from client to the version management controller when finishing the editor of file.The version management controller upgrades storage and the version of this document in edition management system according to this request, and returns the processing of request result to client.
Generally speaking, software scenario can be divided into the entity of two levels.The entity of first level is called as project, and the entity of second level is called as element, and project can be made up of the element of some.According to the physical store granularity of element in the project, software scenario can be divided into two kinds.A kind of (being similar to the common web project of using html script or the like) that is based on file, wherein each element in the project is a file independently.Another kind is based on node (being similar to the Domino Application of IBM Corporation), and wherein all elements all is design elements (node) of project (for example NSF file).Correspondingly, there is the edition management system of supporting these two kinds of software scenarios.Support for example is CVS (parallel version system) based on open source code based on the edition management system of the software scenario of file, SVN (Subversion based on open source code, be version control system), the ClearCase of IBM Corporation, the StartTeam of Borland company, VisualSourceSafe of Microsoft company or the like.Support for example is the teamstudio for Domino App of IBM Corporation based on the edition management system of the software scenario of node.
For the complicated software scenario of exploitation in high quality, need launch cooperation with regard to a project by the developer of different role, and make them can use only Integrated Development Environment to come respective element in the development project.So be easy to occur such situation, promptly different developers uses respectively based on file with based on the edition management system of node and manages its project, and these projects have the common element of common exploitation.In this case, need between these edition management systems, carry out synchronously common element.
Summary of the invention
An object of the present invention is to provide a kind of edition management system, method for edition management, Synchronizing Control Devices, synchronisation control means and synchro system, its can be beneficial to carry out common element between the different editions management system synchronously.
In one embodiment of the invention, the edition management system that is used for the versions of elements of management project comprises: the version management controller, be configured to respond the submission request of the local element that is used for upgrading local project, handle the content of local element and the renewal of version; First synchronous device, be configured to receive and transmit submission to the version management controller and ask, handle the request of submitting in response to the version management controller, obtain the current version and the content of local element, and first notice that the local element of local project takes place to upgrade in an external unit transmits about edition management system, and described current version and content; Second synchronous device, be configured in response to second notice that receives the local element that is used to upgrade local project from external unit and the content of described local element, generation is used for local element is carried out the submission request of corresponding renewal and offers the version management controller, and handle the request of submitting in response to the version management controller, obtain the current version of local element, and to external unit output current version.
In one embodiment of the invention, Synchronizing Control Devices comprises: the mapping treating apparatus is configured to: first notice of renewal and the current version of local element take place in the local element that receives about local project the edition management system from edition management system; Determine to comprise in the identical mapping relations of the local element content of the local project of at least two edition management systems in the set of dissimilar edition management systems, whether have the mapping relations of the local element of the local project that relates to edition management system in the indication of being stored; With in response to determining to exist mapping relations, determine whether current version identical with the local versions of elements of being stored; And synchronous device, be configured to: the content that receives local element from edition management system; With inequality in response to the local versions of elements of determining to exist mapping relations and current version and stored, local element at the local project of each related other edition management system of mapping relations, visit information according to each other edition management system of being stored, be used to upgrade second notice of local element and the content of local element to each other edition management system transmission, wherein said mapping treating apparatus further is configured to: the current version that receives local element from each other edition management system; With the local versions of elements of being stored with the current version renewal.
In one embodiment of the invention, the method for the versions of elements of management project comprises in the edition management system: receive the submission request of the local element be used for upgrading local project; According to the content of submitting the local element of Request Processing to and the renewal of version; Upgrade in response to handling, obtain the current version and the content of local element, and first notice that the local element of local project takes place to upgrade in external unit transmits about edition management system, and current version and content; With in response to second notice that receives the local element that is used to upgrade local project from external unit and the content of local element, generation is used for local element is carried out the submission request of corresponding renewal, according to the content of the local element of the submission Request Processing that generates and the renewal of version, and upgrade in response to handling, obtain the current version of local element, and to external unit output current version.
In one embodiment of the invention, synchronisation control means comprises: receive first notice that renewal takes place about the local element of local project the edition management system from edition management system, the content and the current version of local element, determine to comprise in the identical mapping relations of the local element content of the local project of at least two edition management systems in the set of dissimilar edition management systems in the indication of being stored, existence relates to the mapping relations of local element of the local project of edition management system, and, determine whether current version is identical with the local versions of elements of being stored in response to determining to exist mapping relations; With inequality in response to the local versions of elements of determining to exist mapping relations and current version and stored, local element at the local project of each related other edition management system of mapping relations, visit information according to each other edition management system of being stored, be used to upgrade second notice of local element and the content of local element to each other edition management system transmission, receive the current version of local element from each other edition management system, and upgrade the local versions of elements of being stored with current version.
In one embodiment of the invention, synchro system comprises: at least two aforesaid edition management systems; With at least one aforesaid Synchronizing Control Devices, wherein, described at least one external unit of described at least two edition management systems is described at least one Synchronizing Control Devices.
According to embodiments of the invention, the common element in the project of managing for dissimilar edition management systems can automatically be synchronized to the renewal to common element in the edition management system in other edition management system.
Description of drawings
With reference to below in conjunction with the explanation of accompanying drawing, can understand above and other purpose of the present invention, characteristics and advantage more easily to the embodiment of the invention.In the accompanying drawings, technical characterictic or parts identical or correspondence will adopt identical or corresponding Reference numeral to represent.
Fig. 1 is the block diagram of edition management system according to an embodiment of the invention.
Fig. 2 is the block diagram of Synchronizing Control Devices according to an embodiment of the invention.
Fig. 3 is the process flow diagram of the method for edition management in the explanation edition management system shown in Figure 1.
Fig. 4 is the process flow diagram of the synchronisation control means in the explanation Synchronizing Control Devices shown in Figure 2.
Fig. 5 is the block diagram that the logical organization example of the mapping relations of being stored is shown.
Fig. 6 A and 6B show the example of the XML file of expression mapping relations.
Fig. 7 is the process flow diagram that the method for edition management in the edition management system according to another embodiment of the present invention is described.
Fig. 8 is the process flow diagram that the synchronisation control means in the Synchronizing Control Devices according to another embodiment of the present invention is described.
Fig. 9 is the block diagram of synchro system according to an embodiment of the invention.
Figure 10 is the block diagram that the exemplary configurations that wherein realizes computing machine of the present invention is shown.
Embodiment
Embodiments of the invention are described with reference to the accompanying drawings.Should be noted that for purpose clearly, omitted the parts that have nothing to do with the present invention, those of ordinary skills are known and the expression and the description of processing in accompanying drawing and the explanation.
Fig. 1 is the block diagram of edition management system 100 according to an embodiment of the invention.
As shown in Figure 1, edition management system 100 comprises version management controller 101, first synchronous device 103 and second synchronous device 104.
The user can send the submission request that is used to upgrade the element (that is local element) in the project (that is local project) that edition management system 100 managed from the client (not shown) to edition management system 100.First synchronous device 103 receives and transmits the request of submitting to version management controller 101.Version management controller 101 can be identical with the version management controller of existing edition management system, and its response is submitted request to and handled the content of the related local element of submission request and the renewal of version.
Here, the renewal of local element takes place in the edition management system 100, and this local element might have elements corresponding (promptly in other edition management system (not shown), the local element of other edition management system), therefore may need the renewal that edition management system 100 takes place is synchronized to other edition management system.Therefore, handle the submission request in response to version management controller 101, first synchronous device 103 can carry out with Synchronizing Control Devices 200 (back can be illustrated) shown in Figure 2 alternately.
Can be according to submitting to the action type information that comprises in the request to determine whether the submission request that is used to upgrade.In this case, need resolve submitting request to.Also can submit to request front and back versions of elements to determine whether the submission request that is used to upgrade by comparing 101 processing of version management controller.
First synchronous device 103 obtains the current version of the local element that upgraded and the content of local element from edition management system 100.Preferably, because the element between the different editions management system there are differences, for example element is based on the form difference that file also is based on node, at the element content that carries out transmitting mutually when synchronous Unified Form, can avoid an edition management system need understand the problem of form of the element content of other edition management system.Unified form can be for example text, XML file or the like, as long as can conveniently handle.Content at the local element that obtains does not have under the situation of Unified Form, and first synchronous device 103 can be converted into Unified Form.Under the known situation of the standard of the form of the element content that edition management system provides and Unified Form, this conversion and rightabout conversion are that those of ordinary skills can realize.Be synchronous renewal, the notice of renewal and current version that is obtained and content take place in the local element of first synchronous device 103 local project in Synchronizing Control Devices 200 transmits about edition management system 100.
As mentioned above, first synchronous device 103 is responsible for triggering synchronous opertaing device 200, and relevantly whether renewal is synchronized to other edition management system, renewal is synchronized to determining of what element in what project of what edition management system, and concrete synchro control, then be responsible for by Synchronizing Control Devices 200.
Fig. 2 is the block diagram of Synchronizing Control Devices 200 according to an embodiment of the invention.
As shown in Figure 2, Synchronizing Control Devices 200 comprises mapping treating apparatus 202 and synchronous device 203.
As previously mentioned, when an edition management system by first synchronous device will be wherein the update notification of local element during to Synchronizing Control Devices 200, Synchronizing Control Devices 200 need determine whether renewal to be synchronized to other edition management system, renewal is synchronized to what element in what project of what edition management system.
For the set that comprises some dissimilar edition management systems, if there is common element (being the identical element of content) in the local project that all edition management systems of a subclass (comprising at least two edition management systems) of this set are managed, then think to have mapping relations between this common element of this this locality project of each edition management system of this subclass.Can understand that such subclass can be more than one, thereby such mapping relations can be more than one.
Can store such mapping relations in advance, identical with each the local element content of local project of indicating at least two edition management systems in such set.Fig. 5 is the block diagram of logical organization example that the mapping relations of storage are shown.As shown in Figure 5, mapping relations 500 comprise unit 1 to unit N, and the common element of the local project that an edition management system in the subclass manages is represented in each unit.The number of unit depends on the number of edition management system in the subclass.Each unit comprises the sign SID 501 of edition management system, the sign PID 502 of project and the sign EID 503 of element.Should be understood that logical organization shown in Figure 5 is an example, can adopt other form to represent mapping relations, for example chained list, database relation table, text, XML file or the like.
For example Fig. 6 A and 6B show the example of the XML file of expression mapping relations.XML document definition shown in Fig. 6 A the mapping between the project of edition management system, node＜ProjectUUIDinBridge wherein〉definition project mapping numbering,＜InTypeAServer〉with＜InTypeBServer〉identify different edition management systems on the one hand, be the node of definition detailed programs on the other hand.Node＜ProjectUUID〉defined item purpose system banner, node＜ProjectName〉defined item purpose external name, node＜ProjectPath〉the defined item destination path.XML document definition shown in Fig. 6 B the mapping between the element of edition management system, node＜ProjectUUIDinBridge wherein〉definition project mapping numbering, node＜SynchronizedElement〉define the corresponding project mapping of this project mapping numbering mapping between the element of each edition management system down, node＜ElementUUIDinBridge wherein〉be used for the mapping between marker element, node＜Locked〉locking state that shines upon between marker element,＜InTypeAServer〉with＜InTypeBServer〉identify different edition management systems on the one hand, be the node of the concrete element of definition on the other hand.＜ElementUUID〉definition element system banner,＜ElementName〉definition element external name,＜ElementPath〉definition element the path,＜ElementVersion〉definition versions of elements.The XML file of Fig. 6 A and 6B has defined mapping relations jointly.
Referring again to Fig. 2, also can store each related local versions of elements of each mapping relations in advance, promptly nearest version, for example among Fig. 6 B＜ElementVersion value " Vers20080305-2 ".Similar with mapping relations, can and make it related by the various forms storage version with respective element.Under the situation of initially setting up mapping relations, version can be made as the value outside the normal version codomain, or element is at the actual version of edition management system separately.In addition, also can store the visit information of each related edition management system of each mapping relations, for example the addressing information of edition management system, the required authentication information of visit edition management system or the like.Similarly, can and make it related by various forms memory access information with the respective version management system.
Mapping treating apparatus 202 receives the notice of being sent by first synchronous device 103 as previously mentioned from edition management system.Mapping treating apparatus 202 is also from the current version of the related local element of first synchronous device, 103 reception notifications.According to the notice that receives, mapping treating apparatus 202 is determined to comprise in the identical mapping relations of the local element content of the local project of at least two edition management systems in the set of dissimilar edition management systems in the indication of being stored, existence relates to this mapping relations of notifying the local element of the local project that indicated edition management system manages, for example for mapping relations shown in Figure 5, if comprising, one of them unit notifies indicated edition management system, local project and local element, then these mapping relations are and will determine the mapping relations that exist.Determining to exist under the situation of such mapping relations, whether mapping treating apparatus 202 further determines to notify the current version of indicated local element identical with this this locality versions of elements of being stored.
Synchronous device 203 receives the content of above-mentioned edition management system by the local element of first synchronous device, 103 transmissions.Under the situation that mapping treating apparatus 202 determines to exist mapping relations and current version and the local versions of elements of being stored is inequality, local element for the local project of each related other edition management system of mapping relations, remove to comprise in the mapping relations for example shown in Figure 5 and notify indicated edition management system, the indicated edition management system in each other unit outside the unit of local project and local element, local project and local element, the visit information of each other edition management system that synchronous device 203 acquisitions are stored, send the notice of the local element of the local project that is used to upgrade this edition management system according to visit information to each other edition management system, also send the content that is received from first synchronous device 103.
Referring again to Fig. 1, under the situation of edition management system 100 as foregoing each other edition management system, second synchronous device 104 receives the notice that is sent by synchronous device 203 as previously mentioned.Second synchronous device 104 also receives as previously mentioned the content of the local element that is sent by synchronous device 203.Second synchronous device 104 is used for local element is carried out the submission request of corresponding renewal and offers version management controller 101 according to the submission standard generation of edition management system 100.For example, for satisfying the content-form requirement, second synchronous device 104 is local form with the content of local element from for example Unified Form or other formal transformation.Second synchronous device 104 is also handled in response to version management controller 101 and is submitted request to, obtains the current version of local element, and returns the current version that is obtained to Synchronizing Control Devices 200.
Referring again to Fig. 2, correspondingly, mapping treating apparatus 202 receives foregoing current version from second synchronous device 104, and upgrades the corresponding local versions of elements of being stored with current version.
Fig. 3 is the process flow diagram of the method for edition management in the explanation edition management system 100 shown in Figure 1.
As shown in Figure 3, method begins in step 301.In step 302, first synchronous device 103 receives the submission request of the local element that is used for upgrading local project.In step 303, version management controller 101 is according to the content of submitting the described local element of Request Processing to and the renewal of version.Then in step 304, the notice of renewal takes place in the local element of first synchronous device 103 local project in Synchronizing Control Devices 200 transmits about edition management system 100.In step 306, first synchronous device obtains the current version and the content of local element, and transmits current version and content to Synchronizing Control Devices 200.Then method finishes in step 314.
In another case, method begins in step 301.In step 307, second synchronous device 104 receives the notice of the local element that is used to upgrade local project from Synchronizing Control Devices 200.In step 309, second synchronous device 104 receives the content of local element.Then in step 310, second synchronous device 104 generates the submission request that is used for local element is carried out corresponding renewal.In step 311, version management controller 101 is according to the content of the local element of the submission Request Processing that generates and the renewal of version.In step 313, second synchronous device 104 obtains the current version of local element, and transmits current version to Synchronizing Control Devices 200.Method finishes in step 314.
Fig. 4 is the process flow diagram of the synchronisation control means in the explanation Synchronizing Control Devices 200 shown in Figure 2.
For example shown in Figure 4, suppose for the set that comprises dissimilar edition management systems, store each the identical mapping relations of local element content of local project that are used for indicating at least two edition management systems of described set in advance, and the visit information of related each edition management system of related each the local versions of elements of mapping relations and mapping relations.Certainly, if do not store foregoing, can when beginning, method store.As shown in Figure 4, method begins in step 401.In step 403, mapping treating apparatus 202 receives the notice that renewal takes place about the local element of local project the edition management system from edition management system.In step 405, mapping treating apparatus 202 and synchronous device 203 receive the content of the current version and the local element of local element respectively.In step 406, mapping treating apparatus 202 is determined to comprise in the identical mapping relations of the local element content of the local project of at least two edition management systems in the set of dissimilar edition management systems in the indication of being stored, existence relates to the mapping relations of local element of the local project of edition management system, and, determine whether current version is identical with the local versions of elements of being stored in response to determining to exist mapping relations.In step 407, mapping treating apparatus 202 is inequality in response to the local versions of elements of determining to exist mapping relations and current version and stored, local element at the local project of each related other edition management system of these mapping relations, according to the visit information of each other edition management system of being stored, send the notice that is used to upgrade local element to each other edition management system.In step 409, synchronous device 203 sends the content of local element to each other edition management system.In step 410, mapping treating apparatus 202 receives the current version of local element from each other edition management system, and upgrades the local versions of elements of being stored with current version.Then method finishes in step 413.
In front among the embodiment that describes with reference to Fig. 1, first synchronous device 103 needs to obtain under the synchronous situation and transmit contents to Synchronizing Control Devices 200 not determining whether.In fact, some local element may and have neither part nor lot in mapping relations, thereby causes the section processes ability of edition management system 100 and Synchronizing Control Devices 200 to be wasted in the processing of content.
In a further embodiment, first synchronous device 103 can transmit foregoing notice and current version to Synchronizing Control Devices 200 earlier.Whether mapping treating apparatus 202 can identical with the local versions of elements of being stored according to current version, send notice to edition management system 100, with the local element in the local project that indicates whether the renewal of local element need to be synchronized to each related other edition management system of mapping relations.First synchronous device 103 can receive this notice, and need carry out just carrying out the acquisition and the transmission of content under the synchronous situation in this notice indication.Correspondingly, synchronous device 201 only need carry out just carrying out the reception of content under the synchronous situation in this notice indication.Like this, owing to only just carry out the processing of content in the case of necessary, thereby avoid the waste of processing power.Yet the local element that present embodiment may occur upgrading also has neither part nor lot in any mapping relations but still the situation of acquisition and transmission current version.This can cause the waste of processing power equally.
In a further embodiment, first synchronous device 103 can transmit foregoing notice before the forwarding of submitting request to.Mapping treating apparatus 202 can be after reception notification, determining to exist under the situation of foregoing mapping relations, send notice to edition management system 100, may need renewal with local element to be synchronized to local element in the local project of each related other edition management system of mapping relations with indication.First synchronous device 103 is receiving under the situation of this notice, just submits the forwarding of request, the acquisition and the transmission of current version to, and the acquisition of content and transmission.Correspondingly, mapping treating apparatus 202 only under the situation that sends this notice, just carries out the reception of current version.Therefore, can further avoid the waste of processing power.
In further embodiment embodiment illustrated in fig. 1, first synchronous device 103 can receive and transmit the submission request that is used for the delete items element to version management controller 101.The submission request that the action type information that comprises in can asking according to submission determines whether to be used to delete element.Also can by handle at version management controller 101 submit request to after searching elements whether have the submission request that is used to delete of determining whether.Under the situation of the submission request that is used to delete, 103 of first synchronous devices need be in Synchronizing Control Devices 200 transmits about edition management system 100 the local element of local project the notice of deletion takes place.
Correspondingly, in further embodiment embodiment illustrated in fig. 2, mapping treating apparatus 202 receives the notice of the relevant generation deletion of being sent by first synchronous device 103 from edition management system.Whether mapping treating apparatus 202 determines to comprise in the identical mapping relations of the local element content of the local project of at least two edition management systems in the set of dissimilar edition management systems in the indication of being stored, exist to relate to the mapping relations that this notifies the local element of the local project that indicated edition management system manages.Determining to exist under the situation of such mapping relations, local element for the local project of each related other edition management system of mapping relations, synchronous device 203 obtains the visit information of each other edition management system of being stored, sends the notice of the local element of the local project that is used to delete this edition management system to each other edition management system according to visit information.
Get back to above-mentioned further embodiment embodiment illustrated in fig. 1, second synchronous device 104 receives the notice that is used to delete that is sent by synchronous device 203.According to this notice, second synchronous device 104 is used for the submission request that local element is deleted and offers version management controller 101 according to the submission standard generation of edition management system 100.
Get back to above-mentioned further embodiment embodiment illustrated in fig. 2, correspondingly, the mapping relations of existence are determined in 202 deletions of mapping treating apparatus, mapping relations for example shown in Figure 5, the version of each local element (the local element that each unit in the mapping relations for example shown in Figure 5 is indicated) that mapping relations are related and the visit information of the edition management system that other mapping relations do not relate to.
Fig. 7 is the process flow diagram of explanation according to the method for edition management in the edition management system 100 of above-mentioned further embodiment embodiment illustrated in fig. 1.
As shown in Figure 7, method begins in step 701.In step 702, first synchronous device 103 receives the submission request that is used for upgrading or deleting the local element of local project.In step 703, version management controller 101 is according to the content of submitting the described local element of Request Processing to and the renewal or the deletion of version.Then in step 704, the notice of renewal or deletion takes place in the local element of first synchronous device 103 local project in Synchronizing Control Devices 200 transmits about edition management system 100.Determine whether deletion in step 705.If then method finishes in step 714.If not, then in step 706, first synchronous device obtains the current version and the content of local element, and transmits current version and content to Synchronizing Control Devices 200.Then method finishes in step 714.
In another case, method begins in step 701.In step 707, second synchronous device 104 receives the notice that is used to upgrade or delete the local element of local project from Synchronizing Control Devices 200.Then determine whether deletion.If not, then in step 709, second synchronous device 104 receives the content of local element.Then in step 710, second synchronous device 104 generates the submission request that is used for local element is carried out corresponding renewal or deletion.In step 711, version management controller 101 is according to the content of the local element of the submission Request Processing that generates and the renewal or the deletion of version.If determine it is deletion in step 708, then forward step 710 to.After step 711, determine whether deletion in step 712.If not, then in step 713, second synchronous device 104 obtains the current version of local element, and transmits current version to Synchronizing Control Devices 200.Then, perhaps determine it is deletion in step 712, then method finishes in step 714.
Fig. 8 is the process flow diagram of explanation according to the synchronisation control means in the Synchronizing Control Devices 200 of above-mentioned further embodiment embodiment illustrated in fig. 2.
For example shown in Figure 8, suppose for the set that comprises dissimilar edition management systems, store each the identical mapping relations of local element content of local project that are used for indicating at least two edition management systems of described set in advance, and the visit information of related each edition management system of related each the local versions of elements of mapping relations and mapping relations.Certainly, if do not store foregoing, can when beginning, method store.As shown in Figure 8, method begins in step 801.In step 803, mapping treating apparatus 202 receives the notice that renewal or deletion take place about the local element of local project the edition management system from edition management system.In step 804, determine whether deletion.If not, then in step 805, mapping treating apparatus 202 and synchronous device 203 receive the content of the current version and the local element of local element respectively.In step 806, mapping treating apparatus 202 is determined to comprise in the identical mapping relations of the local element content of the local project of at least two edition management systems in the set of dissimilar edition management systems in the indication of being stored, existence relates to the mapping relations of local element of the local project of edition management system, and, determine whether current version is identical with the local versions of elements of being stored in response to determining to exist mapping relations.If determine it is deletion in step 804, then forward step 806 to.In step 807, mapping treating apparatus 202 is in response to determining to exist mapping relations (under the situation of deletion), perhaps determine current version and the local versions of elements of being stored (under news more) inequality, local element at the local project of each related other edition management system of these mapping relations, according to the visit information of each other edition management system of being stored, send the notice that is used to upgrade or delete local element to each other edition management system.Then determine whether deletion in step 808.If not, then in step 809, synchronous device 203 sends the content of local element to each other edition management system.In step 810, mapping treating apparatus 202 receives the current version of local element from each other edition management system, and upgrades the local versions of elements of being stored with current version.Then method finishes in step 813.If determine it is deletion in step 808, then in step 812, the visit information of the edition management system that each local versions of elements that the mapping treating apparatus definite mapping relations that exist of 202 deletions and this mapping relations are related and other mapping relations do not relate to.Then method finishes in step 813.
In front among the embodiment of Miao Shuing, first synchronous device 103 needs to obtain under the synchronous situation and transmit contents to Synchronizing Control Devices 200 not determining whether.In fact, some local element may and have neither part nor lot in mapping relations, thereby causes the section processes ability of edition management system 100 and Synchronizing Control Devices 200 to be wasted in the processing of content.
In a further embodiment, first synchronous device 103 can more transmit foregoing notice and current version to Synchronizing Control Devices 200 earlier under the news.Whether mapping treating apparatus 202 can basis exist foregoing mapping relations under the situation of deletion, perhaps whether identical according to current version under news more with the local versions of elements of being stored, send notice to edition management system 100, with the local element in the local project that indicates whether the renewal or the deletion of local element to be synchronized to each related other edition management system of mapping relations.First synchronous device 103 can receive this notice, and need carry out just carrying out the acquisition and the transmission of content under the synchronous situation in renewal and the indication of this notice.Correspondingly, synchronous device 201 only need carry out just carrying out the reception of content under the synchronous situation in renewal and the indication of this notice.Like this, owing to only just carry out the processing of content in the case of necessary, thereby avoid the waste of processing power.Yet the local element that present embodiment may occur upgrading also has neither part nor lot in any mapping relations but still the situation of acquisition and transmission current version.This can cause the waste of processing power equally.
In a further embodiment, under news more, first synchronous device 103 can transmit foregoing notice before the forwarding of submitting request to.Mapping treating apparatus 202 can be after reception notification, determining to exist under the situation of mapping relations, send notice to edition management system 100, may need renewal with local element to be synchronized to local element in the local project of each related other edition management system of mapping relations with indication.First synchronous device 103 is receiving under the situation of this notice, just submits the forwarding of request, the acquisition and the transmission of current version to, and the acquisition of content and transmission.Correspondingly, mapping treating apparatus 202 only under the situation that sends this notice, just carries out the reception of current version.Therefore, can further avoid the waste of processing power.
Previously described edition management system and Synchronizing Control Devices can be formed synchro system.Fig. 9 is the block diagram of synchro system 900 according to an embodiment of the invention.As shown in Figure 9, synchro system 900 comprises the edition management system 901 and 902 identical with previously described edition management system 100, with the Synchronizing Control Devices 903 identical with previously described Synchronizing Control Devices 200. Edition management system 901 and 902 and Synchronizing Control Devices 903 carry out foregoing mutual.
As previously mentioned, the edition management system managed of the Synchronizing Control Devices in the synchro system can have more than two.In addition, Synchronizing Control Devices can have more than one.Exist under the situation of a plurality of Synchronizing Control Devices, all mapping relations can be managed by different Synchronizing Control Devices.Correspondingly, edition management system also comprises storer (do not give and illustrating), be used to store the incidence relation of the Synchronizing Control Devices under the mapping relations that local element participates in, be the local element in local project and the local project and the incidence relation of Synchronizing Control Devices, and the visit information that is used to visit associated Synchronizing Control Devices, for example addressing information or the like.First synchronous device of edition management system can be according to the related local project of the submission request that is received and the incidence relation of local element and Synchronizing Control Devices, Synchronizing Control Devices that acquisition is associated and corresponding visit information, thus carry out foregoing mutual with this Synchronizing Control Devices.Certainly, storer also can be positioned at outside the edition management system, as long as can be had access to by first synchronous device.
In such synchro system,, two or more edition management systems more under the news, may cause the problem of inconsistency when participating in the local element of same mapping relations if taking place.
In a further embodiment, the mapping treating apparatus of Synchronizing Control Devices can be worked as when determining to have mapping relations under the situation of deletion, perhaps when determining that under news more current version and the local versions of elements of being stored are inequality, under the situation that mapping relations do not lock, it is locked, and under the situation that mapping relations have locked, transmit and comprise indication owing to lock failure and do not need to carry out synchronous notification of information, be synchronized to the notice of the local element in the local project of other edition management system may need renewal with local element as aforementioned indication to initiating synchronous edition management system.Correspondingly, first synchronous device of edition management system can stop submitting to processing of request in response to this notice.Under the situation that mapping relations are locked, the mapping treating apparatus can upgrade the local versions of elements stored and with mapping relations release (under news more) in response to using from current version.Can adopt various known lock technologies to realize locking of mapping relations and release, zone bit for example, signal lamp or the like.
According to embodiments of the invention, only need on existing edition management system, increase by first and second synchronous devices and just can implement a new synchro system, therefore can utilize the original version management controller of edition management system and other Module Design easily, thereby shorten the construction cycle, reduce the develop and field cost.
The realization environment of system of the present invention, unit and method as shown in figure 10.
In Figure 10, CPU (central processing unit) (CPU) 1001 is carried out various processing according to program stored among read-only mapping (enum) data (ROM) 1002 or from the program that storage area 1008 is loaded into random access mapping (enum) data (RAM) 1003.In RAM 1003, also store data required when CPU 1001 carries out various processing or the like as required.
Following parts are connected to input/output interface 1005: importation 1006 comprises keyboard, mouse or the like; Output 1007 comprises display, such as cathode ray tube (CRT), LCD (LCD) or the like and loudspeaker or the like; Storage area 1008 comprises hard disk or the like; With communications portion 1009, comprise that network interface unit is such as LAN card, modulator-demodular unit or the like.Communications portion 1009 is handled such as the Internet executive communication via network.
As required, driver 1010 also is connected to input/output interface 1005.Detachable media 1011 is installed on the driver 1010 as required such as disk, CD, magneto-optic disk, semiconductor mapping (enum) data or the like, makes the computer program of therefrom reading be installed to as required in the storage area 1008.
Realizing by software under the situation of above-mentioned steps and processing, such as detachable media 1011 program that constitutes software is being installed such as the Internet or storage medium from network.
It will be understood by those of skill in the art that this storage medium is not limited to shown in Figure 10 wherein having program stored therein, distribute separately so that the detachable media 1011 of program to be provided to the user with equipment.The example of detachable media 1011 comprises disk, CD (comprising read-only mapping (enum) data of CD (CD-ROM) and digital universal disc (DVD)), magneto-optic disk and (comprises mini-disk (MD) and semiconductor mapping (enum) data.Perhaps, storage medium can be hard disk that comprises in ROM 1002, the storage area 1008 or the like, computer program stored wherein, and be distributed to the user with the equipment that comprises them.
With reference to specific embodiment the present invention has been described in the instructions in front.Yet those of ordinary skill in the art understands, and can carry out various modifications and change under the prerequisite that does not depart from the scope of the present invention that limits as claims.
Claims (22)
1. edition management system is used for the versions of elements of management project, comprising:
The version management controller is configured to respond the submission request of the local element that is used for upgrading local project, handles the content of local element and the renewal of version;
First synchronous device, be configured to receive and transmit submission to the version management controller and ask, handle the request of submitting in response to the version management controller, obtain the current version and the content of local element, and first notice that the local element of local project takes place to upgrade in an external unit transmits about edition management system, and described current version and content;
Second synchronous device, be configured in response to second notice that receives the local element that is used to upgrade local project from external unit and the content of described local element, generation is used for local element is carried out the submission request of corresponding renewal and offers the version management controller, and handle the request of submitting in response to the version management controller, obtain the current version of local element, and to external unit output current version.
2. edition management system as claimed in claim 1, wherein,
The version management controller further is configured to respond the submission request of the local element that is used for deleting local project, deletes local element,
First synchronous device further is configured to receive and transmits this submission request to the version management controller, handle this submission request in response to the version management controller, the 3rd deleted notice of the local element of local project in external unit transmits about edition management system;
Second synchronous device further is configured to know in response to the four-way that receives the local element that is used to delete local project from external unit, generates to be used to delete the submission request of local element and to offer the version management controller.
3. edition management system as claimed in claim 1, wherein said first synchronous device further is configured at first carry out the described transmission of described first notice and described current version, receive the 3rd notice of the local element the local project indicate whether the renewal of described local element need to be synchronized to other edition management system from external unit, and need carry out the 3rd synchronous notice in response to receiving indication, carry out the described acquisition and the transmission of described content.
4. edition management system as claimed in claim 3, wherein said first synchronous device further is configured to carry out the described transmission of described first notice before the described forwarding of carrying out described submission request, know in response to the four-way that receives indication from external unit and may need renewal with described local element to be synchronized to the local element the local project of other edition management system, carry out the described acquisition and the transmission of the described forwarding of described submission request, described current version, and the described acquisition and the transmission of described content.
5. edition management system as claimed in claim 4, wherein said four-way knows that comprising indication does not need to carry out synchronous information owing to lock failure, and described first synchronous device further is configured in response to the described submission processing of request of described end-of-message.
6. edition management system as claimed in claim 1, wherein, described external unit is one of a plurality of external units, and described first synchronous device further is configured to according to the local element in local project and the local project and the incidence relation between a plurality of external unit and the visit information that is used to visit described a plurality of external units, local project in the submission request that definite existence is received and the incidence relation between local element and the described external unit, obtain described external unit and corresponding visit information in the incidence relation of described existence, and communicate by letter with described external unit foundation according to corresponding visit information.
7. Synchronizing Control Devices comprises:
The mapping treating apparatus is configured to:
First notice of renewal and the current version of local element take place in the local element that receives about local project the edition management system from edition management system;
Determine to comprise in the identical mapping relations of the local element content of the local project of at least two edition management systems in the set of dissimilar edition management systems, whether have the mapping relations of the local element of the local project that relates to edition management system in the indication of being stored; With
In response to determining to exist mapping relations, determine whether current version is identical with the local versions of elements of being stored; With
Synchronous device is configured to:
Receive the content of local element from edition management system; With
Inequality in response to the local versions of elements of determining to exist mapping relations and current version and stored, local element at the local project of each related other edition management system of mapping relations, visit information according to each other edition management system of being stored, be used to upgrade second notice of local element and the content of local element to each other edition management system transmission
Wherein said mapping treating apparatus further is configured to:
Receive the current version of local element from each other edition management system; With
Upgrade the local versions of elements of being stored with current version.
8. Synchronizing Control Devices as claimed in claim 7, whether wherein shine upon treating apparatus further is configured to according to current version identical with the local versions of elements of being stored, send the 3rd notice of the local element in the local project indicate whether the renewal of local element need to be synchronized to each related other edition management system of mapping relations to edition management system, and
Synchronous device further is configured to carry out the reception of content under the situation of the 3rd notice that sends the local element of indicating in the local project that the renewal of local element need be synchronized to each related other edition management system of mapping relations.
9. Synchronizing Control Devices as claimed in claim 8, wherein said mapping treating apparatus further is configured to:
After the reception of described first notice, in response to determining to exist mapping relations, know to the four-way that edition management system sends indication and may need renewal with local element to be synchronized to the local element in the local project of each related other edition management system of mapping relations; With
Under the situation that the transmission four-way is known, carry out the reception of current version.
10. Synchronizing Control Devices as claimed in claim 9, wherein four-way is known and is comprised indication because the failure and do not need to carry out synchronous information of locking, and the mapping treating apparatus further is configured to:
In response to determining that current version is inequality with the local versions of elements of being stored, under the situation that mapping relations do not lock, it is locked, and under the situation that mapping relations have locked, generate the four-way that comprises described information and know; With
In response to using the current version that receives from each other edition management system to upgrade the local versions of elements of being stored, with the mapping relations release.
11. Synchronizing Control Devices as claimed in claim 7, wherein,
The mapping treating apparatus further is configured to receive about the 3rd deleted notice of the local element of local project the edition management system from edition management system, determine in the mapping relations of being stored, whether to exist the mapping relations of the local element of the local project that relates to edition management system, the mapping relations of existence are determined in deletion, with each the local versions of elements that relates to by mapping relations of being stored, with the visit information of the edition management system of being stored that does not relate to by other mapping relations, and
Synchronous device further is configured in response to determining to exist mapping relations, local element at the local project of each related other edition management system of mapping relations, according to the visit information of each other edition management system of being stored, send the four-way that is used to delete local element to each other edition management system and know.
12. the method for the versions of elements of management project in the edition management system comprises:
Reception is used for upgrading the submission request of the local element of local project;
According to the content of submitting the local element of Request Processing to and the renewal of version;
Upgrade in response to handling, obtain the current version and the content of local element, and first notice that the local element of local project takes place to upgrade in external unit transmits about edition management system, and current version and content; With
In response to second notice that receives the local element that is used to upgrade local project from external unit and the content of local element, generation is used for local element is carried out the submission request of corresponding renewal, according to the content of the local element of the submission Request Processing that generates and the renewal of version, and upgrade in response to handling, obtain the current version of local element, and to external unit output current version.
13. method as claimed in claim 12 also comprises:
Reception is used for deleting the submission request of the local element of local project, according to submitting the local element of request deletion to, and submits request in response to handling this, transmits about the 3rd deleted notice of the local element of local project to external unit; With
Know in response to the four-way that receives the local element that is used to delete local project from external unit, generate and be used to delete the submission request of local element and handle this submissions and ask.
14. method as claimed in claim 12, wherein at first carry out the transmission of first notice and current version, receive the 3rd notice of the local element the local project indicate whether the renewal of local element need to be synchronized to other edition management system from external unit, and need carry out the 3rd synchronous notice in response to receiving indication, carry out the acquisition and the transmission of content.
15. method as claimed in claim 14, wherein before carrying out, carry out the transmission of first notice according to the renewal of submitting request to, know in response to the four-way that receives indication from external unit and may need renewal with local element to be synchronized to the local element the local project of other edition management system, carry out according to the renewal of submitting request to, the acquisition and the transmission of current version, and the acquisition of content and transmission.
16. method as claimed in claim 15, wherein four-way knows that comprising indication does not need to carry out synchronous information owing to lock failure, and described method also comprises in response to described end-of-message submission processing of request.
17. method as claimed in claim 12, wherein, described external unit is one of a plurality of external units, and described method also comprises:
According to the local element in local project and the local project and the incidence relation between a plurality of external unit and the visit information that is used to visit described a plurality of external units, local project in the submission request that definite existence is received and the incidence relation between local element and the described external unit, obtain described external unit and corresponding visit information in the incidence relation of described existence, and communicate by letter with described external unit foundation according to corresponding visit information.
18. a synchronisation control means comprises:
Receive first notice of upgrading about the local element generation of local project the edition management system, the content and the current version of local element from edition management system, determine to comprise in the identical mapping relations of the local element content of the local project of at least two edition management systems in the set of dissimilar edition management systems in the indication of being stored, existence relates to the mapping relations of local element of the local project of edition management system, and, determine whether current version is identical with the local versions of elements of being stored in response to determining to exist mapping relations; With
Inequality in response to the local versions of elements of determining to exist mapping relations and current version and stored, local element at the local project of each related other edition management system of mapping relations, visit information according to each other edition management system of being stored, be used to upgrade second notice of local element and the content of local element to each other edition management system transmission, receive the current version of local element from each other edition management system, and upgrade the local versions of elements of being stored with current version.
19. synchronisation control means as claimed in claim 18, wherein whether identical with the local versions of elements of being stored according to current version, send the 3rd notice of the local element in the local project indicate whether the renewal of local element need to be synchronized to each related other edition management system of mapping relations to edition management system, and
Under the situation of the 3rd notice that sends the local element of indicating in the local project that the renewal of local element need be synchronized to each related other edition management system of mapping relations, carry out the reception of content.
20. synchronisation control means as claimed in claim 19 also comprises:
After the reception of first notice, in response to determining to exist mapping relations, know to the four-way that edition management system sends indication and may need renewal with local element to be synchronized to the local element in the local project of each related other edition management system of mapping relations; With
Under the situation that the transmission four-way is known, carry out the reception of current version.
21. synchronisation control means as claimed in claim 20, wherein four-way knows that comprising indication does not need to carry out synchronous information owing to lock failure, and described method also comprises:
In response to determining that current version is inequality with the local versions of elements of being stored, under the situation that mapping relations do not lock, it is locked, and under the situation that mapping relations have locked, generate the four-way that comprises described information and know; With
In response to using the current version that receives from each other edition management system to upgrade the local versions of elements of being stored, with the mapping relations release.
22. synchronisation control means as claimed in claim 18 also comprises:
Receive about the 3rd deleted notice of the local element of local project the edition management system from edition management system, determine in the mapping relations of being stored, whether to exist the mapping relations of the local element of the local project that relates to edition management system, the mapping relations of existence are determined in deletion, visit information with each local versions of elements that relates to by mapping relations of being stored and the edition management system that does not relate to by other mapping relations stored; With
In response to determining to exist mapping relations, local element at the local project of each related other edition management system of mapping relations, according to the visit information of each other edition management system of being stored, send the four-way that is used to delete local element to each other edition management system and know.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810135535A CN101661388A (en) | 2008-08-29 | 2008-08-29 | Version management system, version management method, synchronous control equipment and synchronous control method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810135535A CN101661388A (en) | 2008-08-29 | 2008-08-29 | Version management system, version management method, synchronous control equipment and synchronous control method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101661388A true CN101661388A (en) | 2010-03-03 |
Family
ID=41789437
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200810135535A Pending CN101661388A (en) | 2008-08-29 | 2008-08-29 | Version management system, version management method, synchronous control equipment and synchronous control method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101661388A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103019718A (en) * | 2011-12-16 | 2013-04-03 | 微软公司 | Use of distributed source control in centralized source control environment |
| CN103729195A (en) * | 2014-01-15 | 2014-04-16 | 北京奇虎科技有限公司 | Control method and system for software version |
| CN105955746A (en) * | 2016-05-06 | 2016-09-21 | 中国银行股份有限公司 | Version management method and apparatus |
| CN107220010A (en) * | 2016-03-21 | 2017-09-29 | 北大方正集团有限公司 | A kind of layout file passes version safety locking method and apparatus |
| CN107704505A (en) * | 2017-08-30 | 2018-02-16 | 北京仿真中心 | A kind of project and task data method for edition management based on collaborative design |
| CN107977218A (en) * | 2017-11-23 | 2018-05-01 | 武汉斗鱼网络科技有限公司 | Code update method, device, electronic equipment and readable storage medium storing program for executing |
| CN110622156A (en) * | 2017-05-12 | 2019-12-27 | 华为技术有限公司 | Incremental graph computation for querying large graphs |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1475933A (en) * | 2003-07-29 | 2004-02-18 | 威盛电子股份有限公司 | Synchronous renew method, device and medium used on language net page data |
| CN1489052A (en) * | 2002-10-11 | 2004-04-14 | 鸿富锦精密工业（深圳）有限公司 | Multi-node file syn chronizing system and method |
| CN101167069A (en) * | 2005-04-22 | 2008-04-23 | 微软公司 | System and method for peer to peer synchronization of files |
-
2008
- 2008-08-29 CN CN200810135535A patent/CN101661388A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1489052A (en) * | 2002-10-11 | 2004-04-14 | 鸿富锦精密工业（深圳）有限公司 | Multi-node file syn chronizing system and method |
| CN1475933A (en) * | 2003-07-29 | 2004-02-18 | 威盛电子股份有限公司 | Synchronous renew method, device and medium used on language net page data |
| CN101167069A (en) * | 2005-04-22 | 2008-04-23 | 微软公司 | System and method for peer to peer synchronization of files |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103019718A (en) * | 2011-12-16 | 2013-04-03 | 微软公司 | Use of distributed source control in centralized source control environment |
| CN103019718B (en) * | 2011-12-16 | 2016-07-06 | 微软技术许可有限责任公司 | Distributed source is used to control in centralized source controls environment |
| US10025793B2 (en) | 2011-12-16 | 2018-07-17 | Microsoft Technology Licensing, Llc | Using distributed source control in a centralized source control environment |
| CN103729195A (en) * | 2014-01-15 | 2014-04-16 | 北京奇虎科技有限公司 | Control method and system for software version |
| CN107220010A (en) * | 2016-03-21 | 2017-09-29 | 北大方正集团有限公司 | A kind of layout file passes version safety locking method and apparatus |
| CN107220010B (en) * | 2016-03-21 | 2019-12-24 | 北大方正集团有限公司 | Method and device for safely locking page file transfer |
| CN105955746A (en) * | 2016-05-06 | 2016-09-21 | 中国银行股份有限公司 | Version management method and apparatus |
| CN105955746B (en) * | 2016-05-06 | 2019-03-12 | 中国银行股份有限公司 | A kind of method and device of version management |
| CN110622156A (en) * | 2017-05-12 | 2019-12-27 | 华为技术有限公司 | Incremental graph computation for querying large graphs |
| CN110622156B (en) * | 2017-05-12 | 2022-05-31 | 华为技术有限公司 | Incremental graph calculation method and device for querying large graph |
| CN107704505A (en) * | 2017-08-30 | 2018-02-16 | 北京仿真中心 | A kind of project and task data method for edition management based on collaborative design |
| CN107977218A (en) * | 2017-11-23 | 2018-05-01 | 武汉斗鱼网络科技有限公司 | Code update method, device, electronic equipment and readable storage medium storing program for executing |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200257673A1 (en) | Key pattern management in multi-tenancy database systems | |
| EP3477488B1 (en) | Deploying changes to key patterns in multi-tenancy database systems | |
| US10482080B2 (en) | Exchanging shared containers and adapting tenants in multi-tenancy database systems | |
| US10740315B2 (en) | Transitioning between system sharing types in multi-tenancy database systems | |
| US10621167B2 (en) | Data separation and write redirection in multi-tenancy database systems | |
| US10713277B2 (en) | Patching content across shared and tenant containers in multi-tenancy database systems | |
| US10452646B2 (en) | Deploying changes in a multi-tenancy database system | |
| US10320879B2 (en) | Software service discovery and service evolution management | |
| US9229890B2 (en) | Method and a system for integrating data from a source to a destination | |
| US7805420B2 (en) | Versioning and concurrency control for multiple client access of data | |
| US20190130121A1 (en) | System sharing types in multi-tenancy database systems | |
| US9244999B2 (en) | Database query using a user-defined function | |
| CN101661388A (en) | Version management system, version management method, synchronous control equipment and synchronous control method | |
| US20180373767A1 (en) | Database table conversion | |
| US11321226B2 (en) | Joint validation across code repositories | |
| US10140166B2 (en) | Message oriented middleware with integrated rules engine | |
| US20220197620A1 (en) | Deploying micro frontends to different clusters from a single repository | |
| CN110990081A (en) | Microservice registration and discovery method and device, storage medium and electronic equipment | |
| CN111782235A (en) | Data upgrading and querying method and device | |
| CN103888545A (en) | Method and device for processing global data in distributed system | |
| US8214330B2 (en) | Information processing apparatus, information processing method, and computer program product | |
| JP2018180722A (en) | Data management system | |
| CN113626007B (en) | Application method and device of connector model and server | |
| US8943517B2 (en) | Generalized application message generation service | |
| CN112948348B (en) | Operation and maintenance control method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20100303 |