WO2020244033A1

WO2020244033A1 - General data configuration method and system for service invocation

Info

Publication number: WO2020244033A1
Application number: PCT/CN2019/096630
Authority: WO
Inventors: 张继鹏; 董卫东; 张晓�; 周超; 李涛; 王建
Original assignee: 烽火通信科技股份有限公司
Priority date: 2019-06-05
Filing date: 2019-07-19
Publication date: 2020-12-10
Also published as: CN112052294A; CN112052294B

Abstract

Disclosed are a general data configuration method and system for service invocation, relating to the field of data configuration. The method comprises the steps of: defining a uniform data model for each sub-service, and establishing an iteration relationship for each sub-service required by a service to be invoked, wherein the iteration relationship comprises one initial sub-service and the remaining partner sub-services; after the configuration of one partner sub-service is completed, determining the initial sub-service according to the iteration relationship; and after the configuration of the initial sub-service is completed, if it is determined, according to the iteration relationship, that the configuration of all the remaining partner sub-services is also completed, forming service configuration information of said service. According to the present invention, a uniform data model is invoked by different services, thereby obviously simplifying a service configuration process; and according to the present invention, by means of the division of an initial sub-service, partner sub-services, and an iteration relationship therebetween, a whole service to be invoked can be configured according to the iteration relationship, regardless of any acquired sub-service of a service to be invoked.

Description

General data configuration method and system for business calling

Technical field

The invention relates to the field of data configuration, in particular to a general data configuration method and system for business invocation.

Background technique

The business configuration platform is mainly based on the idea of modularity, that is, the module is the most basic business unit; the realization of a business often requires the interaction between multiple modules (ie multiple sub-businesses).

However, the following defects exist when configuring services through the service configuration platform:

When configuring a business, the configuration staff first needs to understand all the sub-businesses required by the business and the relationship between the sub-businesses, and then the configuration staff needs to write codes corresponding to each sub-business and the relationship. This is not only the configuration process is more cumbersome and the error rate is high; it also requires high configuration personnel (the configuration personnel need to understand the code information of each sub-business, etc.), which limits the scope of use; at the same time, due to the code written by different configuration personnel The types are different, so the reusability of the code written by different configuration personnel is poor.

Summary of the invention

In view of the defects in the prior art, the technical problem solved by the present invention is: how to call a pre-set general data model to configure any service without writing code.

To achieve the above objectives, the general data configuration method for business invocation provided by the present invention includes the following steps: define a unified data model for each sub-business, establish an iterative relationship for each sub-business required by the business to be invoked, and in the iterative relationship Including an initial sub-business and other partner sub-businesses; when a partner sub-business is configured, the initial sub-business is determined according to the iterative relationship; when the initial sub-business is configured, if it is determined according to the iterative relationship that all other partner sub-businesses are configured When completed, the service configuration information of the service to be invoked is formed.

On the basis of the above technical solution, the method specifically includes the following steps: obtaining the data model of any sub-service required by the service to be invoked:

If the current sub-business is the initial sub-business and it is determined based on the iteration relationship that the data models of all partner sub-businesses are all configured, then the business configuration information of the service to be invoked is formed according to all the data models;

If the current sub-business is a partner sub-business, and the data model configuration of the initial sub-business is determined to be completed according to the iterative relationship, the data model of the initial sub-business is acquired.

On the basis of the above technical solution, each data model includes the association relationship between the sub-business and other sub-businesses. The process of creating a data model for each sub-business includes: classifying all sub-businesses according to functions, and one All sub-businesses in a category have the same association relationship; each category records the association relationship between the category and other categories; determine the category corresponding to the sub-business that needs to be created, and according to the association relationship between this category and other categories, After the sub-business is associated with other sub-businesses, the data model of the sub-business is formed.

On the basis of the above technical solution, the relationship between sub-businesses includes dependency and parent-child relationship. The dependency is that the sub-business only depends on or is dependent on one other sub-business, and the parent-child relationship is that the sub-business is controlled by multiple other sub-businesses. The business depends on, or is jointly dependent on a sub-business with other sub-businesses.

On the basis of the foregoing technical solution, both the initial sub-business and the partner sub-business may be non-essential sub-businesses, and the data model of the non-essential sub-business is issued after the configuration of the service configuration information of the calling service is completed.

The general data configuration system for business calling provided by the present invention includes a data model creation module and a data model calling module;

The data model creation module is used to: create a data model for each sub-business, and each data model includes the association relationship between the sub-business and other sub-businesses;

The data model invocation module is used for: when all the data models required by the service to be invoked are all configured, form the service configuration information of the service to be invoked according to all the data models.

On the basis of the above technical solution, the data model calling module includes a general iteration engine, an initial sub-business module and a partner sub-business module;

The general iterative engine is used to obtain all sub-business information required by the business to be invoked. All sub-business information includes an initial sub-business and other partner sub-businesses; all sub-businesses are formed according to the relationship between all sub-businesses Get the data model of any sub-business in all sub-businesses: if the data model of the initial sub-business is acquired, notify the initial sub-business module to start working; if the data model of the partner’s sub-business is acquired, notify the partner The sub-business module starts to work;

The initial sub-service module is used to: when it is determined according to the iterative relationship that the data models of all partner sub-services are configured, form the service configuration information of the service to be invoked according to all the data models;

The partner sub-business module is used to notify the starting sub-business module to start work when it is determined that the data model configuration of the initial sub-business is completed according to the iteration relationship.

On the basis of the above technical solution, all the sub-service information also includes non-essential sub-services that can be flexibly configured, and the data model of the non-essential sub-service is issued after the configuration of the service configuration information of the calling service is completed.

On the basis of the above technical solution, the workflow of the data model creation module includes: classifying all sub-businesses according to their functions, and all sub-businesses in a category have the same association relationship; each category records the relationship between this category and other categories. Determine the category corresponding to the sub-business that needs to be created, and form the data model of the sub-business after associating the sub-business with other sub-businesses according to the relationship between this category and other categories.

On the basis of the above technical solution, the association relationship between the sub-businesses in the data model created by the data model creation module includes a dependency relationship and a parent-child relationship, and the dependency relationship is that the child business only depends on or is dependent on one other child business, The parent-child relationship is that the sub-business is dependent on multiple other sub-businesses, or is dependent on one sub-business in common with other sub-businesses.

Compared with the prior art, the advantages of the present invention are:

The present invention can be invoked by different services through a unified data model that is pre-configured and has a very high reusability, so that the configuration personnel only need to know the sub-services required by the service, and there is no need to write each sub-service and the corresponding relationship. In turn, it not only significantly simplifies the business configuration process, and greatly reduces the error rate; but also has low requirements for configuration personnel, and has a wide range of use, which well realizes the unified management of platform data.

On this basis, the present invention divides the initial sub-business and partner sub-business, and its iterative relationship, so as to realize that no matter what sub-business of the business to be called is acquired, the entire business to be called can be configured by iterative relationship. Furthermore, the unified management of platform data is well realized, which is very suitable for promotion.

Description of the drawings

Figure 1 is a schematic diagram of a data model storage method in an embodiment of the present invention;

2 is a schematic diagram of a data model of a sub-service in an embodiment of the present invention;

Figure 3 is a schematic diagram of the association relationship between the data models in Figure 2;

4 is a schematic diagram of storing data in an embodiment of the invention;

Fig. 5 is a schematic diagram of an iteration process in an embodiment of the present invention;

FIG. 6 is a schematic diagram of the mapping relationship between the service to be invoked and the sub-service in the embodiment of the present invention.

Detailed ways

The present invention will be further described in detail below in conjunction with the drawings and embodiments.

The general data configuration method for business invocation in the embodiment of the present invention includes the following steps: define a data model for each sub-business that needs to be used (including soon to be used, to be used in the future, and to be used in the future), and each data model Including sub-business keywords, the relationship between the sub-business and other sub-businesses, and the business data of the sub-business; when all the data models required by the business to be called are all configured, it is formed according to all the data models Service configuration information of the service to be invoked.

Preferably, the association relationship between sub-businesses includes dependency relationship and parent-child relationship:

The dependency is that the sub-service depends on or is dependent on another sub-service, for example, the ARP table (the sub-service) depends on the out-interface table (other sub-services) through the index (foreign key) of the outbound interface;

The parent-child relationship is that the sub-business as the "father" is dependent on multiple other sub-businesses, or the sub-business and other sub-businesses are both regarded as "sons" and both depend on one "father" sub-business, such as multiple lag tables (other The child business "son") relies on the same interface table (the child business "father") through the interface index (foreign key).

The difference between the dependency relationship and the parent-child relationship is: the dependency relationship is a one-to-one correspondence, and the parent-child relationship is a one-to-many relationship.

Preferably, referring to Figure 1, the process of defining a data model for each sub-business that needs to be used includes:

All sub-businesses are classified according to function, that is, all sub-businesses in a category have the same association relationship, and the types of sub-businesses of different categories are different; each type of node (CLASS_TREE) records the association relationship between this category and other categories , As shown in the dependency relationship (DEPENDENCY_INFO) and parent-child relationship (FATHER_CHILDREN_INFO) in Figure 1. The dependency relationship includes the list of other classes (depender_list and observer_list) and specific information (DEPENDER_INFO and OBSERVER_INFO) that are dependent on and dependent on this class; the parent-child relationship includes the list of "father" and "son" classes (myfather_list and mychildren_list) and Specific information (FATHER__INFO and CHILDREN__INFO); other types of lists and specific information are related through the list node (list_node).

Determine the category corresponding to the sub-business that needs to be created, and determine whether the data model of the sub-business exists under this category. If it is, it proves that it has been created and ended; otherwise, the sub-business is based on the association relationship between this category and other categories. After being associated with other sub-businesses, the data model of the sub-business is formed and stored in the category.

It can be concluded that when there is no associated sub-business associated with the sub-business in other classes, the associated sub-business can be created in the above manner.

Referring to Figures 2 and 3, the data model of the sub-service in the embodiment of the present invention includes:

Route (routing table), including routing and the next piece of information, depends on Route_path (route protection table) through the foreign key path_id; that is, Route and Route_path are dependent;

Route_path (route protection table), including the number of route members, is dependent on multiple Route_path_mem (route member tables) through the same path_id, that is, Route_path (parent) and Route_path_mem (child) are parent-child relationships;

Route_path_mem, in addition to the parent-child relationship with Route_path, also includes next hop information, which depends on Nh (next hop table) through nh_id;

Nh, including next hop type and next hop information, depends on Arp (Address resolution protocol, address resolution protocol table) through ifindex (index);

Arp depends on if_net (outbound interface table) through the same ifindex;

if_net is dependent on Arp.

The present invention configures the data model for each sub-service in advance, so that the specific sub-service can be directly called when the service is configured; when the sub-service is called, other required services can be obtained according to the association relationship in the sub-service data model. Sub-business. For example, as shown in Figure 2, the L3PATH (layer three protection) service directly calls the Route and Route_path_mem write drivers; the L3UNI (layer three user) service directly calls the Nh, Arp and if_net write drivers; the ARP service directly calls the Arp and if_net write drivers.

It can be seen that the present invention can be called by different services through a pre-configured universal data model with very high reusability, so that the configuration personnel only need to know the sub-services required by the service, and there is no need to write each sub-service. And the code corresponding to the association relationship; in turn, it not only significantly simplifies the business configuration process and greatly reduces the error rate; but also has low requirements for configuration personnel, a wide range of applications, and a good realization of the unified management of platform data.

Preferably, after all the data models required for the service to be invoked are all configured, the process of forming the service configuration information of the service to be invoked according to all the data models includes:

Obtain all the sub-business information required by the service to be invoked. All sub-business information includes 1 initial sub-business (that is, the sub-business that initiates mapping to the business to be invoked) and other partner sub-businesses (that is, other sub-businesses that participate in mapping or notification). business).

As shown in Figure 4, the method of specifying the starting sub-business and the partner sub-business, and the iteration relationship can be specified by the business to be invoked, specifically:

Each sub-service (class A) contains two parts of information when registering:

(1) Mapping_starter_list information block: that is, some basic information of the sub-business as the starting sub-business, including the product callback function, the sub-business attribute bitmap that the business to be called is concerned with, and the dependent path_list linked list; because one sub-business may be used as multiple to be called The starting sub-business of the business, so the path_list needs to be traversed when the mapping is triggered.

(2) Mapping_parter_list information block: that is, when the sub-business is the partner sub-business of the current service to be called, it needs to notify the corresponding initial sub-business to trigger the mapping of the dependency chain information;

Path_list information in STARTER_MAPPING_INFO:

The collection of dependency chains where the partner sub-business information required for the assembly of the business to be called is located; when the platform gathers all partner sub-business information, it will traverse these dependency chain collections to obtain the attributes of all partner sub-businesses that are concerned by the business to be called Value, the final assembly and delivery of the product.

PARTER_MAPPING_INFO and its PATH_NODE information:

PARTER_MAPPING_INFO will store partner sub-business information, attribute bitmap information of interest, necessary and non-essential attribute information, product callback function, etc.; and PATH_NODE is essentially a path information that records the completeness from the partner sub-business to the initial sub-business information.

In actual use, the above process can be realized through the initial sub-business module and the partner sub-business module. The initial sub-business module stores initial sub-business information and all sub-businesses (that is, the initial sub-business and all partner sub-businesses) Path information; the partner sub-business module stores the complete path information used to notify the initial sub-business.

Next, referring to Figure 5, we need to obtain the data model of any sub-business in all sub-businesses:

When the data model of the initial sub-business is obtained, determine whether the data models of all other partner sub-businesses are configured according to the iterative relationship (cycle according to the iterative relationship, and obtain the data model information of a partner sub-business in each cycle until the traversal All partner sub-services), if yes, form the service configuration information of the service to be invoked according to all the data models; otherwise, it proves that the data model has not been fully configured, and needs to continue to wait;

When the partner sub-business is acquired, judge whether the data model of the initial sub-business is configured according to the iterative relationship. If so, obtain the data model of the initial sub-business (after entering the above-mentioned acquisition is the data model of the initial sub-business) Process); otherwise, it proves that the data model of the initial sub-business has not been configured, and it needs to continue to wait.

From this, it can be seen that the present invention can iterate out all partner sub-businesses through the initial sub-business for mapping; or notify the corresponding initial sub-business through the partner sub-business iteration, and then trigger the mapping by the initial sub-business. Therefore, the present invention completes the monitoring of all the configurations of all data models required by the business to be called through the "loop + recursion" mode of the initial sub-business and the partner sub-business; thus, it can meet the custom design and has a high degree of flexibility. The service to be called (because no matter what kind of sub-service is issued, the present invention has corresponding logic to iterate).

Preferably, because the design process of the service to be called often encounters multiple alternative scenarios (that is, there is a flexibly configurable "fork point" sub-service notified by the service to be called, that is, the service to be called is notified of the "fork point" "The attributes of sub-services are not necessary, and they may or may not exist). For example, the route NH (next hop) can be UNI (user side) or NNI (network side), and TUNNEL (tunnel selection table) can be FTN TUNNEL or TE TUNNEL, etc.; but in the actual scenario, only one type of service will be issued. If the normal process is iterated, it cannot be processed adaptively at this "fork point".

Therefore, the present invention also introduces sub-services with non-essential attributes that can be flexibly configured in all sub-service information (hereinafter referred to as non-essential sub-services, namely "fork point" sub-services); because non-essential sub-services will not hinder the to-be-called The configuration of the business, so the non-essential sub-business does not belong to the necessary business configuration information (that is, the non-essential sub-business is not in a parallel relationship with the initial sub-business and the partner sub-business), and the data model of the non-essential sub-business is in the business configuration of the business to be called After the information is configured, it can be issued. For example, a service to be called needs to call 3 sub-services, but the attribute of one of the sub-services is unnecessary. At this time, as long as the other two sub-services have been established, the non-essential sub-service can be issued.

The present invention realizes the rationality condition determination of the "fork point" sub-business through the above design, effectively solves this multiple-choice scenario, greatly increases the flexibility of business design, is concise and versatile, and is very in line with the idea of platformization. Well adapted to the needs of various products.

The following examples illustrate the formation process of service configuration information.

As shown in Figure 6, each circle in the left half of the area represents a sub-service, the left and right short arrows indicate the dependency between sub-services, and the long arrow indicates that multiple sub-services on the left jointly map a service to be called. In this scenario, GROUP (routing working group) is the initial sub-service, UNI (next hop on the user side), NNI (next hop on the network side), TUNNEL (tunnel selection table), FTN (FEC to NHLFE mapping table), TE_PROT (Traffic Engineering Protection Table) These sub-services all exist in more than one scenario, the consortium scenario, so they will be set as unnecessary sub-services to increase the flexibility of product design. The remaining sub-services are all partner sub-services. Although MEMBER (Working Group Member Table) and ARP are sub-services that do not need to be mapped for the service to be called, they must participate in the mapping as path partners.

The general data configuration system for business invocation in the embodiment of the present invention includes a data model creation module and a data model invocation module.

The data model creation module is used to: create a data model for each sub-business, and each data model includes the relationship between the sub-business and other sub-business; the relationship includes dependency and parent-child relationship, and the dependency is only Depends on or is dependent on one other sub-business, and the parent-child relationship is that the sub-business is dependent on multiple other sub-businesses, or is jointly dependent on one sub-business with other sub-businesses.

The specific work flow of the data model creation module includes: classify all sub-businesses according to their functions, and all sub-businesses in a category have the same association relationship; each category records the association relationship between this category and other categories; determine and need The category corresponding to the created sub-business is associated with other sub-businesses based on the association relationship between the sub-business and other sub-businesses to form the data model of the sub-business.

The data model calling module specifically includes the general iteration engine, the initial sub-business module and the partner sub-business module;

The general iterative engine is used to obtain all the sub-business information required by the service to be invoked. All sub-business information includes 1 starting sub-business, several partner sub-businesses, and several non-essential sub-businesses that can be flexibly configured; The relationship between the businesses forms the iterative relationship of all sub-businesses; to obtain the data model of any sub-business in all sub-businesses: if the data model of the initial sub-business is acquired, notify the initial sub-business module to start working; It is the data model of the partner's sub-business, and the partner's sub-business module is notified to start working; if the data model of the non-essential sub-business is obtained, the business configuration information of the service to be called is issued after the configuration is completed.

The initial sub-service module is used to form the service configuration information of the service to be invoked according to all the data models when it is determined that the data models of all partner sub-services are configured according to the iterative relationship.

It should be noted that when the system provided by the embodiment of the present invention performs inter-module communication, only the division of the above-mentioned functional modules is used as an example for illustration. In actual applications, the above-mentioned functions can be allocated by different functional modules as required. That is, the internal structure of the system is divided into different functional modules to complete all or part of the functions described above.

Further, the present invention is not limited to the above-mentioned embodiments. For those of ordinary skill in the art, without departing from the principle of the present invention, several improvements and modifications can be made, and these improvements and modifications are also regarded as the present invention. Within the scope of protection. The content not described in detail in this specification belongs to the prior art known to those skilled in the art.

Claims

A general data configuration method for business invocation, which is characterized in that the method includes the following steps: define a unified data model for each sub-business, establish an iterative relationship for each sub-business required by the business to be invoked, and the iterative relationship includes One initial sub-business and other partner sub-businesses; when a partner sub-business is configured, the initial sub-business is determined according to the iterative relationship; when the initial sub-business is configured, if it is determined according to the iteration relationship that the remaining partner sub-businesses are all configured , Then the service configuration information of the service to be invoked is formed.
The universal data configuration method for service invocation according to claim 1, wherein the method specifically includes the following steps: obtaining the data model of any sub-service required by the service to be invoked:

If the current sub-business is the initial sub-business and it is determined based on the iteration relationship that the data models of all partner sub-businesses are all configured, then the business configuration information of the service to be invoked is formed according to all the data models;

If the current sub-business is a partner sub-business, and the data model configuration of the initial sub-business is determined to be completed according to the iterative relationship, the data model of the initial sub-business is acquired.
The universal data configuration method for business invocation according to claim 1, wherein each data model includes the association relationship between the sub-business and other sub-businesses, and the data model creation method for each sub-business The process includes: classifying all sub-businesses according to their functions, and all sub-businesses in a category have the same association relationship; each category records the association relationship between this category and other categories; determining the category corresponding to the sub-business that needs to be created According to the association relationship between this class and other classes, after associating this sub-business with other sub-businesses, the data model of this sub-business is formed.
The universal data configuration method for business invocation according to claim 1, characterized in that: the association relationship between the sub-services includes a dependency relationship and a parent-child relationship, and the dependency relationship is that the sub-business only depends on or is dependent on one of the other children. Business, the parent-child relationship is that the sub-business is dependent on multiple other sub-businesses, or is dependent on one sub-business in common with other sub-businesses.
The general data configuration method for business invocation according to any one of claims 1 to 4, wherein the initial sub-business and partner sub-business can both be non-essential sub-business, and data of non-essential sub-business The model will be issued after the configuration of the service configuration information of the service to be called.
A general data configuration system for business calling, characterized in that: the system includes a data model creation module and a data model calling module;

The data model creation module is used to: create a data model for each sub-business, and each data model includes the association relationship between the sub-business and other sub-businesses;

The data model invocation module is used for: when all the data models required by the service to be invoked are all configured, form the service configuration information of the service to be invoked according to all the data models.
8. The general data configuration system for business invocation according to claim 6, wherein the data model invocation module includes a general iteration engine, an initial sub-business module and a partner sub-business module;

The general iterative engine is used to obtain all sub-business information required by the business to be invoked. All sub-business information includes an initial sub-business and other partner sub-businesses; all sub-businesses are formed according to the relationship between all sub-businesses Get the data model of any sub-business in all sub-businesses: if the data model of the initial sub-business is acquired, notify the initial sub-business module to start working; if the data model of the partner’s sub-business is acquired, notify the partner The sub-business module starts to work;

The initial sub-service module is used to: when it is determined according to the iterative relationship that the data models of all partner sub-services are configured, form the service configuration information of the service to be invoked according to all the data models;

The partner sub-business module is used to notify the starting sub-business module to start work when it is determined that the data model configuration of the initial sub-business is completed according to the iteration relationship.
The universal data configuration system for service invocation according to claim 7, characterized in that: the information of all sub-services also includes non-essential sub-services that can be flexibly configured, and the data model of the non-essential sub-services is the service to be invoked. The configuration information is delivered after the configuration is completed.
The universal data configuration system for business invocation according to any one of claims 6 to 8, wherein the workflow of the data model creation module includes: classifying all sub-businesses according to functions, and all sub-businesses in a category The association relationship of the sub-business is the same; each category records the association relationship between this category and other categories; determines the category corresponding to the sub-business that needs to be created, and based on the association relationship between this category and other categories, After the business is associated with other sub-businesses, the data model of the sub-business is formed.
The general data configuration system for business invocation according to any one of claims 6 to 8, characterized in that: the association relationship between the sub-businesses in the data model created by the data model creation module includes a dependency relationship and a parent-child relationship , The dependency relationship is that the sub-business only depends on or is dependent on one other sub-business, and the parent-child relationship is that the sub-business is dependent on multiple other sub-businesses, or is jointly dependent on one sub-business with other sub-businesses.