An information synchronization change method and device, electronic equipment and storage medium

Abstract

The application relates to the technical field of information processing, in particular to an information synchronization changing method and device, electronic equipment and a storage medium, which are used to improve information synchronization changing accuracy. The method comprises the following steps: receiving a notification message triggered based on a target changing event, and obtaining a first serial number of the target changing event from the notification message; determining service identification information of at least one to-be-processed service in which service information is changed based on at least the first serial number, wherein the to-be-processed service at least comprises a target service; sending a changing information acquisition request to a service server, wherein the changing information acquisition request carries the service identification information of the at least one to-be-processed service; and performing information synchronization changing based on service information of at least one to-be-processed service changing returned by the service server. Since the service identification information of the service needing to change information is determined based on the serial number in the application, the changed service information can be acquired, and the information synchronization changing accuracy can be effectively improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of information processing, and in particular to an information synchronization changing method and device, electronic equipment and storage medium. BACKGROUND

[0002] With the rapid development of the Internet, people's work, life, study and communication increasingly rely on the network for information transmission, and some information will be stored in multiple terminals. When the information changes, multiple terminals need to be synchronized.

[0003] Taking customer group information change as an example, the related art mainly adopts the following two ways to change the information synchronization:

[0004] Method one: first pull the customer group data in full, and then when the object is operated (add, delete or modify) the customer group through the client, the customer group change event will be generated, and the enterprise will be called back to inform the current changed customer group ID (Identity document, identity number); the enterprise receives the change event, and obtains the details of the customer group according to the customer group ID; the enterprise updates the local data according to the details pulled.

[0005] Method two: pull the customer group details in full according to a certain period (for example, every day), and cover the local data.

[0006] However, based on method one, due to network reasons or the stability of the server of the enterprise receiving the event, some events cannot be successfully called back to the enterprise; or, due to network delay, the order of receiving multiple events may not be accurate, which may cause the change event received by the enterprise to be unreliable, so that the data cannot be accurately synchronized, and the information update part is unreliable; based on method two, full pulling will bring great traffic pressure, and the information synchronization changing efficiency is low. Therefore, how to efficiently and accurately realize information synchronization changing is urgent to be solved. SUMMARY

[0007] The embodiments of the present application provide an information synchronization changing method, device, electronic equipment and storage medium, to improve the accuracy of information synchronization changing.

[0008] The first information synchronization changing method provided by the embodiments of the present application comprises:

[0009] Receiving a notification message triggered based on a target change event, and obtaining a first flow identifier of the target change event from the notification message; the target change event represents that the business information of a target business changes;

[0010] Determining, based at least on the first flow identifier, service identifier information of at least one to-be-processed service whose service information has been changed, the to-be-processed service at least including the target service;

[0011] Sending a change information acquisition request to a service server, wherein the change information acquisition request carries service identification information of the at least one service to be processed;

[0012] Based on the business information of the at least one pending business change returned by the business server, information synchronization change is performed.

[0013] The second information synchronization change method provided in the embodiment of the present application includes:

[0014] Sending a notification message triggered by a target change event to a service management terminal, so that the service management terminal obtains a first flow identifier of the target change event from the notification message, and determines service identifier information of at least one pending service that has changed based at least on the first flow identifier; the target change event indicates that service information of a target service has changed, and the pending services include at least the target service;

[0015] Receiving a change information acquisition request sent by the service management terminal, wherein the change information acquisition request carries service identification information of the at least one service to be processed;

[0016] Return the service information of the at least one pending service change to the service management end, so that the service management end performs information synchronization changes.

[0017] The first information synchronization change device provided in the embodiment of the present application includes:

[0018] A receiving unit, configured to receive a notification message triggered by a target change event, and obtain a first flow identifier of the target change event from the notification message; the target change event indicates that business information of a target business has changed;

[0019] A first determining unit is configured to determine, based at least on the first flow identifier, service identification information of at least one to-be-processed service whose service information has been changed, wherein the to-be-processed service includes at least the target service;

[0020] A sending unit, configured to send a change information acquisition request to a service server, wherein the change information acquisition request carries service identification information of the at least one service to be processed;

[0021] The changing unit is configured to perform information synchronization changes based on the business information of the at least one pending business change returned by the business server.

[0022] Optionally, values of the flow identifiers are sequentially increased according to the order of the corresponding change events; the apparatus further comprises a second determination unit configured to:

[0023] determine that the value of the first flow identifier is not greater than the value of the second flow identifier, and not process the information synchronization change this time.

[0024] Optionally, the first determination unit is specifically configured to:

[0025] determine, based on at least the first flow identifier, service identifier information of at least one to-be-processed service in which service information has changed and a corresponding change type;

[0026] The change unit is specifically configured to:

[0027] perform information synchronization change based on the corresponding change type of each of the at least one to-be-processed service and the corresponding changed service information, respectively.

[0028] The second information synchronization change apparatus provided by the embodiment of the present application comprises:

[0029] a sending unit configured to send, to a service management end, a notification message triggered based on a target change event, so that the service management end obtains, from the notification message, a first flow identifier of the target change event and determines, based on at least the first flow identifier, service identifier information of at least one to-be-processed service in which service information has changed; the target change event indicates that service information of a target service has changed, and the to-be-processed service at least includes the target service.

[0030] a first receiving unit configured to receive a change information acquisition request sent by the service management end, the change information acquisition request carrying the service identifier information of the at least one to-be-processed service;

[0031] a returning unit configured to return, to the service management end, changed service information of the at least one to-be-processed service, so that the service management end performs information synchronization change.

[0032] Optionally, before the receiving of the change information acquisition request sent by the service management end, the apparatus further comprises a second receiving unit configured to:

[0033] receive an identifier acquisition request sent by the service management end, and determine service identifier information of services related to each of the target flow identifiers in the identifier acquisition request;

[0034] determine, based on each of the target flow identifiers, service identifier information, and return the service identifier information to the service management end as the identifier information of the at least one to-be-processed service;

[0035] Among them, the target flow identifier is determined by the business management end. If the business management end receives other historical change events before receiving the target change event, then at least one target flow identifier is determined based on the second flow identifier of the last processed historical change event and the first flow identifier; if the business management end does not receive other historical change events before receiving the target change event, then the first flow identifier is used as the target flow identifier.

[0036] Optionally, the device further includes a storage unit, configured to:

[0037] Every time a notification message triggered by a change event is received from a business client, the business identification information of the business whose business information has changed is stored and a serial identifier is generated. The value of the serial identifier increases in sequence according to the corresponding change event.

[0038] An embodiment of the present application provides an electronic device, including a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of any one of the above-mentioned information synchronization change methods.

[0039] An embodiment of the present application provides a computer-readable storage medium, which includes a computer program. When the computer program is run on an electronic device, the computer program is used to enable the electronic device to execute the steps of any one of the above-mentioned information synchronization change methods.

[0040] An embodiment of the present application provides a computer program product, which includes a computer program, and the computer program is stored in a computer-readable storage medium; when a processor of an electronic device reads the computer program from the computer-readable storage medium, the processor executes the computer program, so that the electronic device performs the steps of any one of the above-mentioned information synchronization change methods.

[0041] The beneficial effects of this application are as follows:

[0042] The information synchronization change method, device, electronic device and storage medium provided in the embodiments of the present application receive a notification message triggered by a target change event, obtain the first flow identifier of the target change event from the notification message, and determine the business identification information of at least one pending business whose business information has changed based on at least the first flow identifier; then, send a change information acquisition request to the business server, and perform information synchronization change based on the business information of at least one pending business change returned by the business server. In the above manner, information synchronization change is triggered based on the change event, and information is pulled based on the flow identifier corresponding to each change event. Only the business information of at least one pending business whose business information has changed based on the first flow identifier is pulled, that is, incremental information is pulled. Compared with periodic full information pulling, it can reduce traffic pressure and improve the efficiency of information synchronization change; further, determining the business identification information of the business information that has changed based on the first flow identifier and obtaining the changed business information based on the business identification information can avoid the situation where the information synchronization change is inconsistent due to the loss or disorder of the notification message, thereby improving the accuracy of information synchronization change.

[0043] Other features and advantages of the present application will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present application. The purposes and other advantages of the present application can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0045] Figure 1 A schematic diagram of an information synchronization change method in the related art;

[0046] Figure 2 A schematic diagram of another information synchronization change method in the related art;

[0047] Figure 3 This is an optional schematic diagram of an application scenario in an embodiment of the present application;

[0048] Figure 4 Flowchart of an implementation of an information synchronization change method provided in an embodiment of the present application

[0049] Figure 5 This is a diagram showing the correspondence between the first callback notification and the change flow in the embodiment of the present application;

[0050] Figure 6A corresponding relationship diagram of callback notification and change pipeline in the first embodiment of the present application;

[0051] Figure 7 A corresponding relationship diagram of callback notification and change pipeline in the first embodiment of the present application;

[0052] Figure 8 An implementation flowchart of another information synchronization change method in the embodiments of the present application;

[0053] Figure 9 A schematic diagram of a pipeline identification generation mechanism in the embodiments of the present application;

[0054] Figure 10 An interaction timing diagram of an information synchronization change method in the embodiments of the present application;

[0055] Figure 11A A flowchart of an information synchronization change method in the embodiments of the present application;

[0056] Figure 11B A logic diagram of an information synchronization change method in the embodiments of the present application;

[0057] Figure 11C A flowchart of another information synchronization change method in the embodiments of the present application;

[0058] Figure 12 A structural diagram of an information synchronization change device in the embodiments of the present application;

[0059] Figure 13 A structural diagram of another information synchronization change device in the embodiments of the present application;

[0060] Figure 14 A hardware structural diagram of an electronic device applying the embodiments of the present application;

[0061] Figure 15 A hardware structural diagram of another electronic device applying the embodiments of the present application. DETAILED DESCRIPTION

[0062] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments described in the present application, all other embodiments obtained by those skilled in the art without any creative work fall within the scope of protection of the technical solutions of the present application.

[0063] The following is an introduction to some concepts involved in the embodiments of this application.

[0064] Business server: used to store all business information. One business server can correspond to multiple business management terminals. When business information changes, the business server notifies the corresponding business management terminal to synchronize the information changes.

[0065] Business management terminal: a server specifically used to handle a certain business, or a client corresponding to a related account specifically used to handle a certain business. Taking the server as an example, for example, all businesses will be stored in the business server. Business server A is used to handle the business of company A, and business server B is used to handle the business of company B.

[0066] Incremental update: refers to updating only the areas that need to be changed during the update operation. Areas that do not need to be updated or have already been updated will not be updated repeatedly. In the embodiment of the present application, the business information of the pending business that has changed is synchronized with the incremental update method, which can save traffic and improve the efficiency of information synchronization updates.

[0067] Event callback: refers to calling the callback interface after an event occurs to respond to event changes. In the embodiment of the present application, after a change event occurs, the business server will call the event back to the business management end to notify the business management end to synchronize information changes.

[0068] Information synchronization changes: refers to information that needs to be synchronized on multiple terminals after the information is changed. In the embodiment of this application, the customer group information change is mainly taken as an example. When the object adds, deletes, or modifies the customer group through the client, the changed information is synchronized between the business management terminal and the business service terminal.

[0069] Application Programming Interface (API): A set of predefined interfaces (such as function interfaces) or agreements that connect different components of a software system. It is used to provide a set of routines that applications and developers can access based on a certain software or hardware without having to access the source code or understand the details of the internal working mechanism.

[0070] A client, or user end, is a program that interfaces with a server and provides local services to clients. Aside from some applications that run only locally, it's typically installed on a regular client computer and requires interaction with the server. Since the development of the Internet, common client applications have included web browsers for the World Wide Web, email clients for sending and receiving emails, and instant messaging client software. These applications require servers and services on the network to provide the corresponding services, such as databases and email. Therefore, a specific communication connection must be established between the client and server to ensure the proper functioning of the application.

[0071] The following is a brief introduction to the design concept of the embodiment of this application:

[0072] With the rapid development of the Internet, people's work, life, study and communication increasingly rely on the Internet to transmit information. Moreover, some information will be stored on multiple terminals. When the information changes, multiple terminals need to synchronize the information.

[0073] Taking customer group information changes as an example, related technologies mainly use the following two methods to synchronize information changes:

[0074] Method 1: If Figure 1 As shown, the enterprise server (business management end) pulls the customer group in full for the first time and maintains a copy of the data. When the object operates (adds, deletes, or modifies) the customer group through the enterprise communication client, a customer group change event is generated on the enterprise communication server (business server). The enterprise communication server calls back to inform the enterprise server of the customer group ID that has changed. After receiving the change event, the enterprise server obtains the customer group change details based on the customer group ID and updates the local data based on the pulled details. The data is incrementally updated each time based on the callback event to keep the data on both the enterprise server and the business server aligned.

[0075] Method 2: If Figure 2 As shown, the enterprise server pulls all customer group details from the enterprise communication server at a certain period (for example, every day), overwriting the local data.

[0076] However, based on method 1, due to network problems or the stability of the enterprise's server receiving events, some events may not be successfully callbacked to the enterprise server. Alternatively, due to network latency, the order in which multiple events are received may not be accurate. This may cause the change events received by the enterprise server to be unreliable, making it impossible to accurately synchronize data and resulting in unreliable information updates.

[0077] With the second approach, because the number of customer groups can grow without a limit, full data pulls will cause increasing traffic pressure and slow down the process as the number of customer groups increases. Furthermore, due to the high cost of full data pulls, frequent pulls are not possible (generally, only daily scheduled pulls are possible). Therefore, problematic data may exist until the data is repaired within a day, resulting in low real-time data repair and inefficient information synchronization.

[0078] In summary, existing technologies essentially rely on the business management side passively receiving change events from the business service side for incremental updates. However, due to unavoidable event loss or out-of-order processing on the service receiving side or due to network issues, a heavy full data pull is required to continuously repair the data, resulting in low information synchronization efficiency. Therefore, how to achieve efficient and accurate information synchronization is an urgent problem to be solved.

[0079] In view of this, the embodiments of the present application propose an information synchronization change method, device, electronic device and storage medium. In the embodiments of the present application, by receiving a notification message triggered by a target change event, and obtaining the first flow identifier of the target change event from the notification message, and determining the business identification information of at least one pending business whose business information has changed based on at least the first flow identifier; then, sending a change information acquisition request to the business server, and performing information synchronization change based on the business information of at least one pending business change returned by the business server. Through the above-mentioned method, information synchronization change is triggered based on the change event, and information is pulled based on the flow identifier corresponding to each change event, and only the business information of at least one pending business whose business information has changed based on the first flow identifier is pulled, that is, incremental pulling of information. Compared with periodic full-volume pulling of information, it can reduce traffic pressure and improve the efficiency of information synchronization change. Furthermore, by determining the business identification information of the business information that has changed based on the first flow identifier, and obtaining the changed business information based on the business identification information, it can avoid the situation where the information synchronization change is inconsistent due to the loss or disorder of the notification message, thereby improving the accuracy of information synchronization change.

[0080] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application can be combined with each other if there is no conflict.

[0081] like Figure 3 , which is a schematic diagram of an application scenario of an embodiment of the present application. The application scenario diagram includes two terminal devices 310 and a server 320.

[0082] In the embodiment of the present application, the terminal device 310 includes but is not limited to mobile phones, tablet computers, laptop computers, desktop computers, e-book readers, intelligent voice interaction devices, smart home appliances, car terminals and other devices; a client related to information interaction can be installed on the terminal device, which can be software (such as a browser, instant messaging software, etc.), or a web page, applet, etc. The server 320 is a background server corresponding to the software or web page, applet, etc., or a server specifically used for synchronizing information changes, which is not specifically limited in this application. The server 320 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and basic cloud computing services such as big data and artificial intelligence platforms.

[0083] It should be noted that the information synchronization change method in the embodiment of the present application can be executed by an electronic device, which can be a server 320 or a terminal device 310, that is, the method can be executed by the server 320 or the terminal device 310 alone, or jointly by the server 320 and the terminal device 310, or jointly by multiple servers 320. For example, when jointly executed by the server 320 and the terminal device 310, the terminal device 310 receives a notification message triggered by a target change event, obtains the first flow identifier of the target change event from the notification message, and determines the business identification information of at least one pending business whose business information has changed based on at least the first flow identifier, and then sends a change information acquisition request carrying the business identification information of at least one pending business to the business server 320. Finally, based on the business information of at least one pending business change returned by the business server 320, the information synchronization change is performed.

[0084] It should be noted that the service management end here is only described as the terminal device 310. In fact, the service management end in the embodiment of the present application can be the terminal device 310 or the server 320. The information change method in the embodiment of the present application can be jointly executed by the terminal device and the server, or by multiple servers, and no specific limitation is made here.

[0085] In an optional implementation, the terminal device 310 and the server 320 may communicate via a communication network.

[0086] In an optional implementation, the communication network is a wired network or a wireless network.

[0087] It should be noted that Figure 3 The figures are only examples. In fact, the number of terminal devices and servers is not limited and is not specifically limited in the embodiments of this application.

[0088] In an embodiment of the present application, when there are multiple servers, the multiple servers can be combined into a blockchain, and the servers are nodes on the blockchain; as disclosed in the information synchronization change method of the embodiment of the present application, the business information involved can be saved on the blockchain, such as customer group ID, etc.

[0089] In addition, the embodiments of the present application can be applied to various scenarios, including not only information synchronization change scenarios, but also including but not limited to cloud technology, artificial intelligence, smart transportation, assisted driving and other scenarios.

[0090] It is understandable that in the specific implementation of this application, related data such as user information is involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0091] The following describes the information synchronization change method provided by the exemplary embodiment of the present application in combination with the application scenarios described above and with reference to the accompanying drawings. It should be noted that the above application scenarios are only shown to facilitate understanding of the spirit and principles of the present application, and the implementation methods of the present application are not limited in this respect.

[0092] See Figure 4 , is an implementation flow chart of an information synchronization change method provided in an embodiment of the present application, which is applied to the business management end. The following takes the synchronization change of customer group information as an example to introduce the information synchronization change method in this application. The specific implementation process of this method is as follows:

[0093] S401: The service management terminal receives a notification message triggered by a target change event, and obtains the first flow identifier of the target change event from the notification message;

[0094] The target change event represents a change in the business information of the target business. In the embodiments of this application, specific information synchronization can refer to: synchronized changes in customer information, synchronized changes in organizational structure, etc. In addition, it can also refer to any other information synchronization changes that require remote synchronization. The following mainly uses the synchronized changes in customer group information as an example to illustrate.

[0095] Optionally, the values ​​of the flow identifiers can be incremented in the order of the corresponding change events. For example, if the target service is a customer group change service, and user A of Enterprise A uses the enterprise communication client to add a new enterprise customer group, then the addition of the new enterprise customer group is the target change event. The enterprise server (i.e., the service management end) needs to synchronously update the customer group information and receive a notification message with the first flow identifier "Event 001." If user A of Enterprise A subsequently deletes the enterprise customer group, the first flow identifier carried in the notification message received by the enterprise server is "Event 002."

[0096] S402: The service management terminal determines, based at least on the first flow identifier, service identification information of at least one to-be-processed service whose service information has been changed;

[0097] Among them, the business to be processed includes at least the target business. For example, when the first flow is identified as "Event 001", the business management end determines that the customer group ID of the corresponding business information that has changed is "Enterprise Customer Group 5" based on "Event 001".

[0098] S403: The service management terminal sends a request for obtaining change information to the service server;

[0099] Among them, the change information acquisition request carries the business identification information of at least one business to be processed. For example, the business management end sends a change information acquisition request carrying the customer group ID "enterprise customer group 5", indicating that the business management end needs to obtain the change information of enterprise customer group 5.

[0100] S404: The service management terminal performs information synchronization based on the service information of at least one pending service change returned by the service server.

[0101] For example, the business server returns the information of enterprise customer group 5, and the business management end correspondingly adds the information of enterprise customer group 5 to the local customer group information.

[0102] In an embodiment of the present application, information synchronization changes are triggered based on change events, and information is pulled based on the flow identifier corresponding to each change event. Only the business information of at least one pending business whose business information has changed based on the first flow identifier is pulled, that is, incremental information is pulled. Compared with periodic full-scale information pulling, this can reduce traffic pressure and improve the efficiency of information synchronization changes. Furthermore, by determining the business identification information of the business information that has changed based on the first flow identifier and obtaining the changed business information based on the business identification information, it can avoid the situation where inconsistent information synchronization changes are caused by loss or disorder of notification messages, thereby improving the accuracy of information synchronization changes.

[0103] Optionally, there are two cases when implementing step S402:

[0104] Case 1: If it is determined that other historical change events are received before the target change event is received, at least one target serial identifier is determined based on the second serial identifier of the last processed historical change event and the first serial identifier; an identifier acquisition request carrying each target serial identifier is sent to the service server; and the service identifier information of the service related to each target serial identifier returned by the service server is taken as the service identifier information of at least one to-be-processed service.

[0105] Among them, when determining at least one target serial identifier based on the second serial identifier and the first serial identifier, it can be further divided into the following two categories:

[0106] 1) If the value of the first serial identifier is adjacent to the value of the second serial identifier, the first serial identifier is taken as the target serial identifier;

[0107] For example, if the first serial identifier is "event 003" and the second serial identifier is "event 002", it indicates that the information synchronization change processing corresponding to "event 002" has been completed when the last information synchronization change is performed, and the information synchronization change processing corresponding to "event 003" is requested to be completed when the current information synchronization change is performed, so "event 003" needs to be taken as the target serial identifier.

[0108] Further, the identifier acquisition request is sent to the service server to acquire the service identifier information corresponding to "event 003": "customer group 2", and the service identifier information is taken as the service identifier information of the to-be-processed service.

[0109] 2) If the value of the first serial identifier is not adjacent to the value of the second serial identifier, the first serial identifier and each intermediate serial identifier between the first serial identifier and the second serial identifier are taken as the target serial identifier.

[0110] For example, if the first serial identifier is "event 004" and the second serial identifier is "event 001", it indicates that the information synchronization change processing corresponding to "event 001" has been completed when the last information synchronization change is performed, and the information synchronization change processing corresponding to "event 004" is requested to be completed when the current information synchronization change is performed, and the change events corresponding to "event 002" and "event 003" also need to be performed in the current information synchronization due to network delay or other reasons, so "event 002", "event 003" and "event 004" are taken as the target serial identifier.

[0111] Then, an identification acquisition request is sent to the business server to obtain the business identification information corresponding to "Event 002", "Event 003" and "Event 004" respectively: "Customer Group 7", "Customer Group 2", "Customer Group 10", and the above three business identification information are used as the business identification information of the business to be processed.

[0112] It should be noted that the above are simple examples of one change event (or flow identifier) ​​corresponding to one customer group. In fact, changes in information of several customer groups within a period of time also correspond to the same change event. At this time, one target flow identifier also corresponds to multiple business identification information, which is not specifically limited here.

[0113] Case 2: If it is determined that no other historical change events have been received before the target change event is received, the first transaction identifier is directly used as the target transaction identifier; an identifier acquisition request carrying each target transaction identifier is sent to the business server; the business identifier information of the business related to the change event corresponding to each target transaction identifier returned by the business server is used as the business identifier information of at least one business to be processed.

[0114] Specifically, taking the first flow identifier of the currently received target change event as "Event 003" as an example, if no other historical change events have been received before, "Event 003" is directly used as the target flow identifier, and an identifier acquisition request is sent to the business server to obtain the business identification information corresponding to "Event 003" as "Customer Group 2", and "Customer Group 2" is used as the business identification information of the business to be processed.

[0115] It should be noted that the first serial number identifier and the second serial number identifier in the embodiment of the present application are both serial number identifiers determined based on the order in which the change events occur. "First" and "second" are only used to distinguish between target change events and historical change events, and cannot limit the order in which the change events occur.

[0116] Assume that the order of occurrence of the three change events is: ABC, and their corresponding serial numbers are: 101, 102, and 103 respectively.

[0117] Optionally, when the business management end pulls the change flow based on the callback notification (i.e., notification message), it can be divided into the following three situations:

[0118] Case 1: The callback is normal;

[0119] like Figure 5 As shown in the figure, the business management terminal receives three change events ABC in sequence. Each time it receives an event, it obtains a change flow. After receiving three callback notifications, it pulls the three change flows 101-102-103 (i.e., flow identifiers, also called flow numbers) in sequence.

[0120] Case 2: callback is lost;

[0121] like Figure 6 As shown in the figure, when callback notification B is lost, the business management end only receives callback notifications A and C. When callback notification A is received, flow 101 is pulled and the maximum number 101 is recorded. When callback notification C is received, the two change flows 102 and 103 are pulled, and the three change flows 101-102-103 are also obtained.

[0122] Case 3: Callbacks are out of order.

[0123] like Figure 7 As shown, in the case where callback notification A is out of order, the business management end receives three callback notifications BCA in succession. When callback notification B is received, the corresponding change flow is 102, and the flow identifier of the last processing is 100. Therefore, change flows 101 and 102 are pulled this time. When callback notification C is received, the corresponding change flow is 103. The change flow 102 was pulled last time, so the change flow 103 is pulled this time. When callback notification A is received, the corresponding change flow is 101, which is not greater than the change flow 103 pulled last time. Therefore, this change is not processed. In this way, the three change flows 101-102-103 are still pulled in succession.

[0124] In the above three situations, the business management end obtains the three change flows 101-102-103 in succession. It can be seen that through the information change method provided in the embodiment of the present application, the loss or disorder of callback events will not cause data inconsistency problems. Therefore, this mechanism has the property of automatic compensation, and there is no need to add additional compensation logic for pulling the full amount of data every day.

[0125] Optionally, based at least on the first flow identifier, determine the business identification information and corresponding change type of at least one pending business whose business information has changed; and perform information synchronization changes based on the corresponding change type of at least one pending business and the corresponding changed business information.

[0126] Specifically, the change types may include customer group addition, customer group deletion, customer group modification, etc. For example, the first flow identifier is "Event 003", the second flow identifier is "Event 002", the target flow identifier is "Event 003", the corresponding business identification information is "Customer Group 2", and the corresponding change type is customer group modification, then the information of customer group 2 is modified in the local customer group data.

[0127] Based on the above implementation method, information synchronization changes are performed. Compared with the prior art that performs incremental updates based on the enterprise server passively receiving change events from the enterprise communication server, because the prior art inevitably causes event loss or disorder due to service receiving end or network reasons, it is necessary to pull a lot of full data to continuously repair the data. However, this application changes from passive to active. By storing a list of customer groups that have changed on the enterprise communication server, the enterprise server can actively pull the change flow information to incrementally synchronize data, which can avoid problems such as packet loss and disorder caused by passive reception. More importantly, the actual proportion of customer groups that have changed is very low compared to the full customer group, so it can greatly alleviate traffic pressure and improve real-time performance.

[0128] See Figure 8 , which is an implementation flow chart of another information synchronization change method in an embodiment of the present application, applied to a business server, including the following steps:

[0129] S801: The service server sends a notification message triggered by a target change event to the service management terminal;

[0130] Among them, the business management end obtains the first flow identifier of the target change event from the notification message, and determines the business identification information of at least one pending business that has changed based at least on the first flow identifier; the target change event indicates that the business information of the target business has changed, and the pending business includes at least the target business.

[0131] S802: The service server receives a request for obtaining change information sent by the service management terminal;

[0132] The change information acquisition request carries business identification information of at least one business to be processed;

[0133] S803: The service server returns service information of at least one pending service change to the service management terminal.

[0134] Among them, the business management end performs information synchronization changes based on the business information of the pending business changes.

[0135] Optionally, each time the service server receives a notification message triggered by a change event from the service client, it stores the service identification information of the service whose service information has been changed and generates a serial number.

[0136] For example, if a user adds a new customer group 6 through the business client, the business server receives the notification message, stores the business identification information "customer group 6", and generates a flow identification "event 001". Later, the user modifies the information of customer group 5 through the business client. After receiving the notification message, the business server stores the business identification information "customer group 5" and generates a flow identification "event 002". Similarly, the values ​​of the flow identifications increase in sequence according to the corresponding change events.

[0137] See Figure 9 , which is a schematic diagram of a flow identification generation mechanism in an embodiment of the present application. The business server records each customer group ID (i.e., business identification information) that has changed in chronological order. Each change in flow has an auto-increment number. When the business management end pulls the flow, the maximum number of the flow pulled this time is recorded as a cursor. The next time the business management end pulls the flow, it can start pulling from the maximum number pulled last time. Figure 9 As shown, it is like a sliding window sliding to the right along the time axis.

[0138] Optionally, before step S82, the business server further receives an identification acquisition request sent by the business management end, and determines business identification information of the business related to the change event corresponding to each target flow identification in the identification acquisition request; uses the business identification information determined based on each target flow identification as identification information of at least one business to be processed, and returns the information to the business management end;

[0139] For example, the target flow identifier included in the acquisition request sent by the business management end is "Event 005", and the business server determines that the business identification information corresponding to the target flow identifier is "Customer Group 7", then "Customer Group 7" is used as the identification information of the business to be processed and returned to the business management end, so that the business management end sends a request to obtain the change information corresponding to "Customer Group 7" based on the received identification information.

[0140] See Figure 10 , which is an interactive sequence diagram of an information synchronization change method of the present application, used to introduce the interaction logic between the business management terminal and the business server, including the following steps:

[0141] S1001: The service server stores the service identification information according to the notification information carrying the service identification information sent by the service client, and generates a flow identification.

[0142] S1002: The service server sends a notification message carrying a first flow identifier to the service management terminal;

[0143] S1003: The business management terminal determines the target flow ID based on whether other historical change events have been received;

[0144] S1004: The service management terminal sends an identifier acquisition request carrying a target flow identifier to the service server;

[0145] S1005: The service server searches for corresponding service identification information in the stored data according to the target flow identification;

[0146] S1006: The service server sends service identification information corresponding to the target flow identification to the service management terminal;

[0147] S1007: The service management terminal sends a request for obtaining change information carrying service identification information to the service server;

[0148] S1008: The service server sends change information corresponding to the service identification information to the service management terminal;

[0149] S1009: The business management terminal performs information synchronization changes based on the business information of at least one pending business change returned by the business server.

[0150] See Figure 11A , which is a flow chart of a method for synchronously changing information in an embodiment of the present application, and the following is combined with Figure 11A Taking the example of a user adding a new customer group to the enterprise communication client, the information synchronization change method in this application is introduced.

[0151] First, the enterprise user adds a new customer group in the enterprise communication client (i.e., business client), and the customer group ID (i.e., business identification information) is "Customer Group 5". The enterprise communication client sends a notification message carrying the customer group ID to the enterprise communication server (i.e., business server). After receiving the notification message, the enterprise communication server stores the business identification information "Customer Group 5" and generates a serial identification "Event 001". Each time a notification message is received thereafter, the business identification information is stored and a serial identification is generated.

[0152] Then, the enterprise communication server sends a notification message to the enterprise server, and carries the flow identification "Event 001". The enterprise server has not processed other historical change events before, so it uses "Event 001" as the target identification information. The enterprise server sends an identification acquisition request to the enterprise communication server, requesting to obtain the customer group ID corresponding to "Event 001". The enterprise communication server sends the customer group ID "Customer Group 5" corresponding to "Event 001" to the enterprise server. After the enterprise server receives the business identification information "Customer Group 5", it sends a change information acquisition request to the enterprise communication server, requesting to obtain the change information corresponding to "Customer Group 5". The business server receives the change information acquisition request sent by the business management end, and returns the business information of the change of customer group 5. Based on the business information of the change of customer group 5 returned by the business server, the business management end adds customer group 5 information to the local data to synchronize the information.

[0153] in addition, Figure 11A The information change method in this application is introduced by taking the addition of a new customer group as an example. The information change of a customer group can also be the deletion of a customer group, or the modification of the data in the original customer group. The information change method in this application can also be applied to any scenario that requires synchronous changes in information, such as synchronous changes in organizational structure. This application does not make specific limitations here.

[0154] In an embodiment of the present application, the enterprise communication server stores a list of customer group IDs that have changed. When the enterprise server receives a callback notification, it not only obtains the details of the currently changed customer group, but first pulls the list of customer group IDs that have changed from the last change to the present, and then pulls these customer group details in a targeted manner to update the local data. The callback notification is actually just a notification to inform the enterprise server that there is the latest change flow, while the actual change details are pulled by the enterprise server itself. By handling it in this way, even if the callback notification is lost due to network reasons, when the next notification event arrives, the last lost update can be naturally compensated. Similarly, if the callback events received are out of order, it will not cause any impact, because this method does not rely on the order of the callback events. Moreover, because only the details of the customer groups that have changed from the last change event to the present are pulled, information is synchronized in an incremental manner rather than a full manner, avoiding traffic pressure.

[0155] See Figure 11B , which is a logical diagram of an information synchronization change method in an embodiment of the present application, Figure 11B The information synchronization change process of three change events is given as an example. The following takes event 101 as an example. Figure 11C Another embodiment of the information synchronization change method in this application is introduced.

[0156] A corporate user changes the customer information of Customer Group 2 in the corporate communication client. The corporate communication client sends a notification message with the change information to the corporate communication server. The corporate communication server stores the business identifier of this change, "Customer Group 2," generates a serial number identifier, "Event 101," and then sends a callback notification with the serial number identifier, "Event 101," to the corporate server. The corporate server finds that the serial number identifier of the last change event processed is "Event 99," so "Event 100" has not yet been processed. The server requests the business identifier information corresponding to "Event 100" and "Event 101" from the corporate communication server. The server returns the customer group IDs "Customer Group 8" corresponding to "Event 100" and "Customer Group 2" corresponding to "Event 101." The corporate server then requests the change information for "Customer Group 8" and "Customer Group 2." The server returns the change information for "Customer Group 8": the addition of group member Xiao X, and the change information for "Customer Group 2": the change of administrator from Xiao Wang to Xiao Li. The corporate communication server updates local data based on the change information.

[0157] Based on the same inventive concept, the embodiment of the present application also provides an information synchronization change device. Figure 12 As shown, it is a structural diagram of the information synchronization change device 1200, which may include:

[0158] The receiving unit 1201 is configured to receive a notification message triggered by a target change event and obtain a first flow identifier of the target change event from the notification message; the target change event indicates that business information of the target business has changed;

[0159] A first determining unit 1202 is configured to determine, based at least on the first flow identifier, service identification information of at least one to-be-processed service whose service information has been changed, where the to-be-processed service includes at least a target service;

[0160] The sending unit 1203 is configured to send a change information acquisition request to the service server, where the change information acquisition request carries service identification information of at least one service to be processed;

[0161] The changing unit 1204 is configured to perform information synchronization changes based on the business information of at least one pending business change returned by the business server.

[0162] Optionally, the first determining unit 1202 is specifically configured to:

[0163] If it is determined that other historical change events are received before the target change event is received, then at least one target serial number identifier is determined based on the second serial number identifier of the last processed historical change event and the first serial number identifier; or if it is determined that no other historical change events are received before the target change event is received, then the first serial number identifier is used as the target serial number identifier;

[0164] Send an ID acquisition request carrying each target flow ID to the business server;

[0165] The business identification information of the business related to the change event corresponding to each target flow identifier returned by the business server is used as the business identification information of at least one business to be processed.

[0166] Optionally, the first determining unit 1202 is specifically configured to:

[0167] If the value of the first flow identifier is adjacent to the value of the second flow identifier, the first flow identifier is used as the target flow identifier;

[0168] If the value of the first running water identifier is not adjacent to the value of the second running water identifier, the first running water identifier and each intermediate running water identifier between the first running water identifier and the second running water identifier are used as the target running water identifier.

[0169] Optionally, the values ​​of the flow identifiers are incremented in order of the corresponding change events; the apparatus further includes a second determining unit 1205, configured to:

[0170] If it is determined that the value of the first serial number identifier is not greater than the value of the second serial number identifier, the information synchronization change will not be processed.

[0171] Optionally, the first determining unit 1202 is specifically configured to:

[0172] Determining, based at least on the first flow identifier, business identification information and a corresponding change type of at least one pending business whose business information has changed;

[0173] The changing unit 1204 is specifically used for:

[0174] Information synchronization changes are performed based on the change type corresponding to at least one pending business and the business information corresponding to the change.

[0175] Based on the same inventive concept, the embodiment of the present application also provides another information synchronization change device. Figure 13 As shown, it is a schematic diagram of the structure of the information synchronization change device 1300, which may include:

[0176] A sending unit 1301 is configured to send a notification message triggered by a target change event to a service management terminal, so that the service management terminal obtains a first flow identifier of the target change event from the notification message, and determines service identifier information of at least one pending service that has changed based at least on the first flow identifier; the target change event indicates that service information of a target service has changed, and the pending services include at least the target service;

[0177] The first receiving unit 1302 is configured to receive a change information acquisition request sent by the service management terminal, where the change information acquisition request carries service identification information of at least one service to be processed;

[0178] The returning unit 1303 is configured to return at least one piece of service information of a pending service change to the service management terminal, so that the service management terminal can perform information synchronization changes.

[0179] Optionally, before receiving the change information acquisition request sent by the service management terminal, the apparatus further includes a second receiving unit 1304, configured to:

[0180] Receive the identification acquisition request sent by the business management end, and determine the business identification information of the business related to the change event corresponding to each target flow identification in the identification acquisition request;

[0181] Using the service identification information determined based on each target flow identification as identification information of at least one service to be processed, and returning it to the service management terminal;

[0182] Among them, the target flow identifier is determined by the business management end. If the business management end receives other historical change events before receiving the target change event, it determines at least one target flow identifier based on the second flow identifier of the last processed historical change event and the first flow identifier; if the business management end does not receive other historical change events before receiving the target change event, the first flow identifier is used as the target flow identifier.

[0183] Optionally, the device further includes a storage unit 1305, configured to:

[0184] Every time a notification message triggered by a change event is received from a business client, the business identification information of the business whose business information has changed is stored and a serial identifier is generated. The value of the serial identifier increases in sequence according to the corresponding change event.

[0185] For the convenience of description, the above parts are divided into modules (or units) according to their functions and described separately. Of course, when implementing this application, the functions of each module (or unit) can be implemented in the same or multiple software or hardware.

[0186] Those skilled in the art will appreciate that various aspects of the present application can be implemented as systems, methods, or program products. Therefore, various aspects of the present application can be specifically implemented in the following forms: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation that combines hardware and software aspects, which may be collectively referred to herein as a "circuit," "module," or "system."

[0187] Based on the same inventive concept as the above method embodiment, an electronic device is also provided in the embodiment of the present application. In one embodiment, the electronic device may be a server, such as Figure 3 In this embodiment, the structure of the electronic device can be as follows: Figure 14 As shown, it includes a memory 1401 , a communication module 1403 and one or more processors 1402 .

[0188] Memory 1401 is used to store computer programs executed by processor 1402. Memory 1401 may primarily include a program storage area and a data storage area. The program storage area may store an operating system and programs required for running instant messaging functions, while the data storage area may store various instant messaging messages and operating instruction sets.

[0189] Memory 1401 may be a volatile memory, such as random-access memory (RAM); a non-volatile memory, such as read-only memory, flash memory, a hard disk drive (HDD), or a solid-state drive (SSD); or any other medium capable of carrying or storing a desired computer program in the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 1401 may be a combination of the aforementioned memories.

[0190] The processor 1402 may include one or more central processing units (CPUs) or digital processing units, etc. The processor 1402 is configured to implement the above-mentioned information synchronization change method when calling the computer program stored in the memory 1401 .

[0191] The communication module 1403 is used to communicate with terminal devices and other servers.

[0192] The specific connection medium between the memory 1401, the communication module 1403 and the processor 1402 is not limited in the embodiment of the present application. Figure 14 The memory 1401 and the processor 1402 are connected through the bus 1404, and the bus 1404 is connected between the other components Figure 14 The connection between the other components is described by a thick line, which is only illustrative and not limited. The bus 1404 can be divided into an address bus, a data bus, a control bus, etc. For the convenience of description, Figure 14 Only one thick line is used for description, but only one bus or one type of bus is not described.

[0193] The memory 1401 stores a computer storage medium, and the computer storage medium stores computer executable instructions for implementing the information synchronization change method of the embodiments of the present application. The processor 1402 is used to execute the above information synchronization change method, as Figure 4 Indicated.

[0194] In another embodiment, the electronic device can also be other electronic devices, such as the terminal device 310 as Figure 3 Indicated. In this embodiment, the structure of the electronic device can be as Figure 15 Indicated, including a communication component 1510, a memory 1520, a display unit 1530, a camera 1540, a sensor 1550, an audio circuit 1560, a Bluetooth module 1570, a processor 1580, and the like.

[0195] The communication component 1510 is used for communication with the server. In some embodiments, a wireless fidelity (WiFi) module can be included, which belongs to a short-range wireless transmission technology. The electronic device can help the user to send and receive information through the WiFi module.

[0196] The memory 1520 can be used to store software programs and data. The processor 1580 executes various functions and data processing of the terminal device 310 by running the software programs or data stored in the memory 1520. The memory 1520 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state memory device. The memory 1520 stores an operating system that enables the terminal device 310 to run. In the present application, the memory 1520 can store an operating system and various application programs, and can also store codes for executing the information synchronization change method of the embodiments of the present application.

[0197] The display unit 1530 can also be used to display information input by the user or provided to the user, as well as a graphical user interface (GUI) of various menus of the terminal device 310. Specifically, the display unit 1530 may include a display screen 1532 disposed on the front of the terminal device 310. The display screen 1532 may be configured in the form of a liquid crystal display, a light-emitting diode, etc. The display unit 1530 can be used to display the user interface of the communication software in the embodiments of the present application, etc.

[0198] The display unit 1530 can also be used to receive input digital or character information and generate signal input related to user settings and function control of the terminal device 310. Specifically, the display unit 1530 may include a touch screen 1531 set on the front of the terminal device 310, which can collect user touch operations on or near it, such as clicking a button, dragging a scroll box, etc.

[0199] The touch screen 1531 can be covered on the display screen 1532, or the touch screen 1531 and the display screen 1532 can be integrated to realize the input and output functions of the terminal device 310. The integrated touch screen can be simply called a touch display screen. In this application, the display unit 1530 can display applications and corresponding operation steps.

[0200] The camera 1540 can be used to capture still images, and users can post comments on the images captured by the camera 1540 through the application. There can be one or more cameras 1540. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transmitted to the processor 1580 for conversion into a digital image signal.

[0201] The terminal device may further include at least one sensor 1550, such as an acceleration sensor 1551, a distance sensor 1552, a fingerprint sensor 1553, and a temperature sensor 1554. The terminal device may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, a light sensor, and a motion sensor.

[0202] The audio circuit 1560, speaker 1561, and microphone 1562 provide an audio interface between the user and the terminal device 310. The audio circuit 1560 can convert the received audio data into an electrical signal and transmit it to the speaker 1561, which converts it into a sound signal for output. The terminal device 310 may also be equipped with a volume button for adjusting the volume of the sound signal. On the other hand, the microphone 1562 converts the collected sound signal into an electrical signal, which is received by the audio circuit 1560 and converted into audio data. The audio data is then output to the communication component 1510 for transmission to, for example, another terminal device 310, or the audio data is output to the memory 1520 for further processing.

[0203] The Bluetooth module 1570 is used to exchange information with other Bluetooth devices having a Bluetooth module through the Bluetooth protocol. For example, the terminal device can establish a Bluetooth connection with a wearable electronic device (such as a smart watch) that also has a Bluetooth module through the Bluetooth module 1570 to exchange data.

[0204] The processor 1580 is the control center of the terminal device. It uses various interfaces and lines to connect various parts of the entire terminal. By running or executing software programs stored in the memory 1520 and calling data stored in the memory 1520, it performs various functions of the terminal device and processes data. In some embodiments, the processor 1580 may include one or more processing units; the processor 1580 may also integrate an application processor and a baseband processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the baseband processor mainly processes wireless communications. It is understandable that the above-mentioned baseband processor may not be integrated into the processor 1580. In the present application, the processor 1580 can run the operating system, application programs, user interface display and touch response, as well as the information synchronization change method of the embodiment of the present application. In addition, the processor 1580 is coupled to the display unit 1530.

[0205] In some possible implementations, various aspects of the information synchronization change method provided in the present application may also be implemented in the form of a program product, which includes a computer program. When the program product is run on an electronic device, the computer program is used to enable the electronic device to execute the steps of the information synchronization change method according to various exemplary embodiments of the present application described above in this specification. For example, the electronic device may execute the following steps: Figure 4 Follow the steps shown in .

[0206] The program product can employ any combination of one or more computer-readable media. The computer-readable media can be a computer-readable storage medium or a computer-readable signal medium. The computer-readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0207] The program product of the embodiments of the present application can employ a compact disc read-only memory (CD-ROM) and include a computer program and can be run on a computing device. However, the program product of the present application is not limited thereto, and in the present document, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.

[0208] The computer-readable signal medium can include a computer-readable storage medium that is configured to store and deliver a computer program, and can propagate the computer program in a computer-readable storage medium. Such a propagated computer program can take many forms, including but not limited to, a magnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[0209] The computer program contained in the computer-readable medium can be transmitted by any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0210] The computer program for performing the operations of the present application can be written in any combination of one or more programming languages, including an object-oriented programming language such as Java, C++, etc., and a conventional procedural programming language such as the "C" language or a similar programming language. The computer program can be executed entirely on a user computing device, partially on a user device, as a separate software package, partially on a user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device by any kind of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, by connecting to an Internet service provider through the Internet).

[0211] It should be noted that although several units or subunits of the device are mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, depending on the embodiment of the application, the features and functions of two or more units described above can be embodied in a single unit. Conversely, the features and functions of a single unit described above can be further divided and embodied by multiple units.

[0212] Furthermore, although the operations of the method of the present application are described in a particular order in the accompanying drawings, this does not require or imply that the operations must be performed in this particular order, or that all illustrated operations must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0213] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain a computer-usable computer program.

[0214] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program commands. These computer program commands can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the commands executed by the processor of the computer or other programmable data processing device generate commands for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0215] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising a command device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0216] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0217] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present application.

[0218] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A method for synchronously changing information, characterized in that: The method includes: receiving a notification message triggered by a target change event, and obtaining a first flow identifier of the target change event from the notification message; the target change event indicates that business information of the target business has changed; If other historical change events are received before the target change event is received, the second serial number identifier of the last processed historical change event and the first serial number identifier are used to determine at least one target serial number identifier; if it is determined that no other historical change events are received before the target change event is received, the first serial number identifier is used as the target serial number identifier; Send an ID acquisition request carrying each target flow ID to the business server; Using the business identification information of the business related to the change event corresponding to each target flow identifier returned by the business server as the business identification information of at least one business to be processed, the business to be processed at least including the target business; Sending a change information acquisition request to a service server, wherein the change information acquisition request carries service identification information of the at least one service to be processed; Based on the business information of the at least one pending business change returned by the business server, information synchronization change is performed.

2. The method according to claim 1, wherein The determining of at least one target transaction identifier based on the second transaction identifier of the last processed historical change event and the first transaction identifier includes: If the value of the first flow identifier is adjacent to the value of the second flow identifier, the first flow identifier is used as the target flow identifier; If the value of the first flow identifier is not adjacent to the value of the second flow identifier, the first flow identifier and each intermediate flow identifier between the first flow identifier and the second flow identifier are used as the target flow identifier.

3. The method according to claim 1, wherein The values ​​of the flow identifiers are incremented in order of the corresponding change events; the method further includes: If it is determined that the value of the first flow identifier is not greater than the value of the second flow identifier, the information synchronization change is not processed.

4. The method according to any one of claims 1 to 3, wherein: The method further comprises: Determining, based at least on the first transaction identifier, a change type of at least one pending service whose service information has changed; The information synchronization change includes: Information synchronization changes are performed based on the change type corresponding to each of the at least one pending business and the corresponding changed business information.

5. A method for synchronously changing information, characterized in that: The method includes: Sending a notification message triggered by a target change event to a service management terminal, so that the service management terminal obtains a first flow identifier of the target change event from the notification message; the target change event indicates that service information of a target service has changed, and the services to be processed include at least the target service; receiving an identification acquisition request sent by the service management terminal, and determining service identification information of services related to change events corresponding to respective target flow identifications in the identification acquisition request; Using the service identification information determined based on each target flow identifier as identification information of the at least one service to be processed, and returning the information to the service management terminal; The target flow identifier is determined by the service management end. If the service management end receives other historical change events before receiving the target change event, the service management end determines at least one target flow identifier based on the second flow identifier of the last processed historical change event and the first flow identifier. If the service management end does not receive other historical change events before receiving the target change event, the service management end uses the first flow identifier as the target flow identifier. Receiving a change information acquisition request sent by the service management terminal, wherein the change information acquisition request carries service identification information of the at least one service to be processed; Return the service information of the at least one pending service change to the service management end, so that the service management end performs information synchronization changes.

6. The method according to claim 5, wherein The method further comprises: Every time a notification message triggered by a change event is received from a business client, the business identification information of the business whose business information has changed is stored and a serial identifier is generated. The value of the serial identifier increases in sequence according to the corresponding change event.

7. An information synchronization change device, characterized in that: include: a receiving unit, configured to receive a notification message triggered by a target change event, and obtain a first flow identifier of the target change event from the notification message; The target change event indicates that the business information of the target business has changed; A first determining unit is configured to determine at least one target transaction identifier based on the second transaction identifier of the last processed historical change event and the first transaction identifier if other historical change events are received before the target change event is received; If it is determined that no other historical change events have been received before the target change event is received, the first transaction identifier is used as the target transaction identifier; Send an ID acquisition request carrying each target flow ID to the business server; Using the business identification information of the business related to the change event corresponding to each target flow identifier returned by the business server as the business identification information of at least one business to be processed, the business to be processed at least including the target business; A sending unit, configured to send a change information acquisition request to a service server, wherein the change information acquisition request carries service identification information of the at least one service to be processed; The changing unit is configured to perform information synchronization changes based on the business information of the at least one pending business change returned by the business server.

8. The device according to claim 7, wherein The first determining unit is specifically configured to: If the value of the first flow identifier is adjacent to the value of the second flow identifier, the first flow identifier is used as the target flow identifier; If the value of the first flow identifier is not adjacent to the value of the second flow identifier, the first flow identifier and each intermediate flow identifier between the first flow identifier and the second flow identifier are used as the target flow identifier.

9. An information synchronization change device, characterized in that: include: a sending unit, configured to send a notification message triggered by a target change event to a service management terminal, so that the service management terminal obtains a first flow identifier of the target change event from the notification message; The target change event indicates that the business information of the target business has changed; A second receiving unit is used to receive the identification acquisition request sent by the business management end, determine the business identification information of the business related to the change event corresponding to each target flow identification in the identification acquisition request; use the business identification information determined based on each target flow identification as the identification information of at least one business to be processed, and return it to the business management end; wherein, the business to be processed includes at least the target business, and the target flow identification is determined by the business management end. If the business management end receives other historical change events before receiving the target change event, then at least one target flow identification is determined based on the second flow identification of the historical change event processed last and the first flow identification; if the business management end does not receive other historical change events before receiving the target change event, then the first flow identification is used as the target flow identification; A first receiving unit is configured to receive a change information acquisition request sent by the service management terminal, wherein the change information acquisition request carries service identification information of the at least one service to be processed; The returning unit is used to return the service information of the at least one pending service change to the service management end, so that the service management end can perform information synchronization changes.

10. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor is enabled to perform the steps of any one of the methods of claims 1 to 6.

11. A computer-readable storage medium, characterized in that The method comprises a computer program. When the computer program is run on an electronic device, the computer program is used to enable the electronic device to execute the steps of any one of the methods of claims 1 to 6.

12. A computer program product, characterized in that The method comprises a computer program stored in a computer-readable storage medium; when a processor of an electronic device reads the computer program from the computer-readable storage medium, the processor executes the computer program, so that the electronic device performs the steps of any one of the methods described in claims 1 to 6.

Images