CN112052294B - General data configuration method and system for service call - Google Patents
General data configuration method and system for service call Download PDFInfo
- Publication number
- CN112052294B CN112052294B CN201910488130.7A CN201910488130A CN112052294B CN 112052294 B CN112052294 B CN 112052294B CN 201910488130 A CN201910488130 A CN 201910488130A CN 112052294 B CN112052294 B CN 112052294B
- Authority
- CN
- China
- Prior art keywords
- sub
- service
- data model
- services
- partner
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000013499 data model Methods 0.000 claims abstract description 119
- 230000008569 process Effects 0.000 claims abstract description 10
- 230000001419 dependent effect Effects 0.000 claims description 12
- 239000003999 initiator Substances 0.000 claims description 3
- 238000013507 mapping Methods 0.000 description 15
- 238000010586 diagram Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000007858 starting material Substances 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/285—Clustering or classification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a general data configuration method and a general data configuration system for service calling, and relates to the field of data configuration. The method comprises the following steps: defining a uniform data model for each sub-service, and establishing an iterative relationship for each sub-service required by the service to be called, wherein the iterative relationship comprises 1 initial sub-service and other partner sub-services; when one partner sub-service configuration is completed, determining an initial sub-service according to the iterative relationship; and after the initial sub-service configuration is completed, if the configuration of the rest partner sub-services is determined to be completed according to the iterative relationship, forming service configuration information of the service to be called. The invention can be called by different services through a unified data model, thereby obviously simplifying the service configuration process; and the invention can realize that the whole service to be called can be configured by the iterative relationship no matter any sub-service of the service to be called is obtained by dividing the initial sub-service, the partner sub-service and the iterative relationship thereof.
Description
Technical Field
The invention relates to the field of data configuration, in particular to a general data configuration method and a general data configuration system for service invocation.
Background
The service configuration platform is mainly based on a modular idea, namely a module is used as the most basic service unit; the implementation of a service often requires interaction between multiple modules (i.e., multiple sub-services).
However, the following disadvantages exist when configuring the service through the service configuration platform:
when configuring a service, firstly, a configuration person needs to know all sub-services required by the service and the association relationship between the sub-services, and then the configuration person needs to write codes corresponding to the sub-services and the association relationship. The configuration process is complicated, and the error rate is high; moreover, the requirement on configuration personnel is high (the configuration personnel needs to know the code information of each sub-service, and the like), and the application range is limited; meanwhile, because the types of codes written by different configurators are different, the reusability of the codes written by different configurators is poor.
Disclosure of Invention
Aiming at the defects in the prior art, the invention solves the technical problems that: how to call a preset general data model to configure any service under the condition of not writing codes.
In order to achieve the above object, the method for configuring universal data for service invocation provided by the present invention comprises the following steps: defining a uniform data model for each sub-service, and establishing an iterative relationship for each sub-service required by the service to be called, wherein the iterative relationship comprises an initial sub-service and other partner sub-services; after one partner sub-service is configured, determining an initial sub-service according to the iteration relation; and after the initial sub-service configuration is completed, if the configuration of the rest partner sub-services is determined to be completed according to the iteration relation, forming service configuration information of the service to be called.
On the basis of the technical scheme, the method specifically comprises the following steps: acquiring a data model of any sub-service required by a service to be called:
if the current sub-business is the initial sub-business and the data models of all partner sub-businesses are judged to be completely configured according to the iteration relation, business configuration information of the business to be called is formed according to all the data models;
and if the current sub-business is the partner sub-business and the data model configuration of the initial sub-business is judged to be completed according to the iterative relationship, acquiring the data model of the initial sub-business.
On the basis of the technical scheme, each data model comprises an incidence relation between the sub-service and other sub-services, and the process of creating the data model for each sub-service comprises the following steps: classifying all the sub-services according to functions, wherein the incidence relations of all the sub-services in one category are the same; the incidence relation between the class and other classes is recorded in each class; determining the category corresponding to the sub-service to be created, and associating the sub-service with other sub-services according to the association relationship between the category and other categories to form a data model of the sub-service.
On the basis of the technical scheme, the incidence relation between the sub-services comprises a dependency relation and a parent-child relation, the dependency relation is that the sub-service only depends on or is dependent on one other sub-service, and the parent-child relation is that the sub-service is dependent on a plurality of other sub-services or depends on one sub-service together with other sub-services.
On the basis of the technical scheme, both the initial sub-business and the partner sub-business can be unnecessary sub-businesses, and the data model of the unnecessary sub-businesses is issued after the business configuration information of the called business is configured.
The invention provides a general data configuration system for service calling, which comprises a data model establishing module and a data model calling module;
the data model creation module is to: creating a data model for each sub-service, wherein each data model comprises an incidence relation between the sub-service and other sub-services;
the data model calling module is used for: and when all the data models required by the service to be called are completely configured, forming service configuration information of the service to be called according to all the data models.
On the basis of the technical scheme, the data model calling module comprises a general iteration engine, an initial sub-business module and a partner sub-business module;
the generic iteration engine is to: acquiring all sub-service information required by a service to be called, wherein all the sub-service information comprises 1 initial sub-service and other partner sub-services; forming an iterative relationship of all the sub-services according to the incidence relationship among all the sub-services; acquiring a data model of any sub-service in all sub-services: if the data model of the initial sub-service is acquired, informing the initial sub-service module to start working; if the data model of the partner sub-business is acquired, informing the partner sub-business module to start working;
the start sub-service module is used for: when the data models of all partner sub-services are judged to be completely configured according to the iterative relationship, service configuration information of the service to be called is formed according to all the data models;
the partner sub-service module is used for: and when the data model configuration of the initial sub-service is judged to be completed according to the iteration relation, informing the initial sub-service module to start working.
On the basis of the technical scheme, the sub-service information also comprises non-necessary sub-services which can be flexibly configured, and the data model of the non-necessary sub-services is issued after the configuration of the service configuration information of the called service is completed.
On the basis of the technical scheme, the work flow of the data model creating module comprises the following steps: classifying all the sub-services according to functions, wherein the incidence relations of all the sub-services in one category are the same; the incidence relation between the class and other classes is recorded in each class; determining the category corresponding to the sub-service to be created, and associating the sub-service with other sub-services according to the association relationship between the category and other categories to form a data model of the sub-service.
On the basis of the technical scheme, the incidence relation between the sub-services in the data model created by the data model creating module comprises a dependency relation and a parent-child relation, wherein the dependency relation is that the sub-service only depends on or is dependent on one other sub-service, and the parent-child relation is that the sub-service is dependent on a plurality of other sub-services or depends on one sub-service together with other sub-services.
Compared with the prior art, the invention has the advantages that:
the invention can be called by different services through the pre-configured uniform data model with very high reusability, so that a configurator only needs to know the sub-services required by the service and does not need to write codes corresponding to the sub-services and the incidence relation; therefore, the service configuration process is remarkably simplified, and the error rate is greatly reduced; moreover, the requirement on configuration personnel is low, the application range is wide, and the platform data is well managed in a unified way.
On the basis, the invention realizes that the whole service to be called can be configured by the iterative relationship no matter any sub-service of the service to be called is obtained by dividing the initial sub-service, the partner sub-service and the iterative relationship thereof, thereby well realizing the unified management of platform data and being very suitable for popularization.
Drawings
FIG. 1 is a diagram illustrating a data model storage method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a data model of a sub-service in an embodiment of the present invention;
FIG. 3 is a schematic diagram of the relationship between data models of FIG. 2;
FIG. 4 is a schematic diagram of data management mode storage according to an embodiment of the present invention;
FIG. 5 is a schematic illustration of an iteration flow in an embodiment of the invention;
fig. 6 is a schematic diagram of a mapping relationship between a service to be called and a sub-service in the embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples.
The general data configuration method for service invocation in the embodiment of the invention comprises the following steps: defining a data model for each sub-service needing to be used (including about to be used, used later and possible to be used later), wherein each data model comprises a sub-service keyword, an incidence relation between the sub-service and other sub-services and service data of the sub-service; and when all the data models required by the service to be called are completely configured, forming service configuration information of the service to be called according to all the data models.
Preferably, the association relationship between the sub-services includes a dependency relationship and a parent-child relationship:
the dependency relationship is that the sub-service depends on or is dependent on one other sub-service, such as that the ARP table (the sub-service) depends on the egress interface table (other sub-service) through the index (foreign key) of the egress interface;
the parent-child relationship is that the child service is used as a "parent" and depended on by a plurality of other child services, or the child service and the other child services are both used as "children" and all depend on one "parent" child service, for example, a plurality of lag tables (other child services "children") depend on the same interface table (the child service "parent") through an interface index (external key).
The difference between the dependency relationship and the parent-child relationship is as follows: the dependency relationship is a one-to-one correspondence relationship, and the parent-child relationship is a one-to-many relationship.
Preferably, referring to fig. 1, the process of defining a data model for each sub-service that needs to be used includes:
classifying all the sub-services according to functions, namely that the incidence relation of all the sub-services in one class is the same, and the types of the sub-services in different classes are different; the node (CLASS _ TREE) of each CLASS records the association relationship between the CLASS and other classes, such as the DEPENDENCY relationship (DEPENDENCY _ INFO) and parent-child relationship (failure _ child _ INFO) in fig. 1. The dependency relationship comprises other class lists (dependency _ list and OBSERVER _ list) of dependent and depended class and specific information (DePENDER _ INFO and OBSERVER _ INFO); the parent-child relationship, in turn, includes a list of "parent" and "child" classes (myfather _ list and mychildrenjlist) and specific information (FATHER _ INFO and CHILDREN _ INFO); the list of other classes is associated with the specific information through a list node (list _ node).
Determining the class corresponding to the sub-service to be created, judging whether a data model of the sub-service exists in the class, if so, proving that the sub-service is created, and ending; otherwise, according to the association relationship between the class and other classes, the sub-service is associated with other sub-services to form a data model of the sub-service and store the data model in the class.
It can be derived that when there is no associated sub-service associated with the sub-service in the other class, an associated sub-service can be created in the manner described above.
Referring to fig. 2 and 3, the data model of the sub-service in the embodiment of the present invention includes:
route (routing table) including routing and next information, and depending on Route _ path (routing protection table) through foreign key path _ id; namely, the Route and the Route _ path are in a dependency relationship;
route _ path (Route protection table), including the number of Route members, is depended on by multiple Route _ path _ mem (Route member table) through the same path _ id, i.e. Route _ path (parent) and Route _ path _ mem (child) are in parent-child relationship;
route _ path _ mem, which, in addition to having a parent-child relationship with Route _ path, also includes next hop information, which depends on Nh (next hop table) by Nh _ id;
nh, including a next hop type and information of a next hop, depending on Arp (Address resolution protocol) through ifindex (index);
arp depends on if _ net (out-interface table) through the same ifindex;
if _ net, is depended on by Arp.
The invention enables the specific sub-service to be directly called when the service is configured in a mode of configuring the data model for each sub-service in advance; when the sub-service is called, other sub-services required to be used can be obtained according to the incidence relation in the sub-service data model. For example, as shown in fig. 2, the L3PATH (three-layer protection) service directly calls Route and Route _ PATH _ mem write drivers; the L3UNI (three-layer user) service directly calls the write drivers of Nh, arp and if _ net; the ARP service directly calls the ARP and if _ net write drivers.
Therefore, the method can be called by different services through the pre-configured general data model with very high reusability, so that a configurator only needs to know the sub-services required by the services without compiling codes corresponding to the sub-services and the incidence relation; therefore, the service configuration process is remarkably simplified, and the error rate is greatly reduced; and the requirement on configuration personnel is low, the application range is wide, and the unified management of platform data is well realized.
Preferably, after all the data models required by the service to be called are configured completely, the process of forming the service configuration information of the service to be called according to all the data models includes:
acquiring all sub-service information required by the service to be called, wherein the all sub-service information comprises 1 starting sub-service (namely, a sub-service for initiating mapping to the service to be called) and other partner sub-services (namely, other sub-services participating in mapping or notification).
Referring to fig. 4, the specifying mode and the iterative relationship of the starting sub-service and the partner sub-service may be specified by the service to be invoked itself, specifically:
each sub-service (class a) contains two pieces of information at registration:
(1) mapping _ starter _ list info block: the sub-service is used as some basic information of the initial sub-service, including a product callback function, a sub-service attribute bitmap to be called and selectively concerned by the service, and a dependent path _ list chain table; since one sub-service may serve as a starting sub-service for a plurality of services to be called, the path _ list needs to be traversed when the mapping is triggered.
(2) mapping _ parent _ list information block: when the sub-service is used as a partner sub-service of the current service to be called, the dependency chain information of the corresponding initial sub-service trigger mapping needs to be informed;
path _ list information in STARTER _ MAPPING _ INFO:
a set of dependency chains where partner sub-service information required for service assembly to be called is located; when the platform collects all the partner sub-business information, the dependency chain sets are traversed, attribute values concerned by the business to be called in all the partner sub-businesses are obtained, and finally, the issuing product is assembled at one time.
PARTER _ MAPPING _ INFO and its PATH _ NODE information:
the PARTER _ MAPPING _ INFO stores partner sub-service information, concerned attribute bitmap information, necessary and unnecessary attribute information, a product callback function and the like; and PATH _ NODE is essentially a PATH information recording the complete information from the partner sub-service to the originating sub-service.
In actual use, the process can be realized through the initial sub-business module and the partner sub-business module, wherein the initial sub-business module stores initial sub-business information and path information of all sub-businesses (namely the initial sub-business and all partner sub-businesses); the partner sub-service module stores complete path information for notifying the starting sub-service.
Referring next to fig. 5, it is necessary to obtain a data model of any sub-service in all sub-services:
when the data model of the initial sub-business is obtained, judging whether the data models of all the rest partner sub-businesses are configured or not according to the iteration relation (carrying out circulation according to the iteration relation, obtaining the data model information of one partner sub-business each time till traversing all the partner sub-businesses), if so, forming the business configuration information of the business to be called according to all the data models; otherwise, the data model is proved to be not completely configured and needs to be continuously waited;
when the partner sub-business is obtained, judging whether the data model of the initial sub-business is configured or not according to the iteration relation, if so, obtaining the data model of the initial sub-business (and then entering the process when the data model of the initial sub-business is obtained); otherwise, the data model of the initial sub-service is proved to be not configured and needs to continue waiting.
Therefore, the method can iterate all partner sub-businesses for mapping through the initial sub-business; or the partner sub-service iteration informs the corresponding initial sub-service, and the initial sub-service triggers mapping. Therefore, the invention completes the monitoring of all data models required by the service to be called in a mode of circulation and recursion of the initial sub-service and the partner sub-service; and further, the method can meet the requirements of the user-defined design and the service to be called with higher flexibility (because the method has corresponding logic for iteration no matter what sub-service is issued).
Preferably, since a more than one scenario is often encountered in the design process of the service to be invoked (i.e. there is a flexibly configurable "branch point" sub-service notified by the service to be invoked, that is, the service to be invoked notifies the attribute of the "branch point" sub-service as unnecessary, and may or may not be present), for example, the route NH (next hop) may be UNI (user side) or NNI (network side), the TUNNEL (TUNNEL selection table) may be FTN TUNNEL or TE TUNNEL, etc.; however, in an actual scene, only one type of service is issued, and if a common flow iterates, adaptive processing cannot be performed at the "bifurcation point".
Therefore, the invention introduces the sub-service with the non-necessary attribute (hereinafter referred to as non-necessary sub-service, namely the sub-service of a bifurcation point) which can be flexibly configured into all the sub-service information; the unnecessary sub-business does not belong to the necessary business configuration information (namely the unnecessary sub-business is not in parallel relation with the initial sub-business and the partner sub-business), and the data model of the unnecessary sub-business can be issued after the business configuration information of the business to be called is configured. For example, a service to be invoked needs to invoke 3 sub-services, but the attribute of one of the sub-services is unnecessary, and at this time, the unnecessary sub-service can be issued as long as the other 2 sub-services are already established.
The invention realizes the judgment of the rationality condition of the branch point sub-service through the design, effectively solves the problem of one-out-of-multiple scene, greatly increases the flexibility of service design, is simple and universal, quite accords with the platform idea, and well adapts to the requirements of various products.
The following illustrates the formation flow of the service configuration information.
Referring to fig. 6, each circle box of the left half area represents a sub-service, the left and right short arrows represent the dependency relationship between the sub-services, and the long arrow represents that a plurality of sub-services on the left side map a service to be called together. In this scenario, GROUP (routing working GROUP) is the initial sub-service, and these sub-services all exist in a multiple-out-of-one scenario, i.e. a complex scenario, UNI (user side next hop), nnil (TUNNEL selection table), FTN (FEC to NHLFE mapping table), and TE _ PROT (traffic engineering protection table), and thus are set as unnecessary sub-services to increase flexibility of product design. The rest sub-services are partner sub-services, and although the MEMBER (working group MEMBER table) and the ARP are sub-services which do not need mapping of the service to be invoked, the sub-services need to participate in mapping as path partners.
The general data configuration system for service invocation in the embodiment of the invention comprises a data model creation module and a data model invocation module.
The data model creation module is to: creating a data model for each sub-service, wherein each data model comprises an incidence relation between the sub-service and other sub-services; the association relationship comprises a dependency relationship and a parent-child relationship, the dependency relationship is that the child service depends on or is dependent on only one other child service, and the parent-child relationship is that the child service is dependent on a plurality of other child services or depends on one child service together with other child services.
The specific work flow of the data model creating module comprises the following steps: classifying all sub-services according to functions, wherein the incidence relations of all sub-services in one class are the same; the incidence relation between the class and other classes is recorded in each class; determining the category corresponding to the sub-service to be created, and associating the sub-service with other sub-services according to the association relationship between the category and other categories to form a data model of the sub-service.
The data model calling module is used for: and when all the data models required by the service to be called are completely configured, forming service configuration information of the service to be called according to all the data models.
The data model calling module specifically comprises a general iteration engine, an initial sub-business module and a partner sub-business module;
the generic iteration engine is to: acquiring all sub-service information required by a service to be called, wherein the sub-service information comprises 1 initial sub-service, a plurality of partner sub-services and a plurality of non-necessary sub-services which can be flexibly configured; forming an iterative relationship of all the sub-services according to the incidence relationship among all the sub-services; acquiring a data model of any sub-service in all sub-services: if the data model of the initial sub-service is acquired, informing the initial sub-service module to start working; if the data model of the partner sub-business is acquired, informing the partner sub-business module to start working; and if the acquired data model of the unnecessary sub-service is not the data model of the necessary sub-service, the service configuration information of the service to be called is issued after the configuration is completed.
The initiator sub-service module is used for: and when the data models of all the partner sub-services are judged to be completely configured according to the iterative relationship, forming service configuration information of the service to be called according to all the data models.
The partner sub-business module is used for: and when the data model configuration of the initial sub-service is judged to be completed according to the iteration relation, informing the initial sub-service module to start working.
It should be noted that: in the system provided in the embodiment of the present invention, when performing inter-module communication, only the division of each functional module is illustrated, and in practical applications, the above function distribution may be completed by different functional modules as needed, that is, the internal structure of the system is divided into different functional modules to complete all or part of the above described functions.
Further, the present invention is not limited to the above-mentioned embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and these modifications and improvements are also considered to be within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.
Claims (8)
1. A method for generic data configuration for service invocation, the method comprising the steps of: defining a uniform data model for each sub-service, and establishing an iterative relationship for each sub-service required by the service to be called, wherein the iterative relationship comprises an initial sub-service and other partner sub-services; when one partner sub-service configuration is completed, determining an initial sub-service according to the iterative relationship; after the initial sub-business configuration is completed, if the configuration of the other partner sub-businesses is determined to be completed according to the iteration relation, business configuration information of the business to be called is formed;
the method specifically comprises the following steps: acquiring a data model of any sub-service required by a service to be called:
when the data model of the initial sub-service is obtained, judging whether the data models of all the rest partner sub-services are configured or not according to the iteration relation, if so, forming service configuration information of the service to be called according to all the data models; otherwise, the data model is proved to be not completely configured and needs to be continuously waited;
when the data model of the partner sub-business is obtained, judging whether the data model of the initial sub-business is configured or not according to the iterative relationship, if so, obtaining the data model of the initial sub-business; otherwise, the data model of the initial sub-service is proved to be not configured and needs to continue waiting.
2. The method according to claim 1, wherein each data model includes an association relationship between the sub-service and other sub-services, and the process of creating the data model for each sub-service includes: classifying all sub-services according to functions, wherein the incidence relations of all sub-services in one class are the same; the incidence relation between the class and other classes is recorded in each class; determining the category corresponding to the sub-service to be created, and associating the sub-service with other sub-services according to the association relationship between the category and other categories to form a data model of the sub-service.
3. The method for generic data configuration for service invocation of claim 1, wherein: the incidence relation between the sub-services comprises a dependency relation and a parent-child relation, wherein the dependency relation is that the sub-service depends on or is dependent on one other sub-service, and the parent-child relation is that the sub-service is dependent on a plurality of other sub-services or depends on one sub-service together with other sub-services.
4. The method according to any one of claims 1 to 3, wherein the initiator sub-service and the partner sub-service are both non-essential sub-services, and the data model of the non-essential sub-services is issued after the configuration of the service configuration information of the invoked service is completed.
5. A generic data configuration system for service invocation, characterized by: the system comprises a data model establishing module and a data model calling module;
the data model creation module is to: creating a data model for each sub-service, wherein each data model comprises an incidence relation between the sub-service and other sub-services;
the data model calling module is used for: after all data models required by the service to be called are completely configured, forming service configuration information of the service to be called according to all the data models;
the data model calling module comprises a general iteration engine, an initial sub-business module and a partner sub-business module;
the generic iteration engine is to: acquiring all sub-service information required by a service to be called, wherein all the sub-service information comprises 1 initial sub-service and other partner sub-services; forming an iterative relationship of all the sub-services according to the incidence relationship among all the sub-services; acquiring a data model of any sub-service in all sub-services: if the data model of the initial sub-service is acquired, informing the initial sub-service module to start working; if the data model of the partner sub-business is acquired, informing the partner sub-business module to start working;
the initiator sub-service module is used for: judging whether the data models of all the rest partner sub-services are configured or not according to the iteration relation, if so, forming service configuration information of the service to be called according to all the data models; otherwise, the data model is proved to be not completely configured and needs to be continuously waited;
the partner sub-business module is used for: judging whether the data model of the initial sub-service is configured or not according to the iteration relation, and if so, acquiring the data model of the initial sub-service; otherwise, the data model of the starting sub-service is proved to be not configured and needs to continue waiting.
6. The universal data configuration system for service invocation according to claim 5, wherein: and the data model of the unnecessary sub-service is issued after the configuration of the service configuration information of the service to be called is completed.
7. A generic data configuration system for service invocation according to any of claims 5 to 6, characterized by: the work flow of the data model establishing module comprises the following steps: classifying all sub-services according to functions, wherein the incidence relations of all sub-services in one class are the same; the incidence relation between the class and other classes is recorded in each class; determining the category corresponding to the sub-service to be created, and associating the sub-service with other sub-services according to the association relationship between the category and other categories to form a data model of the sub-service.
8. A generic data configuration system for service invocation according to any of claims 5 to 6, characterized by: the incidence relation between the sub-services in the data model created by the data model creating module comprises a dependency relation and a parent-child relation, wherein the dependency relation is that the sub-service only depends on or depends on one other sub-service, and the parent-child relation is that the sub-service is dependent on a plurality of other sub-services or depends on one sub-service together with other sub-services.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910488130.7A CN112052294B (en) | 2019-06-05 | 2019-06-05 | General data configuration method and system for service call |
| PCT/CN2019/096630 WO2020244033A1 (en) | 2019-06-05 | 2019-07-19 | General data configuration method and system for service invocation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910488130.7A CN112052294B (en) | 2019-06-05 | 2019-06-05 | General data configuration method and system for service call |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112052294A CN112052294A (en) | 2020-12-08 |
| CN112052294B true CN112052294B (en) | 2023-01-31 |
Family
ID=73609520
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910488130.7A Active CN112052294B (en) | 2019-06-05 | 2019-06-05 | General data configuration method and system for service call |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112052294B (en) |
| WO (1) | WO2020244033A1 (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103095504A (en) * | 2013-01-25 | 2013-05-08 | 山东广电网络有限公司济南分公司 | Management system of wired network basic resources |
| CN103825755A (en) * | 2013-11-27 | 2014-05-28 | 广东电网公司电力调度控制中心 | Power secondary system modeling method and system |
| CN106776995A (en) * | 2016-12-06 | 2017-05-31 | 北京神舟航天软件技术有限公司 | A kind of tree-like acquisition technique of structural data based on MDA |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103186834A (en) * | 2011-12-31 | 2013-07-03 | 阿里巴巴集团控股有限公司 | Method and device of business process configuration |
| CN104270257B (en) * | 2014-09-10 | 2017-11-07 | 烽火通信科技股份有限公司 | NE-level webmaster business configuration adaption system and method based on PB and XPATH |
| US9886270B2 (en) * | 2015-04-17 | 2018-02-06 | Sap Se | Layered business configuration |
| CN105959135B (en) * | 2016-04-28 | 2019-01-04 | 烽火通信科技股份有限公司 | A kind of single-deck configuration system and method for the PTN device based on general service model |
-
2019
- 2019-06-05 CN CN201910488130.7A patent/CN112052294B/en active Active
- 2019-07-19 WO PCT/CN2019/096630 patent/WO2020244033A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103095504A (en) * | 2013-01-25 | 2013-05-08 | 山东广电网络有限公司济南分公司 | Management system of wired network basic resources |
| CN103825755A (en) * | 2013-11-27 | 2014-05-28 | 广东电网公司电力调度控制中心 | Power secondary system modeling method and system |
| CN106776995A (en) * | 2016-12-06 | 2017-05-31 | 北京神舟航天软件技术有限公司 | A kind of tree-like acquisition technique of structural data based on MDA |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020244033A1 (en) | 2020-12-10 |
| CN112052294A (en) | 2020-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7688960B1 (en) | Method and system for separating business and device logic in a computing network system | |
| US6751659B1 (en) | Distributing policy information in a communication network | |
| CN100409710C (en) | Method and system for checking configuration of nodes in telecommunications network | |
| WO2021073433A1 (en) | Monitoring method and device, server, and storage medium | |
| CN107104824A (en) | A kind of network topology determines method and apparatus | |
| US11361027B2 (en) | Historical state management in databases | |
| CN108616402B (en) | Management method and system of remote equipment | |
| JP2004208297A (en) | System and method for rapid selection of device in tree topology network | |
| CN110351111A (en) | A kind of subscription processing method, network node and customer data base | |
| US20120127896A1 (en) | Method and device for implementing group intelligent service of mobile virtual private network | |
| US5483585A (en) | Apparatus for managing an element manager for a telecommunications switch | |
| CN101677441B (en) | Method, device and system of authorization control | |
| EP3637690B1 (en) | Service configuration-driven flow table method and device | |
| CN108733698A (en) | A kind of processing method and background service system of log information | |
| JPH09509541A (en) | Data storage | |
| CN111488515A (en) | Information query method, device, equipment and storage medium | |
| CN112181441A (en) | Construction and application deployment method and system using chaos engineering and gray scale release | |
| CN109379764A (en) | File transmitting method and device | |
| CN112052294B (en) | General data configuration method and system for service call | |
| CN113891374B (en) | Fault network element identification method, device and equipment | |
| US7738640B1 (en) | Methods for reconciling discrepancies in circuit information among various telecommunication network management systems | |
| CN111865655A (en) | ARP table configuration method and system for service board card | |
| US20130024458A1 (en) | System and Method for Efficiently Representing and Managing A Computer Facility | |
| CN112583622B (en) | Method and system for reporting fault event information | |
| CN100375442C (en) | Communication network management and processing system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240625 Address after: 430000 No. 6, High-tech Fourth Road, Donghu High-tech Development Zone, Wuhan City, Hubei Province Patentee after: FIBERHOME TELECOMMUNICATION TECHNOLOGIES Co.,Ltd. Country or region after: China Patentee after: Wuhan Changjiang Computing Technology Co.,Ltd. Address before: 430000 No. 6, High-tech Fourth Road, Donghu High-tech Development Zone, Wuhan City, Hubei Province Patentee before: FIBERHOME TELECOMMUNICATION TECHNOLOGIES Co.,Ltd. Country or region before: China |