Testing method and device of departure client, electronic equipment and storage medium

Abstract

The invention discloses a test method and device for a departure client, electronic equipment and a storage medium, and relates to the technical field of aviation information. The method comprises the steps that control instruction data sent by a target departure client side in a plurality of departure client sides are received, and different departure client sides adopt different data protocols when sending the control instruction data; converting the control instruction data into standard instruction data by using an equipment data model; processing the standard instruction data through the standard departure equipment to obtain a processing result; and determining a test result of the target departure client according to the processing result. According to the invention, the technical problem of low test efficiency of the departure client is solved.

Description

Technical Field

[0001] The present invention relates to the field of aviation information technology, and in particular to a testing method, device, electronic equipment and storage medium for a departure client. Background Art

[0002] In the airport LAN, there are many external devices, such as boarding pass printers, baggage tag printers, manifest printers, gate scanners, passport scanners, etc. Due to the differences in models of these external devices, it is not convenient for airlines to use them. In order to shield this difference and facilitate the departure client to call external devices, many manufacturers have developed a variety of departure device platforms. The departure client can call the external device control interface through the departure device platform to meet the needs of using external devices.

[0003] Different departure clients use different departure device platforms. When the departure client version is upgraded, time-consuming and labor-intensive testing and certification is required on the corresponding departure device platform. Different departure clients using different departure device platforms cannot be tested at the same time, resulting in low testing efficiency of the departure clients.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present invention provide a method, device, electronic device and storage medium for testing a departing client, so as to at least solve the technical problem of low testing efficiency of the departing client.

[0006] According to one aspect of an embodiment of the present invention, a method for testing a departure client is provided, comprising: receiving control instruction data sent by a target departure client among multiple departure clients, wherein different departure clients use different data protocols when sending the control instruction data; converting the control instruction data into standard instruction data using a device data model; processing the standard instruction data using a standard departure device to obtain a processing result; and determining a test result of the target departure client according to the processing result.

[0007] Further, receiving control instruction data sent by a target departure client among multiple departure clients includes: in response to receiving a connection request sent by the target departure client, establishing and determining a target protocol thread that matches the target departure client based on the connection request, wherein the target protocol thread is used to represent a thread corresponding to a data protocol adopted by the target departure client; and acquiring the control instruction data through the target protocol thread.

[0008] Further, establishing and determining a target protocol thread that matches the target departure client based on the connection request includes: parsing the connection request sent by the target departure client to obtain request information, wherein the request information includes at least one of the following: platform type, device type, Internet Protocol address (IP address for short), and port; and determining a target protocol thread that matches the target departure client based on the request information.

[0009] Furthermore, obtaining control instruction data through the target protocol thread includes: connecting and monitoring data transmission of the target departure client through the target protocol thread; and reading the control instruction data through the target protocol thread when the control instruction data transmitted by the target departure client is detected.

[0010] Furthermore, the control instruction data is converted into standard instruction data using a device data model, including: determining a target data protocol corresponding to the control instruction data based on a target protocol thread for reading the control instruction data; parsing the control instruction data based on the target data protocol using the device data model to extract device semantic fields; and generating standard instruction data based on the extracted device semantic fields using the device data model.

[0011] Furthermore, the device control instruction data is parsed based on the target data protocol using the device data model to extract the device semantic fields, including: using the device data model to identify device-independent fields in the control instruction data according to the target data protocol, wherein the device-independent fields are used to characterize fields that differ in the instruction data corresponding to different data protocols; deleting the device-independent fields in the control instruction data to obtain the device semantic fields.

[0012] Furthermore, the method also includes: when the original device identifiers of the multiple outbound clients are different, unifying the original device identifiers of the multiple outbound clients to obtain the target device identifiers of the multiple outbound clients; and storing the target device identifiers of the multiple outbound clients in a unified device cache.

[0013] According to another aspect of an embodiment of the present invention, a test device for a departure system is further provided, including: a receiving module, used to receive control instruction data sent by a target departure client among multiple departure clients, wherein the instruction data sent by different departure clients adopt different data protocols; a conversion module, used to convert the control instruction data into standard instruction data using a device data model; a processing module, used to process the standard instruction data through a standard departure device to obtain a processing result; and a determination module, used to determine a test result of the target departure client according to the processing result.

[0014] According to another aspect of an embodiment of the present invention, there is further provided an electronic device, comprising: a memory storing an executable program; and a processor for running the program, wherein the above-mentioned method for testing a departure client is executed when the program is running.

[0015] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is further provided. The computer-readable storage medium includes a stored executable program, wherein when the executable program runs, the device where the storage medium is located is controlled to execute the above-mentioned test method for the departure client.

[0016] In an embodiment of the present invention, control instruction data sent by a target departure client among multiple departure clients are received, wherein different departure clients use different data protocols when sending control instruction data; the control instruction data are converted into standard instruction data using a device data model; the standard instruction data are processed by a standard departure device to obtain a processing result; and a test result of the departure client is determined according to the processing result. It is easy to notice that by converting the control instruction data sent by the target departure client among multiple departure clients and converting the control instruction data into standard instruction data that can be processed by the standard departure device, the control instruction data of multiple departure clients using different departure device platforms can be converted into standard instruction data at the same time, and the standard instruction data can be processed by the standard departure device to obtain a test result, so as to achieve the purpose of testing multiple departure clients using different departure device platforms at the same time, thereby achieving the technical effect of improving the test efficiency of the departure client, and further solving the technical problem of low test efficiency of the departure client. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0018] Figure 1 is a flow chart of a method for testing a departure client according to an embodiment of the present invention;

[0019] Figure 2 is a schematic diagram of an optional multi-platform testing system according to an embodiment of the present invention;

[0020] Figure 3 is a flow chart of an optional outbound client testing method according to an embodiment of the present invention;

[0021] Figure 4 2 is a schematic diagram of a testing device for a departing client according to an embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0024] Example 1

[0025] According to an embodiment of the present invention, an embodiment of a method for testing a departure client is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0026] Figure 1 is a flow chart of a method for testing a departure client according to an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0027] Step S102: receiving control instruction data sent by a target outbound client among a plurality of outbound clients, wherein different outbound clients use different data protocols when sending the control instruction data.

[0028] The departure client in the above steps is the client used by airlines or airport staff to handle departure services such as passenger check-in, baggage check-in, boarding pass printing, etc. It is also called the departure front-end system. The departure client needs to be connected to the departure device platform to determine the control interface of the departure device and call the departure device. Different departure clients can be connected to different departure device platforms.

[0029] The target outbound client in the above steps is the outbound client that sends the test requirements to the test system and establishes a connection with the test system.

[0030] The control instruction data in the above steps include control commands and parameters for the departure device, as well as communication control information, data packet formatting information, error checking information and other data irrelevant to the control of the departure device.

[0031] The data protocol in the above steps is used to characterize the data format and transmission rules in the data communication process.

[0032] In an optional embodiment, the test system for implementing the test method includes multiple departure equipment platforms that comply with the CUTE (Common-Use Terminal Equipment) standard, such as the SITA platform (a departure equipment platform launched by the International Aeronautical Telecommunications Association based on the CUTE standard), the ARINC (a departure equipment platform launched by the Aeronautical Radio Communications Corporation based on the CUTE standard) platform, etc. A client among the multiple departure clients that sends control instruction data to the departure equipment platform in the test system is determined as a target client, and a Socket connection thread is used to receive the control instruction data sent by the target departure client.

[0033] It should be noted that different target departure clients use different departure equipment platforms. Since the departure equipment platforms use different data protocols, when different target departure clients send control instruction data to different departure equipment platforms in the test system, different data protocols are used. The type of data protocol used needs to be determined based on the departure equipment platform used by the target departure client.

[0034] Step S104: using the device data model to convert the control instruction data into standard instruction data.

[0035] The equipment data model in the above steps is used to parse the control instruction data and convert the control instruction data into standard instruction data in a unified format for analysis and execution by standard departure equipment.

[0036] The standard instruction data in the above steps has a data format that complies with universal standards and can be directly executed by standard departure equipment. Exemplarily, the standard instruction data can be data that complies with AEA (Association of European Air Lines, departure equipment standards set by the European Airlines Association) standards, but is not limited to this.

[0037] In an optional embodiment, since different departure clients adopt different data protocols when sending control instruction data, the header field of the control data instruction often has format differences caused by different data protocols. In order to facilitate the processing of standard departure equipment, the control instruction data is input into the equipment data model, and the control instruction data is converted into standard instruction data to shield the format differences caused by different data protocols, and only retain the data related to equipment control in the control instruction data.

[0038] Step S106, processing the standard instruction data by the standard departure equipment to obtain a processing result.

[0039] The standard departure equipment in the above steps is a departure equipment that complies with universal standards, and may be a departure equipment that complies with AEA standards, but is not limited thereto. The departure equipment may include but is not limited to a boarding pass printer, a baggage tag printer, and the like.

[0040] The processing results in the above steps are the results of the standard departure equipment executing the instruction operation after receiving the standard instruction data, which may include but are not limited to successful execution, print output, successful scanning or information error.

[0041] In an optional embodiment, the standard departure device is an AEA device, and the standard instruction data is an AEA instruction set data. After receiving the standard instruction data, the standard departure device will parse the standard instruction data to determine the device operation contained in the standard instruction data, such as printing a boarding pass, reading a barcode, verifying a certificate, etc. After parsing the standard instruction data, the standard departure device will perform the corresponding operation according to the parsed instruction. For example, if the device operation contained in the standard instruction data is printing a boarding pass, the printer will start printing and generate a boarding pass. After the device operation contained in the standard instruction data is completed, the standard departure device can generate a processing result, which includes information such as whether the operation is successful, the device status, and whether there is an error.

[0042] Step S108, determining the test result of the target outbound client according to the processing result.

[0043] The test results in the above steps are used to characterize whether the function of the departure client calling the standard departure device is normal, which can be obtained by comparing the processing results with the prediction results.

[0044] In an optional embodiment, it is checked whether the operation result meets expectations, whether the device status is normal, and whether there is any error information based on the processing result, that is, the condition for the test to pass is set as the operation result meets expectations, the device status is normal, and there is no error information. The test result is determined to be a test pass when the operation result meets expectations, the device status is normal, and there is no error information. The rules for test failure can be flexibly set according to the actual application situation. The test can be determined to fail when any one of the following situations exists: the operation result does not meet expectations, the device status is abnormal, and there is error information; the test can also be determined to fail when any two of the following situations exist: the operation result does not meet expectations, the device status is abnormal, and there is error information; the test can also be determined to fail when all three situations exist: the operation result does not meet expectations, the device status is abnormal, and there is error information. In the case of a test failure, an error code and error description can be provided to locate the problem with the departure client.

[0045] The following is a description of a preferred embodiment. Figure 2 is a schematic diagram of an optional multi-platform test system according to an embodiment of the present invention. Figure 2 As shown, the target departure client sends a test request to the multi-platform test system and interacts with the platform control unit in the multi-platform test system. The two departure equipment platforms included in the target departure client are the SITA platform and the ARINC platform. The standard departure equipment managed by the SITA platform and the ARINC platform are both departure boarding pass printers (ATB for short) and departure baggage tag printers (BTP for short). The platform control unit establishes a socket connection thread according to the departure equipment platform type, standard departure equipment type, Internet protocol address and port requested by the target departure client. The following three cases are used as examples for explanation.

[0046] The first case: when the target departure client needs to connect to the SI TA platform, a socket connection thread facing the SI TA platform is established, and the control instruction data sent by the target departure client is obtained through the socket connection thread facing the SI TA platform. Since the target departure client does not specify which standard departure device in the SI TA platform is to be controlled, the universal departure boarding pass printer data model and the universal departure baggage tag printer data model are used respectively to convert the control instruction data into standard departure boarding pass printer data and standard departure baggage tag printer data, so that the departure boarding pass printer can process the standard departure boarding pass printer data. The departure baggage tag printer can process the standard departure baggage tag printer data and obtain the processing result.

[0047] The second situation: when the target departure client needs to connect to the ARINC platform to control the departure boarding pass printer, a socket connection thread facing the ARINC platform for the departure boarding pass printer is established; the control instruction data sent by the target departure client is obtained through the socket connection thread facing the ARINC platform for the departure boarding pass printer; the universal departure boarding pass printer data model is used to convert the control instruction data into standard departure boarding pass printer data, so that the departure boarding pass printer can process the standard departure boarding pass printer data to obtain the processing result.

[0048] In the third case, when the target departure client needs to connect to the ARINC platform to control the departure baggage tag printer, a socket connection thread facing the ARINC platform for the departure baggage tag printer is established; the control instruction data sent by the target departure client is obtained through the socket connection thread facing the ARINC platform for the departure baggage tag printer; the control instruction data is converted into standard departure baggage tag printer data using a universal departure baggage tag printer data model, so that the departure baggage tag printer can align with the departure baggage tag printer data to obtain a processing result.

[0049] Then, the multi-platform test system determines the test result of the departure client according to the processing result. It should be noted that the general departure boarding pass printer data model and the general departure baggage tag printer data model are both the device data models mentioned above, the departure boarding pass printer and the departure baggage tag printer are both the standard departure devices mentioned above, and the standard departure boarding pass printer data and the standard departure baggage tag printer data are both the standard instruction data mentioned above.

[0050] In an embodiment of the present invention, control instruction data sent by a target departure client among multiple departure clients are received, wherein the instruction data sent by different departure clients use different data protocols; the control instruction data are converted into standard instruction data using a device data model; the standard instruction data are processed by a standard departure device to obtain a processing result; and a test result of the target departure client is determined according to the processing result. It is easy to notice that by converting the control instruction data sent by a target departure client among multiple departure clients into standard instruction data that can be processed by a standard departure device through a device data model, the control instruction data of multiple departure clients using different departure device platforms can be converted into standard instruction data at the same time, and the standard instruction data can be processed by the standard departure device to obtain a test result, so as to achieve the purpose of testing multiple departure clients using different departure device platforms at the same time, thereby achieving the technical effect of improving the test efficiency of the departure client, and further solving the technical problem of low test efficiency of the departure client.

[0051] In one embodiment of the present application, receiving control instruction data sent by a target departure client among multiple departure clients includes: in response to receiving a connection request sent by the target departure client, establishing and determining a target protocol thread that matches the target departure client based on the connection request, wherein the target protocol thread is used to represent a thread corresponding to a data protocol adopted by the target departure client; and acquiring the control instruction data through the target protocol thread.

[0052] The connection request in the above steps is a request sent by the target departure client to the departure device platform in the test system. The purpose of sending the connection request is to establish a connection with the departure device platform so as to control the standard departure device through the device control interface provided by the departure device platform.

[0053] The target protocol thread in the above steps is a communication thread customized for the data protocol used by the target departure client, and is used to monitor and receive control instruction data sent by the target departure client. The target protocol thread can be a Socket connection thread, but is not limited thereto.

[0054] In an optional embodiment, when the target departure client sends a connection request to the test system, the network monitoring module of the test system will receive the connection request. The test system will parse the received connection request, extract the request information therein, and determine the departure device platform that the target departure client needs to use and the standard departure device that needs to be controlled. According to the departure device platform that the target departure client needs to use and the standard departure device that needs to be controlled, a target protocol thread that can monitor the target departure client is established, and when the target departure client sends control instruction data, the target protocol thread is used to receive and obtain the control instruction data.

[0055] In one implementation of the present application, establishing and determining a target protocol thread that matches a target departure client based on a connection request includes: parsing a connection request sent by the target departure client to obtain request information, wherein the request information includes at least one of the following: platform type, device type, Internet Protocol address, port; and determining a target protocol thread that matches the target departure client based on the request information.

[0056] The request information in the above steps is the specific information contained in the connection request sent by the target departure client.

[0057] The platform type in the above steps is the type of the departure equipment platform to which the target departure client is connected, which may be a SITA platform or an ARINC platform, but is not limited thereto.

[0058] The device type in the above steps is the type of standard departure device that the target departure client wants to control through the departure device platform.

[0059] The Internet Protocol address in the above step is used to identify the location of the target outbound client in the network so that the test system can determine the address to which it needs to respond.

[0060] The ports in the above steps are used to identify different services or applications running on the same device. The target outbound client provides the port in the connection request, and the test system establishes the correct network connection based on it.

[0061] In an optional embodiment, service objects are established for ports of different departure equipment platforms. For example, a first ServerSocket service object can be established for the port of the SITA platform, a second ServerSocket service object can be established for the ATB port of ARINC, and a third ServerSocket service object can be established for the BTP port of ARINC. The IP address and port number corresponding to the service object are monitored through the above-mentioned ServerSocket service object to receive the connection request sent by the target departure client.

[0062] When receiving a connection request sent by the target departure client, the connection request is parsed to obtain request information. When the port in the request information is the port of the SI TA platform, the target protocol thread is determined to be the SI TA_Socket (SI TA platform_socket) thread, the SI TA_Socket thread is created, and the thread is stored in the HashMap (hash map) cache for unified management; when the port in the request information is the ATB port of ARINC, the target protocol thread is determined to be the ARINC_ATB_Socket (ARINC platform_departure boarding pass printer_socket) thread, the ARINC_ATB_Socket thread is created, and the thread is stored in the HashMap cache for unified management; when the port in the request information is the BTP port of ARINC, the target protocol thread is determined to be the ARINC_BTP_Socket (ARINC platform_departure baggage tag printer_socket) thread, the ARINC_BTP_Socket thread is created, and the thread is stored in the HashMap cache for unified management.

[0063] Through the above process, the automatic adaptation of the target departure client and the departure equipment platform is completed, the target protocol thread matching the target departure client is established, and the unified management and concurrent control of each target protocol thread are completed.

[0064] In one implementation of the present application, obtaining control instruction data through a target protocol thread includes: connecting and monitoring data transmission of a target departure client through a target protocol thread; and reading the control instruction data through the target protocol thread when control instruction data sent by the target departure client is monitored.

[0065] In an optional embodiment, the target protocol thread monitors the client socket of the target departure client and waits for the target departure client to send control instruction data. When it is detected that the target departure front end has control instruction data sent, the target protocol thread reads the control instruction data and stores the control instruction data in the memory.

[0066] In one embodiment of the present application, a device data model is used to convert control instruction data into standard instruction data, including: determining a target data protocol corresponding to the control instruction data based on a target protocol thread that reads the control instruction data; parsing the control instruction data based on the target data protocol using the device data model to extract device semantic fields; and generating standard instruction data based on the extracted device semantic fields using the device data model.

[0067] The target data protocol in the above steps is the data communication protocol used by the target departure client when interacting with the test system. Different departure equipment platforms (such as SITA, ARINC, etc.) have their own data protocols, which define the data format, command structure, field meaning, etc. Since the departure equipment platform that the target departure client needs to connect to when interacting with the test system is different, the target departure client uses different target protocol threads when sending control command data.

[0068] The device semantic field in the above steps is a field in the control instruction data that is directly related to the device function and operation. The device semantic field carries the actual instruction information sent by the target departure client to the standard departure device, such as printing specific content to the boarding pass or reading passenger information.

[0069] In an optional embodiment, different departure equipment platforms have their own data protocols. The departure equipment platform corresponding to the target protocol thread can be determined according to the target protocol thread, and the data protocol used by the departure equipment platform is found, and the data protocol is determined as the target data protocol. The device data model is used to determine which fields in the control instruction data are header fields irrelevant to the device operation and which fields are fields related to the device operation according to the target data protocol, and only the fields related to the device operation are retained as device semantic fields.

[0070] Then continue to use the equipment data model to further adapt and unify the equipment instructions, equipment status, error codes, etc. of the departure equipment platform, and convert the equipment semantic fields into standard instruction data. For example, when the target data protocol is the data protocol of the SITA platform, the instruction for operating the equipment is "AD; CB", and when the target data protocol is the data protocol of the ARINC platform, the instruction for operating the equipment is "CB", and the standard AEA instructions corresponding to "AD; CB" and "CB" are both "CB", so the equipment semantic field "AD; CB" is converted into the standard instruction data "CB".

[0071] In one embodiment of the present application, a device data model is used to parse device control instruction data based on a target data protocol to extract device semantic fields, including: using the device data model to identify device-independent fields in the control instruction data according to the target data protocol, wherein the device-independent fields are used to characterize fields that differ in instruction data corresponding to different data protocols; deleting the device-independent fields in the control instruction data to obtain device semantic fields.

[0072] The device-independent fields in the above steps are fields in the control instruction data that are not directly related to the device function or operation. The device-independent fields may include header and tail identifiers, length fields, checksums, sequence numbers, padding fields, etc. When the target data protocols are different, the device-independent fields in the control instruction data for the same standard departure device are different.

[0073] In an optional embodiment, the device data model is used to decouple the header field in the control instruction data, that is, the device-independent field, according to the target data protocol, and retain the device semantic field. Exemplarily, the target protocol thread is the SITA_Socket thread as an example. When the SITA_Socket thread reads a data stream, that is, the control instruction data, the target data protocol is the data protocol of the SITA platform. The header field of the target data protocol is identified based on the data protocol of the SITA platform. The header field contains information such as the data stream length Len, the cyclic redundancy check code Crc, the data stream self-increment code Seq, and the filler data filler. These device-independent fields are deleted, and the remaining fields are the device semantic fields.

[0074] In one implementation of the present application, the method further includes: when the original device identifiers of the multiple departing clients are different, unifying the original device identifiers of the multiple departing clients to obtain the target device identifiers of the multiple departing clients; and storing the target device identifiers of the multiple departing clients in a unified device cache.

[0075] The original equipment identification in the above steps is an identifier used to uniquely identify the standard departure equipment on different departure equipment platforms. The original equipment identification of the same standard departure equipment on different departure equipment platforms may be different.

[0076] The target device ID in the above steps is a standard device ID uniformly used in the test system to replace the original device ID.

[0077] In an optional embodiment, the original device identifiers of the same standard departure device in different departure device platforms may be different. Therefore, when different departure clients connect to different departure device platforms in the test system, the original device identifiers corresponding to the standard departure devices called by multiple departure clients may be different. In this case, the original device identifiers corresponding to the same standard departure device are replaced with a unified identifier to obtain the target device identifier, and the target device identifier is stored in a unified device cache. Exemplarily, when the established target protocol thread is an ARINC_ATB_Socket thread and an ARINC_BTP_Socket thread, the original device identifiers of ATB and BTP in the ARINC platform are converted into the target device identifier corresponding to ATB and the target device identifier corresponding to BTP, respectively, and the target device identifier corresponding to ATB and the target device identifier corresponding to BTP are stored in the List cache, thereby completing the decoupling of the device identifiers of the departure device platform, thereby performing unified device cache management.

[0078] A preferred embodiment is described below. Figure 3 is a flow chart of an optional outbound client testing method according to an embodiment of the present invention, such as Figure 3 As shown, an optional test method flow of the outbound client is as follows:

[0079] Step S302: the departure client accesses the multi-platform testing system.

[0080] The departure client accesses the multi-platform test system including multiple departure equipment platforms by sending a connection request. After successful access, the departure client sends control command data to the multi-platform test system.

[0081] Step S304: decoupling the platform device identification.

[0082] In view of the situation that the same departure equipment has different equipment identifications in multiple departure equipment platforms, the multi-platform testing system unifies the equipment identifications of the same departure equipment in multiple departure equipment platforms to complete the decoupling of platform equipment identifications.

[0083] Step S306, decoupling the platform protocol field header.

[0084] The multi-platform test system deletes the field headers related to the data protocol in the control instruction data, and only retains the device semantic fields related to device control, thereby realizing the decoupling of the platform protocol field headers.

[0085] Step S308: importing the device data model.

[0086] Step S310, adapting device instructions, general device status, and platform error codes of different platforms.

[0087] The device data model unifies the device instructions, common device status, and platform error codes of different departure device platforms.

[0088] Step S312, interacting with standard departure equipment.

[0089] The device semantic field is converted into standard instruction data that can be processed by the standard departure device, and the standard instruction data is used to interact with the standard departure device. The standard departure device may be a standard AEA device, and the standard instruction data may be AEA instruction set data, but is not limited thereto.

[0090] Example 2

[0091] According to an embodiment of the present invention, an embodiment of a testing device for a departing client is provided. The device can execute the testing method for a departing client provided in the above embodiment 1. The specific implementation method and preferred application scenario are the same as those in the above embodiment 1 and will not be described in detail here.

[0092] Figure 4 is a schematic diagram of a test device for a departure client according to an embodiment of the present invention, such as Figure 4 As shown, the test device of the departure client includes:

[0093] A receiving module 40 is used to receive control instruction data sent by a target departure client among multiple departure clients, wherein the instruction data sent by different departure clients adopt different data protocols;

[0094] A conversion module 42, for converting the control instruction data into standard instruction data using the device data model;

[0095] The processing module 44 is used to process the standard instruction data through the standard departure equipment to obtain the processing result;

[0096] The determination module 46 is used to determine the test result of the target departure client according to the processing result.

[0097] The receiving module includes: a first determining unit, which is used to establish and determine a target protocol thread that matches the target departure client based on the connection request in response to receiving a connection request sent by the target departure client, wherein the target protocol thread is used to characterize a thread corresponding to a data protocol adopted by the target departure client; and an acquiring unit, which is used to acquire control instruction data through the target protocol thread.

[0098] The first determination unit is further used to parse the connection request sent by the target departure client to obtain request information, wherein the request information includes at least one of the following: platform type, device type, Internet Protocol address, port; and determine a target protocol thread that matches the target departure client based on the request information.

[0099] The acquisition unit is also used to monitor the data transmission of the target departure client through the target protocol thread connection; when the control instruction data sent by the target departure client is monitored, the control instruction data is read through the target protocol thread.

[0100] The conversion module includes: a second determination unit, which is used to determine the target data protocol corresponding to the control instruction data based on the target protocol thread that reads the control instruction data; a parsing unit, which is used to parse the control instruction data based on the target data protocol using the device data model and extract the device semantic fields; and a generation unit, which is used to generate standard instruction data based on the extracted device semantic fields using the device data model.

[0101] The parsing unit is also used to use the device data model to identify device-independent fields in the control instruction data according to the target data protocol, wherein the device-independent fields are used to characterize fields that are different in the instruction data corresponding to different data protocols; delete the device-independent fields in the control instruction data to obtain the device semantic fields.

[0102] The receiving module also includes: a unification unit, which is used to unify the original device identifications of multiple outbound clients when the original device identifications of multiple outbound clients are different, so as to obtain the target device identifications of the multiple outbound clients; and a storage unit, which is used to store the target device identifications of the multiple outbound clients into a unified device cache.

[0103] Example 3

[0104] According to an embodiment of the present invention, there is further provided an electronic device, comprising: a memory storing an executable program; and a processor for running the program, wherein the test method for the departure client in Embodiment 1 is executed when the program is running.

[0105] Example 4

[0106] An embodiment of the present application further provides a computer-readable storage medium, which includes a stored executable program, wherein when the executable program is running, the device where the computer-readable storage medium is located is controlled to execute the test method of the departure client in each embodiment of the present invention.

[0107] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0108] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0109] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0110] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0111] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0112] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0113] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for testing a departing client, characterized in that: include: receiving control instruction data sent by a target departure client among the plurality of departure clients, wherein different departure clients use different data protocols when sending the control instruction data; Converting the control instruction data into standard instruction data using a device data model; Processing the standard instruction data by standard departure equipment to obtain a processing result; The test result of the target outbound client is determined according to the processing result.

2. The method for testing the outbound client according to claim 1, characterized in that: Receiving control instruction data sent by a target departure client among multiple departure clients, including: In response to receiving a connection request sent by the target departure client, establishing and determining a target protocol thread that matches the target departure client based on the connection request, wherein the target protocol thread is used to represent a thread corresponding to a data protocol used by the target departure client; The control instruction data is obtained through the target protocol thread.

3. The method for testing the outbound client according to claim 2, characterized in that: Establishing and determining a target protocol thread matching the target outbound client based on the connection request includes: Parsing the connection request sent by the target departure client to obtain request information, wherein the request information includes at least one of the following: platform type, device type, Internet protocol address, and port; A target protocol thread matching the target outbound client is determined based on the request information.

4. The method for testing the outbound client according to claim 2, characterized in that: Acquiring the control instruction data through the target protocol thread includes: Monitor the data transmission status of the target departure client through the target protocol thread connection; In the case of monitoring the control instruction data sent by the target departure client, the control instruction data is read through the target protocol thread.

5. The method for testing the outbound client according to claim 1, characterized in that: The control instruction data is converted into standard instruction data using a device data model, including: Determining a target data protocol corresponding to the control instruction data based on a target protocol thread that reads the control instruction data; Parsing the control instruction data based on the target data protocol using the device data model to extract device semantic fields; The standard instruction data is generated based on the extracted device semantic fields using the device data model.

6. The method for testing the outbound client according to claim 5, characterized in that: The device control instruction data is parsed based on the target data protocol using the device data model to extract device semantic fields, including: Using the device data model to identify device-independent fields in the control instruction data according to the target data protocol, wherein the device-independent fields are used to represent fields that are different in the instruction data corresponding to different data protocols; The device-independent field in the control instruction data is deleted to obtain the device semantic field.

7. The method for testing a departing client according to any one of claims 1 to 6, characterized in that: The method further comprises: In the case where the original device identifiers of the multiple outbound clients are different, unifying the original device identifiers of the multiple outbound clients to obtain the target device identifiers of the multiple outbound clients; The target device identifiers of the multiple outbound clients are stored in a unified device cache.

8. A testing device for a departure client, characterized in that: include: A receiving module, used for receiving control instruction data sent by a target departure client among multiple departure clients, wherein the instruction data sent by different departure clients adopt different data protocols; A conversion module, used to convert the control instruction data into standard instruction data using a device data model; A processing module, used for processing the standard instruction data through standard departure equipment to obtain a processing result; A determination module is used to determine the test result of the departure client according to the processing result.

9. An electronic device, characterized in that: include: A memory storing an executable program; A processor is used to run the program, wherein the program executes the test method for the departure client according to any one of claims 1 to 7 when running.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is run, the device where the storage medium is located is controlled to execute the method for testing the departure client according to any one of claims 1 to 7.

Images