CN114866442A - 8583 protocol-based cross-virtual service session holding test method and device - Google Patents
8583 protocol-based cross-virtual service session holding test method and device Download PDFInfo
- Publication number
- CN114866442A CN114866442A CN202210609226.6A CN202210609226A CN114866442A CN 114866442 A CN114866442 A CN 114866442A CN 202210609226 A CN202210609226 A CN 202210609226A CN 114866442 A CN114866442 A CN 114866442A
- Authority
- CN
- China
- Prior art keywords
- client
- message
- server
- service
- virtual service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/26—Special purpose or proprietary protocols or architectures
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Environmental & Geological Engineering (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Debugging And Monitoring (AREA)
- Computer And Data Communications (AREA)
Abstract
The present disclosure relates to a test method and device for cross-virtual service session maintenance based on 8583 protocol, comprising: configuring a first virtual service and a second virtual service, wherein the first virtual service is used for receiving 8583 messages sent by a client and client service access, and the second virtual service is used for receiving server requests sent by a real server and server service access; 8583 message automatic generation step; a client request initiating step; a client service access monitoring step; recording a client service access result; a server receives a message; a server request initiating step; monitoring server service access; recording a server service access result; a step of receiving a message by a client; a client detection step; and repeating the steps from the 8583 message automatic generation step to the client detection step until the test end condition is met, wherein in the 8583 message automatic generation step, the 8583 message in the automatically generated standard format is randomly converted.
Description
Technical Field
The present disclosure relates to the field of testing technologies, and in particular, to a method and an apparatus for testing across virtual service session maintenance based on 8583 protocol.
Background
The ISO8583 message (also called 8583 message) is an international standard packet format, which is composed of 128 field fields at most, each field has a uniform specification and has a fixed length and a variable length. The application development of the POS is often implemented by means of 8583 messages, for example, the application of a member management system of a returning customer on the POS.
The cross-virtual service session maintenance based on the 8583 protocol is a session maintenance mode of load balancing equipment, and aims to realize that 8583 messages sent by the same client are connected and separated through the load balancing equipment, the load is distributed to a background server, and when the server sends received data to the client, the load balancing loads the service to the same client. Namely, the load balancing device performs connection and disconnection according to the length identifier in the client request message, the load is distributed to the background server, and when the background server initiates a request to the client, the session is maintained according to the domain characteristics in the 8583 message. More specifically, when a client initiates a service access based on the 8583 protocol, the load balancing device performs accurate splitting according to the length identifier in the message, and distributes the load to the background server according to a preset load balancing algorithm; the background server sends the received data message back to the client, the load is very large, the device accurately positions the client according to the characteristics of different domains in the server request message, session maintenance is carried out according to the information, and all the data sent by the same client can be returned to the client.
As one of the important functions of load balancing devices, cross virtual service session maintenance based on 8583 protocol is widely applied in the financial industry. In an actual use environment, various networking environments and service flows can be encountered, so that testers can be required to fully simulate various networking environments and service flows, different networking is built to simulate different service flows, the progress of a test can be seriously delayed, and the test kept by crossing virtual service sessions based on the 8583 protocol occupies a relatively long test time to influence the test progress of a project. More specifically, when testing the cross-virtual service session maintenance based on the 8583 protocol, a tester needs to simulate a plurality of clients, simulate and construct data messages with different identifier lengths and different contents, test whether the load device is correctly split according to the identifier lengths, and test whether the session maintenance is correctly performed according to the domain characteristics. In the testing process, the tester needs to frequently and manually modify the data content, and manually calculate whether the split message is correct or not to confirm whether the service access is normal or not. When a plurality of devices are needed, the manual construction of the data message is extremely complicated and is easy to cause errors, the manual calculation of the message splitting result is easy to cause large errors, and when environmental problems and calculation errors occur, the test progress is greatly influenced, and further the progress of the whole project is influenced.
Therefore, there is a need for an automated 8583 protocol-based cross-virtual service session hold testing method and apparatus.
Disclosure of Invention
In view of the above, the present disclosure provides a method and an apparatus for testing across virtual service session maintenance based on 8583 protocol.
According to an aspect of the present disclosure, a method for testing across virtual service session maintenance based on 8583 protocol is provided, the method comprising: configuring a first virtual service and a second virtual service, wherein the first virtual service is used for receiving a 8583 message and a client service access sent by a client through long connection, the client service access comprises splitting the 8583 message received by the client according to a length identifier of the 8583 message and carrying out load distribution on the split 8583 request message based on a load balancing strategy, a real service address of the first virtual service is an IP address of a server, the second virtual service is used for receiving a server request and a server service access sent by the real server, the server service access comprises session maintenance according to characteristics of the 8583 message received by the server service access, and a real service address of the second virtual service is an IP address of the client; an 8583 message automatic generation step, namely setting 8583 message length identification, judging whether the 8583 message length identification is correct or not, and automatically generating an 8583 message in a standard format based on an 8583 protocol and the 8583 message length identification when the result of judging whether the 8583 message length identification is correct is 'yes'; a client request initiating step, in which a simulation client initiates a client request to the first virtual service, and the content of the client request is the generated 8583 message; a client service access monitoring step, namely monitoring whether the client service access initiated by the client request to the first virtual service is normal or not; a client service access result recording step, in which when the result of monitoring whether the client service access initiated by the client request to the first virtual service is normal is yes, a splitting result of the first virtual service for splitting the 8583 message and a distribution result of load distribution of the split 8583 message based on a load balancing strategy are recorded; a step of receiving a message by a server, namely receiving 8583 messages by an analog server, and recording and printing data received by the server; a server request initiating step, in which a simulation server initiates a server request to the second virtual service, wherein the content of the server request is the 8583 message received by the simulation server; a server service access monitoring step, namely monitoring whether the server service access initiated by the server request to the second virtual service is normal or not; a server service access result recording step, in which when the result of monitoring whether the server service access initiated by the server request to the second virtual service is normal is yes, a session holding result of the second virtual service for holding the session according to the characteristics of the received 8583 message is recorded; a step of receiving a message by a client, namely simulating the client to receive an 8583 message and automatically comparing the received 8583 message with a 8583 message sent by the client; a client detection step, namely judging whether the 8583 message received by the client is the same as the 8583 message sent by the client, judging that the test is successful when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is yes, recording and printing the 8583 message received by the client and displaying that the test is successful; and repeating the 8583 message automatic generation step, the client request initiation step, the client service access monitoring step, the client service access result recording step, the server message receiving step, the server request initiation step, the server service access monitoring step, the server service access result recording step, the client message receiving step and the client detection step until the test is completed, wherein in the 8583 message automatic generation step, the 8583 message in the automatically generated standard format is randomly transformed so as to verify the robustness of cross-virtual service session maintenance based on the 8583 protocol.
The test method for cross-virtual service session maintenance based on 8583 protocol according to the present disclosure further comprises: in the step of automatically generating the 8583 message, when the result of judging whether the 8583 message length identifier is correct is 'no', recording the 8583 message length identifier error and terminating the test.
The test method for cross-virtual service session maintenance based on 8583 protocol according to the present disclosure further comprises: in the client service access monitoring step, when the result of monitoring whether the client service access initiated by the client request to the first virtual service is normal is 'no', recording the client service access abnormity and terminating the test.
The test method for cross-virtual service session maintenance based on 8583 protocol according to the present disclosure further comprises: in the step of recording the server service access result, when the result of monitoring whether the server service access initiated by the server request to the second virtual service is normal is 'no', recording the server service access exception and terminating the test.
The test method for cross-virtual service session maintenance based on 8583 protocol according to the present disclosure further comprises: in the client detection step, when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is 'no', recording the abnormal comparison and terminating the test.
According to another aspect of the present disclosure, a testing apparatus for cross virtual service session maintenance based on 8583 protocol is proposed, the apparatus comprising: the virtual service configuration component is used for configuring a first virtual service and a second virtual service, the first virtual service is used for receiving a 8583 message and a client service access which are sent by a client through long connection, the client service access comprises splitting the 8583 message received by the client according to the length identification of the 8583 message and carrying out load distribution on the split 8583 request message based on a load balancing strategy, the real service address of the first virtual service is the IP address of a server, the second virtual service is used for receiving a server request and a server service access sent by the real server, the server service access comprises session maintenance according to the characteristics of the 8583 message received by the server, and the real service address of the second virtual service is the IP address of the client; an 8583 message automatic generation component, configured to set a 8583 message length identifier, determine whether the 8583 message length identifier is correct, and automatically generate an 8583 message in a standard format based on a 8583 protocol and the 8583 message length identifier when a result of determining whether the 8583 message length identifier is correct is "yes"; a client request initiating component, configured to simulate a client to initiate a client request to the first virtual service, where content of the client request is the generated 8583 packet; the client business access monitoring component is used for monitoring whether the client business access initiated by the client request to the first virtual service is normal or not; a client service access result recording component, configured to record, when a result of monitoring whether a client service access initiated by the client request to the first virtual service is normal is yes, a splitting result of the first virtual service for splitting the 8583 message and a distribution result of load distribution of the split 8583 message based on a load balancing policy; the server receiving message component is used for simulating the server to receive 8583 messages and recording and printing data received by the server; a server request initiating component, configured to initiate a server request for the second virtual service by a simulation server, where content of the server request is a 8583 message received by the simulation server; the server service access monitoring component is used for monitoring whether the server service access initiated by the server request to the second virtual service is normal or not; a server service access result recording component, configured to record, when a result of monitoring whether server service access initiated by the server request to the second virtual service is normal is yes, a session holding result of the second virtual service for performing session holding according to characteristics of a 8583 message received by the second virtual service; the client receives the message assembly, is used for simulating the client to receive the 8583 message, and automatically compares the received 8583 message with the 8583 message sent by the client; the client detection component is used for judging whether the 8583 message received by the client is the same as the 8583 message sent by the client, judging that the test is successful when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is yes, recording and printing the 8583 message received by the client and displaying that the test is successful; and the circulating component is used for repeatedly calling the 8583 message automatic generation component, the client request initiation component, the client service access monitoring component, the client service access result recording component, the server message receiving component, the server request initiation component, the server service access monitoring component, the server service access result recording component, the client message receiving component and the client detection component until the test is completed, wherein in the 8583 message automatic generation component, an 8583 message in a standard format which is automatically generated is randomly transformed so as to verify the robustness of cross-virtual service session maintenance based on the 8583 protocol.
The 8583 protocol-based cross-virtual service session maintenance testing apparatus according to the present disclosure, wherein the 8583 message automatic generation component is further configured to: and when the result of judging whether the 8583 message length identification is correct is 'no', recording the 8583 message length identification error and terminating the test.
A 8583 protocol-based cross virtual service session hold testing apparatus according to the present disclosure, wherein the client traffic access monitoring component is further configured to: and when the result of monitoring whether the client service access initiated by the client request to the first virtual service is normal is 'no', recording the client service access abnormity and terminating the test.
A 8583 protocol-based cross virtual service session hold testing apparatus according to the present disclosure, wherein the server traffic access monitoring component is further configured to: and when the result of monitoring whether the server service access initiated by the second virtual service is normal is 'no', recording the server service access abnormity and terminating the test.
A 8583 protocol-based cross virtual service session hold testing apparatus according to the present disclosure, wherein the client detection component is further configured to: and when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is negative, recording the abnormal comparison and terminating the test.
In summary, the 8583 protocol-based cross-virtual service session maintenance test method and device can automatically construct 8583 messages according to requirements, can simulate the request behaviors of a client and a server and automatically perform service access, and can automatically calculate the data message splitting result and the session maintenance result. Specifically, the method comprises the steps of automatically generating a data message in a standard 8583 protocol format, automatically circularly simulating 8583 data requests and updating data contents in a random machine; and automatically calculating the data message splitting result. On the basis of ensuring the test result and the test efficiency, the workload of testers is saved, and the stable operation of the project is ensured.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The above and other objects, features and advantages of the present application will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings. The drawings described below are only some embodiments of the present application, and other drawings may be derived from those drawings by those skilled in the art without inventive effort.
Fig. 1 is a schematic flow chart illustrating a test method for cross virtual service session maintenance based on 8583 protocol according to an embodiment of the present disclosure.
Fig. 2 is a schematic diagram illustrating a specific flow of testing a client request in a testing method for maintaining across virtual service sessions based on 8583 protocol according to an embodiment of the present disclosure.
Fig. 3 is a schematic diagram illustrating a specific flow of a request test for a server in a test method for maintaining across virtual service sessions based on 8583 protocol according to an embodiment of the present disclosure.
FIG. 4 is a schematic diagram illustrating a testing apparatus held across virtual service sessions based on the 8583 protocol according to an embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, systems, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
It is to be understood by those skilled in the art that the drawings are merely schematic representations of exemplary embodiments, and that the blocks or processes shown in the drawings are not necessarily required to practice the present disclosure and are, therefore, not intended to limit the scope of the present disclosure.
According to the test method and device for cross-virtual service session maintenance based on the 8583 protocol, an 8583 data message is automatically sent according to the using principle of the 8583 protocol, and whether the cross-virtual service session maintenance service based on the 8583 protocol on the load balancing equipment is normal or not is tested, and the test result is automatically recorded.
Fig. 1 is a schematic flow chart illustrating a test method for cross virtual service session maintenance based on 8583 protocol according to an embodiment of the present disclosure.
As shown in fig. 1, in step S102, a first virtual service and a second virtual service are configured, where the first virtual service is configured to receive an 8583 message sent by a client through long connection and a client service access, the client service access includes splitting the 8583 message received by the client according to a length identifier of the 8583 message and performing load distribution on the split 8583 request message based on a load balancing policy, a real service address of the first virtual service is an IP address of a server, and the second virtual service is configured to receive a server request and a server service access sent by a real server, the server service access includes session maintenance according to characteristics of the 8583 message received by the server service access, and a real service address of the second virtual service is an IP address of the client.
More specifically, the following configuration is made in the load balancing apparatus:
s1, configure client → server side to VIP1, configure real service (real service address is server side IP address).
S2, configure server → client direction VIP2, configure real service (real service address is client IP address).
S3, the connection splitting function is started, 8583 message length identification length and offset bits are specified, and the client-side → server-side direction VIP1 refers to the strategy.
S4, open the function of maintaining across virtual service sessions based on the 8583 protocol, the server → client direction referring to the VIP2 for the policy.
In step S104, an 8583 message automatic generation step, which sets a 8583 message length identifier, determines whether the 8583 message length identifier is correct, and automatically generates an 8583 message in a standard format based on the 8583 protocol and the 8583 message length identifier when the result of determining whether the 8583 message length identifier is correct is "yes". After the configuration from S1 to S4 is completed in the load balancing device, the specified 8583 message length identifier is input, a data message in the standard 8583 format is automatically generated, whether the 8583 message length identifier is input incorrectly is judged, and the next step is continuously executed under the condition that the 8583 message length identifier is input correctly.
In step S106, a client request initiating step, where a simulation client initiates a client request to the first virtual service, and the content of the client request is the generated 8583 packet.
In step S108, a client service access monitoring step of monitoring whether the client service access initiated by the client request to the first virtual service is normal.
In step S110, a step of recording a client service access result, in which when the result of monitoring whether the client service access initiated by the client request to the first virtual service is normal is yes, a splitting result of splitting the 8583 packet by the first virtual service and a distribution result of load distribution of the split 8583 packet based on a load balancing policy are recorded.
Namely, in step S106, step S108 and step S110, the client-initiated request is simulated, the request content of the client-initiated request is an automatically generated 8583 message, whether the service access to the client-initiated request is normal or not is monitored, and the next step is continued when the service access to the client-initiated request is normal.
In step S112, the server receives the message step, and the simulation server receives 8583 the message, records and prints the data received by the server. Namely, the simulation server receives the message, records and prints the received data.
In step S114, a server request initiating step, where the simulation server initiates a server request for the second virtual service, and the content of the server request is the 8583 message received by the simulation server.
In step S116, a server service access monitoring step of monitoring whether the server service access initiated by the server request to the second virtual service is normal.
In step S118, a server service access result recording step, when the result of monitoring whether the server service access initiated by the server request to the second virtual service is normal is yes, recording a session holding result that the second virtual service holds a session according to the characteristics of the 8583 message received by the second virtual service.
Namely, in step S114, step S116 and step S118, the simulation server initiates a request, the request content of which is the received data message, and monitors whether the service access to the server initiated request is normal, and continues to execute the next step in case the service access to the server initiated request is normal.
In step S120, the client receives the message, and the simulation client receives the 8583 message and automatically compares the received 8583 message with the 8583 message sent by the simulation client.
In step S122, the client detects whether the 8583 message received by the client is the same as the 8583 message sent by the client, and when the result of determining whether the 8583 message received by the client is the same as the 8583 message sent by the client is "yes", the client determines that the test is successful, records and prints the 8583 message received by the client, and displays that the test is successful.
That is, in step S120 and step S122, the simulation client receives the message, automatically compares whether the comparison data is consistent with the transmission data, records and prints the received data when the comparison data is consistent, and displays the test result.
In step S124, it is determined whether to terminate the test, and the test is terminated when the result of the determination of whether to terminate the test is yes.
When the step S124 determines that the result of whether to terminate the test is "no", the 8583 message automatic generation step S104, the client request initiation step S106, the client service access monitoring step S108, the client service access result recording step S110, the server message receiving step S112, the server request initiation step S114, the server service access monitoring step S116, the server service access result recording step S118, the client message receiving step S120, and the client detection step S122 are repeated until the test is completed, wherein in the 8583 message automatic generation step S104, the 8583 message in the standard format that is automatically generated is randomly transformed to verify the robustness of the 8583 protocol across virtual service sessions. That is, steps S104 to S122 are executed in a loop until the test termination condition is satisfied, and during the process of executing the test steps in a loop, the message content of the 8583 message generated in step S104 is randomly changed each time, so as to verify the robustness of the cross-virtual service session based on the 8583 protocol.
The test method for cross-virtual service session maintenance based on the 8583 protocol according to the embodiment of the disclosure further comprises the following steps: in the step of automatically generating the 8583 message, when the result of judging whether the 8583 message length identifier is correct is 'no', recording the 8583 message length identifier error and terminating the test. Namely, when the inputted 8583 message length identification is not equal to the preset 8583 message length identification, recording the abnormity and stopping the test process.
The test method for cross-virtual service session maintenance based on 8583 protocol according to the embodiment of the present disclosure further includes: in the client service access monitoring step, when the result of monitoring whether the client service access initiated by the client request to the first virtual service is normal is 'no', recording the client service access abnormity and terminating the test. Namely, under the condition that the service access of the request initiated by the client is monitored to be abnormal, the abnormality is recorded and the test process is stopped.
The test method for cross-virtual service session maintenance based on 8583 protocol according to the embodiment of the present disclosure further includes: in the step of recording the server service access result, when the result of monitoring whether the server service access initiated by the server request to the second virtual service is normal is 'no', recording the server service access exception and terminating the test. Namely, under the condition that the service access of the request initiated by the server is monitored to be abnormal, the abnormality is recorded and the test process is stopped.
The test method for cross-virtual service session maintenance based on 8583 protocol according to the embodiment of the present disclosure further includes: in the client detection step, when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is 'no', recording the abnormal comparison and terminating the test. Namely, when the comparison data are judged to be inconsistent, recording the abnormity and stopping the test process.
Fig. 2 is a schematic diagram illustrating a specific flow of testing a client request in a testing method for maintaining across virtual service sessions based on 8583 protocol according to an embodiment of the present disclosure.
As shown in fig. 2, in step S202, a message length identifier is input.
In step S204, it is determined whether the message length identifier is correctly input.
If it is determined in step S204 that the result of the message length indicator input is correct is yes, the process proceeds to step S206. In step S206, an 8583 message is generated.
In step S208, the client request is simulated.
In step S210, it is determined whether the connection splitting result is correct.
If it is determined in step S210 that the result of the connection/disconnection result is correct is yes, the process proceeds to step S212. In step S212, it is determined whether the monitoring service is normal.
If the result of determining whether the monitoring service is normal in step S212 is yes, the process proceeds to step S214. In step S214, the server prints the reception information. And then, ending the test process of the client request.
If the result of determining whether the message length identifier is correctly input in step S204 is "no", the process proceeds to step S216. In step S216, the message length identification error information is recorded. And then, ending the test process of the client request.
If the result of determining whether the message length identifier is correctly input is yes in step S204 and if the result of determining whether the connection/disconnection result is correct is no in step S210, the process proceeds to step S218. In step S218, split exception information is recorded. And then, ending the test process of the client request.
If the result of determining whether the message length identifier is correctly input is yes in step S204, if the result of determining whether the connection and splitting result is correct is yes in step S210, and if the result of determining whether the monitoring service is normal is no in step S212, the process proceeds to step S220. In step S220, service access exception information is recorded. And then, ending the test process of the client request.
Fig. 3 is a schematic diagram illustrating a specific flow of a request test for a server in a test method for maintaining across virtual service sessions based on 8583 protocol according to an embodiment of the present disclosure.
As shown in fig. 3, in step S302, a server request is simulated.
In step S304, it is determined whether the monitoring service is normal.
If the result of determining whether the monitoring service is normal in step S304 is yes, the process proceeds to step S306. In step S306, it is determined whether the monitoring service is normal.
If the result of determining whether the monitoring service is normal in step S306 is yes, the process proceeds to step S308. In step S308, the session maintenance result is recorded.
In step S310, the client prints the reception information. Thereafter, the test procedure for the server request is ended.
If the result of determining whether the monitoring service is normal in step S304 is "no", the process proceeds to step S312. In step S312, service access exception information is recorded. Thereafter, the test procedure for the server request is ended.
If the result of determining whether the monitored traffic is normal is yes in step S304 and if the result of determining whether the monitored traffic is normal is no in step S306, the process proceeds to step S314. In step S314, service access exception information is recorded. Thereafter, the test procedure for the server request is ended.
FIG. 4 is a schematic diagram illustrating a testing apparatus held across virtual service sessions based on the 8583 protocol according to an embodiment of the present disclosure. As shown in fig. 4, the apparatus includes:
a virtual service configuration component 402, configured to configure a first virtual service and a second virtual service, where the first virtual service is configured to receive an 8583 message and a client service access sent by a client through long connection, the client service access includes splitting the 8583 message received by the client according to a length identifier of the 8583 message and performing load distribution on the split 8583 request message based on a load balancing policy, a real service address of the first virtual service is an IP address of a server, and the second virtual service is configured to receive a server request and a server service access sent by the real server, the server service access includes session maintenance performed according to characteristics of the 8583 message received by the server service access, and a real service address of the second virtual service is an IP address of the client;
an 8583 message automatic generation component 404, configured to set a 8583 message length identifier, determine whether the 8583 message length identifier is correct, and automatically generate a 8583 message in a standard format based on a 8583 protocol and the 8583 message length identifier when the result of determining whether the 8583 message length identifier is correct is "yes";
a client request initiating component 406, configured to simulate a client to initiate a client request to the first virtual service, where content of the client request is the generated 8583 packet;
a client service access monitoring component 408, configured to monitor whether a client service access initiated by the client request to the first virtual service is normal;
a client service access result recording component 410, configured to record, when a result of monitoring whether the client service access initiated by the client request to the first virtual service is normal is yes, a splitting result of the first virtual service for splitting the 8583 message and a distribution result of load distribution of the split 8583 message based on a load balancing policy;
the server receiving message component 412 is used for simulating the server receiving 8583 message, and recording and printing the data received by the server;
a server request initiating component 414, configured to initiate a server request for the second virtual service by a simulation server, where content of the server request is a 8583 message received by the simulation server;
a server service access monitoring component 416, configured to monitor whether a server service access initiated by the server request to the second virtual service is normal;
a server service access result recording component 418, configured to record, when a result of monitoring whether the server service access initiated by the server request to the second virtual service is normal is yes, a session holding result of the second virtual service for performing session holding according to characteristics of the 8583 message received by the second virtual service;
the client receiving message component 420 is configured to simulate the client receiving 8583 message, and automatically compare the received 8583 message with the 8583 message sent by the client;
the client detection component 422 is used for judging whether the 8583 message received by the client is the same as the 8583 message sent by the client, judging that the test is successful when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is yes, recording and printing the 8583 message received by the client and displaying that the test is successful;
and a loop component 424, configured to repeatedly call the 8583 message automatic generation component, the client request initiation component, the client service access monitoring component, the client service access result recording component, the server message receiving component, the server request initiation component, the server service access monitoring component, the server service access result recording component, the client message receiving component, and the client detection component until the test is completed, where in the 8583 message automatic generation component, an 8583 message in an automatically generated standard format is randomly transformed to verify robustness of cross-virtual service session based on the 8583 protocol.
The 8583 protocol-based cross-virtual service session maintaining test apparatus according to the embodiment of the present disclosure, wherein the 8583 message automatic generation component 404 is further configured to: and when the result of judging whether the 8583 message length identification is correct is 'no', recording the 8583 message length identification error and terminating the test.
The 8583 protocol-based cross virtual service session maintenance testing apparatus according to an embodiment of the present disclosure, wherein the client service access monitoring component 408 is further configured to: and when the result of monitoring whether the client service access initiated by the client request to the first virtual service is normal is 'no', recording the client service access abnormity and terminating the test.
The 8583 protocol-based cross virtual service session maintenance testing apparatus according to the embodiment of the present disclosure, wherein the server traffic access monitoring component 416 is further configured to: and when the result of monitoring whether the server service access initiated by the second virtual service is normal is 'no', recording the server service access abnormity and terminating the test.
A 8583 protocol-based cross virtual service session hold test apparatus according to an embodiment of the present disclosure, wherein the client detection component 422 is further configured to: and when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is negative, recording the abnormal comparison and terminating the test.
In summary, the 8583 protocol-based cross-virtual service session maintenance test method and device can automatically construct 8583 messages according to requirements, can simulate the request behaviors of a client and a server and automatically perform service access, and can automatically calculate the data message splitting result and the session maintenance result. Specifically, the method comprises the steps of automatically generating a data message in a standard 8583 protocol format, automatically circularly simulating 8583 data requests and updating data contents in a random machine; and automatically calculating the data message splitting result. On the basis of ensuring the test result and the test efficiency, the workload of the tester is saved, and the stable operation of the project is ensured.
Generally, in the prior art, when a test is performed, multiple devices are needed, manually constructing a data message is extremely complicated and is easy to cause errors, a manually calculating message splitting result is easy to cause large errors, and when environmental problems and calculation errors occur, the test progress is greatly influenced, and then the progress of the whole project is influenced. Therefore, the 8583 message is automatically constructed according to the requirement, the request behaviors of the client and the server can be simulated, the service access is automatically carried out, and the data message splitting result and the session holding result can be automatically calculated. Therefore, in particular, the present disclosure automatically sends 8583 data messages according to the use principle of the 8583 protocol, tests whether the service is normal, and automatically records the test result. Firstly, inputting a specified message length mark, automatically generating a data message in a standard 8583 format, recording abnormal stop when the length mark is input incorrectly, and otherwise, continuously executing the next step. And then, the simulation client initiates a request, the request content is an automatically generated 8583 message, whether the service access is normal or not is monitored, if the access is abnormal, the abnormal stop is recorded, otherwise, the connection splitting result and the load distribution result are recorded, and the next step is continued. Then, the simulation server receives the message, records and prints the received data; and the simulation server initiates a request, the request content is the received data message, whether the service access is normal or not is monitored, if the access is abnormal, the recording is stopped abnormally, otherwise, the session holding result is recorded, and the next step is continuously executed. Then, the simulation client receives the message, automatically compares whether the message is consistent with the sent data, and if the compared data is inconsistent, records abnormal stop; otherwise, recording and printing the received data and displaying the test result. The above processing procedure is executed by loop. Wherein, in the initial stage, 8583 data message content is randomly changed. Thereby verifying the robustness of maintenance across virtual service sessions based on the 8583 protocol. The load balancing device needs to be configured as follows: configure client → server side direction VIP1, configure real service (real service address is server side IP address). Configure server side → client side to VIP2, configure real service (real service address is client IP address). The connection split function is turned on, the length flag length and offset bits are specified, and the client → server direction refers to the policy for VIP 1. The function of holding across virtual service sessions based on the 8583 protocol is turned on, and the server side → client side direction VIP2 references the policy.
By adopting the testing device for cross-virtual service session maintenance based on the 8583 protocol, the data message in the standard 8583 protocol format can be automatically generated, the 8583 data request can be automatically simulated circularly, the random data content can be updated, and the data message split result can be automatically calculated. Therefore, on the basis of ensuring the test result and the test efficiency, the workload of the tester is saved, and the stable operation of the project is ensured.
The software product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
Those skilled in the art will appreciate that the modules described above may be distributed in the apparatus according to the description of the embodiments, or may be modified accordingly in one or more apparatuses unique from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiment of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiment of the present application.
Exemplary embodiments of the present application are specifically illustrated and described above. It is to be understood that the application is not limited to the details of construction, arrangement, or method of implementation described herein; on the contrary, the intention is to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (10)
1. A test method for cross-virtual service session maintenance based on 8583 protocol comprises the following steps:
configuring a first virtual service and a second virtual service, wherein the first virtual service is used for receiving an 8583 message sent by a client through long connection and client service access, the client service access comprises splitting the received 8583 message according to a length identifier of the 8583 message and carrying out load distribution on the split 8583 request message based on a load balancing strategy, and a real service address of the first virtual service is an IP address of a server, and
the second virtual service is used for receiving a server request and server service access sent by a real server, the server service access comprises session maintenance according to the characteristics of a received 8583 message, and the real service address of the second virtual service is the IP address of a client;
an 8583 message automatic generation step, namely setting 8583 message length identification, judging whether the 8583 message length identification is correct or not, and automatically generating an 8583 message in a standard format based on an 8583 protocol and the 8583 message length identification when the result of judging whether the 8583 message length identification is correct is 'yes';
a client request initiating step, in which a simulation client initiates a client request to the first virtual service, and the content of the client request is the generated 8583 message;
a client service access monitoring step, namely monitoring whether the client service access initiated by the client request to the first virtual service is normal or not;
a client service access result recording step, in which when the result of monitoring whether the client service access initiated by the client request to the first virtual service is normal is yes, a splitting result of the first virtual service for splitting the 8583 message and a distribution result of load distribution of the split 8583 message based on a load balancing strategy are recorded;
a step of receiving a message by a server, namely receiving 8583 messages by an analog server, and recording and printing data received by the server;
a server request initiating step, in which a simulation server initiates a server request to the second virtual service, wherein the content of the server request is the 8583 message received by the simulation server;
a server service access monitoring step, namely monitoring whether the server service access initiated by the server request to the second virtual service is normal or not;
a server service access result recording step, in which when the result of monitoring whether the server service access initiated by the server request to the second virtual service is normal is yes, a session holding result of the second virtual service for holding the session according to the characteristics of the received 8583 message is recorded;
a step of receiving a message by a client, namely simulating the client to receive an 8583 message and automatically comparing the received 8583 message with a 8583 message sent by the client;
a client detection step, namely judging whether the 8583 message received by the client is the same as the 8583 message sent by the client, judging that the test is successful when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is yes, recording and printing the 8583 message received by the client and displaying that the test is successful;
and repeating the 8583 message automatic generation step, the client request initiation step, the client service access monitoring step, the client service access result recording step, the server message receiving step, the server request initiation step, the server service access monitoring step, the server service access result recording step, the client message receiving step and the client detection step until the test is completed, wherein in the 8583 message automatic generation step, the 8583 message in the automatically generated standard format is randomly transformed so as to verify the robustness of cross-virtual service session maintenance based on the 8583 protocol.
2. The 8583 protocol-based cross virtual service session hold testing method of claim 1, further comprising:
in the step of automatically generating the 8583 message, when the result of judging whether the 8583 message length identifier is correct is 'no', recording the 8583 message length identifier error and terminating the test.
3. The 8583 protocol-based cross virtual service session hold testing method of claim 1, further comprising:
in the client service access monitoring step, when the result of monitoring whether the client service access initiated by the client request to the first virtual service is normal is 'no', recording the client service access abnormity and terminating the test.
4. The 8583 protocol-based cross virtual service session hold testing method of claim 1, further comprising:
in the step of recording the server service access result, when the result of monitoring whether the server service access initiated by the server request to the second virtual service is normal is 'no', recording the server service access exception and terminating the test.
5. The 8583 protocol-based cross virtual service session hold testing method of claim 1, further comprising:
in the client detection step, when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is 'no', recording the abnormal comparison and terminating the test.
6. A test apparatus for cross virtual service session hold based on 8583 protocol, comprising:
the virtual service configuration component is used for configuring a first virtual service and a second virtual service, the first virtual service is used for receiving a 8583 message and client service access sent by a client through long connection, the client service access comprises splitting the 8583 message received by the client according to a length identifier of the 8583 message and carrying out load distribution on the split 8583 request message based on a load balancing strategy, a real service address of the first virtual service is an IP address of a server, and
the second virtual service is used for receiving a server request and server service access sent by a real server, the server service access comprises session maintenance according to the characteristics of a received 8583 message, and the real service address of the second virtual service is the IP address of a client;
an 8583 message automatic generation component, configured to set a 8583 message length identifier, determine whether the 8583 message length identifier is correct, and automatically generate an 8583 message in a standard format based on a 8583 protocol and the 8583 message length identifier when a result of determining whether the 8583 message length identifier is correct is "yes";
a client request initiating component, configured to simulate a client to initiate a client request to the first virtual service, where content of the client request is the generated 8583 packet;
the client business access monitoring component is used for monitoring whether the client business access initiated by the client request to the first virtual service is normal or not;
a client service access result recording component, configured to record, when a result of monitoring whether a client service access initiated by the client request to the first virtual service is normal is yes, a splitting result of the first virtual service for splitting the 8583 message and a distribution result of load distribution of the split 8583 message based on a load balancing policy;
the server receiving message component is used for simulating the server to receive 8583 messages and recording and printing data received by the server;
a server request initiating component, configured to initiate a server request for the second virtual service by a simulation server, where content of the server request is a 8583 message received by the simulation server;
the server service access monitoring component is used for monitoring whether the server service access initiated by the server request to the second virtual service is normal or not;
a server service access result recording component, configured to record, when a result of monitoring whether server service access initiated by the server request to the second virtual service is normal is yes, a session holding result of the second virtual service for performing session holding according to characteristics of a 8583 message received by the second virtual service;
the client receives the message assembly, is used for simulating the client to receive the 8583 message, and automatically compares the received 8583 message with the 8583 message sent by the client;
the client detection component is used for judging whether the 8583 message received by the client is the same as the 8583 message sent by the client, judging that the test is successful when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is yes, recording and printing the 8583 message received by the client and displaying that the test is successful;
and the circulating component is used for repeatedly calling the 8583 message automatic generation component, the client request initiation component, the client service access monitoring component, the client service access result recording component, the server message receiving component, the server request initiation component, the server service access monitoring component, the server service access result recording component, the client message receiving component and the client detection component until the test is completed, wherein in the 8583 message automatic generation component, an 8583 message in a standard format which is automatically generated is randomly transformed so as to verify the robustness of cross-virtual service session maintenance based on the 8583 protocol.
7. The 8583 protocol-based cross virtual service session maintenance testing apparatus according to claim 6, wherein the 8583 message automatic generation component is further configured to:
and when the result of judging whether the 8583 message length identification is correct is 'no', recording the 8583 message length identification error and terminating the test.
8. The 8583 protocol-based cross virtual service session hold testing device of claim 6, wherein the client traffic access monitoring component is further to:
and when the result of monitoring whether the client service access initiated by the client request to the first virtual service is normal is 'no', recording the client service access abnormity and terminating the test.
9. The 8583 protocol-based cross virtual service session hold testing apparatus of claim 6, wherein the server traffic access monitoring component is further to:
and when the result of monitoring whether the server service access initiated by the second virtual service is normal is 'no', recording the server service access abnormity and terminating the test.
10. The 8583 protocol-based cross virtual service session hold testing apparatus of claim 6, wherein the client detection component is further to:
and when the result of judging whether the 8583 message received by the client is the same as the 8583 message sent by the client is negative, recording the abnormal comparison and terminating the test.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210609226.6A CN114866442B (en) | 2022-05-31 | 2022-05-31 | 8583 protocol-based cross-virtual service session maintenance test method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210609226.6A CN114866442B (en) | 2022-05-31 | 2022-05-31 | 8583 protocol-based cross-virtual service session maintenance test method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114866442A true CN114866442A (en) | 2022-08-05 |
| CN114866442B CN114866442B (en) | 2023-05-26 |
Family
ID=82642129
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210609226.6A Active CN114866442B (en) | 2022-05-31 | 2022-05-31 | 8583 protocol-based cross-virtual service session maintenance test method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114866442B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060130133A1 (en) * | 2004-12-14 | 2006-06-15 | International Business Machines Corporation | Automated generation of configuration elements of an information technology system |
| CN101534321A (en) * | 2009-03-09 | 2009-09-16 | 浪潮电子信息产业股份有限公司 | Load-balancing session-keeping algorithm based on cookie |
| CN104811488A (en) * | 2015-04-13 | 2015-07-29 | 深信服网络科技（深圳）有限公司 | Load balancing equipment-based session keeping method and system and load balancing equipment |
| CN104852934A (en) * | 2014-02-13 | 2015-08-19 | 阿里巴巴集团控股有限公司 | Method for realizing flow distribution based on front-end scheduling, device and system thereof |
| CN108322524A (en) * | 2018-01-22 | 2018-07-24 | 杭州迪普科技股份有限公司 | A kind of load-balancing device session keeps test method and device |
| CN109510878A (en) * | 2018-12-24 | 2019-03-22 | 杭州迪普科技股份有限公司 | A kind of long connection session keeping method and device |
| CN110535976A (en) * | 2019-09-27 | 2019-12-03 | 杭州迪普科技股份有限公司 | A kind of session keeping method and device |
| CN112910793A (en) * | 2019-12-04 | 2021-06-04 | 中国电信股份有限公司 | Method for connection multiplexing in seven-layer load balancing and load balancer |
| CN113835836A (en) * | 2021-09-23 | 2021-12-24 | 证通股份有限公司 | System, method, computer device and medium for dynamically publishing container service |
| CN114205274A (en) * | 2021-11-02 | 2022-03-18 | 北京百度网讯科技有限公司 | Network equipment testing method and device |
-
2022
- 2022-05-31 CN CN202210609226.6A patent/CN114866442B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060130133A1 (en) * | 2004-12-14 | 2006-06-15 | International Business Machines Corporation | Automated generation of configuration elements of an information technology system |
| CN101534321A (en) * | 2009-03-09 | 2009-09-16 | 浪潮电子信息产业股份有限公司 | Load-balancing session-keeping algorithm based on cookie |
| CN104852934A (en) * | 2014-02-13 | 2015-08-19 | 阿里巴巴集团控股有限公司 | Method for realizing flow distribution based on front-end scheduling, device and system thereof |
| CN104811488A (en) * | 2015-04-13 | 2015-07-29 | 深信服网络科技（深圳）有限公司 | Load balancing equipment-based session keeping method and system and load balancing equipment |
| CN108322524A (en) * | 2018-01-22 | 2018-07-24 | 杭州迪普科技股份有限公司 | A kind of load-balancing device session keeps test method and device |
| CN109510878A (en) * | 2018-12-24 | 2019-03-22 | 杭州迪普科技股份有限公司 | A kind of long connection session keeping method and device |
| CN110535976A (en) * | 2019-09-27 | 2019-12-03 | 杭州迪普科技股份有限公司 | A kind of session keeping method and device |
| CN112910793A (en) * | 2019-12-04 | 2021-06-04 | 中国电信股份有限公司 | Method for connection multiplexing in seven-layer load balancing and load balancer |
| CN113835836A (en) * | 2021-09-23 | 2021-12-24 | 证通股份有限公司 | System, method, computer device and medium for dynamically publishing container service |
| CN114205274A (en) * | 2021-11-02 | 2022-03-18 | 北京百度网讯科技有限公司 | Network equipment testing method and device |
Non-Patent Citations (2)
| Title |
|---|
| 赵艳芳;蒋云起;: "Web服务器负载均衡会话保持的研究", 云南民族大学学报(自然科学版) * |
| 郭建金: "云平台下负载均衡集群中会话保持的研究与实现", 《中国硕士学位论文全文数据库 信息科技辑》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114866442B (en) | 2023-05-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8079017B2 (en) | Automated QS interface testing framework | |
| US9053238B2 (en) | Tool-independent automated testing of software | |
| US7827531B2 (en) | Software testing techniques for stack-based environments | |
| US7979532B2 (en) | Systems and methods for using an access point for testing multiple devices and using several consoles | |
| CN107241315B (en) | Access method and device of bank gateway interface and computer readable storage medium | |
| US20070097872A1 (en) | Network connection apparatus testing method | |
| EP1990972A1 (en) | Method for testing safety access protocol conformity to identification service entity and system thereof | |
| CN109600280B (en) | Pressure testing system, method, device and computer readable storage medium | |
| CN110536132B (en) | IPC simulation method, IPC simulation software system and server | |
| CN112311620A (en) | Method, apparatus, electronic device and readable medium for diagnosing network | |
| CN113238965B (en) | Interface test script generation method, system and storage medium | |
| CN112116997B (en) | Remote diagnosis method, device and system, electronic equipment and computer readable storage medium | |
| CN110445658B (en) | Message processing method and system | |
| CN114866442B (en) | 8583 protocol-based cross-virtual service session maintenance test method and device | |
| CN110198222A (en) | A kind of distribution power automation terminal plug and play test method and test main website | |
| CN112882948A (en) | Stability testing method, device and system for application and storage medium | |
| CN111538646A (en) | System and method for testing performance of spatial information network | |
| CN115190293A (en) | Dial testing method and device, electronic equipment and computer storage medium | |
| CN114257632A (en) | Disconnection reconnection method and device, electronic equipment and readable storage medium | |
| CN115426301B (en) | Device detection method, device, equipment and storage medium based on self-generated message | |
| CN113157558B (en) | System testing method and device | |
| CN116893977B (en) | Automatic deployment method, device, equipment and medium for distributed simulation test environment | |
| CN117527658A (en) | Method for testing reliability of SD-WAN transit server | |
| CN115226137A (en) | Fault warning method and device, electronic equipment and readable medium | |
| CN117075871A (en) | Method, device, equipment and storage medium for generating calling code of application program interface |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |