CN117041044A - Gateway configuration method, device and system - Google Patents

Abstract

The application relates to a gateway configuration method, device and system. The method comprises the following steps: loading first configuration data by calling an interface of a first configuration center, wherein the first configuration center represents a configuration center matched with a first configuration mode, and the first configuration mode represents a configuration mode used by the gateway engine; under the condition of successfully loading the first configuration data, constructing a first configuration object based on the first configuration data, and placing the first configuration object into a cache management queue for processing; and in the process of processing the cache management queue, when the first configuration object is acquired from the cache management queue, updating the first configuration data into a gateway cache to configure the gateway. By adopting the method, the reliability of gateway configuration can be improved.

Description

Gateway configuration method, device and system

Technical Field

The present application relates to the field of network technologies, and in particular, to a gateway configuration method, device, and system.

Background

The gateway, as a channel for providing network services for operators, digital content providers and network equipment manufacturers, can provide a plurality of network operations and services such as bandwidth data, voice, video, network security, energy management, health monitoring and the like.

In the conventional technology, configuration data of a gateway is stored in a database, and dynamic update of the database depends on a monitoring mechanism of middleware such as a nano or a zookeeper. When a corresponding table is added in the database for storing configuration data, the corresponding record is issued to a configuration center of the Nacos or a zookeeper node through database updating operation, and the gateway engine monitors the Nacos or the zookeeper to realize dynamic updating of the configuration data.

However, if the listening middleware fails in the method, the configuration data cannot be updated dynamically, and the reliability is poor.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a gateway configuration method, apparatus, and system that can improve reliability.

In a first aspect, the present application provides a gateway configuration method, the method being applied to a gateway engine, the method comprising:

loading first configuration data by calling an interface of a first configuration center, wherein the first configuration center represents a configuration center matched with a first configuration mode, and the first configuration mode represents a configuration mode used by the gateway engine;

under the condition of successfully loading the first configuration data, constructing a first configuration object based on the first configuration data, and placing the first configuration object into a cache management queue for processing;

And in the process of processing the cache management queue, when the first configuration object is acquired from the cache management queue, updating the first configuration data into a cache of a gateway to configure the gateway.

In one possible implementation, the method further includes:

determining whether a local configuration file exists;

loading second configuration data from the local configuration file in the presence of the local configuration file;

and under the condition of successfully loading the second configuration data, constructing a second configuration object based on the second configuration data, and placing the second configuration object into the cache management queue for processing.

In one possible implementation manner, the loading the first configuration data by calling the interface of the first configuration center includes:

loading the first configuration data by calling an interface of the first configuration center under the condition that the local configuration file does not exist;

or,

and loading the first configuration data by calling an interface of the first configuration center under the condition that the local configuration file exists and the second configuration data is not loaded successfully.

In one possible implementation, the method further includes:

and under the condition that the first configuration data is not loaded successfully, constructing a first failure event based on the first configuration data, and adding the first failure event into a delay queue for processing.

In one possible implementation, the method further includes:

when the time length of the first failure event entering the delay queue is greater than a first threshold value, acquiring the first failure event from the delay queue;

loading the first configuration data from the first configuration center again according to a configuration class of the first failure event when the retry number of the first failure event is smaller than a second threshold value, wherein the configuration class is used for indicating the type of a configuration model adopted by the first configuration data;

if the reloading is successful, constructing the first configuration object based on the first configuration data, and putting the first configuration object into the cache management queue for processing;

and if the reloading fails, adding the retry times of the first failure event into the delay queue for processing.

In one possible implementation manner, the placing the first configuration object into a cache management queue for processing includes:

Determining whether a third configuration object exists in the cache management queue, wherein the third configuration object is used for representing a configuration object which is the same as a configuration center and a configuration class corresponding to the first configuration object, the configuration class is used for indicating the type of a configuration model, and the configuration model is used for indicating the storage format of configuration data;

if the third configuration object exists and the version number of the first configuration object is larger than the version number of the third configuration object, the first configuration object is placed into the cache queue for processing;

or,

and if the third configuration object does not exist, the first configuration object is put into the cache queue for processing.

In one possible implementation, the method further includes:

if the first configuration data is not successfully updated to the cache and the retry number of the first configuration object is smaller than a third threshold value, the retry number of the first configuration object is added by one and then is put into the cache management queue again for processing.

In one possible implementation, the method further includes:

initializing the first configuration center, and adding a configuration change monitor to each configuration class of the first configuration center, wherein the configuration class is used for indicating the type of a configuration model, and the configuration model is used for indicating the storage format of configuration data;

Subscribing to an event bus;

and when a fourth configuration object is received from the event bus, placing the fourth configuration object into the cache management queue for processing, wherein the fourth configuration object is issued to the event bus by the configuration change monitor and is generated according to the configuration data updated in the first configuration center.

In a second aspect, the application further provides a gateway configuration device. The apparatus is applied to a gateway engine. The device comprises:

the loading module is used for loading first configuration data by calling an interface of a first configuration center, wherein the first configuration center represents a configuration center matched with a first configuration mode, and the first configuration mode represents a configuration mode used by the gateway engine;

the construction module is used for constructing a first configuration object based on the first configuration data under the condition of successfully loading the first configuration data, and placing the first configuration object into a cache management queue for processing;

and the updating module is used for updating the first configuration data into a cache of a gateway when the first configuration object is acquired from the cache management queue in the process of processing the cache management queue so as to configure the gateway.

In one possible implementation, the apparatus further includes:

the determining module is used for determining whether a local configuration file exists;

the loading module is further configured to load second configuration data from the local configuration file if the local configuration file exists; and under the condition of successfully loading the second configuration data, constructing a second configuration object based on the second configuration data, and placing the second configuration object into the cache management queue for processing.

In one possible implementation, the loading module is further configured to:

loading the first configuration data by calling an interface of the first configuration center under the condition that the local configuration file does not exist;

or,

and loading the first configuration data by calling an interface of the first configuration center under the condition that the local configuration file exists and the second configuration data is not loaded successfully.

In one possible implementation, the building module is further configured to:

and under the condition that the first configuration data is not loaded successfully, constructing a first failure event based on the first configuration data, and adding the first failure event into a delay queue for processing.

In one possible implementation, the apparatus further includes: the device comprises an acquisition module and a first adding module;

the acquisition module is used for acquiring the first failure event from the delay queue when the duration of the first failure event entering the delay queue is greater than a first threshold value;

the loading module is further configured to, when the retry number of the first failure event is less than a second threshold, reload the first configuration data from the first configuration center according to a configuration class of the first failure event, where the configuration class is used to indicate a type of a configuration model adopted by the first configuration data;

the construction module is further configured to construct the first configuration object based on the first configuration data if reloading is successful, and put the first configuration object into the cache management queue for processing;

and the first adding module is used for adding the retry times of the first failure event into the delay queue for processing if the reloading fails.

In one possible implementation manner, the placing the first configuration object into a cache management queue for processing includes:

Determining whether a third configuration object exists in the cache management queue, wherein the third configuration object is used for representing a configuration object which is the same as a configuration center and a configuration class corresponding to the first configuration object, the configuration class is used for indicating the type of a configuration model, and the configuration model is used for indicating the storage format of configuration data;

if the third configuration object exists and the version number of the first configuration object is larger than the version number of the third configuration object, the first configuration object is placed into the cache queue for processing;

or,

and if the third configuration object does not exist, the first configuration object is put into the cache queue for processing.

In one possible implementation, the apparatus further includes: a second adding module;

and if the first configuration data is not successfully updated to the cache and the retry number of the first configuration object is smaller than a third threshold value, the second adding module adds one to the retry number of the first configuration object and then re-puts the first configuration object into the cache management queue for processing.

In one possible implementation, the apparatus further includes:

the initialization module is used for initializing the first configuration center, adding a configuration change monitor to each configuration class of the first configuration center, wherein the configuration class is used for indicating the type of a configuration model, and the configuration model is used for indicating the storage format of configuration data;

The subscription module is used for subscribing the event bus;

and the third adding module is used for placing a fourth configuration object into the cache management queue for processing under the condition that the fourth configuration object is received from the event bus, wherein the fourth configuration object is issued to the event bus by the configuration change monitor and is generated according to the configuration data updated in the first configuration center.

In a third aspect, the present application also provides a gateway configuration system, where the system includes a gateway management and control end, a configuration center, and a gateway engine;

the gateway control end is used for receiving control data, wherein the control data is used for configuring the gateway and comprises data required by configuring the gateway and a corresponding configuration mode; assembling the management and control data into configuration data according to a configuration model, wherein the configuration model is used for indicating a storage format of the configuration data; storing the configuration data, the configuration class and the version number in a configuration center corresponding to the configuration mode in an associated mode, wherein the configuration class is used for indicating the type of the configuration model;

the configuration centers are used for storing configuration data, configuration classes and version numbers in an associated mode, and each configuration center corresponds to a unique configuration mode;

The gateway engine is configured to perform the gateway configuration method of the first aspect or any one of the possible implementation manners of the first aspect.

In a fourth aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor which when executing the computer program performs the steps of:

loading first configuration data by calling an interface of a first configuration center, wherein the first configuration center represents a configuration center matched with a first configuration mode, and the first configuration mode represents a configuration mode used by the gateway engine;

under the condition of successfully loading the first configuration data, constructing a first configuration object based on the first configuration data, and placing the first configuration object into a cache management queue for processing;

and in the process of processing the cache management queue, when the first configuration object is acquired from the cache management queue, updating the first configuration data into a cache.

In a fifth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:

Loading first configuration data by calling an interface of a first configuration center, wherein the first configuration center represents a configuration center matched with a first configuration mode, and the first configuration mode represents a configuration mode used by the gateway engine;

under the condition of successfully loading the first configuration data, constructing a first configuration object based on the first configuration data, and placing the first configuration object into a cache management queue for processing;

and in the process of processing the cache management queue, when the first configuration object is acquired from the cache management queue, updating the first configuration data into a cache.

In a sixth aspect, the application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of:

loading first configuration data by calling an interface of a first configuration center, wherein the first configuration center represents a configuration center matched with a first configuration mode, and the first configuration mode represents a configuration mode used by the gateway engine;

under the condition of successfully loading the first configuration data, constructing a first configuration object based on the first configuration data, and placing the first configuration object into a cache management queue for processing;

And in the process of processing the cache management queue, when the first configuration object is acquired from the cache management queue, updating the first configuration data into a cache.

According to the gateway configuration method, the gateway configuration device and the gateway configuration system, the configuration data are stored in the configuration centers with different configuration modes, the configuration centers have high reliability, the gateway engine can load the configuration data from the configuration centers through the corresponding interfaces according to the used configuration modes, and update the configuration data into the cache, so that the configuration data meeting the service requirements of the gateway are obtained in real time under the condition of omitting the monitoring middleware, and the reliability is improved.

Drawings

Fig. 1 is a schematic architecture diagram of a gateway configuration system according to an embodiment of the present application;

FIG. 2 is an exemplary schematic diagram of a configuration center provided by an embodiment of the present application;

fig. 3 is an interaction schematic diagram of a gateway configuration method according to an embodiment of the present application;

fig. 4 is a flow chart of a gateway configuration method according to an embodiment of the present application;

fig. 5 is a flow chart of a gateway configuration method according to an embodiment of the present application;

fig. 6 is a flow chart of a gateway configuration method according to an embodiment of the present application;

fig. 7 is a flow chart of a gateway configuration method according to an embodiment of the present application;

Fig. 8 is a flow chart of a gateway configuration method according to an embodiment of the present application;

FIG. 9 is a block diagram of a configuration device according to an embodiment of the present application;

fig. 10 is an internal structural view of a computer device in one embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

Fig. 1 is a schematic diagram of a gateway configuration system according to an embodiment of the present application. As shown in fig. 1, the gateway configuration system includes a gateway management end, a configuration center and a gateway engine. The configuration center can be used for storing configuration data, and the gateway management and control end can store the configuration data to the configuration center. The gateway engine is used with configuration data that can be loaded from the configuration center.

As shown in fig. 1, the terminal may communicate with the gateway management and control end through a network. And the user can send the control data to the gateway control end through the terminal. The management and control data can be used for configuring the gateway, and the management and control data can comprise data required for configuring the gateway and a corresponding configuration mode. The terminal may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and the like.

The gateway management and control terminal can be used for receiving management and control data, assembling the management and control data into configuration data according to a configuration model, and storing the configuration data, the configuration class and the version number in a configuration center corresponding to the configuration model in an associated mode. The gateway management and control end can be realized by an independent server or a server cluster formed by a plurality of servers.

Wherein the configuration model may be used to indicate a storage format of the configuration data. In the embodiment of the present application, a configuration model may be predefined. In one example, the configuration model may include one or more of a communication container, an application program interface (Application Programming Interface, API), application information, current limits, fusing, retry, black and white list, and baffles, among others. There may be a plurality of predefined configuration models. The fields included by these configuration models may be different. Each configuration model is assigned a configuration class that can be used to identify a unique configuration model. That is, a configuration model may be determined based on a configuration class. These configuration models uniformly implement gateway basic configuration (gateway baseconfig) interfaces, which define the configuration classes described above.

The configuration centers may be used to store configuration data, configuration classes, and version numbers in association, with each configuration center corresponding to a unique configuration schema. The gateway management and control end can be connected with a plurality of configuration centers. Different configuration centers correspond to different configuration modes. For example, the configuration centers may include an Apollo configuration center (Apoll Config Repository), a Nacos configuration center (Nacos Config Repository), a file system configuration center (File System Config Repository), and the like. The user may specify a configuration mode in the management data. After the gateway management and control terminal receives the management and control data, on one hand, the gateway management and control terminal can assemble the data carried in the management and control data according to the configuration model to obtain the configuration data, and on the other hand, the gateway management and control terminal can acquire the configuration mode from the management and control data, so that the configuration data can be stored in a configuration center corresponding to the configuration mode.

In order to facilitate the use of the configuration data, the configuration class corresponding to the stored configuration data is also associated when the configuration data is stored. To enable version management, changes between recorded versions or rollbacks to historical versions may also be associated with a storage version number when storing configuration data. In one example, a timestamp of the generation of the configuration data may be used as the version number to which the configuration data corresponds. Thus, the configuration data, the configuration class and the version number are stored in the configuration center corresponding to the configuration mode in an associated manner.

In the embodiment of the application, the configuration data is managed in a centralized way through the configuration center, and the configuration data is managed and updated through the gateway management and control end, so that the maintainability and the expandability of the configuration data are improved.

Fig. 2 is an exemplary schematic diagram of a configuration center provided in an embodiment of the present application. As shown in fig. 2, first, a configuration center interface is defined. The Apollo configuration center interface, the Nacos configuration center interface, the file system configuration center interface and the like are then integrated in the configuration center interface in a plug-in manner. Of course, the above integrated configuration center interfaces are only exemplary, and other configuration mode configuration center interfaces may be integrated. Next, a configuration center loader is defined. The plug-in defined above is loaded by the configuration center loader, and the implementation of the plug-in may be a service provisioning interface (Service Provider Interface, SPI) or an automatic assembly (springboot). The configuration center loader then registers the loaded configuration center in a configuration center registry. It can be seen that the configuration center registry may indicate all loaded configuration centers. In one example, the configuration center registry may include an interface and configuration schema for the loaded configuration center. In this way, after determining the configuration mode corresponding to the configuration data, the gateway management and control end can search the interface corresponding to the configuration mode from the configuration center registry, so that the configuration data, the configuration class and the version number are associated and stored in the configuration center through the searched interface.

In one possible implementation, as shown in fig. 1, the gateway configuration system may further include a database. The gateway management and control end is also used for storing the configuration data, the configuration class, the version number and the configuration mode in the database in an associated mode.

In the embodiment of the application, the configuration data, the configuration class, the version number and the configuration mode association are stored in the database, so that the configuration data can be backed up, and the reliability is improved.

Optionally, the database may also record status information of the management and control data. When the configuration data corresponding to the management and control data is successfully stored in the corresponding configuration center, the gateway management and control end can modify the state information of the management and control data in the database to be published. Therefore, the manageability of the configuration data can be improved, and the user can find the configuration data conveniently.

Fig. 3 is an interaction schematic diagram of a gateway configuration method according to an embodiment of the present application. The method can be applied to the gateway configuration system shown in fig. 1. As shown in fig. 3, the method may include:

in step S301, the terminal issues management and control data to the gateway management and control terminal.

In step S302, the gateway control terminal receives the control data.

Step S303, the gateway control terminal assembles the control data into configuration data according to a configuration model.

In step S304, the gateway management and control end stores the configuration data, the configuration class, the version number and the configuration mode association in the database.

In step S305, the gateway management and control end stores the configuration data, the configuration class and the version number in association with the configuration center corresponding to the configuration mode.

In step S306, the gateway management and control end modifies the status information of the management and control data in the database to published status information.

Step S307, the gateway control terminal determines whether the configuration center is successfully stored in the corresponding configuration center; if yes, go to step S308, otherwise go to step S309.

Step S308, the gateway control end returns a prompt message for indicating successful release to the terminal.

Step S309, the gateway control end returns a prompt message for indicating the release failure to the terminal.

After receiving the prompt message for indicating the release failure, the terminal can release the control data again until the retransmission times exceed a certain threshold value, and then notify the user.

In the embodiment of the application, the configuration data is stored in the configuration center through the gateway control end, so that unified management of the configuration data is realized, decentralized storage and management are avoided, and maintainability and expandability of the configuration data are improved. Meanwhile, the configuration center is provided with a high availability mechanism, such as a Nacos configuration center supporting functions of registration, discovery, state synchronization and the like of the distributed nodes, so that high availability and reliability of the configuration center are ensured. In addition, the configuration center can be increased or decreased according to the service requirement, so that the expandability is further improved. In addition, version numbers are stored in a correlated mode when configuration data are stored, changes among historical versions are reflected, and version management and version rollback are facilitated.

The storage of the configuration data in the configuration center is completed, and a process of reading the configuration data from the configuration center by the gateway engine will be described. In one embodiment, fig. 4 is a flowchart of a gateway configuration method according to an embodiment of the present application. As shown in fig. 4, taking an example that the method is applied to the gateway engine shown in fig. 1, the gateway configuration method may include:

step S401, loading the first configuration data by calling the interface of the first configuration center.

Wherein the first configuration data may represent configuration data loaded by invoking an interface of the first configuration center. The first configuration center may represent a configuration center that matches a first configuration pattern. The first configuration mode may represent a configuration mode used by the gateway engine.

The gateway engine can be set to be used in different configuration modes according to application requirements. The gateway engine may find the interface of the first configuration center in the configuration center registry according to the currently used configuration mode and then load the first configuration data by calling the interface of the first configuration center.

Step S402, under the condition of successfully loading the first configuration data, constructing a first configuration object based on the first configuration data, and placing the first configuration object into a cache management queue for processing.

Wherein the first configuration object may represent a configuration object (event) generated based on the first configuration object. The cache management queue may be used to update the gateway's cache. A plurality of configuration objects may be included in the cache management queue. The first configuration object may be placed in a cache management queue for storage. The process of placing the first configuration object into the cache management queue by the gateway engine will be described in detail later, and will not be described herein.

Step S403, in the process of processing the cache management queue, when the first configuration object is obtained from the cache management queue, updating the first configuration data into a cache of a gateway to configure the gateway.

Multiple configuration objects may be included in the cache management queue. The gateway engine can sequentially acquire the configuration objects from the cache management queue for processing. In one example, the gateway engine may sequentially obtain configuration objects from the cache management queue for processing in a first-to-last order into the cache management queue. Of course, the gateway engine may also obtain the configuration objects from the cache management queue for processing according to other orders, which is not limited in the embodiment of the present application.

In the process of processing the cache management queue, when the first configuration object is acquired, the gateway engine can update the first configuration data into the cache. Updating the first configuration data into the cache by the gateway engine represents the gateway engine completing the configuration of the first configuration data. The process of updating the first configuration data into the cache by the gateway engine will be described in detail later, and will not be described here again.

In the embodiment of the application, the configuration data are stored in the configuration centers with different configuration modes, the configuration centers have high reliability, and the gateway engine can load the configuration data from the configuration centers through the corresponding interfaces according to the used configuration modes and update the configuration data into the cache, so that the configuration data meeting the service requirements of the gateway can be obtained in real time under the condition of omitting the monitoring middleware, and the reliability is improved.

In addition, the implementation mode of the configuration center is very flexible, and the gateway engine can select different implementation modes according to different service requirements so as to meet the requirements of different configuration centers.

Considering the initial start-up of the gateway engine, there may be a case where communication with the configuration center is unstable. Therefore, in the embodiment of the application, the local configuration file is introduced, so that the gateway engine can normally complete configuration even if not communicated with the configuration center, and thus, the application service can be provided in time. The process of the gateway engine loading configuration data in the case of the introduction of a local configuration file is described below in connection with fig. 5. Fig. 5 is a flow chart of a gateway configuration method according to an embodiment of the present application. As shown in fig. 5, the method may include:

Step S501, determining whether a local configuration file exists; if yes, step S502 is executed, otherwise step S505 is executed.

Step S502, loading second configuration data from the local configuration file.

The second configuration data may represent configuration data loaded from a local configuration file. The local configuration file may be generated by the gateway engine from configuration data previously loaded from the configuration center. The second configuration data may refer to the first configuration data, and will not be described herein.

Step S503, determining whether the second configuration data is loaded successfully; if yes, step S504 is executed, otherwise step S505 is executed.

The local profile may be corrupted or unavailable, at which point the gateway engine may not be able to successfully load the second configuration data, despite the presence of the local profile. In the event that the gateway engine does not successfully load the second configuration data, the first configuration data may be loaded from the first configuration center to provide a guarantee for gateway configuration.

Step S504, constructing a second configuration object based on the second configuration data, and placing the second configuration object into the cache management queue for processing.

Step S505, loading the first configuration data by calling an interface of the first configuration center.

Step S506, determining whether the first configuration data is loaded successfully, if yes, executing step S507, otherwise executing step S508.

Step S507, constructing a first configuration object based on the first configuration data, and placing the first configuration object into a cache management queue for processing.

Step S508, a first failure event is constructed based on the first configuration data, and the first failure event is added into a delay queue for processing.

In the event that the first configuration data was not successfully loaded, the gateway engine may construct a first failure event. The first failure event may be added to the delay queue for processing. The delay queue may include a plurality of failure events that may be retried after waiting a period of time. The processing procedure of the delay queue will be described in detail later, and will not be described here again.

In the embodiment of the application, when the gateway engine is started, whether a local configuration file exists or not can be checked first; if the configuration data exists, the configuration data in the local configuration file is loaded preferentially, and if the configuration data does not exist, the configuration data is loaded from the configuration center. On one hand, the loading speed of the configuration data can be increased through the local configuration file, so that the gateway engine can complete configuration to provide service for the application as soon as possible; on the other hand, a guarantee is provided for the gateway engine to complete configuration through the configuration middle.

In consideration of network fluctuation and other factors, the gateway engine may fail when loading the first configuration data from the configuration center. In the embodiment of the application, the first failure event can be constructed under the condition that the loading of the first configuration data fails, and the first failure event is added into the delay queue for processing, so that the automatic reloading of the first configuration data is realized, the influence of network fluctuation is reduced, and the reliability is improved. The processing of the delay queue is described below in conjunction with fig. 6. Fig. 6 is a flowchart of a gateway configuration method according to an embodiment of the present application. As shown in fig. 6, the method may include:

step S601, when the duration of the first failure event entering the delay queue is greater than a first threshold, acquiring the first failure event from the delay queue.

The first threshold may be used to measure whether the duration of the first failure event entering the delay queue is sufficient. The first threshold may be set as desired. The retry frequency is greater when the first threshold is greater and the retry frequency is less when the first threshold is less. When the duration of the first failure event entering the delay queue is greater than a first threshold, the waiting time of the first failure event is long enough to be retried. At this point, the gateway engine may obtain the first failure event from the delay queue for processing.

Step S602, obtaining the configuration class and retry number of the first failure event.

Wherein the configuration class may be used to indicate a type of configuration model employed by the first configuration data. The number of retries may be used to indicate the number of reloads of the first configuration data.

Step S603, determining whether the number of retries of the first failure event is smaller than a second threshold; if yes, step S604 is executed, otherwise step S608 is executed.

The second threshold may be used to measure whether the number of retries of the first failure event exceeds the upper limit, i.e. to measure whether the number of loads of the first configuration data exceeds the upper limit. The second threshold may be set as desired. When the second threshold is larger, the number of allowed retries is larger, so that the probability of successful loading of the first configuration data can be improved. And when the second threshold value is smaller, the number of times of allowed retries is smaller, and early warning can be sent as soon as possible.

Step S604, reloading the first configuration data from the first configuration center according to the configuration class center of the first failure event.

When the number of retries of the first failure event is less than the second threshold, indicating that the upper retry limit is not reached, the first configuration data may be reloaded.

Step S605, determining whether the reloading is successful; if yes, step S606 is executed, otherwise step S607 is executed.

The process of reloading the first configuration data is the same as the process of first loading the first configuration data, and will not be described again here. Reloading data may be successful or may fail. If the reloading is successful, the gateway engine is indicated to successfully acquire the first configuration data, then the first configuration object is constructed based on the first configuration data, and the first configuration object is put into a cache management queue, so that the update of the configuration data can be realized. The process of constructing the first configuration object based on the first configuration data and the process of placing the first configuration object into the cache management queue for processing may refer to step S402, which is not described herein. If the reload fails, the gateway engine may add the number of retries of the first failure time together to the delay queue for processing.

Step S606, constructing the first configuration object based on the first configuration data, and placing the first configuration object into the queue management queue for processing.

Step S607, adding the retry times of the first failure event to the delay queue for processing.

Step S608, issue an early warning event.

When the number of retries of the first failure event is greater than or equal to the second threshold, it indicates that the number of retries of the first failure event has reached the upper limit, and the gateway engine cannot acquire the first configuration data after multiple attempts. At this point, the gateway engine may issue an early warning event. The early warning time can be used as a log record or a monitoring index record.

The processing of the cache management queue is described in detail below with reference to fig. 7. The processing procedure of the buffer management queue is divided into two parts, wherein the first part is a procedure of adding the first configuration object into the buffer management queue, and the second part is a processing procedure after acquiring the first configuration object from the buffer management queue. Fig. 7 is a flowchart of a gateway configuration method according to an embodiment of the present application. As shown in fig. 7, the method may include:

step S701, when the first configuration object is put into a cache management queue for processing, determining whether a third configuration object exists in the cache management queue; if yes, step S702 is executed, otherwise step S703 is executed.

Wherein the third configuration object may be used to represent the same configuration object as the configuration center and the configuration class corresponding to the first configuration object. The configuration class may be used to indicate the type of configuration model. The configuration model may be used to indicate a storage format of the configuration data.

When a configuration object is the same as a configuration center and a configuration class corresponding to the first configuration object, the configuration object and the first configuration object are from the same configuration center, and correspond to the same configuration mode, the same configuration model is adopted, so that the same application requirements can be met, the same configuration effect can be achieved, and the configuration object can be called a third configuration object.

Step S702, determining whether the version number of the first configuration object is greater than the version number of the third configuration object; if yes, step S703 is executed, otherwise step S704 is executed.

When a third configuration object is already present in the cache management queue, it indicates that the gateway engine has obtained configuration data that can meet the application requirements. A new version is generated considering that the configuration data may be updated. Thus, the gateway engine may compare the version numbers of the first configuration object and the third configuration object. It will be appreciated that the larger the version number, the more up to date the configuration data.

When the version number of the first configuration object is greater than that of the third configuration object, the newly loaded configuration data is newer, and version update may be generated, so that the first configuration object can be added into a cache management queue for processing, so that the latest version of configuration data can be updated into a cache of the gateway engine.

When the version number of the first configuration object is less than or equal to the version number of the third configuration object, it indicates that the new configuration data is not the latest version, possibly the intermediate version, so that the first configuration object can be discarded to save computing resources and avoid the configuration data rolling back to the historical version, thereby generating errors.

Step S703, putting the first configuration object into the cache queue for processing.

Step S704, discarding the first configuration object.

Step S705, obtaining the first configuration object from the cache management queue.

Step S706, generating or updating a local configuration file according to the first configuration object.

When the local configuration file does not exist before, the first configuration data can be obtained from the first configuration object, and then the local configuration file is generated based on the first configuration data, so that the configuration data can be quickly obtained when the gateway engine is started next time. When the local configuration file exists before, the first configuration data can be loaded from the first configuration center after the cache is updated by using the local configuration file to generate a first configuration object, and then the local configuration file is updated by adopting the first configuration data in the first configuration object, so that the configuration data in the local configuration file is updated in time.

Step S707 updates the first configuration data to the cache.

Step S708, if the first configuration data is not successfully updated to the cache, determining whether the retry number of the first configuration object is less than a third threshold; if yes, step S709 is performed, otherwise step S710 is performed.

The third threshold may be used to measure whether the number of retries updated based on the first configuration object reaches an upper limit. If the number of retries of the first configuration object is less than the third threshold, the gateway engine may attempt to update again. If the retry number of the first configuration object is greater than or equal to the third threshold, an early warning event may be issued. The third threshold may be set as needed, which is not limited by the embodiment of the present application.

Step S709, adding one to the retry number of the first configuration object, and then putting the retry number into the cache management queue again for processing.

Step S710, issue an early warning event.

The gateway engine will load configuration data after start-up. During operation after the gateway engine is started, configuration data of the configuration center may change. In the embodiment of the application, the gateway engine can dynamically monitor the configuration data of the configuration center, so that the local cache can be updated in time under the condition that the configuration data of the configuration center is updated. The process of this dynamic listening is described below in connection with fig. 8. Fig. 8 is a flowchart of a gateway configuration method according to an embodiment of the present application. As shown in fig. 8, the method may include:

Step S801, initializing a first configuration center.

In the embodiment of the application, after the gateway engine determines the configuration data of the first configuration center according to the used configuration mode, the first configuration data can be initialized.

Step S802, adding a configuration change monitor to each configuration class of the first configuration center.

Wherein the configuration class may be used to indicate a type of configuration model used to indicate a storage format of the configuration data. In an embodiment of the present application, the gateway engine may traverse each configuration class in the first configuration and then add a configuration change listener for each configuration class. In this way, when the configuration data of any configuration class in the first configuration center changes, the configuration change monitor corresponding to the configuration class can monitor the change, thereby generating a fourth configuration object, and issuing the fourth configuration object to the event bus.

Step S803, subscribe to the event bus.

The event bus is an implementation of the publish-subscribe mode, is a centralized event handling mechanism, allows different components to communicate with each other without interdependence, and achieves a decoupling purpose. The event bus serves multiple publishers and subscribers simultaneously, isolates direct dependencies between publishers and subscribers, takes over the publish and subscribe logic of all events, and is responsible for event transit. In the embodiment of the application, the configuration center corresponds to a publisher, and when a plurality of configuration centers exist, the configuration center corresponds to a plurality of publishers, and the gateway engine corresponds to a subscriber. When configuration data of each configuration center changes (i.e., updates), each configuration center may issue configuration objects to the event bus. After subscribing the event bus, the gateway engine can acquire the configuration objects issued by each configuration center and then put the configuration objects into a cache management queue for processing.

Thus, through subscribing event buses, the configuration data in the configuration center can be timely responded to be updated, the accuracy of configuration is improved, direct dependence on the configuration center is isolated, and the reliability is improved.

In step S804, when a fourth configuration object is received from the event bus, the fourth configuration object is put into the cache management queue for processing.

Wherein the fourth configuration object is published into the event bus for the configuration change listener, the fourth configuration object being generated from configuration data updated in the first configuration center.

The gateway engine subscribes to the event bus, so that when a fourth configuration object appears in the event bus, the gateway engine can directly acquire the fourth configuration object from the event bus and add the fourth configuration object into the cache management queue for processing. The process of adding the fourth configuration object to the cache management queue and the process in the cache management queue may refer to the first configuration object, which is not described herein.

In the embodiment of the application, the configuration center can dynamically update the configuration data of the gateway, and then the automatic pushing or timing pulling function of the configuration center is heard, so that the real-time effectiveness of the configuration data is realized, and the service requirement can be responded in time.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a gateway configuration device for realizing the gateway configuration method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in one or more embodiments of the gateway configuration device provided below may refer to the limitation of the gateway configuration method hereinabove, and will not be repeated herein.

In one embodiment, fig. 9 is a block diagram of a configuration device according to an embodiment of the present application. The apparatus may be applied to a gateway engine. As shown in fig. 9, the apparatus 900 includes: a loading module 901, a building module 902, and an updating module 903, wherein:

the loading module is used for loading first configuration data by calling an interface of a first configuration center, wherein the first configuration center represents a configuration center matched with a first configuration mode, and the first configuration mode represents a configuration mode used by the gateway engine;

the construction module is used for constructing a first configuration object based on the first configuration data under the condition of successfully loading the first configuration data, and placing the first configuration object into a cache management queue for processing;

and the updating module is used for updating the first configuration data into a cache of a gateway when the first configuration object is acquired from the cache management queue in the process of processing the cache management queue so as to configure the gateway.

In one possible implementation, the apparatus further includes:

the determining module is used for determining whether a local configuration file exists;

the loading module is further configured to load second configuration data from the local configuration file if the local configuration file exists; and under the condition of successfully loading the second configuration data, constructing a second configuration object based on the second configuration data, and placing the second configuration object into the cache management queue for processing.

In one possible implementation, the loading module is further configured to:

loading the first configuration data by calling an interface of the first configuration center under the condition that the local configuration file does not exist;

or,

and loading the first configuration data by calling an interface of the first configuration center under the condition that the local configuration file exists and the second configuration data is not loaded successfully.

In one possible implementation, the building module is further configured to:

and under the condition that the first configuration data is not loaded successfully, constructing a first failure event based on the first configuration data, and adding the first failure event into a delay queue for processing.

In one possible implementation, the apparatus further includes: the device comprises an acquisition module and a first adding module;

the acquisition module is used for acquiring the first failure event from the delay queue when the duration of the first failure event entering the delay queue is greater than a first threshold value;

the loading module is further configured to, when the retry number of the first failure event is less than a second threshold, reload the first configuration data from the first configuration center according to a configuration class of the first failure event, where the configuration class is used to indicate a type of a configuration model adopted by the first configuration data;

The construction module is further configured to construct the first configuration object based on the first configuration data if reloading is successful, and put the first configuration object into the cache management queue for processing;

and the first adding module is used for adding the retry times of the first failure event into the delay queue for processing if the reloading fails.

In one possible implementation manner, the placing the first configuration object into a cache management queue for processing includes:

determining whether a third configuration object exists in the cache management queue, wherein the third configuration object is used for representing a configuration object which is the same as a configuration center and a configuration class corresponding to the first configuration object, the configuration class is used for indicating the type of a configuration model, and the configuration model is used for indicating the storage format of configuration data;

if the third configuration object exists and the version number of the first configuration object is larger than the version number of the third configuration object, the first configuration object is placed into the cache queue for processing;

or,

and if the third configuration object does not exist, the first configuration object is put into the cache queue for processing.

In one possible implementation, the apparatus further includes: a second adding module;

and if the first configuration data is not successfully updated to the cache and the retry number of the first configuration object is smaller than a third threshold value, the second adding module adds one to the retry number of the first configuration object and then re-puts the first configuration object into the cache management queue for processing.

In one possible implementation, the apparatus further includes:

the initialization module is used for initializing the first configuration center, adding a configuration change monitor to each configuration class of the first configuration center, wherein the configuration class is used for indicating the type of a configuration model, and the configuration model is used for indicating the storage format of configuration data;

the subscription module is used for subscribing the event bus;

and the third adding module is used for placing a fourth configuration object into the cache management queue for processing under the condition that the fourth configuration object is received from the event bus, wherein the fourth configuration object is issued to the event bus by the configuration change monitor and is generated according to the configuration data updated in the first configuration center.

The respective modules in the gateway configuration apparatus described above may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 10. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is for storing configuration data. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a gateway configuration method.

It will be appreciated by those skilled in the art that the structure shown in FIG. 10 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, implements the steps of the method embodiments described above.

In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims (10)

1. A gateway configuration method, wherein the method is applied to a gateway engine, and the method applied to the gateway engine comprises:

loading first configuration data by calling an interface of a first configuration center, wherein the first configuration center represents a configuration center matched with a first configuration mode, and the first configuration mode represents a configuration mode used by the gateway engine;

Under the condition of successfully loading the first configuration data, constructing a first configuration object based on the first configuration data, and placing the first configuration object into a cache management queue for processing;

and in the process of processing the cache management queue, when the first configuration object is acquired from the cache management queue, updating the first configuration data into a cache of a gateway to configure the gateway.

2. The method according to claim 1, wherein the method further comprises:

determining whether a local configuration file exists;

loading second configuration data from the local configuration file in the presence of the local configuration file;

and under the condition of successfully loading the second configuration data, constructing a second configuration object based on the second configuration data, and placing the second configuration object into the cache management queue for processing.

3. The method of claim 2, wherein loading the first configuration data by invoking an interface of the first configuration center comprises:

loading the first configuration data by calling an interface of the first configuration center under the condition that the local configuration file does not exist;

Or,

and loading the first configuration data by calling an interface of the first configuration center under the condition that the local configuration file exists and the second configuration data is not loaded successfully.

4. The method according to claim 1, wherein the method further comprises:

and under the condition that the first configuration data is not loaded successfully, constructing a first failure event based on the first configuration data, and adding the first failure event into a delay queue for processing.

5. The method according to claim 4, wherein the method further comprises:

when the time length of the first failure event entering the delay queue is greater than a first threshold value, acquiring the first failure event from the delay queue;

loading the first configuration data from the first configuration center again according to a configuration class of the first failure event when the retry number of the first failure event is smaller than a second threshold value, wherein the configuration class is used for indicating the type of a configuration model adopted by the first configuration data;

if the reloading is successful, constructing the first configuration object based on the first configuration data, and putting the first configuration object into the cache management queue for processing;

And if the reloading fails, adding the retry times of the first failure event into the delay queue for processing.

6. The method of claim 1, wherein placing the first configuration object into a cache management queue for processing comprises:

determining whether a third configuration object exists in the cache management queue, wherein the third configuration object is used for representing a configuration object which is the same as a configuration center and a configuration class corresponding to the first configuration object, the configuration class is used for indicating the type of a configuration model, and the configuration model is used for indicating the storage format of configuration data;

if the third configuration object exists and the version number of the first configuration object is larger than the version number of the third configuration object, the first configuration object is placed into the cache queue for processing;

or,

and if the third configuration object does not exist, the first configuration object is put into the cache queue for processing.

7. The method according to claim 1, wherein the method further comprises:

if the first configuration data is not successfully updated to the cache and the retry number of the first configuration object is smaller than a third threshold value, the retry number of the first configuration object is added by one and then is put into the cache management queue again for processing.

8. The method according to claim 1, wherein the method further comprises:

initializing the first configuration center, and adding a configuration change monitor to each configuration class of the first configuration center, wherein the configuration class is used for indicating the type of a configuration model, and the configuration model is used for indicating the storage format of configuration data;

subscribing to an event bus;

and when a fourth configuration object is received from the event bus, placing the fourth configuration object into the cache management queue for processing, wherein the fourth configuration object is issued to the event bus by the configuration change monitor and is generated according to the configuration data updated in the first configuration center.

9. A gateway configuration apparatus, the apparatus being applied to a gateway engine, the method comprising:

the loading module is used for loading first configuration data by calling an interface of a first configuration center, wherein the first configuration center represents a configuration center matched with a first configuration mode, and the first configuration mode represents a configuration mode used by the gateway engine;

the construction module is used for constructing a first configuration object based on the first configuration data under the condition of successfully loading the first configuration data, and placing the first configuration object into a cache management queue for processing;

And the updating module is used for updating the first configuration data into a cache of a gateway when the first configuration object is acquired from the cache management queue in the process of processing the cache management queue so as to configure the gateway.

10. The gateway configuration system is characterized by comprising a gateway management and control end, a configuration center and a gateway engine;

the gateway control end is used for receiving control data, wherein the control data is used for configuring the gateway and comprises data required by configuring the gateway and a corresponding configuration mode; assembling the management and control data into configuration data according to a configuration model, wherein the configuration model is used for indicating a storage format of the configuration data; storing the configuration data, the configuration class and the version number in a configuration center corresponding to the configuration mode in an associated mode, wherein the configuration class is used for indicating the type of the configuration model;

the configuration centers are used for storing configuration data, configuration classes and version numbers in an associated mode, and each configuration center corresponds to a unique configuration mode;

the gateway engine for performing the gateway configuration method according to any of claims 1 to 9.