Test method and system for P2SP static networking

Abstract

The invention discloses a P2SP static networking test method and system, and the method comprises the steps: configuring a subscription relation tree of sub-current nodes in P2SP networking according to a to-be-used tool terminal after a background management end obtains the information of an available tool terminal, displaying the real-time data of each node in the subscription relation tree, and synchronizing the subscription relation tree to a server, the server side can store the corresponding static networking configuration data according to the subscription relation tree, and sends an updating instruction and the static networking configuration data to the corresponding tool terminal to be used; afterwards, the tool terminal to be used can update the static networking configuration item according to the update instruction and the static networking configuration data, and feeds back an update result to the server side and the background management side. In this way, the configuration information of each tool terminal can be updated through a method of constructing the static subscription relation tree, so that the effect of quickly completing static networking of P2SP is achieved, and meanwhile, a tester can efficiently obtain data information of each node in the networking.

Description

Technical Field

[0001] This invention relates to the technical field of software testing, and in particular to a testing method and system for P2SP static networking. Background Technology

[0002] With the widespread adoption of mobile internet, people can watch live streams anytime, anywhere via their mobile phones. The content is diverse, covering areas such as games, food, music, sports, and travel, comprehensively meeting user needs. In addition, live streaming platforms offer strong interactivity, allowing for interaction and comments between streamers and users, making live streaming a popular form of entertainment.

[0003] Among them, P2SP can complete mutual subscription between nodes according to certain rules, which greatly reduces the pressure on the server side. However, the growth of the user base also puts a great deal of downlink pressure on the service. Therefore, how to alleviate or eliminate downlink bandwidth pressure has become the primary problem that P2SP (Peer-to-Server and Peer) technology needs to solve.

[0004] Currently, P2SP network subscription relationships are dynamically constructed based on the actual QoS (Quality of Service) of the client. It is impossible to construct subscription relationships specifically. Dynamic networking can only be completed by multiple users entering to watch the live broadcast. Since a specified subscription relationship tree has not been constructed, the network needs to be reconstructed after the user exits the player. This wastes a lot of manpower and resources. Moreover, even with these manpower and resources, it is sometimes impossible to construct a scenario that meets the actual needs, making it difficult to execute and implement the testing work well.

[0005] Furthermore, P2SP live streaming networking is mainly based on multiple devices joining the same circle, which is a cumbersome and inefficient process. The P2SP live streaming service does not record the networking relationship of all nodes. The subscription relationship of each node needs to be determined independently through the logs of each node. Querying and analyzing the logs of each node to find the corresponding subscription relationship tree also suffers from the problems of being too complicated, error-prone, and time-consuming. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to provide a testing method and system for P2SP static networking, which can efficiently complete P2SP static networking and efficiently acquire data information of each node in the network.

[0007] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows:

[0008] A testing method for P2SP static networking includes the following steps:

[0009] The backend management terminal obtains the information of the terminal to be used, configures the subscription relationship tree of the sub-flow nodes in the P2SP network according to the terminal to be used, displays the real-time data of each node in the subscription relationship tree, and synchronizes the subscription relationship tree to the server.

[0010] The server stores the corresponding static network configuration data according to the subscription relationship tree, and sends the update command and the static network configuration data to the corresponding terminal to be used.

[0011] The terminal to be used updates the static network configuration items according to the update command and static network configuration data, and feeds back the update results to the server and the backend management terminal.

[0012] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows:

[0013] A test system for P2SP static networking includes:

[0014] The backend management terminal is used to obtain information about the terminal to be used, configure the subscription relationship tree of the sub-flow nodes in the P2SP network according to the terminal to be used, display the real-time data of each node in the subscription relationship tree, and synchronize the subscription relationship tree to the server.

[0015] The server is used to store the corresponding static network configuration data according to the subscription relationship tree, and send update instructions and the static network configuration data to the corresponding terminal to be used.

[0016] The terminal to be used is used to update the static network configuration items according to the update command and static network configuration data, and to feed back the update results to the server and the backend management terminal.

[0017] The beneficial effects of this invention are as follows: After the backend management terminal obtains information about available tool terminals, it displays the real-time data of each node in the subscription relationship tree of the sub-stream nodes in the P2SP network according to the subscription relationship tree configured on the tool terminal to be used, and synchronizes the subscription relationship tree to the server. The server can then store the corresponding static network configuration data according to the subscription relationship tree and send update instructions and the static network configuration data to the corresponding tool terminal to be used. Afterwards, the tool terminal to be used can update the static network configuration items according to the update instructions and the static network configuration data, and feed back the update results to the server and the backend management terminal. In this way, the configuration information of each tool terminal can be updated by constructing a static subscription relationship tree, so as to quickly complete the static networking effect of P2SP. At the same time, testers can efficiently obtain the data information of each node in the network, and thus understand the network status. Attached Figure Description

[0018] Figure 1 This is a flowchart illustrating a test method for P2SP static networking according to an embodiment of the present invention;

[0019] Figure 2 This is a flowchart illustrating the specific steps of a P2SP static networking test method according to an embodiment of the present invention.

[0020] Figure 3 This is an execution flowchart of the terminal tool to be used in a test method for P2SP static networking according to an embodiment of the present invention.

[0021] Figure 4 This is a schematic diagram of a test system for P2SP static networking according to an embodiment of the present invention. Detailed Implementation

[0022] To explain in detail the technical content, objectives, and effects of the present invention, the following description is provided in conjunction with the embodiments and accompanying drawings.

[0023] Please refer to Figure 1 This invention provides a testing method for P2SP static networking, including the following steps:

[0024] The backend management terminal obtains the information of the terminal to be used, configures the subscription relationship tree of the sub-flow nodes in the P2SP network according to the terminal to be used, displays the real-time data of each node in the subscription relationship tree, and synchronizes the subscription relationship tree to the server.

[0025] The server stores the corresponding static network configuration data according to the subscription relationship tree, and sends the update command and the static network configuration data to the corresponding terminal to be used.

[0026] The terminal to be used updates the static network configuration items according to the update command and static network configuration data, and feeds back the update results to the server and the backend management terminal.

[0027] As described above, the beneficial effects of this invention are as follows: After the backend management terminal obtains information about available tool terminals, it displays the real-time data of each node in the subscription relationship tree based on the subscription relationship tree of the sub-stream nodes in the P2SP network configured on the tool terminal to be used, and synchronizes the subscription relationship tree to the server. The server can then store the corresponding static network configuration data based on the subscription relationship tree and send update instructions and the static network configuration data to the corresponding tool terminal to be used. Afterward, the tool terminal to be used can update the static network configuration items according to the update instructions and the static network configuration data, and feed back the update results to the server and the backend management terminal. In this way, the configuration information of each tool terminal can be updated by constructing a static subscription relationship tree, so as to quickly complete the static networking effect of P2SP. At the same time, testers can efficiently obtain the data information of each node in the network, and thus understand the network status.

[0028] Further, the terminal to be used updates the static network configuration items according to the update command and static network configuration data, including:

[0029] When the terminal to be used receives the update instruction, it searches for the configuration information address of the subscription relationship tree of the P2SP network, and determines whether static network configuration data exists based on the configuration information address. If it exists, the terminal to be used performs static networking based on the static network configuration data; if it does not exist, the terminal to be used performs dynamic networking based on the static network configuration data.

[0030] As described above, the presence or absence of static network configuration data determines whether to perform dynamic or static networking. This method allows for the addition of static networking without affecting dynamic networking.

[0031] Further, the terminal to be used performs static networking based on the static networking configuration data, including:

[0032] The terminal to be used sequentially performs node registration, node acquisition, node removal, and IED hole punching between nodes, and sets the subscription nodes according to the static network configuration data.

[0033] As described above, the static networking process does not disrupt the original dynamic networking process. Instead, it inserts static networking configuration data into the final information of the subscribed nodes so that the sub-stream can be directly subscribed to the nodes with static configuration information, thereby achieving the purpose of static construction.

[0034] Furthermore, the update results will be fed back to the server and the backend management system, including:

[0035] After the terminal tool updates the static network configuration items, it performs log collection and subscription relationship collection, and obtains real-time sub-stream information by analyzing the collected subscription relationships;

[0036] By analyzing the collected logs, it is determined whether data with HOP level 1 or higher in the data stream subscribed to by the node is subscribed to P2P stream, and the subscription data judgment result is obtained;

[0037] The real-time substream information and the subscription data judgment result are fed back to the server and the backend management terminal.

[0038] As described above, by analyzing subscription relationships to obtain real-time sub-stream information, the system can manage data streams more accurately. By analyzing logs, the system can determine whether data with HOP (Hop Count) level 1 or higher in the data stream subscribed by a node is subscribed to a P2P stream. Combining real-time sub-stream information and subscription data judgment results can help testers understand the current network status of the tool terminal and improve the efficiency of server-side decision-making.

[0039] Furthermore, the tool terminal will send the update results back to the server and the backend management terminal, which also includes:

[0040] The server sends the real-time substream information and the subscription data judgment result to the backend management terminal;

[0041] The backend management terminal compares the real-time sub-stream information with the static network configuration data to obtain the subscription relationship comparison result of the static network;

[0042] The results of the subscription data judgment and the comparison results of the subscription relationship will be reported and displayed.

[0043] As described above, by comparing real-time substream information with static network configuration data, we can know the actual situation of changes in business data of each node during the networking and playback process in a real-time, concise, and efficient manner.

[0044] Please refer to Figure 4 Another embodiment of the present invention provides a testing system for P2SP static networking, comprising:

[0045] The backend management terminal is used to obtain information about the terminal to be used, configure the subscription relationship tree of the sub-flow nodes in the P2SP network according to the terminal to be used, display the real-time data of each node in the subscription relationship tree, and synchronize the subscription relationship tree to the server.

[0046] The server is used to store the corresponding static network configuration data according to the subscription relationship tree, and send update instructions and the static network configuration data to the corresponding terminal to be used.

[0047] The terminal to be used is used to update the static network configuration items according to the update command and static network configuration data, and to feed back the update results to the server and the backend management terminal.

[0048] As described above, the beneficial effects of this invention are as follows: After the backend management terminal obtains information about available tool terminals, it displays the real-time data of each node in the subscription relationship tree based on the subscription relationship tree of the sub-stream nodes in the P2SP network configured on the tool terminal to be used, and synchronizes the subscription relationship tree to the server. The server can then store the corresponding static network configuration data based on the subscription relationship tree and send update instructions and the static network configuration data to the corresponding tool terminal to be used. Afterward, the tool terminal to be used can update the static network configuration items according to the update instructions and the static network configuration data, and feed back the update results to the server and the backend management terminal. In this way, the configuration information of each tool terminal can be updated by constructing a static subscription relationship tree, so as to quickly complete the static networking effect of P2SP. At the same time, testers can efficiently obtain the data information of each node in the network, and thus understand the network status.

[0049] Further, the terminal to be used updates the static network configuration items according to the update command and static network configuration data, including:

[0050] When the terminal to be used receives the update instruction, it searches for the configuration information address of the subscription relationship tree of the P2SP network, and determines whether static network configuration data exists based on the configuration information address. If it exists, the terminal to be used performs static networking based on the static network configuration data; if it does not exist, the terminal to be used performs dynamic networking based on the static network configuration data.

[0051] As described above, the presence or absence of static network configuration data determines whether to perform dynamic or static networking. This method allows for the addition of static networking without affecting dynamic networking.

[0052] Further, the terminal to be used performs static networking based on the static networking configuration data, including:

[0053] The terminal to be used sequentially performs node registration, node acquisition, node removal, and IED hole punching between nodes, and sets the subscription nodes according to the static network configuration data.

[0054] As described above, the static networking process does not disrupt the original dynamic networking process. Instead, it inserts static networking configuration data into the final information of the subscribed nodes so that the sub-stream can be directly subscribed to the nodes with static configuration information, thereby achieving the purpose of static construction.

[0055] Furthermore, the update results will be fed back to the server and the backend management system, including:

[0056] After the terminal tool updates the static network configuration items, it performs log collection and subscription relationship collection, and obtains real-time sub-stream information by analyzing the collected subscription relationships;

[0057] By analyzing the collected logs, it is determined whether data with HOP level 1 or higher in the data stream subscribed to by the node is subscribed to P2P stream, and the subscription data judgment result is obtained;

[0058] The real-time substream information and the subscription data judgment result are fed back to the server and the backend management terminal.

[0059] As described above, by analyzing subscription relationships to obtain real-time sub-stream information, the system can manage data streams more accurately. By analyzing logs, the system can determine whether data with HOP level 1 or higher in the data stream subscribed by a node is subscribed to a P2P stream. Combining real-time sub-stream information and subscription data judgment results can help testers understand the current network status of the tool terminal and improve the efficiency of server-side decision-making.

[0060] Furthermore, the tool terminal will send the update results back to the server and the backend management terminal, which also includes:

[0061] The server sends the real-time substream information and the subscription data judgment result to the backend management terminal;

[0062] The backend management terminal compares the real-time sub-stream information with the static network configuration data to obtain the subscription relationship comparison result of the static network;

[0063] The results of the subscription data judgment and the comparison results of the subscription relationship will be reported and displayed.

[0064] As described above, by comparing real-time substream information with static network configuration data, we can know the actual situation of changes in business data of each node during the networking and playback process in a real-time, concise, and efficient manner.

[0065] The P2SP static networking test method and system described above are suitable for efficiently completing P2SP static networking and efficiently acquiring data information of each node in the network. The following is a detailed description of the implementation:

[0066] Example 1

[0067] Please refer to Figures 1 to 3 A testing method for P2SP static networking includes the following steps:

[0068] S1. The backend management terminal obtains the information of the terminal to be used, and configures the subscription relationship tree of the sub-flow nodes in the P2SP network according to the terminal to be used, displays the real-time data of each node in the subscription relationship tree, and synchronizes the subscription relationship tree to the server.

[0069] Specifically, the backend management terminal first needs to obtain the available tool terminals, i.e. the tool terminals to be used, and drag all the corresponding tool terminals to be used to the configuration area in the page for constructing the subscription relationship tree; then, configure the sub-stream nodes of the tool terminals to be used dragged to the configuration area, such as providing tool terminals PC1, PC2, and PC3, and then configuring PC3 to subscribe to sub-streams 0-4 of PC1, and PC3 to subscribe to sub-streams 5-9 of PC2. These subscription relationships can all be configured through the configuration area.

[0070] After configuring the subscription relationship tree on the backend management side, it is necessary to organize the subscription relationships of each terminal of the tool to be used, and upload the organized configuration information to the server so that the subscription relationship tree can be used directly for configuration in the future.

[0071] S2. The server stores the corresponding static network configuration data according to the subscription relationship tree, and sends the update command and the static network configuration data to the corresponding terminal to be used.

[0072] Specifically, the server uses a MySQL database to store data, including static network configuration data. This data primarily stores the node's own ID and substream subscription rule information. Only after storing this basic information can static networking be completed, allowing each node to know its own ID and which node to subscribe to. In some embodiments, static network configuration data may also include static network templates, enabling users to quickly create static networks using these templates.

[0073] S3. The terminal to be used updates the static network configuration items according to the update command and static network configuration data, and feeds back the update results to the server and the backend management terminal.

[0074] When the terminal to be used receives the update instruction, it searches for the configuration information address of the subscription relationship tree of the P2SP network, and determines whether static network configuration data exists based on the configuration information address. If it exists, the terminal to be used performs static networking based on the static network configuration data; if it does not exist, the terminal to be used performs dynamic networking based on the static network configuration data.

[0075] The terminal to be used performs static networking according to the static networking configuration data. Specifically, the terminal to be used performs node registration, node acquisition, node removal, and IED hole punching between nodes in sequence, and sets up subscription nodes according to the static networking configuration data.

[0076] In this embodiment, after receiving the update command, the terminal to be used first needs to find the configuration information address of the P2SP network. Only after finding the address can the subsequent update action be performed. After finding the configuration file, the content of the configuration file needs to be updated. Only after the configuration file is updated can the purpose of static networking be achieved. After the configuration update is completed, a feedback process is required so that both the server and the backend management terminal can reflect the real-time update status.

[0077] Specifically, after receiving the update command to start the P2SP network, the terminal to be used first needs to locate the product's startup directory and then complete the automated product startup process. This involves starting the product, authenticating the product, and entering the product's P2SP process.

[0078] After starting P2SP networking, if a node has not configured static networking data, it will directly undergo dynamic networking. Dynamic networking involves node registration, node acquisition, node removal (some nodes that do not meet the requirements for being subscribed to will be removed), and IED hole punching between nodes, ultimately acquiring an available subscription node and completing the corresponding substream subscription. If a node has received static networking configuration data, it will also undergo dynamic networking (the principle is not to break the dynamic networking process), but the static networking configuration data will be inserted into the final information of the subscription node so that it can directly subscribe to the substream from the node with static configuration information, achieving the purpose of static construction. If the subscription node cannot be found in a short time, it will retry to acquire it until it finally acquires a node (during this process, it will not look for other nodes to subscribe to; until the required node is found, it will subscribe to the CDN source stream). Afterwards, the P2SP function can be terminated directly through the terminal of the tool to be used.

[0079] After the terminal to be used updates the static network configuration items, it needs to collect logs and subscription relationships. By analyzing the collected subscription relationships, real-time sub-stream information is obtained. By analyzing the collected logs, it is determined whether data in the data stream subscribed by the node with a HOP (Hop Count, which refers to the process of a data packet being transferred to another network through a router or directly through a node) level 1 or higher is subscribed to a P2P stream, and the subscription data judgment result is obtained. Then, the real-time sub-stream information and the subscription data judgment result are fed back to the server and the backend management terminal.

[0080] Specifically, the terminal to be used needs to analyze the collected logs, analyze which nodes the nodes subscribe from, and use regular expressions to analyze which nodes the nodes subscribe to substream information from. After obtaining the data, it needs to report it to the server periodically. Analyze the collected logs to determine whether the data stream subscribed by the nodes conforms to the business logic. Under normal circumstances, HOPs of level 1 and above need to subscribe to P2P streams. At the same time, it also needs to report the content, status and other information executed by the terminal to be used.

[0081] S4. The server sends the real-time sub-stream information and the subscription data judgment result to the backend management terminal; the backend management terminal compares the real-time sub-stream information and the static network configuration data to obtain the subscription relationship comparison result of the static network; and reports and displays the subscription data judgment result and the subscription relationship comparison result.

[0082] Specifically, the server also needs to store the business data information reported by the nodes and the tool terminal node information; the business data information mainly stores the actual subscription information reported by the nodes, as well as whether the node player meets the P2SP business logic requirements, and can record the subscription direction, subscription level, and node playback data stream status of its own sub-stream; the tool terminal node information can record the IP matched by the endpoint node, the test account, and whether the terminal node is available.

[0083] After obtaining real-time substream information and subscription data judgment results, the backend management terminal can display the node data and subscription relationships of each P2SP. It can also compare the actual subscription relationship tree with the statically configured subscription relationship tree to see if they are consistent. Specifically, the main data displayed includes: the relationship between a node's subscription to other nodes' substreams (this clearly shows whether the static networking requirements are met); the relationship between a node's substreams and other nodes' subscriptions (this serves as supplementary data to verify if there are any business logic issues with subscription and being subscribed to); the subscription level (this reflects the P2SP level to which the node belongs, and whether the level meets the P2SP business requirements is immediately apparent without needing to query logs for each node); and whether the node is playing a source stream or a P2P stream (in static networking, levels with 2 or more HOPs should subscribe to P2P streams).

[0084] Furthermore, the front-end can use the RelationGraph module to draw the subscription relationships of each node, so as to compare them with the configuration in the static networking configuration module.

[0085] Furthermore, by summarizing the operational status of each node and determining whether P2SP conforms to the business process, it is possible to better reflect whether there are any anomalies in each node: to determine whether the P2SP node is operating normally, currently the main criterion is whether logs are generated; to determine whether the P2SP node's subscription to P2P conforms to the business logic, for levels above level 1, if there is subscription to source stream data, anomalies will also be reflected; and to obtain changes in the P2SP node's subscription process.

[0086] Example 2

[0087] This embodiment provides a specific application scenario for a P2SP static networking testing method based on Embodiment 1:

[0088] Scene 1:

[0089] As the project progresses towards productization, the complexity of the actual user subscription relationship tree often becomes quite high. The project requires testing scenarios with a 7-level HOP hierarchy. However, the existing resources and conditions cannot meet the verification requirements for this case. Therefore, building a 7-level HOP subscription relationship tree is a challenge.

[0090] Using the testing method in this embodiment, tester A only needs 7 terminals to complete the static networking construction of 7 levels of HOPs. The actual operation is as follows: in the static networking module of the backend management terminal, each terminal is adjusted to the subscription relationship of PC1→PC2→PC3→PC4→PC5→PC6→PC7. Then, this static configuration information is distributed to each tool terminal. The tool terminals can then complete the subscription from PC1 to PC2, and other devices complete the substream subscription according to the configuration, thereby achieving the construction of the target scenario.

[0091] Scene 2:

[0092] As the project progresses towards productization, the tester B, responsible for the P2SP module, wants to monitor the dynamic networking process, including node subscription to substreams, changes in subscribed substreams, and whether the playback of source streams and P2P streams conforms to business logic. In the existing test environment, it is difficult to analyze and provide feedback on the business data of each node in real time.

[0093] Using the testing method in this embodiment, tester B only needs to monitor the data reporting status of each terminal node in the backend management terminal to understand the actual situation of each service during the P2SP networking process. Actual operation: Start N tool terminals in the backend management terminal. These N terminals will periodically report substream subscription status and player playback status, which can be viewed in real time in the node data module of the backend management terminal.

[0094] Scene 3:

[0095] C, the tester responsible for the P2SP module, encountered a problem as the project progressed towards productization. The project wanted the P2SP network to be able to break through abnormal network conditions and, before re-establishing the network, return to the CDN stream for playback. Constructing abnormal network cases was not feasible in existing scenarios (or rather, building such cases required significant time investment to achieve even minimal results).

[0096] Using the testing method in this embodiment, tester C only needs to configure the abnormal organization tree in the static configuration module to achieve the abnormal networking required by the product, and at the same time complete the robustness test of the entire P2SP system after abnormal networking. Actual operation: PC1→PC2→PC1, establish a subscription ring network relationship, then have the terminal build the P2SP network, and observe how the subscription ring is broken and how the video is returned to the source stream for normal playback when subscription rings exist at each node.

[0097] Example 3

[0098] Please refer to Figure 4 A test system for P2SP static networking includes:

[0099] The backend management terminal is used to obtain information about the terminal to be used, configure the subscription relationship tree of the sub-flow nodes in the P2SP network according to the terminal to be used, display the real-time data of each node in the subscription relationship tree, and synchronize the subscription relationship tree to the server.

[0100] The server is used to store the corresponding static network configuration data according to the subscription relationship tree, and send update instructions and the static network configuration data to the corresponding terminal to be used.

[0101] The terminal to be used is used to update the static network configuration items according to the update command and static network configuration data, and to feed back the update results to the server and the backend management terminal.

[0102] The server primarily stores static network configuration data, business data reported by nodes, and tool terminal node information. It also provides APIs to the backend management system and the tool terminals to be used. The backend management system serves as the user's entry point to the static network system. It allows users to independently configure the P2SP for each node using the static network module and initiate the static network setup process for the terminal. After network setup is complete, the backend management system allows users to visually check whether the business logic of each node meets the P2SP requirements. The tool terminals are responsible for implementing the static network setup, receiving tasks from the backend management system, executing tasks, and performing a series of data collection and analysis tasks.

[0103] Specifically, the server primarily provides data storage and APIs for the backend management system. It mainly comprises a data storage module and an API module. A detailed description of each module is as follows:

[0104] Data storage module: Provides data storage for the entire system, currently using a MySQL database. The stored data includes static network configuration data, business data reported by nodes, and tool terminal node information. Static network information primarily stores the node's own ID and substream subscription rules. Only after storing this basic information can static networking be completed, allowing each node to know its own ID and which node it is subscribing to. Node business information mainly stores the actual subscription information reported by the node, and whether the node's player meets the P2SP business logic requirements. It can record the substream subscription path, subscription level, and the node's playback data stream status. Tool node information records the IP address matched by the endpoint node, the test account, and whether the terminal node is available.

[0105] API module: Primarily provided to the backend management end and the terminal of the tool to be used. The display of all business data on the backend management end requires business data to be provided based on the API, and the receiving and uploading of data by the terminal of the tool to be used also requires the support of the API module. Therefore, the API module in the server is the bridge connecting the various modules.

[0106] The backend management interface is a crucial component of the P2SP static networking testing method and system. This part provides a visual representation of the static network topology, and its main modules are: the static networking module, the node data module, and the node report module. A detailed description of each module is as follows:

[0107] The static networking module primarily configures the subscription relationship tree for P2SP networking and stores the corresponding configuration information on the server. First, it needs to acquire available terminal devices to be used, dragging all the corresponding terminal devices to the configuration area in the subscription relationship tree construction page. Second, it configures the sub-stream nodes for the terminal devices dragged to the configuration area. After configuring the subscription relationship tree, the backend management terminal needs to organize the subscription relationships of the terminal devices to be used and upload the organized configuration information to the server so that the subscription relationship tree configuration can be used directly later. The backend management terminal issues the configuration and starts the P2SP product. The product will perform dynamic networking (dynamic networking if no configuration information is received) or static networking (static networking if configuration information is received) based on the configuration items.

[0108] The node data module primarily displays the real-time node data and subscription relationships of each P2SP. It also allows comparison of the actual subscription relationship tree with the statically configured subscription relationship tree to ensure consistency. Key data displayed includes: the relationship between a node's subscriptions to other node substreams, the relationship between a node's substreams and other nodes' subscriptions, the subscription level, and whether a node is playing a source stream or a P2P stream. For statically configured networks, levels with two or more HOPs should subscribe to P2P streams. Based on the provided business data, the front-end can also use the RelationGraph module to draw the subscription relationships of each node for comparison with the configuration in the statically configured network module.

[0109] The node reporting module primarily summarizes the operational status of each node and whether the P2SP conforms to the business process, effectively identifying any anomalies in each node. Specifically, it demonstrates: whether the P2SP node is running normally, currently primarily based on log generation; whether the P2SP node's P2P subscription conforms to business logic, with anomalies also appearing for nodes at levels above level 1 if they are subscribing to source stream data; and changes in the P2SP node's subscription process, which requires periodic reporting to the server via the tool terminal, with the server system providing feedback to the reporting module.

[0110] The backend management terminal may also include a terminal data module: primarily providing the working status of the terminals to be used and indicating whether the terminals have received static networking information. The terminal data includes a section on terminal startup. During terminal startup, the server first identifies the static configuration information used for this startup and which terminals are involved. After obtaining the static configuration information and terminal devices, the server locates the corresponding terminals and updates their static configuration information. After starting the P2SP node, the terminals can then provide feedback on their working status and whether they have received configuration information.

[0111] The terminal tool to be used is the implementer of the static networking system and an important component of the system. Its modules include a network information update module, a P2SP start / stop module, and a data analysis and reporting module. A detailed description of each module is as follows:

[0112] The network information update module is primarily responsible for receiving update commands from the server and updating the product configuration items after receiving the commands and static configuration content. Specifically: Upon receiving the update command, it first needs to locate the configuration information address of the P2SP product; only after finding this address can subsequent update actions be performed. After locating the configuration file, it needs to update the configuration file content; only after updating the configuration file can the goal of static network topology be achieved. After completing the configuration update, a feedback process is required so that both the server and the backend management terminal can reflect the real-time update status.

[0113] Starting and stopping the P2SP module: This module is a step in starting the product. Only after the P2SP product is started can the subsequent static networking and dynamic networking processes take place. The specific process of starting and realizing the static networking of the product is as follows: After receiving the P2SP start command, it is first necessary to find the product's start directory and then complete the automated product start process. This involves starting the product, authenticating the product, and entering the product P2SP process. After starting the product's P2SP, if the node does not have a static configuration file, the corresponding node will directly undergo a dynamic networking process. The product's dynamic networking involves node registration, node acquisition, node removal (some nodes that do not meet the requirements for being subscribed to by others will be removed), and IED hole punching between nodes, etc., to finally obtain an available subscription node and then complete the corresponding substream subscription. If the node has received a static configuration file, the product will also perform dynamic networking accordingly (the principle is not to break the dynamic networking process), but insert our static configuration information into the information of the final subscription node so that it can directly subscribe to the substream from the node with the static configuration information to achieve the purpose of static building. If the subscription node cannot be found in a short time, the P2SP module will also retry to obtain it until the node is finally obtained (during the process, it will not look for other nodes to subscribe to; before finding the required node, it will subscribe to the CDN source stream). To end P2SP, the product's P2SP function can be directly terminated through the tool terminal to achieve the corresponding shutdown purpose.

[0114] Data Analysis and Reporting Module: This module serves as the final source of backend data, and all business data from the backend management terminal is the object of the tool's reporting. This mainly involves: analyzing collected logs, analyzing which nodes a node subscribes to (using regular expressions to determine which nodes a node subscribes to for substream information), and periodically reporting the acquired data to the server; analyzing collected logs to determine if the data streams subscribed to by nodes conform to business logic (normally, HOPs at level 1 and above need to subscribe to P2P streams); and reporting the content, status, and other information executed by the tool's terminal.

[0115] In summary, the present invention provides a testing method and system for P2SP static networking. After the backend management terminal obtains information about available tool terminals, it configures the subscription relationship tree of sub-flow nodes in the P2SP network according to the tool terminal to be used, displays the real-time data of each node in the subscription relationship tree, and synchronizes the subscription relationship tree to the server. The server can then store the corresponding static networking configuration data according to the subscription relationship tree and send update instructions and the static networking configuration data to the corresponding tool terminal to be used. Afterwards, the tool terminal to be used can update the static networking configuration items according to the update instructions and the static networking configuration data, and feed the update results back to the server. The server sends the real-time sub-flow information and subscription data judgment results to the backend management terminal. The backend management terminal compares the real-time sub-flow information and static networking configuration data to obtain the subscription relationship comparison result of the static networking. The subscription data judgment result and the subscription relationship comparison result are then reported and displayed. In this way, testers can quickly complete the static networking of P2SP (quickly complete the construction of a customized subscription tree); quickly verify whether the expected networking situation matches the actual networking situation; quickly start and stop the terminal system and quickly obtain the terminal status; know the actual situation of business data changes of each node during networking and playback in real time, simply and efficiently; and also construct abnormal networking situations to verify the overall robustness of P2SP.

[0116] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A test method for P2SP static group networking, characterized in that, The method comprises the steps of: The background management end obtains information of the tool terminal to be used, configures a subscription relationship tree of a sub-flow node in a P2SP network according to the tool terminal to be used, displays real-time data of each node in the subscription relationship tree, and synchronizes the subscription relationship tree to the service end; The service end stores corresponding static network configuration data according to the subscription relationship tree, and sends an update instruction and the static network configuration data to the corresponding tool terminal to be used; The tool terminal to be used updates a static network configuration item according to the update instruction and the static network configuration data, and feeds back the update result to the service end and the background management end.

2. The method of claim 1, wherein the P2SP static group networking test method is characterized by, The tool terminal to be used updates a static network configuration item according to the update instruction and the static network configuration data, and feeds back the update result to the service end and the background management end. When the tool terminal to be used receives the update instruction, the tool terminal to be used finds a configuration information address of the subscription relationship tree of the P2SP network, judges whether there is static network configuration data according to the configuration information address, if there is, the tool terminal to be used performs static network configuration according to the static network configuration data, and if there is not, the tool terminal to be used performs dynamic network configuration according to the static network configuration data.

3. The method of claim 2, wherein the P2SP static networking test method is characterized by, The tool terminal to be used performs static network configuration according to the static network configuration data, which comprises: The tool terminal to be used performs node registration, node acquisition, node elimination and IED hole punching in sequence, and sets a subscription node according to the static network configuration data.

4. The method of claim 1, wherein the P2SP static group networking test method is characterized by, The tool terminal to be used performs log collection and subscription relationship collection after updating the static network configuration item, obtains real-time sub-flow information by analyzing the collected subscription relationship; The tool terminal to be used judges whether data whose HOP is above level 1 in a data stream subscribed by a node subscribes a P2P stream by analyzing the collected log, and obtains a subscription data judgment result; The tool terminal to be used feeds back the real-time sub-flow information and the subscription data judgment result to the service end and the background management end. The tool terminal to be used feeds back the real-time sub-flow information and the subscription data judgment result to the service end and the background management end.

5. The method of claim 4, wherein the P2SP static group networking test method is characterized by, The service end sends the real-time sub-flow information and the subscription data judgment result to the background management end; The background management end compares the real-time sub-flow information and the static network configuration data to obtain a subscription relationship comparison result of static network configuration; The subscription data judgment result and the subscription relationship comparison result are reported and displayed. The method comprises:

6. A test system for P2SP static networking, characterized in that, The background management end is used for obtaining information of the tool terminal to be used, configuring a subscription relationship tree of a sub-flow node in a P2SP network according to the tool terminal to be used, displaying real-time data of each node in the subscription relationship tree, and synchronizing the subscription relationship tree to the service end; The service end is used for storing corresponding static network configuration data according to the subscription relationship tree, and sending an update instruction and the static network configuration data to the corresponding tool terminal to be used; The tool terminal to be used is used for updating a static network configuration item according to the update instruction and the static network configuration data, and feeding back the update result to the service end and the background management end. ​ 7. The test system of claim 6, wherein the P2SP static networking is a P2P static networking. The updating of the static networking configuration item by the to-be-used tool terminal according to the update instruction and the static networking configuration data comprises: When the to-be-used tool terminal receives the update instruction, the to-be-used tool terminal searches for the configuration information address of the subscription relationship tree of the P2SP networking, judges whether there is static networking configuration data according to the configuration information address, if there is, the to-be-used tool terminal performs static networking according to the static networking configuration data, if not, the to-be-used tool terminal performs dynamic networking according to the static networking configuration data.

8. The test system of claim 7, wherein the P2SP static networking is a P2P network. The static networking performed by the to-be-used tool terminal according to the static networking configuration data comprises: The to-be-used tool terminal sequentially performs node registration, node acquisition, node elimination and IED hole punching between nodes, and sets a subscription node according to the static networking configuration data.

9. The test system of claim 6, wherein the P2SP static networking is a P2P network. The update result is fed back to the service end and the background management end, comprising: After the to-be-used tool terminal updates the static networking configuration item, the to-be-used tool terminal collects logs and subscription relationship, and obtains real-time sub-flow information by analyzing the collected subscription relationship; By analyzing the collected logs, it is judged whether the data whose HOP is above level 1 in the data stream subscribed by the node subscribes to P2P flow, and a subscription data judgment result is obtained; The real-time sub-flow information and the subscription data judgment result are fed back to the service end and the background management end.

10. The test system of claim 9, wherein, The to-be-used tool terminal feeds back the update result to the service end and the background management end, further comprising: The service end sends the real-time sub-flow information and the subscription data judgment result to the background management end; The background management end compares the real-time sub-flow information and the static networking configuration data to obtain a subscription relationship comparison result of static networking; The subscription data judgment result and the subscription relationship comparison result are reported and displayed.

Images