An automated testing system and method for railway broadband trunking communication system

Abstract

This invention discloses an automated testing system and method for a railway broadband trunked communication system. These solutions provide a test case description file design, detailing the test case design principles and methods. They also provide a test task distribution and control scheme, explaining the test system's operational logic, enabling control of single, multiple, and concurrent test scenarios, and implementing test statistics and analysis of functions, interfaces, and performance. Furthermore, they provide an MCX interface protocol library design, offering unified MCX-1 and MCX-3 interface library support, enabling efficient upper-layer call-based testing. Based on these solutions, automated testing and analysis of key service functions, interfaces, and performance can be achieved, improving test efficiency. Furthermore, test metrics can be quantified, making function, interface, and performance testing more complete and accurate.

Description

Technical Field

[0001] The present invention relates to the technical field of railway wireless communication, and in particular to an automated testing system and method for a railway broadband trunking communication system. Background Art

[0002] Railway broadband trunking communication is a key service within 5G-R and a crucial component of future 5G-R (5G-Railway, a dedicated 5G mobile communication system for railways). Currently, testing of 5G-R broadband trunking communication systems primarily relies on manual testing methods. Research on automated testing is limited, and no specific implementation solutions have been publicly released. Traditional manual testing methods not only require the coordination of numerous systems and devices but also require a large number of testers to analyze test issues and results. This leads to low test efficiency, high testing costs, and complex test scenarios.

[0003] The Chinese invention patent "Delay Testing System and Method for MCPTT Services," with authorization announcement number CN112737870B, discloses a system and method for testing MCPTT service trials. This patent focuses primarily on delay testing of MCPTT voice services (critical voice services) and does not cover other functions, interfaces, or performance testing of the MCX system (railway broadband trunking communication system). A 2020 paper by Liu Huabin of Beijing Jiaotong University, titled "Research and Implementation of an MCPTT Automated Testing System," introduced an MCPTT automated testing system that implements MCPTT login, individual call, group call, and voice access testing. However, it does not implement other functions, interfaces, or performance testing, and can only simulate terminal roles to test terminal-to-server functionality. Furthermore, the design architecture requires a large number of terminal simulators, and the statistical performance indicators of the test results obtained are limited.

[0004] Therefore, it is necessary to develop a test solution that can realize the functions, interfaces and performance of the MCX system.

[0005] In view of this, the present invention is proposed. Summary of the Invention

[0006] The purpose of the present invention is to provide an automated testing system and method for a railway broadband trunking communication system, which can realize automated testing and analysis of main business functions, interfaces and performance, improve test efficiency, and quantify test indicators, making function, interface and performance testing more complete and accurate.

[0007] The purpose of the present invention is achieved through the following technical solutions:

[0008] An automated testing system for a railway broadband trunking communication system includes: a test system application unit, a test case description file storage unit, and an MCX interface protocol library; wherein:

[0009] The test case description file storage unit is used to store pre-configured test case description files;

[0010] The MCX interface protocol library is used to store MCX interface protocols for interacting with the MCX system to be tested for various types of services, where the MCX system is a railway broadband trunking communication system;

[0011] The test system application unit is configured to parse the test content and configuration data from the test case description file, form test control logic based on the service type in the test content and the parameters in the configuration data, invoke the corresponding MCX interface protocol in the MCX interface protocol library, initiate corresponding functional tests and / or interface tests on the MCX system under test, compile statistics on the test results based on the configuration data, analyze the test results to obtain performance indicator results of the MCX system under test, and, if the performance indicator results do not meet expected requirements, compile statistics on the test results and analyze the cause of the service failure.

[0012] An automated testing method for a railway broadband trunking communication system is implemented based on the aforementioned automated testing system, the method comprising:

[0013] Pre-configured test case description files and MCX interface protocols for various service types of interaction with the MCX system under test, which is a railway broadband trunking communication system;

[0014] Parse the test content and configuration data from the test case description file, form the test control logic based on the service type in the test content and the parameters in the configuration data, call the corresponding MCX interface protocol in the MCX interface protocol library, initiate the corresponding functional test and / or interface test to the MCX system under test, and combine the configuration data to compile statistics on the test results. Then, analyze the test results to obtain the performance index results of the MCX system under test. When the performance index results do not meet the expected requirements, compile statistics on the test results and analyze the reasons for the service failure.

[0015] It can be seen from the technical solution provided by the present invention that an automated testing solution is provided for the railway broadband cluster communication system. On the one hand, it can improve the testing efficiency; on the other hand, it can simultaneously realize tasks such as function, interface, performance testing, statistical analysis, etc., providing important support and guarantee for the research and development, application and maintenance related to 5G-R broadband cluster communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0017] Figure 1 A schematic diagram of an automated testing system for a railway broadband trunking communication system provided by an embodiment of the present invention;

[0018] Figure 2 A schematic diagram of the system architecture provided by an embodiment of the present invention;

[0019] Figure 3 A schematic diagram of the test case description file structure provided by an embodiment of the present invention;

[0020] Figure 4 A schematic diagram of the test task distribution and control process provided by an embodiment of the present invention;

[0021] Figure 5 A schematic diagram of the MCX interface protocol library provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0022] The following is a clear and complete description of the technical solutions in the embodiments of the present invention, in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0023] First, the following terms may be used in this article:

[0024] The term “and / or” means that either or both of them can be realized at the same time. For example, X and / or Y includes both “X” or “Y” and “X and Y”.

[0025] The terms "include," "comprises," "contains," "has," or other similar expressions should be interpreted as non-exclusive. For example, "including certain technical features (such as raw materials, components, ingredients, carriers, dosage forms, materials, dimensions, parts, components, mechanisms, devices, steps, procedures, methods, reaction conditions, processing conditions, parameters, algorithms, signals, data, products, or manufactured articles)" should be interpreted as including not only the technical features explicitly listed, but also other technical features known in the art that are not explicitly listed.

[0026] The term "consisting of" excludes any technical features not explicitly listed. If used in a claim, this term renders the claim closed, excluding any technical features other than those explicitly listed, except for conventional impurities associated with them. If this term appears only in a clause of a claim, it limits only the elements explicitly listed in that clause; elements listed in other clauses are not excluded from the claim as a whole.

[0027] The following describes in detail an automated testing system and method for a railway broadband trunked communication system provided by the present invention. Any information not described in detail in the embodiments of the present invention is prior art known to professionals in the field. Where specific conditions are not specified in the embodiments of the present invention, the test was conducted in accordance with conventional conditions in the field or the conditions recommended by the manufacturer. Reagents or instruments used in the embodiments of the present invention, where the manufacturer is not specified, are all commercially available conventional products.

[0028] Example 1

[0029] The embodiment of the present invention provides an automated testing system for a railway broadband trunking communication system. Figure 1 As shown, it mainly includes: test system application unit, test case description file storage unit, and MCX interface protocol library.

[0030] (1) The test case description file storage unit is used to store pre-configured test case description files.

[0031] Preferably, the test case description file includes: test case name, case type, service type, user information parameter set, test number and time parameters, and concurrent test parameter set; when concurrent testing is not performed, the concurrent test parameter set is an empty set.

[0032] Preferably, a test case description file template may be pre-set, and the configuration of the test case description file may be completed by modifying the content in the template to improve the test configuration efficiency.

[0033] (2) The MCX interface protocol library is used to store MCX interface protocols for interacting with the MCX system to be tested for various types of services. The MCX system is a railway broadband trunking communication system.

[0034] Preferably, the MCX interface protocol library includes: an interface call module, a registration or deregistration module, a function number operation module, a location operation module, a call module, a voice control module, a video transmission control module, a data module, a context maintenance module, and an underlying protocol library module;

[0035] Among them, the registration or deregistration module, function number operation module, location operation module, call module, voice control module, video transmission control module and data module are MCX interface protocol modules used to interact with the MCX system under test for corresponding service types;

[0036] The interface calling module is used to call back the corresponding MCX interface protocol module to the test system application unit according to the corresponding service type;

[0037] The context maintenance module is used to maintain the data called between the MCX interface protocol library and the test system application unit;

[0038] The underlying protocol library module is the underlying protocol stack such as SIP, HTTP, UDP, TCP, etc., which is used to support the effective transmission of data and the interaction between different business types.

[0039] (3) The test system application unit is used to parse the test content and configuration data from the test case description file, form the test control logic according to the service type (identifying the type of initiated service) in the test content and the parameters in the configuration data, call the corresponding MCX interface protocol in the MCX interface protocol library, initiate the corresponding functional test and / or interface test to the MCX system to be tested, and calculate the test results in combination with the configuration data, and then analyze the test results to obtain the performance index results of the MCX system to be tested; and when the performance index results do not meet the expected requirements, calculate the test results and analyze the reasons for the service failure.

[0040] Preferably, the test system application unit includes: a test control module, a user interface module, a database module, and a test result statistics and failure cause analysis module;

[0041] The user interface module is used to pre-configure test case description files in a human-computer interaction manner, select test case description files in a human-computer interaction manner, and provide them to the test control module; it is also used to display the test results, performance indicator results and failure reasons obtained by the test result statistics and failure cause analysis module;

[0042] The test control module is configured to parse the test content and configuration data from the test case description file selected by the user interface module, formulate test control logic based on the service type in the test content and the parameters in the configuration data, invoke the corresponding MCX interface protocol in the MCX interface protocol library, and initiate corresponding functional tests and / or interface tests on the MCX system under test;

[0043] The test result statistics and failure cause analysis module is used to combine the configuration data with the test results, and then analyze the test results to obtain the performance index results of the MCX system under test. When the performance index results do not meet the requirements, the test results are statistically analyzed and the reasons for the service failure are analyzed. In the test failure cause analysis, a comprehensive analysis is performed through protocol content comparison, signaling process analysis, signaling return value, and service logs to summarize and classify the reasons for the service failure.

[0044] The database module is used to store data obtained during the test process (ie, test results, performance indicator results, failure reasons, etc. obtained by the test result statistics and failure reason analysis module).

[0045] Preferably, the statistical test results in combination with the configuration data include:

[0046] (3.1) If it is a single business test, after the test is completed, the results of the single business test will be counted.

[0047] (3.2) If the service test is repeated multiple times, the service test will be initiated according to the specified interval in the configuration data. After the multiple tests are completed, the test results of each time will be counted separately and summarized.

[0048] (3.3) If it is a concurrent business test, then according to the configuration data, the concurrent business is carried out through multi-threading and high-speed input and output means; after the concurrent test is completed, the test results of each time are counted separately and summarized.

[0049] In an embodiment of the present invention, the testing of main business functions can be implemented, and the functional test types include: terminal registration and deregistration test, function number operation test, voice service test, video service test, data service test and railway specific service test; among them, railway specific service test includes: function addressing, location-based addressing and railway emergency call test.

[0050] At the same time, interface testing can also be achieved, including: MCX-1 interface and MCX-3 interface testing; among them, the MCX-1 interface is the interface between the terminal and the MCX system to be tested, and the MCX-3 interface is the interface between the MCX system to be tested and other MCX systems.

[0051] Based on the above function and interface test results, the performance test of the railway broadband trunking communication system can be achieved through data analysis and quantification of test indicators.

[0052] In order to more clearly demonstrate the technical solution and technical effects provided by the present invention, the system provided by the embodiment of the present invention is described in detail below with reference to specific embodiments.

[0053] 1. Overall overview of the plan.

[0054] The solution provided by the embodiments of the present invention can implement automated testing of railway broadband trunking communication functions and interfaces, enable performance testing of the railway broadband trunking communication system, provide a user-friendly test interface, analysis, and display capabilities, and support railway dedicated call service testing and service failure cause analysis. Detailed descriptions are as follows.

[0055] (1) Realize the automated testing of functions and interfaces of railway broadband trunking communications.

[0056] Railway broadband trunking communication services have numerous functions and involve complex interface protocols. Manual testing is inefficient and requires a lot of testing and analysis. The solution provided by the present invention can realize automated testing of the main functions and interface protocols of railway broadband trunking communication MCX.

[0057] (2) Implement performance testing of railway broadband cluster communication system.

[0058] Existing tests primarily focus on functions and interfaces, lacking performance testing, especially when testing high-volume services such as concurrent processing capabilities. The solution provided by the present invention can test the system's concurrent processing performance and quantitatively evaluate system performance. Furthermore, when conducting high-volume testing, there's no need to configure a large number of physical or simulated terminals; the test system itself has a large number of terminal simulation capabilities.

[0059] (3) Provide friendly test interface, analysis and display.

[0060] In the solution provided by the present invention, the UI interface configured by the test system application unit has a friendly display interface, which can provide users with functions such as filled-in test case configuration, startup, result analysis, and display, further improving the convenience of system testing and the comprehensiveness of test result analysis.

[0061] (4) Support railway dedicated call service testing and service failure cause analysis functions.

[0062] The solution provided by this invention is primarily targeted at railway MCX trunking communications services, supporting railway-specific services such as function number operation, function addressing, location addressing, area-based group calling, and emergency calling testing. Furthermore, it provides detailed cause analysis and display capabilities for service failure scenarios.

[0063] 2. Overall system architecture.

[0064] 1. System architecture.

[0065] like Figure 2FIG. 1 shows the overall architecture of the system (automated test system) of the present invention, which mainly includes: a test case description file storage unit, a test system application unit, and an MCX interface protocol library.

[0066] The test system application unit mainly includes a test control module, a user interface (UI) module, a database module, a test result statistics and failure cause analysis module, etc., which are used for controlling and analyzing test business, displaying test data (mainly data obtained by the test result statistics and failure cause analysis module), storing test data, test result statistics and failure cause analysis, etc.

[0067] The test case description file provides specific test case input for the test system, describing settings such as test content and parameter configuration.

[0068] The MCX interface protocol library unit implements MCX interface related protocols for use by the test system application unit.

[0069] 2. Automated testing content.

[0070] The system provided by the embodiment of the present invention can realize automated testing and analysis of major business functions, interfaces and performance, improve testing efficiency, and can quantify test indicators, making function, interface and performance testing more complete and accurate.

[0071] (1) Business function testing.

[0072] (1.2) Terminal registration and logout test.

[0073] (1.3) Function number operation test.

[0074] (1.4) Voice service testing, including individual voice calls, group calls, and voice control testing.

[0075] (1.5) Video service testing, including: video individual call, pull-up, push, group call, video transmission control testing, etc.

[0076] (1.6) Data service testing, including point-to-point and point-to-multipoint transmission testing of short data and file distribution.

[0077] (1.7) Railway-specific service tests, including functional addressing, location-based addressing, and railway emergency call testing. Location-based addressing is implemented by the location operation module and the call module; functional addressing is implemented by the function number operation module and the call module; and railway emergency calls are implemented by the call module.

[0078] (2) Interface testing.

[0079] Implement the test of the MCX-1 interface between the terminal and the MCX system, and the test of the MCX-3 interface between the MCX system and the MCX system.

[0080] (3) Performance testing.

[0081] Performance testing is achieved through statistics and analysis of test results. Performance test indicators include: business success rate, latency, number of concurrent users / businesses, etc.

[0082] 3. Detailed introduction of each part of the system.

[0083] 1. Test case description file storage unit.

[0084] The test case description file is used as the input of the test task, and is mainly used to describe the content, data, and parameters of the specific test task. According to the characteristics of railway broadband trunking communication services, as well as the principles of versatility, readability, and flexible modification of various services, the structure of the test case description file is constructed, such as Figure 3 As shown, it mainly includes test case name, case type, business type, user information parameter set, test number and time parameters, concurrent test parameter set, etc.; among them, the test case name, case type and business type belong to the test content, and the user information parameter set, test number and time parameters and concurrent test parameter set belong to the configuration data.

[0085] In actual use, various test case description file templates are provided in advance, allowing testers to modify specific parameters as needed to improve test configuration efficiency. In addition, the test case description file structure is universal, facilitating reuse for different business functions, interfaces, and performance tests.

[0086] 2. Test system application unit.

[0087] After selecting the corresponding test case file and confirming to start the test, the test business control unit will distribute and control the test tasks according to the content of the test case file.

[0088] like Figure 4 As shown in the figure, the main process of test task distribution and control includes:

[0089] (1) Parse the test case description file to obtain test content and configuration data.

[0090] (2) The test service control unit calls the MCX interface protocol library module according to the service type in the test content and the parameters in the configuration data to initiate the corresponding test.

[0091] (3) For a single business test, after the control unit completes the test, it will collect statistics on the business test indicator results.

[0092] (4) For cyclic multiple service tests, the control unit initiates service tests at specified intervals based on the configuration data; after completing multiple tests, the test results of each test are counted and summarized, for example, to form an average value and indicator results under 95% and 99% conditions.

[0093] (5) For concurrent business testing, the control unit performs concurrent business according to the concurrent configuration data through multi-threading and high-speed IO. After the concurrent test is completed, the test results of each time are counted and summarized. For example, the summary statistics form the indicator results under the concurrent number.

[0094] (6) Test statistics analysis and data storage. The system supports testing in single, multiple-cycle, and concurrent modes. The main statistical performance indicators include business success rate, business latency, and concurrency volume.

[0095] After completing the test using the above methods, the service execution status is determined. If the performance indicator results do not meet the expected requirements, the service is considered to have failed. At this time, the test results are statistically analyzed and the reasons for the service failure are analyzed. This includes: comparing protocol content, analyzing signaling processes, signaling return values, and conducting a comprehensive analysis of service logs. The reasons for the service failure are summarized and categorized and displayed. Specific instructions are as follows.

[0096] The protocol content comparison mainly performs detailed verification of the mandatory fields in the MCX protocol. If the verification fails, the exception is marked and the specific failure content of the protocol is reported.

[0097] Signaling process analysis: MCX's main business functions are completed through multiple signaling interactions. The signaling process points that are interrupted when the business fails are identified for comprehensive analysis.

[0098] The signaling return value and service failure reason refer to the return value of the MCX service signaling response. If the response message carries a specific service failure reason, the corresponding service failure reason is identified.

[0099] The business log mainly contains all the data content and processes of the interaction between the test system and the MCX system, as well as the operation log of the test system, which is used for more in-depth problem troubleshooting.

[0100] 3. MCX interface protocol library.

[0101] like Figure 5As shown, the MCX interface protocol library primarily includes modules for interface invocation, registration / deregistration, function number manipulation, location manipulation, calling, voice control, video transmission control, data, context maintenance, and the underlying protocol library. It implements the MCX interface protocols for railway broadband trunking services, supporting both the MCX-1 and MCX-3 interfaces for invocation by the upper layers of the test system. The MCX interface protocol library provides an efficient invocation and callback interface with the upper layers of the test system, enabling implementation of corresponding interface protocols and communication functions based on upper-layer instructions.

[0102] The above-mentioned system provided by the embodiment of the present invention can realize the automated testing of the functions, interfaces and performance of the MCX system; in the above-mentioned system: (1) a test case description file design is provided, which describes in detail the design principles and methods of the test case; (2) a test task distribution and control scheme is provided, which explains the operating logic of the test system, and can realize the test control of single, multiple, concurrent and other scenarios, and realize the test statistics and analysis of functions, interfaces and performance; (3) an MCX interface protocol library design is provided, which provides unified MCX-1 and MCX-3 class interface library support, which can be efficiently called by the upper layer to realize testing. The above-mentioned scheme of the present invention can realize the automated testing and analysis of major business functions, interfaces and performance, improve the testing efficiency, and can quantify the test indicators, making the function, interface and performance testing more complete and accurate.

[0103] Those skilled in the art will clearly understand that for the convenience and brevity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the system can be divided into different functional modules to complete all or part of the functions described above.

[0104] Example 2

[0105] An embodiment of the present invention further provides an automated testing method for a railway broadband trunking communication system. The method is mainly implemented based on the automated testing system provided in the aforementioned embodiment. The method includes:

[0106] Pre-configured test case description files and MCX interface protocols for various service types of interaction with the MCX system under test, which is a railway broadband trunking communication system;

[0107] Parse the test content and configuration data from the test case description file, form the test control logic based on the service type in the test content and the parameters in the configuration data, call the corresponding MCX interface protocol in the MCX interface protocol library, initiate the corresponding functional test and / or interface test to the MCX system under test, and combine the configuration data to compile statistics on the test results. Then, analyze the test results to obtain the performance index results of the MCX system under test. When the performance index results do not meet the expected requirements, compile statistics on the test results and analyze the reasons for the service failure.

[0108] Considering that the above embodiments have already described the various parts of the system in detail, they will not be described in detail here.

[0109] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by any person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims. The information disclosed in the background technology section of this article is only intended to deepen the understanding of the overall background technology of the present invention, and should not be regarded as an admission or any form of implication that the information constitutes prior art already known to those skilled in the art.

Claims

1. An automated testing system for a railway broadband trunking communication system, characterized in that: include: Test system application unit, test case description file storage unit and MCX interface protocol library; including: The test case description file storage unit is used to store pre-configured test case description files; The MCX interface protocol library is used to store MCX interface protocols for interacting with the MCX system to be tested for various types of services, where the MCX system is a railway broadband trunking communication system; The test system application unit is configured to parse test content and configuration data from a test case description file, wherein the test content includes: test case name, case type, and service type; the configuration data includes: user information parameter set, test number and time parameters, and concurrent test parameter set; form test control logic based on the service type in the test content and the parameters in the configuration data, call the corresponding MCX interface protocol in the MCX interface protocol library, initiate corresponding functional tests and / or interface tests on the MCX system under test, and calculate test results based on the configuration data, and then analyze the test results to obtain the performance of the MCX system under test. Indicator results, and when the performance indicator results do not meet the expected requirements, the test results are statistically analyzed and the reasons for the service failure are analyzed, including: comprehensive analysis through protocol content comparison, signaling process analysis, signaling return value, and service log, summarizing and classifying the reasons for the service failure and presenting them; protocol content comparison is to verify the mandatory fields in the MCX protocol; signaling process analysis is to identify the signaling process point where the service fails and use it for comprehensive analysis; signaling return value refers to the return value of the MCX service signaling response; service log is all the data content and process of the interaction between the test system and the MCX system to be tested, as well as the operation log of the test system.

2. The automated testing system for a railway broadband trunking communication system according to claim 1, characterized in that: The test case description file includes: test case name, case type, business type, user information parameter set, test number and time parameters, and concurrent test parameter set; among them, the test case name, case type and business type belong to the test content, and the user information parameter set, test number and time parameters, and concurrent test parameter set belong to the configuration data.

3. The automated testing system for a railway broadband trunking communication system according to claim 1 or 2, characterized in that: Also includes: Pre-set the test case description file template and complete the configuration of the test case description file by modifying the content in the template.

4. The automated testing system for a railway broadband trunking communication system according to claim 1, characterized in that: The MCX interface protocol library includes: an interface call module, a registration or deregistration module, a function number operation module, a location operation module, a call module, a voice control module, a video transmission control module, a data module, a context maintenance module, and an underlying protocol library module; Among them, the registration or deregistration module, function number operation module, location operation module, call module, voice control module, video transmission control module and data module are MCX interface protocol modules used to interact with the MCX system under test for corresponding service types; The interface calling module is used to call back the corresponding MCX interface protocol module to the test system application unit according to the corresponding service type; The context maintenance module is used to maintain the data called between the MCX interface protocol library and the test system application unit; The underlying protocol library module is the underlying protocol stack, which is used to support data transmission and interaction of different business types.

5. The automated testing system for a railway broadband trunking communication system according to claim 1, characterized in that: The test system application unit includes: a test control module, a user interface module, a database module, and a test result statistics and failure cause analysis module; The user interface module is used to pre-configure test case description files in a human-computer interaction manner, select test case description files in a human-computer interaction manner, and provide them to the test control module; it is also used to display the test results, performance indicator results and failure reasons obtained by the test result statistics and failure cause analysis module; The test control module is configured to parse the test content and configuration data from the test case description file selected by the user interface module, formulate test control logic based on the service type in the test content and the parameters in the configuration data, invoke the corresponding MCX interface protocol in the MCX interface protocol library, and initiate corresponding functional tests and / or interface tests on the MCX system under test; The test result statistics and failure cause analysis module is used to combine the configuration data with the test results, and then analyze the test results to obtain the performance index results of the MCX system under test. When the performance index results do not meet the requirements, the test results are statistically analyzed and the reasons for the service failure are analyzed. In the test failure cause analysis, a comprehensive analysis is performed through protocol content comparison, signaling process analysis, signaling return value, and service logs to summarize and classify the reasons for the service failure. The database module is used to store the test results, performance indicator results and failure reasons obtained by the test result statistics and failure reason analysis module.

6. The automated testing system for a railway broadband trunking communication system according to claim 1 or 5, characterized in that: The statistical test results of the combined configuration data include: If it is a single service test, after the test is completed, the results of the single service test are counted.

7. The automated testing system for a railway broadband trunking communication system according to claim 1 or 5, characterized in that: The statistical test results of the combined configuration data include: If the service test is repeated multiple times, the service test is initiated according to the specified interval in the configuration data. After the multiple tests are completed, the test results of each time are counted separately and summarized.

8. The automated testing system for a railway broadband trunking communication system according to claim 1 or 5, characterized in that: The statistical test results of the combined configuration data include: If it is a concurrent business test, the concurrent business will be carried out according to the configuration data through multi-threading and high-speed input and output means; after the concurrent test is completed, the test results of each time will be counted separately and summarized.

9. The automated testing system for a railway broadband trunking communication system according to claim 1, characterized in that: Functional test types include: terminal registration and deregistration test, function number operation test, voice service test, video service test, data service test and railway-specific service test; among them, railway-specific service test includes: function addressing, location-based addressing and railway emergency call test; Interface testing includes: MCX-1 interface and MCX-3 interface testing; among them, MCX-1 interface is the interface between the terminal and the MCX system to be tested, and MCX-3 interface is the interface between the MCX system to be tested and other MCX systems.

10. An automated testing method for a railway broadband trunking communication system, characterized in that: Implementation based on the automated testing system according to any one of claims 1 to 9, the method comprises: Pre-configured test case description files and MCX interface protocols for various service types of interaction with the MCX system under test, which is a railway broadband trunking communication system; Parse the test content and configuration data from the test case description file, form the test control logic based on the service type in the test content and the parameters in the configuration data, call the corresponding MCX interface protocol in the MCX interface protocol library, initiate the corresponding functional test and / or interface test to the MCX system under test, and combine the configuration data to compile statistics on the test results. Then, analyze the test results to obtain the performance index results of the MCX system under test. When the performance index results do not meet the expected requirements, compile statistics on the test results and analyze the reasons for the service failure.

Images