GB/T 47458-2026Requirements for the long-range test network system of launch vehicles (English PDF)

5.1.1 Network Functions

5.1.1.1 The remote test network should have the following functions.

a) Data Communication. Network connectivity between the launch and control domain, the recovery launch and control domain, and the test center domain enables information communication; key network nodes... The equipment employs redundant design, such as hot standby redundancy for switches and firewalls, enabling it to operate normally even in the event of a single failure.

b) Resource sharing. Provides a secure remote access mechanism, allowing users to access network resources from different locations; key application platforms adopt... Use highly reliable designs, such as employing multiple servers for hot standby or deploying application systems on virtualized cloud platforms.

c) Application Services. Possesses launch support capabilities, enabling monitoring and retrieval of test data from the test center domain and the test control domain. And equipment operating status; possessing network monitoring and management capabilities, including monitoring the network operation and data interaction status of key communication nodes (such as... Real-time monitoring of network device communication status, port status, etc.

d) Data Processing. Possesses the ability to acquire and analyze network data packets, and monitors and traces the flow of network data packets within network devices. Condition.

5.1.1.2 The launch control domain and the recovery control domain should respectively meet the telemetry and control requirements of the launch vehicle during the launch and recovery phases, and should mainly possess the following capabilities. The following functions.

a) The ability to receive, store, manage, and use launch vehicle launch control and recovery data;

b) For measurement and control equipment, recovery measurement and control equipment, remote transmission equipment, network security equipment, transmission security equipment, wireless equipment, and time control equipment. Provides a channel for information exchange, transmission, processing, and display between devices;

c) Send rocket launch control information and recovery control information to the test center domain via a dedicated communication computer or server;

d) Capable of exchanging information with the launch site system for the launch vehicle;

e) It employs a redundant design, enabling it to operate normally under a single failure;

f) Extend the wireless network using wireless devices.

5.1.1.3 The remote transmission link should have the following functions.

a) It can achieve network connectivity between the launch site control domain, the recovery control domain, and the test center domain;

5.1.2 Software Functions

5.1.2.1 Software Information Flow 5.1.2.1.1 The software information flow is shown in Figure

2.The measurement, launch, and control domain and the recovery measurement, launch, and control domain software include real-time transmission software and post-transmission software. During testing... The software suite of Mind Domain includes real-time transmission software, post-transmission software, data service software, data processing software, and data application service software. The real-time transmission software and post-transmission software deployed in the launch control domain and the recovery control domain obtain information from the launch control equipment and then exchange it via the test network. Machines, remote transmission equipment, network security equipment, timing equipment, transmission security equipment, and remote transmission links transmit information to the test center domain. Real-time transmission software and post-transmission software send information to data service software for aggregation, and then to data processing software and data application software. Information is provided using service software. Figure

2.Software information flow in the remote testing network 5.1.2.1.2 The post-transmission software for the test and control domain, the retrieval test and control domain, and the test center domain should have the following functions.

a) Document transfer function between launch sites and launch vehicle development units, compatible with one-to-one or many-to-one modes;

b) A function to record the transfer progress; if the transfer is interrupted, it can resume from the last recorded progress until the file transfer is complete.

c) The ability to directly import structured data into the corresponding database;

d) Function to record the working status and abnormal information during software initialization, operation and shutdown. 5.1.2.1.3 The real-time transmission software for the measurement and control, retrieval measurement and control domain, and test center domain should have the following functions.

a) Receive test data from various systems in the field within the measurement and control area (including telemetry data, ground survey data, wind field meteorological data, and some audio data). The function of transmitting video signals, etc., into data packets (which should include frame counts and verification information) and then sending them to a remote test network;

b) The function of receiving data packets, verifying data packets, and recording anomalies;

c) The function of distributing data packets to their respective designated addresses;

d) Function to count the number of data packets received and sent;

e) Function to count and analyze the number of dropped frames by frame. 5.1.2.1.4 The test center's data service software should have the following functions.

a) Simultaneously receive real-time and post-event data (including telemetry data, ground survey data, and wind field meteorological data) from multiple telemetry and control domains. The system uses functions such as parsing data (including some audio and video signals) to parse the data according to the information frame format in the configuration file.

b) Data storage and ingestion have multi-threaded parallel processing capabilities, which can meet the needs of large-scale real-time data storage and support cloud platforms. Store in the database;

5.1.3 Security Functions

5.1.3.1 Safety Equipment Safety equipment has the following functions.

a) Each domain within the remote test network should be configured with appropriate network security devices, and access between domains across network security boundaries should be managed through these devices. Data flows should communicate through controlled interfaces and access control rules configured on the boundary devices. By default, communication is allowed. Externally controlled interfaces reject all communication;

b) Information transmission between domains within the remote testing network should utilize traffic analysis and tracing equipment to ensure the traceability of transmitted data;

c) A cryptographic device should be configured at the access point between the test and control domain and the remote transmission link, and at the access point between the remote transmission link and the test center domain, to ensure... Information is transmitted in encrypted form over remote transmission links to ensure the security of communication content;

d) Network access control devices should be installed in each network domain to ensure that access network devices are known and controllable;

e) Wireless networks extended by wireless devices should be isolated from wired networks by firewalls.

5.1.3.2 Safety Monitoring The safety monitoring function requirements are as follows:

a) It should possess network analysis capabilities, enabling full-network attack detection and early warning, monitoring abnormal traffic, and providing network intrusion early warning and security features. Situational display capability; (b) It should possess the capability for centralized and unified management, daily operation and maintenance of various safety equipment, and be able to uniformly issue various safety policies. Currently, remote testing is being conducted to improve the interoperability between network security devices and enhance the ability to handle security incidents.

c) It should have the capability to audit security data, enabling it to replay, track, and investigate security incidents;

d) The status of each domain should be monitored and displayed, and changes in the network status of important network nodes should be recorded;

e) Users logging into network switching devices and network security devices should be identified and authenticated. The identity identifier must be unique. When login fails, measures such as ending the session, limiting the number of unauthorized login attempts, and automatically logging out when the login connection times out should be implemented.

f) Antivirus systems should be deployed to implement technical measures or proactive immune trusted verification mechanisms to promptly identify malicious code attacks. Invade and inhibit viral behavior, and effectively block it;

g) Virtual networks for different cloud service customers should be isolated;

h) Wireless networks extended by wireless devices should be physically isolated from the Internet.

6.4 Test Items and Methods

6.4.1 Network Connectivity Test Network connectivity testing shall be conducted between the test control domain (or retrieval test control domain) and the test center domain, with the following requirements.

a) Connect one end of the test tool to the port of the selected access layer device in the test and control domain or the retrieval test and control domain, and connect the other end of the test tool to... Connect to the port of the access layer device selected in the test center domain;

b) Use testing tools to perform 10 tests on critical network devices (such as switches) in the network's key servers, core layer, and aggregation layer. The special network packet explorer (Ping) test, with each test interval of 1 second, is used to test network connectivity;

c) Move the test tool to other test points and repeat step

b) until all devices that need to communicate have been traversed.

6.4.2 Network Performance Testing Network performance testing was conducted according to packet loss rate testing, throughput testing, transmission rate testing, and transmission latency testing, in accordance with GB/T 21671. The regulations shall be followed.

6.4.3 Software Testing

6.4.3.1 Conduct tests on all software used for remote network information transmission, with the following requirements.

a) Develop a test plan and conduct test requirements analysis. Test cases should cover all functions, performance, interfaces, etc., specified in the requirements specification. Safety and other requirements;

b) Design test cases. Test cases should be linked to software requirements and design. Establish a test environment and pass review. Test cases should not be tested in actual use. For tests conducted in an environment, a difference analysis should be performed on the test environment that has been set up.

c) Perform static analysis of the source code according to the test plan, including the functionality, performance, and interfaces of software units, as well as the functionality of software components. The software components were tested item by item, including performance, and integrated and tested step by step to verify that all software met the requirements and related security standards. Determine the extent of all design measures and record the test results;

d) Write a test analysis report. For test cases that cannot be executed, explain the reasons and verify them through other auxiliary means;

e) Complete the software testing summary.

6.4.3.2 For software where problems are found during testing, regression testing should be performed after the software is modified.

6.4.4 Network Security Testing Network security testing shall be conducted in accordance with the provisions of GB/T 22239.

7.1 Hardware Maintenance

7.1.1 The hardware product inspection requirements are as follows:

a) The status of network equipment should be checked regularly and recorded. The interval between two checks should not exceed 90 days.

b) Any malfunctioning equipment should be replaced, but replacement should be avoided whenever possible during the launch vehicle's mission.

c) When changes are required to the configuration of hardware products, the corresponding approval process should be followed, and backups and records should be made.

d) Expired equipment should be replaced, or measures to extend its lifespan should be taken as required by the manufacturer.

7.1.2 Monitor the network connectivity, online status, traffic monitoring, and network security monitoring of all network devices.

7.1.3 The network security maintenance requirements are as follows:

a) Internet access devices should be regularly checked and disinfected using antivirus software or tools that meet the model requirements, and the results should be recorded;

b) Logs of network security devices and software should be checked regularly, and security-related issues should be addressed.

c) The operating system or firmware version of the internet access device should be upgraded regularly, or vulnerability patches should be installed.

7.2 Software Maintenance

7.2.1 The software update and upgrade requirements are as follows:

a) The version number of each software iteration should be clearly defined;

b) The changes made during each software update iteration should be recorded in the software version log;

c) Use software version management software to ensure that you can quickly revert to the original version when a new version becomes abnormal.

7.2.2 The software user access control requirements are as follows:

a) Assign accounts with corresponding permissions to software users according to their security level, profession, and user identity (whether they are administrators);

b) Users may only access files with a security level no higher than their account's password level;

c) Users can only access the applications corresponding to their account;

d) Only administrator accounts can modify software and application configurations;

e) Record the details of any changes to software or application configurations, including the time and account information.

7.3 File Maintenance Detailed management documents for the use, operation, and maintenance of the remote testing network should be developed, clearly defining management, operation, maintenance, and usage based on actual conditions. The organization and responsibilities of the remote testing network should be clearly defined, specifying authorized approval items, approval departments, and approvers. Management documents generally include.

a) Operation and maintenance management solution for remote test network of launch vehicles;

b) Implementation plan and details for the launch vehicle remote test network;

c) Troubleshooting Manual for Launch Vehicle Remote Test Network;