A data processing method and unified gateway

Abstract

The present application provides a data processing method and a unified gateway, wherein the management and control end receives a business rule configuration request sent by a target service, the business rule configuration request includes a plurality of standardized configuration items corresponding to the target gateway docking function configuration item, calls the target standardized model framework corresponding to the target gateway docking function configuration item, generates a standardized docking model corresponding to the business rule configuration request according to a plurality of data standardization requirement items and the target standardized model framework, adds a corresponding model call identifier to the standardized docking model, and sends the standardized docking model to an intermediate carrier; the engine end pulls the standardized docking model from the intermediate carrier, and stores the standardized docking model to the memory corresponding to the unified gateway. The present application generates a corresponding standardized docking model through a standardized model framework, thereby improving the efficiency and accuracy of creating standardized rules between multiple software systems and the unified gateway.

Description

Technical Field

[0001] The present application relates to the field of gateway communication technology, and in particular to a data processing method and a unified gateway. Background Art

[0002] In the existing technology, the unified gateway is responsible for realizing data docking with different software services. The unified gateway is divided into the control end and the engine end. The control end is mainly used to configure business rule data, while the engine end is used to load the business rule data configured by the control end. During the actual business call process, the requested message data needs to be matched with the business rule data configuration loaded by the engine end, and the engine end logical processing is performed according to the matched target business rule data.

[0003] Although the current unified gateway is relatively stable, it is still not flexible enough for the corresponding gateway control and gateway engine within the gateway. Specifically, since the unified gateway usually needs to connect to different software systems, the business rule data corresponding to different software systems, that is, the standardized processing requirements, are also very different. Although external services in the existing technology can implement standardized rule configuration through the control end and the engine end, when the external service needs to add functions, both the external service and the unified gateway need to participate in the functional transformation process, that is, the external service calls the control end to re-enter the standardized rule configuration, and after further processing by the control end, the engine end reloads the modified rules. In this process, it is not difficult to see that the control end still needs to perform a large amount of rule configuration processing. This process improves the efficiency of creating standardized rules between external services and the unified gateway. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide at least a data processing method and a unified gateway, to generate a corresponding standardized docking model through a standardized model framework, and to improve the efficiency and accuracy of creating standardized rules between multiple software systems and the unified gateway.

[0005] This application mainly includes the following aspects:

[0006] In the first aspect, an embodiment of the present application provides a data processing method, which is applied to a unified gateway. The unified gateway includes a management and control end and an engine end. The method includes: the management and control end receives a business rule configuration request sent by a target service, the business rule configuration request includes multiple standardized requirement items corresponding to the target gateway function under different functional attributes, calls the target standardized model framework corresponding to the target gateway function, and generates a standardized docking model corresponding to the business rule configuration request according to the multiple standardized requirement items and the target standardized model framework corresponding to different functional attributes, adds a corresponding model call identifier to the standardized docking model, and sends the standardized docking model to an intermediate carrier. The standardized requirement item refers to the data configuration item that needs to be possessed in the subsequently generated standardized docking model, and the standardized model framework defines multiple functional attribute configuration items corresponding to the target gateway function; the engine end pulls the standardized docking model from the intermediate carrier and stores the standardized docking model in the memory corresponding to the unified gateway.

[0007] In a possible implementation, the method also includes: on the management and control side, for each functional attribute corresponding to the target gateway function, filling multiple standardized requirement items corresponding to the functional attribute into the functional attribute configuration items corresponding to the functional attribute in the target standardized model framework to form multiple standardized configuration items corresponding to the functional attribute; and forming a standardized docking model corresponding to the business rule configuration request from the multiple standardized configuration items corresponding to each functional attribute.

[0008] In a possible implementation, the method also includes: on the management and control side, receiving a business rule revision request sent by the target service, the business rule revision request includes revision requirement data corresponding to the standardized docking model to be revised, retrieving the standardized docking model to be revised, modifying the standardized docking model to be revised according to the revision requirement data, obtaining a revised standardized docking model, and sending the revised standardized docking model to the intermediate carrier; on the engine side, pulling the revised standardized docking model from the intermediate carrier, and updating the revised standardized docking model to the memory.

[0009] In one possible implementation, the revision requirement data includes the standardized configuration items to be revised and the revision operations corresponding to the standardized configuration items to be revised, wherein the method further includes: the management and control end calls the standardized docking model to be revised, performs the revision operation on the standardized configuration items to be revised in the standardized docking model to be revised, and obtains the revised standardized docking model.

[0010] In a possible implementation, the method also includes: the management and control end, before sending the standardized docking model to the intermediate carrier, configures the associated standardized docking model corresponding to the standardized docking model, and the associated standardized docking model is the standardized docking model for other gateway functions except the target gateway function under the target service; the management and control end configures the corresponding processing order for the standardized docking model and its corresponding associated standardized docking model.

[0011] In a possible implementation, the method also includes: on the management and control side, receiving a service docking request sent by the target service, and sending the service docking request to an intermediate carrier, where the service docking request carries message data and a target model call identifier for docking with the downstream service to be docked; on the engine side, pulling the service docking request from the intermediate carrier, and calling the target standardized docking model corresponding to the target model call identifier from the memory corresponding to the unified gateway, applying the target standardized docking model to perform standardized data configuration on the message data, and obtaining the corresponding target standardized data structure.

[0012] In a possible implementation, the method also includes: on the engine side, calling the associated standardized docking model corresponding to the target standardized docking model, and sequentially enabling the target standardized docking model and its associated standardized docking model in accordance with the processing order corresponding to the target standardized docking model and its associated standardized docking model to perform standardized configuration on the message data, and obtaining the target standardized data structure corresponding to each standardized docking model corresponding to the target service.

[0013] In a possible implementation, the method also includes: on the engine side, pulling the service docking request from the intermediate carrier, and if the target standardized docking model corresponding to the target model call identifier does not exist in the memory, directly converting the message data into a format that can be recognized by the unified gateway according to the preset standardized processing rules.

[0014] On the second aspect, an embodiment of the present application also provides a unified gateway, which includes a management and control end and an engine end. The management and control end receives a business rule configuration request sent by a target service, and the business rule configuration request includes multiple standardized requirement items corresponding to the target gateway function under different functional attributes. The target standardized model framework corresponding to the target gateway function is called, and a standardized docking model corresponding to the business rule configuration request is generated according to the multiple standardized requirement items and the target standardized model framework corresponding to the different functional attributes. A corresponding model call identifier is added to the standardized docking model, and the standardized docking model is sent to an intermediate carrier. The standardized requirement item refers to the data configuration item that needs to be possessed in the subsequently generated standardized docking model. The standardized model framework defines multiple functional attribute configuration items corresponding to the target gateway function; the engine end pulls the standardized docking model from the intermediate carrier and stores the standardized docking model in the memory corresponding to the unified gateway.

[0015] In one possible implementation, the management and control end, for each functional attribute corresponding to the target gateway function, fills the multiple standardized requirement items corresponding to the functional attribute into the functional attribute configuration items corresponding to the functional attribute in the target standardized model framework to form multiple standardized configuration items corresponding to the functional attribute; and the multiple standardized configuration items corresponding to each functional attribute form a standardized docking model corresponding to the business rule configuration request.

[0016] An embodiment of the present application provides a data processing method and a unified gateway, wherein the management and control end receives a business rule configuration request sent by a target service, the business rule configuration request includes a plurality of standardized requirement items corresponding to the target gateway function under different functional attributes, calls the target standardized model framework corresponding to the target gateway function, generates a standardized docking model corresponding to the business rule configuration request according to the plurality of standardized requirement items corresponding to different functional attributes and the target standardized model framework, adds a corresponding model call identifier to the standardized docking model, and sends the standardized docking model to an intermediate carrier, wherein the standardized requirement item refers to the data configuration item required to be possessed within the subsequently generated standardized docking model, and the standardized model framework defines a plurality of functional attribute configuration items corresponding to the target gateway function; the engine end pulls the standardized docking model from the intermediate carrier and stores the standardized docking model to the memory corresponding to the unified gateway. The present application generates a corresponding standardized docking model through a standardized model framework, thereby improving the efficiency and accuracy of standardized rule creation between multiple software systems and the unified gateway.

[0017] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0019] Figure 1 A flow chart of a data processing method provided in an embodiment of the present application is shown;

[0020] Figure 2 A schematic diagram of the structure of a unified gateway provided in an embodiment of the present application is shown;

[0021] Figure 3 A schematic diagram of a service model provided by an embodiment of the present application is shown. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of illustration and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowcharts can be implemented out of sequence, and steps without logical context can be reversed or implemented simultaneously. In addition, those skilled in the art, under the guidance of the contents of this application, can add one or more other operations to the flowchart, or remove one or more operations from the flowchart.

[0023] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the present application.

[0024] With the development of the times, there are more and more software systems, and each software system is an independent individual. However, to some extent, some systems will have more or less connections with other systems. For example, the large-screen monitoring system needs to monitor the health of each system. In this way, the system needs to provide a health detection interface or real-time fire detection of the application port to confirm the monitoring of the system. When software systems are interconnected, better data docking and unification are needed. Therefore, fixed docking methods and docking messages are agreed upon between the systems.

[0025] In the existing technology, the unified gateway is responsible for realizing data docking with different software services. The unified gateway is divided into the control end and the engine end. The control end is mainly used to configure business rule data, while the engine end is used to load the business rule data configured by the control end. During the actual business call process, the requested message data needs to be matched with the business rule data configuration loaded by the engine end, and the engine end logical processing is performed according to the matched target business rule data.

[0026] Although the current unified gateway is relatively stable, in the existing technology, although external services can implement standardized rule configuration through the control end and the engine end, when the external service needs to add functions, both the external service and the unified gateway need to participate in the functional transformation process. That is, the external service calls the control end to re-enter the standardized rule configuration, and after further processing by the control end, the engine end reloads the modified rules. In this process, it is not difficult to see that the control end still needs to perform a large amount of rule configuration processing. This process improves the efficiency of creating standardized rules between external services and the unified gateway.

[0027] Based on this, the embodiments of the present application provide a data processing method and a unified gateway, which generates a corresponding standardized docking model through a standardized model framework, thereby improving the efficiency and accuracy of creating standardized rules between multiple software systems and the unified gateway, as follows:

[0028] See also Figure 1 , Figure 1 A flow chart of a data processing method provided by an embodiment of the present application is shown. Figure 2 , Figure 2 FIG. 1 shows a schematic diagram of the structure of a unified gateway provided in an embodiment of the present application. Figure 1 and Figure 2 As shown, the method provided in the embodiment of the present application is applied to a unified gateway, which includes a control terminal Q1 and an engine terminal Q2, and includes the following steps:

[0029] S100: The management and control end receives a business rule configuration request sent by the target service.

[0030] The business rule configuration request includes multiple standardized requirement items corresponding to the target gateway function under different functional attributes.

[0031] S200. The control end calls the target standardized model framework corresponding to the target gateway function.

[0032] S300. The management and control end generates a standardized docking model corresponding to the business rule configuration request based on multiple standardized requirement items and the target standardized model framework corresponding to different functional attributes.

[0033] S400: The management and control end adds a corresponding model call identifier to the standardized docking model and sends the standardized docking model to the intermediate carrier.

[0034] Standardization requirement items refer to the data configuration items required within the subsequently generated standardized docking model. The standardized model framework defines multiple functional configuration items corresponding to the target gateway functions.

[0035] S500: The engine side pulls the standardized docking model from the intermediate carrier and stores the standardized docking model in the memory corresponding to the unified gateway.

[0036] In steps S100 to S500, the unified gateway provides multiple gateway functions, including but not limited to at least one of the following: service, communication protocol, channel, application and interface. Each gateway function jointly provides the target service with the ability to call the downstream system or gateway internal service connected to the unified gateway. The unified gateway pre-creates a standardized model framework corresponding to each gateway function. The management and control end first determines the target standardized model framework corresponding to the target gateway function, and then fills each standardized requirement item corresponding to the target gateway function into the target standardized model framework according to its functional attributes. In this way, a corresponding standardized docking model can be formed. The standardized docking model is actually a standardized processing rule corresponding to the gateway function. That is, in order to facilitate docking with external services, the unified gateway standardizes the model according to the function. Specifically, the standardized docking models corresponding to different gateway functions include:

[0037] Service model: mainly describes the basic service information exposed by the gateway engine;

[0038] Communication protocol model: The gateway engine mainly provides calling services to the outside world through the protocol port.

[0039] Channel model: mainly defines the overall abstract management of the gateway's externally exposed services.

[0040] Application model: It mainly defines a description of how downstream systems are connected to the gateway. Downstream services can be divided into traditional services and microservices.

[0041] Interface model: It mainly defines the description of the interface information of the downstream system accessing the gateway, which includes the basic information of the interface.

[0042] In a preferred embodiment, the method further comprises:

[0043] On the management and control side, for each functional attribute corresponding to the target gateway function, multiple standardized requirement items corresponding to the functional attribute are filled into the functional attribute configuration items corresponding to the functional attribute in the target standardized model framework to form multiple standardized configuration items corresponding to the functional attribute. The multiple standardized configuration items corresponding to each functional attribute form a standardized docking model corresponding to the business rule configuration request.

[0044] In a specific embodiment of this application, please refer to Figure 3 , Figure 3 A schematic diagram of a service model provided by an embodiment of the present application is shown. Figure 3As shown, the standardized model framework provided by the service model includes but is not limited to the following contents: basic service information, matching path, input and output parameters, and model version. The basic service information, matching path, input and output parameters, and model version are the functional attributes corresponding to the service. Among them, this application can fill in the basic service information and input and output parameters according to the multiple standardized requirement items carried in the business rule configuration request. For example, the multiple standardized requirement items corresponding to the basic service information carried in the business rule configuration request include the service name, service code, and service version number. The basic service information item in the final generated standardized docking model only includes the name, service code, and service version number. The matching path and model version can be set according to the actual situation. After the corresponding standardized model is determined on the management side, the corresponding model call identifier needs to be further added to the standardized model to call the model when there is a business request for the subsequent target service. The standardized model with the added model call identifier is sent to the intermediate carrier so that the engine side can pull and save the newly created standardized model from the intermediate carrier.

[0045] Specifically, the intermediate carrier is a middleware for communication between the control end and the engine end of the unified gateway, such as a message middleware, whose main capability is to synchronize the data information generated by the control end to the engine end.

[0046] like Figure 3 In the service model created as shown, the basic service information includes the service name, service code, service version number, service release scope, channel information and communication protocol. The matching path is not limited to http and tcp. http includes service matching key and service matching value. TCP includes service matching key and service matching value. Output and input parameters include output parameters and input parameters. Output parameters include attributes (attribute name, attribute type, attribute length and attribute check).

[0047] It can be seen that the data processing method provided by this application allows different software systems to call the pre-created standardized model framework to generate corresponding standardized docking models, which can flexibly solve the problem of docking multiple systems in external systems due to inconsistent data connection models, thereby enabling the gateway to provide external flexibility and easy-to-dock design concepts.

[0048] In a preferred embodiment, the method provided by the present application further includes:

[0049] The control side receives the business rule revision request sent by the target service, retrieves the standardized docking model to be revised, modifies the standardized docking model to be revised according to the revision requirement data, obtains the revised standardized docking model, and sends the revised standardized docking model to the intermediate carrier. The engine side pulls the revised standardized docking model from the intermediate carrier and updates the revised standardized docking model to the memory.

[0050] Specifically, the business rule revision request also includes the model call identifier and revision requirement data corresponding to the standardized docking model to be revised. The revision requirement data includes but is not limited to at least one of the following items: a revision operation and the standardized configuration item to be revised corresponding to the revision operation. The revision operation includes but is not limited to at least one of the following items: deletion, addition and correction.

[0051] In a specific embodiment, after receiving the business rule revision request, the control end calls the corresponding standardized docking model to be revised from the memory according to the model call identifier, and then revises the corresponding standardized configuration items to be revised in the standardized docking model to be revised according to the revision requirement data. If the standardized docking model to be revised is Figure 3 For the service model shown, revising the requirement data may involve deleting the service code in the basic service information, and the customized standardized docking model is updated into the memory by the engine side.

[0052] From the above process, it can be seen that the standardized docking model created by the method of this application can directly complete the revision processing of the standardized docking model on the management and control side, without the need to make corrections again on the engine side. The revised standardized docking model obtained on the management and control side can be directly passed to the engine side for updating, which simplifies the processing process of business rule changes proposed by different software systems and improves the change speed and accuracy of standardized processing rules.

[0053] In a preferred embodiment, the management and control end: before sending the standardized docking model to the intermediate carrier, configures the associated standardized docking model corresponding to the standardized docking model. The associated standardized docking model is the standardized docking model corresponding to other gateway functions except the target gateway function under the target service. The management and control end: configures the corresponding processing order for the standardized docking model and its corresponding associated standardized docking model.

[0054] In a specific embodiment, the target service may simultaneously submit multiple business rule configuration requests, and the multiple business rule configuration requests correspond one-to-one to multiple gateway functions. In this way, assuming that the multiple gateway functions provided by the unified gateway include services, communication protocols, channels, applications, and interfaces, the corresponding standardized docking models that can be generated include service models, communication protocol models, channel models, application models, and interface models. Then, it is necessary to configure the corresponding associated standardized docking model for each standardized docking model corresponding to the target service. For example, the associated standardized docking model corresponding to the service model is the communication protocol model, channel model, application model, and interface model created under the same service. Then, the corresponding processing sequence is configured for the service model, communication protocol model, channel model, application model, and interface model under the same service. The processing sequence is used for the processing sequence corresponding to the multiple standardized docking models when the corresponding multiple standardized docking models are applied for processing.

[0055] In a preferred embodiment, the method further comprises:

[0056] The control end receives the service docking request sent by the target service and sends the service docking request to the intermediate carrier. The service docking request carries the message data and the target model call identifier for docking with the downstream service to be docked. The engine end: pulls the service docking request from the intermediate carrier and calls the target standardized docking model corresponding to the target model call identifier from the memory corresponding to the unified gateway. The target standardized docking model is applied to standardize the message data to obtain the corresponding target standardized data structure.

[0057] In this application, after creating multiple standardized docking models corresponding to each service connected to the unified gateway, the multiple standardized docking models corresponding to each service can be applied to complete the processing of the service docking request sent by the service. Specifically, the management and control end first receives and passes the service docking request sent by the target service to the intermediate carrier. Then, the engine end pulls the service docking request from the intermediate carrier, and calls the target standardized docking model corresponding to the target model call identifier from the corresponding multiple standardized docking models in the memory, and then further processes the message data according to the target standardized docking model to obtain the standardized target standardized data structure.

[0058] In another preferred embodiment, the engine side is further configured to:

[0059] Retrieve the associated standardized docking model corresponding to the target standardized docking model, and in accordance with the processing order corresponding to the target standardized docking model and its associated standardized docking model, sequentially enable the target standardized docking model and its associated standardized docking model to perform standardized configuration on the message data, and obtain the target standardized data structure corresponding to each target standardized docking model.

[0060] In the specific implementation, there is a corresponding processing order for multiple standardized docking models provided by the same service under different functions of the unified gateway. After receiving the service docking request on the engine side, the target standardized docking model corresponding to the service docking request is first determined, and then the associated standardized docking model corresponding to the target standardized docking model is further determined. Then, the target standardized docking model and its corresponding associated standardized docking model have a processing order for the message data. According to the processing order, the target standardized docking model and its corresponding associated standardized docking model are used to sequentially standardize the message data, and finally multiple target standardized data structures are obtained.

[0061] In a preferred embodiment, the engine side is further used for:

[0062] Pull the service docking request from the intermediate carrier. If the target standardized docking model corresponding to the target model call identifier does not exist in the memory, the message data is directly converted into a format that can be recognized by the unified gateway according to the preset standardized processing rules.

[0063] Specifically, when there is no standardized docking model corresponding to the target model call identifier in the memory, the unified gateway also provides a conversion layer, whose function is to convert the received message data into a standardized data structure that can be recognized by the unified gateway.

[0064] Compared with the existing technology, this technical solution has a design that defines standardized docking, which can flexibly solve the data transmission and docking between multiple service systems outside the unified network management, thereby enabling the gateway to provide external flexibility and easy docking design concepts.

[0065] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0066] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0067] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0068] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0069] The above are only specific embodiments of the present application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A data processing method, applied to a unified gateway, wherein the unified gateway includes a management and control end and an engine end, characterized in that: The unified gateway provides multiple gateway functions, including at least services, communication protocols, channels, applications, and interfaces. The gateway functions collectively provide the target service with the ability to call downstream systems connected to the unified gateway or internal services of the unified gateway. The method includes: The control end receives a business rule configuration request sent by a target service, wherein the business rule configuration request includes multiple standardized requirement items corresponding to the target gateway function under different functional attributes, calls the target standardized model framework corresponding to the target gateway function, generates a standardized docking model corresponding to the business rule configuration request according to the multiple standardized requirement items corresponding to the different functional attributes and the target standardized model framework, adds a corresponding model call identifier to the standardized docking model, and sends the standardized docking model to an intermediate carrier, wherein the standardized requirement item refers to a data configuration item required to be present in the subsequently generated standardized docking model, and the standardized model framework defines multiple functional attribute configuration items corresponding to the target gateway function; The engine side pulls the standardized docking model from the intermediate carrier and stores the standardized docking model in a memory corresponding to the unified gateway.

2. The method according to claim 1, characterized in that The method further comprises: The control end, for each functional attribute corresponding to the target gateway function, fills the multiple standardized requirement items corresponding to the functional attribute into the functional attribute configuration items corresponding to the functional attribute in the target standardized model framework, thereby forming multiple standardized configuration items corresponding to the functional attribute; The control end forms a standardized docking model corresponding to the business rule configuration request by using multiple standardized configuration items corresponding to each functional attribute.

3. The method according to claim 1, characterized in that The method further comprises: The control end receives a business rule revision request sent by a target service, the business rule revision request including revision requirement data corresponding to the standardized docking model to be revised, retrieves the standardized docking model to be revised, modifies the standardized docking model to be revised according to the revision requirement data, obtains a revised standardized docking model, and sends the revised standardized docking model to the intermediate carrier; The engine side pulls the revised standardized docking model from the intermediate carrier and updates the revised standardized docking model to the memory.

4. The method according to claim 3, characterized in that The revision requirement data at least includes a revision operation and a to-be-revised standardized configuration item corresponding to the revision operation. The method further comprises: The control end retrieves the standardized docking model to be revised, performs the revision operation on the standardized configuration item to be revised in the standardized docking model to be revised, and obtains a revised standardized docking model.

5. The method according to claim 1, wherein The method further comprises: The control end configures, before sending the standardized docking model to the intermediate carrier, an associated standardized docking model corresponding to the standardized docking model, wherein the associated standardized docking model is a standardized docking model corresponding to other gateway functions under the target service except the target gateway function; The control end configures a corresponding processing sequence for the standardized docking model and its corresponding associated standardized docking model.

6. The method according to claim 5, characterized in that The method further comprises: The control end receives a service connection request sent by the target service and sends the service connection request to the intermediate carrier. The service connection request carries the message data for connection with the downstream service to be connected and the target model call identifier. The engine side pulls the service docking request from the intermediate carrier, and calls the target standardized docking model corresponding to the target model call identifier from the memory corresponding to the unified gateway, applies the target standardized docking model to perform standardized data configuration on the message data, and obtains the corresponding target standardized data structure.

7. The method according to claim 6, characterized in that The method further comprises: The engine side calls the associated standardized docking model corresponding to the target standardized docking model, and in accordance with the processing order corresponding to the target standardized docking model and its associated standardized docking model, sequentially enables the target standardized docking model and its associated standardized docking model to perform standardized configuration on the message data, and obtains the target standardized data structure corresponding to each standardized docking model corresponding to the target service.

8. The method according to claim 6, characterized in that The method further comprises: The engine side pulls the service docking request from the intermediate carrier. If the target standardized docking model corresponding to the target model call identifier does not exist in the memory, the message data is directly converted into a format that can be recognized by the unified gateway according to the preset standardized processing rules.

9. A unified gateway, comprising a management and control end and an engine end, characterized in that: The unified gateway provides multiple gateway functions, including at least services, communication protocols, channels, applications and interfaces. These gateway functions jointly provide the target service with the ability to call downstream systems connected to the unified gateway or internal services of the unified gateway. The control end receives a business rule configuration request sent by a target service, wherein the business rule configuration request includes multiple standardized requirement items corresponding to the target gateway function under different functional attributes, calls the target standardized model framework corresponding to the target gateway function, generates a standardized docking model corresponding to the business rule configuration request according to the multiple standardized requirement items corresponding to the different functional attributes and the target standardized model framework, adds a corresponding model call identifier to the standardized docking model, and sends the standardized docking model to an intermediate carrier, wherein the standardized requirement item refers to a data configuration item required to be present in the subsequently generated standardized docking model, and the standardized model framework defines multiple functional attribute configuration items corresponding to the target gateway function; The engine side pulls the standardized docking model from the intermediate carrier and stores the standardized docking model in a memory corresponding to the unified gateway.

10. The unified gateway according to claim 9, characterized in that: The control end, for each functional attribute corresponding to the target gateway function, fills the multiple standardized requirement items corresponding to the functional attribute into the functional attribute configuration items corresponding to the functional attribute in the target standardized model framework, thereby forming multiple standardized configuration items corresponding to the functional attribute; A standardized docking model corresponding to the business rule configuration request is formed by multiple standardized configuration items corresponding to each functional attribute.

Images