Automatic test system and method for railway broadband trunking communication system

Abstract

The invention discloses an automatic test system and method for a railway broadband trunking communication system, which are corresponding schemes, and in the related schemes, test case description file design is provided, and the design principle and method of a test case are described in detail; a test task distribution and control scheme is provided, the operation logic of a test system is explained, test control of single, multiple and concurrent scenes can be realized, and test statistics and analysis of functions, interfaces and performance are realized; mCX interface protocol library design is provided, unified MCX-1 and MCX-3 type interface library support is provided, and the method can be efficiently called by an upper layer to achieve testing. Based on the scheme, automatic testing and analysis of main service functions, interfaces, performance and the like can be achieved, the testing efficiency is improved, testing indexes can be quantified, and the functions, the interfaces and the performance testing are 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 automatic testing system and method for a railway broadband trunking communication system. Background Art

[0002] Railway broadband trunking communication is the most distinctive key service in 5G-R and an important part of future 5G-R (5G-Railway, railway 5G dedicated mobile communication system) applications. At present, most of the tests on 5G-R broadband trunking communication systems use manual testing methods. There are few studies on related automated testing and no specific implementation plans are publicly available. Traditional manual testing methods not only require the cooperation of many systems and equipment, but also require a large number of testers to participate and analyze test problems and results. There are problems such as low test efficiency, high test overhead, and complex test scenarios.

[0003] The Chinese invention patent "Time Delay Test System and Method for MCPTT Service" with the authorization announcement number CN112737870B discloses a MCPTT service trial test system and method, which mainly focuses on the time delay test of MCPTT voice service (critical voice service), and does not involve other functions, interfaces and performance tests of the MCX system (railway broadband trunking communication system). The paper "Research and Implementation of MCPTT Automated Test System" published by Liu Huabin of Beijing Jiaotong University in 2020 introduced an MCPTT automated test system, which realized the login, individual call, group call, voice right and other tests of MCPTT; however, it did not realize other functions, interfaces and performance tests, and could only simulate the terminal role to test the functions between the terminal and the server; in addition, a large number of terminal simulators are required to implement the design architecture, and the 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 objective of the present invention is achieved through the following technical solutions: An automated test system for a railway broadband trunking communication system comprises: a test system application unit, a test case description file storage unit and an MCX interface protocol library; wherein: The test case description file storage unit is used to store a pre-configured test case description file; 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 used to parse the test content and configuration data from the test case description file, form a test control logic according to 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 to the MCX system to be tested, and calculate test results in combination with the configuration data, and then analyze the test results to obtain performance indicator results of the MCX system to be tested, and when the performance indicator results do not meet the expected requirements, calculate the test results and analyze the reasons for the service failure.

[0008] An automated testing method for a railway broadband trunking communication system is implemented based on the aforementioned automated testing system, and the method comprises: Pre-configure test case description files and 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. Parse the test content and configuration data from the test case description file, form the test control logic according to 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 to be tested, and combine the configuration data to count the test results, 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, count the test results and analyze the reasons for the service failure.

[0009] 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 test efficiency; on the other hand, it can simultaneously realize tasks such as function, interface, performance testing, statistical analysis, etc., and provide important support and guarantee for the research and development, application and maintenance of 5G-R broadband cluster communication. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0011] Figure 1A schematic diagram of an automated testing system for a railway broadband trunking communication system provided by an embodiment of the present invention; Figure 2 A schematic diagram of a system architecture provided by an embodiment of the present invention; Figure 3 A schematic diagram of the test case description file structure provided by an embodiment of the present invention; Figure 4 A schematic diagram of the test task distribution and control process provided by an embodiment of the present invention; Figure 5 A schematic diagram of the MCX interface protocol library provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0012] The following is a clear and complete description of the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the protection scope of the present invention.

[0013] First, the terms that may be used in this article are explained as follows: The term “and / or” means that either or both of them can be realized at the same time. For example, X and / or Y means both “X” or “Y” and “X and Y”.

[0014] The terms "include", "comprises", "contains", "has" or other descriptions with similar semantics should be interpreted as non-exclusive inclusion. For example, including certain technical feature elements (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 products, etc.) should be interpreted as including not only certain technical feature elements explicitly listed, but also other technical feature elements known in the art that are not explicitly listed.

[0015] The term "consisting of..." means excluding any technical feature elements not explicitly listed. If this term is used in a claim, it will make the claim closed, so that it does not contain technical feature elements other than the technical feature elements explicitly listed, except for the conventional impurities related to them. If this term only appears in a clause of a claim, it only limits the elements explicitly listed in the clause, and the elements recorded in other clauses are not excluded from the overall claim.

[0016] The following is a detailed description of an automated test system and method for a railway broadband trunking communication system provided by the present invention. The contents not described in detail in the embodiments of the present invention belong to the prior art known to professional and technical personnel in the field. If no specific conditions are specified in the embodiments of the present invention, the conventional conditions in the field or the conditions recommended by the manufacturer are followed. If the manufacturer of the reagents or instruments used in the embodiments of the present invention is not specified, they are all conventional products that can be purchased commercially.

[0017] Embodiment 1 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: a test system application unit, a test case description file storage unit, and an MCX interface protocol library.

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

[0019] 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.

[0020] 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.

[0021] (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, where the MCX system is a railway broadband trunking communication system.

[0022] Preferably, the MCX interface protocol library includes: an interface calling module, a registration or deregistration module, a function number operation module, a location operation module, a call module, a speech right 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, the function number operation module, the location operation module, the call module, the voice control module, the video transmission control module and the data module are MCX interface protocol modules for interacting with the MCX system to be tested for the corresponding service type; 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 for data maintenance between the MCX interface protocol library and the test system application unit; 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.

[0023] (3) The test system application unit is used to parse the test content and configuration data from the test case description file, form a 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 indicator results of the MCX system to be tested; and when the performance indicator results do not meet the expected requirements, calculate the test results and analyze the reasons for the service failure.

[0024] 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; The user interface module is used to pre-configure the test case description file in a human-computer interaction manner, and to select the test case description file in a human-computer interaction manner and provide it to the test control module; it is also used to display the test results, performance index results and failure reasons obtained by the test result statistics and failure reason analysis module; The test control module is used to parse the test content and configuration data from the test case description file selected by the user interface module, form a test control logic according to 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, and initiate the corresponding function test and / or interface test to the MCX system to be tested; The test result statistics and failure cause analysis module is used to combine the configuration data to count the test results, and then analyze the test results to obtain the performance index results of the MCX system to be tested; when the performance index results do not meet the requirements, the test results are counted and the reasons for the service failure are analyzed; when analyzing the reasons for the test failure, a comprehensive analysis is performed through protocol content comparison, signaling process analysis, signaling return value, and service log, and the reasons for the service failure are summarized and classified; The database module is used to store the data obtained during the test process (ie, the test results, performance indicator results, failure reasons, etc. obtained by the test result statistics and failure reason analysis module).

[0025] Preferably, the statistical test results in combination with the configuration data include: (3.1) If it is a single service test, after the test is completed, the results of the single service test will be counted.

[0026] (3.2) 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 results of each test are counted separately and summarized.

[0027] (3.3) 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; when the concurrent test is completed, the results of each test will be counted separately and summarized.

[0028] In the 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, the railway specific service test includes: function addressing, location-based addressing and railway emergency call test.

[0029] At the same time, interface testing can also be implemented, including: MCX-1 interface and MCX-3 interface testing; wherein, 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.

[0030] Based on the above function and interface test results, the test indicators can be quantified through data analysis to achieve performance testing of the railway broadband trunking communication system.

[0031] 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 with reference to a specific embodiment below.

[0032] 1. Overall overview of the plan.

[0033] The above solution provided by the embodiment of the present invention can realize the function and interface automatic test of railway broadband trunking communication, realize the performance test of railway broadband trunking communication system, provide a friendly test interface, analysis and display functions, and support railway dedicated call service test and service failure cause analysis functions. The specific description is as follows.

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

[0035] Railway broadband trunking communication services have many functions and involve complex interface protocols. When manual testing is used, the test efficiency is low and there are many test requirements and analysis work. The solution provided by the present invention can realize automated testing of the main functions and interface protocols of railway broadband trunking communication MCX.

[0036] (2) Implement performance testing of railway broadband trunking communication systems.

[0037] The existing test contents mainly focus on functions and interfaces, but lack performance testing, especially large-volume testing such as concurrent processing capability. The solution provided by the present invention can test the concurrent processing performance of the system and conduct quantitative evaluation of the system performance. In addition, when conducting large-volume testing, there is no need to configure a large number of physical or simulated terminals, as the test system itself has a large number of terminal simulation functions.

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

[0039] 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.

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

[0041] The solution provided by the present invention is mainly for railway MCX trunking communication services, and supports railway-specific services such as function number operation, function addressing, location addressing, area-based group calling, emergency calling and other test functions. In addition, for service failure scenarios, it has detailed cause analysis and display functions.

[0042] 2. Overall system architecture.

[0043] 1. System architecture.

[0044] like Figure 2 As shown, the overall architecture of the system (automatic test system) of the present invention mainly includes: a test case description file storage unit, a test system application unit, and an MCX interface protocol library.

[0045] 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 control and analysis of test business, display of test data (mainly data obtained by the test result statistics and failure cause analysis module), storage of test data, test result statistics and failure cause analysis, etc.

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

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

[0048] 2. Automated testing content.

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

[0050] (1) Business function testing.

[0051] (1.2) Terminal registration and deregistration test.

[0052] (1.3) Function number operation test.

[0053] (1.4) Voice service testing, including: voice individual call, group call, voice right control testing, etc.

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

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

[0056] (1.7) Railway specific business tests, including: functional addressing, location-based addressing, railway emergency call test, etc. Among them, 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; railway emergency call is implemented by the call module.

[0057] (2) Interface testing.

[0058] 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 systems.

[0059] (3) Performance testing.

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

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

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

[0063] As the input of the test task, the test case description file 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 3As 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.

[0064] In actual use, various test case description file templates are given in advance, and testers can modify specific parameters as needed to improve test configuration efficiency. In addition, the test case description file structure is universal, which is convenient for different business functions, interfaces, and performance tests to be reused.

[0065] 2. Test system application unit.

[0066] Select the corresponding test case file and confirm 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.

[0067] like Figure 4 As shown in the figure, the main process of test task distribution and control includes: (1) Parse the test case description file to obtain the test content and configuration data.

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

[0069] (3) For a single service test, after the control unit completes the test, it will compile statistics on the service test indicator results.

[0070] (4) For cyclic multiple service tests, the control unit initiates service tests at specified intervals according to 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.

[0071] (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.

[0072] (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 delay, and concurrent volume.

[0073] After completing the test in the above way, determine the service execution status. 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 counted and the reasons for the service failure are analyzed, including: comprehensive analysis through protocol content comparison, signaling process analysis, signaling return value, and service logs, and the reasons for service failure are summarized and classified and displayed. The specific instructions are as follows.

[0074] The protocol content comparison mainly performs detailed verification on 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.

[0075] Signaling process analysis: The main business functions of MCX are completed by multiple signaling interactions. The signaling process points that are interrupted when the business fails are identified for comprehensive analysis.

[0076] 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.

[0077] The business log mainly contains all the data content and process 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 troubleshooting.

[0078] 3. MCX interface protocol library.

[0079] like Figure 5 As shown in the figure, the MCX interface protocol library mainly includes: interface call, registration / deregistration, function number operation, location operation, call, voice control, video transmission control, data, context maintenance, bottom layer protocol library and other modules, which realizes the MCX related interface protocol of railway broadband trunking communication service, supports MCX-1 interface and MCX-3 interface, and is called by the upper layer of the test system. The MCX interface protocol library has an efficient call and callback interface with the upper layer of the test system, and can realize the corresponding interface protocol and communication function according to the upper layer instructions.

[0080] The above system provided by the embodiment of the present invention can realize the automatic testing of the functions, interfaces and performance of the MCX system; in the above 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 operation 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, and can be efficiently called by the upper layer to realize testing. The above scheme of the present invention can realize the automatic testing and analysis of the main business functions, interfaces and performance, improve the test efficiency, and can quantify the test indicators, so that the function, interface and performance test is more complete and accurate.

[0081] Technical personnel in the relevant field can clearly understand that for the convenience and simplicity 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.

[0082] Embodiment 2 The 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 above embodiment. The method includes: Pre-configure test case description files and 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. Parse the test content and configuration data from the test case description file, form the test control logic according to 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 to be tested, and combine the configuration data to count the test results, 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, count the test results and analyze the reasons for the service failure.

[0083] Considering that the above embodiments have already made a detailed introduction to each internal part of the system, they will not be described in detail.

[0084] The above is only a preferred specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by any technician familiar with the technical field within the technical scope disclosed in the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope 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 in any form that the information constitutes prior art 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; among which: The test case description file storage unit is used to store a pre-configured test case description file; 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 used to parse the test content and configuration data from the test case description file, form a test control logic according to 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 to the MCX system to be tested, and calculate test results in combination with the configuration data, and then analyze the test results to obtain performance indicator results of the MCX system to be tested, and when the performance indicator results do not meet the expected requirements, calculate the test results and analyze the reasons for the service failure.

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 which, 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, the function number operation module, the location operation module, the call module, the voice control module, the video transmission control module and the data module are MCX interface protocol modules for interacting with the MCX system to be tested for the corresponding service type; 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 for data maintenance 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 the test case description file in a human-computer interaction manner, and to select the test case description file in a human-computer interaction manner and provide it to the test control module; it is also used to display the test results, performance index results and failure reasons obtained by the test result statistics and failure reason analysis module; The test control module is used to parse the test content and configuration data from the test case description file selected by the user interface module, form a test control logic according to 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, and initiate the corresponding function test and / or interface test to the MCX system to be tested; The test result statistics and failure cause analysis module is used to combine the configuration data to count the test results, and then analyze the test results to obtain the performance index results of the MCX system to be tested; when the performance index results do not meet the requirements, the test results are counted and the reasons for the service failure are analyzed; when analyzing the reasons for the test failure, a comprehensive analysis is performed through protocol content comparison, signaling process analysis, signaling return value, and service log, and the reasons for the service failure are summarized and classified; 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 combined with the configuration data include: If it is a single service test, after the test is completed, the result of the single service test is 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 combined with the configuration data include: If it is a cyclic multiple service test, 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 combined with the 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; when 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; The interface test includes: MCX-1 interface and MCX-3 interface test; wherein, 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.

10. An automated testing method for a railway broadband trunking communication system, characterized in that: Based on the automated testing system according to any one of claims 1 to 9, the method comprises: Pre-configure test case description files and 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. Parse the test content and configuration data from the test case description file, form the test control logic according to 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 to be tested, and combine the configuration data to count the test results, 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, count the test results and analyze the reasons for the service failure.

Images