CN115630345A

CN115630345A - Business management system

Info

Publication number: CN115630345A
Application number: CN202211303855.2A
Authority: CN
Inventors: 梁妍陟; 张杰明; 高宜凡; 甘锴; 陈展尘; 李华圃; 李明锶; 褚裕谦; 陈显超; 翟时雨
Original assignee: Guangdong Power Grid Co Ltd; Zhaoqing Power Supply Bureau of Guangdong Power Grid Co Ltd
Current assignee: Guangdong Power Grid Co Ltd; Zhaoqing Power Supply Bureau of Guangdong Power Grid Co Ltd
Priority date: 2022-10-24
Filing date: 2022-10-24
Publication date: 2023-01-20

Abstract

The invention discloses a service management system, comprising: the system comprises a permission module used for acquiring the permission information of a user, a management module used for responding to a file operation instruction input by the user and managing a file which is in the permission information and has management permission, a cooperation module used for responding to a data operation instruction input by the user and reading or editing data which is in the permission information and has management permission, and a history module used for responding to the history operation instruction input by the user, checking the history record of the data and backtracking the history version of the data. The method is favorable for solving the technical problem that the service management efficiency and the production safety are influenced because the conventional service management method cannot uniformly manage and trace the historical version due to the data management problem, and improves the working efficiency of service management.

Description

Business management system

Technical Field

The invention relates to the technical field of dispatching automation services, in particular to a service management system.

Background

The current dispatching automation service file data comprises professional documents such as various information point tables, graphic files, models and program versions scattered in different people, different equipment and different systems, files are inconvenient to search, unified management cannot be achieved, information sharing cannot be achieved, various changes cannot be synchronized in real time, previous versions cannot be found back, on one hand, the working efficiency of automation personnel is affected, and on the other hand, the possibility that production safety is affected due to data management problems can be generated.

Aiming at the problems, the project is to be transformed and developed by adopting the current open-source document management project to form a set of scheduling automation service online management tools, the information security requirements are met, a worker can quickly retrieve a target file according to self-distributed authority, the operations of accessing, deleting, updating the version, returning and the like of the document are completed, the management tools record modified contents and modified records in real time, the unified management requirements of orderly collecting, classifying, sorting, authorizing, filing and the like of professional documents such as various information point lists, graphic files, models, program versions and the like are realized, and the following effects are achieved: 1) The material management process can be controlled; 2) Historical version materials can be traced; 3) The final material versions may be uniform.

Therefore, in order to improve the work efficiency of business management and solve the technical problem that the business management efficiency and the production safety are affected because the existing business management method cannot uniformly manage and trace the historical version due to the data management problem, it is necessary to construct a business management system.

Disclosure of Invention

The invention provides a service management system, which solves the technical problem that the service management efficiency and the production safety are influenced because the prior service management method cannot uniformly manage and trace the historical version due to the data management problem.

In a first aspect, the present invention provides a service management system, which includes an authority module, a management module, a coordination module and a history module that are connected to each other;

the authority module is used for acquiring authority information of a user;

the management module is used for responding to a file operation instruction input by the user and managing the file with the management authority of the user in the authority information;

the cooperation module is used for reading or editing the data with the management authority of the user in the authority information in response to the data operation instruction input by the user;

and the history module is used for responding to a history operation instruction input by the user, checking the history record of the data and backtracking the history version of the data.

Optionally, the authority module includes an obtaining sub-module, a creating sub-module and an assigning sub-module which are connected with each other;

the acquisition submodule is used for acquiring the authority information;

the creating sub-module is used for responding to a creating instruction input by the user and creating the management authority of the user on the files and/or data;

and the giving sub-module is used for responding to an authorization instruction input by the user and giving the management authority of the user to the lower-layer file corresponding to the upper-layer file in the authority information.

Optionally, the management module includes a retrieval sub-module, a search sub-module, and a management sub-module, which are connected to each other; the file operation instruction comprises a file retrieval instruction and a file management instruction;

the retrieval submodule is used for responding to the retrieval instruction input by the user and retrieving the files which are updated recently and have the management authority by the user in the authority information;

the searching submodule is used for searching a file corresponding to the fuzzy information according to the fuzzy information input by the user;

the searching submodule is used for searching the information input by the user in the file with the management authority of the user in the authority information;

and the management submodule is used for responding to the file management instruction input by the user and managing the files with the management authority of the user in the authority information.

Optionally, the management submodule includes a deleting unit, a naming unit, a moving unit, a copying unit and a transmitting unit, which are connected to each other; the file management instruction comprises a deleting instruction, a naming instruction, a moving instruction, a copying instruction and a transmitting instruction;

the deleting unit is used for responding to the deleting instruction input by the user and deleting the file with the management authority of the user in the authority information;

the naming unit is used for renaming files which have management authority by the user in the authority information in response to the renaming instruction input by the user;

the mobile unit is used for responding to the moving instruction input by the user and moving the file with the management authority of the user in the authority information;

the copying unit is used for responding to the copying instruction input by the user and copying the file with the management authority of the user in the authority information;

and the transmission unit is used for responding to the transmission instruction input by the user and uploading or downloading the file with the management authority of the user in the authority information.

Optionally, the collaboration module is further configured to provide an indication for the user to resolve the editing conflict problem.

Optionally, the coordination module is further configured to combine data in the authority information, which the user has management authority, in response to the data management instruction input by the user.

Optionally, the collaboration module includes a reading sub-module, an editing sub-module, a conflict sub-module, and a merge sub-module, which are connected to each other; the data management instruction comprises a reading instruction, an editing instruction and a merging instruction;

the reading sub-module is used for reading the data with the management authority of the user in the authority information in response to the reading instruction input by the user;

the editing submodule is used for responding to the editing instruction input by the user and editing the data with the management authority of the user in the authority information;

the conflict submodule is used for providing an instruction for the user to solve the editing conflict problem according to the preset problem solving step when the editing conflict problem between the users is detected;

and the merging submodule is used for responding to the merging instruction input by the user and merging the data of the user with the management authority in the authority information.

Optionally, the conflict submodule includes a first conflict unit and a second conflict unit connected to each other;

the first conflict unit is used for providing an instruction for the user to solve the editing conflict problem according to a preset first problem solving step when the existence of the same position of two or more users editing the same data is detected;

and the second conflict subunit is used for providing an instruction for the user to solve the editing conflict problem according to a preset second problem solving step when the user finishes editing the data and the data is changed by another user.

Optionally, the history module is further configured to upload the history of the data to a cloud according to a preset period.

Optionally, the history module comprises a viewing submodule and a backtracking submodule connected to each other; the historical operating instructions comprise a viewing instruction and a backtracking instruction;

the viewing submodule is used for viewing the historical record of the data in response to the viewing instruction input by the user;

and the backtracking sub-module is used for responding to the backtracking instruction input by the user and carrying out version backtracking on data corresponding to the backtracking instruction based on the historical records.

According to the technical scheme, the invention has the following advantages: the invention provides a service management system, which comprises a permission module, a management module, a history module and a collaboration module, wherein the permission module is used for acquiring the permission information of a user, the management module is used for responding to a file operation instruction input by the user and managing a file with management permission of the user in the permission information, the collaboration module is used for responding to a data operation instruction input by the user and reading or editing data with management permission of the user in the permission information, and the history module is used for responding to a history operation instruction input by the user, checking the history record of the data and backtracking the history version of the data.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.

Fig. 1 is a block diagram of a service management system according to an embodiment of the present invention.

Detailed Description

The embodiment of the invention provides a service management system, which is used for solving the technical problem that the service management efficiency and the production safety are influenced because the prior service management method cannot uniformly manage and trace historical versions due to the problem of data management.

In order to make the objects, features and advantages of the present invention more obvious and understandable, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the embodiments described below 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.

In a first embodiment, please refer to fig. 1, fig. 1 is a service management system of the present invention, in which 101 is a permission module, 102 is a management module, 103 is a coordination module, and 104 is a history module; the authority module 101, the management module 102, the cooperation module 103 and the history module 104 are connected with each other;

the authority module 101 is configured to obtain authority information of a user;

the management module 102 is configured to manage a file having a management authority of the user in the authority information in response to a file operation instruction input by the user;

the collaboration module 103 is configured to read or edit data having management rights of the user in the rights information in response to a data operation instruction input by the user;

the history module 104 is configured to view a history record of the data and trace back a history version of the data in response to the history operation instruction input by the user.

Specifically, the authority module 101 includes an obtaining submodule, a creating submodule, and an assigning submodule connected to each other;

the acquisition submodule is used for acquiring the authority information;

the creating submodule is used for responding to a creating instruction input by the user and creating the management authority of the user on the file and/or the data;

In the embodiment of the present invention, the authority module 101 is a basis for the secure operation of the system, when a file is created, a reader writer is designated for the file, and for each file existing in the system, the file has a corresponding reader/writer with authority, when a related operation is performed on the file, the authority check is performed first, and the next operation can be performed only after the verification is passed. The user of the read authority can only check the file, when the file is opened, the file is in a non-editable state, the user of the write authority has the write authority and can edit the file, the most basic authority control is realized, in addition, the authority of the file can also be modified, the authority possession mode of the file has two types, namely inheritance authority and custom authority, the inheritance authority refers to that the user inherits all the authority of the upper folder and has own new authority, the custom authority separates the authority of the user from the authority of the folder, the authority of the file cannot inherit the authority of the folder, the reader writer corresponding to the authority of the user is completely own, the authority modification refers to that the authority of the file is modified between inheritance and customization, a new reader/writer can also be designated for the file, and the original reader/writer is deleted.

In specific implementation, RBAC technology is adopted to realize user authority management.

Every file-related operation performed by a user in the file system requires a permission check. The authority source is whether the file is a new reader/writer of the file when being created, or is a reader/writer of an upper folder of the file before, or other authorized users share the read/write authority of the file with the reader/writer, and as long as the users have the authority, the authority can be always checked when the authority check is carried out in the system.

The file or folder modification permission is the permission for modifying a file for a user with write permission of the file/folder, wherein the modification refers to the mode of modifying the file/folder with the permission, and the modification is carried out between self-definition and inheritance permission, or a new reader writer is appointed for the file or an original reader writer is deleted. The operation of changing the file authority mode mainly comprises the operation that the authority type before the file is inherited, a user with writing authority can change the authority type of the file from inheritance to self-definition, and a new reader writer can be added into an authority list of the user or the reader/writer with authority removal of the user can be removed on the basis that the file is inherited. When the file authority type is self-defined, the user with the writing authority can change the authority type of the file from self-defined to inheritance, and a new reader writer can be added into the authority list of the user or the reader/writer with the authority to be removed can be removed on the basis that the file is the self-defined authority.

And (3) adding and deleting readers/writers on the basis of the user-defined permission: when the authority of the file is customized, the file does not inherit the authority of the upper folder, then all readers/writers of the file create corresponding readers/writers corresponding to a new authority and readers/writers corresponding to an authority list originally owned by the file are compared, an authority list needing to be added and deleted is calculated, and for the authority to be deleted, if the file is a folder, for non-customized folders below the folder, the file inherits the authority to be deleted, so the authority is removed from the authority list of the database; for the permissions to be added, if the file is a folder, all non-custom folders below the folder need to be found and the permissions created for them. And (3) adding and deleting readers/writers on the basis of inheriting file permission: when the file rights are inherited, the addition and deletion of readers/writers are similar to the custom rights, only one step is added, all readers/writers of the file cannot create rights for the reader/writers, firstly, the readers/writers are compared with readers/writers corresponding to the rights list of the parent folder of the reader/writer to find out new readers/writers, then, new rights lists are created for the readers/writers, the created new rights lists are compared with the rights lists of the file per se to obtain the rights to be increased and decreased, the following operation is the same as the process, for the rights to be deleted, if the file is a folder, for the non-custom folders below the folder, the rights to be deleted are inherited, and therefore, the rights are also removed from the rights lists of the database; for the permissions to be added, if the file is a folder, all non-custom folders below the folder need to be found to create the permissions for them.

The file authority possession mode is changed from self-definition to inheritance: when the file authority is inherited from the custom, the file authority of an upper folder of the file is required to be inherited, if the file is a folder, the non-custom folder below the folder is required to inherit the authority, then a reader/writer of the file is compared with a user corresponding to the inherited parent folder authority to obtain a new authority list to be created, and then the new authority list is compared with the unique authority list of the inheriting file to find out an added and deleted authority list, and if the file is a folder, the non-custom folder below the folder inherits the authority to be deleted, so that the authority is also removed from the authority list of the database; for the permissions to be added, if the file is a folder, all non-custom folders below the folder need to be found and the permissions created for them.

When the file permission is changed from inheritance to self-definition, all the permissions of the file and the child nodes thereof inherited from the file and the ancestor node of the file are deleted, and creating a new permission list for the reader writer of the reader, and enabling all non-self-defined folders of the reader to inherit the permissions.

Specifically, the management module 102 includes a retrieval sub-module, a search sub-module, and a management sub-module, which are connected to each other;

In the embodiment of the present invention, the management module 102 is mainly used to implement basic functions of a common file management system, and these functions include loading all folders that a user has right to see, retrieving files/folders by using filename fuzzy matching, searching for files that the user has right to see that are recently updated, creating/deleting files, moving files from one folder to another folder, modifying filenames, copying files, uploading/downloading files, and the like.

In the specific implementation, a Bootstrap front-end framework is adopted, so that better user interaction experience is completed, and an information management function is realized.

The permission module 101 obtains the user permission information, and the user loads the visible top-level folder after entering the system, where the definition of the top-level folder is that the folder has no parent folder or the user has no permission to the parent folder. And after the folders are loaded, carrying out file authority analysis on the folders.

Sometimes, a user wants to see a recently updated file which the user has the authority to see, and only needs to load a non-directory type file which the user has the authority to see from a database according to the updating time, perform file authority analysis, load a file collection state, a directory tree which the user can see, the file browsing number and a file reading record.

The user inputs the name of the file to be searched as a keyword of the file to be searched, and the file searching can be realized by using the sql fuzzy searching sentence.

The current user wants to delete a file/folder, firstly, the write permission is checked, after the check is passed, the user is indicated to have the write permission to the file, then, whether the user has the write permission to the child nodes of the file is checked, and the file can be deleted only if all the child nodes of the file have the write permission.

The user transmits the new name of the file to the back end, after the write permission check is passed, whether the file with the completely same name as the suffix name named by the new name exists in the parent folder of the file is judged, the user has permission to the file, if so, the naming is failed, otherwise, the naming is successful, and the file name is modified.

A file is moved to a designated folder, whether a user has write permission in the folder is judged, the folder is locked after the check, whether the file to be moved by the user has write permission completely because the file to be moved is possibly a directory is checked, the user also has write permission for a subfile of the file to be moved, after the check is passed, if the file to be moved is the directory with the permission in an inheritance mode, the file and the subfile thereof are deleted from the authority of an upper folder in an inheritance mode, and then the file and all non-self-defined subfolders inherit the permission of the designated file and the upper folder thereof. The file moved past is updated to its parent folder, and the file and its subfiles update ancestor nodes.

Copying a file to a designated folder, firstly judging whether a user has write permission to the designated folder, if the copied file is a folder after permission check is passed, creating a file folder with the same name under the directory, wherein the file folder inherits the permission of the designated folder, and circularly copying subfiles of the copied folder; if not, the files with the same name are created under the directory.

Specifically, the management submodule comprises a deleting unit, a naming unit, a moving unit, a copying unit and a transmitting unit which are connected with each other; the file management instruction comprises a deleting instruction, a naming instruction, a moving instruction, a copying instruction and a transmitting instruction;

the mobile unit is used for responding to the moving instruction input by the user and moving a file with management authority of the user in the authority information;

Specifically, the collaboration module 103 is further configured to provide an indication for the user to solve the editing conflict problem.

Specifically, the coordination module 103 is further configured to combine data that the user has management authority in the authority information in response to the data management instruction input by the user.

Specifically, the collaboration module 103 includes a reading sub-module, an editing sub-module, a conflict sub-module, and a merge sub-module, which are connected to each other; the data management instruction comprises a reading instruction, an editing instruction and a merging instruction;

In the embodiment of the present invention, the collaboration module 103 is a core module of the system, and mainly solves how to perform conflict processing when a user edits a copy of its own document, if another user edits the same position of the document at the time, and when the user finishes editing and submits his/her document to a background, it finds how to perform processing when another user has changed the document, and loads basic information of the document when the document is opened.

In the concrete implementation, a SpreadJS technology is adopted to realize the efficient multi-user collaborative editing and merging function.

When a user wants to open a document, the permission module 101 first performs a read permission check, and the subsequent operations can be performed only after the permission check, the document content entity is loaded from the database, the lock on the document is loaded, the document history record is loaded, including creating the history, editing the history, approving the history, adding the permission history, removing the permission history, and the design introduction of the document in the operation rollback module is restored by using the history record. The document content entity is a sheet or document object which is additionally created when the file is created under the control of the authority and the editable document is created, and is used for bearing the editing of the user. And loading a document reading record, and displaying a history read record and a latest read record, wherein the state of the reading record indicates that the record corresponds to the history version or the latest version read by a user. When a document is opened or closed, a corresponding event is created and issued to a subscriber, and after the subscriber receives the event, a corresponding user reading record of the document is created, whether the reading record exists in a database is searched, if the reading record exists, the reading record is updated, the reading time is set to be present, and whether the reading record is read recently is set to be yes. Otherwise, the newly created read record is placed in the database table. When a user edits a document, an edited document event is created and issued to a subscriber, after receiving information, the subscriber takes out all read records corresponding to the document, only the read record corresponding to the current user of the edited document is refreshed to be the latest read record, all the other read records are set to be history read, and the history read records are written back to a database. When the document reading record state changes, corresponding events can be generated, and the subscribers of the events receive the events and send the events to the browser document copy, so that correct history read records and latest read records are displayed in the document.

After the user opens the document and loads all the contents of the document, the authority of the user for the document is judged firstly, if only the read authority exists, the user is not editable, and at the moment, the user can only open the document and is in a non-editable state. The first step of editing is to lock a document paragraph in real time when a user writes content into the paragraph of the document, if the lock of the paragraph is not preempted, the user successfully locks, otherwise, the user who fails to lock sees that the line becomes uneditable. After the user finishes editing, the edited content is written back to the database after the mouse moves to another line, and the paragraph lock is released when the mouse moves to another line. Other users with editing rights will see that locks that were not previously editable become editable. The concrete implementation is as follows: a user edits a paragraph of a document, a paragraph lock of the paragraph is taken out from a background, if the lock is not empty and the lock is added by the user, a locking event is created, the locking is successful, the lock is returned, and otherwise, the locking is failed (the preemption is failed); if the lock is empty, the user searches whether the user has over-locked the document before, if so, the user deletes the lock, otherwise, a paragraph lock is directly created for the paragraph, and the preemption is successful. It should be noted that, in an extreme case, multiple threads preempt the paragraph lock, and in a specific solution, when each user locks a paragraph, the document is locked first, the first user successfully locks the document, the next part of the transaction may be executed, and other users are blocked until the first user locks the document paragraph, and at this time, the next user attempts to lock the paragraph, which indicates that the paragraph has a lock and the locking fails. After the user finishes editing, relevant operations are written into the content of the database document, the validity of each operation is verified for the operation list transmitted from the front end, the current document is locked, the operation list is acted on the document, and the document is changed. The document is written back to the database. It should be noted that each operation of the user corresponds to a version number when modifying the document, and if the database version of the document is found not to correspond to the document version of the user when the user writes the operation back to the database, the document is considered to be modified by other users. Through automatic publishing to other copies of the front end by the server side, other users can see the change of the document. Therefore, the problem of document inconsistency caused by concurrency conflicts is solved. When the user finishes editing, the paragraph lock is released, and other users can see that the previously un-editable paragraph becomes editable.

Specifically, the conflict submodule comprises a first conflict unit and a second conflict unit which are connected with each other;

Specifically, the history module 104 is further configured to upload the history of the data to a cloud according to a preset period.

Specifically, the history module 104 includes a viewing sub-module and a backtracking sub-module connected to each other; the historical operation instruction comprises a viewing instruction and a backtracking instruction;

In the embodiment of the present invention, the history module 104 mainly implements creation of history records of a document, performs real-time synchronization on the history records of the document, displays the history records generated by operations performed on the document by a user in real time on document copies of other users, and performs document recovery by using the history records of the document, and cancels the operations corresponding to the history records, so as to recover the document to the version before the generation of the history records.

In the specific implementation, the SVN technology is adopted to realize the version rollback so as to achieve the history tracing effect.

The types of history records are mainly: creating a document, adding a new reader writer to the document, deleting the document reader writer, commenting the document, and editing the document. The history record is generated mainly by the server end for actively informing the front end of the change of other copies of the same document, and the front end can realize the timely display of the document history after receiving the history record. For example, when a user manages information, a modification event is created when the content of a certain paragraph of a document is modified by a document copy of the user, the modification event is issued, a receiver receives the modification event, creates a historical event and stores the historical event in a historical event database, records in the historical event database are all taken out periodically through a Spring timing calling mechanism to create a historical record and store the historical record in a cache, and the historical message is pushed to a copy of the same document through the pushing of a WebSocket protocol.

Because the history record types of the document comprise creating the document, editing the document and modifying the document authority (adding a new reader writer to the document or deleting an original reader writer), a synchronous history record interface can be called regularly for the document opened at the front end, and the interface is different from the interface for loading the document history record in that the front end can transmit the maximum version number of all current history records owned by the front end, and only the history record with the version number larger than the version number is needed to be loaded during synchronization. When a later of the document opens the document, the history record of the document needs to be loaded, and in order to prevent the Spring mechanism from failing due to network delay, the history record of the document needs to be synchronized periodically, namely, the maximum version number of the history record corresponding to the document copy of the later needs to be transmitted to a background server, and the database history record larger than the version number is loaded.

If a user finds that the user edits the document wrongly or someone else edits the document wrongly, the user can utilize a history record left by the user to edit the document to perform version rollback, the document is rolled back to a version before the version number corresponding to the history record, the process is write authority check, after the check is passed, the document is locked, operations after the version number of the history record is larger than or equal to the version number of the publication number are taken from a database document operation table, the operations are all operations to be cancelled, the operations are reversed to generate a cancellation operation list corresponding to the operations, the list operations are combined by using an operation combination algorithm, the combined operations are combined into a composite operation to act on the document, and history tracing is realized.

The service management system provided by the invention has the following advantages:

1) The online management tool for the dispatching automation service has strong universality, does not depend on the existing power dispatching system, and can realize rapid deployment and application.

2) The information management realizes the file sharing and authority management among different personnel in a dispatching department, and realizes the orderly collection, classification, arrangement, authorization, filing and the like of project files.

3) The multi-user collaborative editing and merging function provides collaborative editing with content conflict detection prompt aiming at scheduling automation, so that the editing efficiency can be improved, and content coverage can be effectively prevented.

4) Authority management, more refined authority control, centralized management and unified authorization, effective control of internal document data, avoidance of leakage of confidential data and improvement of system security

5) History tracing, namely history version storage is adopted to realize history operation tracing, and the problem of mistaken deletion and filling caused by personal operation errors in the original file sharing mode is solved.

The business management system provided by the embodiment of the invention comprises a permission module for acquiring the permission information of a user, a management module for responding to a file operation instruction input by the user and managing files with management permission of the user in the permission information, a cooperation module for responding to a data operation instruction input by the user and reading or editing data with management permission of the user in the permission information, and a history module for responding to the history operation instruction input by the user, checking the history record of the data and backtracking the history version of the data.

It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present application, it should be understood that the system disclosed in the present invention can be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a readable storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned readable storage medium comprises: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims

1. A service management system is characterized by comprising an authority module, a management module, a cooperation module and a history module which are connected with one another;

the authority module is used for acquiring authority information of the user;

2. The service management system according to claim 1, wherein the authority module includes an acquisition submodule, a creation submodule and an assignment submodule connected to each other;

the acquisition submodule is used for acquiring the authority information;

3. The business management system of claim 1, wherein the management module comprises a retrieval submodule, a search submodule and a management submodule which are connected with each other; the file operation instruction comprises a file retrieval instruction and a file management instruction;

4. The traffic management system according to claim 3, wherein the management submodule includes a deletion unit, a naming unit, a mobile unit, a copy unit, and a transmission unit, which are connected to each other; the file management instruction comprises a deleting instruction, a naming instruction, a moving instruction, a copying instruction and a transmitting instruction;

the naming unit is used for renaming files with management authority of the user in the authority information in response to the renaming instruction input by the user;

5. The transaction management system of claim 1, wherein the collaboration module is further configured to provide an indication to the user to resolve an editing conflict.

6. The transaction management system of claim 5, wherein the coordination module is further configured to merge data with management authority of the user in the authority information in response to the data management instruction input by the user.

7. The business management system of claim 1, wherein the collaboration module comprises a reading sub-module, an editing sub-module, a conflict sub-module, and a merge sub-module connected to each other; the data management instruction comprises a reading instruction, an editing instruction and a merging instruction;

8. The traffic management system of claim 7, wherein the conflict submodule comprises a first conflict unit and a second conflict unit coupled to each other;

9. The business management system of claim 1, wherein the history module is further configured to upload a history of the data to a cloud according to a preset period.

10. The business management system of claim 1, wherein the history module comprises a view submodule and a backtrack submodule connected to each other; the historical operation instruction comprises a viewing instruction and a backtracking instruction;