CN110535903B - Real-time and efficient enterprise address book updating method - Google Patents
Real-time and efficient enterprise address book updating method Download PDFInfo
- Publication number
- CN110535903B CN110535903B CN201910655186.7A CN201910655186A CN110535903B CN 110535903 B CN110535903 B CN 110535903B CN 201910655186 A CN201910655186 A CN 201910655186A CN 110535903 B CN110535903 B CN 110535903B
- Authority
- CN
- China
- Prior art keywords
- enterprise
- version number
- data
- department
- address book
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4594—Address books, i.e. directories containing contact information about correspondents
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a real-time and efficient enterprise address book updating method, which comprises the following steps: the method can reduce resource consumption of the server and the client, realize real-time synchronization of the address book data, does not need to maintain individual incremental information, and greatly reduces development difficulty and resource consumption of the server.
Description
Technical Field
The invention relates to an updating technology of an enterprise address book, in particular to a real-time and efficient updating method of the enterprise address book.
Background
The enterprise address book is used as the most basic function of enterprise mobile cooperative application, and the important point of ensuring the information safety and real-time updating of the address book is very important. The current address book updating mechanism capable of satisfying the complex authority relationship is divided into two polarizations: one is a traditional enterprise address book updating technology, all data are basically updated in full amount when changes occur, the consumed flow is large, and the speed is low; the other type of system needs to generate separate data for each user, and has the disadvantages of complex calculation, difficult maintenance, more personnel and excessive resource consumption. For example, patent application publication No. CN109194779A discloses a safe and efficient method for updating an enterprise address book, which can update the enterprise address book, but the method adopts pre-calculation, and each address book change requires calculation of incremental data for each person. If the information of the enterprise address book is changed frequently, a large amount of computing resources and huge storage resources are consumed.
Disclosure of Invention
In order to solve the above problems, an object of the present invention is to provide a real-time and efficient method for updating an enterprise address book, by which resource consumption of a server and a client can be reduced, real-time synchronization of address book data is realized, individual incremental information does not need to be maintained, and development difficulty and resource consumption of the server are greatly reduced.
In order to achieve the above object, an embodiment of the present invention discloses a real-time and efficient method for updating an enterprise address book, which includes the following steps:
the server stores a complete enterprise address book and an authority relationship, wherein the enterprise address book represents an enterprise architecture and comprises a complete enterprise organization relationship, enterprise basic information, department information and personnel information;
setting a plurality of enterprise version numbers to reflect related data of enterprise address records, establishing association among the enterprise version numbers based on enterprise architecture, setting personal version numbers of employees to reflect personal authority relationship of the employees, and maintaining the plurality of version numbers of enterprises and the personal version numbers of the employees by a server;
the client reserves the enterprise version number and the personal version number which are acquired when the client is connected with the server last time, the client needs to acquire the enterprise version number and the personal version number again when being connected with the server each time, and whether the enterprise address book needs to be updated is determined by comparing the version numbers:
if the enterprise version number changes, the specific position needing to be changed is determined according to the association between the specific changed enterprise version number and the enterprise organizational relationship,
if the personal version number changes, the enterprise address book of the client side needs to be updated in a full amount;
the server side calculates the user visible range in real time according to the user authority of the currently connected client side, generates temporary enterprise address book data for the user to see, and pushes the change information to the client side according to the user request.
Optionally, the method further comprises the steps of:
each time the client is connected with the server, a real-time communication key needs to be generated, and all data in the current interaction period are encrypted by using the communication key AES and then transmitted.
Optionally, the method further comprises the steps of:
the server side maintains the states of all current online users, calculates the variation influence range in real time when the server side data varies, and informs all online personnel in the influence range.
Optionally, the enterprise version number includes:
the unique enterprise total version number _ V0 has an initial value of 1, any enterprise address book data change can cause the enterprise total version number to increase, and partial personnel permission change can not cause the _ VO change, namely other personnel are not influenced;
the unique enterprise basic information version number _ V1 is only related to the change of the enterprise basic information;
a unique enterprise data version number _ V2, associated with department data, personnel data and organizational relationships in the enterprise architecture;
the basic information version number _ VD1 of the department corresponding to each department, VD1 is related to the basic information of the current department, and the basic information comprises organization relation change;
the department data version number _ VD2 and _ VD2 set corresponding to each department are related to the personnel change of the current department;
the personnel virtual group version number _ VU set by part of personnel under the corresponding department is not unique, and the data of the associated personnel is changed;
each user has a separate personal version number _ UV.
Optionally, the step of updating the enterprise address book by the client is as follows:
the client needs to acquire the enterprise version number _ V0 and the personal version number _ UV again to detect whether the change is needed or not when the client is started;
if the version numbers of the _ UV and the _ V0 are the same as the locally stored version numbers, the data are unchanged after the updating detection is finished;
if the data exists locally but the value of _ V0 is 0, namely the current employee cannot view the enterprise address book, the enterprise address book needs to be cleared immediately;
if the personal version number _ UV changes, the local data needs to be updated in full, namely the local data is deleted, all the data are downloaded again, and the user pulls for the first time and also relates to the personal version number _ UV change;
if the total enterprise version number _ V0 changes, the server side is continuously accessed to obtain the basic enterprise information version number _ V1 and the enterprise data version number _ V2;
if the version number _ V1 of the enterprise basic information changes, directly requesting the enterprise basic data from the server;
if the enterprise data version number _ V2 changes, sending a request to a server and attaching a history version number _ V2 stored locally, and acquiring all changed department numbers and version numbers _ VD1 and _ VD2 thereof, wherein the changed department data comprises change, new addition and deletion;
if the version number _ VD1 of the department basic information changes, the department basic information needs to be acquired from the server;
if the department data version number _ VD2 changes, sending a request to the server and attaching a locally stored history version number _ VD 2;
the server side judges which virtual groups under a department change according to the old _ VD2 uploaded by the client side, all personnel data in the changed virtual groups are pushed to the client side, and the client side directly covers local data after receiving the personnel data;
and finally, the client stores the enterprise version number and the personal version obtained by the updating.
The method adopts a plurality of enterprise version numbers to subdivide the variation range, adopts the concept of department virtual groups, can reduce the consumption of the changed resources caused by variation as much as possible, adopts a uniform version number, judges whether the update is needed according to the version number, does not need to store incremental information for each employee any more compared with the prior art, and can strengthen the resource consumption of the server. And the personal version number _ UV is introduced, so that other persons can not be influenced when the visible authority of part of persons changes and needs to be updated in full.
Drawings
Fig. 1 is a schematic organization scheme according to an embodiment of the present invention.
Fig. 2 is a detailed flowchart of client update according to an embodiment of the present invention.
Detailed Description
Preferred embodiments of this patent are described in further detail below with reference to the accompanying drawings.
The embodiment of the application discloses a real-time and efficient enterprise address book updating method, which comprises the following steps:
firstly, connection needs to be established between a client and a server, and each employee needs to check an enterprise address book visible in the authority of the employee through the client.
The specific process of the client connecting to the server in this embodiment is as follows: and acquiring a communication key generated in real time, and encrypting all data in the current interaction period by using the communication key AES and then transmitting the encrypted data. And when the client logs in for the first time, the client uses the single password or the short message verification code to perform login authentication, and obtains the unique key with the validity period. The server needs to maintain the status of all users currently online.
The server stores a complete enterprise address book and authority relation, wherein the enterprise address book represents an organization architecture and comprises complete enterprise organization relation, enterprise basic information, department information and personnel information;
as shown in fig. 2, the organization structure in this embodiment is composed of multiple levels of departments and a plurality of employees in each department, and the concept of virtual groups is introduced to divide the employees in the same department into a plurality of virtual groups to subdivide the organization structure as much as possible.
In this embodiment, a plurality of enterprise version numbers are set to reflect related data of the enterprise address book, a correlation is established among the enterprise version numbers based on an organization structure, a personal version number of a staff is set to reflect a personal authority relationship of the staff, and a server maintains a plurality of version numbers of the enterprise and the personal version number of the staff.
With reference to fig. 2, the enterprise version number defined in this embodiment includes:
the unique enterprise total version number _ V0 has an initial value of 1, any enterprise address book data change can cause the enterprise total version number to increase, and partial personnel permission change can not cause the _ VO change, namely other personnel are not influenced;
the unique enterprise basic information version number _ V1 is only related to the change of the enterprise basic information;
a unique enterprise data version number _ V2, associated with department data, personnel data and organizational relationships in the enterprise architecture;
the basic information version number _ VD1 of the department corresponding to each department, VD1 is related to the basic information of the current department, and the basic information comprises organization relation change;
the department data version number _ VD2 and _ VD2 set corresponding to each department are related to the personnel change of the current department;
the personnel virtual group version number _ VU set by part of personnel under the corresponding department is not unique, and the data of the associated personnel is changed;
each user has a separate personal version number _ UV.
Table 1 is an exemplary illustration of rules for enterprise version numbers and individual version number changes
In combination with the above table, the change rule of each enterprise version number and each personal version number in this embodiment is as follows:
1) all the version numbers change in a one-way;
2) all changes of the enterprise address book data need to change the total version number _ VO of the enterprise, and partial personnel permission changes can not cause the changes of the _ VO, namely other personnel are not influenced;
3) enterprise basic information changes: self-increment of V0, wherein the version number of the enterprise basic information _ V1 is equal to self-increment _ V0;
4) adding a new department: self-increment of V0, wherein the basic information version number _ VD1 and the enterprise data version number _ V2 of the new department are equal to self-increment _ V0;
5) add/delete/move member: v0 self-increment by 1, the data version number _ VD2 and the enterprise data version number _ V2 of the department (excluding the upper and lower departments) are equal to the self-increment _ V0, and the personal version number _ UV of the change personnel is also self-increment by 1;
6) department basic information changes (including mobile departments): self-increment of V0, wherein the department basic information version number _ VD1 and the enterprise data version number _ V2 of the department D1 are equal to self-increment _ V0;
7) personnel information changes: self-increment of V0 by 1, wherein the data version number _ VD2 and the enterprise data version number _ V2 of the department (not including the upper and lower departments) are equal to the self-increment of _ V0, and if the personnel are in the virtual group, the virtual group version number _ VU of the personnel is equal to _ V0;
8) and deleting a department: self-increment 1 of _V0, enterprise data version number _ V2 equals self-incremented _ V0, and department deletes records according to _ V2;
9) individual independent rights change (setting/canceling invisible to all, hiding/displaying individual partial data): self-increment of V0 by 1, wherein the data version number _ VD2 and the enterprise data version number _ V2 of the department are equal to the self-increment of V0, and if the personnel are in the virtual group, the virtual group version number _ VU of the personnel is equal to V0;
10) permission group settings (some part of people can only see people within the group): v0 is unchanged (i.e. does not affect people outside the group), the personal version number UV of people within the group is increased by 1;
11) the isolated group setting means that only people in the group can be seen by the part of people in the isolated group, and people outside the group can not see the people in the group: self-increment of V0 by 1, wherein the data version number _ VD2 and the enterprise data version number _ V2 of the department are equal to the self-increment of V0, and the virtual group version numbers _ VU of all the personnel in the group are changed to be equal to V0;
12) specific authority changes, and when the visible relation aiming at part of people changes, the part of people are added/deleted, and visible people/invisible people: v0 is unchanged, personal version number of the changed person UV is incremented by 1.
In summary, the version number _ V1 of the enterprise basic information changes, and only the enterprise basic information needs to be updated; the version number _ VD1 of the basic information of the department changes, and only the basic information of the corresponding department needs to be updated; the department data version number _ VD2 changes, and only the personnel information of a specific virtual group of the corresponding department needs to be updated.
After the above detailed description of the enterprise version number and the personal version number, the following steps may be continuously performed based on the enterprise version number and the personal version number:
the client reserves the enterprise version number and the personal version number which are acquired when the client is connected with the server last time, the client needs to acquire the enterprise version number and the personal version number again when being connected with the server each time, and whether the enterprise address book needs to be updated is determined by comparing the version numbers:
if the enterprise version number changes, the specific position needing to be changed is determined according to the association between the specific changed enterprise version number and the enterprise organizational relationship,
if the personal version number changes, the enterprise address book of the client side needs to be updated in a full amount;
the server side calculates the user visible range in real time according to the user authority of the currently connected client side, generates temporary enterprise address book data for the user to see, and pushes the change information to the client side according to the user request.
With reference to fig. 2, the steps of the client updating the enterprise address book in the above method are described, and the specific steps of the client updating the enterprise address book are as follows:
the client needs to acquire the enterprise version number _ V0 and the personal version number _ UV again to detect whether the change is needed or not when the client is started;
if the version numbers of the _ UV and the _ V0 are the same as the locally stored version numbers, the data are unchanged after the updating detection is finished;
if the data exists locally but the value of _ V0 is 0, namely the current employee cannot view the enterprise address book, the enterprise address book needs to be cleared immediately;
if the personal version number _ UV changes, the local data needs to be updated in full, namely the local data is deleted, all the data are downloaded again, and the user pulls for the first time and also relates to the personal version number _ UV change;
if the total enterprise version number _ V0 changes, the server side is continuously accessed to obtain the basic enterprise information version number _ V1 and the enterprise data version number _ V2;
if the version number _ V1 of the enterprise basic information changes, directly requesting the enterprise basic data from the server;
if the enterprise data version number _ V2 changes, sending a request to a server and attaching a history version number _ V2 stored locally, and acquiring all changed department numbers and version numbers _ VD1 and _ VD2 thereof, wherein the changed department data comprises change, new addition and deletion;
if the version number _ VD1 of the department basic information changes, the department basic information needs to be acquired from the server;
if the department data version number _ VD2 changes, sending a request to the server and attaching a locally stored history version number _ VD 2;
the server side judges which virtual groups under a department change according to the old _ VD2 uploaded by the client side, all personnel data in the changed virtual groups are pushed to the client side, and the client side directly covers local data after receiving the personnel data;
and finally, the client stores the enterprise version number and the personal version obtained by the updating.
The complete process of one-time updating of the client is realized.
As can be seen from the above, the invention has the following advantages due to the adoption of the method: 1. subdividing the variation range, and adopting a department virtual group concept to reduce the consumption of variation resources caused by variation as much as possible; 2. the uniform version number is adopted, so that increment information does not need to be saved for each employee, and resource consumption of a server is reduced; 3. by using the personal version number _ UV, when the visible authority of part of personnel changes and needs to be updated in full, other personnel can not be influenced; 4. the online state of the user is maintained, and the data change can be synchronized in real time.
It should be noted that, those skilled in the art implement the above real-time and efficient enterprise address book updating method through a computer program, and therefore, in order to implement the above method, it is necessary to provide a storage medium on which the computer program is stored, and the program is executed by a processor to implement the above real-time and efficient enterprise address book updating method. Accordingly, there is a need to provide an apparatus, which includes a processor and a storage medium, wherein the storage medium stores a computer program, and the program is executed by the processor to implement the real-time and efficient enterprise address book updating method as described above.
Claims (3)
1. A real-time and efficient enterprise address book updating method is characterized by comprising the following steps:
the server stores a complete enterprise address book and an authority relationship, wherein the enterprise address book represents an enterprise architecture and comprises a complete enterprise organization relationship, enterprise basic information, department information and personnel information;
setting a plurality of enterprise version numbers to reflect related data of enterprise address records, establishing association among the enterprise version numbers based on an organization structure, setting personal version numbers of employees to reflect personal authority relationships of the employees, and maintaining the plurality of version numbers of the enterprises and the personal version numbers of the employees by a server;
the client reserves the enterprise version number and the personal version number which are acquired when the client is connected with the server last time, the client needs to acquire the enterprise version number and the personal version number again when being connected with the server each time, and whether the enterprise address book needs to be updated is determined by comparing the version numbers:
if the enterprise version number changes, determining the specific position to be changed according to the association between the specific changed enterprise version number and the enterprise organization relationship, and if the personal version number changes, updating the enterprise address book of the client in full;
the server side calculates the user visible range in real time according to the user authority of the currently connected client side, generates temporary enterprise address book data for the user to see, and pushes the change information to the client side according to the user request;
the enterprise version number includes:
the unique enterprise total version number _ V0 has an initial value of 1, any enterprise address book data change can cause the enterprise total version number to increase, and partial personnel permission change can not cause the _ VO change, namely other personnel are not influenced;
the unique enterprise basic information version number _ V1 is only related to the change of the enterprise basic information;
a unique enterprise data version number _ V2, associated with department data, personnel data and organizational relationships in the enterprise architecture;
the basic information version number _ VD1 of the department corresponding to each department, VD1 is related to the basic information of the current department, and the basic information comprises organization relation change;
the department data version number _ VD2 and _ VD2 set corresponding to each department are related to the personnel change of the current department;
the personnel virtual group version number _ VU set by part of personnel under the corresponding department is not unique, and the data of the associated personnel is changed;
each user has an independent personal version number _ UV;
the step of updating the enterprise address book by the client is as follows:
the client needs to acquire the enterprise version number _ V0 and the personal version number _ UV again to detect whether the change is needed or not when the client is started;
if the version numbers of the _ UV and the _ V0 are the same as the locally stored version numbers, the data are unchanged after the updating detection is finished;
if the data exists locally but the value of _ V0 is 0, namely the current employee cannot view the enterprise address book, the enterprise address book needs to be cleared immediately;
if the personal version number _ UV changes, the local data needs to be updated in full, namely the local data is deleted, all the data are downloaded again, and the user pulls for the first time and also relates to the personal version number _ UV change;
if the total enterprise version number _ V0 changes, the server side is continuously accessed to obtain the basic enterprise information version number _ V1 and the enterprise data version number _ V2;
if the version number _ V1 of the enterprise basic information changes, directly requesting the enterprise basic data from the server;
if the enterprise data version number _ V2 changes, sending a request to a server and attaching a history version number _ V2 stored locally, and acquiring all changed department numbers and version numbers _ VD1 and _ VD2 thereof, wherein the changed department data comprises change, new addition and deletion;
if the version number _ VD1 of the department basic information changes, the department basic information needs to be acquired from the server;
if the department data version number _ VD2 changes, sending a request to the server and attaching a locally stored history version number _ VD 2;
the server side judges which virtual groups under a department change according to the old _ VD2 uploaded by the client side, all personnel data in the changed virtual groups are pushed to the client side, and the client side directly covers local data after receiving the personnel data;
and finally, the client stores the enterprise version number and the personal version obtained by the updating.
2. The method for updating the enterprise address book in real time and efficiently according to claim 1, further comprising the steps of:
each time the client is connected with the server, a real-time communication key needs to be generated, and all data in the current interaction period are encrypted by using the communication key AES and then transmitted.
3. The method for updating the enterprise address book in real time and efficiently according to claim 1, further comprising the steps of:
the server side maintains the states of all current online users, calculates the variation influence range in real time when the server side data varies, and informs all online personnel in the influence range.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910655186.7A CN110535903B (en) | 2019-07-19 | 2019-07-19 | Real-time and efficient enterprise address book updating method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910655186.7A CN110535903B (en) | 2019-07-19 | 2019-07-19 | Real-time and efficient enterprise address book updating method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110535903A CN110535903A (en) | 2019-12-03 |
| CN110535903B true CN110535903B (en) | 2021-10-19 |
Family
ID=68660416
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910655186.7A Active CN110535903B (en) | 2019-07-19 | 2019-07-19 | Real-time and efficient enterprise address book updating method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110535903B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111476534A (en) * | 2020-03-20 | 2020-07-31 | 深圳万威科技有限公司 | Method for processing architecture version and authority in enterprise management system |
| CN113872994A (en) * | 2020-06-30 | 2021-12-31 | 腾讯科技（深圳）有限公司 | Organization architecture synchronization method, device, computer equipment and storage medium |
| CN113824811A (en) * | 2021-08-25 | 2021-12-21 | 北京平治东方科技股份有限公司 | System and method for managing address book of internal telephone network of large enterprise |
| CN115604285A (en) * | 2022-08-26 | 2023-01-13 | 紫光云技术有限公司（Cn） | Method for realizing address book of App terminal |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101895579A (en) * | 2010-07-08 | 2010-11-24 | 中兴通讯股份有限公司 | Address book synchronization method and system |
| CN102959905B (en) * | 2011-04-09 | 2016-03-02 | 华为技术有限公司 | Method, Apparatus and system that associated person information is synchronous |
| CN102510357A (en) * | 2011-09-26 | 2012-06-20 | 深圳中兴网信科技有限公司 | Synchronous method of enterprise organization structure address book and system thereof |
| CN107071080B (en) * | 2011-10-20 | 2020-11-17 | 华为技术有限公司 | Method and system for maintaining contact information |
| CN104469741A (en) * | 2014-11-17 | 2015-03-25 | 小米科技有限责任公司 | Terminal configuration method and device |
| CN105933402A (en) * | 2016-04-19 | 2016-09-07 | 福建星网智慧科技股份有限公司 | Method for synchronizing enterprise contacts |
| CN106056365A (en) * | 2016-07-07 | 2016-10-26 | 珠海佳米科技有限公司 | Enterprise address book visibility authority control method and apparatus |
| CN107528909A (en) * | 2017-09-05 | 2017-12-29 | 无锡智谷锐拓技术服务有限公司 | A kind of synchronous method of network communication contact book data cloud |
| CN109194779A (en) * | 2018-09-14 | 2019-01-11 | 山东浪潮通软信息科技有限公司 | A kind of safe and efficient enterprise directory update method |
-
2019
- 2019-07-19 CN CN201910655186.7A patent/CN110535903B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN110535903A (en) | 2019-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110535903B (en) | Real-time and efficient enterprise address book updating method | |
| US20220360609A1 (en) | Ephemeral control of a data resource according to a use policy | |
| US10356094B2 (en) | Uniqueness and auditing of a data resource through an immutable record of transactions in a hash history | |
| US11853457B2 (en) | Selectively verifying personal data | |
| JP3222165U (en) | System to realize universal distributed solution for user authentication by mutual authentication configuration | |
| CN109242326B (en) | Policy sharing system based on big data and artificial intelligence | |
| US20240031167A1 (en) | Systems and methods for maintaining decentralized digital identities | |
| US7516134B2 (en) | Controlling access to a database using database internal and external authorization information | |
| US9077710B1 (en) | Distributed storage of password data | |
| CN111371805A (en) | Token-based unified identity authentication interface and method | |
| US8838679B2 (en) | Providing state service for online application users | |
| US20220263660A1 (en) | Authentication through use of an unforgable hash function based credential | |
| US8818906B1 (en) | Systems and methods for performing authentication of a customer interacting with a banking platform | |
| CN101529412A (en) | Data file access control | |
| CN109691057A (en) | Sensitive content is convertibly fetched via private contents distribution network | |
| US10540511B2 (en) | Information rights management offline file access facility | |
| CN108650289B (en) | Method and device for managing data based on block chain | |
| US20140105399A1 (en) | Method for providing application service | |
| CN103546544A (en) | Data management system on basis of cloud computing | |
| CN109241352A (en) | The acquisition methods and server of Profile information | |
| US11394542B2 (en) | Deauthorization of private key of decentralized identity | |
| CN109845183A (en) | For from client device to the method for cloud storage system storing data block | |
| CN108369614A (en) | User authen method and system for carrying out the process | |
| US9432344B2 (en) | Secure storage and sharing of user objects | |
| CN115859362A (en) | Data storage system, method, device and medium based on block chain side chain |
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 |