A method, device, equipment and storage medium for synchronizing application registration information

Abstract

The present invention discloses a synchronization method, device, equipment and storage medium for application registration information. The application registration information of the user side is obtained in a specified manner, and the specified manner includes a data passive push method or a data active pull method; a communication protocol matching the registration information is obtained; and the registration information is transmitted to the application supplier side using the communication protocol, so that the application registration information is synchronized on the application supplier side. Synchronizing the application registration information by passive push or active data pull can meet the synchronization needs of all scenarios, realize diversified synchronization technology, and adopt a communication protocol matching the application registration information to transmit the obtained application registration information to the supplier side, meeting the synchronization needs of all scenarios and the needs of heterogeneous technology docking, and ensuring synchronization efficiency and accuracy.

Description

Technical Field

[0001] The present invention relates to the technical field of information synchronization, and in particular to a method, device, equipment and storage medium for synchronizing application registration information. Background Art

[0002] With the sharing of services between the Open Banking APIX and multiple suppliers, the intercommunication and synchronization methods of application registration information on the supplier side have become diversified, and the requirements for synchronization efficiency and accuracy of application registration information are becoming increasingly higher.

[0003] The existing technology relies on producers to agree on synchronization methods, synchronization protocols, synchronization frequencies and other conditions in advance through HTTP interface calls or message middleware transfer, and then completes registration information synchronization according to the agreed method.

[0004] The existing technology has a single technical means for completing registration information synchronization, and the synchronization efficiency is low and the accuracy is poor through the message middleware transfer method. Summary of the invention

[0005] The present invention provides a method, device, equipment and storage medium for synchronizing application registration information to solve the problem of heterogeneous technology full-scenario synchronization of application registration information.

[0006] According to one aspect of the present invention, a method for synchronizing application registration information is provided, comprising:

[0007] Acquire the application registration information on the user side in a specified manner, wherein the specified manner includes a passive data push manner or an active data pull manner;

[0008] Get the communication protocol that matches the application registration information;

[0009] The application registration information is transmitted to the application supplier side using a communication protocol, so that the application registration information is synchronized on the application supplier side.

[0010] According to another aspect of the present invention, there is provided a device for synchronizing application registration information, comprising:

[0011] An application registration information acquisition module is used to acquire the application registration information of the user side in a specified manner, wherein the specified manner includes a data passive push manner or a data active pull manner;

[0012] A communication protocol acquisition module is used to acquire a communication protocol that matches the application registration information;

[0013] The application registration information synchronization module is used to transmit the application registration information to the application supplier side using a communication protocol so that the application registration information is synchronized on the application supplier side.

[0014] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0015] at least one processor; and

[0016] a memory communicatively connected to the at least one processor; wherein,

[0017] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute a method for synchronizing application registration information described in any embodiment of the present invention.

[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement a method for synchronizing application registration information described in any embodiment of the present invention when executed.

[0019] The technical solution of the embodiment of the present invention can meet the synchronization needs of all scenarios by synchronizing application registration information through passive push or active data pulling, realizes diversified synchronization technology, and adopts a communication protocol matching the application registration information to transmit the acquired application registration information to the supplier side, thereby meeting the synchronization needs of all scenarios and the needs of heterogeneous technology docking, and ensuring synchronization efficiency and accuracy.

[0020] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0022] Figure 1 is a flowchart of a method for synchronizing application registration information provided according to Embodiment 1 of the present invention;

[0023] Figure 2 is a flowchart of a method for synchronizing application registration information provided according to Embodiment 1 of the present invention;

[0024] Figure 3 is a flowchart of a method for synchronizing application registration information provided according to Embodiment 2 of the present invention;

[0025] Figure 4 is a schematic diagram of the structure of a device for synchronizing application registration information provided according to Embodiment 3 of the present invention;

[0026] Figure 5 The present invention is a schematic diagram of the structure of an electronic device for implementing a method for synchronizing application registration information according to an embodiment of the present invention. DETAILED DESCRIPTION

[0027] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0029] Embodiment 1

[0030] Figure 1 A flowchart of a method for synchronizing application registration information is provided for the first embodiment of the present invention. This embodiment is applicable to situations where synchronization of application registration information is required. The method can be performed by a device for synchronizing application registration information. The device can be implemented in software and / or hardware and can generally be integrated in a computer device. Figure 1 As shown, the method includes:

[0031] S110: Acquire application registration information on the user side in a specified manner.

[0032] Specifically, the user side refers to users who subscribe to applications produced by suppliers through the APIX open exchange platform, including portal platform users and management platform users. The portal platform is the user end of the APIX open exchange platform, and the management platform is the background management end of the APIX open exchange platform. Users will generate application registration information in the process of subscribing or using applications. For example, users will generate application registration information when operating system parameters, applications, and device drivers. The APIX open exchange platform can obtain the application registration information on the user side through a specified method. The application registration information includes: application APP (Application, APP) registration information and application programming interface API (Application Programming Interface, API) registration information. The specified method in this embodiment may include a passive data push method or an active data pull method. Passive data push means that when the application registration information on the user side changes, the changed application registration information will be pushed to the application supplier side through the APIX open exchange platform. The active data pull method means that the application supplier side can also actively query the application registration information from the user side through the APIX open exchange platform.

[0033] Among them, the APP registration information can be the APP unique identifier, APP status, APP whitelist, APP whitelist status and APP name, etc., and the API registration information can be the API name, API banned list, API subscription status and API review status, etc.

[0034] This embodiment mainly describes the synchronization method of application registration information in the passive data push mode. Figure 2 A flowchart of a method for synchronizing application registration information is provided in an embodiment of the present invention. Figure 2 When the designated mode is a passive data push mode, step S110 mainly includes the following steps S111 to S112:

[0035] S111 . Monitor the application registration message queue through a message monitoring unit of the application registration center.

[0036] Among them, the application registration information on the user side is mainly stored in the application information table. The following Table 1 is a schematic diagram of the application information table on the user side:

[0037] Table 1

[0038]

[0039]

[0040] The application information table includes both APP registration information and API registration information. Different types of application registration information have corresponding data types and application registration information metadata in the application registration information table. For example, when the type of application registration information is APP unique identifier, the corresponding data type is String, and the application registration information metadata is app_config.clientId. Due to space limitations, this implementation only provides an example of the application registration information table.

[0041] It should be noted that when the portal platform user or the management platform user operates the subscribed application, the registration information in Table 1 will change, and there are many scenarios that cause the registration information in Table 1 to change. The following Table 2 shows the scenarios that cause the application information table to change:

[0042] Table 2

[0043]

[0044]

[0045] Among them, the APIX open exchange platform updates application registration information mainly into updates of the user operation portal platform and updates of the user operation management platform. Updates to application registration information include updates to APP registration information and updates to API registration information. After the user executes the operations in Table 2, the corresponding application registration information will change. For example, if the user executes the APP rename operation on the portal platform, the APP registration information will change and generate updated application registration information.

[0046] When the APIX open exchange platform detects that the application registration information metadata or application registration information in Table 1 has changed, the changed application registration information will be sent to the application registration message queue, for example, the Kafka message queue, and the API registration information and the APP registration information will be sorted separately in the Kafka message queue. The message monitoring unit monitors the application registration message queue.

[0047] S112: When it is determined according to the monitoring result that the application registration message queue contains updated application registration information, the updated application registration information is extracted from the application registration message queue.

[0048] Specifically, the APIX open exchange platform receives the monitoring result, which refers to the result generated by the APIX open exchange platform after monitoring the API registration message queue or the APP registration message queue. The monitoring result includes the situation where the application registration message queue is monitored and the application registration message queue is not monitored. When the application registration message queue is monitored, the APIX open exchange platform will extract and update the application registration information from the application registration message queue. When the application registration message queue is not monitored, the APIX open exchange platform will not extract and update the application registration information.

[0049] S120: Acquire a communication protocol that matches the application registration information.

[0050] Specifically, the communication protocol refers to the protocol for communication between devices. It refers to the rules and agreements that the communicating parties must follow to complete communication or services. Different communication protocols have different performance, data rate, coverage, power and memory. When application registration information is transmitted, different communication protocols will be selected due to different types and contents.

[0051] Preferably, the designated method includes a passive data push method to obtain a communication protocol that matches the registration information, including: identifying the application registration information to obtain the type of the application registration information; obtaining a pre-stored application scenario configuration file, the application scenario configuration file containing a correspondence between the type of application registration information and the communication protocol; querying the application scenario configuration file according to the type of application registration information to obtain a communication protocol that matches the application registration information.

[0052] Specifically, the APIX open exchange platform will identify the application registration information and obtain the type of application registration information; then obtain the pre-stored application scenario configuration file. The application scenario configuration file is set in advance by the user in the APIX open exchange platform, which contains the correspondence between the type of application registration information and the communication protocol. The APIX open exchange platform can determine the communication protocol corresponding to different types of application registration information through the application scenario configuration file, where the communication protocol includes the full-duplex communication protocol WebSocket, the reverse application programming interface protocol WebHooks or the Hypertext Transfer Protocol (HTTP).

[0053] Among them, the full-duplex communication protocol WebSocket refers to the full-duplex communication standard between the Web browser and the Web server. The server can actively push information to the client, and the client can also actively send information to the server. The reverse application programming interface protocol WebHooks refers to a protocol in which the client does not actively send requests and is completely pushed by the server. It is mainly used to provide updated and specified data when resources are newly created or updated. HTTP is the basis for data exchange on the Web. It is a "client-server" protocol that is mainly used for data transmission that does not require high data confidentiality.

[0054] S130. Transmit the application registration information to the application supplier side using a communication protocol, so that the application registration information is synchronized on the application supplier side.

[0055] Specifically, the application supplier side refers to the producer of the application. When the APIX open exchange platform queries the communication protocol that matches the application registration information through the application scenario configuration file, it will use the communication protocol to transmit it to the application supplier side. For example, the APIX open exchange platform queries the application scenario configuration file and finds that the communication protocol corresponding to the APP registration information A is HTTP. Then the APIX open exchange platform will transmit the APP registration information A to the application supplier side using HTTP.

[0056] Preferably, the application registration information is transmitted to the application supplier side using a communication protocol, including: encrypting the application registration information according to an encryption algorithm configured on the application supplier side to obtain the encrypted application registration information; and transmitting the encrypted application registration information to the application supplier side.

[0057] Specifically, in order to ensure the security of APIX open exchange platform in transmitting application registration information, APIX open exchange platform supports differentiated encryption methods, which can convert plain text into ciphertext after encryption. According to the encryption algorithm configured on the application supplier side, the encryption algorithm can be configured to different encryption functions to encrypt the application registration information on demand, and the encrypted application registration information can be transmitted to the application supplier side.

[0058] The technical solution of the embodiment of the present invention can meet the synchronization needs of all scenarios by synchronizing application registration information in a passive push manner, realizes diversified synchronization technology, and adopts a communication protocol matching the application registration information to transmit the acquired application registration information to the supplier side, thereby meeting the synchronization needs of all scenarios and the needs of heterogeneous technology docking, and ensuring synchronization efficiency and accuracy.

[0059] Embodiment 2

[0060] Figure 3This is a flowchart of a method for synchronizing application registration information provided by Embodiment 2 of the present invention. Based on the above embodiments, this embodiment mainly describes in detail the synchronization method of application registration information in the data active pull mode. Figure 3 As shown, the method includes:

[0061] S210: Receive an application registration information query request through the application registration center based on a communication protocol specified by the supplier, where the application registration information query request includes the type of application registration information.

[0062] Specifically, the APIX open exchange platform can receive an application registration information query request, which includes the type of application registration information, that is, the type of application registration information can be queried through the application registration information query request. Since the supplier side knows the communication protocol adapted to the type of application registration information being queried, when sending a query request to the APIX open exchange platform through the terminal, the communication protocol will be specified on the terminal, and the specified communication protocol will be used to interact with the APIX open exchange platform. Among them, the communication protocol includes HTTP or Remote Progress Call (RPC), which is a protocol that requests services from a remote computer program over the network without the need to understand the underlying network technology.

[0063] S220: Search the application registration information table on the user side according to the type to obtain application registration information matching the type.

[0064] Specifically, the APIX open exchange platform queries the application registration information table on the user side according to the type, that is, by querying the above Table 1, the application registration information matching the type can be obtained; for example, when the type of the application registration information is a subscription user mailbox, the matching application registration information that can be obtained by querying Table 1 is app_config.userEmail. Of course, this implementation only illustrates the query of the registration information corresponding to the subscription user mailbox as an example. In actual applications, the specified APP registration information, specified API registration information, all APP registration information, all API registration information, etc. of the application supplier can also be queried. This implementation does not limit the specific content of the registration information queried on the supplier side.

[0065] S230, obtaining a communication protocol that matches the application registration information

[0066] Preferably, in the active data pulling mode, obtaining the communication protocol that matches the application registration information includes: determining the communication protocol specified by the supplier side; and using the communication protocol specified by the supplier side as the communication protocol that matches the application registration information.

[0067] Specifically, after obtaining the application registration information required by the supplier side through query, it is necessary to obtain the communication protocol that matches the application registration information in order to accurately feed back the application registration information to the supplier side. Since the supplier side has specified the communication protocol when sending a query request to the APIX open exchange platform, and the communication protocol specified by the user can accurately feed back the application registration information to the supplier side, the APIX open exchange platform will use the communication protocol specified by the supplier side as the communication protocol that matches the application registration information.

[0068] S240: Transmit the application registration information to the application supplier side using a communication protocol, so that the application registration information is synchronized on the application supplier side.

[0069] Exemplarily, the APIX open exchange platform obtains that the communication protocol specified by the supplier side is RPC. When receiving an application registration information query request, it is found in Table 1 that the application registration information type is API subscription and the application registration information metadata is api_config.scribe. The application registration information will be transmitted to the application supplier side using RPC to synchronize the application registration information on the application supplier side.

[0070] The technical solution of the embodiment of the present invention can meet the synchronization needs of all scenarios by synchronizing application registration information through active data pulling, realizes diversified synchronization technology, and adopts a communication protocol matching the application registration information to transmit the acquired application registration information to the supplier side, thereby meeting the synchronization needs of all scenarios and the needs of heterogeneous technology docking, and ensuring synchronization efficiency and accuracy.

[0071] Embodiment 3

[0072] Figure 4 This is a schematic diagram of the structure of a synchronization device for application registration information provided by Embodiment 3 of the present invention. Figure 4 As shown, the device includes: an application registration information acquisition module 310, which is used to obtain the application registration information of the user side in a specified manner, and the specified manner includes a data passive push method or a data active pull method; a communication protocol acquisition module 320, which is used to obtain a communication protocol matching the application registration information; an application registration information synchronization module 330, which is used to transmit the application registration information to the application supplier side using the communication protocol, so that the application registration information is synchronized on the application supplier side.

[0073] Preferably, the designated method includes a passive data push method, and the application registration information acquisition module 310 is specifically used to: monitor the application registration message queue through the message monitoring unit of the application registration center, wherein the application registration message queue is used to save the updated application registration information that has changed in the application registration information table on the user side; when it is determined according to the monitoring result that the application registration message queue contains updated application registration information, the updated application registration information is extracted from the application registration message queue.

[0074] Preferably, the designated method includes a passive data push method, and the communication protocol acquisition module 320 is specifically used to: identify the application registration information to obtain the type of the application registration information; obtain a pre-stored application scenario configuration file, the application scenario configuration file contains the correspondence between the type of application registration information and the communication protocol; query from the application scenario configuration file according to the type of application registration information to obtain a communication protocol that matches the application registration information, wherein the communication protocol includes a full-duplex communication protocol WebSocket, WebHooks or a hypertext transfer protocol HTTP.

[0075] Preferably, the designated method includes an active data pulling method, and the application registration information acquisition module 310 is specifically used to: receive an application registration information query request through an application registration center based on a communication protocol specified by the supplier side, wherein the application registration information query request includes the type of application registration information; query from the application registration information table on the user side according to the type, and obtain application registration information that matches the type.

[0076] Preferably, the designated method includes an active data pulling method, and the communication protocol acquisition module 320 is specifically used to: determine the communication protocol specified by the supplier side; use the communication protocol specified by the supplier side as the communication protocol matching the registration information, wherein the communication protocol includes the Hypertext Transfer Protocol HTTP or the Remote Procedure Call RPC protocol.

[0077] Preferably, the application registration information synchronization module 330 is specifically used to: encrypt the application registration information according to the encryption algorithm configured on the application supplier side, obtain the encrypted application registration information; and transmit the encrypted application registration information to the application supplier side.

[0078] The technical solution of the embodiment of the present invention can meet the synchronization needs of all scenarios by synchronizing application registration information through passive push or active data pulling, realizes diversified synchronization technology, and adopts a communication protocol matching the application registration information to transmit the acquired application registration information to the supplier side, thereby meeting the synchronization needs of all scenarios and the needs of heterogeneous technology docking, and ensuring synchronization efficiency and accuracy.

[0079] An application registration information synchronization device provided in an embodiment of the present invention can execute an application registration information synchronization method provided in any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0080] Embodiment 4

[0081] Figure 5 A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0082] like Figure 5 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0083] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0084] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a synchronization method for application registration information.

[0085] In some embodiments, the method for synchronizing application registration information may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the method for synchronizing application registration information described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the method for synchronizing application registration information in any other appropriate manner (e.g., by means of firmware).

[0086] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0087] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0088] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0089] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0090] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0091] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0092] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0093] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for synchronizing application registration information, characterized in that: include: The application registration information on the user side is obtained in a specified manner, the specified manner including a passive data push manner or an active data pull manner, wherein the application registration information is generated in the process of user subscription or use of the application, the application registration information includes application program APP registration information and application programming interface API registration information, the user side refers to the user who subscribes to the application produced by the supplier, the passive data push manner means that when the application registration information on the user side changes, the changed application registration information will be pushed to the application supplier side, and the active data pull manner means that the application supplier side actively queries the user side for application registration information; Acquire a communication protocol that matches the application registration information, wherein the communication protocol that matches the application registration information is preset by a user; The application registration information is transmitted to the application supplier side using the communication protocol, so that the application registration information is synchronized on the application supplier side, where the application supplier side refers to the producer of the application.

2. The method according to claim 1, characterized in that The specified method includes a data passive push method, and the specified method is used to obtain application registration information, including: The application registration message queue is monitored by a message monitoring unit of the application registration center, wherein the application registration message queue is used to store updated application registration information that has changed in the application registration information table on the user side; When it is determined according to the monitoring result that the application registration message queue contains updated application registration information, the updated application registration information is extracted from the application registration message queue.

3. The method according to claim 1, characterized in that The specified method includes an active data pulling method, and the specified method is used to obtain application registration information, including: receiving, by the application registration center, an application registration information query request based on a communication protocol specified by the supplier side, wherein the application registration information query request includes a type of application registration information; According to the type, a query is performed from the application registration information table on the user side to obtain application registration information matching the type.

4. The method according to claim 2, characterized in that: The obtaining of a communication protocol matching the application registration information includes: Identify the application registration information to obtain the type of the application registration information; Obtaining a pre-stored application scenario configuration file, wherein the application scenario configuration file includes a correspondence between a type of application registration information and a communication protocol; According to the type of the application registration information, a query is performed from the application scenario configuration file to obtain a communication protocol matching the application registration information, wherein the communication protocol includes a full-duplex communication protocol WebSocket, a reverse application programming interface protocol WebHooks or a hypertext transfer protocol HTTP.

5. The method according to claim 3, characterized in that: The obtaining of a communication protocol matching the application registration information includes: Determining a communication protocol specified by the supplier side; The communication protocol specified by the supplier side is used as the communication protocol matching the application registration information, wherein the communication protocol includes the Hypertext Transfer Protocol HTTP or the Remote Procedure Call RPC protocol.

6. The method according to claim 1, characterized in that The step of transmitting the application registration information to the application provider side using the communication protocol includes: Encrypting the application registration information according to the encryption algorithm configured on the application supplier side, and obtaining the encrypted application registration information; The encrypted registration information is transmitted to the application provider.

7. A device for synchronizing application registration information, characterized in that: include: An application registration information acquisition module is used to acquire the application registration information of the user side in a specified manner, wherein the specified manner includes a data passive push manner or a data active pull manner, wherein the application registration information is generated in the process of a user subscribing to or using an application, and the application registration information includes an application program APP registration information and an application programming interface API registration information, wherein the user side refers to a user who subscribes to an application produced by a supplier, wherein the data passive push manner refers to when the application registration information of the user side changes, the changed application registration information will be pushed to the application supplier side, and wherein the data active pull manner refers to the application supplier side actively querying the user side for application registration information; A communication protocol acquisition module, used to acquire a communication protocol matching the application registration information, wherein the communication protocol matching the application registration information is preset by a user; The application registration information synchronization module is used to transmit the application registration information to the application supplier side using the communication protocol so that the application registration information is synchronized on the application supplier side, and the application supplier side refers to the producer of the application.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can perform the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method according to any one of claims 1 to 6 when executed.

Images