A method and device for generating and checking a channel capacity configuration, and a medium

Abstract

The application provides a channel capacity expansion configuration generation and verification method, device and medium, the method comprising: receiving user input capacity expansion information; using a template engine, generating at least one channel capacity expansion configuration according to the capacity expansion information; confirming each channel capacity expansion configuration and individually verifying each confirmed channel capacity expansion configuration; performing full-quantity verification on all individually verified channel capacity expansion configurations and publishing all full-quantity verified channel capacity expansion configurations to a configuration center. The method, device and medium can solve the problem that the generation and verification of channel capacity expansion configurations in the prior art rely on manual work and lack systematic generation and verification means.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus and medium for generating verification of channel expansion configuration. Background Technology

[0002] With the rapid development of mobile internet and the arrival of the 5G era, operators have fully deployed applications in the cloud to improve the support capabilities of their business systems. When system processing capacity is insufficient, achieving rapid capacity expansion while ensuring the accuracy and security of the expansion is crucial for improving user experience. The billing system involves multiple applications across its upstream and downstream processes, and different services have different configurations, requiring extensive configuration modifications during expansion.

[0003] Currently, the billing application has been fully deployed in the cloud. Since the existing billing application is stateful, each container binds a channel number variable at startup to distinguish instances. During application runtime, it relies on channel configuration files to connect upstream and downstream directories. Channel configuration is crucial; errors will directly affect billing accuracy, leading to missed charges or user complaints.

[0004] However, the generation and verification of existing channel expansion configurations rely on manual methods and lack systematic generation and verification means. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to address the above-mentioned shortcomings of the prior art by providing a channel expansion configuration generation and verification method, apparatus and medium to solve the problem that the generation and verification of channel expansion configuration in the prior art depends on manual labor and lacks a systematic generation and verification means.

[0006] In a first aspect, the present invention provides a method for generating and verifying channel expansion configurations, comprising:

[0007] Receive expansion information input by the user;

[0008] Using a template engine, at least one channel expansion configuration is generated based on the expansion information;

[0009] Each of the channel expansion configurations is confirmed, and each confirmed channel expansion configuration is verified individually.

[0010] Perform a full verification on all the channel expansion configurations that have been individually verified, and publish all the channel expansion configurations that have undergone full verification to the configuration center.

[0011] Furthermore, before receiving the expansion information input by the user, the method further includes:

[0012] The preset basic template rule base is maintained, wherein the basic template rule base includes at least one template information.

[0013] Furthermore, the step of using a template engine to generate at least one channel expansion configuration based on the expansion information specifically includes:

[0014] Based on the expansion information, select the template information to be used in this expansion;

[0015] Using the template engine, the at least one channel expansion configuration is generated based on the change type in the expansion information and the template information.

[0016] Furthermore, the change types are divided into addition and modification. The step of using the template engine to generate the at least one channel expansion configuration based on the change types in the expansion information and the template information specifically includes:

[0017] If the change type in the expansion information is "addition", then the template engine is used to load the template information and generate the at least one channel expansion configuration;

[0018] If the change type in the expansion information is "modification", then the expansion configuration of the at least one channel is pulled from the configuration center.

[0019] Furthermore, the step of loading the template information using the template engine to generate the at least one channel expansion configuration specifically includes:

[0020] The expansion information is parsed, and based on the key elements after parsing the expansion information, predefined variables of the template information are bound.

[0021] The template engine is used to load the bound template information, and a corresponding rule tree is generated based on the template class, template attributes, and validation rules corresponding to the bound template information.

[0022] Based on the rule tree, the at least one channel expansion configuration is generated cyclically.

[0023] Furthermore, the confirmation of the expansion configuration for each of the channels specifically includes:

[0024] Each channel expansion configuration is confirmed using the corresponding code or form, and each confirmed channel expansion configuration is marked as confirmed.

[0025] Furthermore, the step of individually verifying each confirmed channel expansion configuration specifically includes:

[0026] Based on the rule tree, the validity of each confirmed channel expansion configuration is verified.

[0027] Furthermore, the step of performing a full verification of all the individually verified channel expansion configurations specifically includes:

[0028] Pull all the channel expansion configurations that have been individually verified to the preset local code library;

[0029] In the local code repository, query all channel expansion configurations that have been individually verified and then sequentially perform host directory validity verification, distributed file system directory validity verification, distributed message system topic validity verification, and upstream and downstream application directory docking verification.

[0030] Furthermore, the step of publishing all the channel expansion configurations after full verification to the configuration center specifically includes:

[0031] All channel expansion configurations that have undergone full verification will be tagged with versions and uploaded to the server, so that the server will publish all tagged channel expansion configurations to the configuration center.

[0032] Furthermore, after publishing all the channel expansion configurations after full verification to the configuration center, the method further includes:

[0033] For applications that have completed channel expansion, the following checks are performed in sequence: channel operation status check, channel log processing call detail record (CDR) status check, input / output directory CDR backlog check, and upstream / downstream CDR balance verification.

[0034] Secondly, the present invention provides a channel expansion configuration generation and verification device, comprising:

[0035] The receiving module is used to receive expansion information input by the user;

[0036] A generation module, connected to the receiving module, is used to generate at least one channel expansion configuration based on the expansion information using a template engine.

[0037] A verification module, connected to the generation module, is used to verify each of the channel expansion configurations and to verify each of the confirmed channel expansion configurations individually.

[0038] The verification and release module, connected to the confirmation and verification module, is used to perform a full verification of all the channel expansion configurations that have been individually verified, and to release all the channel expansion configurations that have been fully verified to the configuration center.

[0039] Thirdly, the present invention provides a channel expansion configuration generation and verification device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the channel expansion configuration generation and verification method described in the first aspect.

[0040] Fourthly, the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the channel expansion configuration generation and verification method described in the first aspect.

[0041] The present invention provides a channel expansion configuration generation and verification method, apparatus, and medium. First, it receives expansion information input by a user. Then, using a template engine, it generates at least one channel expansion configuration based on the expansion information. Next, it confirms each channel expansion configuration and verifies each confirmed configuration individually. Finally, it performs a full verification of all individually verified channel expansion configurations and publishes all verified channel expansion configurations to a configuration center. This invention integrates channel expansion configuration generation and verification, utilizing a template engine to systematically and automatically generate and verify channel expansion configurations. This reduces manual resources, improves channel expansion efficiency and quality, and solves the problem in existing technologies where channel expansion configuration generation and verification rely on manual processes and lack systematic generation and verification methods. Attached Figure Description

[0042] Figure 1 This is a flowchart of a channel expansion configuration generation and verification method according to Embodiment 1 of the present invention;

[0043] Figure 2 This is a flowchart illustrating the verification process for completing channel expansion applications according to an embodiment of the present invention.

[0044] Figure 3 A structural diagram of the verification system generated for channel expansion configuration in an embodiment of the present invention;

[0045] Figure 4 This is a schematic diagram of the structure of a channel expansion configuration generation verification device according to Embodiment 2 of the present invention;

[0046] Figure 5 This is a schematic diagram of a channel expansion configuration generation verification device according to Embodiment 3 of the present invention. Detailed Implementation

[0047] To enable those skilled in the art to better understand the technical solution of the present invention, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

[0048] It is understood that the specific embodiments and accompanying drawings described herein are merely for explaining the invention and are not intended to limit the invention.

[0049] It is understood that, without conflict, the various embodiments and features in the embodiments of the present invention can be combined with each other.

[0050] It is understood that, for ease of description, only the parts related to the present invention are shown in the accompanying drawings, while the parts unrelated to the present invention are not shown in the drawings.

[0051] It is understood that each unit or module involved in the embodiments of the present invention may correspond to only one entity structure, or may be composed of multiple entity structures, or multiple units or modules may be integrated into one entity structure.

[0052] It is understood that, without conflict, the functions and steps marked in the flowcharts and block diagrams of this invention may occur in a different order than that marked in the accompanying drawings.

[0053] It is understood that the flowcharts and block diagrams of this invention illustrate the possible architecture, functions, and operations of systems, apparatuses, devices, and methods according to various embodiments of this invention. Each block in the flowchart or block diagram may represent a unit, module, program segment, or code, containing executable instructions for implementing the specified function. Furthermore, each block or combination of blocks in the block diagram and flowchart can be implemented using a hardware-based system to achieve the specified function, or using a combination of hardware and computer instructions.

[0054] It is understood that the units and modules involved in the embodiments of the present invention can be implemented by software or by hardware. For example, the units and modules can be located in a processor.

[0055] Application Overview

[0056] With the rapid development of mobile internet and the arrival of the 5G era, operators have fully deployed applications in the cloud to improve the support capabilities of their business systems. When system processing capacity is insufficient, achieving rapid capacity expansion while ensuring the accuracy and security of the expansion is crucial for improving user experience. The billing system involves multiple applications across its upstream and downstream processes, and different services have different configurations, requiring extensive configuration modifications during expansion.

[0057] Currently, the billing application has been fully deployed in the cloud. Since the existing billing application is stateful, each container binds a channel number variable at startup to distinguish instances. During application runtime, it relies on channel configuration files to connect upstream and downstream directories. Channel configuration is crucial; errors will directly affect billing accuracy, leading to missed charges or user complaints.

[0058] However, the generation and verification of existing channel expansion configurations rely on manual methods and lack systematic generation and verification means, which poses a high risk.

[0059] When expanding channel capacity, it is necessary to simultaneously expand multiple applications involved in the call detail record (CDR) stream. This involves numerous and complex configuration items, requiring manual configuration and advance expansion plans. Expansion efficiency is low, and when the system's processing capacity is insufficient, rapid expansion is impossible, leading to CDR backlogs and the risk of user complaints. Configuration verification is time-consuming and labor-intensive, consuming significant manpower. Furthermore, due to human error, omissions and errors are inevitable during the verification process, compromising quality. There is a lack of verification of the connections between upstream and downstream module directories and post-deployment checks and verifications.

[0060] Currently, channel expansion configuration relies on manual methods and lacks systematic generation and verification mechanisms.

[0061] The following problems exist:

[0062] 1. Manual configuration is required, which involves numerous and complex configuration items and a large workload. It is necessary to submit an expansion plan in advance.

[0063] 2. Configuration and verification are time-consuming and labor-intensive, consuming a lot of manpower. Moreover, due to human factors, there is an inevitable risk of omissions and errors during the inspection process, making it impossible to guarantee quality.

[0064] 3. The connection between upstream and downstream module directories was not verified, which poses a risk of directory mismatch.

[0065] 4. Lack of post-launch auditing methods and no check on the balance of upstream and downstream call detail records make it easy for malfunctions to occur if configuration is incorrect.

[0066] To address the aforementioned technical issues, this application integrates channel expansion configuration generation and configuration verification, utilizing a template engine to systematically and automatically generate and verify channel expansion configurations. This reduces manual resources and improves the efficiency and quality of channel expansion, thereby at least solving the problem that the generation and verification of channel expansion configurations in the prior art rely on manual processes and lack systematic generation and verification methods.

[0067] After introducing the basic principles of this application, various non-limiting embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0068] Example 1:

[0069] This embodiment provides a method for generating verification of channel expansion configuration, such as... Figure 1 As shown, the method includes:

[0070] Step S101: Receive expansion information input by the user.

[0071] Specifically, the user inputs expansion information such as change type, province, expansion application, business, start channel number, and number of expansion channels, and the system receives the user's expansion information.

[0072] In an optional embodiment, before receiving the expansion information input by the user, the method further includes:

[0073] The preset basic template rule base is maintained, wherein the basic template rule base includes at least one template information.

[0074] Specifically, during the initial expansion, it is necessary to maintain the template information used by the application, maintain the relationship between the application and the corresponding verification template, and form a basic template rule base.

[0075] It's important to note that templates, as the carriers of rules, are a core component of the template engine. They form a rule tree composed of template classes, template attributes, and corresponding validation rules. Each validation rule consists of a validation type, a validation expression, and a default value. As the basic unit for generating validation configurations, a template allows an application to define multiple templates based on business needs, ensuring compatibility with different business scenarios and making it suitable for situations where configurations differ significantly between different businesses.

[0076] Step S102: Using a template engine, generate at least one channel expansion configuration based on the expansion information.

[0077] Specifically, based on the expansion information, the template information to be used in this expansion is selected; using the template engine, the expansion configuration of the at least one channel is generated according to the change type in the expansion information and the template information.

[0078] In one optional embodiment, the change type is divided into addition and modification. The step of using the template engine to generate the at least one channel expansion configuration based on the change type in the expansion information and the template information specifically includes:

[0079] If the change type in the expansion information is "addition", then the template engine is used to load the template information and generate the at least one channel expansion configuration;

[0080] If the change type in the expansion information is "modification", then the expansion configuration of the at least one channel is pulled from the configuration center.

[0081] Specifically, the configuration generation strategy is matched based on the change type (addition or modification) in the expansion information. When the change type is added, the template engine loads the template information, parses the rule tree, and generates a default configuration based on the validation rules configured in the template attributes and the default value information, supporting multiple formats such as JSON, XML, and YAML. When the change type is modified, the configuration is directly pulled from the etcd configuration center.

[0082] In one optional embodiment, the step of loading the template information using the template engine to generate the at least one channel expansion configuration specifically includes:

[0083] The expansion information is parsed, and based on the key elements after parsing the expansion information, predefined variables of the template information are bound.

[0084] The template engine is used to load the bound template information, and a corresponding rule tree is generated based on the template class, template attributes, and validation rules corresponding to the bound template information.

[0085] Based on the rule tree, the at least one channel expansion configuration is generated cyclically.

[0086] Specifically, the method for generating channel expansion configurations is as follows:

[0087] (1) Template variable parsing: Parse key elements such as province, application, business, and channel number, and bind them to predefined template variables;

[0088] (2) Template loading: The template engine loads the template and parses it into a rule tree based on the template class, template attributes, and corresponding attribute validation rules;

[0089] (3) Generate default configuration: The rule parser traverses the rule tree and generates a single-channel default configuration based on the verification type, verification expression, default value rule, and template variable, and generates batch channel expansion configurations in a loop.

[0090] It should be noted that this method adopts the concept of convention over configuration, standardizes the management of configuration files, binds configuration item generation rules to validation rules, and provides a combination of basic rules and combined rules to solve complex configuration item generation and validation scenarios.

[0091] Step S103: Confirm each of the channel expansion configurations and verify each confirmed channel expansion configuration individually.

[0092] Specifically, confirm the batch channel expansion configuration information generated above, and verify the confirmed batch channel expansion configuration information separately to ensure the accuracy of the application configuration.

[0093] In one optional embodiment, confirming the expansion configuration for each of the channels specifically includes:

[0094] Each channel expansion configuration is confirmed using the corresponding code or form, and each confirmed channel expansion configuration is marked as confirmed.

[0095] Specifically, page elements are parsed based on template attribute configurations, and form rendering is performed. Configuration details are presented in two ways: configuration code and form. Forms are rendered dynamically, allowing modification of the configuration via either code or form; modifications are marked as confirmed upon completion.

[0096] It should be noted that the above form is generated through page element rendering.

[0097] Specifically, the rule tree is traversed to generate default configuration information and attribute component types, and dynamic forms are generated through parsing.

[0098] In an optional embodiment, the step of individually verifying each confirmed channel expansion configuration specifically includes:

[0099] Based on the rule tree, the validity of each confirmed channel expansion configuration is verified.

[0100] Specifically, the template engine loads template information, parses the rule tree, performs validity checks on each configuration rule, summarizes the configuration items that fail the check and displays them on the interface, dynamically displays the reasons for the failure in the form, and provides modification suggestions to the configuration personnel.

[0101] It should be noted that the validity validation rules, as the core of configuration validation, consist of two main categories: basic rules and combined rules. Basic rules include fixed value validation, null value validation, variable matching, enumerated value validation, enumerated variable validation, value range validation, regular expression validation, ratio calculation, summation calculation, complex calculation, and expression parsing, providing basic validation logic. Combined rules include prefix enumeration combination validation, prefix enumeration regular expression combination validation, and dynamic parsing of validation rules (recursive validation), providing validation for complex scenarios.

[0102] Step S104: Perform a full verification of all the channel expansion configurations that have been individually verified, and publish all the channel expansion configurations that have been fully verified to the configuration center.

[0103] Specifically, before deployment, all individually verified channel expansion configurations are fully validated to ensure the accuracy of upstream and downstream application integration, and the fully validated channel expansion configurations are then deployed to the etcd configuration center.

[0104] In one optional embodiment, the step of performing a full verification on all the individually verified channel expansion configurations specifically includes:

[0105] Pull all the channel expansion configurations that have been individually verified to the preset local code library;

[0106] In the local code repository, query all channel expansion configurations that have been individually verified and then sequentially perform host directory validity verification, distributed file system directory validity verification, distributed message system topic validity verification, and upstream and downstream application directory docking verification.

[0107] Specifically, the method for performing a full verification of all individually verified channel expansion configurations is as follows:

[0108] 1. Retrieve the full production configuration information to the local code repository;

[0109] 2. Query the full configuration information of the channels launched this time (i.e., the expansion configuration of all channels after individual verification) in the local code repository;

[0110] 3. The template engine performs configuration checks, sequentially verifying the validity of the host directory, the distributed file system directory, the distributed messaging system topic, and the upstream and downstream application directory connections to ensure the accuracy of the upstream and downstream application directory connections.

[0111] It should be noted that the upstream and downstream application directory docking verification is performed in the local code repository, while the host directory validity verification, distributed file system directory validity verification, and distributed messaging system topic validity verification need to connect to the external system to check whether the corresponding directory and topic have been created.

[0112] In one optional embodiment, the step of publishing all the channel expansion configurations after full verification to the configuration center specifically includes:

[0113] All channel expansion configurations that have undergone full verification will be tagged with versions and uploaded to the server, so that the server will publish all tagged channel expansion configurations to the configuration center.

[0114] Specifically, the method for publishing all channel expansion configurations after full verification to the configuration center is as follows:

[0115] 1. Version tagging is performed on all channel expansion configuration information after full verification involved in this expansion;

[0116] 2. Upload all configuration information after version tagging to the SVN (Subversion) server;

[0117] 3. All configuration information involved in this version is published to the etcd configuration center via an SVN server;

[0118] 4. Automatic comparison after configuration release to ensure successful configuration release.

[0119] In an optional embodiment, after publishing all the channel expansion configurations after full verification to the configuration center, the method further includes:

[0120] For applications that have completed channel expansion, the following checks are performed in sequence: channel operation status check, channel log processing call detail record (CDR) status check, input / output directory CDR backlog check, and upstream / downstream CDR balance verification.

[0121] Specifically, such as Figure 2 As shown, after the channel expansion is completed, the template engine sequentially performs channel operation status checks, channel log processing call detail record (CDR) status checks, input / output directory CDR backlog checks, and upstream / downstream CDR balance checks to ensure normal application processing and normal upstream / downstream connection after going online, thus ensuring the accuracy of channel expansion.

[0122] It is worth mentioning that the channel expansion configuration generation and verification method proposed in this invention is based on cloud-native applications and integrates channel expansion configuration generation, configuration verification, and post-deployment verification. It realizes automated configuration generation, configuration verification, and post-expansion verification functions based on a template engine. It adopts the concept of convention over configuration and uses a template engine to realize rich verification rules. With digital thinking, it systematically solves the problem that automatic configuration generation, configuration verification, and post-deployment verification rely on manual processes, thereby improving the efficiency and quality of channel expansion.

[0123] In one specific embodiment, to reduce manual resources, improve system expansion efficiency and quality, and enhance user experience, a template engine-based method for generating and verifying channel expansion configurations is proposed. This method is flexibly extensible and improves configuration accuracy. A method for auditing the integration of upstream and downstream application directories in the expansion channel is also proposed to improve the configuration quality of related modules. Furthermore, a post-expansion verification method is proposed to promptly identify expansion issues, improve expansion quality, and ensure billing accuracy. Specifically, this channel expansion configuration generation and verification method is applied to applications such as... Figure 3 The channel expansion configuration generation and verification system shown includes a configuration generation module, a configuration confirmation module, a configuration verification module, a pre-release check module, a release and launch module, and a post-launch verification module. The channel expansion configuration generation and verification method may include the following steps:

[0124] 1. The configuration generation module automatically generates configurations based on the expansion information such as province, application, business, and template entered by the user.

[0125] 1.1 Basic rule base maintenance. During the initial expansion, it is necessary to maintain the template information used by the application and the relationship between the application and the corresponding validation template, thus forming a basic template rule base.

[0126] 1.2 Expansion Information Entry. Enter the basic information for this expansion, including the change type (addition, modification), province, expansion application, business, starting channel number, number of expansion channels, and select the template to be used for this expansion.

[0127] 1.3 The rule parser generates configuration information. The rule parser matches the configuration to generate a strategy based on the change type. When the change type is "Add," the template engine loads the template information, parses the rule tree, and the rule parser generates a default configuration based on the validation rules configured in the template attributes and the default value information, supporting multiple formats such as JSON, XML, and YAML. When the change type is "Modify," the rule parser directly pulls the configuration from the etcd configuration center.

[0128] New channel configuration generation process:

[0129] (1) Template variable parsing: Parse key elements such as province, application, business, and channel number, and bind them to predefined variables in the template;

[0130] (2) Template loading: The template engine loads the template and parses it into a rule tree based on the template class, template attributes, and corresponding attribute validation rules;

[0131] (3) Generate default configuration: The rule parser traverses the rule tree, generates a single-channel default configuration based on the verification type, verification expression, default value rule, and template variables, and generates batch configurations in a loop;

[0132] (4) Page element rendering: The rule parser traverses the rule tree, generates default configuration information and attribute component types, and parses to generate dynamic forms.

[0133] 2. The configuration confirmation module confirms the generated batch channel expansion configuration information. If the information is correct, it is marked as confirmed.

[0134] 2.1 The rule parser parses page elements based on template attribute configurations and renders forms. It provides two methods for presenting configuration details: configuration code and forms. Forms are rendered dynamically, allowing modifications to the configuration via either code or forms; modifications are marked as confirmed upon completion.

[0135] 3. The configuration verification module verifies the modified channel expansion configuration information to ensure the accuracy of the single application configuration.

[0136] 3.1 The template engine loads template information, parses the rule tree, performs validity checks on each configuration rule, summarizes the configuration items that fail the check and displays them on the interface, dynamically displays the reasons for the failure in the form, and provides modification suggestions to the configuration personnel.

[0137] 4. Before the deployment, the pre-deployment inspection module performs a full verification of all application configurations packaged for this deployment to ensure the accuracy of upstream and downstream application integration.

[0138] 4.1 Pull the full production configuration information to the local code repository.

[0139] 4.2 Query the full configuration information of the channels launched this time.

[0140] 4.3 The template engine performs configuration checks, sequentially executing host directory validity checks, distributed file system directory validity checks, distributed message system topic validity checks, and upstream and downstream application directory connection checks to ensure the accuracy of upstream and downstream application directory connection.

[0141] 5. The deployment module will publish the expansion configuration information to the configuration center.

[0142] 5.1 Version tagging is performed on all application channel information involved in this expansion.

[0143] 5.2 Upload the configuration information to the SVN server.

[0144] Version 5.3 involves publishing expansion configuration information to the etcd configuration center.

[0145] 5.4 Automatic comparison after configuration release ensures successful configuration release.

[0146] 6. After going live, the verification module verifies the application that has completed the channel expansion.

[0147] 6.1 After the channel expansion is completed, the template engine sequentially performs the following checks: channel operation status check, channel log processing call detail record (CDR) status check, input / output directory CDR backlog check, and upstream / downstream CDR balance check. This ensures that the application processes normally after going online, that upstream and downstream connections are normal, and that the channel expansion is accurate.

[0148] The channel expansion configuration generation and verification method provided in this invention first receives expansion information input by the user; then, using a template engine, it generates at least one channel expansion configuration based on the expansion information; next, it confirms each channel expansion configuration and verifies each confirmed configuration individually; finally, it performs a full verification of all individually verified channel expansion configurations and publishes all verified channel expansion configurations to a configuration center. This invention integrates channel expansion configuration generation and verification, utilizing a template engine to systematically and automatically generate and verify channel expansion configurations, thereby reducing manual resources, improving channel expansion efficiency and quality, and solving the problem in existing technologies where channel expansion configuration generation and verification rely on manual processes and lack systematic generation and verification methods.

[0149] Example 2:

[0150] like Figure 4 As shown, this embodiment provides a channel expansion configuration generation and verification device for executing the above-described channel expansion configuration generation and verification method, including:

[0151] The receiving module 11 is used to receive expansion information input by the user;

[0152] The generation module 12, connected to the receiving module 11, is used to generate at least one channel expansion configuration based on the expansion information using a template engine.

[0153] The verification module 13, connected to the generation module 12, is used to verify each of the channel expansion configurations and to verify each of the confirmed channel expansion configurations individually.

[0154] The verification and release module 14 is connected to the confirmation and verification module 13. It is used to perform a full verification of all the channel expansion configurations that have been individually verified, and to release all the channel expansion configurations that have been fully verified to the configuration center.

[0155] Furthermore, the device also includes:

[0156] The maintenance module is used to maintain a preset basic template rule base, wherein the basic template rule base includes at least one template information.

[0157] Furthermore, the generation module 12 specifically includes:

[0158] The selection unit is used to select the template information to be used in this expansion based on the expansion information;

[0159] The first generation unit is used to generate the at least one channel expansion configuration by using the template engine, based on the change type in the expansion information and the template information.

[0160] Furthermore, the change types are divided into addition and modification, and the first generation unit specifically includes:

[0161] The second generation unit is used to load the template information using the template engine and generate the at least one channel expansion configuration if the change type in the expansion information is "addition".

[0162] The first pull unit is used to pull the at least one channel expansion configuration from the configuration center if the change type in the expansion information is modification.

[0163] Furthermore, the second generating unit is specifically used for:

[0164] The expansion information is parsed, and based on the key elements after parsing the expansion information, predefined variables of the template information are bound.

[0165] The template engine is used to load the bound template information, and a corresponding rule tree is generated based on the template class, template attributes, and validation rules corresponding to the bound template information.

[0166] Based on the rule tree, the at least one channel expansion configuration is generated cyclically.

[0167] Furthermore, the confirmation and verification module 13 specifically includes:

[0168] The confirmation and marking unit is used to confirm each channel expansion configuration through the code or form corresponding to the channel expansion configuration, and mark each confirmed channel expansion configuration as confirmed.

[0169] The first verification unit is used to verify the validity of each confirmed channel expansion configuration according to the rule tree.

[0170] Furthermore, the verification and release module 14 specifically includes:

[0171] The second pull unit is used to pull all the channel expansion configurations that have been individually verified to a preset local code library;

[0172] The second verification unit is used to query all the channel expansion configurations that have been individually verified in the local code repository and perform host directory validity verification, distributed file system directory validity verification, distributed message system topic validity verification, and upstream and downstream application directory docking verification in sequence.

[0173] The tagging and publishing unit is used to tag all the channel expansion configurations after full verification and upload them to the server, so that the server publishes all the tagged channel expansion configurations to the configuration center.

[0174] Furthermore, the device also includes:

[0175] The inspection and verification module is used to sequentially check the channel operation status, channel log processing call detail record status, input and output directory call detail record backlog, and upstream and downstream call detail record balance for applications that have completed channel expansion.

[0176] Example 3:

[0177] refer to Figure 5This embodiment provides a channel expansion configuration generation and verification device, including a memory 21 and a processor 22. The memory 21 stores a computer program, and the processor 22 is configured to run the computer program to execute the channel expansion configuration generation and verification method in Embodiment 1.

[0178] The memory 21 is connected to the processor 22. The memory 21 can be a flash memory, a read-only memory or other memory, and the processor 22 can be a central processing unit or a microcontroller.

[0179] Example 4:

[0180] This embodiment provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the channel expansion configuration generation and verification method in Embodiment 1 above.

[0181] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other memory technologies, CD-ROM (Compact Disc Read-Only Memory), DVD or other optical disc storage, cartridges, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer.

[0182] In summary, the channel expansion configuration generation and verification method, apparatus, and medium provided in this embodiment of the invention first receive expansion information input by the user; then, using a template engine, at least one channel expansion configuration is generated based on the expansion information; each channel expansion configuration is then confirmed, and each confirmed channel expansion configuration is individually verified; finally, all individually verified channel expansion configurations are fully verified, and all fully verified channel expansion configurations are published to the configuration center. This invention integrates channel expansion configuration generation and configuration verification, utilizing a template engine to systematically and automatically generate and verify channel expansion configurations, thereby reducing manual resources, improving channel expansion efficiency and quality, and solving the problem in the prior art where the generation and verification of channel expansion configurations rely on manual labor and lack systematic generation and verification methods.

[0183] It is understood that the above embodiments are merely exemplary implementations used to illustrate the principles of the present invention, and the present invention is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and essence of the present invention, and these modifications and improvements are also considered to be within the scope of protection of the present invention.

Claims

1. A method for generating verification of channel expansion configuration, characterized in that, The method includes: Receive expansion information input by the user; Using a template engine, at least one channel expansion configuration is generated based on the expansion information; Each of the channel expansion configurations is confirmed, and each confirmed channel expansion configuration is verified individually. Perform a full verification on all the channel expansion configurations that have been individually verified, and publish all the channel expansion configurations that have been fully verified to the configuration center; The step of using a template engine to generate at least one channel expansion configuration based on the expansion information specifically includes: Based on the expansion information, select the template information to be used for this expansion; Using the template engine, the at least one channel expansion configuration is generated based on the change type in the expansion information and the template information; The step of individually verifying each confirmed channel expansion configuration specifically includes: According to the rule tree, the validity of each confirmed channel expansion configuration is verified. The rule tree is generated based on the template class, template attributes, and verification rules corresponding to the template information. The at least one channel expansion configuration is generated cyclically according to the rule tree. The step of performing a full verification of all the channel expansion configurations that have been individually verified specifically includes: Pull all the channel expansion configurations that have been individually verified to the preset local code library; In the local code repository, query all channel expansion configurations that have been individually verified and then sequentially perform host directory validity verification, distributed file system directory validity verification, distributed message system topic validity verification, and upstream and downstream application directory docking verification.

2. The method according to claim 1, characterized in that, Before receiving the expansion information input by the user, the method further includes: The preset basic template rule base is maintained, wherein the basic template rule base includes at least one template information.

3. The method according to claim 2, characterized in that, The change types are divided into addition and modification. The template engine is used to generate the at least one channel expansion configuration based on the change types in the expansion information and the template information, specifically including: If the change type in the expansion information is "addition", then the template engine is used to load the template information and generate the at least one channel expansion configuration; If the change type in the expansion information is "modification", then the expansion configuration of the at least one channel is pulled from the configuration center.

4. The method according to claim 3, characterized in that, The step of loading the template information using the template engine to generate the at least one channel expansion configuration specifically includes: The expansion information is parsed, and based on the key elements after parsing the expansion information, predefined variables of the template information are bound. The template engine is used to load the bound template information, and a corresponding rule tree is generated based on the template class, template attributes, and validation rules corresponding to the bound template information. Based on the rule tree, the at least one channel expansion configuration is generated cyclically.

5. The method according to claim 1, characterized in that, The confirmation of each channel expansion configuration specifically includes: Each channel expansion configuration is confirmed using the corresponding code or form, and each confirmed channel expansion configuration is marked as confirmed.

6. The method according to claim 1, characterized in that, The step of publishing all the channel expansion configurations after full verification to the configuration center specifically includes: All channel expansion configurations that have undergone full verification will be tagged with versions and uploaded to the server, so that the server will publish all tagged channel expansion configurations to the configuration center.

7. The method according to claim 1, characterized in that, After publishing all the channel expansion configurations that have undergone full verification to the configuration center, the method further includes: For applications that have completed channel expansion, the following checks are performed in sequence: channel operation status check, channel log processing call detail record (CDR) status check, input / output directory CDR backlog check, and upstream / downstream CDR balance verification.

8. A channel expansion configuration generation and verification device, characterized in that, include: The receiving module is used to receive expansion information input by the user; A generation module, connected to the receiving module, is used to generate at least one channel expansion configuration based on the expansion information using a template engine. A verification module, connected to the generation module, is used to verify each of the channel expansion configurations and to verify each of the confirmed channel expansion configurations individually. The verification and release module, connected to the confirmation and verification module, is used to perform a full verification of all the channel expansion configurations that have been individually verified, and to release all the channel expansion configurations that have been fully verified to the configuration center. The generation module specifically includes: The selection unit is used to select the template information to be used in this expansion based on the expansion information; The first generation unit is used to generate the at least one channel expansion configuration by using the template engine, based on the change type in the expansion information and the template information; The confirmation and verification module includes: The first verification unit is used to verify the validity of each confirmed channel expansion configuration according to the rule tree, wherein the rule tree is generated based on the template class, template attributes and verification rules corresponding to the template information, and the at least one channel expansion configuration is generated cyclically according to the rule tree; The verification and release module includes: The second pull unit is used to pull all the channel expansion configurations that have been individually verified to a preset local code library; The second verification unit is used to query all the channel expansion configurations that have been individually verified in the local code repository and sequentially perform host directory validity verification, distributed file system directory validity verification, distributed message system topic validity verification, and upstream and downstream application directory docking verification.

9. A channel expansion configuration generation and verification device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to implement the channel expansion configuration generation verification method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the channel expansion configuration generation and verification method as described in any one of claims 1-7.

Images