CN116185524A

CN116185524A - Configuration distribution system

Info

Publication number: CN116185524A
Application number: CN202310100852.7A
Authority: CN
Inventors: 陆晓浒
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2023-02-07
Filing date: 2023-02-07
Publication date: 2023-05-30

Abstract

The application discloses a configuration distribution system, which belongs to the field of data processing. The system comprises: the management module is used for generating a configuration background by using an extensible background template based on the design result, and the configuration background is used for providing an interface for calling data; wherein the design result is obtained based on a design condition; the background module is used for configuring background management data; and the distribution module is used for acquiring and distributing the data of the configuration background.

Description

Configuration distribution system

Technical Field

The application belongs to the field of data processing, and particularly relates to a configuration distribution system.

Background

The form type low-code platform in the related art generally pulls the front end to generate a form interface, or defines a data structure first to complete data modeling, so that the creation of a configuration form by using the low-code platform in the related art is relatively complicated and time-consuming, and the low-code platform or technology in the related art is relatively difficult in supporting various distribution strategies of configuration.

Therefore, how to improve the efficiency of creating configuration forms and the configuration distribution capability at the same time becomes a problem to be solved.

Disclosure of Invention

The embodiment of the application aims to provide a configuration distribution system which can solve the problems that in the related art, the creation of a configuration form based on a low-code platform is complicated and time-consuming, and the configuration distribution capability is low.

An embodiment of the present application provides a configuration distribution system, including:

the management module is used for generating a configuration background by using an extensible background template based on a design result, wherein the configuration background is used for providing an interface for calling data; wherein the design result is obtained based on a design condition;

the background module is used for configuring background management data;

and the distribution module is used for acquiring and distributing the data of the configuration background.

In the embodiment of the application, the management module can quickly generate the configuration background by using the extensible background template based on the design result, then the data of the configuration background is managed by the background module, and the distribution module acquires and distributes the data by using the quickly generated configuration background, so that the complete flow of the configuration distribution of the background data and the construction of unified intelligent configuration distribution capability are realized, the efficiency of the configuration distribution of the background data is improved, and the configuration distribution capability is also improved.

Drawings

FIG. 1 is a schematic diagram of a configuration distribution system provided in an embodiment of the present application;

FIG. 2 is a schematic flow diagram of background rendering provided in an embodiment of the present application;

FIG. 3 is a flow diagram of a distribution process provided by an embodiment of the present application;

fig. 4 is a schematic flow chart of a design background provided in an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type and not limited to the number of objects, e.g., the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.

The configuration distribution system provided by the embodiment of the application is described in detail below through specific embodiments and application scenes thereof with reference to the accompanying drawings.

Fig. 1 is a schematic structural diagram of a configuration distribution system provided in an embodiment of the present application, and as shown in fig. 1, the configuration distribution system 100 includes:

a management module 110, configured to generate a configuration background using an extensible background template based on a design result, where the configuration background is configured to provide an interface for retrieving data; wherein the design result is obtained based on a design condition;

a background module 120 for managing data using the configuration background;

and the distribution module 130 is used for acquiring and distributing the data of the configuration background.

Alternatively, the management module may be used by a developer.

Alternatively, the developer may make the configuration background using module capabilities (no code).

Alternatively, the developer may design a background based on the form elements by the form designer, configure the background elements, and use the design conditions.

Alternatively, the form designer may derive the design result based on the design condition.

Alternatively, the developer may apply low code capabilities through an extensible back-end template, with a form designer, and may quickly generate the configuration back-end, such as within 1 minute or 2 minutes or 3 minutes.

Alternatively, the configuration background may provide an interface to invoke the data.

Alternatively, the background module may be used by the operator.

Alternatively, the operations may use the configuration background generated by the management module to generate and manage background data.

Alternatively, the configuration background may maintain a data management operation record of the operation.

Alternatively, the distribution module may be used by a third party developer.

Alternatively, third party developers may obtain and distribute data for the background operations.

Alternatively, third party developers may use configuration daemons to invoke data of the background operations.

Alternatively, the distribution module may provide an interface, such as http or dubbo, to accurately give the background data to third party users, such as An Zhuoduan or H5 or servers.

Optionally, the design condition includes at least one of: condition code number, condition description, condition field type, condition value, condition expansion rule, automatic matching or not, automatic matching method and automatic matching field.

Optionally, the background meeting the user requirement can be configured by configuring the background element when the background is configured.

Alternatively, the design condition is one of the elements of the background, which can be used to control the configuration distribution policy.

Optionally, the form designer also needs to complete the configuration of the following elements: background code number, background name, background configuration (e.g., configuration name, configuration field, configuration type, and configuration component high-level settings, etc.), background high-level settings (e.g., operation function selection, and at most configuring several pieces of data, etc.), background authority settings and distribution settings (e.g., at most returning N pieces of data, whether the data is assembled with other background assembly distribution results, etc.), and the like.

Alternatively, after adding the data of the configuration background, the data may be stored as a conditional code corresponding to the key value of the actual configuration content.

For example, if the actual configuration content is a text class or a single-choice class, the corresponding condition code number may be "_strImei": 123"; if the actual configuration content is multi-choice, the corresponding condition code number can be "_strImei": 123,12345"; if the actual configuration content is a numerical class, the corresponding conditional code may be "_napsplice": ">13, <20".

Alternatively, the developer may make the configuration background through a low code platform.

Alternatively, different configuration backgrounds may correspond to different condition codes.

Alternatively, the condition specification may include a correspondence between the condition code number and the actual configuration content.

Alternatively, the condition field type may include a text class, or a multi-choice class, or a radio choice class, or a numeric comparison class, or the like.

Alternatively, the condition value may include a value of a condition field.

Alternatively, the condition expansion rule may include at least one of limiting the number of the call conditions, limiting an input manner of the call conditions, and limiting an input parameter of the call conditions.

Alternatively, the input parameter limiting the call condition may include inputting an independent identification (hash's salt value or token of a different service).

Alternatively, the limit on the amount of data per call may be 3 call conditions or 2 call conditions or 1 call condition.

For example, an identifier corresponding to the type of data to be scheduled must be input.

For example, in order to acquire data of month 12 of 2022, the user may input the character "202212" or input the language description "please display data of month 12 of 2022", and retrieve data generated at month 12 of 2022 from the stored data.

Alternatively, whether or not the match is automatic may provide an option of automatic and non-automatic matching.

Alternatively, the method of automatic matching may include numerical comparison, text full matching, text end matching, multi-choice matching, hash matching, and the like.

Optionally, the configuration background can automatically acquire the values of the corresponding condition fields in the input parameters according to the condition expansion rules, and calculate by using an automatic matching method to screen the content meeting the conditions.

Alternatively, the auto-match field may include a corresponding condition field in the entry.

Optionally, based on the call condition set by the configuration background through the condition expansion rule, the configuration background can automatically identify and match the corresponding data.

For example, the call condition may be time; a fixed drop down box that may be based on the settings; the stored data may include a generated device log of month 2022, 9, 10, 11, and 12; the drop down box may include the following options: the characters "202209", "202210", "202211" and "202212" may be displayed when the user selects the drop-down box when retrieving data, and may indicate that the user retrieves the generated device log of month 2022 and 9 when the user selects the option "202209".

Optionally, the limiting the input parameters of the call condition may include limiting the user to input only parameters meeting the requirement when inputting the call condition, such as only a numerical identifier corresponding to the data to be called, or only a string identifier corresponding to the data to be called.

Alternatively, the call condition may include the setting of one table field of the configuration background.

Alternatively, the data conforming to the call condition may be filtered out in accordance with a request input by the user for the call condition.

Optionally, the management module may obtain the design result and the background data of the form designer, and render the background that can be directly operated and used in the design background through the template engine.

Alternatively, the design conditions may include a description of the data, data characterizing what the data corresponds to in the background of the configuration, or the name of the data, or a description of the data.

Alternatively, the description of the data may include the name or category of the data.

For example, the description of the data may include configuring a domain name stored in the background;

for example, the description of the data may include configuring a usage log stored in the background and a date corresponding to each usage log.

Alternatively, the design conditions may include a data type of the data.

Alternatively, the data type may include text, numerical values, or character strings, among others.

Alternatively, the design conditions may include setting rules of the call conditions of the data.

Alternatively, in the case of configuring a background storage usage log, each usage log has a corresponding date, the setting rule of the call condition of the data may be set as: the user obtains a use log corresponding to the date through inputting the date; then when the user invokes the data, the usage log for one month may be invoked by selecting the date corresponding to the usage log for one month, or the user may select the usage log for machine a for one month.

Optionally, in the case of configuring the background storage domain names, each domain name has a corresponding device, and the setting rule of the data call condition may be set as follows: a user obtains a domain name or a domain name range or a domain name list corresponding to the equipment identifier or the equipment identifier range through inputting the equipment identifier or the equipment identifier range; when the user invokes the data, the domain name or domain name range or domain name list corresponding to the device identifier or the device identifier range can be obtained through inputting the device identifier or the device identifier range.

Optionally, the setting rule of the data call condition may further set that the user can only set 2 call conditions at most at a time, for example, the user can only input 2 call conditions at a time, and if a certain date and a certain device, the user calls a usage log of a certain device in a certain date correspondence, and cannot simultaneously input more than 2 call conditions, for example, cannot directly call a usage log of a certain device in a certain date correspondence in a certain area network.

Alternatively, when the background storage data is configured, the condition for the user to call the data may be set as time, or the data source, or the like.

Alternatively, the design condition may include at least one of a description of the data, a data type of the data, and a setting rule of a call condition of the data.

In the embodiment of the application, the design result and background data of the form designer are obtained through the management module, and the background which can be directly operated and used for designing the background is rendered through the template engine; by determining the condition expansion rule, various configuration background meeting the requirements can be flexibly developed based on the requirements, and the flexibility of generating the configuration background is improved.

Optionally, the management module is further configured to configure a permission role code and a name, and when the configuration background is generated, the permission role group to which the configuration background belongs is specified based on the permission role code and the name.

Alternatively, the rights may be a kind of secured access to the configuration background resource, such as if the user wants to access the A resource if the user has to have access rights to the A resource.

Alternatively, a role may be a collection of rights, or a carrier of rights.

For example, roles in a forum system may include "superadministrator" and "territory", rights may include "territory" may manage posts and users within a edition, etc., and when a user is granted these rights, the rights need not be granted directly to the user, and the role of "territory" may be granted to the user.

Alternatively, the rights may be given to the user by a role, e.g. the user has a certain right because the user plays a certain role.

Optionally, the authority roles may be the basis for configuring the background function authority setting, which is equivalent to grouping users, and the users correspond to the corresponding authority roles, so that all the function authorities given by the authority roles are provided.

Alternatively, the authority role code may include a numeric code, such as 0, or 1, or 2, or 4, etc., or an alphabetical code, such as a or B, or C, etc.

Alternatively, the authority role names may include a system administrator (System Administrator, SA), a database administrator (Database Administrator, DA), a storage administrator (Storage Administrator, STA), and the like.

Alternatively, the user may be associated with the rights through a role.

For example, if the user applies for the novel operation role authority, the user may have all novel operation role authorities under the management module.

For example, if the user applies for the role authority of the novel of the background a, the user may have the role authority of the novel of the background a.

Alternatively, different users may correspond to different roles.

Alternatively, different roles may have different rights.

For example, a user may have several roles, each with several rights, and an authorization model of "user-role-rights" may be constructed in which there is a generally many-to-many relationship between users and roles, and between roles and rights.

Alternatively, when the number of users is very large, each user of the system needs to be authorized (role-granted) one by one, which is cumbersome. Users may be grouped, with multiple users within each user group. In addition to authorizing the user, the user group may be authorized. All rights possessed by a user are the sum of the rights possessed by the user in the individual and the rights possessed by the user group in which the user is located.

Alternatively, the operation rights of different backend owned by the operation can be managed by setting a rights role group.

Optionally, when the background designer is used for creating the configuration background, the authority role group to which the configuration background belongs can be designated, and when the configuration background is operated, the authority system can be firstly cleared to inquire the authority role code number and the authority role name owned by the user, confirm whether the user has the authority of the configuration background or not, and control the operation of the configuration background.

For example, when the background designer is used for creating the configuration background, the authority role group to which the configuration background belongs can be designated as B, and when the configuration background is operated, the authority system can be firstly inquired that the authority role owned by the user is A, B, C, and the user is confirmed to have the authority for configuring the background B, so that the operation of the configuration background B can be controlled.

For example, when the background designer is used for creating the configuration background, the authority role group to which the configuration background belongs can be designated as D, and when the configuration background is operated, the authority system can be firstly queried for the authority role which the user owns as A, B, C, so that the user is confirmed to have no authority for configuring the background D, and the operation of the configuration background D cannot be controlled.

Optionally, the configuration background may determine, in real time, the authority role group to which the operation belongs.

Optionally, the data may be managed based on the management rights corresponding to the rights role group to which the operation belongs, and the data management operation command of the operation.

Optionally, it may be checked at the server whether the logged-in operation has a viewing or operating authority of a certain page.

Alternatively, if the logged-in operation does not have the viewing or operation authority of the page, the corresponding data management operation button and data may not be displayed.

Optionally, if the logged operation has the viewing or operating authority of the page, the corresponding data management operation button and data may be displayed.

For example, the authority role group includes A, B, C, D; wherein, the management authority corresponding to A comprises: only allowing viewing of the data; the management authority corresponding to the B comprises the following steps: allowing viewing of the data and augmentation of the data; the management authority corresponding to C comprises: allowing viewing of data, adding data, copying data, and modifying data; the management authority corresponding to the D comprises permission to view data, add data, copy data, modify data and delete data; if the operation is carried out by configuring background management data, displaying an interface configuring the background, wherein the interface comprises a plurality of data management operation buttons which respectively correspond to different data management operation commands; if the authority role group is determined to be C, the data management operation button corresponding to the data management operation command of deleting data is in an 'unselected' state, the data management operation buttons of several data management operation commands of checking data, adding data, copying data and modifying data are in a 'selectable' state, and the operation can perform data management operations such as checking, adding, copying or modifying data by selecting the buttons.

In the embodiment of the application, the classification management and control of the background permission are realized by designing the permission role group, so that the efficiency of configuration and distribution of the background data is improved, and the configuration and distribution capacity is improved.

Optionally, the management module is specifically configured to:

based on the design result, configuring a background name, a unique identifier, a permission role group, a condition field and expansion thereof, a content field and expansion function thereof, a distribution strategy and interface configuration through a background designer.

Alternatively, the developer may configure the background name through the background designer based on the design result, and the background name may be the name of the configuration background, such as configuration background a, or configuration background B, or configuration background C, and the like.

Alternatively, the developer may configure the unique identifier through the background designer based on the design results, and different configuration backgrounds may configure different identifiers.

Alternatively, the developer may configure the authority character code and the authority character name of the authority character group through the background designer based on the design result.

Alternatively, the developer may configure the condition field and its extensions through the background designer based on the condition field type and the condition extension rules.

Alternatively, the developer may configure the content fields and their extended functionality through a background designer based on the design results.

Optionally, the expansion can be used to supplement each component, such as checking the size of a picture, checking the length of a text, checking the regularity, mounting an associated form, configuring remote drop-down frame data, and the like.

Alternatively, the developer may configure the distribution policy by a background designer based on the design results.

Alternatively, the distribution policy may include data assembly, data selection, data distribution, and the like.

Alternatively, the developer may interface configuration of the configuration background through the background designer based on the design results.

Alternatively, the interface configuration may include button display or hiding, custom skip and custom buttons, and the like.

Alternatively, the background configuration table may be stored in MySQL.

Alternatively, the background configuration table may include a background name, code, rights, interface display, interface logic, and distribution policy configuration, etc.

Alternatively, a background field configuration table may be stored in MySQL.

Optionally, the background field configuration table may include the name of the field, the field code number, the field type, and the component high-level extensions, among others.

Alternatively, the role of the background design may include providing a form interface, entering the condition fields and logic required after generation.

In the embodiment of the application, the design of the configuration background is realized through a background designer based on the design result; and storing data by using a MySQL database, and preparing for subsequent data distribution.

Optionally, the background module is specifically configured to:

and inquiring and analyzing the background configuration, the field configuration and the background data of the configuration background through a page renderer, and rendering the configuration background through the background template.

Optionally, the operation can query and analyze the background configuration, the field configuration and the background data through the page renderer, and finally, the corresponding configuration background can be rendered by using a unified background template.

Optionally, the rendering may include a server side rendering (Server Side Render, SSR).

Fig. 2 is a schematic flow chart of background rendering according to an embodiment of the present application. As shown in fig. 2, the process includes the steps of:

step 211, accessing a configuration background address;

optionally, first operating an address that can access the configuration background;

step 212, inquiring background configuration, field configuration and background data;

optionally, after accessing the address of the configuration background, the database may be queried for background configuration, field configuration and background data;

step 213, returning query data;

optionally, the query data may be returned from the database after the database queries the background configuration, field configuration, and background data;

step 221, rendering a background frame according to the background configuration and the field configuration;

optionally, the operation can query and analyze the background configuration and the field configuration through the page renderer, and a framework of the corresponding configuration background can be rendered by using a unified background template;

step 222, rendering a final background page according to the background data;

optionally, the operation can inquire and analyze the background data through the page renderer, and finally, a corresponding page configured with the background can be rendered through a unified background template;

step 223, returning to the background page;

optionally, a page configuring the background may be returned;

step 231, performing operations such as adding data or deleting data or modifying data or querying data by using the configuration background;

optionally, after returning to the page of the configuration background, the operation may use the configuration background to perform operations such as adding data, deleting data, modifying data, or querying data;

step 232, checking whether the operation has operation authority;

optionally, the background module may be used to check whether the operation has an operation right;

optionally, whether the operation has the operation authority of the configuration background can be determined based on the authority character code number and the authority character name owned by the operation and the authority character group to which the configuration background belongs.

Step 233, saving an operation log;

optionally, under the condition that the operation has the operation authority of the configuration background A, the configuration background A can save an operation log of the operation after the operation performs related operation on the configuration background A;

step 234, saving the operation data;

optionally, in the case that the operation has the operation authority of the configuration background a, after the operation performs the related operation by the configuration background a, the configuration background a may save the operation data of the operation.

In the embodiment of the application, the background configuration, the field configuration and the background data of the configuration background are queried and analyzed through the page renderer, and the configuration background is rendered through the background template, so that the configuration background is rendered.

Optionally, the background module includes at least one of the following background interfaces: the system comprises an adding interface, a query list interface, a single data query interface, an updating interface, a deleting interface, a modifying interface, an importing interface, an exporting interface and a self-defining operation interface;

the background interface is connected with the configuration background, and the background module performs data management through the background interface.

Alternatively, at least one configuration background generated using the extensible background template may use the same background operational interface.

Optionally, a configuration background that is rendered based on the template and is operable for use can be generated by combining a set of universal background operation interfaces with the configuration background of the unified template rendering.

Optionally, the background operation interface may include an add interface, a query list interface, a query single data interface, an update interface, a delete interface or bulk delete interface, a modify interface, an import interface, an export interface, a custom operation interface, and the like.

Optionally, the custom operation interface can be matched with a custom button to use a three-way code to realize a corresponding operation function.

Alternatively, the data may be stored via a MySQL database.

Alternatively, the data may be stored through an unstructured class library table.

Alternatively, the data may be stored in a unified library table through a generic background interface.

Alternatively, the library table may comprise a text large field in a MySQL database.

Alternatively, the library table may include unstructured class storage such as HBase, mongoDB, infoGrid, or the like.

Table 1 is a schema table of MySQL provided in an embodiment of the present application.

TABLE 1 scheme table of MySQL

Alternatively, mySQL scheme is shown in table 1, req_data and content_data are the condition field and the content field in the form, respectively.

Alternatively, the background configuration table may be stored in MySQL.

Alternatively, a background field configuration table may be stored in MySQL.

Optionally, a configuration background that is operable for use after rendering on a template basis may be generated by a set of generic background operation interfaces in combination with a configuration background for unified template rendering.

In the embodiment of the application, the unified intelligent configuration distribution capacity is built through a set of universal background operation interfaces, and the configuration distribution capacity is improved.

Optionally, the distribution module is specifically configured to: based on the API service, monitoring whether the configuration background is subjected to data updating, and under the condition that the data updating is monitored, reloading the background configuration, carrying out data caching and updating the background configuration version number.

Optionally, after the configuration background issues data, the application programming interface (Application Programming Interface, API) service may monitor the background changes, in which case the background configuration may be reloaded, cached, and the configuration version number updated; or the background data may be loaded from the database upon query by a third party developer.

In the embodiment of the application, whether the configuration background is subjected to data updating or not is monitored through the API service, and loading and updating of the configuration background data are achieved.

Optionally, the distribution module is specifically configured to: and under the condition that a third-party query request is received, loading the data of the configuration background, screening the data based on the third-party query request, and returning a screening result.

Optionally, after the background release data is configured, when the third party developer inquires, background data can be loaded from the database, data screening is performed based on the third party inquiry request, and a screening result is returned.

Fig. 3 is a schematic flow chart of a distribution process provided in an embodiment of the present application, as shown in fig. 3, where the flow includes the following steps:

step 301, initiating a background configuration query;

optionally, first a third party developer may initiate a background configuration query;

step 302, inquiring data processing rules;

optionally, after the third party developer initiates the background configuration query, the data processing rule may be queried;

step 303, inquiring all configuration data of the background;

optionally, based on the data processing rules, the third party developer may query all configuration data of the configuration background;

step 304, processing the input parameters and loading design conditions;

optionally, after the third party developer queries all configuration data of the background, the configuration background can process the fields of the input parameters and load design conditions;

optionally, the design conditions may include at least one of: condition code number, condition description, condition field type, condition value, condition expansion rule, automatic matching or not, automatic matching method and automatic matching field.

Step 305, condition mapping, automatically screening configuration data conforming to design conditions;

optionally, after the background is configured to load the design conditions, condition mapping can be performed, and the configuration background can automatically screen configuration data conforming to the design conditions;

step 306, judging whether other background is related in the data processing rule;

optionally, if no other background is associated in the data processing rule, a result may be returned;

optionally, if other background is associated in the data processing rule, all configuration data associated with the background may be queried;

alternatively, if other background is associated in the data processing rule, steps 304 and 305 may be repeated;

step 307, assembling the data into a result set according to rules;

optionally, in the case that other background is associated in the data processing rule, the data may be uniformly stored to the result set based on the data processing rule;

optionally, step 306 may be repeated after the data is uniformly stored to the result set.

Alternatively, when a user initiates a request, condition screening logic may be implemented for the enrollment.

For example, in the case where the request initiated by the user is get.docode=test 1& version=1, the version of the joining party may be matched with the_version of the form by the conditional automatic matching capability, and all configurations may be returned to the user with the background configuration_version=1 or with the_version empty.

Alternatively, conditional operations may support internet protocol (Internet Protocol, IP) based regional, operator and network matching, as well as generic multi-choice matching, numerical comparison, hash operations, text full matching, etc.

In the embodiment of the application, the data meeting the calling conditions is called out from the data based on the calling conditions by acquiring the calling conditions received by the configuration background, and the user uses the rapidly-generated configuration background to call the data so as to realize configuration distribution of the background data.

Optionally, in the case that the condition expansion rule includes a data packing rule, the background module is specifically configured to: packaging the background configuration data of the configuration background into a CDN file, wherein the distribution module is specifically configured to: and distributing CDN links corresponding to the CND files.

Optionally, after the data is invoked in the configuration background, the invoked data may be data-packaged to obtain a content delivery network (Content Delivery Network, CDN) file, and a link to the CDN file is output.

Optionally, after the data is called by using the configuration background, if the data package is configured in the background rule, the called data may be packaged into a CDN file according to the package rule, and a link of the CDN file is output.

Alternatively, in the case of using an interface to obtain a CDN file, only one CDN link may be used.

In the embodiment of the application, the data is packaged, and under the condition that the CDN file is obtained by using the interface, the data can be distributed by only using one CDN link, so that the configuration distribution capability is improved.

Optionally, in the case that the number of configuration backgrounds is at least two, the distribution module is specifically configured to: and assembling and distributing the data of at least two configuration backgrounds through the background designer.

Optionally, after the data is respectively called by adopting at least one configuration background associated with each other, the data respectively called by the at least one configuration background associated with each other can be packaged into data to obtain a CDN file, and a link of the CDN file is output.

Alternatively, the associated background may be configured by the background designer, the highest priority configuration of the background such as B, C, D may be obtained, the assembly may be issued together in the results of a, and the capability of the client configuration center may be implemented by the form a.

Optionally, the associated background may be configured by a background designer to obtain all the eligible configurations of the B background, and assembled in the package field in a.

Optionally, the associated background can be configured by a background designer to obtain the field of the B form associated with a certain field of the a form, and the fields are assembled in the result of the a.

Fig. 4 is a schematic flow chart of the design background provided in the embodiment of the present application, as shown in fig. 4, the flow chart includes the following steps:

step 410, inputting design conditions;

alternatively, first the developer may configure design conditions, which may include at least one of: the method comprises the steps of a condition code number, a condition description, a condition field type, a condition value, a condition expansion rule, whether to automatically match, a method for automatically matching and an automatic matching field;

alternatively, the user may input a condition, acquire data.

Alternatively, the condition value may include a value of a condition field.

Step 411, save design conditions;

alternatively, the developer may save the design conditions in a database;

step 420, configuring a permission role group, and inputting a permission role code and a permission role name;

optionally, the developer can configure the authority character group and input the authority character code number and the authority character name;

optionally, when generating the configuration background, the authority role group to which the configuration background belongs may be specified based on the authority role code number and the authority role name;

step 421, storing the authority character code and the authority character name;

optionally, the developer may save the rights role code and the rights role name in a database;

step 430, background design;

optionally, the developer may perform design of the configuration background;

optionally, the developer can configure the background name, the unique identifier, the authority role group, the condition field and the expansion thereof, the content field and the expansion function thereof, the distribution strategy and the interface configuration through the background designer based on the design condition;

step 431, saving background design content;

alternatively, the developer may save the content of the background design in a database.

Alternatively, configuring the background when performing the background design may provide a form interface and the developer may enter the fields and logic needed to generate the background.

Optionally, the developer can configure the background name, the unique identifier, the authority role group, the system condition field and the expansion thereof, the content field and the expansion function thereof, the distribution strategy and the interface configuration through the background designer;

In the embodiment of the application, the data of at least two configuration backgrounds are assembled and distributed through the background designer, so that the data distribution is realized, the configuration request is saved, and the configuration distribution capability is improved.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A configuration distribution system, comprising:

the background module is used for configuring background management data;

2. The configuration distribution system according to claim 1, wherein the design conditions include at least one of: condition code number, condition description, condition field type, condition value, condition expansion rule, automatic matching or not, automatic matching method and automatic matching field.

3. The configuration distribution system according to claim 1, wherein the management module is further configured to configure a rights role code and a name, and when the configuration background is generated, specify a rights role group to which the configuration background belongs based on the rights role code and the name.

4. The configuration distribution system according to claim 1, wherein the management module is specifically configured to:

5. The configuration distribution system according to claim 1, wherein the background module is specifically configured to:

6. The configuration distribution system of claim 1, wherein the background module comprises at least one of the following background interfaces: the system comprises an adding interface, a query list interface, a single data query interface, an updating interface, a deleting interface, a modifying interface, an importing interface, an exporting interface and a self-defining operation interface;

7. The configuration distribution system according to claim 1, characterized in that said distribution module is specifically configured to: based on the API service, monitoring whether the configuration background is subjected to data updating, and under the condition that the data updating is monitored, reloading the background configuration, carrying out data caching and updating the background configuration version number.

8. The configuration distribution system according to claim 1, characterized in that said distribution module is specifically configured to: and under the condition that a third-party query request is received, loading the data of the configuration background, screening the data based on the third-party query request, and returning a screening result.

9. The configuration distribution system according to claim 2, wherein, in the case where the condition expansion rule includes a data packing rule, the background module is specifically configured to: packaging the background configuration data of the configuration background into a CDN file, wherein the distribution module is specifically configured to: and distributing CDN links corresponding to the CND files.

10. The configuration distribution system according to claim 4, wherein in case the number of configuration daemons is at least two, the distribution module is specifically configured to: and assembling and distributing the data of at least two configuration backgrounds through the background designer.