Automatic testing method for realizing interaction with FTTR terminal through MQTT protocol

Abstract

The invention relates to an automatic test method for realizing interaction with an FTTR terminal through an MQTT protocol, which can solve the problems of difficulty in manual test, incapability of meeting functional requirements of the terminal before network access, no standardized automatic process test and the like, and is beneficial to improving the test efficiency and the terminal quality and reducing the cost of manpower, material resources and financial resources. Comprising the following steps of: automatically identifying a management request message reported by a terminal through a packaging MQTT message technology, realizing unified authentication management of the terminal by utilizing an MQTT protocol, performing automatic analysis operation on an FTTR terminal message through automatic task management of an automatic test platform, performing process management and control on terminal normative test and performance alarm data, and performing data management and control on the terminal normative test and performance alarm data. And full-process end-to-end task management and control are performed from application, auditing, execution and results.

Description

Technical Field

[0001] The present invention relates to the technical field of terminal automated network access testing, and particularly to an automated testing method for interacting with an FTTR terminal through the MQTT protocol. Background Art

[0002] The MQTT protocol is a lightweight client-server based message publish / subscribe transport protocol (MQTT, Message Queuing Telemetry Transport). The MQTT protocol enables lightweight, simple, open, and flexible message interaction.

[0003] FTTR (Fiber to The Room) is a technology that extends optical fibers from a communication base station to every corner of a home interior, aiming to provide home users with extremely high-speed Internet access services. By replacing network cables with optical fibers and deploying optical networking terminals, interconnection with a home gateway is achieved, and combined with technologies such as dual-band Wi-Fi, Wi-Fi6, and Wi-Fi7, full-house network coverage is ensured.

[0004] A terminal, abbreviated as CPE (Customer Premise(s) Equipment), is any connected device used to access the Internet or generally access services on a provider's network, whether directly or indirectly connected to the network terminal.

[0005] Along with the high-quality, high-bandwidth, and high-connection requirements of home user networks, and with the popularization of P2P, P2B, AI devices, and applications, the demand of home users for the network is no longer just connection, but rather the ability to uniformly manage AI smart home applications and provide a wonderful digital life experience. The FTTR technology meets this demand through a fiber-to-the-room solution, promoting the upgrade of home broadband from "one network" to a "smart home". To solve problems such as low rate, poor coverage, and slow roaming in traditional full-house Wi-Fi networking, the FTTR technology is innovated to extend optical fibers to each room, each local point, and each hidden point, achieving full-house Wi-Fi coverage. To solve these problems, it is necessary to conduct automated testing on the functions of the FTTR terminal when the terminal accesses the gateway, and the terminal can be accessed and used if it meets the network access conditions.

[0006] The pre-network access testing process for terminals is not perfect, with deficiencies in problem recheck, arrival sampling inspection, and pre-network access testing; on the other hand, there is no systematic support for testing process control. In previous testing processes, information was mainly recorded and transmitted through emails and other forms, and the process was not rigorous enough, easily resulting in risks such as insufficient performance after the terminal accesses the network, leading to fault complaints and leakage.

[0007] There are many FTTR terminal manufacturers that major operators need to manage currently, with uneven software versions, models, etc. Under the existing terminal management mode, when the functions of the FTTR terminal version change, many manufacturers need to cooperate in modification and debugging, and then version upgrades are carried out. The debugging and upgrade cycles are relatively long, and the ability to support standardized, process-based, and automated testing methods has not been introduced. The following defects exist in the existing technology:

[0008] 1) Test the terminal manually, and the manual test is slow and the data is inaccurate.

[0009] 2) It is impossible to conduct automated testing in a unified standard.

[0010] 3) It is impossible to use a unified standard process for automated testing.

[0011] 4) It is impossible to batch execute standardized functions, performance alarm data standards, and normative ability tests.

[0012] 5) Manual testing of individual terminals increases labor and material costs and takes a long time. Summary of the Invention

[0013] In view of the defects or deficiencies in the existing technology, the present invention provides an automated testing method for interacting with FTTR terminals through the MQTT protocol, which can solve problems such as difficult manual testing, failure to meet the functional requirements before terminal network access, and lack of standardized automated process testing, and is conducive to improving testing efficiency, terminal quality, and reducing labor, material, and financial costs.

[0014] The technical solution of the present invention is as follows:

[0015] An automated testing method for interacting with FTTR terminals through the MQTT protocol, characterized in that it includes automatically identifying the terminal-reported management request message by encapsulating MQTT message technology, implementing unified authentication management of the terminal using the MQTT protocol, and automatically analyzing the FTTR terminal message through the automated task management of the automated testing platform, and conducting process control on the terminal normative test and performance alarm data, and conducting end-to-end task control on the entire process from application, review, execution to result.

[0016] It includes a query operation between the automated testing platform and the FTTR terminal, and the steps are as follows:

[0017] Step A1, the FTTR terminal requests to create an MQTT connection to the automated testing platform;

[0018] Step A2, the automated testing platform responds to the connection request;

[0019] Step A3, the FTTR terminal subscribes to the topics of registration response and operation request from the automated testing platform;

[0020] Step A4, the FTTR terminal sends a registration request to the automated test platform;

[0021] Step A5, the automated test platform responds to the registration request;

[0022] Step A6, the automated test platform sends a query operation request to the FTTR terminal;

[0023] Step A7, the FTTR terminal sends a query operation response to the automated test platform.

[0024] Including data reporting between the automated test platform and the FTTR terminal, the steps are as follows:

[0025] Step B1, the FTTR terminal requests to create an MQTT connection from the automated test platform;

[0026] Step B2, the automated test platform responds to the connection request;

[0027] Step B3, the FTTR terminal subscribes to the topics of registration response and operation request from the automated test platform;

[0028] Step B4, the FTTR terminal sends a registration request to the automated test platform;

[0029] Step B5, the automated test platform responds to the registration request;

[0030] Step B6, the automated test platform sends a data reporting request to the FTTR terminal;

[0031] Step B7, the FTTR terminal responds to the data reporting request.

[0032] Including test task execution between the automated test platform and the FTTR terminal, the steps are as follows:

[0033] Step 1, create a test task;

[0034] Step 2, save the test task to the database;

[0035] Step 3, judge whether it is successful. If not, end. If so, go to Step 4;

[0036] Step 4, start the audit test task;

[0037] Step 5, judge whether it needs to be executed. If not, it is regarded as a failed audit and return to Step 1. If so, go to Step 6;

[0038] Step 6, schedule the monitoring task;

[0039] Step 7, determine whether to start execution. If not, return to Step 6. If yes, proceed to Step 8;

[0040] Step 8, send an execution transaction request to the ACS, where ACS is the Automatic Configuration Server;

[0041] Step 9, determine whether the request is valid. If not, return to Step 6. If yes, proceed to Step 10;

[0042] Step 10, add the test task to the queue;

[0043] Step 11, the ACS process updates the execution result of the test task in the queue;

[0044] Step 12, determine whether the execution is completed. If yes, end. If not, return to Step 6.

[0045] It includes the network access test process between the automated test platform and the FTTR terminal, and the steps are as follows:

[0046] Step C1, the terminal manufacturer submits a test application;

[0047] Step C2, the automated test platform reviews the test information. If the review is passed, proceed to the next step. If the review fails, return to the terminal manufacturer;

[0048] Step C3, the tester performs the test and generates a test report. For the test items that fail the test, return them to Step C1.

[0049] It includes the automated application process between the automated test platform and the FTTR terminal, and the steps are as follows:

[0050] Step D1, after the manufacturer fills in the application information, terminal information, and test item information, it is transferred to the network department;

[0051] Step D2, if the network department rejects the application, it sends a rejection notice to the manufacturer. If the network department agrees, proceed to Step D3;

[0052] Step D3, the manufacturer's test department conducts the test and exports the test information after the test is completed.

[0053] It includes the automated test implementation process between the automated test platform and the FTTR terminal, and the steps are as follows:

[0054] Step E1, the test department generates test tasks for the online terminals by issuing tests;

[0055] Step E2, the test department obtains the test results based on the test tasks and rewrites the test items that fail the test execution;

[0056] Step E3, generate a document for the test results.

[0057] The technical effects of the present invention are as follows: The present invention realizes an automated test method for interacting with FTTR terminals through the MQTT protocol. By conducting process control over the standardized testing of terminal devices and test tasks, end-to-end task control is carried out throughout the entire process from application, review to the execution of test tasks. Especially in the part of FTTR terminal network access testing, it solves the problems of cumbersome manual test processes, long time consumption, and inaccurate resource matching, and further improves the quality and efficiency of terminal network access.

[0058] Through the MQTT protocol and the automated test platform, the present invention can automatically identify and register FTTR terminals and conduct classified automated testing, which is faster and more accurate than manual testing.

[0059] Through the automated network access testing of FTTR terminals, the present invention selects test sets, automatically creates service work orders, automatically creates test tasks, and generates test result reports when executing test tasks. The entire process can complete the test within 2 hours. In the past, the test cycle took 1 to 3 weeks to complete, greatly improving the test efficiency.

[0060] Initiated by testers / manufacturers / administrators, reviewed by managers, and executed by testers, the entire test process can be managed and controlled, making the entire test process procedural, standardized, standardized, and unified. After the test is completed, a full and detailed test report is generated, providing a reliable basis for the formal network access of FTTR terminals.

[0061] Based on the test report data, the present invention conducts a full analysis of the test data before the network access of FTTR terminals. Detailed data is generated through all test items such as command execution, remote operation, fault diagnosis, and decoupling management, and a quality-difference terminal identifier is formed, thereby screening out high-quality terminals and enhancing market competitiveness. At the same time, it can also be used as a reference standard for guiding the procurement of FTTR terminals.

[0062] Based on the automated test result report, the present invention establishes a quality-difference terminal library for existing problematic terminals, and then detects the business execution effect of the terminals after network access through test indicators, providing business guarantee for the subsequent network access of existing problematic terminals. To improve the customer business quality and usage perception and reduce the customer fault complaint rate. Brief Description of the Drawings

[0063] Figure 1 It is a schematic diagram of the FTTR interaction process involved in implementing the automated test method for interacting with FTTR terminals through the MQTT protocol. MQTT is Message Queuing Telemetry Transport. FTTR is Fiber to The Room. Figure 1It includes Step 1, where the FTTR terminal requests to create an MQTT connection from the automated test platform; Step 2, where the automated test platform responds to the connection request; Step 3, where the FTTR terminal subscribes to the topics of registration responses and operation requests from the automated test platform; Step 4, where the FTTR terminal sends a registration request to the automated test platform; Step 5, where the automated test platform responds to the registration request; Step 6, where the automated test platform sends a query operation request to the FTTR terminal; Step 7, where the FTTR terminal sends a query operation response to the automated test platform.

[0064] Figure 2 It is a schematic diagram of the main FTTR data flow involved in implementing the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 2 It includes Step 1, where the FTTR terminal requests to create an MQTT connection from the automated test platform; Step 2, where the automated test platform responds to the connection request; Step 3, where the FTTR terminal subscribes to the topics of registration responses and operation requests from the automated test platform; Step 4, where the FTTR terminal sends a registration request to the automated test platform; Step 5, where the automated test platform responds to the registration request; Step 6, where the automated test platform sends a data reporting request to the FTTR terminal; Step 7, where the FTTR terminal responds to the data reporting request.

[0065] Figure 3 It is a schematic diagram of the process of the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 3 It includes Step 1, creating a test task; Step 2, saving the test task to the database; Step 3, judging whether it is successful. If not, end. If so, enter Step 4; Step 4, starting the audit test task; Step 5, judging whether it needs to be executed. If not, it is regarded as a failed audit and return to Step 1. If so, enter Step 6; Step 6, scheduling the monitoring task; Step 7, judging whether it starts to be executed. If not, return to Step 6. If so, enter Step 8; Step 8, sending an execution transaction request to the ACS, where ACS is the Auto-Configuration Server; Step 9, judging whether the request is valid. If not, return to Step 6. If so, enter Step 10; Step 10, adding the test task to the queue; Step 11, the ACS process updates the execution result of the test task in the queue; Step 12, judging whether the execution is ended. If so, end. If not, return to Step 6.

[0066] Figure 4 It is a schematic diagram of the network access test process involved in implementing the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 4It includes Step 1 where the terminal manufacturer submits a test application; Step 2 where the automated test platform reviews the test information. If the review passes, it proceeds to the next step. If the review fails, it returns to the terminal manufacturer; Step 3 where the tester performs the test and generates a test report. For the test items that fail the test, they are returned to Step 1. The test items that fail the test can be repeatedly tested, and the test items can be customarily selected in the submitted test application.

[0067] Figure 5 It is a schematic diagram of the test item configuration principle involved in implementing the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 5 It includes Test Item 1, Test Item 2, and Test Item 3. Each test item contains its own id and the id of the upper level, i.e., the parent id. Each test item involves basic default parameter configuration and custom addition of return parameter configuration.

[0068] Figure 6 It is a schematic diagram of the automated application process involved in implementing the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 6 It includes Step 1 where the manufacturer fills in the application information, terminal information, and test item information and then transfers it to the network department; Step 2 where if the network department rejects the application, it sends the rejection notice to the manufacturer. If the network department agrees, it proceeds to Step 3; Step 3 where the manufacturer's test department conducts the test and exports the test information after the test is completed.

[0069] Figure 7 It is a schematic diagram of the automated test implementation process involved in implementing the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 7 It includes Step 1 where the test department generates a test task for the online terminal by issuing a test; Step 2 where the test department obtains the test result based on the test task and rewrites the test items that fail the test execution; Step 3 where the test result is generated into a document.

[0070] Figure 8 It is a diagram of the operation page setting for the overall view of test items and global configuration of test item parameters included in the configuration of global test items involved in implementing the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention.

[0071] Figure 9 It is a diagram of the operation page setting for filling in basic application information and basic device information included in the automated test application involved in implementing the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention.

[0072] Figure 10It is a diagram of the operation page setting for filling in audit information in the management staff audit involved in implementing the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention.

[0073] Figure 11 It is a diagram of the operation page setting for the test department to select self-defined parameters including audit information and test item operations in the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention.

[0074] Figure 12 It is a diagram of the operation page setting for the test department to select self-defined parameters including the test item parameters of this application in the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention.

[0075] Figure 13 It is a diagram of the page setting for generating an automated test result document including an execution result list in the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention.

[0076] Figure 14 It is a schematic diagram of the relationship between the test task and the FTTR terminal in the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Detailed implementation manners

[0077] The present invention will be described below with reference to the accompanying drawings ( Figures 1 - 14 ) and embodiments.

[0078] Figure 1 It is a schematic diagram of the FTTR interaction process involved in the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 2 It is a schematic diagram of the main FTTR data process involved in the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 3 It is a schematic diagram of the process of the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 4 It is a schematic diagram of the network access test process involved in the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 5 It is a schematic diagram of the test item configuration principle involved in the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 6 It is a schematic diagram of the automated application process involved in the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention. Figure 7 It is a schematic diagram of the automated test implementation process involved in the automated test method for interacting with the FTTR terminal through the MQTT protocol of the present invention.Figure 8 It is a diagram of the operation page setting for configuring global test item parameters involved in the automated test method for implementing the interaction between the present invention and the FTTR terminal through the MQTT protocol, which includes an overview of test items and global configuration of test item parameters. Figure 9 It is a diagram of the operation page setting for the automated test application involved in the automated test method for implementing the interaction between the present invention and the FTTR terminal through the MQTT protocol, which includes filling in basic application information and basic device information. Figure 10 It is a diagram of the operation page setting for the management staff review involved in the automated test method for implementing the interaction between the present invention and the FTTR terminal through the MQTT protocol, which includes filling in review information. Figure 11 It is a diagram of the operation page setting for the test department to select self-defined parameters involved in the automated test method for implementing the interaction between the present invention and the FTTR terminal through the MQTT protocol, which includes review information and test item operations. Figure 12 It is a diagram of the operation page setting for the test department to select self-defined parameters involved in the automated test method for implementing the interaction between the present invention and the FTTR terminal through the MQTT protocol, which includes the test item parameters for this application. Figure 13 It is a diagram of the page setting for generating the automated test result document involved in the automated test method for implementing the interaction between the present invention and the FTTR terminal through the MQTT protocol, which includes an execution result list. Figure 14 It is a schematic diagram of the relationship between the test task and the FTTR terminal involved in the automated test method for implementing the interaction between the present invention and the FTTR terminal through the MQTT protocol. Refer to Figures 1 to 14 As shown, the automated test method for implementing the interaction between the MQTT protocol and the FTTR terminal includes automatically identifying the terminal-reported management request message by encapsulating the MQTT message technology, implementing unified authentication management of the terminal using the MQTT protocol, and automatically analyzing the FTTR terminal message through the automated task management of the automated test platform, and performing process control on the terminal's normative test and performance alarm data, and conducting end-to-end task control from application, review, execution to result.

[0079] It includes a query operation between the automated test platform and the FTTR terminal, and the steps are as follows: Step A1, the FTTR terminal requests to create an MQTT connection to the automated test platform; Step A2, the automated test platform responds to the connection request; Step A3, the FTTR terminal subscribes to the topics of registration response and operation request from the automated test platform; Step A4, the FTTR terminal sends a registration request to the automated test platform; Step A5, the automated test platform responds to the registration request; Step A6, the automated test platform sends a query operation request to the FTTR terminal; Step A7, the FTTR terminal sends a query operation response to the automated test platform.

[0080] Including data reporting between the automated test platform and the FTTR terminal, the steps are as follows: Step B1, the FTTR terminal requests to create an MQTT connection from the automated test platform; Step B2, the automated test platform responds to the connection request; Step B3, the FTTR terminal subscribes to the topics of registration response and operation request from the automated test platform; Step B4, the FTTR terminal sends a registration request to the automated test platform; Step B5, the automated test platform responds to the registration request; Step B6, the automated test platform sends a data reporting request to the FTTR terminal; Step B7, the FTTR terminal responds to the data reporting request.

[0081] Including test task execution between the automated test platform and the FTTR terminal, the steps are as follows: Step 1, create a test task; Step 2, save the test task to the database; Step 3, determine whether it is successful. If not, end. If so, proceed to Step 4; Step 4, start to review the test task; Step 5, determine whether it needs to be executed. If not, it is regarded as a failed review and return to Step 1. If so, proceed to Step 6; Step 6, schedule a monitoring task; Step 7, determine whether to start execution. If not, return to Step 6. If so, proceed to Step 8; Step 8, send an execution transaction request to the ACS, where ACS is the automatic configuration server; Step 9, determine whether the request is valid. If not, return to Step 6. If so, proceed to Step 10; Step 10, add the test task to the queue; Step 11, the ACS process updates the execution result of the test task in the queue; Step 12, determine whether the execution is completed. If so, end. If not, return to Step 6.

[0082] Including the network access test process between the automated test platform and the FTTR terminal, the steps are as follows: Step C1, the terminal manufacturer submits a test application; Step C2, the automated test platform reviews the test information. If the review is passed, proceed to the next step. If the review fails, return to the terminal manufacturer; Step C3, the tester performs the test and generates a test report. For the test items that fail, return them to Step C1.

[0083] Including the automated application process between the automated test platform and the FTTR terminal, the steps are as follows: Step D1, after the manufacturer fills in the application information, terminal information, and test item information, it is transferred to the network department; Step D2, if the network department rejects the application, it sends a rejection notice to the manufacturer. If the network department agrees, proceed to Step D3; Step D3, the manufacturer's test department conducts the test and exports the test information after the test is completed.

[0084] It includes the automated test implementation process between the automated test platform and the FTTR terminal, and the steps are as follows: Step E1, the testing department generates test tasks for the online terminals by issuing tests; Step E2, the testing department obtains test results according to the test tasks and rewrites the test items with failed test executions; Step E3, generates a document for the test results.

[0085] In view of the fact that there is no strict review process and management mechanism before the terminal version is put into the network in the present invention. When a failure occurs, the response mechanism and traceability mechanism are relatively weak, and a relatively perfect test, management, and response mechanism is not established throughout the process. An automated test method for interacting with the FTTR terminal through the MQTT protocol is adopted to solve the problems of difficult manual testing, inability to meet the functional requirements before the terminal is put into the network, and lack of standardized automated process testing, improve the test efficiency and terminal quality, and reduce the costs of manpower, material resources, and financial resources. A set of terminal automated test process standards is customized, which mainly meets five application scenarios: terminal network access testing, problem retesting, sampling testing, sending for testing, and service configuration. The monitoring means are further improved to make the entire test process manageable and visible. At the same time, in view of the fact that there is no strict review process and management mechanism before the version is put into the network; when a failure occurs, the response mechanism and traceability management are relatively weak. A relatively perfect test, management, and response mechanism is not established throughout the process; based on this, a new automated task management requirement is added. Process management is carried out for the terminal compliance testing and the accuracy of the terminal performance alarm reporting data. Process task control management is carried out from application, review, and execution.

[0086] The present invention mainly solves the problems that due to the large number of terminals, many terminal manufacturers, and uneven quality, various problems brought about after the terminals are put into the network affect high-quality users and the business development of operators, and cannot meet the requirements of operators for terminal quality control and support for marketing and business decision-making. It improves the processes of terminal network access testing, terminal network access, data processing, operation functions, etc. For each function, a large amount of test time and energy need to be invested for repeated testing; the overall efficiency is low. At the same time, in view of the fact that there is no strict review process and management mechanism before the version is put into the network; when a failure occurs, the response mechanism and traceability management are relatively weak. A relatively perfect test, management, and response mechanism is not established throughout the process; based on this, a new automated task management capability is added. The present technical invention improves the terminal network access quality and test efficiency, and solves the problems of rapid recovery of high-user-quality failures and the increase in the ARUP value (ARUP, average revenue per user) brought about by the high-quality development of operator services.

[0087] An automated test method for interacting with FTTR terminals through the MQTT protocol automatically identifies, authenticates, and registers FTTR terminals through the MQTT protocol technology cycle, automatically identifies and classifies the manufacturer models, software versions, and hardware versions of FTTR terminals, and uses terminal remote management based on the MQTT protocol to establish an ACS Server (Automatic Configuration Server) to perform secure automated tests on FTTR terminals. It mainly realizes the automated test capabilities for the specification functions, parameter data, performance monitoring and alarming, and fault diagnosis functions of FTTR terminals.

[0088] The automated test platform realizes the remote access authentication of FTTR terminals. Among them, through the MQTT protocol, it receives and executes the test instructions issued by the ACS Server; the MQTT Adapter provides the required automated test functions for the FTTR terminal remote communication mechanism.

[0089] Using the MQTT protocol, a "bridge" is built between the system ACS Server service and the MQTT Adapter server, enabling the FTTR terminal to obtain a service connection. Through this service connection, the method can be called to achieve the purpose of communication between the FTTR and the automated test platform, and realize the communication between the FTTR terminal and the ACS Server service to achieve the unified registration authentication and operation of the FTTR terminal.

[0090] The automated test issues instructions to the specified FTTR terminal, performs command operations and automatic test function points, performance alarm data, and specification functions on the FTTR terminal before it enters the network, and returns the statistical data of the execution test results to the customer, and the process ends.

[0091] Using the MQTT protocol to implement automated tests for interacting with FTTR terminals, completing the unified management, unified authentication, unified standards, unified specifications, unified functions, and remote fault diagnosis and processing capabilities of FTTR terminals. The specific implementation part of the present invention describes the fully automated unified standard and standardized test method for realizing the management of FTTR terminals.

[0092] An automated test method for interacting with the FTTR terminal through the MQTT protocol. The automated test platform refers to the network device that is connected to the network from the FTTR terminal at the user end and provided to the user. The user does not care about its internal structure and principle, but only cares about the functions it provides and how to use these functions. The MQTT is an application layer network management technology protocol. The terminal is the device end connected to the FTTR. The test task is to configure the server for automated testing. In the MQTT end and the FTTR end, the protocol messages encapsulated in the MQTT publish / subscribe mode are in the FTTR end to implement the automated test task. The FTTR end uses the MQTT protocol communication mechanism call method between the MQTT message service and the FTTR client to achieve unified standardization, automation, processization, and standardization testing of the FTTR terminal, meeting application scenarios such as operator FTTR terminal network access testing, in-network problem retesting, sampling / sending for testing, and standardization testing, and realizing that the entire test process can be managed, controlled, and visualized.

[0093] The present invention relates to the invocation of external tools including: 1. JAVA: openjdk1.8; 2. Spring, a lightweight open-source framework mainly used to simplify the development of Java enterprise applications. By providing functions of dependency injection (DI) and inversion of control (IoC), it helps developers reduce the complexity of application programs and improve development efficiency; 3. Build tool: maven; 4. Front-end framework vue2.6.10, a progressive JavaScript framework for building user interfaces. It is built based on HTML, CSS, and JavaScript, provides a declarative component-based programming model, and can efficiently develop user interfaces; 5. zookeeper: dubbo service registry; 6. Service framework Dubbo3: Architected in a layered manner, using this method can decouple each layer. It runs according to the idea that the provider provides services and the consumer consumes services. 7. Logging framework log4j2: Used for processing such as monitoring, management, and classification of logs. 8. Message middleware RocketMQ: A distributed, queue-model message middleware. 9. Database oracle: A relational database with good system portability, simple use, and powerful functions.

[0094] Reference Figure 1, the pre - process of the test operation is as follows: 1. The FTTR terminal requests to create an MQTT connection from the test platform. 2. The test platform responds to the connection request, and the MQTT connection is successfully created. 3. The FTTR terminal subscribes to MQTT topic messages such as registration responses and operation requests. 4. The FTTR terminal sends a registration request to the test platform. 5. The test platform responds to the registration request, and the management channel is formally established and maintained. The management operation process is as follows: 6. The test platform sends a management operation request message. 7. The intelligent gateway sends a response message for the management operation. 8. End.

[0095] Reference Figure 2 , the pre - process of data reporting is as follows: 1. The FTTR terminal requests to create an MQTT connection from the test platform. 2. The test platform responds to the connection request, and the MQTT connection is successfully created. 3. The FTTR terminal subscribes to MQTT topic messages such as registration responses and operation requests. 4. The FTTR terminal sends a registration request to the test platform. 5. The test platform responds to the registration request, and the management channel is formally established and maintained. The data reporting process is as follows: 6. The FTTR terminal regularly sends a data reporting request message. 7. The test platform sends a corresponding response each time it receives a data reporting request. 8. End.

[0096] Reference Figure 3 and Figure 4 , the permission description and process permission nodes are as follows: Submission of application (process initiator): Terminal manufacturer; To - do item (process review department): Operator management personnel; Task execution: Testers; Task result viewing: Terminal manufacturer, operator management personnel, testers. The process description is as follows: 1. Terminal manufacturers under the provincial company / city branch of the operator need to apply for terminal network access testing, and fill in the basic device information in the review process to submit the application. 2. The provincial company / city branch of the operator reviews the application requirements submitted by the terminal manufacturer; selects the test items to be tested. If the review is passed, the task item changes from the to - do item status to the completed item status, and the process enters the test execution step. If the review is rejected, the reviewer can specify it to the rejection node; the applicant resubmits the information and conducts the review again, and the reviewer can also end the review process with one key; the process ends. 3. For scenarios where terminal manufacturers may conduct repeated tests on certain test items; the management review is a configurable node; the review information is configured for the terminal manufacturer to review. After the terminal manufacturer completes the execution, the task item changes from the to - do item status to the completed item. 4. Testers perform task testing and generate a test report after completion; for unpassed test items, the terminal manufacturer can conduct repeated tests, and the process ends.

[0097] Reference Figure 5, The automated testing platform manages and reviews the submitted test tasks. According to the application information submitted by the terminal manufacturer, the management staff reviews the set task strategy information; the automated testing platform automatically creates and generates task information. The basic information in the management task is obtained from the application items in the review process, and the strategy information is executed according to the strategy set by the management staff. Implementation principle: The product contains multiple test items, which are displayed in the form of a hierarchical directory. Each test item contains its own id and the id of the upper level, forming an association. Each test item contains some basic default parameters. When the user does not make special customization, the issued command will obtain the corresponding default parameters; when customizing and adding return parameter configurations, when the command returns, the corresponding configured return parameters will be obtained.

[0098] Reference Figure 6 , The manufacturer's application testing process is divided into information in three modules:

[0099] Application basic information module: According to the role information, the applicant and the application department are automatically generated. The manufacturer needs to fill in the name of the application, the application testing time, and the reason for the application.

[0100] Basic information module: Fill in the device type, device manufacturer, device model, hardware version, software version, port information, whether it supports IPV6, network side interface, and device identification of the device. Click to search to verify the device information.

[0101] Test item information: It includes 5 major test blocks: service activation test, fault diagnosis test, local configuration test, compliance test verification, and key data collection. It includes necessary test items and optional test items.

[0102] Management staff review: After receiving the manufacturer's application, the management staff verifies it. If it is rejected, the application will be returned to the manufacturer; after agreeing to the application, the application will be transferred to the manufacturer's test department for testing.

[0103] Test department testing: After receiving the application, the test department can view the default parameters of the test items and can also customize the default parameters independently.

[0104] Issue test items, automatically wait for the terminal device to go online. After going online, the terminal reports event-type information. After receiving the information, automated testing is performed on the set test items, and each test item can return test item result information.

[0105] Regarding the automated test item result information, both the manufacturer and the management staff can view it. For the failed test items, they can be manually executed for retesting.

[0106] Export test results: After confirming the results of automated and manual testing, the data will be automatically exported in the format to generate a modular PDF test result document.

[0107] Reference Figure 7 After the testing department checks and confirms the test information, it will issue the test and generate a test task. When the test task reaches the set test execution time, it will wait for the online message of the terminal. After receiving the online message of the terminal, it will interact with the terminal to complete the test items of service activation test, fault diagnosis test, local configuration test, compliance test verification, and key data collection. After the test is completed, the testing department can retest the test items that failed to execute. Finally, the test results will be generated into a test document.

[0108] Reference Figures 8 - 13 All are computer pages in the simulation case.

[0109] The specific source code of the technical solution of the present invention is as follows:

[0110]

[0111]

[0112]

[0113]

[0114]

[0115]

[0116] The content not described in detail in the specification of the present invention belongs to the prior art well-known to those skilled in the art. It is hereby pointed out that the above description helps those skilled in the art to understand the present invention, but does not limit the protection scope of the present invention. Any implementation that makes equivalent substitutions, modifications and improvements, and / or simplifies the above description without departing from the essence of the present invention falls within the protection scope of the present invention.

Claims

1. An automated testing method for interacting with FTTR terminals through the MQTT protocol, characterized in that: This includes automatically identifying terminal reporting management request messages through encapsulation of MQTT message technology, using the MQTT protocol to achieve unified authentication management of terminals, and automatically analyzing FTTR terminal messages through the automated task management of the automated testing platform, as well as process control of terminal compliance testing and performance alarm data, and end-to-end task control of the entire process from application, review, execution, and results.

2. The automated testing method for interacting with FTTR terminals through the MQTT protocol according to claim 1, characterized in that: Including the query operation between the automated test platform and the FTTR terminal, the steps are as follows: Step A1, the FTTR terminal requests the automated test platform to create an MQTT connection; Step A2, the automated testing platform responds to the connection request; Step A3, the FTTR terminal subscribes to the topics of registration response and operation request from the automated test platform; Step A4, the FTTR terminal sends a registration request to the automated test platform; Step A5, the automated testing platform responds to the registration request; Step A6, the automated test platform sends a query operation request to the FTTR terminal; Step A7: The FTTR terminal sends a query operation response to the automated test platform.

3. The automated testing method for interacting with FTTR terminals through the MQTT protocol according to claim 1, characterized in that: Including data reporting between the automated test platform and the FTTR terminal, the steps are as follows: Step B1, the FTTR terminal requests the automated test platform to create an MQTT connection; Step B2, the automated testing platform responds to the connection request; Step B3, the FTTR terminal subscribes to the topics of registration response and operation request from the automated test platform; Step B4, the FTTR terminal sends a registration request to the automated test platform; Step B5, the automated testing platform responds to the registration request; Step B6, the automated test platform sends a data reporting request to the FTTR terminal; Step B7: The FTTR terminal responds to the data reporting request.

4. The automated testing method for interacting with FTTR terminals through the MQTT protocol according to claim 1, characterized in that: Including the test task execution between the automated test platform and the FTTR terminal, the steps are as follows: Step 1: Create a test task; Step 2, save the test task to the database; Step 3, determine whether it is successful, if not, then end, if yes, then go to step 4; Step 4: Start the audit test task; Step 5: Determine whether it needs to be executed. If not, it is deemed to have failed the review and returns to step 1. If yes, proceed to step 6. Step 6, scheduling monitoring tasks; Step 7, determine whether to start execution, if not, return to step 6, if yes, go to step 8; Step 8: Send a transaction execution request to ACS, which is an automatic configuration server; Step 9, determine whether the request is established, if not, return to step 6, if yes, go to step 10; Step 10, add the test task to the queue; Step 11, the ACS process updates the execution results of the test tasks in the queue; Step 12, determine whether the execution is completed, if yes, then end, if not, return to step 6.

5. The automated testing method for interacting with FTTR terminals through the MQTT protocol according to claim 1, characterized in that: The network access test process between the automated test platform and the FTTR terminal is as follows: Step C1, the terminal manufacturer submits a test application; Step C2: the automated testing platform reviews the test information. If the review is passed, it proceeds to the next step. If the review is not passed, it returns to the terminal manufacturer. In step C3, the tester performs the test and generates a test report. For any test items that fail, the report is returned to step C1.

6. The automated testing method for interacting with FTTR terminals through the MQTT protocol according to claim 1, characterized in that: Including the automated application process between the automated test platform and the FTTR terminal, the steps are as follows: Step D1: The manufacturer fills in the application information, terminal information and test item information and transfers it to the network department; Step D2: If the network department rejects the application, the rejection notice will be sent to the manufacturer. If the network department agrees, the process proceeds to step D3; Step D3: The manufacturer's testing department performs testing and exports test information after the testing is completed. The automated test implementation process between the automated test platform and the FTTR terminal includes the following steps: Step E1, the testing department generates a test task for the online terminal by issuing a test; Step E2, the testing department obtains the test results according to the test tasks and the test items that failed in the rewriting test execution; Step E3, generating a document of the test results.

Images