CN1235163C - Method for realizing data sharing between diferent user's computers in embedded system - Google Patents
Method for realizing data sharing between diferent user's computers in embedded system Download PDFInfo
- Publication number
- CN1235163C CN1235163C CN 02145962 CN02145962A CN1235163C CN 1235163 C CN1235163 C CN 1235163C CN 02145962 CN02145962 CN 02145962 CN 02145962 A CN02145962 A CN 02145962A CN 1235163 C CN1235163 C CN 1235163C
- Authority
- CN
- China
- Prior art keywords
- user
- database
- server
- data base
- customer data
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Storage Device Security (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present invention discloses a method for realizing data sharing among different user clients in embedded systems. The method comprises the procedures: 1. a configuration database is established in a server of an embedded system, and user information in the configuration database is grouped; 2. a user client selects a group and joins the group according to self requirements; 3. a user establishes credit relation with a calling user in the same group through a server; 4. the server returns the copy of a database of the calling user to a client of a called user according to the credit relation; 5. the user client accesses the copy of the user database of the client of the called user; 6. after accessing is finished, the copy of the database of the called user is used for updating the database in the client of the called user. The present invention effectively supports data exchange modes in embedded systems. Meanwhile, the present invention has the advantage of convenient maintenance, and the correctness of data can be ensured.
Description
Technical field
The present invention relates to data sharing technology in a kind of embedded system, particularly a kind ofly realize in the embedded system method of data sharing between the different user client computer.
Background technology
At present, a lot of embedded systems have been introduced embedded database.The data exchanging function of embedded database makes that embedded product can be unblocked when the data of other electronic equipment of visit (as PC, database server, communication facilities etc.), simultaneously, because its independence for platform can freely be transplanted between embedded platform.Embedded database can satisfy embedded system to requirements such as data processing and exchanges data, and it and embedded OS organically combine, for the application developer provides effective data management means.Embedded database has obtained application in concrete industries such as insurance, banking industry, retail trade, health care, forwarding business, government departments, also will expand to gradually in the different industries.
According to use dividing, embedded database can be divided into customer data base on user's client computer and the central database on the server, and what preserve in the customer data base of client computer is user's self data, and what preserve in the central database mainly is publicly-owned data.Be in the embedded system of server with the computing machine, can also preserving each user's private data in the central database.
At present, user's client computer can be given central database with the data upload in self customer data base, or download publicly-owned data from central database, if preserved user's private data in the central database, the user also can download the private data of self from central database, realizes its data exchange.Yet, existing embedded database has a common defective: oneself private data or publicly-owned data be downloaded or be uploaded to each user's client computer can only from central database, but can't visit the user data database data of other client computer, that is to say, can't realize the data sharing between different client computer in the embedded system.This makes can not give play to powerful data by embedded database it has enjoyed function when carrying out exchanges data, restricted the expanded application of embedded database in industry-by-industry.
Summary of the invention
In view of this, the object of the present invention is to provide a kind of method of data sharing between the different user client computer that realizes in the embedded system, can realize in the embedded system method of data sharing between different client computer, data sharing between user's client computer in the embedded system provides effective support to the data exchange ways in the embedded system.
For achieving the above object, technical scheme of the present invention specifically is achieved in that
A kind ofly realize in the embedded system method of data sharing between the different user client computer, this method may further comprise the steps:
1) in the server of embedded system, sets up the configuration database that comprises all user configuration informations, and divide into groups according to the user's information in the configuration database;
2) user's client computer is according to self needs selection group and adding;
3) user is by the information of other customer data bases in the inquiry group, after inquiring the customer data base that to visit, user's client computer sends the request trust information by server accessed user on the same group, after accessed user accepts request trust information is added in the configuration database, the relation of breaking the wall of mistrust is also notified the user;
4) the request trust information accepted according to accessed user of server, the access right of the customer data base copy that accessed user's client computer is set up returns to user's client computer;
5) user's client computer conducts interviews to the customer data base copy of accessed user's client computer;
6) visit finishes, and upgrades database in accessed user's client computer with accessed user's data storehouse copy.
Wherein, the described configuration database of setting up of step 1) can comprise: set up user profile list, group information list, database information list and trusting relationship list.Step 1) can further include a default set is set in server, and when adding new user or deletion group in system, server adds this default set with this user or with all users in deleted group.
Step 2) may further include: all group information in the user inquiring system, the particular function information that obtains each group is described by group.
Step 3) can further include: the user sends to server with self storehouse/table name and access rights, and server returns to the user with the user to the access rights of accessed customer data base.Step 3) can further include: the access rights of setting compared when the access rights that user request is imported into when breaking the wall of mistrust were set up with himself storehouse, if the user asks access rights to be higher than initial rights when building the storehouse, user's access rights initial rights when building the storehouse then, otherwise the access rights of importing into when breaking the wall of mistrust for user's request.
In this method, non-trust user on the same group can be with the publicly-owned data in the accessed database in the read-only mode visit on the same group.
Step 4) can judge whether the copy of interviewed customer data base exists earlier for: server, if there is no, then from configuration database, read key, should decipher by interviewed customer data base, and notify accessed user on accessed client computer, to set up the customer data base copy, simultaneously the access right of the Database Replica after the deciphering is returned to user's client computer, if Database Replica exists, then direct access right with Database Replica returns to user's client computer.
This method can also further be reference count of each user data lab setting in server, when server is created the customer data base copy or the customer data base copy exist, when having other users to conduct interviews to same customer data base copy again, this customer data base reference count adds 1; When needs were closed certain customer data base, the reference count of this customer data base subtracted 1.
In this method,, allow this record to be operated other user's delay operation by one of them user if when a plurality of user requires to operate to same record of same customer data base simultaneously.
This method is when the deletion customer data base, if this customer data base is by other user captures, then can be by server with this customer data base setting delete database that is as the criterion, when server is restarted, server should accurate delete database be deleted from configuration database, deletes the customer data base in user's client computer simultaneously.
This method can further include: all information of transmitting between server and the user are carried out encryption/decryption process; All information in customer data base and the configuration database are carried out encryption/decryption process; All data of carrying out exchanges data between the customer data base are carried out encryption/decryption process.
By such scheme as seen, the method of data sharing between different client computer in this realization embedded system of the present invention, by setting up the purpose that trusting relationship has reached data sharing between the client computer in user grouping and the group, provide effective support to the data exchange ways in the embedded system, simultaneously, invention is easy to alleviate the copy maintenance work, and can guarantees the correctness of data owing to adopt a Database Replica.
Description of drawings
The structural representation of the configuration database that Fig. 1 sets up in server for the present invention;
Fig. 2 is the new user of interpolation of the present invention and new user's adding group synoptic diagram;
Fig. 3 concerns synoptic diagram for of the present invention breaking the wall of mistrust;
Fig. 4 is the synoptic diagram of other customer data bases of client access of the present invention;
Fig. 5 is the customer data base synoptic diagram of closing of the present invention.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, below in conjunction with embodiment and accompanying drawing, the present invention is described in more detail.
Referring to Fig. 1, the synoptic diagram of the configuration database that the present invention sets up in server.The prerequisite of implementation method of the present invention is to set up the information of configuration database 101 in order to recording user and group in server.Preserve a key when initial on server, be used for the host-host protocol content-encrypt, the user is unknowable.After repository 101 is built up, at first add a default set (default_group), be used for reclaiming free user specially, do not have general group characteristic.Foundation group is then added to after the user divided into groups in each group, for each newly-established group, its " open ended maximum number of user in the group " is made as 0, expression without limits, this parameter can be revised by the data in server library manager.Data in server library manager is meant the user who central database is had operating right, and each system can only have one, and it can newly-built group, and the deletion group is provided with open ended maximum number of user in the group, the change group name, and have the initiatively right of closing server; Other users are domestic consumers, be meant the user who holds client computer and need logon server, they can create storehouse, table, carry out a series of storehouse, table, recording operation, can change the group at own place, can ask to break the wall of mistrust to visit other people database with on the same group other subscriber computers.
As shown in Figure 1, after server 100 initialization finished, configuration database 101 had comprised four lists: group information table 102, user message table 103, trusting relationship table 104 and database information table 105.The structure of these four lists is referring to table one.
| Form name | Field |
| User message table | User name, the logon server password, affiliated group name, hour of log-on, the user describes. |
| The group information table | Group name, open ended maximum number of user in the group, the current number of users that held, group is described. |
| The database information table | Database name, database builder, the data base encryption key, creation-time, access rights, current reference count, the storehouse is described. |
| The trusting relationship table | User name is trusted in request, is requested user name, and the requested date library name is requested table name, whether receives the request flag position. |
Table one
Among Fig. 1, the dotted line in the configuration database 101 between each list represents that they are to get in touch by the field of definition in the table.Between the client computer 110 and the dotted line between the configuration database 101 in they and the server 100 represent that current system does not still have the user to register.
Newly to add a user, the process that its client computer A visits other client user databases describes for embodiment below.Present embodiment comprises following step:
At first, the first step: the user sets up the customer data base of oneself in client computer A, and wherein the configuration information of database will insert in the configuration database of server when the User login server.
Then, second step: add user A.Referring to Fig. 2, add new user and new user's adding group synoptic diagram.As shown in Figure 2, server 200 is the servers after the initialization, and it has set up configuration database 201.Relation table 206, user message table 207, database information table 208, group information table 209 and organize 202 have broken the wall of mistrust in the configuration database 201.Group has set up default set 204 in 202 and the user organizes 203.The user organizes and has set up n group 205 in 203.
At this moment, a new user---client computer A210 logon server 200 is arranged, earlier its user name and login password is deposited in the user message table 207 of configuration database 201, among the figure with arrow 2 these processes of signal; Simultaneously user A is added in the default set 204, illustrate with arrow 1 among the figure.Set the user A that just logins server 200 and be free user.Default set 204 is sightless for user A, i.e. user A and do not know oneself to be added in a certain group, and in his view, oneself still is in free state.If the group that this moment, client computer A210 inquired about own place, server 200 can return user A not in any group.
Then, the 3rd step: user A adds oneself in the group to.Referring to Fig. 2, add new user and new user's adding group synoptic diagram.Shown in Fig. 2 arrow 3, user A organizes in 203 inquiry the user, all subscriber group informations in the system up till now, the specific function of each group of understanding is described by group, thereby select own interested group of request to add the group 1 in the present embodiment in the user A selection group 205.Server 200 judges that at first whether the number of users in the new group of selecting 1 has reached maximal value, if do not reach maximal value, then accepts request.Otherwise server 200 is sent out to client computer A210 can not adding group information.Shown in Fig. 2 arrow 4, in case server 200 has been accepted request, will change user profile, the information of user A newly being selected group 1 inserts in the user message table 207; Shown in Fig. 2 arrow 5, the information of user A is inserted the group information table 209 of configuration database 201 simultaneously.The group that this moment, client computer A210 inquired about own place again, server 200 can return to client computer A210 with the group name of group 1.
Like this, just can enter for the 4th step: other customer data bases in the user A access group 1.User A desire in the access group 1 other customer data bases earlier will with the accessed customer data base relation of breaking the wall of mistrust, referring to Fig. 3, breaking the wall of mistrust concerns synoptic diagram.Shown in Fig. 3 arrow 6, after the user A adding group 1, other user's data library informations in the inquiry group in case user A has determined to carry out the storehouse of exchanges data, are just asked the owner in the storehouse relation of breaking the wall of mistrust therewith.During request, client computer A is the storehouse/table name of request visit, and access mode, authority send to server 200 together.Shown in Fig. 3 arrow 7, if the other side has accepted credential request, will add trust information in the trusting relationship table 306 of configuration database 301 to, simultaneously user A is returned to client computer A to the access rights of accessed customer data base.Client computer A just can carry out suitable operation to the customer data base of accessed user in client computer according to this authority.
In the process of determining access rights, can adopt " minimum access rights " method.The access mode of setting when this method is imported user's request into when breaking the wall of mistrust access mode is set up with the request storehouse compares, if the user asks access rights to be higher than initial rights when building the storehouse, then reduces user's access rights.
Because database is just encrypted when creating, the user is before gain access, server judges at first whether the copy in this storehouse exists, if there is no, then from repository, read key,, and notify accessed user on accessed client computer, to set up the customer data base copy the database deciphering, simultaneously the access right of the Database Replica after the deciphering is returned to user's client computer, the reference count in storehouse is added 1; If Database Replica exists, then directly the access right of Database Replica is returned to user's client computer, the reference count in storehouse is added 1.
The present invention only adopts a Database Replica, can avoid like this owing to, when closing database, must upgrade former storehouse simultaneously with the content of all copies for each user creates a Copy, operational difficulty of bringing and the extra resource overhead that increases because will use temporary file.Adopt a copy, just can when a plurality of users produce the reading and writing conflict to same record, can produce certain delay according to concurrent strategy.Single copy is easy to alleviate the copy maintenance work, and can guarantee the correctness of data.
Referring to Fig. 4, the synoptic diagram of other customer data bases of client access.For example, shown in Fig. 4, user A, B, C, D are arranged in group 1 in the server 400, and user E is arranged in group 2, and wherein arrow 8 expression user A have obtained the trust of user B.In the present embodiment, user A and user B break the wall of mistrust when concerning, the database of user B is not by other user captures, so, the Database Replica that server 400 is judged user B does not exist as yet, so from configuration database 401, read this database key, database is deciphered, and notify user B on client computer B, to set up customer data base copy 422, simultaneously the access right of the Database Replica 422 after the deciphering is returned to client computer A, the reference count of the customer data base of user B is added 1 insert in the database information table 408 of configuration database 401, as 9 expressions of arrow among Fig. 4.User B sets up the customer data base copy on client computer B.
As shown in Figure 4, among the client computer B, except the customer data base 421 of comprising of self publicly-owned data 4211 and private data 4212, also set up the Database Replica 422 that comprises publicly-owned data 4221 and private data 4222 equally.
Wherein, user C, the D of the group 1 that coexists can only be with the publicly-owned data 4221 of read-only mode calling party B in the Database Replica 422 of client computer B420.That is to say that non-trust user on the same group can visit publicly-owned data in the accessed database with read-only mode.
User A can visit user B all data in the Database Replica 422 of client computer B420 of having set up trusting relationship with it, comprise publicly-owned data 4221 and private data 4222, and publicly-owned data 4221 there is the authority of rewriting, but has only read-only authority for private data 4222.If when having this moment other users that same record of the Database Replica 422 of client computer B420 required to operate simultaneously, this record is operated another user's delay operation by one of them user.
Shown in arrow among Fig. 4 10, the Database Replica 422 of client computer A410 access client B420.In the present embodiment, client computer A410 only operates the data of user B in the Database Replica 422 of client computer B420, and client computer A410 does not need Database Replica is opened and set up to the customer data base 410 of self.If client computer A410 wants the data of download user B in the Database Replica 422 of client computer B420, or the data in modification its data storehouse, client computer A410 need open and set up Database Replica with the customer data base 410 of self, and the reference count of the customer data base of user A simultaneously adds 1 and inserts in the database information table 408 of configuration database 401.
At last, visit finishes, and closes user B database.Referring to Fig. 5, close the customer data base synoptic diagram.Shown in arrow among Fig. 5 11, client computer A510 is to the request of server 500 transmission closing database, and server 500 is checked the reference count of the customer data base of user B, if reference count is 1, representing currently only has this user to database manipulation, and the storehouse can be closed.Shown in arrow among Fig. 5 12, server 500 can be encrypted copy again, and notice client computer B520 deletion copy, simultaneously reference count is subtracted 1; If reference count, represents currently other users are still arranged at accessing database greater than 1, can not carry out closing truly, server 500 just subtracts the reference count of this database 1 and has abandoned use to this storehouse to be shown with a user.In the present embodiment, the Database Replica 522 of client computer B520 has only client computer A510 operation, and this moment, client computer A510 operation finished.Therefore, shown in arrow among Fig. 5 13, client computer the B520 publicly-owned data 5221 of Database Replica 522 and the publicly-owned data 5211 and the private data 5212 in private data 5222 updating user data storehouses 521.
Like this, just finished the whole process that client computer A visits other client user databases.Adopt and use the same method, the customer data base that other user's client computer in the server also can access client A.This has just realized the data sharing between different client computer in the embedded system.
In said process, user A can also visit other user's data storehouses by another kind of mode: user elder generation inquiry system is interior except that all user's data library informations oneself, if find own interested storehouse, request adds in the group at founder place, this storehouse, just can carry out with above-mentioned the 4th step identical operations and visit the database of being asked.
If user A also needs to visit the customer data base of other groups, then user A changes the group at own place, and it must break away from from this group earlier, adds another group again, carries out and above-mentioned the 4th step identical operations again.Thereby guarantee a user only in a group, the chaotic situation that may occur in preventing to operate.
User A will break away from from former group, the trusting relationship of other customer data bases in must deleting it earlier and organize.For example, in the present embodiment, need the trusting relationship of deletion user A and user B.The deletion trusting relationship is very simple, only needs in the trusting relationship table with repository in " user name is trusted in request " field that the record deletion of user B gets final product in the record of user A and " being requested user name " field.Then, user A joins default_group, becomes free user.
If server need be deleted user A, need with its in configuration database all information deletions and the customer data base among the client computer A deleted.That is: earlier that all are relevant with user A trusting relationship is deleted from the trusting relationship table, all user profile of user A is deleted from user message table again, all group information of user A are deleted, all database informations of user A are deleted from the database information table from the group information table.Simultaneously, the customer data base among the client computer A is deleted.
When the deletion customer data base, customer data base may appear by other user captures, i.e. and reference count is not 0 situation, and delete database then is as the criterion this customer data base setting.DELETED realizes by this database " database builder " field in the repository database information table is changed to, and accurate delete database does not allow to have the user to attempt to open again, and can not carry out real deletion work this moment.So, adopted the method for " delayed deletion ", when restarting, at first the database information of accurate delete database is deleted each server, just searching " database builder " field in the database information table of configuration database is the record of DELETED, with this record deletion, simultaneously the customer data base physics in the client computer of this customer data base is deleted.
The inventive method can also be with the group deletion of having set up.The operating process of deletion group is: all users were recovered among the default_group in should organizing earlier, became free user, waited to be added to going in the new group, the information deletion that should organize in the group information table of configuration database were got final product again.
In addition, the inventive method has all been carried out encryption/decryption process to all information of transmitting between server and the user; All information in customer data base and the configuration database have also been carried out encryption/decryption process; All data of carrying out exchanges data between the customer data base have also been carried out encryption/decryption process.This has just been avoided the malicious sabotage of other users to database, has guaranteed safety of data.
This shows that the inventive method has realized the data sharing between the client computer in the embedded system.The present invention is easy to alleviate the copy maintenance work, and can guarantees the correctness of data owing to adopt a Database Replica.Simultaneously, the present invention distinguishes logical operation and physical operations by using the database reference count and accurate delete database being set when the deletion user, makes the disposable or batch processing of operation of consumes resources, has accelerated the travelling speed of total system.In addition, the database that the user creates all is to pass through encryption, and key is only grasped in the database builder hand, has avoided the malicious sabotage of other users to database, has guaranteed safety of data.
In sum, the present invention program has fully taken into account the efficient of correctness, security and the system of data, by setting up the purpose that trusting relationship has reached data sharing between the client computer in grouping management and the group, provide effective support to the data exchange ways in the embedded system.
Claims (12)
1, a kind ofly realize in the embedded system method of data sharing between the different user client computer, it is characterized in that this method may further comprise the steps:
1) in the server of embedded system, sets up the configuration database that comprises all user configuration informations, and divide into groups according to the user's information in the configuration database;
2) user's client computer is according to self needs selection group and adding;
3) user is by the information of other customer data bases in the inquiry group, after inquiring the customer data base that to visit, user's client computer sends the request trust information by server accessed user on the same group, after accessed user accepts request trust information is added in the configuration database, the relation of breaking the wall of mistrust is also notified the user client computer;
4) the request trust information accepted according to accessed user of server, the access right of the customer data base copy that accessed user's client computer is set up returns to user's client computer;
5) user's client computer conducts interviews to the customer data base copy of accessed user's client computer;
6) visit finishes, and upgrades database in accessed user's client computer with accessed user's data storehouse copy.
2, the method for data sharing according to claim 1, it is characterized in that: the described configuration database of setting up of step 1) comprises: set up user profile list, group information list, database information list and trusting relationship list.
3, the method for data sharing according to claim 1, it is characterized in that: step 1) further is included in a default set is set in the server, when system added new user or deletion group, server added this default set with this user or with all users in deleted group.
4, the method for data sharing according to claim 1 is characterized in that this method step 2) further comprise: all group information in the user inquiring system, the particular function information that obtains each group is described by group.
5, the method for data sharing according to claim 1 is characterized in that this method step 3) further comprise: the user sends to server with self storehouse/table name and access rights; After the relation of breaking the wall of mistrust, server returns to the user with the user to the access rights of accessed customer data base.
6, as the method for data sharing as described in the claim 5, it is characterized in that, this method step 3) further comprise: the access rights of setting compared when the access rights that user request is imported into when breaking the wall of mistrust were set up with himself storehouse, if the user asks access rights to be higher than initial rights when building the storehouse, user's access rights initial rights when building the storehouse then, otherwise the access rights of importing into when breaking the wall of mistrust for user's request.
7, the method for data sharing according to claim 1 is characterized in that: non-trust user on the same group is with the publicly-owned data in the accessed database in the read-only mode visit on the same group.
8, the method for data sharing according to claim 1, it is characterized in that, this method step 4) be: server judges whether the copy of interviewed customer data base exists earlier, if there is no, then from configuration database, read key, should decipher by interviewed customer data base, and notify accessed user on accessed client computer, to set up the customer data base copy, simultaneously the access right of the Database Replica after the deciphering is returned to user's client computer, if Database Replica exists, then direct access right with Database Replica returns to user's client computer.
9, as the method for data sharing as described in the claim 8, it is characterized in that: in server, further be reference count of each user data lab setting, when server is created the customer data base copy or the customer data base copy exist, when having other users to conduct interviews to same customer data base copy again, this customer data base reference count adds 1; When needs were closed certain customer data base, the reference count of this customer data base subtracted 1, if the result is 0, then closed this customer data base.
10, the method for data sharing according to claim 1, it is characterized in that, this method further comprises: if when a plurality of user requires to operate to same record of same customer data base simultaneously, this record is operated other user's delay operation by one of them user.
11, the method for data sharing according to claim 1, it is characterized in that, this method further comprises: when the deletion customer data base, if this customer data base is by other user captures, then server is with this customer data base setting delete database that is as the criterion, when server was restarted, server should accurate delete database be deleted from configuration database, deletes the customer data base in user's client computer simultaneously.
12, the method for data sharing according to claim 1 is characterized in that this method further comprises: all information of transmitting between server and the user are carried out encryption/decryption process; All information in customer data base and the configuration database are carried out encryption/decryption process; All data of carrying out exchanges data between the customer data base are carried out encryption/decryption process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 02145962 CN1235163C (en) | 2002-10-25 | 2002-10-25 | Method for realizing data sharing between diferent user's computers in embedded system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 02145962 CN1235163C (en) | 2002-10-25 | 2002-10-25 | Method for realizing data sharing between diferent user's computers in embedded system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1492347A CN1492347A (en) | 2004-04-28 |
| CN1235163C true CN1235163C (en) | 2006-01-04 |
Family
ID=34232568
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 02145962 Expired - Fee Related CN1235163C (en) | 2002-10-25 | 2002-10-25 | Method for realizing data sharing between diferent user's computers in embedded system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1235163C (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2447961A1 (en) * | 2003-10-31 | 2005-04-30 | Ibm Canada Limited - Ibm Canada Limitee | Research data repository system and method |
| CN100361102C (en) * | 2005-06-02 | 2008-01-09 | 北京凌创超胜科技有限公司 | Embedded network sharing device installed in mainframe |
| CN101145150B (en) * | 2006-09-15 | 2011-11-02 | 中国银联股份有限公司 | Batch file processing method and system |
| US8825824B2 (en) * | 2012-02-28 | 2014-09-02 | General Electric Company | Systems and methods for machine configuration |
| CN103491052A (en) * | 2012-06-11 | 2014-01-01 | 上海博路信息技术有限公司 | Multi-user data exchange method |
| CN110300160A (en) * | 2019-06-14 | 2019-10-01 | 杭州爱科科技股份有限公司 | Data sharing method for embedded system |
-
2002
- 2002-10-25 CN CN 02145962 patent/CN1235163C/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN1492347A (en) | 2004-04-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7171557B2 (en) | System for optimized key management with file groups | |
| CA2538506C (en) | A directory system | |
| RU2408069C2 (en) | Coordinated authority | |
| JP3943090B2 (en) | Review of cached user-group information for digital rights management (DRM) license issuance of content | |
| US20070011469A1 (en) | Secure local storage of files | |
| US7437661B2 (en) | Latches-links as virtual attachments in documents | |
| US20070011749A1 (en) | Secure clipboard function | |
| CN111698228A (en) | System access authority granting method, device, server and storage medium | |
| US20020095432A1 (en) | Document management system | |
| US8191115B2 (en) | Method and apparatus for extensible security authorization grouping | |
| WO2007008808A2 (en) | Maintaining security for file copy operations | |
| US7647398B1 (en) | Event query in the context of delegated administration | |
| CN1701315A (en) | Database access control method, database access controller, agent processing server | |
| JPH05250247A (en) | Control method for access and data processing system | |
| CN1552021A (en) | Access control protocol for user profile management | |
| US7290053B2 (en) | System and method for enforcing quotas on object creation in a replicated directory service database | |
| CN1543163A (en) | Method for creating a peer-to-peer home network using common group label | |
| US8516086B2 (en) | Generalized credential and protocol management of infrastructure | |
| CN1691587A (en) | Method and apparatus for authorizing access to grid resources | |
| US20070168364A1 (en) | Non-Mutating Tree-Structured File Identifiers | |
| US20060156020A1 (en) | Method and apparatus for centralized security authorization mechanism | |
| US20060156021A1 (en) | Method and apparatus for providing permission information in a security authorization mechanism | |
| CN1235163C (en) | Method for realizing data sharing between diferent user's computers in embedded system | |
| JP2003108440A (en) | Data disclosing method, data disclosing program, and data disclosing device | |
| CN112818038A (en) | Data management method based on combination of block chain and IPFS (Internet protocol file system) and related equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20060104 Termination date: 20201025 |