CN112738008B - Information synchronous changing method, device, computer and readable storage medium - Google Patents

Information synchronous changing method, device, computer and readable storage medium Download PDF

Info

Publication number
CN112738008B
CN112738008B CN201911032411.8A CN201911032411A CN112738008B CN 112738008 B CN112738008 B CN 112738008B CN 201911032411 A CN201911032411 A CN 201911032411A CN 112738008 B CN112738008 B CN 112738008B
Authority
CN
China
Prior art keywords
information
change
communication client
callback
service
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
Application number
CN201911032411.8A
Other languages
Chinese (zh)
Other versions
CN112738008A (en
Inventor
赖旭凯
莫云飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201911032411.8A priority Critical patent/CN112738008B/en
Publication of CN112738008A publication Critical patent/CN112738008A/en
Application granted granted Critical
Publication of CN112738008B publication Critical patent/CN112738008B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • 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
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • 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
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P80/00—Climate change mitigation technologies for sector-wide applications
    • Y02P80/10—Efficient use of energy, e.g. using compressed air or pressurized fluid as energy carrier

Abstract

The embodiment of the application discloses an information synchronous changing method, which comprises the following steps: the first communication client side obtains service change information; responding to the submission operation aiming at the service change information, calling a change notification address and a callback token from the callback parameter, and generating an information change message according to the change notification address, the callback token and the service change information; the event server refers to a server pointed by the change notification address; sending an information change message to the event server so that the event server sends the service change information in the information change message to the second communication client; the service change information is used for updating service data in the second communication client. By adopting the method and the device, when the business change information appears in the first communication client, the business change information is sent to other communication clients through the event server, so that the other communication clients can update own business data in time, synchronous change of the information is realized, and the unified management efficiency of the information is improved.

Description

Information synchronous changing method, device, computer and readable storage medium
Technical Field
The present application relates to the field of computing technologies, and in particular, to a method and an apparatus for synchronously changing information, a computer, and a readable storage medium.
Background
With the development of the internet, people have more and more online activities, and due to the high efficiency, convenience and the like of information propagation, data management and member management in the internet, enterprises and the like mostly perform mobile office through the internet so as to improve the management efficiency and the information propagation rate of the interior of the enterprises. Currently, many enterprises use Instant Messaging (IM) tools, mobile Office platforms (mobile Office platforms, etc.) to manage enterprise data so as to perform mobile Office, such as Active Directory (AD) systems, Human Resource (HR) systems, mailbox systems, Office Automation (OA) systems, etc. However, based on different purposes of use, an enterprise may use a plurality of mobile office platforms or IMs, which requires a manager to uniformly update different mobile office platforms or IMs when business data in the enterprise is changed, thereby wasting time and energy. Because the office data of the enterprise is very important, when the business data of the enterprise changes, if the relevant configuration in the enterprise cannot be changed, the office data of the enterprise may be leaked, for example, when an employee leaves, if the relevant data of the employee cannot be updated in time, including employee information and the authority owned by the employee, the employee may still access the relevant office data of the enterprise, and the office data of the enterprise may be leaked. Therefore, how to effectively manage information and intelligently and efficiently change information becomes an urgent problem to be solved.
Disclosure of Invention
The embodiment of the application provides an information synchronous change method and device, which can improve the intelligence and efficiency of information synchronous change and improve the unified management efficiency of information.
A first aspect of the embodiments of the present application provides an information synchronization changing method, including:
the first communication client side obtains service change information;
responding to the submission operation aiming at the service change information, calling a change notification address and a callback token from a callback parameter, generating a callback address based on the callback token and the change notification address, and generating an information change message according to the callback address and the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with an event server; the event server is a server pointed by the change notification address, and is configured with a communication address of a second communication client;
sending the information change message to the event server, so that the event server sends the service change information in the information change message to the second communication client indicated by the communication address after verifying the validity of the information change message according to the callback token; the service change information is used for updating service data in the second communication client; the first communication client, the event server and the second communication client belong to different service platforms respectively.
Wherein the method further comprises:
obtaining the callback parameters in a configuration interface, wherein the callback parameters comprise the change notification address and the callback token;
responding to the configuration operation aiming at the callback parameter, storing the callback parameter, and sending the callback parameter to the event server pointed by the change notification address through the change notification address so that the event server configures the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server.
Wherein the callback parameter further comprises a key;
the generating of the information change message according to the callback address and the service change information includes:
encrypting the service change information through the key to obtain encrypted information, and generating the information change message according to the callback address and the encrypted information; and the key is used for indicating the event server to decrypt the encrypted information when receiving the information change message.
Wherein generating a callback address based on the callback token and the change notification address comprises:
acquiring a random parameter, and generating a first encryption signature based on the callback token and the random parameter;
splicing the change notification address, the first encryption signature and the random parameter to obtain the callback address; and the first encryption signature and the random parameter are used for verifying the legality of the information change message when the event server receives the information change message.
A second aspect of the present application provides an information synchronization changing method, including:
the method comprises the steps that an event server obtains an information change message sent by a first communication client through a change notification address, wherein the information change message is generated by the first communication client according to a callback address and service change information, the callback address is generated by the first communication client based on a callback token in a callback parameter and the change notification address, and the change notification address is an address called from the callback parameter when the first communication client responds to submission operation aiming at the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with the event server; the event server is a server to which the change notification address points;
verifying the legality of the information change message according to the callback address in the information change message, and if the information change message is a legal message, extracting the service change information in the information change message;
sending the service change information to a second communication client indicated by a configured communication address, so that the second communication client updates first service data recorded in the second communication client based on the service change information, and the event server is configured with the communication address of the second communication client; the first communication client, the event server and the second communication client belong to different service platforms respectively.
Wherein the method further comprises:
obtaining a callback parameter which is sent by the first communication client and carries the change notification address and the callback token, and configuring the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server.
Wherein the callback parameter further comprises a key; the information change message comprises the callback address and encrypted information, and the encrypted information is obtained by encrypting the service change information through the secret key by the first communication client;
the extracting the service change information in the information change message includes:
acquiring the encrypted information in the information change message;
and decrypting the encrypted information through the key to obtain the service change information.
The information change message comprises the callback address and the service change information; the callback address comprises the change notification address, the random parameter and a first encryption signature; the first encrypted signature is generated by the first communication client based on the callback token and the random parameter;
the verifying the validity of the information change message according to the callback address in the information change message includes:
acquiring the callback address in the information change message, and generating a second encryption signature according to the callback token and the random parameter in the callback address;
if the second encrypted signature is the same as the first encrypted signature, the information change message is represented as a legal message, and the step of extracting the service change information in the information change message is executed;
and if the second encrypted signature is different from the first encrypted signature, indicating that the information change message is an illegal message, and sending a synchronous change failure message to the first communication client.
Wherein the method further comprises:
if the accumulated time reaches the target time length, acquiring second service data of the first communication client and updated first service data in the second communication client;
if the second service data is different from the updated first service data, sending an information change abnormal message to the second communication client, so that the second communication client updates the updated first service data based on the second service data in the information change abnormal message;
and if the second service data is the same as the updated first service data, sending a message synchronous change normal message to the second communication client.
Wherein the method further comprises:
sending a data format aiming at the service change information to the second communication client;
the sending the service change information to the second communication client indicated by the configured communication address includes:
and packaging the service change information into packaged data with the data format, and sending the packaged data to the second communication client indicated by the configured communication address, so that the second communication client acquires each parameter included in the packaged data based on the data format, and changes the first service data recorded in the second communication client through each parameter.
A third aspect of the embodiments of the present application provides an information synchronization changing apparatus, including:
the first acquisition module is used for the first communication client to acquire the service change information;
the generating module is used for responding to the submission operation aiming at the service change information, calling a change notification address and a callback token from a callback parameter, generating a callback address based on the callback token and the change notification address, and generating an information change message according to the callback address and the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with the event server; the event server is a server pointed by the change notification address, and is configured with a communication address of a second communication client;
a sending module, configured to send the information change packet to the event server, so that after verifying the validity of the information change packet according to the callback token, the event server sends the service change information in the information change packet to the second communication client indicated by the communication address; the service change information is used for updating service data in the second communication client;
the first communication client, the event server and the second communication client belong to different service platforms respectively.
Wherein the apparatus further comprises:
a second obtaining module, configured to obtain the callback parameter in a configuration interface, where the callback parameter includes the change notification address and the callback token;
the response module is used for responding the configuration operation aiming at the callback parameter, storing the callback parameter and sending the callback parameter to the event server pointed by the change notification address through the change notification address so as to enable the event server to configure the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server.
Wherein the callback parameter further comprises a key;
in the aspect of generating an information change packet according to the callback address and the service change information, the generating module includes:
the encryption unit is used for encrypting the service change information through the secret key to obtain encrypted information; the key is used for indicating the event server to decrypt the encrypted information when receiving the information change message;
and the first generating unit is used for generating the information change message according to the callback address and the encryption information.
Wherein, in the aspect of generating the callback address based on the callback token and the change notification address, the generating module further includes:
the second generation unit is used for acquiring a random parameter and generating a first encryption signature based on the callback token and the random parameter;
the splicing unit is used for splicing the change notification address, the first encryption signature and the random parameter to obtain the callback address; and the first encryption signature and the random parameter are used for verifying the legality of the information change message when the event server receives the information change message.
A fourth aspect of the embodiments of the present application provides an apparatus for synchronously changing information, where the apparatus includes:
a first obtaining module, configured to obtain, by an event server, an information change packet sent by a first communication client through a change notification address, where the information change packet is generated by the first communication client according to a callback address and service change information, the callback address is generated by the first communication client based on a callback token in a callback parameter and the change notification address, and the change notification address is an address called from the callback parameter by the first communication client when responding to a commit operation for the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with the event server; the event server is a server to which the change notification address points;
the extraction module is used for verifying the legality of the information change message according to the callback address in the information change message, and extracting the service change information in the information change message if the information change message is a legal message;
a first sending module, configured to send the service change information to a second communication client indicated by a configured communication address, so that the second communication client updates first service data recorded in the second communication client based on the service change information, and the event server is configured with the communication address of the second communication client;
the first communication client, the event server and the second communication client belong to different service platforms respectively.
Wherein the apparatus further comprises:
the second obtaining module is used for obtaining a callback parameter which is sent by the first communication client and carries the change notification address and the callback token, and configuring the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server.
Wherein the callback parameter further comprises a key; the information change message comprises the callback address and encrypted information, and the encrypted information is obtained by encrypting the service change information through the secret key by the first communication client;
in the aspect of extracting the service change information in the information change message, the extracting module includes:
a first obtaining unit configured to obtain the encrypted information in the information change message;
and the decryption unit is used for decrypting the encrypted information through the key to obtain the service change information.
Wherein, the message of information change includes the callback address and the service change information; the callback address comprises the change notification address, the random parameter and a first encryption signature; the first encrypted signature is generated by the first communication client based on the callback token and the random parameter;
in the aspect of verifying the validity of the information change message according to the callback address in the information change message, the extraction module further includes:
a second obtaining unit, configured to obtain the callback address in the information change message;
the generating unit is used for generating a second encryption signature according to the callback token and the random parameter in the callback address;
a comparison unit for comparing the second encrypted signature with the first encrypted signature;
the comparing unit is further configured to indicate that the information change message is a legal message if the second encrypted signature is the same as the first encrypted signature, and execute the step of extracting the service change information in the information change message through the extracting module;
and the first sending unit is used for indicating that the information change message is an illegal message if the second encryption signature is different from the first encryption signature, and sending a synchronous change failure message to the first communication client.
Wherein the apparatus further comprises:
a third obtaining module, configured to obtain second service data of the first communication client and updated first service data in the second communication client if the accumulated time reaches the target time length;
a second sending module, configured to send an information change exception message to the second communication client if the second service data is different from the updated first service data, so that the second communication client updates the updated first service data based on the second service data in the information change exception message;
the second sending module is further configured to send a message that the information is changed normally synchronously to the second communication client if the second service data is the same as the updated first service data.
Wherein the apparatus further comprises:
a third sending module, configured to send a data format for the service change information to the second communication client;
the first sending module includes:
the encapsulation unit is used for encapsulating the service change information into encapsulated data with the data format;
and the second sending unit is used for sending the encapsulated data to the second communication client indicated by the configured communication address so that the second communication client can acquire all parameters included in the encapsulated data based on the data format and change the first service data recorded in the second communication client through all the parameters.
A fifth aspect of the embodiments of the present application provides a computer, including a processor, a memory, and an input/output interface;
the processor is connected to the memory and the input/output interface, respectively, where the input/output interface is used for inputting data and outputting data, the memory is used for storing program codes, and the processor is used for calling the program codes to execute the information synchronization changing method as described in the first aspect of the embodiment of the present application or the second aspect of the embodiment of the present application.
A sixth aspect of embodiments of the present application provides a computer-readable storage medium, which stores a computer program, where the computer program includes program instructions, and the program instructions, when executed by a processor, perform an information synchronization change method as described in the first aspect of embodiments of the present application or the second aspect of embodiments of the present application.
The embodiment of the application has the following beneficial effects:
the embodiment of the application calls the change notification address and the callback token from the callback parameter in response to the submission operation aiming at the service change information when the first communication client side acquires the service change information, generates the callback address according to the callback token and the change notification address, generates the information change message according to the callback address and the service change information, sends the information change message to the event server pointed by the change notification address based on the change notification address, verifies the legality of the information change message according to the callback address in the information change message after the event server acquires the information change message sent by the first communication client side, extracts the service change information in the information change message if the information change message is legal, and sends the service change information to the second communication client side indicated by the configured communication address, and the second communication client updates the first service data recorded in the second communication client based on the service change information, thereby realizing the unified update management of the information. Specifically, when the first communication client is used as the central communication client, when the service data in the first communication client changes, the changed service data is called back to the event server, the event server sends the changed service data to the second communication client, and the second communication client can update the service data based on the received changed service data, so that the data consistency can be ensured in each communication client in the same information network, thereby improving the intelligence and efficiency of information synchronous change, and further improving the efficiency of information unified update management.
Drawings
In order to more clearly illustrate the embodiments of the present application 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, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1a is a diagram of an information synchronization change architecture according to an embodiment of the present application;
fig. 1b is a schematic diagram of an information synchronization change process provided in an embodiment of the present application;
fig. 2 is a flowchart of an information synchronization changing method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a member management page provided in an embodiment of the present application;
fig. 4 is a flowchart of another information synchronization changing method provided in an embodiment of the present application;
fig. 5 is a schematic view of an interaction flow of information synchronization change according to an embodiment of the present application;
fig. 6a is a schematic view of an information synchronous change interface according to an embodiment of the present application;
fig. 6b is a schematic diagram illustrating a callback parameter setting provided in an embodiment of the present application;
fig. 6c is a schematic diagram illustrating another callback parameter setting provided in the embodiment of the present application;
fig. 7 is a schematic diagram of service change data input based on a front-end page according to an embodiment of the present application;
FIG. 8 is a schematic diagram of a scenario of changing data by an individual user according to an embodiment of the present application;
FIG. 9 is a diagram of an information-synchronized change data transfer provided by an embodiment of the present application;
fig. 10 is a schematic diagram of an information synchronization changing apparatus according to an embodiment of the present application;
fig. 11 is a schematic diagram of another information synchronous changing apparatus provided in an embodiment of the present application;
fig. 12 is a schematic structural diagram of a computer according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, 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 application.
Specifically, please refer to fig. 1a, fig. 1a is an information synchronization change architecture diagram provided in the embodiment of the present application, as shown in fig. 1a, for an organization, the architecture includes a first communication client 101, a plurality of second communication clients 103, and an event server 102, where the communication clients constitute a mobile office environment of the organization, the first communication client 101, the event server 102, and the plurality of second communication clients 103 respectively belong to different service platforms, the event server 102 belongs to a service platform of the organization, and for a management background of the organization, the first communication client 101 and the plurality of second communication clients 103 respectively belong to an application, and each application belongs to a service platform for developing the application, where the organization may be an enterprise, a department, or an organization. When the first communication client 101 monitors a submitting operation for the service change information, the first communication client 101 acquires data submitted in a service change page as the service change information, responds to the submitting operation for the service change information, acquires a change notification address from a callback parameter, and generates an information change message according to the change notification address and the service change information, wherein the callback parameter is a parameter configured by the first communication client 101 and used for communicating with the event server 102, the event server 102 is a server to which the change notification address points, and the first communication client 101 sends the information change message to the event server 102. Because the event server belongs to the management background of the organization, cross-platform communication between the first communication client and the second communication client can be avoided by means of communication between the event server and the first communication client and the second communication client respectively, and the event server can manage relevant information of the organization, namely service data of the organization in the first communication client and the second communication client can be managed, so that synchronous updating of address lists of different service platforms can be realized without cross-platform communication, namely cross-platform communication development of a service platform to which the first communication client belongs and a service platform to which the second communication client belongs is not required, and development cost of cross-platform synchronous updating is reduced.
The first communication client 101 and the plurality of second communication clients 103 herein each include a front end and a background corresponding to the communication client, and the front end of the first communication client 101 or the front end of the second communication client 103 is an electronic device, including but not limited to a mobile phone, a tablet computer, a desktop computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), a wearable device (e.g., a smart watch, a smart bracelet, etc.), and the like. For an organization, the service data of the organization is managed by using application programs developed by a plurality of service platforms, one of the application programs is determined as the first communication client 101, other application programs are determined as the second communication client 103, and the first communication client 101 background and the plurality of second communication client 103 backgrounds respectively correspond to servers in the organization for processing the communication clients. For an organization, the application programs used for mobile office work include and only include the first communication client 101 and the plurality of second communication clients 103, so that the business data of all the application programs needing to be changed in the organization can be updated through the information synchronous change process. In other words, the second communication client 103 is an application other than the first communication client 101 among all applications used by the organization.
Specifically referring to fig. 1b, fig. 1b is a schematic diagram of an information synchronization change process provided in an embodiment of the present application, and fig. 1b is a schematic diagram of an information synchronization change process based on that shown in fig. 1a, as shown in fig. 1b, a first communication client 101 shown in fig. 1a includes a first communication client front end 101a and a first communication client background 101b, and a second communication client 1031 is any one of a plurality of second communication clients 103 shown in fig. 1 a. In the embodiment of the present application, when information synchronization change is performed, first, through the process shown in fig. 1b, a callback parameter negotiation is performed between the first communication client 101 and the event server 102, and then, through the process shown in fig. 1b, an information synchronization change process between the first communication client 101 and the second communication client 1031 is implemented. Specifically, a callback parameter is configured in the first communication client front end 101a, the callback parameter at least includes a change notification address and a callback token, the first communication client background 101b obtains the callback parameter configured in the first communication client front end 101a, the callback parameter is sent to the event server 102 through the change notification address in the callback parameter, and the event server 102 stores the callback parameter after receiving the callback parameter, wherein the callback parameter is used for establishing communication connection between the first communication client 101 and the event server 102, and the change notification address in the callback parameter is used for sending the changed service data to the event server 102 to which the change notification address points when the service data in the first communication client 101 changes.
When the service change information is acquired in the first communication client front-end 101a, the first communication client back-end 101b acquires the service change information in the first communication client front-end 101a in response to a commit operation for the service change information, and generates an information change message according to the service change information and the configured callback parameter, the first communication client back-end 101b sends the generated information change message to the event server 102 based on the change notification address by acquiring the change notification address in the callback parameter, the event server 102 verifies the validity of the information change message by the callback token in the callback parameter based on the callback parameter stored in the event server 102 after receiving the information change message, extracts the service change information in the information change message when the information change message is a valid message, and sends the service change information to the second communication client 1031, the second communication client 1031 can update the service data recorded by the second communication client 1031 based on the service change information, thereby realizing unified data update for all communication clients included in the mobile office environment of the organization and ensuring the consistency of the service data of each communication client.
For example, a first enterprise uses four applications for managing employee information in the first enterprise, one of the four applications is a configured first communication client, the other of the four applications is a second communication client, and the first enterprise does not use other applications to manage employee information in the first enterprise except for the four applications. When the employee leaves the job in the first enterprise, the employee is employee A, the manager of the first enterprise inputs the information of the employee A in the first communication client front end 101a, the leaving information of the employee a is service change information, and when the first communication client background 101b monitors the submitting operation of the service change information, the service change information is acquired, and responding to the submitting operation, acquiring the configured change notification address, sending the service change information to the event server 102 pointed by the change notification address, after the event server 102 receives the service change information, the service change information is transmitted to the second communication client 1031, the second communication client 1031 deletes the information related to employee a based on the service change information, and closes the authority of the employee a owned by the first enterprise, so that the business data in the first communication client 101 and the plurality of second communication clients 103 are kept consistent.
Further, please refer to fig. 2, and fig. 2 is a flowchart of an information synchronization changing method according to an embodiment of the present application. As shown in fig. 2, the first communication client is used as a main body for description, and the information synchronization change process includes the following steps:
step S201, the first communication client obtains service change information.
Specifically, when the service data change occurs, the manager submits the service change data through the service change page of the first communication client to change the service data of the first communication client, and the first communication client monitors the submission operation of the service change page to obtain the service change information of the service change page, wherein the service change information is composed of the service change data of the service change page. The first communication client comprises a front end and a background corresponding to the first communication client, a manager inputs service change data on a service change page of the front end of the first communication client, and the background of the first communication client monitors operations occurring at the front end of the first communication client so as to acquire data, display data or execute corresponding processes and the like according to the monitored operations. The service change information here includes, but is not limited to, service change data generated by employee entry, employee departure, call, and department adjustment in the enterprise, addition, change, deletion, and the like of departments in the enterprise, and the service change information may be composed of service change data generated by the enterprise, school, or organization, and the like. The service data recorded in each communication client may be member information and/or office information in an organization, and is not limited herein.
Specifically, referring to fig. 3, the schematic view of a member management page provided in the embodiment of the present application is shown in fig. 3, where the business data recorded in the communication client is member information of a company XX, and a manager can view all member information in the company XX in the member management page, where each member information includes a name, a job title, a department, a mobile phone number, a mailbox, and the like of the member. The management personnel can uniformly manage the member information displayed in the page through the member management page, so that the member information of each member in the XX company can be added, modified or deleted, when the management personnel changes the member information of any member of the XX company, the changed member information is submitted, the first communication client side monitors the submitting operation of the changed member information, and the changed member information submitted in the member management page is obtained, so that the service change information is obtained.
Step S202, responding to the submitting operation of the service change information, calling a change notification address and a callback token from the callback parameter, and generating an information change message according to the callback token, the change notification address and the service change information.
Specifically, the submission operation of the service change information is responded, a change notification address and a callback token are obtained from a callback parameter, a callback address is generated based on the callback token and the change notification address, and an information change message is generated according to the callback address and the service change information. Specifically, after the service change information is acquired, a change notification address is acquired in response to a commit operation of the service change information, so as to determine an address to which the service change information is sent. The callback parameter is a parameter configured by the first communication client for communicating with the event server, and the change notification address is an address of the event server configured in the first communication client.
Specifically, the first communication client is configured with a callback parameter, the callback parameter at least includes a change notification address and a callback token, the change notification address is used for indicating an address of an event server which receives and forwards the service change information, the callback token is used for indicating identity information of the first communication client, after the first communication client acquires the service change information, the first communication client responds to a submission operation aiming at the service change information to acquire the change notification address in the callback parameter, the callback address is generated based on the callback token and the change notification address, an information change message is generated according to the callback address and the service change information, and the information change message is used for representing that the service change information is sent to the event server which the change notification address points to.
Step S203, sending the information change message to the event server, so that the event server sends the service change information in the information change message to the second communication client.
Specifically, an information change message is sent to the event server, so that the event server sends service change information in the information change message to the second communication client after receiving the information change message, and the service change information is used for updating service data in the second communication client. Specifically, the first communication client sends the service change information in the information change message to the event server by calling back the change notification address in the parameter, when the event server monitors that the change notification address is accessed, the information change message received by the change notification address is acquired, the callback address in the information change message is acquired, the legality of the information change message is verified based on the callback address, when the message is legal, extracting the service change message from the message, sending the service change message to the second communication client terminal indicated by the configured communication address, so that the second communication client can update its own recorded service data based on the received service change information, the number of the second communication clients can be one or more, and the configured communication address is the communication address of the second communication client configured by the event server. The change notification address is a Uniform Resource Locator (URL), where the URL is used to locate an address of the event server for processing the service change information, and is an access port of the event server, and after the first communication client generates the information change packet, the first communication client determines the access port of the event server according to the change notification address in the information change packet, establishes a communication connection with the event server through the access port, and sends the service change information in the information change packet to the event server through the communication connection.
Further, please refer to fig. 4, where fig. 4 is a flowchart of another information synchronization changing method provided in the embodiment of the present application. As shown in fig. 4, the information synchronization change process is described by taking an event server as a main body, and includes the following steps:
step S401, the event server obtains the information change message sent by the first communication client through the change notification address.
Specifically, the event server obtains an information change message sent by the first communication client through a change notification address, the information change message is generated by the first communication client according to a callback address and service change information, the callback address is generated by the first communication client based on a callback token in a callback parameter and the change notification address, the change notification address is an address called from the callback parameter by the first communication client when responding to a submission operation for the service change information, the callback parameter is a parameter configured by the first communication client and used for communicating with the event server, and the event server is a server to which the change notification address points. Specifically, after the first communication client configures the callback parameter, the callback parameter is sent to the event server, so that the event server stores the callback parameter configured by the first communication client, the callback parameter at least comprises a change notification address and a callback token, so that the first communication client can establish communication connection with the event server through the callback parameter, and the event server obtains the information change message sent by the first communication client based on the communication connection. Optionally, the callback parameter may be composed of any one or more of a change notification address, a callback token, a key, and the like.
Under the condition of the first callback parameter, if the callback parameter comprises a change notification address, after receiving the callback parameter, the event server configures the callback parameter, wherein the callback parameter is used for indicating the communication relationship between the first communication client and the event server, and the first communication client establishes communication connection with the event server through the change notification address. The first communication client generates an information change message according to the change notification address and the service change information, sends the information change message to the event server through the change notification address, and the event server acquires the information change message received in the change notification address.
Under the second callback parameter condition, if the callback parameter includes a change notification address and a key, the event server configures the callback parameter after receiving the callback parameter, the change notification address is used for establishing communication connection between the first communication client and the event server, the key is used for encrypting and decrypting data, and the data is service change information. The first communication client encrypts the service change information through a secret key to obtain encrypted information, and generates an information change message through the encrypted information and the change notification address, the first communication client sends the information change message to an event server, and the event server obtains the information change message sent by the first communication client, wherein the information change message comprises the encrypted information and the change notification address.
Under the third callback parameter condition, if the callback parameter includes a change notification address and a callback token, the event server configures the callback parameter after receiving the callback parameter, wherein the change notification address is used for establishing communication connection between the first communication client and the event server, and the callback token is used for verifying the identity of the first communication client by the event server, namely verifying the validity of the information change message sent by the first communication client. The method comprises the steps that a first communication client generates a random parameter, a first encryption signature is generated according to the random parameter and a callback token, the first communication client splices a change notification address, the first encryption signature and the random parameter to obtain a callback address, an information change message is generated according to the callback address and service change information and sent to an event server, and the event server acquires the information change message sent by the first communication client, wherein the information change message comprises the callback address and the service change information.
Under the condition of a fourth callback parameter, if the callback parameter comprises a change notification address, a callback token and a secret key, the first communication client encrypts the service change information through the secret key to obtain encrypted information, obtains a random parameter, generates a first encrypted signature according to the random parameter and the callback token in the callback parameter, generates the change notification address, the first encrypted signature and the random parameter into the callback address, generates an information change message according to the encrypted information and the callback address, and sends the information change message to the event server, and the event server obtains the information change message sent by the first communication client, wherein the information change message comprises the callback address and the encrypted information.
Optionally, the service change information may also be converted according to a requirement, for example, format conversion is performed on the service change information, so as to increase security of transmission of the service change information.
Step S402, extracting the service change information in the information change message.
Specifically, the validity of the information change message is verified according to the callback address in the information change message, and if the information change message is a legal message, the service change information is extracted from the acquired information change message. Specifically, the information change message is analyzed according to the data included in the information change message, so as to obtain the service change information in the information change message. Optionally, the information change message may be obtained based on different composition modes of the callback parameter, and the information change messages generated by different composition modes of the callback parameter are different.
Under the condition of the first information change message, the information change message comprises service change information and a change notification address, and a callback parameter is configured in the event server and comprises the change notification address. And after receiving the information change message, the event server acquires the service change information in the information change message.
In the case of the second information change message, the information change message includes encrypted information and a change notification address, and the event server is configured with a callback parameter, which includes the change notification address and a secret key. And after receiving the information change message, the event server acquires the encrypted information in the information change message, and decrypts the encrypted information through the key in the stored callback parameter to obtain the service change information.
Under the condition of a third information change message, the information change message comprises a callback address and service change information, and a callback parameter is configured in the event server and comprises a change notification address and a callback token. The event server acquires a callback address in an information change message after receiving the information change message, acquires a random parameter in the callback address, generates a second encryption signature according to the random parameter and a callback token in the callback parameter, extracts service change information from the information change message when a first encryption signature is the same as the second encryption signature and indicates that the information change message is sent by a first communication client, sends a synchronous change failure message to the first communication client when the first encryption signature is different from the second encryption signature, and ends the synchronous change process of the information. The sender of the information change message can be authenticated through the encrypted signature, and the generation algorithm of the first encrypted signature is the same as that of the second encrypted signature. The callback token is negotiated between the first communication client and the event server and used for indicating identity information of the first communication client, the first communication client generates a first encryption signature according to the callback token and other random parameters, the event server can generate a second encryption signature based on the callback token and the random parameters sent by the first communication client, and the callback token used when the first encryption signature is generated is the callback token configured by the event server only when the first encryption signature is the same as the second encryption signature. When other communication clients or malicious software and the like acquire the change notification address of the event server and send an information change message to the event server, because the other communication clients or malicious software and the like do not know the callback parameter configured by the event server, the first encryption signature in the information change message is different from the second encryption signature generated in the event server, so that the event server can refuse to receive the information change message, and the safety of information change is improved.
Under the fourth information change message condition, the information change message comprises encryption information and a callback address, and a callback parameter is configured in the event server and comprises a change notification address, a callback token and a secret key. The event server acquires a callback address in the information change message after receiving the information change message, acquires a random parameter in the callback address, generates a second encryption signature according to the random parameter and a callback token in the callback parameter, and decrypts the encryption information through a key in the callback parameter when the first encryption signature is the same as the second encryption signature to acquire service change information.
Optionally, when the service change information has other conversions, the event server restores the received information change message according to the conversion condition to obtain the service change information, and when the format conversion of the service change information exists, restores the converted service change information according to the converted format to obtain the initial service change information.
Step S403, sending the service change information to the second communication client, so that the second communication client updates the first service data recorded by the second communication client based on the service change information.
Specifically, after extracting the service change information in the information change message, the event server sends the service change information to the second communication client indicated by the configured communication address, so that the second communication client updates the first service data recorded in the second communication client based on the service change information, and the event server is configured with the communication address of the second communication client. The event server is configured with at least one second communication client, specifically, the event server is configured with a contact way of the at least one second communication client, so that the event server can establish communication connection with the at least one second communication client through the configured contact way of the at least one second communication client, and send data to the at least one second communication client. The mobile office platform of the organization is composed of the first communication client and at least one second communication client, namely, the office tool used by the organization comprises the first communication client and at least one second communication client, so that when business information is changed in the first communication client, business change information generated in the first communication client is sent to the at least one second communication client through the event server, the at least one second communication client updates own business data, the at least one second communication client is a communication client except the first communication client in all the communication clients used in the corresponding organization, and the communication clients used in the organization can be updated synchronously, so that the business data of the communication clients are consistent.
In the embodiment of the present application, the information synchronization changing process is described with reference to fig. 2 and fig. 4, specifically, the steps performed by the first communication client in the information synchronization changing process are described with reference to fig. 2, and the steps performed by the event server in the information synchronization changing process are described with reference to fig. 4. The steps of fig. 2 and fig. 4 constitute a complete information synchronous change process, which comprises calling a change notification address and a callback token from a callback parameter in response to a submission operation for the service change information when a first communication client acquires the service change information, generating a callback address based on the callback token and the change notification address, generating an information change message according to the callback address and the service change information, sending the information change message to an event server pointed by the change notification address based on the change notification address, verifying the validity of the information change message by the callback address in the information change message after the event server acquires the information change message sent by the first communication client, extracting the service change information in the information change message when the information change message is valid, and sending the service change information to a second communication client indicated by a communication address configured by the event server And the second communication client updates the first service data recorded in the second communication client based on the service change information, thereby realizing the unified update management of the information. Specifically, when the first communication client is used as the central communication client, when the service data in the first communication client changes, the changed service data is called back to the event server, the event server sends the changed service data to the second communication client, and the second communication client can update the service data based on the received changed service data, so that the data consistency can be ensured in each communication client in the same information network, thereby improving the intelligence and efficiency of information synchronous change, and further improving the efficiency of information unified update management.
Further, referring to fig. 5, fig. 5 is a schematic view of an interaction flow of information synchronization change provided in an embodiment of the present application. As shown in fig. 5, the method comprises the following steps:
and step S501, setting callback parameters.
Specifically, the first communication client sets a callback parameter, where the callback parameter at least includes a change notification address, and may also include a callback Token and/or a key. Specifically, callback parameters are obtained in a configuration interface, and the callback parameters comprise a change notification address and a callback Token and/or a key; responding the configuration operation aiming at the callback parameter, storing the callback parameter, and sending the callback parameter to an event server pointed by a change notification address through the change notification address so that the event server configures the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server. Wherein Token is the callback Token.
The change notification address URL is an access protocol and an address of the event server for receiving the information change message pushed by the first communication client, supports an http protocol or an https protocol and the like, namely the change notification address URL is an address of the event server for receiving the service change information fed back by the first communication client; calling back a Token for identity authentication, and carrying out unique identification on a communication client needing identity authentication so as to represent identity information of the communication client; the key is used for encrypting and decrypting data, is a symmetric password and is obtained through a symmetric encryption algorithm, wherein the symmetric encryption algorithm is an encryption algorithm using the same key for encryption and decryption, and a key is agreed before data transmission is carried out between the first communication client and the event server, so that the event server can decrypt the encrypted data based on the key when receiving the data which is sent by the first communication client and encrypted through the key. The callback Token or the key may be randomly generated, or may be a random Token or a random key that is input by an administrator. The key may be obtained by using an Encryption Algorithm such as a Data Encryption Standard (DES), Triple DES (3 DES), International Data Encryption Algorithm (IDEA), Digital Signature Algorithm (DSA), Advanced Encryption Standard (AES), and the like. If an encrypted AES key (EncodingAESKey) is generated in the first communication client, the EncodingAESKey is generated in an encoding mode Base64 of the AES encryption algorithm for transmitting an 8-bit bytecode, the first communication client sends the EncodingAESKey as a key in the callback parameter to the event server, and the event server records a corresponding decrypted AES key (DecodingAESKey) based on the EncodingAESKey, and the DecodingAESKey is the same as the EncodingAESKey.
Specifically, refer to fig. 6a to 6c, which are schematic diagrams illustrating generation of a callback parameter according to an embodiment of the present application. As shown in fig. 6a, fig. 6a is a schematic diagram of setting an information synchronous change interface according to an embodiment of the present application, where a page 601 of the setting of the information synchronous change interface includes a page description, a synchronous mode setting, a permission setting, and an event server setting interface. The page description is used to indicate that the information synchronization change Interface setting page 601 is a setting for service data synchronization change, and specifically, service data may be synchronized through an Application Programming Interface (API), where the service data synchronization change mode is determined based on a parameter set in the synchronization mode, and by setting the API Interface mode in the synchronization mode setting, a function of the first communication client for service change information synchronization change is started, that is, a function of the first communication client for feeding back the service change information to the event server is started, and by setting an authority of the API Interface, an authority of accessing the service data recorded in the first communication client through the API Interface is opened. The first configuration interface 602 in the callback parameter setting diagram shown in fig. 6b is entered in response to a click operation on the event server setting interface, where the first configuration interface 602 includes a change notification address URL, a callback Token and a key, where the change notification address URL is used to indicate an address of the event server for receiving an information change packet, and supports an http or https protocol, the callback Token is used to perform identity verification, and may be randomly generated, or obtain parameters input in the first configuration interface 602, and the key is used to encrypt and decrypt data, and may be randomly generated, or obtain parameters input at the key in the first configuration interface 602. After the first communication client acquires the callback parameter through the first configuration interface 602, the first communication client responds to the configuration operation of the callback parameter, namely, monitors the click operation of the save button in the first configuration interface 602, stores the callback parameter in the first configuration interface 602, and sends the callback parameter to the event server through the change notification address URL configured in the first configuration interface 602, so that the event server configures the callback parameter, and the first communication client and the event server can establish communication connection through the callback parameter.
For example, assume that the administrator inputs a change notification address in the first configuration interface 602, clicks the random get button of the callback Token and the random get button of the key, generates a random callback Token and a random key, generates various parameters in the second configuration interface 603 as shown in another callback parameter setting diagram in fig. 6c, if the address of the event server for receiving the information change message sent by the first communication client is "http:// api.3depth.com", the administrator of the first communication client inputs "http:// api.3depth.com" at the change notification address URL for indicating the address of the event server, and randomly generates the callback Token "eyjzdwwi:/' RydWV 9" and the key "dshfefjewfafdfaftfaftfaftfaftfaftfaftfafs", when the first communication client monitors that the second configuration interface 603 stores the callback Token, the configuration interface 603 responds to the click of the callback parameter, the callback parameter is stored in the database 604 of the first communication client, and is transmitted to the event server 605 via the change notification address, so that the event server 605 transmits the received callback parameter "URL: http:// api.3dept.com; token: eyjzdwi × RydWV 9; EncodingAESKey: the dshfohafjoewufaffafsdptt "is stored in the database of the event server 605.
Step S502, monitoring the change notification address.
Specifically, the event server monitors the change notification address to obtain the accessed condition of the change notification address in real time. Specifically, the event server monitors the change notification address in real time, so that the event server performs an operation on the received data as soon as the data is received in the change notification address. For example, when the first communication client sends an information change message to the event server, and the event server receives the information change message through the change notification address, the event server executes corresponding operation, and sends the service change information in the information change message to the second communication client, so that the second communication client updates its service data based on the received service change information, thereby ensuring the synchronization of information change, and enabling the second communication client to update its service data in time when the service data in the first communication client changes.
In step S503, the service change data is input.
Specifically, the manager inputs the business change data, which may be data generated by member changes of the organization or office information changes, in the first communication client. The manager may input the service change data through a front-end page of the first communication client, or may input the service change data by calling a service change API. After the first communication client acquires the service change data input by the front-end page or the service change data input by the service change API, the first communication client sorts the service change data to obtain service change information. Optionally, the first communication client may generate service change information based on the obtained service change data, where the service change information is expressed in a database operation language. Optionally, the personal user may also change the personal information of the personal user through the first communication client, where the changing right of the personal user is different from that of the associated person.
For example, in the case of the first input of service change data, refer to fig. 7, which is a schematic diagram of inputting service change data based on a front-end page according to an embodiment of the present application, as shown in fig. 7, a user may set a member management page shown in fig. 3, and if information of a user a, a user C, and a user D in the XX company is changed, the three users are selected to obtain a member management page 701 shown in fig. 7. If the user a, the user C and the user D leave the company XX, the user a, the user C and the user D can directly click a delete button, and the first communication client acquires service change data fed back by the member management page when monitoring the click operation of the delete button, and generates service change information "delete the user a, the user C and the user D" according to the service change data, for example, the service change information can be expressed by "delete user a, user b and user C". If the personal information of the user a, the user C and the user D in the company XX is changed, the change operation can be performed one by one in the member management interface 701, or the unified change operation can be performed by entering the service change page 702, the manager can input the change data of the changed user in the service change page 702, if the role of the user a is changed, the "assistant president" of the changed role of the user a can be directly input in the role column of the user a in the service change page 702, and if the mobile phone of the user C is changed, the "177" 2465 "of the changed mobile phone of the user C can be directly input in the mobile phone column of the user C in the service change page 702, and the service change information" change the role of the user a to the assistant president, change the mobile phone of the user C to the 177 "2465" and change the mobile phone of the user D to the two "can be generated according to the service change data input in the service change page, for example, the name of the secondary part may be "user a" through "set role; update set mobile phone 177 user name 2465 user C; and update set department two-place name user D ".
For example, in the case of inputting service change data in the second kind, see fig. 8, which is a scene schematic diagram of personal user change data provided in the embodiment of the present application, as shown in fig. 8, a user enters a personal information display page 802 through a home page 801 of a first communication client, when the first communication client monitors a setting operation in the personal information display page 802, a personal information editing page 803 is displayed for the user, and the user can input personal information changed by the user through the personal information editing page 803, where the personal user can only edit part of information related to the user, and if the information is related to a company, the personal user has no editing right, such as a department or a job to which the user belongs in the company. The background 804 of the first communication client obtains the data in the personal information editing page 803 to obtain the service change information.
Step S504, the business data is updated according to the business change data.
Specifically, the first communication client updates the service data in the first communication client according to the acquired service change data. Optionally, if the service change information generated according to the service change data in step S503 is expressed in the database operation language, the service data recorded in the database of the first communication client is directly changed according to the service change information, where the service data includes the service change information and data associated with the service change information.
For example, based on the example shown in step S503, if the service change information is "delete user a, user C, and user D", deleting the personal information of user a, user C, and user D and the associated data of the three users in the database of the first communication client, which includes removing the three users from the group where the three users are located, and closing the respective permissions of the three users at company XX, etc. If the service change information is that "the role of the user a is changed to the secondary division, the mobile phone of the user C is changed to 177 × 2465, and the division of the user D is changed to two", the authority related to the secondary division is opened to the user a, the personal information of the user a is changed, the places where the user C is associated with the mobile phone are changed to 177 × 2465, and the information related to the division of the user D is changed to the information related to the two parts.
Step S505 generates an information change message.
Specifically, the first communication client generates an information change message based on the callback parameter and the service change information. The process of generating the information change packet is specifically described with reference to step S401 in fig. 4, and the callback parameters respectively include a change notification address, a callback parameter includes a change notification address and a key, the callback parameter includes a change notification address and a Token, the callback parameter includes a change notification address, a Token and a key, and other situations, which are not described herein again. Optionally, the service change information may be encapsulated into an Extensible Markup Language (XML) format.
For example, under the first callback parameter, the callback parameter includes a change notification address http:// api.3depth.com, and the first communication client generates an information change message according to the change notification address and the service change information.
Under the second callback parameter condition, the callback parameter comprises a change notification address 'http:// api.3dept.com' and a secret key 'dshfahfjoewufaffafsdptt', the first communication client encrypts the service change information based on the secret key to obtain encrypted information, and generates an information change message according to the encrypted information and the change notification address. If the service change information is "change user a role is minor leader, change user C mobile phone is 177 × 2465, change user D department is two", encrypt the service change information by key "dshfahfjoufwufaffaffdptt", generate encrypted information "U2 fsdgvgx 19 llnt 6CVS/+ zlnykZNe6EpS2nVJzaPw86fyzultqe q/pwtcwuuvrtod 6BkNb5/BbkJXXu8 oamphenk hnf 37R 7BV/4 wstdmkkeb 7P5 wddfuuh 9j1 mbfuwzbe 3n7 wxwvvvlzal 0t1 pi 0", and generate encrypted information and notify the encrypted information of the change information.
In the case of the third type of callback parameter, the callback parameter includes a change notification address and a callback Token, where the change notification address is "http:// api.3dept.com", and the callback Token is "eyjzdwi. The first communication client acquires the random parameter, generates a first encryption signature based on Token and the random parameter, splices the change notification address, the first encryption signature and the random parameter to obtain a callback address, and generates an information change message according to the callback address and the service change information. The random parameter may include a timestamp, a random number, a first communication client identifier, and/or a signature parameter, etc. For example, if the random parameter includes the timestamp 13500001234 and the random number 123412323, assuming that the first encryption signature "asdfqwexzcvaqfadfasdfss" is generated from Token and the random parameter, the change notification address, the first encryption signature, and the random parameter are concatenated to obtain the callback address "http:// api.3dept.com/? msg _ signature is ASDFQWEXZCVAQFASDFASDFSS & timing 13500001234& notification 123412323 ", and an information change message is generated according to the callback address and the service change information.
And under the condition of the fourth callback parameter, the callback parameter comprises a change notification address, a callback token and a secret key, the first communication client encrypts the service change information through the secret key to obtain encrypted information, acquires a random parameter, generates a first encrypted signature according to the random parameter and the callback token in the callback parameter, generates the callback address by using the change notification address, the first encrypted signature and the random parameter, and generates an information change message according to the encrypted information and the callback address. For example, based on the second and third examples of the callback parameters, based on the encryption information "U2 FsdGVkX? The msg _ signature is asdfqwexzcvaqfadfasdfss & timekeeping is 13500001234& nonce is 123412323 "to generate an information change message.
Step S506, the message change message is sent.
Specifically, the first communication client sends the information change message to the event server through the change notification address. Optionally, the first communication client may send the information change packet post to a change notification address of the event server. Wherein, the post is generally used for updating the resource information, generally used for sending an update request to the destination server, and attached with a requesting entity, sending the update request to the destination server by adding the specified message into the message queue of the window. As shown in fig. 8, the first communication client background 804 sends an information change message to the event server 805.
Step S507, extracting the service change information.
Specifically, the event server extracts the service change information in the information change message based on the specific generation mode of the information change message. The process is described in detail with reference to step S402 in fig. 4, and is not described herein again.
In the fourth callback parameter case in step S505, the event server stores the callback parameters, which include "URL: http:// api.3dept.com; token: eyjzdwi × RydWV 9; EncodingAESKey: the dshfohafjoewufhidfaffdttt "message includes the callback address" http:// api.3dept.com/? msg _ signature ═ asdfqwexzcvaqfadfasdfss & timekeeping ═ 13500001234& nonce ═ 123412323 "and encryption information" U2 fsdgvgkx 19lIiNt6CVS/+ zlnykZNe6EpS2nVJzaPw86 fyzuleq/pwtcwuuvud 6BkNb5/BbkJXXu8 oapheimhnf 37pDQc65R7BV/4 wstdmddhmkeb 7P5wzaDFuh9j1 mobfuwwzw 1HSje3n7 lwxwzal 0t 1I 5w 8w0 ═. The event server acquires a callback address in the information change message, acquires a first encryption signature ' ASDFQEXZCVAQFASDFASDFSS ' and random parameters from the callback address, wherein the random parameters comprise a ' timestamp 13500001234 and a random number 123412323 ', and generates a second encryption signature according to the random parameters and a callback token ' eyJzdWIi ' RydWV9 ' by a generation algorithm of the first encryption signature. Assuming that the second encrypted signature is asdfqwexzcvaqfadfasdfss, comparing the second encrypted signature with the first encrypted signature, determining that the second encrypted signature is the same as the first encrypted signature, obtaining the encrypted information in the information change message, decrypting the encrypted information according to the key 'dshfahfjoewufaffaffdptt', and obtaining service change information 'change the role of the user a to be the secondary leader, change the role of the user C to be 177 × 2465, and change the role of the user D to be two'.
Step S508, the service change information is sent.
Specifically, the event server sends the acquired service change information to the second communication client. The event server is configured with a communication address of at least one second communication client, where the communication address is used to point to a corresponding second communication client, and may be an address of a background data processing interface of the at least one second communication client or an address of a database access interface of the second communication client, and the event server sends the service change information to the second communication client through the access interface. Optionally, the event server sends a data format for the service change information to the second communication client in advance, packages the service change information into packaged data with the data format, and sends the packaged data to the second communication client, for example, the data format is "object, name, post, belonging, mobile phone, mailbox, etc.", if the received service change information is "change user a role to minor leader", packages the service change information based on the data format to obtain packaged data "member, user a, minor leader, 0, 0, 0", if the received service change information is "change first department to external processing department", packages the service change information based on the data format to obtain packaged data "department, first department, external processing, 0, 0, 0", the event server sends the packaged data to the second communication client, and if the data format has a field without corresponding data, adding a default value to the field. The service change information may also be encapsulated in other data formats, which is not limited herein. Optionally, if the service change information is described in the database operation language, the service change information is directly sent to the second communication client. As shown in fig. 8, the event server 805 sends service change information to the second communication client 806.
Step S509, update the service data of the second communication client.
Specifically, the second communication client receives the service change information sent by the event server, and updates the first service data of the second communication client based on the service change information. Optionally, after receiving the service change information sent by the event server, the second communication client determines the reliability of the service change information based on the sender information of the service change information, for example, it is determined that the event server is a management server of an organization to which the second communication client belongs based on a physical Access Control (MAC) Address or an Internet Protocol Address (IP Address) of the event server, and if the event server is a management server of the organization to which the second communication client belongs, it is determined that the event server is reliable. Optionally, if the service change information is sent to the second communication client as encapsulated data, the second communication client receives the encapsulated data, and obtains each parameter included in the encapsulated data based on the obtained data format sent by the event server, so as to change the service data recorded in the second communication client through each parameter. Optionally, if the service change information is described in a database operation language, the second communication client determines, according to the service change information, a data table associated with the service change information in the database of the second communication client, so as to generate an operation language for the database of the second communication client according to the determined associated data table and the service change information, and update the service data of the second communication client according to the operation language for the database of the second communication client. As shown in fig. 8, the second communication client 806 updates the service data 807 of the second communication client based on the service change information.
Optionally, in step S507, if the second communication client provides an access interface of the database to the event server and opens an access right of the event server to the database of the second communication client, after the event server extracts the service change information, the second communication client may also perform service data update on the database of the second communication client according to the service change information. Specifically, the event server acquires a data table associated with the service change information from the database of the second communication client according to the extracted service change information, generates a database operation statement for the database of the second communication client based on the associated data table and the service change information, and updates the service data in the database of the second communication client according to the database operation statement.
The processes from step S510a to step S511 are optional steps in the information synchronization change process. Specifically, the event server counts time after sending the service change information to the second communication client, and acquires the second service data of the first communication client and the updated first service data in the second communication client if the accumulated time reaches the target time length.
Step S510a, the second service data is sent.
Specifically, after receiving a service data acquisition request sent by an event server, a first communication client sends second service data to the event server, where the second service data is service data recorded in the first communication client.
Step S510b, the first service data after being changed and updated is sent.
Specifically, after receiving a service data acquisition request sent by the event server, the second communication client sends updated first service data to the event server, where the updated first service data is service data recorded at the current time in the second communication client.
Step S511 determines that the second service data is the same as the updated first service data.
Specifically, the event server compares the updated first service data with the updated second service data, and if the second service data is different from the updated first service data, sends an information change exception message to the second communication client, so that the second communication client updates the service data recorded in the second communication client based on the second service data in the information change exception message; and if the second service data is the same as the updated first service data, sending a normal message of information synchronous change to the second communication client. Optionally, if the service data ranges recorded in the first communication client and the second communication client are different, when the event server compares the updated first service data with the updated second service data, only the data with the same parameter of the second service data and the updated first service data are compared, and when the second service data is the same as the data with the same parameter of the updated first service data, it is determined that the second service data and the updated first service data are the same, for example, the first communication client is used for managing member information of the whole enterprise, the second service data includes member information of the whole enterprise, one second communication client is used for managing member information of a first department, the updated first service data includes member information of the first department, the event server compares the member information of the first department in the second service data with the updated first service data, and if the member information of the first department in the second service data is the same as the updated first service data, sending a normal information synchronous change message to the second communication client, and if the member information of the first department in the second service data is different from the updated first service data, sending an abnormal information change message to the second communication client, wherein the abnormal information change message comprises the member information of the first department in the second service data, so that the second communication client updates the service data recorded in the second communication client based on the second service data in the abnormal information change message.
Further, referring to fig. 9, fig. 9 is a data transfer diagram of information synchronization change according to an embodiment of the present application, and as shown in fig. 9, a data flow direction in the information synchronization change process is schematically illustrated by taking the fourth callback parameter case as an example, where the callback parameter at this time includes a change notification address, a callback token, and a key. Specifically, when the service data in the first communication client 901 changes, the first communication client 901 obtains the changed service data to obtain service change information, obtains a key from the callback parameter 902, encrypts the service change information by using the key to obtain encrypted information, obtains the callback token in the callback parameter 902, obtains a random parameter, generates a first encryption signature according to the callback token and the random parameter, concatenates the change notification address in the callback parameter 902, the generated first encryption signature and the obtained random parameter to obtain a callback address, and generates an information change message according to the callback address and the encrypted information. Wherein, the encryption information and the generation process of the callback address can be exchanged. After generating an information change message, the first communication client 901 sends the information change message to the event server 903, and the event server 903 is configured with a callback parameter 904, where before executing an information synchronization change process, when the first communication client 901 is configured with the callback parameter 902, the callback parameter 902 is sent to the event server 903 through a change notification address, and the event server 903 is configured with the callback parameter 904.
After the event server 903 receives the information change message sent by the first communication client 901, the event server 903 obtains a callback address in the information change message, and obtains a first encryption signature and a random parameter contained in the callback address according to the callback address, the event server 903 obtains a callback token in the callback parameter 904, generates a second encryption signature according to the random parameter and the callback token, and executes a comparison process 905 of the first encryption signature and the second encryption signature, wherein the generation algorithm of the second encryption signature is the same as that of the first encryption signature. The event server 903 determines whether the second encrypted signature is consistent with the first encrypted signature based on a comparison process 905 between the first encrypted signature and the second encrypted signature, if the second encrypted signature is different from the first encrypted signature, it indicates that the sender of the information change message is not a negotiated sender, and the information change message may have a security problem, sends a synchronization change failure message to the first communication client 901, if the second encrypted signature is the same as the first encrypted signature, acquires encrypted information in the information change message, decrypts the encrypted information by using a key in the callback parameter 904 to obtain service change information, the event server 903 sends the obtained service change information to the second communication client 906, so that the second communication client 906 updates service data recorded in the second communication client 906 based on the received service change information, thereby realizing the synchronous information update between the first communication client 901 and the second communication client 906.
When the callback parameter only includes a change notification address, the first communication client 901 generates an information change message directly based on the change notification address and the service change information, and sends the information change message to the event server 903, and the event server 903 sends the service change information in the information change message to the second communication client 906; when the callback parameter includes a change notification address and a callback token, executing a process of a branch where the change notification address and the callback token are located as shown in fig. 9, after the first communication client 901 obtains the callback address, generating an information change message according to the callback address and service change information, sending the information change message to the event server 903, comparing whether a second encryption signature is consistent with a first encryption signature or not by the event server 903 on the basis of the callback address in the callback parameter 904 and the callback address in the information change message, if the second encryption signature is consistent with the first encryption signature, obtaining the service change information in the information change message, and sending the service change information to the second communication client 906; when the callback parameter includes a change notification address and a key, a process of a branch including the change notification address and the key as shown in fig. 9 is executed, the first communication client 901 encrypts the service change information by the key to obtain encrypted information, generates an information change message according to the encrypted information and the change notification address, and sends the information change message to the event server 903, the event server 903 obtains the encrypted information in the information change message after receiving the information change message, decrypts the encrypted information by the key in the callback parameter 904 to obtain the service change information, and the event server 903 sends the service change information to the second communication client.
According to the embodiment of the application, when the first communication client side obtains the service change information, the change notification address is called from the callback parameter in response to the submission operation aiming at the service change information, the information change message is generated according to the callback parameter and the service change information, the information change message is sent to the event server pointed by the change notification address based on the change notification address, after the event server obtains the information change message sent by the first communication client side, the service change information in the information change message is extracted, the service change information is sent to the second communication client side, so that the second communication client side updates the first service data recorded in the second communication client side based on the service change information, and therefore unified updating management of the information is achieved. Specifically, when the first communication client serves as a central communication client, when the service data in the first communication client changes, the changed service data is called back to the event server, the event server sends the changed service data to the second communication client, and the second communication client can update the service data based on the received changed service data, so that the data consistency can be ensured in each communication client in the same information network, the intelligence and the efficiency of information synchronous change are improved, and the unified update management efficiency of information is further improved. Meanwhile, transmission data between each communication client and the event server is encrypted or signed, so that the safety of service change information transmission is improved.
Referring to fig. 10, fig. 10 is a schematic view of an information synchronization changing apparatus provided in an embodiment of the present application, and as shown in fig. 10, the information synchronization changing apparatus 100 may be used in a computer in the embodiment corresponding to fig. 2, specifically, the apparatus may include: a first acquiring module 11a, a generating module 12a and a sending module 13 a.
A first obtaining module 11a, configured to obtain service change information by a first communication client;
the generating module 12a is configured to respond to a submission operation for the service change information, call a change notification address and a callback token from a callback parameter, generate a callback address based on the callback token and the change notification address, and generate an information change message according to the callback address and the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with an event server; the event server is a server pointed by the change notification address, and is configured with a communication address of a second communication client;
a sending module 13a, configured to send the information change packet to the event server, so that after verifying the validity of the information change packet according to the callback token, the event server sends the service change information in the information change packet to the second communication client indicated by the communication address; the service change information is used for updating service data in the second communication client;
the first communication client, the event server and the second communication client belong to different service platforms respectively.
Wherein the apparatus 100 further comprises:
a second obtaining module 14a, configured to obtain the callback parameter in a configuration interface, where the callback parameter includes the change notification address and the callback token;
a response module 15a, configured to respond to a configuration operation for the callback parameter, store the callback parameter, and send the callback parameter to the event server pointed by the change notification address through the change notification address, so that the event server configures the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server.
Wherein the callback parameter further comprises a key;
in the aspect of generating an information change packet according to the callback address and the service change information, the generating module 12a includes:
an encrypting unit 121a, configured to encrypt the service change information by using the key to obtain encrypted information; the key is used for indicating the event server to decrypt the encrypted information when receiving the information change message;
a first generating unit 122a, configured to generate the information change packet according to the callback address and the encryption information.
In the aspect of generating the callback address based on the callback token and the change notification address, the generating module 12a further includes:
a second generating unit 123a, configured to obtain a random parameter, and generate a first encryption signature based on the callback token and the random parameter;
a splicing unit 124a, configured to splice the change notification address, the first encryption signature, and the random parameter to obtain the callback address; and the first encryption signature and the random parameter are used for verifying the validity of the information change message when the event server receives the information change message.
Referring to fig. 11, fig. 11 is a schematic view of another information synchronization changing apparatus provided in the embodiment of the present application, and as shown in fig. 11, the information synchronization changing apparatus 110 may be used in the computer in the embodiment corresponding to fig. 4, specifically, the apparatus may include: a first obtaining module 11b, an extracting module 12b and a first sending module 13 b.
A first obtaining module 11b, configured to obtain, by an event server, an information change packet sent by a first communication client through a change notification address, where the information change packet is generated by the first communication client according to a callback address and service change information, the callback address is generated by the first communication client based on a callback token in a callback parameter and the change notification address, and the change notification address is an address called from the callback parameter by the first communication client when responding to a commit operation for the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with the event server; the event server refers to a server to which the change notification address points;
the extracting module 12b is configured to verify the validity of the information change packet according to the callback address in the information change packet, and if the information change packet is a valid packet, extract the service change information in the information change packet;
a first sending module 13b, configured to send the service change information to a second communication client indicated by a configured communication address, so that the second communication client updates first service data recorded in the second communication client based on the service change information, and the event server is configured with the communication address of the second communication client;
the first communication client, the event server and the second communication client belong to different service platforms respectively.
Wherein the apparatus 110 further comprises:
a second obtaining module 14b, configured to obtain a callback parameter that is sent by the first communication client and carries the change notification address and the callback token, and configure the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server.
Wherein the callback parameter further comprises a key; the information change message comprises the callback address and encrypted information, and the encrypted information is obtained by encrypting the service change information through the secret key by the first communication client;
in the aspect of extracting the service change information in the information change message, the extracting module 12b includes:
a first obtaining unit 121b configured to obtain the encrypted information in the information change message;
a decryption unit 122b, configured to decrypt the encrypted information through the key to obtain the service change information.
The message of information change comprises a callback address and the information of service change; the callback address comprises the change notification address, the random parameter and a first encryption signature; the first encrypted signature is generated by the first communication client based on the callback token and the random parameter;
in the aspect of verifying the validity of the information change packet according to the callback address in the information change packet, the extracting module 12b further includes:
a second obtaining unit 123b, configured to obtain the callback address in the information change message;
a generating unit 124b, configured to generate a second encryption signature according to the callback token and the random parameter in the callback address;
a comparing unit 125b for comparing the second cryptographic signature with the first cryptographic signature;
the comparing unit 125b is further configured to, if the second cryptographic signature is the same as the first cryptographic signature, indicate that the information change message is a legitimate message, and execute the step of extracting the service change information in the information change message through the extracting module 12 b;
a first sending unit 126b, configured to, if the second encrypted signature is different from the first encrypted signature, indicate that the information change packet is an illegal packet, and send a synchronization change failure message to the first communication client.
Wherein the apparatus 110 further comprises:
a third obtaining module 15b, configured to obtain second service data of the first communication client and updated first service data in the second communication client if the accumulated time reaches the target time length;
a second sending module 16b, configured to send an information change exception message to the second communication client if the second service data is different from the updated first service data, so that the second communication client updates the updated first service data based on the second service data in the information change exception message;
the second sending module 16b is further configured to send a message that the information is changed normally and synchronously to the second communication client if the second service data is the same as the updated first service data.
Wherein the apparatus 110 further comprises:
a third sending module 17b, configured to send a data format for the service change information to the second communication client;
the first sending module 13b includes:
an encapsulating unit 131b, configured to encapsulate the service change information into encapsulated data with the data format;
a second sending unit 132b, configured to send the encapsulated data to the second communication client indicated by the configured communication address, so that the second communication client obtains each parameter included in the encapsulated data based on the data format, and changes the first service data recorded in the second communication client according to each parameter.
In the embodiment of the present application, an information synchronization changing apparatus is described with reference to fig. 10 and 11, where fig. 10 is an information synchronization changing apparatus corresponding to a first communication client, and fig. 11 is an information synchronization changing apparatus corresponding to an event server. Fig. 10 and 11 constitute a complete information synchronous change apparatus, which calls a change notification address from a callback parameter in response to a commit operation for service change information when a first communication client acquires the service change information, generates an information change message according to the change notification address and the service change information, sends the information change message to an event server to which the change notification address points based on the change notification address, and after the event server acquires the information change message sent by the first communication client, extracts the service change information in the information change message, and sends the service change information to a second communication client, so that the second communication client updates first service data recorded in the second communication client based on the service change information, thereby implementing unified update management of information. Specifically, when the first communication client is used as the central communication client, when the service data in the first communication client changes, the changed service data is called back to the event server, the event server sends the changed service data to the second communication client, and the second communication client can update the service data based on the received changed service data, so that the data consistency can be ensured in each communication client in the same information network, thereby improving the intelligence and efficiency of information synchronous change, and further improving the efficiency of information unified update management.
Referring to fig. 12, fig. 12 is a schematic structural diagram of a computer according to an embodiment of the present disclosure. As shown in fig. 12, the computer in the embodiment of the present application may include: one or more processors 1201, memory 1202, and input-output interface 1203. The processor 1201, the memory 1202, and the input/output interface 1203 are connected by a bus 1204. The memory 1202 is used for storing a computer program, which includes program instructions, and the input/output interface 1203 is used for inputting and outputting data, including data interaction between each communication client and the event server, and data interaction between the user and each communication client; the processor 1201 is configured to execute the program instructions stored in the memory 1202 to perform the following operations:
the first communication client side obtains service change information;
responding to the submission operation aiming at the service change information, calling a change notification address and a callback token from a callback parameter, generating a callback address based on the callback token and the change notification address, and generating an information change message according to the callback address and the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with an event server; the event server is a server pointed by the change notification address, and is configured with a communication address of a second communication client;
sending the information change message to the event server, so that the event server sends the service change information in the information change message to the second communication client indicated by the communication address after verifying the validity of the information change message according to the callback token; the service change information is used for updating service data in the second communication client; the first communication client, the event server and the second communication client belong to different service platforms respectively.
Wherein the processor 1201 is further configured to:
obtaining the callback parameters in a configuration interface, wherein the callback parameters comprise the change notification address and the callback token;
responding to the configuration operation aiming at the callback parameter, storing the callback parameter, and sending the callback parameter to the event server pointed by the change notification address through the change notification address so that the event server configures the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server.
The callback parameter further comprises a key;
in the aspect of generating an information change packet according to the callback address and the service change information, the processor 1201 is further configured to:
encrypting the service change information through the key to obtain encrypted information, and generating the information change message according to the callback address and the encrypted information; and the key is used for indicating the event server to decrypt the encrypted information when receiving the information change message.
Wherein, in said generating a callback address based on said callback token and a change notification address, said processor 1201 is further configured to:
acquiring a random parameter, and generating a first encryption signature based on the callback token and the random parameter;
splicing the change notification address, the first encryption signature and the random parameter to obtain the callback address; and the first encryption signature and the random parameter are used for verifying the validity of the information change message when the event server receives the information change message.
And the following operations:
the method comprises the steps that an event server obtains an information change message sent by a first communication client through a change notification address, wherein the information change message is generated by the first communication client according to a callback address and service change information, the callback address is generated by the first communication client based on a callback token in a callback parameter and the change notification address, and the change notification address is an address called from the callback parameter when the first communication client responds to submission operation aiming at the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with the event server; the event server is a server to which the change notification address points;
verifying the legality of the information change message according to the callback address in the information change message, and if the information change message is a legal message, extracting the service change information in the information change message;
sending the service change information to a second communication client indicated by a configured communication address, so that the second communication client updates first service data recorded in the second communication client based on the service change information, and the event server is configured with the communication address of the second communication client; the first communication client, the event server and the second communication client belong to different service platforms respectively.
Wherein the processor 1201 is further configured to:
obtaining a callback parameter which is sent by the first communication client and carries the change notification address and the callback token, and configuring the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server.
The callback parameter further comprises a key; the information change message comprises the callback address and encrypted information, and the encrypted information is obtained by encrypting the service change information through the secret key by the first communication client;
in the aspect of extracting the service change information in the information change message, the processor 1201 is further configured to:
acquiring the encrypted information in the information change message;
and decrypting the encrypted information through the key to obtain the service change information.
The information change message comprises a callback address and the service change information; the callback address comprises the change notification address, the random parameter and a first encryption signature; the first encrypted signature is generated by the first communication client based on the callback token and the random parameter;
in the aspect of verifying the validity of the information change packet according to the callback address in the information change packet, the processor 1201 is further configured to:
acquiring the callback address in the information change message, and generating a second encryption signature according to the callback token and the random parameter in the callback address;
if the second encrypted signature is the same as the first encrypted signature, the information change message is represented as a legal message, and the step of extracting the service change information in the information change message is executed;
and if the second encrypted signature is different from the first encrypted signature, indicating that the information change message is an illegal message, and sending a synchronous change failure message to the first communication client.
The processor 1201 is further configured to:
if the accumulated time reaches the target time length, acquiring second service data of the first communication client and updated first service data in the second communication client;
if the second service data is different from the updated first service data, sending an information change exception message to the second communication client, so that the second communication client updates the updated first service data based on the second service data in the information change exception message;
and if the second service data is the same as the updated first service data, sending a message synchronous change normal message to the second communication client.
The processor 1201 is further configured to:
sending a data format aiming at the service change information to the second communication client;
the sending the service change information to the second communication client indicated by the configured communication address includes:
and packaging the service change information into packaged data with the data format, and sending the packaged data to the second communication client indicated by the configured communication address, so that the second communication client acquires each parameter included in the packaged data based on the data format, and changes the first service data recorded in the second communication client through each parameter.
In some possible embodiments, the processor 1201 may be a Central Processing Unit (CPU), and the processor may be other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 1202 may include both read-only memory and random access memory, and provides instructions and data to the processor 1201 and the input output interface 1203. A portion of the memory 1202 may also include non-volatile random access memory. For example, memory 1202 may also store device type information.
In a specific implementation, the computer may execute the implementation manners provided in the steps in fig. 2 to fig. 5 through the built-in functional modules, which may specifically refer to the implementation manners provided in the steps in fig. 2 to fig. 5, and details are not described herein again.
The embodiment of the present application provides a computer, including: the processor, the input/output interface and the memory are used for acquiring computer instructions in the memory through the processor, executing the steps of the method shown in the figures 2 to 5 and performing information synchronous change operation. With the computer instructions in the memory, the processor performs the steps of: when the first communication client side obtains the service change information, responding to the submission operation aiming at the service change information, calling a change notification address from the callback parameter, generating an information change message according to the change notification address and the service change information, sending the information change message to an event server pointed by the change notification address based on the change notification address, extracting the service change information in the information change message after the event server obtains the information change message sent by the first communication client side, and sending the service change information to the second communication client side, so that the second communication client side updates the first service data recorded in the second communication client side based on the service change information, thereby realizing the unified update management of the information. Specifically, when the first communication client is used as the central communication client, when the service data in the first communication client changes, the changed service data is called back to the event server, the event server sends the changed service data to the second communication client, and the second communication client can update the service data based on the received changed service data, so that the data consistency can be ensured in each communication client in the same information network, thereby improving the intelligence and efficiency of information synchronous change, and further improving the efficiency of information unified update management.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, where the computer program includes program instructions, and when the program instructions are executed by a processor, the method for synchronously changing information provided in each step in fig. 2 to 5 is implemented, which may specifically refer to the implementation manners provided in each step in fig. 2 to 5, and is not described herein again.
The computer-readable storage medium may be the information synchronous changing apparatus provided in any of the foregoing embodiments or an internal storage unit of the computer, such as a hard disk or a memory of the computer. The computer readable storage medium may also be an external storage device of the computer, such as a plug-in hard disk, a Smart Memory Card (SMC), a Secure Digital (SD) card, a flash memory card (flash card), and the like, provided on the computer. Further, the computer-readable storage medium may also include both an internal storage unit and an external storage device of the computer. The computer-readable storage medium is used for storing the computer program and other programs and data required by the computer. The computer readable storage medium may also be used to temporarily store data that has been output or is to be output.
The terms "first," "second," and the like in the description and in the claims and drawings of the embodiments of the present application are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "comprises" and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, apparatus, product, or apparatus that comprises a list of steps or elements is not limited to the listed steps or modules, but may alternatively include other steps or modules not listed or inherent to such process, method, apparatus, product, or apparatus.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The method and the related apparatus provided by the embodiments of the present application are described with reference to the flowchart and/or the structural diagram of the method provided by the embodiments of the present application, and specifically, each flow and/or block of the flowchart and/or the structural diagram of the method, and the combination of the flows and/or blocks in the flowchart and/or the block diagram, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block or blocks of the block diagram. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block or blocks of the block diagram. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block or blocks.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto, and all equivalent variations and modifications can be made to the present application.

Claims (14)

1. An information synchronous changing method, characterized in that the method comprises:
the first communication client side obtains service change information;
responding to the submission operation aiming at the service change information, updating service data in the first communication client according to the service change information, calling a change notification address and a callback token from a callback parameter, generating a callback address based on the callback token and the change notification address, and generating an information change message according to the callback address and the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with the event server; the event server is a server pointed by the change notification address, and is configured with a communication address of a second communication client;
sending the information change message to the event server, so that the event server sends the service change information in the information change message to the second communication client indicated by the communication address after verifying the validity of the information change message according to the callback token; the service change information is used for updating service data in the second communication client; the first communication client, the event server and the second communication client belong to different service platforms respectively; the first communication client, the event server and the second communication client are associated with the same organization, and the second communication client is an application program except the first communication client in all application programs used by the organization.
2. The method of claim 1, wherein the method further comprises:
obtaining the callback parameters in a configuration interface, wherein the callback parameters comprise the change notification address and the callback token;
responding to the configuration operation aiming at the callback parameter, storing the callback parameter, and sending the callback parameter to the event server pointed by the change notification address through the change notification address so that the event server configures the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server.
3. The method of claim 1, wherein the callback parameter further comprises a key;
the generating an information change message according to the callback address and the service change information includes:
encrypting the service change information through the key to obtain encrypted information, and generating the information change message according to the callback address and the encrypted information; and the key is used for indicating the event server to decrypt the encrypted information when receiving the information change message.
4. The method of claim 1, wherein said generating a callback address based on said callback token and said change notification address comprises:
acquiring a random parameter, and generating a first encryption signature based on the callback token and the random parameter;
splicing the change notification address, the first encryption signature and the random parameter to obtain the callback address; and the first encryption signature and the random parameter are used for verifying the legality of the information change message when the event server receives the information change message.
5. An information synchronous changing method, characterized in that the method comprises:
the method comprises the steps that an event server obtains an information change message sent by a first communication client through a change notification address, wherein the information change message is generated by the first communication client according to a callback address and service change information, the callback address is generated by the first communication client based on a callback token in a callback parameter and the change notification address, and the change notification address is an address called from the callback parameter when the first communication client responds to submission operation aiming at the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with the event server; the event server is a server to which the change notification address points; the service change information is used for updating service data in the first communication client;
verifying the legality of the information change message according to the callback address in the information change message, and if the information change message is a legal message, extracting the service change information in the information change message;
sending the service change information to a second communication client indicated by a configured communication address, so that the second communication client updates first service data recorded in the second communication client based on the service change information, and the event server is configured with the communication address of the second communication client; the first communication client, the event server and the second communication client belong to different service platforms respectively; the first communication client, the event server and the second communication client are associated with the same organization, and the second communication client is an application program except the first communication client in all application programs used by the organization.
6. The method of claim 5, wherein the method further comprises:
obtaining a callback parameter which is sent by the first communication client and carries the change notification address and the callback token, and configuring the callback parameter; the callback parameter is used for indicating the communication relationship between the first communication client and the event server.
7. The method of claim 5, wherein the callback parameter further comprises a key; the information change message comprises the callback address and encrypted information, and the encrypted information is obtained by encrypting the service change information through the secret key by the first communication client;
the extracting the service change information in the information change message includes:
acquiring the encrypted information in the information change message;
and decrypting the encrypted information through the key to obtain the service change information.
8. The method of claim 5, wherein said information change message includes said callback address and said service change information; the callback address comprises the change notification address, a random parameter and a first encryption signature; the first encrypted signature is generated by the first communication client based on the callback token and the random parameter;
the verifying the validity of the information change message according to the callback address in the information change message includes:
acquiring the callback address in the information change message, and generating a second encryption signature according to the callback token and the random parameter in the callback address;
if the second encrypted signature is the same as the first encrypted signature, the information change message is represented as a legal message, and the step of extracting the service change information in the information change message is executed;
and if the second encrypted signature is different from the first encrypted signature, indicating that the information change message is an illegal message, and sending a synchronous change failure message to the first communication client.
9. The method of claim 5, wherein the method further comprises:
if the accumulated time reaches the target time length, acquiring second service data of the first communication client and updated first service data in the second communication client;
if the second service data is different from the updated first service data, sending an information change abnormal message to the second communication client, so that the second communication client updates the updated first service data based on the second service data in the information change abnormal message;
and if the second service data is the same as the updated first service data, sending a message synchronous change normal message to the second communication client.
10. The method of claim 5, wherein the method further comprises:
sending a data format aiming at the service change information to the second communication client;
the sending the service change information to the second communication client indicated by the configured communication address includes:
and packaging the service change information into packaged data with the data format, and sending the packaged data to the second communication client indicated by the configured communication address, so that the second communication client acquires each parameter included in the packaged data based on the data format, and changes the first service data recorded in the second communication client through each parameter.
11. An information synchronization changing apparatus, comprising:
the first acquisition module is used for the first communication client to acquire the service change information;
the generating module is used for responding to the submission operation aiming at the service change information, updating the service data in the first communication client according to the service change information, calling a change notification address and a call-back token from a call-back parameter, generating a call-back address based on the call-back token and the change notification address, and generating an information change message according to the call-back address and the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with the event server; the event server is a server pointed by the change notification address, and is configured with a communication address of a second communication client;
a sending module, configured to send the information change packet to the event server, so that after verifying the validity of the information change packet according to the callback token, the event server sends the service change information in the information change packet to the second communication client indicated by the communication address; the service change information is used for updating service data in the second communication client;
the first communication client, the event server and the second communication client belong to different service platforms respectively; the first communication client, the event server and the second communication client are associated with the same organization, and the second communication client is an application program except the first communication client in all application programs used by the organization.
12. An information synchronization changing apparatus, comprising:
a first obtaining module, configured to obtain, by an event server, an information change packet sent by a first communication client through a change notification address, where the information change packet is generated by the first communication client according to a callback address and service change information, the callback address is generated by the first communication client based on a callback token and the change notification address, and the change notification address is an address called from a callback parameter by the first communication client in response to a commit operation for the service change information; the callback parameter is a parameter configured in the first communication client and used for communicating with the event server; the event server is a server to which the change notification address points; the service change information is used for updating service data in the first communication client;
the extraction module is used for verifying the legality of the information change message according to the callback address in the information change message, and extracting the service change information in the information change message if the information change message is a legal message;
a first sending module, configured to send the service change information to a second communication client indicated by a configured communication address, so that the second communication client updates first service data recorded in the second communication client based on the service change information, and the event server is configured with the communication address of the second communication client;
the first communication client, the event server and the second communication client belong to different service platforms respectively; the first communication client, the event server and the second communication client are associated with the same organization, and the second communication client is an application program except the first communication client in all application programs used by the organization.
13. A computer, comprising a processor, a memory, an input output interface;
the processor is connected to the memory and the input/output interface, respectively, wherein the input/output interface is used for inputting and outputting data, the memory is used for storing program codes, and the processor is used for calling the program codes to execute the method according to any one of claims 1-4 or claims 5-10.
14. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions which, when executed by a processor, perform the method according to any of claims 1-4 or claims 5-10.
CN201911032411.8A 2019-10-28 2019-10-28 Information synchronous changing method, device, computer and readable storage medium Active CN112738008B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911032411.8A CN112738008B (en) 2019-10-28 2019-10-28 Information synchronous changing method, device, computer and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911032411.8A CN112738008B (en) 2019-10-28 2019-10-28 Information synchronous changing method, device, computer and readable storage medium

Publications (2)

Publication Number Publication Date
CN112738008A CN112738008A (en) 2021-04-30
CN112738008B true CN112738008B (en) 2022-07-12

Family

ID=75589355

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911032411.8A Active CN112738008B (en) 2019-10-28 2019-10-28 Information synchronous changing method, device, computer and readable storage medium

Country Status (1)

Country Link
CN (1) CN112738008B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207580A (en) * 2007-12-25 2008-06-25 腾讯科技（深圳）有限公司 System and method for adding and deleting linkman synchronously by instant communication platform and business platform
CN104519100A (en) * 2013-09-29 2015-04-15 重庆新媒农信科技有限公司 Method for automatic heterogeneous platform file synchronization and puppet server
US9955444B1 (en) * 2014-11-05 2018-04-24 PubNub Inc. Data synchronization across multiple devices connecting to multiple data centers
CN108063757A (en) * 2017-11-24 2018-05-22 海尔优家智能科技（北京）有限公司 A kind of account relating and the method and apparatus of information sharing
CN109309729A (en) * 2018-10-29 2019-02-05 杭州安恒信息技术股份有限公司 The method and apparatus of data are transmitted under a kind of big flow faster
CN110336828A (en) * 2019-07-15 2019-10-15 中国联合网络通信集团有限公司 A kind of information synchronization method and first server

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207580A (en) * 2007-12-25 2008-06-25 腾讯科技（深圳）有限公司 System and method for adding and deleting linkman synchronously by instant communication platform and business platform
CN104519100A (en) * 2013-09-29 2015-04-15 重庆新媒农信科技有限公司 Method for automatic heterogeneous platform file synchronization and puppet server
US9955444B1 (en) * 2014-11-05 2018-04-24 PubNub Inc. Data synchronization across multiple devices connecting to multiple data centers
CN108063757A (en) * 2017-11-24 2018-05-22 海尔优家智能科技（北京）有限公司 A kind of account relating and the method and apparatus of information sharing
CN109309729A (en) * 2018-10-29 2019-02-05 杭州安恒信息技术股份有限公司 The method and apparatus of data are transmitted under a kind of big flow faster
CN110336828A (en) * 2019-07-15 2019-10-15 中国联合网络通信集团有限公司 A kind of information synchronization method and first server

Also Published As

Publication number Publication date
CN112738008A (en) 2021-04-30

Similar Documents

Publication Publication Date Title
US10880732B2 (en) Authentication of phone caller identity
US8245037B1 (en) Encryption key management
US8447970B2 (en) Securing out-of-band messages
CN110868301B (en) Identity authentication system and method based on state cryptographic algorithm
CN112822255B (en) Block chain-based mail processing method, mail sending end, receiving end and equipment
US8848922B1 (en) Distributed encryption key management
KR20150079489A (en) Instant messaging method and system
CN112400299B (en) Data interaction method and related equipment
US10063655B2 (en) Information processing method, trusted server, and cloud server
CN114143117B (en) Data processing method and device
WO2023160420A1 (en) Group message encryption method and apparatus, device and storage medium
CN112202557A (en) Encryption method, device, equipment and storage medium based on secret key update distribution
CN108418679B (en) Method and device for processing secret key under multiple data centers and electronic equipment
CN113872940B (en) Access control method, device and equipment based on NC-Link
CN111181920A (en) Encryption and decryption method and device
CN103997730A (en) Method for decrypting, copying and pasting encrypted data
CN109120576A (en) Data sharing method and device, computer equipment and storage medium
CN112738008B (en) Information synchronous changing method, device, computer and readable storage medium
CN115391795A (en) Data processing method, related device and medium
CN112699391A (en) Target data sending method and privacy computing platform
CN113761566A (en) Data processing method and device
CN113785547B (en) Safety transmission method and corresponding device for Profile data
CN110881040B (en) Calling method and device
CN116192466A (en) Letter processing method, device, electronic equipment and storage medium
CN113591153A (en) Data processing method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40041935

Country of ref document: HK

SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant