CN114879889A - Processing method, device, revocation system, electronic equipment and storage medium - Google Patents

Processing method, device, revocation system, electronic equipment and storage medium Download PDF

Info

Publication number
CN114879889A
CN114879889A CN202210494599.3A CN202210494599A CN114879889A CN 114879889 A CN114879889 A CN 114879889A CN 202210494599 A CN202210494599 A CN 202210494599A CN 114879889 A CN114879889 A CN 114879889A
Authority
CN
China
Prior art keywords
version number
revocation
container
information
native
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.)
Granted
Application number
CN202210494599.3A
Other languages
Chinese (zh)
Other versions
CN114879889B (en
Inventor
陈聪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Mihoyo Tianming Technology Co Ltd
Original Assignee
Shanghai Mihoyo Tianming Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shanghai Mihoyo Tianming Technology Co Ltd filed Critical Shanghai Mihoyo Tianming Technology Co Ltd
Priority to CN202210494599.3A priority Critical patent/CN114879889B/en
Publication of CN114879889A publication Critical patent/CN114879889A/en
Application granted granted Critical
Publication of CN114879889B publication Critical patent/CN114879889B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04845—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range for image manipulation, e.g. dragging, rotation, expansion or change of colour
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/02—Input arrangements using manually operated switches, e.g. using keyboards or dials
    • G06F3/0202—Constructional details or processes of manufacture of the input device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
    • G06F3/033—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor
    • G06F3/0354—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor with detection of 2D relative movements between the device, or an operating part thereof, and a plane or surface, e.g. 2D mice, trackballs, pens or pucks
    • G06F3/03543—Mice or pucks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The embodiment of the invention discloses a processing method, a processing device, a revocation system, electronic equipment and a storage medium. The method is applied to an auxiliary revocation module in a serialized revocation system, wherein the auxiliary revocation module stores a container containing a first version number set and a second version number set, and the container is used for storing an operation set, and the method comprises the following steps: receiving operation callback information of a native revocation device, acquiring a current first version number and a current second version number, and comparing the first version number with the second version number; and responding the operation callback information according to the comparison result of the first version number and the second version number and the operation stored in the container. The embodiment of the invention realizes the revocation or the revocation of the non-serialized operation such as the user-defined operation or the extended operation in the serialized revocation system. The auxiliary revocation device and the native revocation device are compatible with each other, and the situation that the revocation and anti-revocation operations ignore the inputted editing operation is avoided.

Description

Processing method, device, revocation system, electronic equipment and storage medium
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a processing method, a processing device, a revocation system, electronic equipment and a storage medium.
Background
In an editing process in an editable system, an editing process for a target object is realized by inputting an editing operation, wherein the editing operation and the editing object may be different based on an editing system. Because there are requirements for undo and undo for the inputted editing operation in the editing process, the editing process can be realized by inputting undo operation and undo operation, and the flexibility of the editing process is improved.
In a serialized revocation system, for example, a unity system, revocation and revocation can only be implemented on operations that can be serialized in the system, and revocation cannot be implemented on all editing operations, especially non-serialized operations.
Disclosure of Invention
The embodiment of the invention provides a processing method, a processing device, a revocation system, electronic equipment and a storage medium, which are used for realizing revocation and revocation of non-serialized operations in a serialized revocation system.
According to an aspect of the present invention, there is provided a processing method applied to a secondary revocation module in a serialized revocation system, where the secondary revocation module stores a container containing a first version number set and a second version number set, and stores a set of operations, the method including:
receiving operation callback information of a native revocation device, acquiring a current first version number and a current second version number, and comparing the first version number with the second version number;
and responding the operation callback information according to the comparison result of the first version number and the second version number and the operation stored in the container.
According to another aspect of the present invention, there is provided a secondary revocation module, in which a module is stored, the module being configured to store a container including a first version number set and a second version number set, and a container configured to store an operation set;
the version number information reading module is used for receiving operation callback information of the original revocation device and acquiring a current first version number and a current second version number;
the version number comparison module is used for comparing the first version number with the second version number;
and the operation response module is used for responding the operation callback information according to the comparison result of the first version number and the second version number and the operation stored in the container.
According to another aspect of the present invention, a revocation system is provided, which includes a native revocation device and an auxiliary revocation device, wherein the native revocation device executes a preset operation when detecting the preset operation, generates operation callback information, and sends the operation callback information to the auxiliary revocation device;
the auxiliary revocation device receives operation callback information of the native revocation device, responds to the operation callback information, obtains a current first version number and a current second version number, compares the first version number with the second version number, and responds to the operation callback information according to a comparison result of the first version number and the second version number and an operation stored in the container so as to execute the preset operation.
According to another aspect of the present invention, there is provided an electronic apparatus including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the processing method of any of the embodiments of the invention.
According to another aspect of the present invention, there is provided a computer-readable storage medium storing computer instructions for causing a processor to implement a processing method according to any one of the embodiments of the present invention when the computer instructions are executed.
In the technical solution provided in this embodiment, by setting an auxiliary revocation device, the auxiliary revocation device records version number information corresponding to each non-serialized operation in the editing process, and is driven by a native revocation device, and when a preset operation of a revocation operation or an anti-revocation operation on a non-serialized operation is detected, determines the type of the input preset operation based on a comparison result of a first version number and a second version number, and further executes the revocation operation or the anti-revocation operation based on operation information stored in a container, thereby implementing revocation or anti-revocation on a non-serialized operation such as a custom operation or an extended operation in a serialized revocation system. The primary revocation system is assisted by the auxiliary revocation device, secondary development of the primary revocation system is not needed, and development cost is reduced. Furthermore, the auxiliary revocation device is driven by the original revocation device, the auxiliary revocation device and the original revocation device are compatible with each other, an input mode of revocation operation or anti-revocation operation does not need to be set independently, and the condition that the input editing operation is ignored is avoided.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic flow chart of a processing method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an auxiliary revocation apparatus according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a revocation system according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device in an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Fig. 1 is a flowchart of a processing method according to an embodiment of the present invention, where the present embodiment is applicable to a situation where revocation and revocation of non-serialized operations are implemented in a serialized revocation system, and the method may be implemented by an auxiliary revocation apparatus provided in an embodiment of the present invention, where the auxiliary revocation apparatus may be implemented by software and/or hardware, and the auxiliary revocation apparatus may be configured on an electronic computing device. The processing method provided in this embodiment is applied to an auxiliary revocation module in a serialized revocation system, where the auxiliary revocation module stores a container that includes a first version number set and a second version number set, and is used for storing an operation set.
The revocation operation and the anti-revocation operation of the editor by the serialized revocation system are realized by serializing data, and the system for realizing the revocation operation and the anti-revocation operation in the above way is a serialized revocation system. Exemplary serialization revocation systems include, but are not limited to, unity systems.
For example, in the editor, the position of the object a is modified through an editing operation, that is, the X coordinate is modified from 100 to 200, the serialization revocation system serializes the information of the object before and after editing, and compares the serialized contents before and after editing to obtain a differentiated serialized content, that is, by way of example only, without representing the true situation, "the X coordinate of the position of the object a" is modified: 100, after the modification: 200 "and storing the different serialized contents. When the undo operation is executed, the different serialized contents corresponding to the undo operation are read from the stored read serialized contents, the object A and the X coordinate of the position of the object A are determined according to the different serialized contents, and the 100 before modification in the different serialized contents is set to the X coordinate, so that the undo operation is realized. Similarly, the revocation operation is a reverse process of the above process, and is not described here again.
Taking the unity system as an example, the serialization revocation system realizes revocation and revocation through serialization of data, and the following requirements exist: object needs to be inherited from unity engine and revoked fields need to be serializable. The above requirements limit the scope of revocation applications native to Unity, i.e., revocation and revocation cannot be performed for fields that are completely custom data, cannot be serialized.
In some embodiments, the editing operation type can be added to the serialized revocation system in a manner of performing secondary development on the serialized revocation system, so as to improve the editing capability of the system and improve the convenience of editing by a user. The editing operation (i.e., the extension operation) added by the secondary development may be a non-serialization operation, and the serialization revocation system cannot perform serialization processing on data generated by the extension operation, i.e., revocation and revocation reversal cannot be achieved. Illustratively, editing operations such as adding images, deleting images, adjusting image positions and the like belong to original operations of a serialized revocation system, operations such as performing face segmentation on images and performing beautification processing on objects in the images for the serialized operations belong to extension operations of the serialized revocation system, and the operations are non-serialized operations. It should be noted that, for different serialized revocation systems, the serialized operation may be different, and further, for any serialized revocation system, the non-serialized operation obtained according to the development requirement may be different and determined according to the development requirement. Non-serialized operations in the serialized revocation system can be determined at the development stage, and in some embodiments, a non-serialized operation container can be created in advance for storing the non-serialized operations in the serialized revocation system to facilitate matching. In some embodiments, a nonserializing flag may be set for a nonserializing operation to identify whether the input operation is a nonserializing operation. In some embodiments, a judgment module may be created in advance, and a judgment rule of the non-serialized operation is configured in the judgment module to identify whether the input editing operation is the non-serialized operation.
In this embodiment, the serialized revocation system includes a native revocation device and an auxiliary revocation device. The native revocation device and the auxiliary revocation device are matched to realize the revocation and the revocation of any editing operation in the serialized revocation system, wherein any editing operation can be a serialized operation and a non-serialized operation. The primary revocation device revokes and revokes the serialization operation, and the primary revocation device and the auxiliary revocation device revoke and revoke the serialization operation through information interaction.
When the editing operation is detected, the editing operation is judged, and the operation type of the editing operation is determined, wherein the operation type can be a serialization operation type and a non-serialization operation type. Optionally, identifying the operation type of the editing operation based on a preset judgment module; optionally, identifying an operation identifier in the editing operation, and matching the operation identifier of the non-serialized operation with the operation identifier in the editing operation to determine whether the editing operation is the non-serialized operation; optionally, the editing operation is matched with the non-serialized operation in the non-serialized operation container, when the matching is successful, the editing operation is determined as the non-serialized operation, and when the matching is failed, the editing operation is determined as the serialized operation. Here, the determination method of the operation type of the editing operation is not limited, and the determination may be performed according to a judgment rule.
When the editing operation is a serialization operation, the native revocation device serializes data of the serialization operation to obtain and store serialized content corresponding to the serialization operation. For example, the native revocation apparatus may store serialized content corresponding to each editing operation through a preset serialized content storage list. The serialization content corresponding to the serialization operation may be change data caused by the serialization operation, or description information of the change data, and the like, which is not limited herein.
In the case that the editing operation is a non-serialized operation, the native revocation device is triggered to generate new version information, and the new version information is transmitted to the auxiliary revocation device. The auxiliary revocation device is provided with a first version number set, a second version number set and a container for storing the operation set. Under the condition that the auxiliary revocation device receives the newly added version information sent by the original revocation device, respectively increasing a first version number in the first version number set and a second version number in the second version number set; and storing the operation associated with the new version information into the container. The first version number set and the second version number set are respectively used for storing file version numbers formed by various editing operations, and the first version number set is controlled by the native revocation device, so that access of the native revocation device can be received, and the first version numbers stored in the first version number set are updated; the second set of version numbers is not controlled by the native revocation device and cannot receive access by the native revocation device.
And in the case that the new edition operation is a non-serialized operation, the original revocation device is triggered to generate new edition information, the new edition information can comprise a preset identifier so as to facilitate identification of the auxiliary revocation device, wherein the new edition information is preset, a generation rule of the new edition information is set in the original revocation device, and an identification rule of the new edition information is set in the auxiliary revocation device. The auxiliary revocation device updates a first version number in the first version number set and a second version number in the second version number set based on the newly added version information, wherein the first version number serializebleversion and the second version number nonseillizedversion are respectively shaping fields, and the initial values are 0. Correspondingly, the auxiliary revocation device responds to the newly added version information and respectively adds a first version number in the first version number set and a second version number in the second version number set. Illustratively, the current first version number and the current second version number are respectively 3, the current first version number and the current second version number may be respectively adjusted to 4 based on the newly added version information, or a newly added version number of 4 may be respectively added to the first version number set and the second version number set based on the newly added version information.
The auxiliary revocation device stores the operation associated with the newly added version information into the container, the container is a set for recording editing operation, and optionally, the container stores all the editing operation; optionally, the operation information recorded in the container may be the operation information of the editing operation, wherein the operation information includes the operation type and the operation data, for example, the operation information may include the key "a", the delete "B", the add image M, and the like, wherein A, B, M is only an example, and may be changed according to the specific data of the editing operation. It should be noted that the operation information stored in the container may be provided with an identifier, where the identifier may be a serial number identifier, and the serial number may be a first version number/a second version number corresponding to the operation.
In some embodiments, an editing operation may correspond to a plurality of operation information, for example, the editing operation is a batch operation, which may implement synchronous processing on a plurality of data, and correspondingly, the editing operation corresponds to a plurality of operation information, and the identifiers corresponding to the operation information are the same, so that when performing revocation and revocation, it is convenient to perform batch revocation and batch revocation based on the plurality of operation information.
On the basis of the above embodiment, in order to avoid that a native revocation device skips unnumbered operations when performing revocation and revocation, version number change information is registered in the native revocation device according to version number change information in the first version number set and the second version number set. The first version number and the second version number in the exemplary first version number set and second version number set are both changed from A1 to A2, and correspondingly, the version number change information may be A1-A2. The version number change information includes version number information before change and version number information after change, and the setting mode of the version number information before change and the version number information after change in the version number change information is not limited, for example, the version number information before change can be connected through a "-" symbol, and the version number information after change can be connected after the "-" symbol; for example, the connection may be made based on a "/" symbol, and the like, which is not limited.
The version number change information is registered in the native revocation apparatus, for example, the version number change information is stored in a serialized content storage list as serialized content corresponding to the non-serialized operation to characterize the corresponding operation as the non-serialized operation, and the native revocation apparatus is triggered to call the auxiliary revocation apparatus to respond to the revocation operation or the anti-revocation operation.
An operation user inputs an undo operation or an undo operation through a keyboard, a mouse or a touch screen, and exemplarily determines that the undo operation is detected when a shortcut key such as ctrl + Z is pressed, and determines that the undo operation is detected when the shortcut key such as ctrl + Y is pressed; for example, when a cancel control or an anti-cancel control in a system display page is clicked through a mouse or a touch screen, it is determined that a cancel operation or an anti-cancel operation is detected.
The native revocation apparatus, upon detecting a revocation operation or an anti-revocation operation, determines corresponding serialized content in a serialized content storage list. Optionally, a pointer may be set in the serialized content storage list, when a revocation operation is detected, determining the serialized content corresponding to the current pointer as the serialized content corresponding to the revocation operation, and after the revocation operation is performed, moving the pointer to the position of the previous serialized content; when the anti-revocation operation is detected, determining the next serialized content of the current pointer position as the serialized content corresponding to the anti-revocation operation, and after the anti-revocation operation is executed, moving the pointer to the next serialized content position. Optionally, the serialized contents in the serialized content storage list correspond to timestamps or sequence number identifiers, and when a revocation operation is detected, the serialized contents corresponding to the maximum timestamps or the serialized contents corresponding to the maximum sequence number identifiers are determined as the serialized contents corresponding to the revocation operation. In some embodiments, a revocation list may be set to store revoked serialized contents, and accordingly, after a revocation operation is performed, the serialized contents corresponding to the maximum timestamp or the serialized contents corresponding to the maximum serial number identifier are moved to the revocation list; after the anti-revocation operation is detected, determining the serialized content corresponding to the maximum timestamp or the serialized content corresponding to the maximum serial number identifier in the revocation list, and after the anti-revocation operation is executed, moving the serialized content corresponding to the maximum timestamp or the serialized content corresponding to the maximum serial number identifier to the serialized content storage list.
When the serialized content is not version number change information, indicating that the editing operation corresponding to the revocation operation or the anti-revocation operation is the serialization operation, the native revocation apparatus executes the revocation operation or the anti-revocation operation based on the read serialized content. When the serialized content is version number change information, it indicates that the editing operation corresponding to the revocation operation or the anti-revocation operation is non-serialized operation, and the native revocation device cannot implement the revocation operation or the anti-revocation operation.
The native revocation apparatus accesses the auxiliary revocation apparatus based on the version number change information to update the first version number in the first version number set. The auxiliary revocation device receives access generated by a native revocation device based on a preset operation input from the outside so as to update the first version number in the first version number set. The preset operation is a revocation operation or an anti-revocation operation, the primary revocation device reduces the first version number through the access auxiliary revocation device under the condition that the preset operation is the revocation operation, namely the first version number is reduced by one, and the primary revocation device increases the first version number through the access auxiliary revocation device under the condition that the preset operation is the anti-revocation operation, namely the first version number is increased by one. It should be noted that the premise of performing the anti-undo operation is that the previous operation is an undo operation, and in the case that the previous operation is not an undo operation, the detected anti-undo operation is an invalid operation.
And when the native revocation device reads the version number change information, the executed revocation operation or the anti-revocation operation is invalid operation, operation callback information is generated, and the callback information is sent to the auxiliary revocation device.
On the basis of the above embodiment, the auxiliary revocation device responds to the operation callback information, and performs a revocation operation to cancel the operation, thereby realizing revocation or revocation of the non-serialized operation.
The method specifically comprises the following steps:
s110, receiving operation callback information of a native revocation device, acquiring a current first version number and a current second version number, and comparing the first version number with the second version number.
And S120, responding to the operation callback information according to the comparison result of the first version number and the second version number and the operation stored in the container.
In this embodiment, in the process of continuously inputting the editing operation from the outside, the first version number in the first version number set and the second version number in the second version number set are increased in synchronization and are in the same state. After the primary revocation apparatus accesses the secondary revocation apparatus based on the revocation operation or the anti-revocation operation, the first version number is updated, resulting in the first version number and the second version number being different.
The auxiliary revocation device receives operation callback information transmitted by the native revocation device, reads the first version number and the second version number from the first version number set and the second version number set, and compares the first version number with the second version number. The comparison result of the first version number and the second version number comprises that the first version number is larger than the second version number, and the first version number is smaller than the second version number.
When the first version number is smaller than the second version number, the first version number is reduced by the access of the native revocation device, namely the currently detected prediction operation is a revocation operation; in the case that the first version number is greater than the second version number, it indicates that the access of the first version number by the native revocation apparatus is increased, i.e., the currently detected prediction operation is an anti-revocation operation.
Correspondingly, responding the operation callback information according to the comparison result of the first version number and the second version number and the operation stored in the container, and the method comprises the following steps: if the comparison result is that the first version number is larger than the second version number, performing a reverse revocation operation based on the association operation in the container; and if the comparison result shows that the first version number is smaller than the second version number, executing a revocation operation based on the associated operation in the container.
And storing each input editing operation in a preset container, and reading the corresponding editing operation, namely the association operation, from the container based on the comparison result of the first version number and the second version number so as to execute the revocation operation or the anti-revocation operation. Specifically, based on the comparison result between the first version number and the second version number, the corresponding association operation is matched from the container, and the association operation is an editing operation corresponding to a larger version number of the first version number and the second version number. Illustratively, the first version number is 3, the second version number is 4, the comparison result corresponds to a revocation operation, that is, the version number 4 is revoked to the version number 3, and the change between the version number 3 and the version number 4 is realized by an editing operation corresponding to the version number 4, that is, on the basis of the version number 3, the version number 4 is obtained by executing the editing operation 4, that is, the association operation is an editing operation corresponding to the second version number 4. Illustratively, the first version number is 4, the second version number is 3, the comparison result corresponds to an undo operation, that is, an undo operation is performed from version number 3 to version number 4, and correspondingly, the association operation is an editing operation corresponding to the first version number 4, that is, an undone editing operation 4.
The undo operation is realized by performing the association operation in the reverse direction, and the undo operation is realized by performing the association operation in the forward direction. Correspondingly, performing operation revocation based on the associated operation in the container includes: and determining version number change information according to the comparison result, matching association operation in the container based on the version number change information, and executing the association operation in the forward direction. And performing, by the processor, an undo operation based on the associated operation in the container, including: and determining version number change information according to the comparison result, matching association operation in the container based on the version number change information, and reversely executing the association operation.
Illustratively, the association operation is to modify "a" into "B", and then the revocation operation is implemented by modifying "B" into "a", the premise of the revocation operation being that the current information has been modified into "a", and correspondingly, the revocation operation is implemented by modifying "a" into "B". Illustratively, the association operation is typing "M", the revocation operation is implemented by deleting the typed "M", the anti-revocation operation is premised on the typed "M" having been deleted, and correspondingly, the anti-revocation operation is implemented by re-typing "M". The terms "a", "B" and "M" are merely illustrative, and may be text, image, audio, video, attributes of any object, and the like, and may be different according to actual data of an editing operation, which is not limited thereto.
On the basis of the above embodiment, after performing the undo operation or the undo operation, the method further includes: and adjusting a second version number in the second version number set to be the same as the first version number. Illustratively, the second version number is incremented after performing the anti-undo operation on the basis that the first version number is greater than the second version number. And on the basis that the first version number is smaller than the second version number, reducing the second version number after the revocation operation is executed. By adjusting the second version number to be the same as the first version number after performing a revocation operation or an anti-revocation operation, the identification and execution of the next revocation operation or anti-revocation operation is facilitated.
In some embodiments, the serialized revocation system may include a plurality of editing pages, each editing page may correspond to a set of the first version number set, the second version number set, and the container, and when a new added editing page is created, a set of empty first version number set, second version number set, and container is created, so that the editing operations input in each editing page may be revoked or revoked without mutual interference. And under the condition that the editing page is closed or the system is cancelled in a serialization manner, the corresponding first version number set, the corresponding second version number set and the corresponding container are cleared, so that the occupation of the memory is reduced.
In the technical solution provided in this embodiment, by setting an auxiliary revocation device, the auxiliary revocation device records version number information corresponding to each non-serialized operation in the editing process, and is driven by a native revocation device, and when a preset operation of a revocation operation or an anti-revocation operation on a non-serialized operation is detected, determines the type of the input preset operation based on a comparison result of a first version number and a second version number, and further executes the revocation operation or the anti-revocation operation based on operation information stored in a container, thereby implementing revocation or anti-revocation on a non-serialized operation such as a custom operation or an extended operation in a serialized revocation system. The primary revocation system is assisted by the auxiliary revocation device, secondary development of the primary revocation system is not needed, and development cost is reduced. Further, the auxiliary revocation device is driven by the native revocation device, the auxiliary revocation device and the native revocation device are compatible with each other, it is not necessary to separately set an input mode (for example, a new shortcut key) for the revocation operation or the anti-revocation operation, and it is avoided to ignore the inputted editing operation.
The auxiliary withdrawing device is further provided on the basis of the embodiment. Referring to fig. 2, fig. 2 is a schematic structural diagram of an auxiliary revocation apparatus according to an embodiment of the present invention, where the apparatus includes:
a storage module 210, configured to store a container including a first version number set and a second version number set, and a container for storing an operation set;
the version number information reading module 220 is configured to receive operation callback information of a native revocation device, and obtain a current first version number and a current second version number;
a version number comparison module 230, configured to compare the first version number with the second version number;
an operation response module 240, configured to respond to the operation callback information according to a comparison result between the first version number and the second version number and an operation stored in the container.
Optionally, the apparatus further comprises:
a version number updating module, configured to increase a first version number in the first version number set and a second version number in the second version number set respectively when new version information sent by the native revocation apparatus is received;
and the operation updating module is used for storing the operation related to the new version information into the container.
Optionally, the apparatus further comprises:
and the version number registration module is used for registering version number change information in the native revocation device according to the version number change information in the first version number set and the second version number set.
Optionally, the apparatus further comprises:
and the version number updating module is used for receiving an access generated by the native revocation device based on an externally input preset operation before receiving operation callback information of the native revocation device so as to update the first version number in the first version number set.
Optionally, the operation response module 240 includes:
a first response unit, configured to execute a reverse revocation operation based on an association operation in the container if the comparison result indicates that the first version number is greater than the second version number;
a second response unit, configured to execute a revocation operation based on an association operation in the container if the comparison result indicates that the first version number is smaller than the second version number.
Optionally, the first response unit is configured to determine version number change information according to the comparison result, match an association operation in the container based on the version number change information, and execute the association operation in a forward direction;
the second response unit is used for determining version number change information according to the comparison result, matching association operation in the container based on the version number change information, and reversely executing the association operation.
The auxiliary revocation device provided by the embodiment of the invention can execute the processing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of executing the processing method.
On the basis of the above embodiment, a revocation system is further provided, referring to fig. 3, and fig. 3 is a structural schematic diagram of the revocation system provided by the embodiment of the present invention. The system comprises: the revocation method comprises a native revocation device 310 and an auxiliary revocation device 320, wherein the native revocation device 310 executes a preset operation when detecting the preset operation, generates operation callback information, and sends the operation callback information to the auxiliary revocation device 320;
the auxiliary revocation device 320 receives operation callback information of the native revocation device 310, acquires a current first version number and a current second version number in response to the operation callback information, compares the first version number with the second version number, and responds to the operation callback information according to a comparison result of the first version number and the second version number and an operation stored in the container to execute the preset operation.
The native revocation apparatus 310 determines, when detecting the revocation operation or the anti-revocation operation, corresponding serialized content in a native list (i.e., a serialized content storage list), and, when the serialized content is version number change information, triggers, based on the preset operation, access to the auxiliary revocation apparatus 320 to adjust, based on the preset operation, the first version number in the first version number set. If the preset operation is a revocation operation, the first version number is decremented by one by accessing the auxiliary revocation device 320, and if the preset operation is a revocation operation, the first version number is incremented by one by accessing the auxiliary revocation device 320.
In the case that the serialized content is version number change information, the native revocation device 310 performs a preset operation, generates operation callback information, and triggers the auxiliary revocation device 320 to perform the preset operation through the operation callback information. The auxiliary revocation device 320, upon receiving the operation callback information, reads the current first version number and the current second version number, compares the two, and invokes a corresponding associated operation from the container based on the comparison result to execute a preset operation. Specifically, if the comparison result indicates that the first version number is greater than the second version number, performing a revocation operation based on an association operation in the container; and if the comparison result shows that the first version number is smaller than the second version number, executing a revocation operation based on the associated operation in the container.
Optionally, the auxiliary revocation device 320 is configured to: determining version number change information according to the comparison result, matching association operation in the container based on the version number change information, and executing the association operation in the forward direction; and determining version number change information according to the comparison result, matching association operation in the container based on the version number change information, and reversely executing the association operation.
In this embodiment, the auxiliary revocation device 320 is provided to assist the native revocation device 310, so as to implement revocation and revocation of non-serialized operations. The non-serialized operation is a custom operation or an extended operation besides the native editing operation in the serialized revocation system, and can be used for realizing secondary development of the serialized revocation system, and is not limited to the native editing operation in the serialized revocation system, further, the native revocation device 310 is compatible with the auxiliary revocation device 320, so that an input mode based on the revocation operation and the anti-revocation operation in the serialized revocation system is realized, and the non-serialized operation is revoked and anti-revoked.
On the basis of the above embodiment, the native revocation apparatus 310 is further configured to, in a case where a serialization operation is detected, record operation information of the serialization operation in a native list; and, in case of detecting the non-serialized operation, generating new version information and sending the new version information to the auxiliary revocation device 320; the auxiliary revocation device 320 receives the new version information sent by the native revocation device 310, respectively adds a first version number in the first version number set and a second version number in the second version number set, and stores an operation associated with the new version information into the container.
Optionally, the auxiliary revocation device 320 is further configured to: registering version number change information in the native revocation apparatus 310 according to version number change information in the first version number set and the second version number set.
Optionally, the system further includes a determining module, configured to identify an operation type of the external input operation, and send the operation type to the native revocation apparatus 310, where the operation type includes a serialized operation and a non-serialized operation.
FIG. 4 shows a schematic block diagram of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 4, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM)12, a Random Access Memory (RAM)13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM)12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 may also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. The processor 11 performs the various methods and processes described above, such as the processing method.
In some embodiments, the processing method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the processing method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the processing method by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
It is to be noted that the foregoing description is only exemplary of the invention and that the principles of the technology may be employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (17)

1. A processing method applied to a secondary revocation module in a serialized revocation system, wherein the secondary revocation module stores a container containing a first version number set and a second version number set, and stores a set of operations, the method comprising:
receiving operation callback information of a native revocation device, acquiring a current first version number and a current second version number, and comparing the first version number with the second version number;
and responding the operation callback information according to the comparison result of the first version number and the second version number and the operation stored in the container.
2. The method of claim 1, further comprising:
under the condition of receiving newly added version information sent by the original revocation device, respectively increasing a first version number in the first version number set and a second version number in the second version number set;
and storing the operation associated with the new version information into the container.
3. The method according to claim 2, wherein the new version information is generated by triggering the native revocation apparatus when the determining module detects a non-serialized operation inputted from outside.
4. The method of claim 2, further comprising:
and according to version number change information in the first version number set and the second version number set, registering the version number change information in the native revocation device.
5. The method of claim 2, further comprising, prior to receiving operation callback information of a native revocation device:
and receiving access generated by the native revocation device based on a preset operation input from the outside so as to update the first version number in the first version number set.
6. The method of claim 1, wherein the responding to the operation callback information according to the comparison result of the first version number and the second version number and the operation stored in the container comprises:
if the comparison result is that the first version number is larger than the second version number, performing a reverse revocation operation based on the association operation in the container;
and if the comparison result shows that the first version number is smaller than the second version number, executing a revocation operation based on the associated operation in the container.
7. The method of claim 6, wherein performing an anti-undo operation based on the association operation in the container comprises:
determining version number change information according to the comparison result, matching association operation in the container based on the version number change information, and executing the association operation in the forward direction;
and performing, by the processor, a revocation operation based on the association operation in the container, including:
and determining version number change information according to the comparison result, matching association operation in the container based on the version number change information, and reversely executing the association operation.
8. An auxiliary revocation device is characterized in that the auxiliary revocation device comprises a storage module, wherein the storage module is used for storing a container containing a first version number set and a second version number set, and storing an operation set;
the version number information reading module is used for receiving operation callback information of the native revocation device and acquiring a current first version number and a current second version number;
the version number comparison module is used for comparing the first version number with the second version number;
and the operation response module is used for responding the operation callback information according to the comparison result of the first version number and the second version number and the operation stored in the container.
9. The revocation system is characterized by comprising a native revocation device and an auxiliary revocation device, wherein the native revocation device executes a preset operation when detecting the preset operation, generates operation callback information, and sends the operation callback information to the auxiliary revocation device;
the auxiliary revocation device receives operation callback information of the native revocation device, responds to the operation callback information, obtains a current first version number and a current second version number, compares the first version number with the second version number, and responds to the operation callback information according to a comparison result of the first version number and the second version number and operation stored in a container so as to execute the preset operation.
10. The system of claim 9, wherein the native revocation apparatus is further configured to, if a serialization operation is detected, record operation information of the serialization operation in a native list; under the condition that the non-serialization operation is detected, generating new version information and sending the new version information to an auxiliary revocation device;
and the auxiliary revocation device receives the newly added version information sent by the original revocation device, respectively increases a first version number in the first version number set and a second version number in the second version number set, and stores the operation associated with the newly added version information into the container.
11. The system of claim 10, wherein the secondary revocation apparatus is further configured to: and according to version number change information in the first version number set and the second version number set, registering the version number change information in the native revocation device.
12. The system of claim 10, further comprising a determination module configured to identify an operation type of an external input operation and to generate the operation type to the native revocation apparatus, wherein the operation type comprises a serialized operation and a non-serialized operation.
13. The system of claim 9, wherein the native revocation apparatus is further configured to:
and detecting a preset operation, and triggering access to the auxiliary revocation device based on the preset operation so as to adjust the first version number in the first version number set based on the preset operation.
14. The system according to claim 9, wherein the secondary revocation device is configured to:
if the comparison result is that the first version number is larger than the second version number, performing a reverse revocation operation based on the association operation in the container;
and if the comparison result shows that the first version number is smaller than the second version number, executing a revocation operation based on the associated operation in the container.
15. The system according to claim 14, wherein the secondary revocation device is configured to:
determining version number change information according to the comparison result, matching association operation in the container based on the version number change information, and executing the association operation in the forward direction; and the number of the first and second groups,
and determining version number change information according to the comparison result, matching association operation in the container based on the version number change information, and reversely executing the association operation.
16. An electronic device, characterized in that the electronic device comprises:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the processing method of any one of claims 1-7.
17. A computer-readable storage medium storing computer instructions for causing a processor to perform the processing method of any one of claims 1 to 7 when executed.
CN202210494599.3A 2022-05-07 2022-05-07 Processing method, processing device, revocation system, electronic equipment and storage medium Active CN114879889B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210494599.3A CN114879889B (en) 2022-05-07 2022-05-07 Processing method, processing device, revocation system, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210494599.3A CN114879889B (en) 2022-05-07 2022-05-07 Processing method, processing device, revocation system, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN114879889A true CN114879889A (en) 2022-08-09
CN114879889B CN114879889B (en) 2024-03-29

Family

ID=82674606

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210494599.3A Active CN114879889B (en) 2022-05-07 2022-05-07 Processing method, processing device, revocation system, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114879889B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004086233A1 (en) * 2003-03-26 2004-10-07 Sony Corporation Information recording medium, information processing device, information recording medium manufacturing device, and method, and computer program
CN102298558A (en) * 2010-06-24 2011-12-28 索尼公司 Information processing device, information processing method, and program
CN105431821A (en) * 2013-07-30 2016-03-23 苹果公司 Undo system
CN111679812A (en) * 2020-06-10 2020-09-18 深圳前海微众银行股份有限公司 Service processing method, device, equipment and computer readable storage medium
CN111857518A (en) * 2020-07-30 2020-10-30 北京默契破冰科技有限公司 Method and device for canceling image editing operation, electronic equipment and medium
US20210176078A1 (en) * 2017-12-01 2021-06-10 Nagravision Sa Capability revocation in a content consumption device

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004086233A1 (en) * 2003-03-26 2004-10-07 Sony Corporation Information recording medium, information processing device, information recording medium manufacturing device, and method, and computer program
US20060259979A1 (en) * 2003-03-26 2006-11-16 Tomoyuki Asano Information recording medium, information processing device, information storage medium production apparatus, method, and computer program
CN102298558A (en) * 2010-06-24 2011-12-28 索尼公司 Information processing device, information processing method, and program
CN105431821A (en) * 2013-07-30 2016-03-23 苹果公司 Undo system
US20210176078A1 (en) * 2017-12-01 2021-06-10 Nagravision Sa Capability revocation in a content consumption device
CN111679812A (en) * 2020-06-10 2020-09-18 深圳前海微众银行股份有限公司 Service processing method, device, equipment and computer readable storage medium
CN111857518A (en) * 2020-07-30 2020-10-30 北京默契破冰科技有限公司 Method and device for canceling image editing operation, electronic equipment and medium

Also Published As

Publication number Publication date
CN114879889B (en) 2024-03-29

Similar Documents

Publication Publication Date Title
CN113626223A (en) Interface calling method and device
CN113392974A (en) Model training method and device, electronic equipment and storage medium
CN117170655A (en) Metadata processing method and device, data processing equipment and storage medium
CN114879889B (en) Processing method, processing device, revocation system, electronic equipment and storage medium
CN116824609A (en) Document format detection method and device and electronic equipment
CN115454971A (en) Data migration method and device, electronic equipment and storage medium
CN116028517A (en) Fusion database system and electronic equipment
CN115905322A (en) Service processing method and device, electronic equipment and storage medium
CN115880508A (en) Image data processing method, device, equipment and storage medium
CN113076343B (en) Data query method, device, equipment and storage medium
CN112860811B (en) Method and device for determining data blood relationship, electronic equipment and storage medium
CN114445682A (en) Method, device, electronic equipment, storage medium and product for training model
CN113901033A (en) Data migration method, device, equipment and medium
CN113126866A (en) Object determination method and device, electronic equipment and storage medium
CN114741072B (en) Page generation method, device, equipment and storage medium
CN113342413B (en) Method, apparatus, device, medium, and article for processing components
CN116561075B (en) Method for generating dynamic link library file, method and device for calling operator
CN115202538B (en) Menu configuration method and device, electronic equipment and storage medium
CN113254993B (en) Data protection method, apparatus, device, storage medium, and program product
CN117539832A (en) File system object renaming method, device and computer program product
CN113343005A (en) Searching method, searching device, electronic equipment and readable storage medium
CN115620015A (en) Data processing method, data processing device, electronic equipment and storage medium
CN115687244A (en) File processing monitoring method, device, equipment and medium
CN115860959A (en) Method, device, equipment and storage medium for managing trusted architecture
CN118132536A (en) Data migration method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant