Multi-platform service protocol management system

Abstract

The invention provides a multi-platform service protocol management system. The multi-platform service protocol management system comprises a service protocol management module, a service quantity acquisition module and a service quantity statistics module, the service protocol management module has a protocol management function for a service protocol of the third-party protocol management platform, and the protocol management function comprises a protocol editing function for constructing an association relationship between the service protocol and a plurality of service directories; the service directory is used for representing cooperation items signed by the multi-platform service protocol management system and a third-party protocol management platform; the service quantity acquisition module has a rule configuration function for constructing a data acquisition rule, and is used for acquiring quantity data on which a plurality of service directories depend from the third-party protocol management platform according to the data acquisition rule; and the service quantity statistics module has a logic configuration function for constructing data statistics logic and is used for generating a monthly consumption bill and a real-time consumption report according to the data statistics logic and the consumption data.

Description

Technical Field

[0001] The present invention mainly relates to the technical field of data management, and particularly relates to a multi-platform service agreement management system. Background Art

[0002] Currently, when service providers provide service agreements, they will record the basic information and service terms of the service agreements through some third-party agreement management platforms. However, with the increase in service agreements, a large amount of manpower and material resources are required to strengthen the management of the third-party agreement management platforms, which cannot meet the current service providers' requirements for efficient, accurate, and automated service management. Summary of the Invention

[0003] The purpose of the present invention is to provide a multi-platform service agreement management system, which simplifies the service agreement management process through an integrated system and supports data collection and analysis of multiple third-party agreement management platforms, aiming to improve the efficiency and automation level of service management.

[0004] The technical solution of the present application lies in:

[0005] In a first aspect, the present application provides a multi-platform service agreement management system, which is connected to multiple third-party agreement management platforms and multiple clients. The multi-platform service agreement management system includes a service agreement management module, a service volume collection module, and a service volume statistics module;

[0006] The service agreement management module has a protocol management function for the service agreements of the third-party agreement management platforms. The protocol management function includes a protocol editing function for constructing the association relationship between the service agreements and multiple service directories, where the service directories are used to represent the cooperation items signed between the multi-platform service agreement management system and the third-party agreement management platforms, and the cooperation items include multiple service level agreement (SLA) indicators required to achieve business goals;

[0007] The service volume collection module has a rule configuration function for constructing data collection rules, and is used to collect the usage data on which the multiple service directories depend from the third-party agreement management platforms according to the data collection rules;

[0008] The service volume statistics module has a logic configuration function for constructing data statistics logic, and is used to generate monthly usage bills and real-time usage reports according to the data statistics logic and the usage data.

[0009] In one implementation, the protocol editing function includes four types of first menu functions, and the four types of first menu functions include a service directory adding function, a batch import function, an SLA editing function, and an SLA automatic update function.

[0010] In one implementation, the multi-platform service protocol management system further includes a service catalog management module and an SLA management module;

[0011] The service catalog management module has a catalog management function for the service catalog, and the catalog management function includes any one or combination of a service catalog creation function, a service catalog batch import function, a service catalog editing function, a service catalog deletion function, a service catalog submission function, and a service catalog approval function;

[0012] The SLA management module has an SLA management function for the SLA metrics, and the SLA management function includes any one or combination of an SLA creation function, an SLA batch import function, an SLA deletion function, an SLA submission function, and an SLA approval function.

[0013] In one implementation, the SLA management function includes an SLA editing function for constructing an association relationship between the service catalog and the SLA metrics, and the SLA editing function includes four types of second menu functions, and the four types of second menu functions include a service catalog association function, a signing agency editing function, a quantitative metric editing function, and a qualitative metric editing function.

[0014] In one implementation, the rule configuration function includes any one or combination of a multi-platform management function, an execution cycle configuration function, a collection execution configuration function, an execution log viewing function, and a collection service volume deletion function.

[0015] In one implementation, the logic configuration function includes any one or combination of a logic creation function, a logic editing function, a logic statistical execution function, and a logic deletion function;

[0016] The logic editing function includes four types of third menu functions, and the four types of third menu functions include an exception system filtering function, a branch settlement mode configuration function, an execution plan configuration function, and a custom retrieval condition configuration function.

[0017] In one implementation, the multi-platform service protocol management system further includes a real-time report management module;

[0018] The real-time report management module has any one or combination of a service catalog statistical overview function, a historical data archiving function, a data verification function, and a data export function;

[0019] The service catalog statistical overview function includes a daily summary and detail statistics function, an exclusive usage viewing function, and a shared usage viewing function.

[0020] In one implementation, the multi-platform service protocol management system further includes a monthly usage bill management module;

[0021] The monthly bill management module has a bill management function for constructing bill push rules and is used to push the monthly usage bill to the multiple clients or a specified client according to the bill push rules;

[0022] The bill management function includes any one or a combination of an automatic usage import function, a bill approval function, a tenant bill push function, and a report download function.

[0023] In one implementation, the multi-platform service protocol management system has an online debugging mode;

[0024] In the online debugging mode, the multi-platform service protocol management system responds to an SQL statement from a debugger and displays the result set of the SQL to the debugger, where the result set is used to represent the result of the online debugging.

[0025] In one implementation, the multi-platform service protocol management system has an integration testing mode;

[0026] In the integration testing mode, the multi-platform service protocol management system responds to a test plan from a tester and returns the corresponding test results to the tester, where the test plan includes any one or a combination of functional testing, performance testing, and security testing.

[0027] Compared with the prior art, the present application provides an integrated multi-platform service protocol management system. The multi-platform service protocol management system can support the management of multiple third-party protocol management platforms of different types (such as cloud desktops, cloud disks, etc.), realizing unified management and monitoring of data; through the service protocol management module, it can support centralized editing of multiple service directories associated with service protocols, improving the convenience of user operations; through the service volume collection module, it can support flexible setting of data collection rules, and the system can automatically complete the data collection process according to the data collection rules, reducing manual intervention and improving the timeliness and accuracy of data acquisition; through the service volume statistics module, it can support flexible setting of data statistics logic, and the system can automatically complete the statistics and analysis of usage data according to the data statistics logic, and quickly generate monthly usage bills and real-time usage reports, improving the efficiency and reliability of service management.

[0028] It should be understood that the content of the invention is not used to identify the key or essential features of the embodiments of the present disclosure, nor is it used to limit the scope of the present disclosure. Through the following description, other features of the present disclosure will become easily understood. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The accompanying drawings are included to provide a further understanding of the present application, and they are incorporated and constitute a part of this application. The drawings illustrate embodiments of the present application and, together with this specification, serve to explain the principles of the present application. In the drawings:

[0030] Figure 1 is a schematic diagram of an application scenario of a multi-platform service protocol management system 100 provided by an embodiment of the present application;

[0031] Figure 2 is a schematic diagram of a multi-platform service protocol management system 100 provided by an embodiment of the present application;

[0032] Figure 3 is a schematic diagram of another multi-platform service protocol management system 200 provided by an embodiment of the present application;

[0033] Figure 4 is a schematic diagram of yet another multi-platform service protocol management system 300 provided by an embodiment of the present application;

[0034] Figure 5 is a functional structure diagram 400 of a multi-platform service protocol management system 300 provided by way of example. Detailed implementation manners

[0035] Now, the principles of the present disclosure will be described with reference to some embodiments. It should be understood that the description of these embodiments is for illustrative purposes only and helps those skilled in the art understand and implement the present disclosure, without imposing any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in a different manner from that described below.

[0036] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the art to which this disclosure pertains.

[0037] References in the present disclosure to "an embodiment", "embodiment", "exemplary embodiment", etc. indicate that the described embodiment may include a specific feature, structure, or characteristic, but not every embodiment necessarily includes the specific feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an exemplary embodiment, whether or not explicitly described, those skilled in the art will appreciate such feature, structure, or characteristic in connection with other embodiments.

[0038] It should be understood that although terms such as "first" and "second" may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0039] The terms used herein are only for the purpose of describing particular embodiments and are not intended to limit the exemplary embodiments. The singular forms "a", "an", and "the" used herein also include the plural forms unless the context clearly indicates otherwise. As used herein, "a set of elements" or "a collection of elements" is intended to include one or more elements. It should also be understood that the terms "comprises", "comprising", "has", "having", "includes", and / or "including", when used herein, specify the presence of the stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0040] SLA (Service Level Agreement): Service Level Agreement.

[0041] Figure 1 It is a schematic diagram of an application scenario of a multi-platform service protocol management system 100 provided by an embodiment of the present application. As Figure 1 , the multi-platform service protocol management system 100 is connected to a plurality of third-party protocol management platforms 101 and is also connected to a plurality of client terminals 102.

[0042] The third-party protocol management platform 101 is responsible for pulling the usage data on which the service catalog depends from the data source. In some embodiments, the third-party protocol management platform 101 may be a platform of types such as a configuration information management platform, a cloud desktop platform, a cloud disk platform, or a private cloud platform, etc. The data source is the client terminal 102 connected to the multi-platform service protocol management system 100 and is responsible for storing the usage data.

[0043] In some embodiments, the client terminal 102 may be a tenant client terminal of the multi-platform service protocol management system 100.

[0044] In some embodiments, the multi-platform service protocol management system 100 provides an integration interface for various types of third-party protocol management platforms 101 to uniformly access, and is connected to a plurality of third-party protocol management platforms 101 through the integration interface to ensure that data can be smoothly transmitted to the multi-platform service protocol management system 100.

[0045] Figure 2It is a schematic diagram of a multi-platform service agreement management system 100 provided by an embodiment of the present application. As Figure 2 , the multi-platform service agreement management system 100 includes a service agreement management module 10, a service volume collection module 20, and a service volume statistics module 30.

[0046] The service agreement management module 10 has a protocol management function for the service agreements of the third-party protocol management platform 101. The protocol management function includes a protocol editing function for constructing the association relationship between the service agreement and multiple service directories. The service directories are used to represent the cooperation items signed between the multi-platform service agreement management system 100 and the third-party protocol management platform 101. The cooperation items include multiple service level agreement (SLA) indicators required to achieve the business goals.

[0047] In some embodiments, the service agreement management module 10 also has a protocol creation function, a protocol deletion function, a protocol submission function, and a protocol approval function.

[0048] In some embodiments, the protocol editing function includes four categories of first menu functions. The four categories of first menu functions include a service directory addition function, a batch import function, an SLA editing function, and an SLA automatic update function.

[0049] The service volume collection module 20 has a rule configuration function for constructing data collection rules. The service volume collection module 20 is used to collect the usage data relied on by multiple service directories from the third-party protocol management platform according to the data collection rules.

[0050] In some embodiments, the rule configuration function includes any one or combination of a multi-platform management function, an execution cycle configuration function, a collection execution configuration function, an execution log viewing function, and a collected service volume deletion function.

[0051] The service volume statistics module 30 has a logic configuration function for constructing data statistics logic. The service volume statistics module 30 is used to generate a monthly usage bill and a real-time usage report according to the data statistics logic and the usage data.

[0052] In some embodiments, the logic configuration function includes any one or combination of a logic creation function, a logic editing function, a logic statistics execution function, and a logic deletion function;

[0053] The logic editing function includes four categories of third menu functions. The four categories of third menu functions include an exception system filtering function, a branch settlement mode configuration function, an execution plan configuration function, and a custom retrieval condition configuration function.

[0054] The multi-platform service agreement management system 100 supports managing multiple third-party agreement management platforms of different types, achieving unified management and monitoring of data; the service agreement management module 10 supports centrally editing multiple service directories associated with service agreements, improving the convenience of user operations; the service volume collection module 20 supports flexibly setting data collection rules and automatically completing the data collection process according to the data collection rules, reducing manual intervention and improving the timeliness and accuracy of data acquisition; the service volume statistics module 30 supports flexibly setting data statistics logics and automatically completing the statistics and analysis of usage data according to the data statistics logics, quickly generating monthly usage bills and real-time usage reports, improving the efficiency and reliability of service management.

[0055] It should be noted that the service volume collection module 20 can customize the collection period. For example, it can collect the usage data on which multiple service directories in the target service agreement depend from the target third-party agreement management platform every other week. The target third-party agreement management platform can be all the third-party agreement management platforms 101 or a specified third-party agreement management platform 101. The target service agreement can be all the service agreements constructed in the service agreement management module 10 or a specified service agreement among them. The service volume statistics module 30 supports customizing retrieval conditions, facilitating the quick retrieval and screening of data.

[0056] Figure 3 It is a schematic diagram of another multi-platform service agreement management system 200 provided by an embodiment of the present application. The difference between the multi-platform service agreement management system 200 and the multi-platform service agreement management system 100 is that it further includes a service directory management module 40 and an SLA management module 50.

[0057] The service directory management module 40 has a directory management function for service directories. The directory management function includes any one or combination of a service directory creation function, a service directory batch import function, a service directory editing function, a service directory deletion function, a service directory submission function, and a service directory approval function.

[0058] The SLA management module 50 has an SLA management function for SLA metrics. The SLA management function includes any one or combination of an SLA creation function, an SLA batch import function, an SLA deletion function, an SLA submission function, and an SLA approval function.

[0059] In some embodiments, the SLA management function includes an SLA editing function for constructing the association relationship between service directories and SLA metrics. The SLA editing function includes four types of second menu functions, and the four types of second menu functions include a service directory association function, a signing agency editing function, a quantitative metric editing function, and a qualitative metric editing function.

[0060] Compared with the multi-platform service agreement management system 100, in the multi-platform service agreement management system 200, the service catalog management module 40 supports users to view and flexibly edit the service catalog in a timely manner. The SLA management module 50 supports users to view and flexibly edit SLA metrics in a timely manner, and also supports the associated editing, signing agency editing, quantitative metric editing, and qualitative metric editing between SLA metrics and the service catalog, improving the user experience and management effect.

[0061] Figure 4 FIG. 4 is a schematic diagram of another multi-platform service agreement management system 300 provided by an embodiment of the present application. The difference between the multi-platform service agreement management system 300 and the multi-platform service agreement management system 200 is that it further includes a real-time report management module 60 and a monthly usage bill management module 70.

[0062] The real-time report management module 60 has any one or a combination of a service catalog statistics overview function, a historical data archiving function, a data verification function, and a data export function.

[0063] The service catalog statistics overview function includes a daily summary and detail statistics function, an exclusive usage viewing function, and a shared usage viewing function.

[0064] The monthly bill management module 70 has a bill management function for constructing bill push rules. The monthly bill management module 70 is used to push the monthly usage bill to multiple clients 102 or a specified client 102 according to the bill push rules.

[0065] The bill management function includes any one or a combination of an automatic usage import function, a bill approval function, a tenant bill push function, and a report download function.

[0066] Compared with the multi-platform service agreement management system 200, in the multi-platform service agreement management system 300, the real-time report management module 60 supports displaying the summary and details of the real-time usage report, and supports viewing exclusive usage data and shared usage data, improving the efficiency of report processing. The monthly bill management module 70 supports flexible setting of bill push rules, automatically completes the automatic push of the monthly usage bill according to the bill push rules, and supports functions such as automatic usage import, bill approval, tenant bill push, and report download, improving the efficiency of bill management.

[0067] Figure 5 FIG. 400 is a functional structure diagram of a multi-platform service agreement management system 300 provided by way of example. Refer to Figure 5, in the multi-platform service agreement management system 300, the service agreement management module 10 may have a protocol creation function, a protocol editing function, a protocol deletion function, a protocol submission function, and a protocol approval function. The protocol editing function includes a service catalog addition function, a batch import function, an SLA editing function, and an SLA automatic update function; the service volume collection module 20 may have a multi-platform management function, an execution cycle configuration function, a collection execution configuration function, an execution log viewing function, and a collection service volume deletion function; the service volume statistics module 30 may have an exception system filtering function, a branch settlement mode configuration function, an execution plan configuration function, and a custom retrieval condition configuration function; the service catalog management module 40 may have a service catalog creation function, a service catalog batch import function, a service catalog editing function, a service catalog deletion function, a service catalog submission function, and a service catalog approval function; the SLA management module 50 may have an SLA editing function, an SLA creation function, an SLA batch import function, an SLA deletion function, an SLA submission function, and an SLA approval function. The SLA editing function includes a service catalog association function, a signing agency editing function, a quantitative index editing function, and a qualitative index editing function; the real-time report management module 60 may have a service catalog statistics overview function, a historical data archiving function, a data verification function, and a data export function; the monthly bill management module 70 may have a usage automatic import function, a bill approval function, a tenant bill push function, and a report download function.

[0068] Based on the functional structure diagram 400, the multi-platform service agreement management system 300 can automatically collect usage data, complete the statistics and analysis of service usage, quickly generate monthly usage bills and real-time usage reports, and provide visualization of various data, improving the efficiency and automation of service management.

[0069] In one embodiment, the multi-platform service agreement management system 300 has an online debugging mode and an integration testing mode.

[0070] In the online debugging mode, the multi-platform service agreement management system 300 responds to an SQL statement from a debugger and presents the result set of the SQL to the debugger, where the result set is used to represent the result of the online debugging.

[0071] In the integration testing mode, the multi-platform service agreement management system 300 responds to a test plan from a tester and returns the corresponding test results, where the test plan includes any one or a combination of functional testing, performance testing, and security testing.

[0072] Based on the online debugging mode and the integration testing mode, the multi-platform service agreement management system 300 supports users to centrally conduct online debugging and integration testing, ensuring the smoothness of multi-platform access, the accuracy of data processing, and the timeliness of report generation.

[0073] Compared with the prior art, the present application provides an integrated multi-platform service agreement management system. The multi-platform service agreement management system can support the management of multiple third-party agreement management platforms of different types (such as cloud desktops, cloud disks, etc.), realizing unified management and monitoring of data; through the service agreement management module, it can support centralized editing of multiple service directories associated with service agreements, improving the convenience of user operations; through the service volume collection module, it can support flexible setting of data collection rules, and the system can automatically complete the data collection process according to the data collection rules, reducing manual intervention and improving the timeliness and accuracy of data acquisition; through the service volume statistics module, it can support flexible setting of data statistics logic, and the system can automatically complete the statistics and analysis of usage data according to the data statistics logic, and quickly generate monthly usage bills and real-time usage reports, improving the efficiency and reliability of service management.

[0074] The basic concepts have been described above. Obviously, for those skilled in the art, the above invention disclosure is only an example and does not constitute a limitation to the present application. Although not explicitly stated here, those skilled in the art may make various modifications, improvements, and corrections to the present application. Such modifications, improvements, and corrections are proposed in the present application, so such modifications, improvements, and corrections still fall within the spirit and scope of the exemplary embodiments of the present application.

[0075] At the same time, the present application uses specific terms to describe the embodiments of the present application. Such as "one embodiment", "an embodiment", and / or "some embodiments" mean a certain feature, structure, or characteristic related to at least one embodiment of the present application. Therefore, it should be emphasized and noted that the "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more at different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of the present application can be appropriately combined.

[0076] Some aspects of the present application can be executed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above-mentioned hardware or software can all be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". The processor can be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. In addition, aspects of the present application may be embodied as a computer product located in one or more computer-readable media, which includes computer-readable program code. For example, computer-readable media may include, but are not limited to, magnetic storage devices (such as hard disks, floppy disks, magnetic tapes...), optical discs (such as compact discs CD, digital versatile discs DVD...), smart cards, and flash memory devices (such as cards, sticks, key drives...).

[0077] Similarly, it should be noted that, in order to simplify the presentation of the disclosure of the present application and thus help the understanding of one or more embodiments of the invention, in the foregoing description of the embodiments of the present application, sometimes multiple features are grouped into one embodiment, drawing, or description thereof. However, this method of disclosure does not mean that the features required by the subject matter of the present application are more than those mentioned in the claims. In fact, the features of the embodiments are fewer than all the features of the individual embodiments disclosed above.

[0078] In some embodiments, numbers are used to describe components and the quantity of attributes. It should be understood that such numbers used for the description of embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise stated, "about", "approximately" or "substantially" indicate that the stated number allows a variation of ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, and the approximate values can change according to the characteristics required by individual embodiments. In some embodiments, the numerical parameters should consider the specified significant digits and adopt the method of retaining the general number of digits. Although the numerical ranges and parameters used in some embodiments of the present application to confirm the breadth of their scope are approximate values, in specific embodiments, such numerical settings are as precise as possible within the feasible range.

[0079] Although the present application has been described with reference to the current specific embodiments, those of ordinary skill in the art in this technical field should recognize that the above embodiments are only used to illustrate the present application, and various equivalent changes or substitutions can be made without departing from the spirit of the present application. Therefore, as long as the changes and modifications of the above embodiments are within the scope of the spirit of the present application, they will fall within the scope of the claims of the present application.

Claims

1. A multi-platform service protocol management system, characterized in that, The multi-platform service agreement management system is connected to multiple third-party agreement management platforms and multiple clients. The multi-platform service agreement management system includes a service agreement management module, a service volume collection module, and a service volume statistics module; The service agreement management module has a protocol management function for the service agreements of the third-party agreement management platforms. The protocol management function includes a protocol editing function for constructing the association relationship between the service agreements and multiple service catalogs, where the service catalogs are used to represent the cooperation items signed between the multi-platform service agreement management system and the third-party agreement management platforms. The cooperation items include multiple service level agreement (SLA) indicators required to achieve business objectives; The service volume collection module has a rule configuration function for constructing data collection rules, and is used to collect the usage data on which the multiple service catalogs depend from the third-party agreement management platforms according to the data collection rules; The service volume statistics module has a logic configuration function for constructing data statistics logics, and is used to generate monthly usage bills and real-time usage reports according to the data statistics logics and the usage data.

2. The multi-platform service agreement management system according to claim 1, wherein, The protocol editing function includes four types of first menu functions, and the four types of first menu functions include a service catalog addition function, a batch import function, an SLA editing function, and an SLA automatic update function.

3. The multi-platform service agreement management system according to claim 2, characterized in that, The multi-platform service agreement management system further includes a service catalog management module and an SLA management module; The service catalog management module has a catalog management function for the service catalogs. The catalog management function includes any one or combination of a service catalog creation function, a service catalog batch import function, a service catalog editing function, a service catalog deletion function, a service catalog submission function, and a service catalog approval function; The SLA management module has an SLA management function for the SLA indicators. The SLA management function includes any one or combination of an SLA creation function, an SLA batch import function, an SLA deletion function, an SLA submission function, and an SLA approval function.

4. The multi-platform service agreement management system according to claim 3, wherein The SLA management function includes an SLA editing function for constructing the association relationship between the service catalogs and the SLA indicators. The SLA editing function includes four types of second menu functions, and the four types of second menu functions include a service catalog association function, a signing agency editing function, a quantitative indicator editing function, and a qualitative indicator editing function.

5. The multi-platform service agreement management system according to any one of claims 1-3, characterized in that, The rule configuration function includes any one or combination of a multi-platform management function, an execution cycle configuration function, a collection execution configuration function, an execution log viewing function, and a collection service volume deletion function; 6. The multi-platform service agreement management system according to any one of claims 1 to 3, characterized in that The logic configuration function includes any one or combination of a logic creation function, a logic editing function, a logic statistics execution function, and a logic deletion function; The logic editing function includes four types of third menu functions, and the four types of third menu functions include an exception system filtering function, a branch settlement mode configuration function, an execution plan configuration function, and a custom retrieval condition configuration function.

7. The multi-platform service agreement management system according to any one of claims 1 to 3, characterized in that The multi-platform service agreement management system further includes a real-time report management module; The real-time report management module has any one or combination of the service catalog statistics overview function, historical data archiving function, data verification function, and data export function; The service catalog statistics overview function includes the daily summary and detailed statistics function, exclusive usage view function, and shared usage view function.

8. The multi-platform service agreement management system according to any one of claims 1-3, characterized in that, The multi-platform service agreement management system further includes a monthly usage bill management module; The monthly bill management module has a bill management function for constructing bill push rules, and is used to push the monthly usage bill to the multiple clients or specified clients according to the bill push rules; The bill management function includes any one or combination of the usage automatic import function, bill approval function, tenant bill push function, and report download function.

9. The multi-platform service agreement management system according to any one of claims 1 to 3, characterized in that The multi-platform service agreement management system has an online debugging mode; In the online debugging mode, the multi-platform service agreement management system responds to an SQL statement from a debugger and displays the result set of the SQL to the debugger, where the result set is used to represent the result of the online debugging.

10. The multi-platform service agreement management system according to any one of claims 1-3, characterized in that, The multi-platform service agreement management system has an integrated test mode; In the integrated test mode, the multi-platform service agreement management system responds to a test plan from a tester and returns the corresponding test results to the tester, where the test plan includes any one or combination of functional testing, performance testing, and security testing.

Images