Service design inspection method and device, communication equipment and storage medium

Abstract

The invention relates to a service design inspection method and device, communication equipment, a storage medium, a chip and a computer program product. The method comprises the steps of obtaining to-be-verified data, and determining a data type of the to-be-verified data and a structure layer to which the to-be-verified data belongs; based on a verification method of a structure layer to which the to-be-verified data belongs, performing design content and data integrity verification of service design on the to-be-verified data to obtain a verification result; and generating a verification report of the to-be-verified data according to the problem description and the problem level in the verification result. By adopting the method, the design content of service design and data integrity verification can be carried out on the to-be-verified data, so that whether the to-be-verified data meets the design concept of a PSR model or not is judged, pre-auditing processing can be carried out on design problems possibly generated in the product design process before a product is online, the labor cost is saved, and the product quality is improved. And the efficiency of product verification and product release is improved.

Description

Technical Field

[0001] The present application relates to the field of software development technology, and in particular to a service design inspection method, apparatus, communication equipment, storage medium, chip and computer program product. Background Art

[0002] With the development of software development technology, communication products based on the PSR (Product-Service-Resource) model have emerged. The design concept of the PSR model is to decouple resources, resource services, business services and products in a layered manner, and assemble and design them based on the underlying cloud network capabilities to form network services and business services, and provide communication services and communication products to users.

[0003] In traditional technology, before the design of a cloud network service based on the PSR model is released, the designer can submit a cloud network service design data package to the reviewer, and the reviewer can review whether the cloud network service design complies with the design rules of the PSR model based on the cloud network service design data package.

[0004] However, with the current design verification method, during the design process, technical personnel may submit service design review requirements multiple times. As a result, reviewers are required to conduct multiple reviews of the service design, which results in extended launch time for communication services and communication products and low design efficiency for communication services and communication products. Summary of the invention

[0005] The embodiments of the present application provide a service design verification method, apparatus, communication equipment, storage medium, chip and computer program product, which can solve the problem of low design efficiency of communication services and communication products.

[0006] A service design inspection method, the method comprising:

[0007] Acquire the data to be verified, and determine the data type of the data to be verified and the structural layer to which the data to be verified belongs;

[0008] Based on the verification method of the structural layer to which the data to be verified belongs, the design content and data integrity of the service design of the data to be verified are verified to obtain a verification result;

[0009] A verification report for the data to be verified is generated based on the problem description and problem level in the verification result.

[0010] In one embodiment, the obtaining of the data to be verified, the data type of the data to be verified, and the structural layer to which the data to be verified belongs includes:

[0011] The data to be verified is obtained through a trigger operation, and the types of the trigger operation include automatic triggering and manual triggering.

[0012] In one embodiment, the automatic triggering is triggered at any time.

[0013] In one embodiment, the verification of the design content of the service design on the data to be verified includes:

[0014] Verify whether the status of the data to be verified and the calling data of the data to be verified meet the design requirements of the service design.

[0015] In one of the embodiments, the levels of the structural layer include a business service layer or service layer, a network service layer or sub-service layer, and a resource layer.

[0016] In one of the embodiments, the structure layer level also includes a product layer.

[0017] In one embodiment, the verification method based on the structural layer to which the data to be verified belongs, performing service design design content and data integrity content verification on the data to be verified, includes:

[0018] Obtaining the object structure of the data to be verified;

[0019] Based on the design requirements of the service design of the structural layer to which the data to be verified belongs, the object structure of the data to be verified is verified.

[0020] In one embodiment, the verification method based on the structural layer to which the data to be verified belongs performs a verification of the design content and data integrity of the service design on the data to be verified to obtain a verification result, including:

[0021] In the case where the object structure of the data to be verified does not meet the design requirements of the service design, adding the structural problem description and the first-level problem level to the verification result; or,

[0022] In the case that the object structure of the data to be verified meets the design requirements of the service design, the structural problem description and the three-level problem level are added to the verification result.

[0023] In one embodiment, the method further comprises:

[0024] According to the data to be verified, it is determined whether the calling data of the data to be verified exists.

[0025] In one embodiment, the method further comprises:

[0026] According to the data to be verified, it is determined whether the status of the calling data of the data to be verified is available.

[0027] In one embodiment, the method further comprises:

[0028] According to the data to be verified, it is determined whether the data to be verified and the calling data of the data to be verified are complete.

[0029] In one of the embodiments, determining whether the status of the calling data of the data to be verified is available includes:

[0030] Acquire the state of the call data, the state including a first state and a second state, the first state is used to indicate that the call data is in an online state, and the second state is used to indicate that the call data is not in an online state;

[0031] Based on the design requirements of the service design of the data to be verified, verify the state of the call data, and if the state of the call data is the second state, determine that the state of the call data is unavailable, and add the call problem description and the secondary problem level to the verification result; or

[0032] In a case where the state of the call data is the first state, it is determined that the state of the call data is available, and the call problem description and the third-level problem level are added to the verification result.

[0033] In one embodiment, the method further comprises:

[0034] In the case that the data type of the data to be verified is an object, object verification and object capability verification are performed on the data to be verified.

[0035] In one embodiment, the method further comprises:

[0036] In the case where the data type of the data to be verified is an object, determining whether there is a first-level problem level in the verification result;

[0037] When the first-level problem level does not exist in the verification result, acquiring the capability of the associated object of the data to be verified from the data to be verified;

[0038] In the case that the data to be verified does not have the associated object capability, adding the structural problem description and the first-level problem level to the verification result; or,

[0039] In the case where the data to be verified has the capability of being associated with an object, the structural layer problem description and the three-level problem level are added to the verification result.

[0040] In one of the embodiments, when the data type of the data to be verified is an object, determining whether the data to be verified is complete includes:

[0041] Determine whether a first field and an object structure of the data to be verified are complete, wherein the first field is field information included in data of a preset object type;

[0042] In a case where the data type of the data to be verified is object capability, determining whether the data to be verified is complete includes:

[0043] Determine whether the second field of the data to be verified and the calling design requirements are complete, the second field being field information included in data of a preset object capability type.

[0044] In one embodiment, the method further comprises:

[0045] Acquire field information and object structure from the data to be verified;

[0046] Performing data integrity verification on the field information and object structure of the data to be verified, and adding the object integrity problem description and the secondary problem level to the verification result when the field information of the data to be verified does not match the first field and / or the object structure of the data to be verified does not meet the object structure requirement; or

[0047] When the field information of the data to be verified matches the first field and the object structure of the data to be verified meets the object structure requirement, the object integrity problem description and the three-level problem level are added to the verification result.

[0048] In one of the embodiments, when the data type of the data to be verified is object capability, based on the verification method of the structural layer to which the data to be verified belongs, performing data integrity verification on the data to be verified to obtain a verification result includes:

[0049] Acquire field information and call flow information from the data to be verified;

[0050] Verify the field information and call process information of the data to be verified, and if the field information of the data to be verified does not match the second field and / or the call process information of the data to be verified does not meet the call design requirements, add the object capability integrity problem description and the secondary problem level to the verification result; or

[0051] When the field information of the data to be verified matches the second field and the calling process information of the data to be verified meets the calling design requirements, the object capability integrity problem description and the three-level problem level are added to the verification result.

[0052] In one embodiment, the problem level includes a first-level problem level, a second-level problem level and a third-level problem level, the priority of the first-level problem level representation is higher than the priority of the second-level problem level representation, and the priority of the second-level problem level representation is higher than the priority of the third-level problem level representation.

[0053] In one embodiment, generating a verification report of the data to be verified according to the problem description and problem level in the verification result includes:

[0054] In the case that there is no first-level problem level in the verification result, obtaining the number of the second-level problem levels in the verification result;

[0055] When the number of the second-level problem levels in the verification result is greater than a preset number, combining the second-level problem levels into a first-level problem level;

[0056] Based on the description of each problem in the verification result and the first-level problem level, a verification report of the data to be verified is generated.

[0057] In one embodiment, the method further comprises:

[0058] When the number of the secondary problem levels in the verification result is less than or equal to the preset number, obtaining the number of each problem level;

[0059] Determining a target problem level among the plurality of said problem levels;

[0060] Based on the description of each problem and the target problem level, a verification report of the data to be verified is generated.

[0061] In one embodiment, the method further comprises:

[0062] monitoring the problem level in the verification result, and stopping the verification process when the first-level problem level is detected in the verification result;

[0063] A verification report for the data to be verified is generated based on the problem description in the current verification result and the first-level problem level.

[0064] In one embodiment, after generating the verification report of the data to be verified according to the problem description and problem level in the verification result, the method further includes:

[0065] When the verification report of the data to be verified indicates that the data to be verified has passed the verification, generating a manual review request based on the data to be verified;

[0066] After the data to be verified is reviewed and approved, the data to be verified is allowed to be packaged.

[0067] A service design inspection device, comprising:

[0068] A first acquisition module is used to acquire the data to be verified, and determine the data type of the data to be verified and the structural layer to which the data to be verified belongs;

[0069] A first verification module, configured to verify the design content of the service design and the data integrity content of the data to be verified based on the verification method of the structural layer to which the data to be verified belongs, and obtain a verification result, wherein the verification result includes a problem description and a problem level of the data to be verified;

[0070] The first generating module is used to generate a verification report of the data to be verified according to the problem description and problem level in the verification result.

[0071] In one embodiment, the first acquisition module is specifically used for:

[0072] The data to be verified is obtained through a trigger operation, and the types of the trigger operation include automatic triggering and manual triggering.

[0073] In one embodiment, the automatic triggering is triggered at any time.

[0074] In one embodiment, the first verification module is specifically used for:

[0075] Verify whether the status of the data to be verified and the calling data of the data to be verified meet the design requirements of the service design.

[0076] In one of the embodiments, the levels of the structural layer include a business service layer or service layer, a network service layer or sub-service layer, and a resource layer.

[0077] In one of the embodiments, the structure layer level also includes a product layer.

[0078] In one embodiment, the first verification module is specifically used for:

[0079] Obtaining the object structure of the data to be verified;

[0080] Based on the design requirements of the service design of the structural layer to which the data to be verified belongs, the object structure of the data to be verified is verified.

[0081] In one embodiment, the first verification module is specifically used for:

[0082] In the case where the object structure of the data to be verified does not meet the design requirements of the service design, adding the structural problem description and the first-level problem level to the verification result; or,

[0083] In the case that the object structure of the data to be verified meets the design requirements of the service design, the structural problem description and the three-level problem level are added to the verification result.

[0084] In one embodiment, the device further comprises:

[0085] The first determining module is used to determine whether the calling data of the data to be verified exists according to the data to be verified.

[0086] In one embodiment, the device further comprises:

[0087] The second determining module is used to determine whether the status of the calling data of the data to be verified is available according to the data to be verified.

[0088] In one embodiment, the device further comprises:

[0089] The third determination module is used to determine whether the data to be verified and the calling data of the data to be verified are complete according to the data to be verified.

[0090] In one embodiment, the second determining module is specifically configured to:

[0091] Acquire the state of the call data, the state including a first state and a second state, the first state is used to indicate that the call data is in an online state, and the second state is used to indicate that the call data is not in an online state;

[0092] Based on the design requirements of the service design of the data to be verified, verify the state of the call data, and if the state of the call data is the second state, determine that the state of the call data is unavailable, and add the call problem description and the secondary problem level to the verification result; or

[0093] In a case where the state of the call data is the first state, it is determined that the state of the call data is available, and the call problem description and the third-level problem level are added to the verification result.

[0094] In one embodiment, the device further comprises:

[0095] The second verification module is used to perform object verification and object capability verification on the data to be verified when the data type of the data to be verified is an object.

[0096] In one embodiment, the device further comprises:

[0097] A fourth determination module, configured to determine whether there is a first-level problem level in the verification result when the data type of the data to be verified is an object;

[0098] A second acquisition module is used to acquire the associated object capability of the data to be verified from the data to be verified when the first-level problem level does not exist in the verification result;

[0099] A first adding module is used to add the structural problem description and the first-level problem level to the verification result when the data to be verified does not have the associated object capability; or

[0100] The second adding module is used to add the structural problem description and the three-level problem level to the verification result when the data to be verified has associated object capabilities.

[0101] In one of the embodiments, when the data type of the to-be-verified data is an object, the third determination module is specifically configured to:

[0102] Determine whether a first field and an object structure of the data to be verified are complete, wherein the first field is field information included in data of a preset object type;

[0103] In a case where the data type of the data to be verified is object capability, determining whether the data to be verified is complete includes:

[0104] Determine whether the second field of the data to be verified and the calling design requirements are complete, the second field being field information included in data of a preset object capability type.

[0105] In one embodiment, the device further comprises:

[0106] A third acquisition module is used to acquire field information and object structure from the data to be verified;

[0107] A third adding module is used to perform data integrity verification on the field information and object structure of the data to be verified, and when the field information of the data to be verified does not match the first field and / or the object structure of the data to be verified does not meet the object structure requirement, add the object integrity problem description and the secondary problem level to the verification result;

[0108] A fourth adding module is used to add the object integrity problem description and the third-level problem level to the verification result when the field information of the data to be verified matches the first field and the object structure of the data to be verified meets the object structure requirement.

[0109] In one of the embodiments, when the data type of the data to be verified is object capability, the first verification module is specifically configured to:

[0110] Acquire field information and call flow information from the data to be verified;

[0111] Verify the field information and call process information of the data to be verified, and if the field information of the data to be verified does not match the second field and / or the call process information of the data to be verified does not meet the call design requirements, add the object capability integrity problem description and the secondary problem level to the verification result; or

[0112] When the field information of the data to be verified matches the second field and the calling process information of the data to be verified meets the calling design requirements, the object capability integrity problem description and the three-level problem level are added to the verification result.

[0113] In one embodiment, the problem level includes a first-level problem level, a second-level problem level and a third-level problem level, the priority of the first-level problem level representation is higher than the priority of the second-level problem level representation, and the priority of the second-level problem level representation is higher than the priority of the third-level problem level representation.

[0114] In one embodiment, the first generating module is specifically used for:

[0115] In the case that there is no first-level problem level in the verification result, obtaining the number of the second-level problem levels in the verification result;

[0116] When the number of the second-level problem levels in the verification result is greater than a preset number, combining the second-level problem levels into a first-level problem level;

[0117] Based on the description of each problem in the verification result and the first-level problem level, a verification report of the data to be verified is generated.

[0118] In one embodiment, the device further comprises:

[0119] A fourth acquisition module, configured to acquire the number of each of the problem levels when the number of the secondary problem levels in the verification result is less than or equal to the preset number;

[0120] A fifth determination module, used to determine a target problem level among the plurality of problem levels;

[0121] The second generating module is used to generate a verification report of the data to be verified based on each problem description and the target problem level.

[0122] In one embodiment, the device further comprises:

[0123] A monitoring module, used for monitoring the problem level in the verification result, and stopping the verification process when the first-level problem level is detected in the verification result;

[0124] The third generating module is used to generate a verification report of the data to be verified according to the problem description in the current verification result and the first-level problem level.

[0125] In one embodiment, the device further comprises:

[0126] A fourth generating module, configured to generate a manual review request based on the data to be verified when the verification report of the data to be verified indicates that the data to be verified has passed the verification;

[0127] The packaging module is used to allow the data to be verified to be packaged after the data to be verified is reviewed and approved.

[0128] A communication device includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above-mentioned service design verification method when executing the computer program.

[0129] A computer-readable storage medium stores a computer program, which implements the steps of the above-mentioned service design verification method when executed by a processor.

[0130] A chip includes a programmable logic circuit and / or program instructions, and when the chip is running, it can execute the steps of the above-mentioned service design inspection method.

[0131] A computer program product includes a computer program, characterized in that when the computer program is executed by a processor, the steps of the above-mentioned service design verification method are implemented.

[0132] The above-mentioned service design verification method, device, communication equipment, storage medium and computer program product obtain the data to be verified, determine the data type of the data to be verified and the structural layer to which the data to be verified belongs; based on the verification method of the structural layer to which the data to be verified belongs, perform service design design content and data integrity verification on the data to be verified to obtain a verification result; and generate a verification report for the data to be verified based on the problem description and problem level in the verification result. By adopting this method, the design content and data integrity of the service design can be verified on the data to be verified, so as to determine whether the data to be verified meets the design concept of the PSR model, and can pre-audit and process the design problems that may arise in the product design process before the product goes online, saving labor costs and improving the efficiency of product verification and product release. BRIEF DESCRIPTION OF THE DRAWINGS

[0133] Figure 1 An application environment diagram of a service design inspection method in an embodiment;

[0134] Figure 2 A flowchart of a service design inspection method in one embodiment;

[0135] Figure 3 A schematic diagram of a process for obtaining a verification result of data to be verified in one embodiment;

[0136] Figure 4 A schematic diagram of the relationship between various structural layers in an embodiment;

[0137] Figure 5 A schematic diagram of a flow chart of verifying an object structure of data to be verified in one embodiment;

[0138] Figure 6 A schematic diagram of a flow chart of verifying an object structure of data to be verified to obtain a verification result in one embodiment;

[0139] Figure 7 A schematic diagram of a process of verifying the state of the calling data based on the data to be verified in one embodiment;

[0140] Figure 8 A schematic diagram of a flow chart of determining whether the data to be verified has the capability of being associated with an object in one embodiment;

[0141] Fig. 9 A schematic diagram of a process of performing data integrity verification on data to be verified in one embodiment;

[0142] Fig.10 A schematic diagram of a process for determining whether the calling process information of the data to be verified meets the calling design requirements in one embodiment;

[0143] Fig.11 A schematic diagram of a process for generating a verification report of data to be verified in one embodiment;

[0144] Fig.12 A schematic diagram of a process for generating a verification report of data to be verified in another embodiment;

[0145] Fig.13 A schematic diagram of a process for generating a verification report of data to be verified in another embodiment;

[0146] Fig.14 A schematic diagram of a process for determining whether the data to be verified meets the data release condition in one embodiment;

[0147] Fig.15A schematic diagram of an example of a processing procedure of a service design inspection method in an embodiment;

[0148] Fig.16 A structural block diagram of a service design inspection device in one embodiment. DETAILED DESCRIPTION

[0149] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0150] Figure 1 A schematic diagram of an application scenario of a service design verification method provided in an embodiment of the present application. Figure 1 As shown, in this scenario, there are a user terminal 100 and an audit terminal 200. The user terminal 100 and the audit terminal 200 perform data transmission via a network. The user terminal 100 and the audit terminal 200 can be terminals such as personal computers and laptop computers.

[0151] In traditional technology, the PSR design concept is to decouple resources, resource services, business services, and products in layers, and assemble and design them based on the underlying cloud network capabilities to form network services and business services, and provide communication services / products to the outside world. However, the current cloud network service design based on the PSR model lacks verification steps before loading and publishing. Technical personnel may submit service design review requirements multiple times, increasing the time for reviewers to review network / business services or products, or the time it takes for network / business services or products to go online, which will cost manpower and time.

[0152] It should be noted that the beneficial effects brought about by the embodiments of the present application or the technical problems solved are not limited to this one, but may also include other implicit or related problems. For details, please refer to the description of the following embodiments.

[0153] Before introducing the specific embodiments of the present invention, the professional terms involved in the present invention are explained first:

[0154] PSR (Product-Service-Resource) model: multiple resources constitute network services, one or more network services constitute business services, and one or more businesses constitute communication services / products. The design concept of the PSR model is to decouple resources, services, and products in layers, and assemble and design them based on the underlying cloud network capabilities to form services and provide communication services / products to the outside world.

[0155] Business services: Customer-oriented services.

[0156] Network services: Resource-oriented services.

[0157] The service layer is divided into network services and business services.

[0158] Products are designed and released products and communication services.

[0159] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0160] In one embodiment, Figure 2 As shown in the figure, a service design verification method is provided, which is applied to Figure 1 The user terminal in the example is used as an example to illustrate, including the following steps:

[0161] Step 202: Acquire the data to be verified, determine the data type of the data to be verified and the structural layer to which the data to be verified belongs.

[0162] In the embodiment of the present application, in product design, the user terminal may be pre-installed with a front-end platform, wherein the front-end platform is used to store the structural layer directories corresponding to the product and the files corresponding to each structural layer directory during the product development process.

[0163] Each level of structure layer directory may contain multiple structure layer directories, each structure layer directory corresponds to a structure (i.e., network topology), and each structure layer directory stores files related to the structure layer corresponding to the structure layer directory. Each structure layer directory also corresponds to a data type. For example, the structure layer corresponding to structure layer directory A is the network service layer, and the corresponding data type is object.

[0164] Based on the user terminal, the user can determine the target structure layer directory in the front-end platform of the product, and select the files under the target directory and the structure layer and data type corresponding to the target directory for packaging processing, so that the user terminal can obtain the data to be verified, the data type of the data to be verified, and the structure layer to which the data to be verified belongs.

[0165] The user terminal may pre-store in the backend database the design requirements of the service design corresponding to each structural layer and the data integrity requirements of each data type.

[0166] The user terminal determines the design requirements of the service design corresponding to the data to be verified based on the structural layer to which the data to be verified belongs and the design requirements of the service design corresponding to each structural layer, and determines the data integrity requirements corresponding to the data to be verified according to the data type of the data to be verified and the data integrity requirements of each data type.

[0167] Step 204 , based on the verification method of the structural layer to which the data to be verified belongs, the design content and data integrity of the service design are verified on the data to be verified, and a verification result is obtained.

[0168] The verification result includes the problem description and problem level of the data to be verified.

[0169] In the embodiment of the present application, the user terminal verifies the object structure and data integrity of the data to be verified based on the design requirements and data integrity requirements of the service design corresponding to the data to be verified, and obtains a verification result.

[0170] Step 206: Generate a verification report for the data to be verified based on the problem description and problem level in the verification result.

[0171] The problem description is used to describe the problem of the data to be verified, and the problem description may include the problem description of the data to be verified and the corresponding location of the data to be verified, such as the number of code lines or file path. The problem level is used to reflect the severity of the problem of the data to be verified.

[0172] In the embodiment of the present application, the user terminal generates a verification report for the data to be verified based on the problem description and problem level in the verification result.

[0173] In the above service design verification method, by obtaining the data to be verified, the data type of the data to be verified and the structural layer to which the data to be verified belongs are determined; based on the verification method of the structural layer to which the data to be verified belongs, the design content and data integrity of the service design are verified on the data to be verified to obtain the verification result; according to the problem description and problem level in the verification result, a verification report for the data to be verified is generated. By adopting this method, the design content and data integrity of the service design can be verified on the data to be verified, so as to determine whether the data to be verified meets the design concept of the PSR model, and the design problems that may arise in the product design process can be pre-reviewed before the product goes online, saving labor costs and improving the efficiency of product verification and product release.

[0174] In one embodiment, step 202 includes:

[0175] The data to be verified is obtained through a trigger operation, and the types of the trigger operation include automatic triggering and manual triggering.

[0176] Among them, the data verification confirmation operation can be triggered in real time.

[0177] In the embodiment of the present application, the user can select and operate in real time on the front-end platform of the product through the user terminal, determine the data to be verified, and manually submit the operation. The submission operation can also be an automatic trigger operation, which is triggered at any time during the product design stage, mainly to help the user debug. After the trigger operation, the user terminal determines the data to be verified according to the data selected by the user, and determines the data type of the data to be verified and the structural layer to which the data to be verified belongs according to the directory where the data to be verified is located.

[0178] In this embodiment, the user terminal can perform data verification at any time during product design, thereby improving the convenience of verifying any data to be verified during the product design process.

[0179] In one embodiment, the automatic triggering is triggered at any time.

[0180] In the embodiment of the present application, the submission operation can also be an automatically triggered operation, which can be triggered at any time during the product design stage.

[0181] In one embodiment, Figure 3 As shown, step 206 includes:

[0182] Step 302: based on the design requirements of the service design corresponding to the data to be verified, verify the data to be verified to obtain the verification result of the data to be verified.

[0183] In an embodiment of the present application, the user terminal verifies the network topology structure of the data to be verified based on the design requirements of the service design corresponding to the data to be verified stored in the backend, thereby determining whether the network topology structure of the data to be verified meets the design requirements of the PSR model, and obtaining a verification result of the design content of the service design of the data to be verified.

[0184] Step 304: based on the data integrity requirement corresponding to the data to be verified, verify the data to be verified to obtain a verification result of the data to be verified.

[0185] In an embodiment of the present application, the user terminal verifies the data to be verified of each data type based on the data integrity requirements corresponding to the data type of the data to be verified stored in the back end, so as to determine whether the data to be verified meets the data integrity requirements, and obtains a verification result for the data integrity of the data to be verified.

[0186] In this embodiment, the data to be verified can be verified according to the design requirements of the service design and the data integrity requirements corresponding to the data to be verified, and the verification results of the data to be verified can be obtained. A verification report of the data to be verified is generated to inform the technicians of the problems that do not meet the design requirements of the service design and the problems of incomplete data in the data to be verified, so that the technicians can modify the data to be verified according to the verification results, and the data to be verified can be verified again after the modification is completed.

[0187] In one embodiment, step 204 includes:

[0188] Verify whether the status of the data to be verified and the calling data of the data to be verified meet the design requirements of the service design.

[0189] In the embodiment of the present application, the backend of the user terminal stores the design requirements of the service design corresponding to the data to be verified and the design requirements of the service design corresponding to the calling data of the data to be verified. The user terminal verifies whether the status of the data to be verified and the calling data of the data to be verified meet the design requirements of the service design.

[0190] In this embodiment, it is possible to determine whether the status of the data to be verified and the calling data of the data to be verified meet the design requirements of the service design, so as to facilitate obtaining the verification result so that the technician can modify the data to be verified according to the verification result.

[0191] In one embodiment, the levels of the structural layer include a business service layer or service layer, a network service layer or sub-service layer, and a resource layer.

[0192] Among them, the structural layer refers to the architecture layer.

[0193] In the embodiment of the present application, the relationship between the structural layers can refer to Figure 4 As shown, the subordinate layer of the business service layer (also called the service layer) is the network service layer (also called the sub-service layer), that is, the business service is composed of network services; the subordinate layer of the network service layer is the resource layer, that is, the network service is composed of resources. Resources may include but are not limited to device code numbers, address areas, links, configurations, facilities, etc. The embodiments of this application do not specifically limit the specific types of resources.

[0194] Since each structural layer is designed as a layered decoupled layer in the design rules of the PSR model, the backend of the user terminal can store the design requirements of the service design corresponding to each structural layer. For example, the network topology structure corresponding to each structural layer should only include the nodes involved in the structural layer and its subordinate layers, and should not include nodes involved in other structural layers of the same level or the upper structural layer.

[0195] Specifically, when the structural layer to which the data to be verified belongs is the network service layer, the design requirements for the service design corresponding to the network service layer for the data to be verified can be: the network topology structure of the data to be verified only includes the nodes involved in the network service layer and the nodes involved in the subordinate layer of the network service layer (i.e., the resource layer).

[0196] It is understandable that, when the structural layer to which the data to be verified belongs also includes at least one subordinate layer, the user terminal may also verify each subordinate layer according to the design requirements of the service design corresponding to each subordinate layer.

[0197] In this embodiment, the design requirements of the service design corresponding to each structural layer of the data to be verified can be used to determine whether there is a problem with the network topology structure of the data to be verified, and then determine whether the data to be verified meets the design requirements of the service design.

[0198] In one embodiment, the hierarchy of structural layers also includes a product layer.

[0199] In the embodiment of the present application, the backend of the user terminal may also store design requirements for the service design corresponding to the product layer.

[0200] The subordinate layers of the product layer include the resource layer, the network service layer and the business service layer. The design requirements of the service design corresponding to the product layer can be for any product layer, and the network topology structure corresponding to the product layer can include nodes involved in the business service layer, nodes involved in the network service layer, and nodes involved in the resource layer.

[0201] Furthermore, since the subordinate layers of the product layer include the resource layer, the network service layer and the business service layer, the user terminal can also verify each subordinate layer according to the design requirements of the service design corresponding to each subordinate layer.

[0202] In one embodiment, Figure 5 As shown, step 204 includes:

[0203] Step 502: Obtain the object structure of the data to be verified.

[0204] The data to be verified may carry an object structure of the data to be verified; the object structure is network topology information of the data to be verified, such as a network topology diagram of the data to be verified.

[0205] In the embodiment of the present application, the user terminal can determine the object structure of the data to be verified from the multiple files included in the data to be verified.

[0206] For determining the object structure of the data to be verified from the multiple files contained in the data to be verified, a method of assigning an identifier to the file corresponding to the object structure information can be adopted, so that the user terminal can identify the object structure information in the multiple files according to the identifier. Any method that enables the user terminal to identify the object structure information can be applied to the present application, and the embodiments of the present application do not limit this.

[0207] Step 504 , based on the design requirements of the service design of the structural layer to which the data to be verified belongs, verify the object structure of the data to be verified.

[0208] In an embodiment of the present application, the user terminal verifies the object structure of the data to be verified based on the design requirements of the service design corresponding to the structural layer to which the data to be verified belongs, and determines whether the object structure of the data to be verified meets the design requirements of the service design corresponding to the structural layer to which the data to be verified belongs.

[0209] In this embodiment, it is possible to determine whether there is a problem with the network topology structure of the data to be verified through the design requirements of the service design corresponding to the structural layer of the data to be verified, and then determine whether the data to be verified meets the design requirements of the service design.

[0210] In one embodiment, step 504 includes:

[0211] Step 602: When the object structure of the data to be verified does not meet the design requirements of the service design, the structural problem description and the first-level problem level are added to the verification result.

[0212] In the embodiment of the present application, when the object structure of the data to be verified does not meet the design requirements of the service design corresponding to the structural layer to which the data to be verified belongs, the user terminal adds the structural problem description identifier and the first-level problem level to the verification result.

[0213] Among them, the structural problem description can be used to reflect the object structure of the data to be verified, and the description and identification of the existing problems compared with the design requirements of the service design corresponding to the structural layer to which the data to be verified belongs. For example, the structural problem description can be "seriously inconsistent with the design concept of the PSR model, please make modifications", etc. The specific content of the structural problem description is not limited in the embodiments of the present application. The first-level problem level is used to reflect that the severity of the problems existing in the data to be verified is relatively high. For example, the first-level problem level can be a red mark. The embodiments of the present application do not limit the form and color of the first-level problem level mark. Any mark that can be used to reflect the high severity of the problem can be applied to the embodiments of the present application.

[0214] Step 604, when the object structure of the data to be verified meets the design requirements of the service design, the structural problem description and the three-level problem level are added to the verification result.

[0215] In the embodiment of the present application, when the object structure of the data to be verified meets the design requirements of the service design corresponding to the structural layer to which the data to be verified belongs, the user terminal adds the structural problem description and the three-level problem level corresponding to the structural problem description to the verification result.

[0216] Among them, the three-level problem level is used to reflect that there is no problem with the data to be verified or the impact of the problem can be ignored. For example, the three-level problem level logo can be a green logo. The embodiment of the present application does not limit the form and color of the three-level problem level logo. All logos that can be used to reflect that there is no problem with the data to be verified can be applied to the embodiment of the present application.

[0217] It can be understood that when the object structure of the data to be verified meets the design requirements of the service design corresponding to the structural layer to which the data to be verified belongs, it can be characterized that the object structure of the data to be verified meets the design concept of the PSR model. Therefore, the structural problem description corresponding to the data to be verified can reflect the object structure of the data to be verified and meet the description of the design requirements of the service design corresponding to the structural layer to which the data to be verified belongs. For example, the structural problem description of the data to be verified can be "complying with the design concept of the PSR model, please proceed to the next step, etc." The specific content of the structural problem description is not limited in the embodiments of the present application.

[0218] In this embodiment, it is possible to determine whether there is a network topology problem in the data to be verified, and to determine the severity of the network topology problem in the data to be verified through the structural problem description corresponding to the data to be verified and the levels of each problem, so that subsequent technical personnel can learn about the network topology problem of the data to be verified based on the verification report and make modifications.

[0219] In one embodiment, the method further includes:

[0220] According to the data to be verified, determine whether the calling data of the data to be verified exists.

[0221] In the embodiment of the present application, the user terminal determines the calling relationship of the data to be verified according to the data to be verified, and obtains the calling data of the data to be verified. The user terminal can determine whether the calling data of the data to be verified exists.

[0222] Exemplarily, the user terminal determines that file A calls data B whose path is path X based on the files in the data to be verified. Then, the user terminal can obtain data B called by file A based on path X. Data B is the calling data of the data to be verified. Therefore, the user terminal can determine that the calling data of the data to be verified exists.

[0223] It can be understood that the calling data of the data to be verified may include multiple ones.

[0224] In one embodiment, the method further includes:

[0225] According to the data to be verified, it is determined whether the status of the calling data of the data to be verified is available.

[0226] In an embodiment of the present application, the user terminal can obtain the status of the calling data of the data to be verified, and when the status of the calling data of the data to be verified is in an online state, determine that the status of the calling data of the data to be verified is an available state; when the status of the calling data of the data to be verified is not in an online state, determine that the status of the calling data of the data to be verified is an unavailable state.

[0227] In one embodiment, the method further includes:

[0228] According to the data to be verified, determine whether the data to be verified and the calling data of the data to be verified are complete.

[0229] In the embodiment of the present application, the user terminal can perform data integrity verification on the data to be verified and the calling data of the data to be verified, so as to determine whether the data to be verified and the calling data of the data to be verified are complete.

[0230] The user terminal can also determine whether the network topology structure of the data to be verified and the calling data of the data to be verified is complete according to the design requirements of the service design corresponding to the data to be verified and the calling data of the data to be verified.

[0231] In one embodiment, Figure 7 As shown, determining whether the status of the calling data of the data to be verified is available includes:

[0232] Step 702, obtaining the status of the calling data.

[0233] The state includes a first state and a second state. The first state is used to represent that the call data is in an online state, and the second state is used to represent that the call data is not in an online state.

[0234] In the embodiment of the present application, the calling data of the data to be verified includes data and the state of the data. The user terminal determines the state of the calling data of the data to be verified according to the calling data of the data to be verified.

[0235] The user terminal determines that the data is in an online state when the state of the calling data of the data to be verified is in a first state, and determines that the data is not in an online state when the state of the calling data of the data to be verified is in a second state.

[0236] Among them, the status that is not online may include but is not limited to the status of being designed, the status awaiting review, the status of being reviewed, the status of not passing review, and the status of being offline.

[0237] Step 704, based on the design requirements of the service design of the data to be verified, verify the status of the call data, and when the status of the call data is the second status, determine that the status of the call data is unavailable, and add the call problem description and the secondary problem level to the verification result.

[0238] In the embodiment of the present application, the user terminal verifies the status of the call data based on the design requirements of the service design of the data to be verified. When the status of the call data of the data to be verified is not online, the user terminal determines that the status of the call data of the data to be verified is unavailable, and adds the call problem description and the secondary problem level to the verification result.

[0239] Among them, the call problem description is used to reflect the status of the call data of the data to be verified, and is an identifier that does not meet the design requirements of the service design corresponding to the data to be verified. For example, when the status of the call data does not meet the design requirements of the service design, the call problem description identifier can be "the status of the call data of the data to be verified is not in the online state", etc. The specific content of the call problem description identifier is not limited in the embodiment of the present application. The secondary problem level is used to reflect that the severity of the problem existing in the data to be verified is moderate. For example, the identifier of the secondary problem level can be a yellow identifier. The embodiment of the present application does not limit the form and color of the identifier of the secondary problem level. Any identifier that can be used to reflect the moderate severity of the problem can be applied to the embodiment of the present application.

[0240] Step 706: When the state of the call data is the first state, determine that the state of the call data is available, and add the call problem description and the third-level problem level to the verification result.

[0241] In the embodiment of the present application, when the status of the calling data of the to-be-verified data is online, the user terminal determines that the status of the calling data of the to-be-verified data is available. The user terminal adds the calling problem description and the three-level problem level to the verification result.

[0242] Among them, when the status of the calling data is in an available state, the calling problem description can be "the status of the calling data of the data to be verified is in an online state". The specific content of the calling problem description is not limited in the embodiment of the present application.

[0243] In this embodiment, through the design requirements of the service design of the data to be verified, it is possible to determine whether there is a problem with the data call status of the data to be verified, and then determine the severity of the problem with the call status of the data to be verified, so that subsequent technical personnel can know the problem with the call status of the data to be verified based on the verification report and make modifications.

[0244] In one embodiment, the method further includes:

[0245] When the data type of the data to be verified is an object, object verification and object capability verification are performed on the data to be verified.

[0246] The object capability is an API (Application Programming Interface) associated with the data to be verified of the object type.

[0247] In the embodiment of the present application, when the data type of the data to be verified is an object, the user terminal can perform object verification and object capability verification on the data to be verified according to the design requirements of the service design of the object type.

[0248] In one embodiment, Figure 8 As shown, the above method also includes:

[0249] Step 802: When the data type of the data to be verified is an object, determine whether there is a first-level problem level in the verification result.

[0250] In the embodiment of the present application, when the data type of the data to be verified is an object, the user terminal determines whether there is a first-level problem level in the verification result corresponding to the data to be verified.

[0251] Step 804: when there is no first-level problem level in the verification result, the capability of the associated object of the data to be verified is obtained from the data to be verified.

[0252] Among them, API is one of the basic components for realizing object functions. When the data type of the data to be verified is an object (Object), the data to be verified must have an associated API to realize the function.

[0253] In the embodiment of the present application, when there is no level 1 problem in the verification result corresponding to the data to be verified, the user terminal determines that there is no serious problem in the verification of the data to be verified for the design requirements of the service design. Then, the user terminal determines whether there is an associated API of the data to be verified in the multiple files of the data to be verified based on the associated API acquisition strategy.

[0254] Among them, the associated API acquisition strategy is a strategy for acquiring the associated API (i.e., the API used to implement various functions of the object) associated with the object based on the data to be verified of the object type. For the associated API acquisition strategy, any method that can acquire the associated API of data of the object type can be applied to the present application, and the embodiments of the present application do not make specific limitations on this.

[0255] Step 806: When the data to be verified does not have the capability of associated objects, the structural problem description and the first-level problem level are added to the verification result.

[0256] In the embodiment of the present application, when there is no associated API for the data to be verified, the user terminal determines that the data to be verified does not meet the design requirements of the service design, and adds the structural problem description and the first-level problem level to the verification result.

[0257] Among them, when there is no associated API for the data to be verified, the structural problem description can be "there is no associated API for the data to be verified". The embodiment of the present application does not limit the specific content of the structural problem description.

[0258] Step 808: When the data to be verified has associated object capabilities, the structural problem description and the three-level problem level are added to the verification result.

[0259] In the embodiment of the present application, when there is an associated API in the data to be verified, the user terminal determines that the data to be verified meets the design requirements of the service design, and adds the structural problem description and the three-level problem level to the verification result.

[0260] Among them, when there is no associated API for the data to be verified, the structural problem description can be "there is an associated API for the data to be verified". The embodiment of the present application does not limit the specific content of the structural problem description.

[0261] In this embodiment, it is possible to determine whether the data to be verified of the object type has an associated API, and based on whether the data to be verified of the object type has an associated API, determine whether the data to be verified of the object type meets the design requirements of the service design.

[0262] In one embodiment, when the data type of the data to be verified is an object, determining whether the data to be verified is complete includes:

[0263] Determine whether the field information and object structure of the data to be verified are complete.

[0264] The first field is field information contained in data of a preset object type.

[0265] In the embodiment of the present application, the user terminal determines that the standard field corresponding to the field information of the data to be verified is the first field, and determines the object structure requirements corresponding to the data to be verified.

[0266] The user terminal determines whether the field information and the object structure of the data to be verified are complete according to the first field and the object structure requirement corresponding to the data to be verified.

[0267] The first field may be an object basic information field and an object attribute field, and the object basic information field is a mandatory field for the object. The object attribute field may include a dictionary type, a dictionary value, etc. The number and specific contents of the object basic information field and the object attribute field included in the first field may be set by technicians in actual applications, and this application does not limit this.

[0268] When the data type of the data to be verified is object capability, determining whether the data to be verified is complete includes:

[0269] Determine whether the field information and calling process information of the data to be verified are complete.

[0270] The second field is field information included in the data of the preset object capability type.

[0271] In the embodiment of the present application, the user terminal determines that the standard field corresponding to the field information of the data to be verified is the second field, and determines the call design requirements corresponding to the data to be verified.

[0272] The user terminal determines whether the field information and the calling process information of the data to be verified are complete according to the second field and the calling design requirements corresponding to the data to be verified.

[0273] Among them, the second field can be an API basic information field and an API attribute field, and the API basic information field is a required field of the API. The API attribute field can include an API value range, API parameters, etc. The number and specific content of the API basic information field and API attribute field contained in the second field can be set according to the technical personnel in actual application, and this application does not limit this.

[0274] In this embodiment, data integrity check can be performed on the data to be checked based on the data type of the data to be checked.

[0275] In one embodiment, Fig. 9 As shown, the above method also includes:

[0276] Step 902: Obtain field information and object structure from the data to be verified.

[0277] In an embodiment of the present application, when the data type of the data to be verified is an object, the user terminal obtains field information from the data to be verified according to the field keyword determination method, and determines the object structure of the data to be verified according to the network topology diagram of the data to be verified.

[0278] Among them, for the field keyword determination method, any algorithm that can match and obtain field information based on preset field keywords can be applied to the present application, and the embodiments of the present application do not limit this.

[0279] Step 904, perform data integrity verification on the field information and object structure of the data to be verified. If the field information of the data to be verified does not match the first field and / or the object structure of the data to be verified does not meet the object structure requirements, add the object integrity problem description and the secondary problem level to the verification result.

[0280] In the embodiment of the present application, the user terminal verifies the field information of the data to be verified based on the first field corresponding to the data to be verified. If the number of field information of the data to be verified is different from the number of field information of the first field, the user terminal determines that the field information of the data to be verified does not match the first field.

[0281] Exemplarily, when the field information of the data to be verified is three fields, namely field A, field B, and field C, and the field information of the first field is four fields, namely field A, field B, field C, and field D, the user terminal determines that the number of field information of the data to be verified is different from the number of field information of the first field.

[0282] When the specific content of the field information of the data to be verified is different from the specific content of the field information of the first field, the user terminal determines that the field information of the data to be verified does not match the first field.

[0283] Exemplarily, when the field information of the data to be verified is three fields, namely field A, field B and field C, and the field information of the first field is three fields, namely field B, field C and field D, the user terminal determines that the specific content of the field information of the data to be verified is different from the specific content of the field information of the first field.

[0284] When the field information of the data to be verified does not match the first field, the user terminal adds the object integrity problem description and the secondary problem level to the verification result.

[0285] The user terminal verifies the object structure of the data to be verified based on the object structure requirements, determines whether the boundary nodes in the object structure of the data to be verified are the same as the boundary nodes in the object structure requirements, and determines whether each node in the object structure exists and whether the status of each node is in an online state. If the boundary nodes in the object structure of the data to be verified are different from the boundary nodes in the object structure requirements, or any node in the object structure does not exist, or the status of any node in the object structure is not in an online state, the user terminal determines that the object structure of the data to be verified does not meet the object structure requirements.

[0286] When the object structure of the data to be verified does not meet the object structure requirements, the user terminal adds the object integrity problem description and the secondary problem level to the verification result.

[0287] The object integrity problem description is used to reflect whether there is a problem with the data to be verified during the data integrity verification process. When there is a problem with the data to be verified during the data integrity verification process, the object integrity problem description may be "the object structure of the data to be verified does not meet the object structure requirements", "the field information of the data to be verified does not match the first field", etc. The specific content of the object integrity problem description is not limited in the embodiments of the present application.

[0288] Step 906: When the field information of the data to be verified matches the first field and the object structure of the data to be verified meets the object structure requirement, the object integrity problem description and the third-level problem level are added to the verification result.

[0289] In the embodiment of the present application, when the field information of the data to be verified matches the first field and the object structure of the data to be verified meets the object structure requirements, the user terminal adds the object integrity problem description and the three-level problem level to the integrity verification result.

[0290] Among them, when there is no problem with the data to be verified during the data integrity verification process, the object integrity problem description can be "the object structure of the data to be verified meets the object structure requirements and the field information of the data to be verified matches the first field", etc. The specific content of the object integrity problem description identifier is not limited in the embodiment of the present application.

[0291] In this embodiment, the user terminal can perform data integrity verification on the data to be verified and obtain the verification result, so that the technician can know whether there is a data incompleteness problem in the data to be verified and the severity of the problem according to the object integrity problem description and problem level, so that the technician can modify the data to be verified according to the verification result, and can verify the data to be verified again after the modification is completed.

[0292] In one embodiment, Fig.10 As shown, when the data type of the data to be verified is object capability, step 204 includes:

[0293] Step 1002, obtaining field information and calling process information from the data to be verified.

[0294] In an embodiment of the present application, when the data type of the data to be verified is object capability (ie, API), the user terminal obtains field information from the data to be verified according to the field keyword determination method, and determines the calling process information of the data to be verified of the object capability type.

[0295] The calling process information of the data to be verified of the object capability type includes the data to be verified being called by the object (Object) and the data to be verified not being called by the object.

[0296] Step 1004, verify the field information and calling process information of the data to be verified. If the field information of the data to be verified does not match the second field and / or the calling process information of the data to be verified does not meet the calling design requirements, the object capability integrity problem description and the secondary problem level are added to the verification result.

[0297] In an embodiment of the present application, the user terminal verifies the field information of the data to be verified based on the second field corresponding to the data to be verified. When the number of field information of the data to be verified is different from the number of field information of the second field, the user terminal determines that the field information of the data to be verified does not match the second field. When the specific content of the field information of the data to be verified is different from the specific content of the field information of the second field, the user terminal determines that the field information of the data to be verified does not match the second field.

[0298] When the field information of the data to be verified does not match the second field, the user terminal adds the object capability integrity problem description and the secondary problem level to the verification result.

[0299] The user terminal verifies the calling process information of the data to be verified based on the calling design requirements, and determines that the calling process information of the data to be verified does not meet the calling design requirements when the data to be verified is not called by the object. The user terminal adds the object capability integrity problem description and the secondary problem level to the verification result.

[0300] Among them, the object capability integrity problem description is used to reflect whether there is a problem with the data to be verified during the data integrity verification process. When there is a problem with the data to be verified during the data integrity verification process, the object capability integrity problem description can be "the calling process information of the data to be verified does not meet the calling design requirements", "the field information of the data to be verified does not match the second field", etc. The specific content of the object capability integrity problem description is not limited in the embodiments of the present application.

[0301] Step 1006, when the field information of the data to be verified matches the second field and the calling process information of the data to be verified meets the calling design requirements, the object capability integrity problem description and the third-level problem level are added to the verification result.

[0302] In the embodiment of the present application, the user terminal adds the object capability integrity problem description and the third-level problem level to the verification result when the field information of the data to be verified matches the second field and the calling process information of the data to be verified meets the calling design requirements.

[0303] Among them, when there is no problem with the data to be verified during the data integrity verification process, the object capability integrity problem description can be "the calling process information of the data to be verified meets the calling design requirements and the field information of the data to be verified matches the second field", etc. The specific content of the description of the object capability integrity problem is not limited in the embodiment of the present application.

[0304] The backend of the user terminal may also store data mapping rules for determining whether there is a data mapping relationship between objects and capabilities of each object.

[0305] In this embodiment, the user terminal performs data integrity verification on the data to be verified and obtains the verification result, so that the technician can know whether there is a data incomplete problem in the data to be verified and the severity of the problem according to the object capability integrity problem description and problem level, so that the technician can modify the data to be verified according to the verification result, and can verify the data to be verified again after the modification is completed.

[0306] In one embodiment, the problem level identifier includes a primary problem level, a secondary problem level, and a tertiary problem level.

[0307] Among them, the priority of the first-level problem level representation is higher than the priority of the second-level problem level representation, and the priority of the second-level problem level representation is higher than the priority of the third-level problem level representation.

[0308] In the embodiment of the present application, the first-level problem level indicates that the severity of the problem existing in the data to be verified is high, the second-level problem level indicates that the severity of the problem existing in the data to be verified is moderate, and the third-level problem level indicates that there is no problem in the data to be verified. Therefore, the verification result with the first-level problem level indicates that the priority of the data to be verified needs to be modified is higher than the priority of the second-level problem level, and the verification result with the second-level problem level indicates that the priority of the data to be verified needs to be modified is higher than the priority of the third-level problem level.

[0309] In one embodiment, Fig.11 As shown, step 206 includes:

[0310] Step 1102, when there is no first-level problem level in the verification result, obtain the number of second-level problem levels in the verification result.

[0311] In an embodiment of the present application, the user terminal determines whether there is an identifier of the first-level problem level in the verification result. If there is no identifier of the first-level problem level in the verification result, the user terminal obtains the number of identifiers of the second-level problem level in the verification result.

[0312] It can be understood that the presence of a first-level problem level identifier in the verification result can indicate that the data to be verified does not meet the design requirements of the service design. Therefore, in the absence of a first-level problem level identifier in the verification result, it can indicate that the data to be verified meets the design requirements of the service design.

[0313] Step 1104: When the number of the second-level problem levels in the verification result is greater than a preset number, each second-level problem level is combined into a first-level problem level.

[0314] In an embodiment of the present application, the user terminal may store a preset number of secondary problem level identifiers corresponding to the secondary problem level identifiers. When the number of secondary problem level identifiers in the verification result is greater than the preset number of secondary problem level identifiers corresponding to the secondary problem level identifiers, the identifiers of each secondary problem level are combined into a primary problem level identifier.

[0315] Exemplarily, the preset number may be 2, and the number of secondary problem level identifiers in the verification result is 3. Therefore, the user terminal can determine that the number of secondary problem level identifiers in the verification result is greater than the preset number, and therefore, the 3 secondary problem level identifiers are combined into one primary problem level identifier.

[0316] It can be understood that when there are multiple secondary problem level identifiers representing moderate severity of the problem in the data to be verified, it can be represented that the severity of the problem in the data to be verified is moderate and high. Therefore, the identifiers of the secondary problem levels of the data to be verified are combined into a first-level problem level identifier, so that the user terminal can check and modify the data to be verified, thereby reducing the severity of the problem in the data to be verified.

[0317] Step 1106: Generate a verification report for the data to be verified based on the description of each problem in the verification result and the first-level problem level.

[0318] In the embodiment of the present application, after the user terminal synthesizes the identifiers of each secondary problem level into an identifier of the primary problem level, it generates a verification report for the data to be verified based on the descriptions of each problem in the verification result and the primary problem level.

[0319] Exemplarily, the verification report of the data to be verified may include an identifier A of the calling problem description, an identifier B of the integrity problem description, an identifier C of the integrity problem description, and a red identifier (ie, a first-level problem level identifier).

[0320] In this embodiment, when the number of secondary problem level identifiers in each verification result is greater than a preset number, the user terminal can synthesize the secondary problem level identifiers in each verification result into a first-level problem level identifier, thereby achieving an upgrade of the severity of the problem in the verification data when there are multiple problem levels with moderate severity, making it easier for subsequent technical personnel to modify the verification data based on the first problem level identifier in the verification report, thereby improving the reliability of product design.

[0321] In one embodiment, Fig.12 As shown, the above method also includes:

[0322] Step 1202: When the number of secondary problem levels in the verification result is less than or equal to a preset number, the number of each problem level identifier is obtained.

[0323] When the number of identifiers of the secondary problem level in the verification result is less than or equal to a preset number, the user terminal obtains the number of identifiers of each problem level.

[0324] Exemplarily, the preset number may be 2, and the number of secondary problem level identifiers in the verification result is 2. Therefore, the user terminal can determine that the number of secondary problem level identifiers in the verification result is equal to the preset number. When the number of secondary problem level identifiers in the verification result is equal to the preset number, the user terminal obtains the number of identifiers of each problem level. For example, the number of primary problem level identifiers in the verification result is 1, and the number of secondary problem level identifiers is 2.

[0325] Step 1204, determining a target problem level among multiple problem levels.

[0326] In the embodiment of the present application, the user terminal determines, among multiple problem levels, a problem level represented by a problem level having the highest priority as a target problem level.

[0327] Exemplarily, when the first-level problem level in the verification result is 1 and the second-level problem level is 2, the user terminal determines that the first-level problem level representation has the highest priority, and therefore determines the first-level problem level as the target problem level.

[0328] Step 1206: Generate a verification report for the data to be verified based on each problem description and the target problem level.

[0329] In an embodiment of the present application, in an embodiment of the present application, the user terminal can generate a verification report for the data to be verified based on multiple problem descriptions and target problem levels.

[0330] In this embodiment, since the verification report of the data to be verified is used to record the problem description of the data to be verified and reflect the severity of the problem, a problem level can be selected as the target problem level so that the user can know the severity of the problem of the data to be verified, thereby modifying the data to be verified. In addition, the problem description can also record the location of the problem of the data to be verified, which is convenient for the user to locate the location of the problem, thereby improving the efficiency of modifying the data to be verified.

[0331] In one embodiment, Fig.13 As shown, the above method also includes:

[0332] Step 1302, monitor the problem level in the verification result, and stop the verification process when it is monitored that a level 1 problem level is generated in the verification result.

[0333] In the embodiment of the present application, the user terminal can perform service design design content and data integrity verification on the verification data. When verifying the verification data, the user terminal monitors the verification results in real time, and stops the verification process when a level 1 problem level mark is generated in any verification result.

[0334] Exemplarily, when the user terminal verifies the data to be verified based on the design requirements of the service design, if the user terminal detects that an identifier of a first-level problem level is generated in the verification result, the user terminal will not perform data integrity verification on the data to be verified.

[0335] It is understandable that when no identification of the first-level problem level is continuously detected in the verification result, the user terminal completes the design content of the service design for the verification data and the data integrity verification.

[0336] Step 1304, generating a verification report for the data to be verified based on the problem description and the first-level problem level in the current verification result.

[0337] In the embodiment of the present application, the user terminal generates a verification report for the data to be verified based on the problem description and the first-level problem level in the current verification result.

[0338] In this embodiment, when there is a first-level problem level mark in the current verification result of the data to be verified, further verification of the data to be verified is stopped, which can save computing resources. When there is no first-level problem level mark in the current verification result of the data to be verified, further verification of the data to be verified is continued until the design content and data integrity verification of the service design of the data to be verified are completed. The computing resource utilization rate in the data verification process can be improved.

[0339] In one embodiment, Fig.14 As shown, after step 206, the following steps are also included:

[0340] Step 1402 : When the verification report of the data to be verified indicates that the data to be verified has passed the verification, a manual review request is generated based on the data to be verified.

[0341] Among them, the manual review request is a review request for manual review by the reviewer after the data to be verified is sent to the review terminal.

[0342] In the embodiment of the present application, when there is no first-level problem level in the verification report of the data to be verified, it can be indicated that the verification of the data to be verified has passed.

[0343] In one implementation, when the data to be verified passes verification, the user terminal generates a review request carrying the data to be verified according to the review submission operation performed by the user.

[0344] In another implementation, when the verification report of the data to be verified indicates that the data to be verified has passed the verification, the user terminal may also generate an automatic review request based on the data to be verified. The automatic review request is an audit request for automatic review by preset audit rules after the data to be verified is sent to the audit terminal. The preset audit rules may be rules set by the auditor in actual applications and executed by the audit terminal. This application does not specifically limit the preset audit rules.

[0345] When the data to be verified passes the verification, the user terminal can automatically generate an automatic review request carrying the data to be verified.

[0346] Step 1404: After the data to be verified is reviewed and approved, the data to be verified is allowed to be packaged.

[0347] In an embodiment of the present application, after the user terminal sends the review request to the review terminal, the review terminal reviews the data to be verified based on the data to be verified carried in the review request. After the data to be verified is reviewed and passed, the review terminal can respond to the reviewer's confirmation of the review pass operation and return a review pass message to the user terminal.

[0348] The audit terminal is a terminal that receives an audit request carrying data to be verified and audits the data to be verified.

[0349] Optionally, the audit terminal may also automatically perform an audit pass confirmation operation in response to the automatic audit passing, and return an audit pass message to the user terminal.

[0350] The user terminal receives the audit pass message sent by the audit terminal, determines that the data to be verified meets the data release conditions based on the audit pass message, and allows the data to be verified to be packaged.

[0351] In this embodiment, after the verification report of the data to be verified indicates that the data to be verified has passed the verification, the user terminal can further verify the data to be verified through the verification terminal to ensure that the data to be verified meets the data release conditions, thereby improving the reliability of the data to be verified.

[0352] In one embodiment, Fig.15 As shown, a processing example of a service design verification method is also provided, and the specific contents include:

[0353] Step A1, during the design phase, select an object on the front-end platform corresponding to the product and click on "Inspect" to trigger automatic inspection to inspect the object.

[0354] The object may be a customer facing service (CFS) of a fixed dedicated line. The IPRAN (IP Radio Access Network) access scenario of the fixed dedicated line consists of IPRAN PW (Pseudowire) access and IPRAN-CN2 Layer 3 VPN (a Layer 3 virtual private network implemented by using VPN (Virtual Private Network) technology in IPRAN (IP Radio Access Network)) access.

[0355] Step A2, determining whether the status of the calling data of the data to be verified is available.

[0356] Step A3: verify the resource layer in the object structure of the object.

[0357] In the embodiment of the present application, the user terminal checks whether the IPRAN PW access and the IPRAN-CN2 Layer 3 VPN access exist and whether the status is online. If not, the check fails and is marked as yellow.

[0358] Step A4: Check whether the object structure of the object meets the object structure requirements.

[0359] For example, determine whether the network topology of CFS meets the object structure requirements (such as whether the boundary devices between RFS (resourcefacing service) are consistent, etc.). If not, the check fails and is marked in red. And determine whether there are isolated nodes in the network topology conversion scene topology. If so, the check fails and is marked in yellow.

[0360] Step A5: perform data integrity check on the object.

[0361] Exemplarily, it is checked whether a data mapping relationship between the fixed network dedicated line CFS to the IPRAN PW access and the IPRAN-CN2 layer 3 VPN access exists.

[0362] The user terminal verifies whether the attributes of IPRAN PW access and IPRAN-CN2 Layer 3 VPN access exist. If not, the verification fails and is marked in yellow. The user terminal verifies whether the call data (such as object attributes, etc.) of the data mapping rule exists. If not, the verification fails and is marked in yellow.

[0363] The user terminal verifies whether the data (such as dictionary value, dictionary value range, etc.) called in the attributes of the fixed network dedicated line CFS exists. If not, the verification fails and is marked in yellow. The user terminal verifies whether the fixed network dedicated line CFS has an associated API. If not, the verification fails and is marked in red.

[0364] It should be understood that although Figure 2-14 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2-14 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0365] In one embodiment, Fig.16 As shown, a service design verification device 1600 is provided, comprising: a first acquisition module 1602, a first verification module 1604 and a first generation module 1606, wherein:

[0366] The first acquisition module 1602 is used to acquire the data to be verified, determine the data type of the data to be verified and the structural layer to which the data to be verified belongs;

[0367] The first verification module 1604 is used to verify the design content of the service design and the data integrity content of the data to be verified based on the verification method of the structural layer to which the data to be verified belongs, and obtain a verification result, wherein the verification result includes a problem description and a problem level of the data to be verified;

[0368] The first generating module 1606 is used to generate a verification report of the data to be verified according to the problem description and problem level in the verification result.

[0369] By using the service design verification device provided by the embodiment of the present disclosure, the design content and data integrity of the service design can be verified on the data to be verified, so as to determine whether the data to be verified meets the design concept of the PSR model. Before the product goes online, design problems that may arise in the product design process can be pre-reviewed and processed, thereby saving labor costs and improving the efficiency of product verification and product release.

[0370] In one embodiment, the first acquisition module 1602 is specifically used for:

[0371] The data to be verified is obtained through a trigger operation, and the types of the trigger operation include automatic triggering and manual triggering.

[0372] In one embodiment, the automatic triggering is triggered at any time.

[0373] In one embodiment, the first verification module 1604 is specifically used for:

[0374] Verify whether the status of the data to be verified and the calling data of the data to be verified meet the design requirements of the service design.

[0375] In one embodiment, the levels of the structural layer include a business service layer or service layer, a network service layer or sub-service layer, and a resource layer.

[0376] In one embodiment, the hierarchy of structural layers further includes a product layer.

[0377] In one embodiment, the first verification module 1604 is specifically used for:

[0378] Obtaining the object structure of the data to be verified;

[0379] Based on the design requirements of the service design of the structural layer to which the data to be verified belongs, the object structure of the data to be verified is verified.

[0380] In one embodiment, the first verification module 1604 is specifically used for:

[0381] In the case where the object structure of the data to be verified does not meet the design requirements of the service design, adding the structural problem description and the first-level problem level to the verification result; or,

[0382] In the case that the object structure of the data to be verified meets the design requirements of the service design, the structural problem description and the three-level problem level are added to the verification result.

[0383] In one embodiment, the apparatus further comprises:

[0384] The first determining module is used to determine whether the calling data of the data to be verified exists according to the data to be verified.

[0385] In one embodiment, the apparatus further comprises:

[0386] The second determining module is used to determine whether the status of the calling data of the data to be verified is available according to the data to be verified.

[0387] In one embodiment, the apparatus further comprises:

[0388] The third determination module is used to determine whether the data to be verified and the calling data of the data to be verified are complete according to the data to be verified.

[0389] In one embodiment, the second determining module is specifically configured to:

[0390] Acquire the state of the call data, the state including a first state and a second state, the first state is used to indicate that the call data is in an online state, and the second state is used to indicate that the call data is not in an online state;

[0391] Based on the design requirements of the service design of the data to be verified, verify the state of the call data, and if the state of the call data is the second state, determine that the state of the call data is unavailable, and add the call problem description and the secondary problem level to the verification result; or

[0392] In a case where the state of the call data is the first state, it is determined that the state of the call data is available, and the call problem description and the third-level problem level are added to the verification result.

[0393] In one embodiment, the apparatus further comprises:

[0394] The second verification module is used to perform object verification and object capability verification on the data to be verified when the data type of the data to be verified is an object.

[0395] In one embodiment, the apparatus further comprises:

[0396] A fourth determination module, configured to determine whether there is a first-level problem level in the verification result when the data type of the data to be verified is an object;

[0397] A second acquisition module is used to acquire the associated object capability of the data to be verified from the data to be verified when the first-level problem level does not exist in the verification result;

[0398] A first adding module is used to add the structural problem description and the first-level problem level to the verification result when the data to be verified does not have the associated object capability; or

[0399] The second adding module is used to add the structural problem description and the three-level problem level to the verification result when the data to be verified has associated object capabilities.

[0400] In one embodiment, when the data type of the to-be-verified data is an object, the third determination module is specifically configured to:

[0401] Determine whether a first field and an object structure of the data to be verified are complete, wherein the first field is field information included in data of a preset object type;

[0402] In a case where the data type of the data to be verified is object capability, determining whether the data to be verified is complete includes:

[0403] Determine whether the second field of the data to be verified and the calling design requirements are complete, the second field being field information included in data of a preset object capability type.

[0404] In one embodiment, the device further comprises:

[0405] A third acquisition module is used to acquire field information and object structure from the data to be verified;

[0406] The third adding module is used to perform data integrity verification on the field information and object structure of the data to be verified.

[0407] In case the first field does not match and / or the object structure of the data to be verified does not meet the object structure requirement, the object integrity problem description and the secondary problem level are added to the verification result;

[0408] A fourth adding module is used to add the object integrity problem description and the third-level problem level to the verification result when the field information of the data to be verified matches the first field and the object structure of the data to be verified meets the object structure requirement.

[0409] In one embodiment, when the data type of the to-be-verified data is object capability, the first verification module 1604 is specifically configured to:

[0410] Acquire field information and call flow information from the data to be verified;

[0411] Verify the field information and call process information of the data to be verified, and if the field information of the data to be verified does not match the second field and / or the call process information of the data to be verified does not meet the call design requirements, add the object capability integrity problem description and the secondary problem level to the verification result; or

[0412] When the field information of the data to be verified matches the second field and the calling process information of the data to be verified meets the calling design requirements, the object capability integrity problem description and the three-level problem level are added to the verification result.

[0413] In one embodiment, the problem level includes a first-level problem level, a second-level problem level and a third-level problem level, the priority of the first-level problem level representation is higher than the priority of the second-level problem level representation, and the priority of the second-level problem level representation is higher than the priority of the third-level problem level representation.

[0414] In one embodiment, the first generating module 1606 is specifically used for:

[0415] In the case that there is no first-level problem level in the verification result, obtaining the number of the second-level problem levels in the verification result;

[0416] When the number of the second-level problem levels in the verification result is greater than a preset number, combining the second-level problem levels into a first-level problem level;

[0417] Based on the description of each problem in the verification result and the first-level problem level, a verification report of the data to be verified is generated.

[0418] In one embodiment, the apparatus further comprises:

[0419] A fourth acquisition module, configured to acquire the number of each of the problem levels when the number of the secondary problem levels in the verification result is less than or equal to the preset number;

[0420] A fifth determination module, used to determine a target problem level among the plurality of problem levels;

[0421] The second generating module is used to generate a verification report of the data to be verified based on each problem description and the target problem level.

[0422] In one embodiment, the apparatus further comprises:

[0423] A monitoring module, used for monitoring the problem level in the verification result, and stopping the verification process when the first-level problem level is detected in the verification result;

[0424] The third generating module is used to generate a verification report of the data to be verified according to the problem description in the current verification result and the first-level problem level.

[0425] In one embodiment, the apparatus further comprises:

[0426] A fourth generating module, configured to generate a manual review request based on the data to be verified when the verification report of the data to be verified indicates that the data to be verified has passed the verification;

[0427] The packaging module is used to allow the data to be verified to be packaged after the data to be verified is reviewed and approved.

[0428] For the specific definition of the service design inspection device, please refer to the definition of the service design inspection method above, which will not be repeated here. Each module in the above-mentioned service design inspection device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0429] In one embodiment, a communication device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0430] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0431] In one embodiment, a chip is provided, including a programmable logic circuit and / or program instructions, and when the chip is executed, the steps in the above method embodiments are implemented.

[0432] The embodiments of the present application also provide a computer program product including instructions, which, when executed on a computer, enables the computer to execute the steps in the above-mentioned method embodiments.

[0433] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0434] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0435] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A service design inspection method, characterized in that: The method comprises: Acquire the data to be verified, and determine the data type of the data to be verified and the structural layer to which the data to be verified belongs; Based on the verification method of the structural layer to which the data to be verified belongs, the design content and data integrity of the service design of the data to be verified are verified to obtain a verification result; A verification report for the data to be verified is generated based on the problem description and problem level in the verification result.

2. The method according to claim 1, characterized in that: The obtaining of the data to be verified comprises: The data to be verified is obtained through a trigger operation, and the types of the trigger operation include automatic triggering and manual triggering.

3. The method according to claim 2, characterized in that The automatic triggering is triggered at any time.

4. The method according to claim 1 or 2, characterized in that: Performing a design content verification of the service design on the data to be verified includes: Verify whether the status of the data to be verified and the calling data of the data to be verified meet the design requirements of the service design.

5. The method according to claim 4, characterized in that The levels of the structural layer include a business service layer or service layer, a network service layer or sub-service layer, and a resource layer.

6. The method according to claim 5, characterized in that The hierarchy of the structural layer also includes a product layer.

7. The method according to claim 1, characterized in that The verification method based on the structural layer to which the data to be verified belongs, performing service design design content and data integrity content verification on the data to be verified, includes: Obtaining the object structure of the data to be verified; Based on the design requirements of the service design of the structural layer to which the data to be verified belongs, the object structure of the data to be verified is verified.

8. The method according to claim 7, characterized in that The verification method based on the structural layer to which the data to be verified belongs, performing a design content and data integrity verification of the service design on the data to be verified, and obtaining a verification result, includes: In the case where the object structure of the data to be verified does not meet the design requirements of the service design, adding the structural problem description and the first-level problem level to the verification result; or, In the case that the object structure of the data to be verified meets the design requirements of the service design, the structural problem description and the three-level problem level are added to the verification result.

9. The method according to claim 1 or 7, characterized in that: The method further comprises: According to the data to be verified, it is determined whether the calling data of the data to be verified exists.

10. The method according to claim 1 or 7, characterized in that: The method further comprises: According to the data to be verified, it is determined whether the status of the calling data of the data to be verified is available.

11. The method according to any one of claims 1 to 3 or 7, characterized in that: The method further comprises: According to the data to be verified, it is determined whether the data to be verified and the calling data of the data to be verified are complete.

12. The method according to claim 10, characterized in that The determining whether the state of the calling data of the data to be verified is available includes: Acquire the state of the call data, the state including a first state and a second state, the first state is used to indicate that the call data is in an online state, and the second state is used to indicate that the call data is not in an online state; Based on the design requirements of the service design of the data to be verified, verify the state of the call data, and if the state of the call data is the second state, determine that the state of the call data is unavailable, and add the call problem description and the secondary problem level to the verification result; or In a case where the state of the call data is the first state, it is determined that the state of the call data is available, and the call problem description and the third-level problem level are added to the verification result.

13. The method according to claim 7, characterized in that The method further comprises: In the case that the data type of the data to be verified is an object, object verification and object capability verification are performed on the data to be verified.

14. The method according to claim 7, characterized in that The method further comprises: In the case where the data type of the data to be verified is an object, determining whether there is a first-level problem level in the verification result; When the first-level problem level does not exist in the verification result, acquiring the associated object capability of the data to be verified from the data to be verified; In the case that the data to be verified does not have the associated object capability, adding the structural problem description and the first-level problem level to the verification result; or, In the case where the data to be verified has associated object capabilities, the structural problem description and the three-level problem level are added to the verification result.

15. The method according to claim 11, characterized in that In a case where the data type of the data to be verified is an object, determining whether the data to be verified is complete includes: Determine whether the field information and object structure of the data to be verified are complete; In a case where the data type of the data to be verified is object capability, determining whether the data to be verified is complete includes: Determine whether the field information and calling process information of the data to be verified are complete.

16. The method according to claim 15, characterized in that The method further comprises: Acquire field information and object structure from the data to be verified; Performing data integrity verification on the field information and object structure of the data to be verified, and adding the object integrity problem description and the secondary problem level to the verification result when the field information of the data to be verified does not match the first field and / or the object structure of the data to be verified does not meet the object structure requirement; or When the field information of the data to be verified matches the first field and the object structure of the data to be verified meets the object structure requirement, the object integrity problem description and the three-level problem level are added to the verification result.

17. The method according to claim 15, characterized in that When the data type of the data to be verified is object capability, based on the verification method of the structural layer to which the data to be verified belongs, performing data integrity verification on the data to be verified to obtain a verification result includes: Acquire field information and call flow information from the data to be verified; Verify the field information and call process information of the data to be verified, and if the field information of the data to be verified does not match the second field and / or the call process information of the data to be verified does not meet the call design requirements, add the object capability integrity problem description and the secondary problem level to the verification result; or When the field information of the data to be verified matches the second field and the calling process information of the data to be verified meets the calling design requirements, the object capability integrity problem description and the three-level problem level are added to the verification result.

18. The method according to claim 1, characterized in that The problem levels include a first-level problem level, a second-level problem level and a third-level problem level, the priority of the first-level problem level representation is higher than the priority of the second-level problem level representation, and the priority of the second-level problem level representation is higher than the priority of the third-level problem level representation.

19. The method according to claim 16 or 17, characterized in that Generating a verification report of the data to be verified according to the problem description and problem level in the verification result includes: In the case that there is no first-level problem level in the verification result, obtaining the number of the second-level problem levels in the verification result; When the number of the second-level problem levels in the verification result is greater than a preset number, combining the second-level problem levels into a first-level problem level; Based on the description of each problem in the verification result and the first-level problem level, a verification report of the data to be verified is generated.

20. The method according to claim 19, characterized in that The method further comprises: When the number of the secondary problem levels in the verification result is less than or equal to the preset number, obtaining the number of each problem level; Determining a target problem level among the plurality of said problem levels; Based on the description of each problem and the target problem level, a verification report of the data to be verified is generated.

21. The method according to claim 19, characterized in that The method further comprises: monitoring the problem level in the verification result, and stopping the verification process when the first-level problem level is detected in the verification result; A verification report for the data to be verified is generated based on the problem description in the current verification result and the first-level problem level.

22. The method according to claim 1, characterized in that After generating the verification report of the data to be verified according to the problem description and problem level in the verification result, the method further includes: When the verification report of the data to be verified indicates that the data to be verified has passed the verification, generating a manual review request based on the data to be verified; After the data to be verified is reviewed and approved, the data to be verified is allowed to be packaged.

23. A service design inspection device, characterized in that: The device comprises: A first acquisition module is used to acquire the data to be verified, and determine the data type of the data to be verified and the structural layer to which the data to be verified belongs; A first verification module is used to verify the design content of the service design and the data integrity content of the data to be verified based on the verification method of the structural layer to which the data to be verified belongs, and obtain a verification result, wherein the verification result includes a problem description and a problem level of the data to be verified; The first generating module is used to generate a verification report of the data to be verified according to the problem description and problem level in the verification result.

24. A communication device, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 22 are implemented.

25. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 22 are implemented.

26. A chip, characterized in that: The chip comprises a programmable logic circuit and / or program instructions, and the steps of the method according to any one of claims 1 to 22 are implemented when the chip is executed.

27. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 22 are implemented.

Images