Data relay exchange method and device, equipment, storage medium and product

Abstract

The application discloses a data relay exchange method and device, equipment, storage medium and computer program product, and belongs to the technical field of function test. According to the application, when a data relay exchange request is received, a transmission source system and a transmission target system are determined according to the data relay exchange request; a deserialization data model and a serialization callback data model are determined according to the data relay exchange request and a feature code routing table; data of the transmission source system and the transmission target system is processed through the deserialization data model and the serialization callback data model, and obtained exchanged data; and data relay exchange of the transmission source system and the transmission target system is performed according to the exchanged data. In this way, a cross-platform automatic test program can be constructed without relying on an upper test system platform, so that the effectiveness of data is ensured.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of functional testing, in particular to a data relay exchange method, device, equipment, storage medium and computer program product. BACKGROUND

[0002] When a merchant and a user of a network payment are registered, real-name, data filling, SMS push and other functional testing, for the payment sharing capability, how to design the interface test of the appropriate merchant center and user center, and convert it into an executable automatic test script of a specific platform, a specific framework or a specific tool, the existing technical solution is mainly to manually enter, import or fill in the test design data into a specified template.

[0003] The existing test method and test technical solution rely on manual experience and can only be used for a single specified automatic test system data form feature, therefore, there is a problem of low accuracy, in addition, when a new test framework, tool or platform is needed, the above three steps have to be repeated, which consumes a lot of repeated work time, and the accuracy and efficiency are low, and it is difficult to ensure the completeness of the data.

[0004] The above content is only used to assist in understanding the technical solutions of the present application, and does not represent the acknowledgement of the above content as prior art. SUMMARY

[0005] The main purpose of the present application is to provide a data relay exchange method, device, equipment, storage medium and computer program product, which aims to solve the technical problem that the existing technical data test system can only one-way data transmission one by one.

[0006] To achieve the above purpose, the present application provides a data relay exchange method, which comprises the following steps:

[0007] When receiving a data relay exchange request, determining a transmission source system and a transmission target system according to the data relay exchange request;

[0008] According to the data relay exchange request and the feature code routing table, determining a deserialization data model and a serialization callback data model;

[0009] Processing the data of the transmission source system and the transmission target system through the deserialization data model and the serialization callback data model to obtain the data to be exchanged;

[0010] According to the data to be exchanged, the data relay exchange of the transmission source system and the transmission target system is performed.

[0011] Optionally, before the determining the deserialization data model and the serialization callback model according to the data relay exchange request and the feature code routing table, the method further comprises:

[0012] obtaining the plaintext data information of the transmission source system and the transmission target system;

[0013] constructing the identification system feature code according to the plaintext data information;

[0014] constructing the feature code routing table according to the identification system feature code.

[0015] Optionally, the constructing the feature code routing table according to the identification system feature code comprises:

[0016] determining the identification data model strategy feature code through a preset model identification code strategy;

[0017] constructing a feature code set according to the identification system feature code and the identification data model strategy feature code;

[0018] constructing the feature code routing table according to the feature code set.

[0019] Optionally, the determining the deserialization data model and the serialization callback model according to the data relay exchange request and the feature code routing table comprises:

[0020] generating an authentication data frame request according to the data relay exchange request and the feature code routing table;

[0021] authenticating and addressing the source system feature code of the transmission source system and the target system feature code of the transmission target system according to the authentication data frame request;

[0022] determining the deserialization data model and the serialization callback model according to the authentication result.

[0023] Optionally, the determining the deserialization data model and the serialization callback model according to the authentication result comprises:

[0024] when the authentication result is authentication success, querying the feature code routing table according to the source system feature code and the target system feature code to obtain a data model number and a data callback model number;

[0025] determining the deserialization data model and the serialization callback data model according to the data model number and the data callback model number.

[0026] Optionally, the processing the data of the transmission source system and the transmission target system through the deserialization data model and the serialization callback data model to obtain the data to be exchanged comprises:

[0027] determine a data processing strategy according to the deserialization data model and the serialization callback data model;

[0028] determine system corresponding model information of the transmission source system and the transmission target system according to the data processing strategy;

[0029] invoke the deserialization data model and the serialization callback data model to process data of the transmission source system and the transmission target system respectively according to the system corresponding model information, and obtain to-be-exchanged data

[0030] In addition, to achieve the above object, the application further provides a data relay exchange device, which comprises:

[0031] a system determination module, configured to determine a transmission source system and a transmission target system according to a data relay exchange request when the data relay exchange request is received;

[0032] a model determination module, configured to determine a deserialization data model and a serialization callback data model according to the data relay exchange request and a feature code routing table;

[0033] a data processing module, configured to process data of the transmission source system and the transmission target system through the deserialization data model and the serialization callback data model, and obtain to-be-exchanged data;

[0034] a data exchange module, configured to perform data relay exchange of the transmission source system and the transmission target system according to the to-be-exchanged data.

[0035] In addition, to achieve the above object, the application further provides a data relay exchange device, which comprises a memory, a processor and a data relay exchange program stored in the memory and running on the processor, and the data relay exchange program is configured to implement the data relay exchange method as described above.

[0036] In addition, to achieve the above object, the application further provides a storage medium, which stores a data relay exchange program, and the data relay exchange program is executed by a processor to implement the data relay exchange method as described above.

[0037] In addition, to achieve the above object, the application further provides a computer program product, which comprises a data relay exchange program, and the data relay exchange program is executed by a processor to implement the steps of the data relay exchange method as described above.

[0038] The application determines the transmission source system and the transmission target system according to the data relay exchange request when receiving the data relay exchange request; determines the deserialization data model and the serialization callback data model according to the data relay exchange request and the characteristic code routing table; processes the data of the transmission source system and the transmission target system through the deserialization data model and the serialization callback data model, and obtains the data to be exchanged; and performs data relay exchange of the transmission source system and the transmission target system according to the data to be exchanged. In this way, the serialization data model and the serialization callback data model are used in the process of data relay exchange between test systems, and the characteristic code routing table is constructed for quick query and data encryption and decryption, so that a cross-platform automatic test program can be constructed without relying on the upper test system platform, thereby ensuring the effectiveness of the data. BRIEF DESCRIPTION OF DRAWINGS

[0039] Figure 1 is a structural schematic diagram of a data relay exchange device of a hardware running environment related to the embodiment scheme of the application;

[0040] Figure 2 is a flowchart of the first embodiment of the data relay exchange method of the application;

[0041] Figure 3 is a schematic diagram of a data authentication process in the embodiment of the data relay exchange method of the application;

[0042] Figure 4 is a schematic diagram of a characteristic code routing table authentication in the embodiment of the data relay exchange method of the application;

[0043] Figure 5 is a schematic diagram of data relay processing in the embodiment of the data relay exchange method of the application;

[0044] Figure 6 is a flowchart of the second embodiment of the data relay exchange method of the application;

[0045] Figure 7 is a schematic diagram of system entry processing in the embodiment of the data relay exchange method of the application;

[0046] Figure 8 is a structural block diagram of the first embodiment of the data relay exchange device of the application.

[0047] The implementation, functional features and advantages of the application will be further described with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION

[0048] It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application.

[0049] Refer to Figure 1 , Figure 1 The data relay switching device structure schematic diagram of the hardware running environment involved in the embodiment of the present application.

[0050] As Figure 1 shown, the data relay switching device can include: a processor 1001, for example, a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to realize the connection communication between the components. The user interface 1003 can include a display screen, an input unit such as a keyboard, and can also include a standard wired interface, a wireless interface. The network interface 1004 can optionally include a standard wired interface, a wireless interface (such as a wireless fidelity (Wi-Fi) interface). The memory 1005 can be a high-speed random access memory (RAM) memory, or a stable non-volatile memory (NVM) such as a disk memory. The memory 1005 can also be a storage device independent of the aforementioned processor 1001.

[0051] Those skilled in the art can understand that Figure 1 The structure shown in the above does not constitute a limitation on the data relay switching device, and can include more or fewer components than the diagram, or combine certain components, or different component arrangements.

[0052] As Figure 1 shown, the memory 1005 as a storage medium can include an operating system, a network communication module, a user interface module, and a data relay switching program.

[0053] In Figure 1 the data relay switching device shown, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the data relay switching device of the present application can be arranged in the data relay switching device, and the data relay switching device calls the data relay switching program stored in the memory 1005 through the processor 1001, and executes the data relay switching method provided by the embodiment of the present application.

[0054] The embodiment of the present application provides a data relay switching method, referring to Figure 2 , Figure 2A flowchart of a data relay exchange method according to a first embodiment of the present application.

[0055] In this embodiment, the data relay exchange method comprises the following steps:

[0056] Step S10: Upon receiving the data relay exchange request, determining the transmission source system and the transmission target system according to the data relay exchange request.

[0057] In this embodiment, the execution subject of this embodiment can be the data relay exchange device, which has functions of data processing, data communication, program running, etc. The data relay exchange device can be any server or intelligent terminal. Of course, it can also be other devices with similar functions, and the present embodiment does not limit this. For ease of illustration, the present embodiment is described by taking the data relay exchange device as an example.

[0058] It should be noted that when the network payment merchant and the user are registered, real-name, data filling, SMS pushing and other function tests are performed, for the payment sharing capability, how to design the interface test of the appropriate merchant center and user center, and convert it into an executable automatic test script of a specific platform, a specific framework or a specific tool, the existing technical solution mainly includes three main steps: (1) obtaining a request instance and writing a test case. According to the development document, the interface request instance is filled, the browser is captured and recorded, the background log is obtained, and the test case is written and designed according to the test method. (2) Analyze the form or data template and fill in the script data. According to the data composition rules of the platform, tool or framework, the test case data is entered into the form or filled in the data template. (3) Iterate the previous two steps to enter the data of all test cases into the automatic test system. Finally, through the platform, tool or framework system, set the execution environment, execution plan, unattended, etc. The above steps describe how to convert the test design into an automatic test through a tool, a platform, and the whole process. The test design here refers to the interface function test design of the payment sharing capability. According to experience, these interfaces to be tested need to be arranged and combined according to the number of interface parameters and the value range of the parameters. The interfaces of different functions are further divided into a plurality of sets to be tested. According to the selected automatic execution engine template or page form, the designed test case is filled in sequence, and the corresponding automatic test execution plan is formulated to test each function scenario.

[0059] It should be understood that the above several existing test methods and test technical solutions have the following shortcomings: the existing test methods and test technical solutions rely on manual experience and can only be used for a single specified data form feature of an automated test system, thus, there is a problem of low accuracy. In addition, when a new test framework, tool or platform needs to be used, the above three steps need to be repeated, which consumes a lot of time for repeated work, has low accuracy and efficiency, and is difficult to ensure the completeness of data, mainly in the following aspects: 1. How to ensure the accurate relationship between test designs in different systems. The data field names of different frameworks, tools or system platforms can be customized. When the test design data of system A needs to be synchronized to system B, it is necessary to constantly try to select which test data fields to fill in. When there are N different system test data, such as hundreds or thousands of different test case data, it is difficult for a person to analyze and find the relationship between the data of each system from so many test case data. 2. How to determine the adaptation problem of solving the difference in stored data between systems. It is necessary to try and adjust the data storage structure and format of the test case data many times, which has the problems of low efficiency and low accuracy. 3. The existing technology can only one-to-one and one-way system input of test design. Test operation personnel confirm the data template of the target test design one by one according to the experience and the rules and conditions of the system form, template, etc. Due to human factors, this process will cause some data features of the test design to be lost in the one-way data transmission process, and it is impossible to ensure the integrity of the data.

[0060] In specific implementation, in view of the shortcomings of the prior art, a relay device and method for interface test multi-system acceptance based on feature code routing are proposed. The system feature code and the two-way traceable mechanism are used to solve the problem of one-to-one and one-way data transmission of test case data. At the same time, an automatic addressing matching system model based on feature code is proposed to solve the problem of completeness and correctness of test case data transmission. In order to meet the business requirements of test and operation personnel, the scheme of the embodiment also provides two-way reversible relay and exchange of test design data, which can trace back to each data in both directions, ensures the non-repudiation of data, and thus ensures the credibility of data.

[0061] It should be noted that the scheme of the embodiment transforms the technical principle of Ethernet store and forward and applies it to software engineering. Before making a decision according to the serialization of the data of a target system, all test case data of the system is accepted. Once the data is received and buffered, the field values of the data, the version number of the original system, the system name and other characteristics are arranged by the underlying middleware program logic of the application, and the hash value is calculated by using the message digest algorithm, so as to ensure that the data and the data are buffered or stored in the serialization text format. When the transmission request of the system data comes in, the double-factor authentication of the test design data is performed, so as to ensure that the data between systems can be relayed and exchanged, thereby solving the problem of mutual transmission of test case data between multiple systems, and solving the problems of efficiency and accuracy in the process of manual data analysis and import and export. At the same time, the application supports storing the test design case data of each system as a public sequence independently, so that the application can construct a cross-platform automated test program without relying on the upper test system platform, thereby ensuring the effectiveness of the data.

[0062] It should be understood that the scheme of the embodiment mainly involves some concepts: the plaintext space M refers to the set of all plaintexts. The ciphertext space C refers to the set of all ciphertexts. The key space K refers to the set of all keys. The characteristic code encryption algorithm E refers to the encryption transformation from M to C. The NOSQL library refers to a non-relational database, which emphasizes Key-Value storage document data. The storage and forwarding middleware refers to an intermediate program for storing source data in common and forwarding the common storage to destination data.

[0063] In specific implementation, the received data relay exchange request is issued by a transmission source system, that is, a request for exchanging and mutually transmitting test data with other systems. The transmission source system is the initiating system, and the transmission target system is the system that passively exchanges data.

[0064] Step S20: determining a deserialization data model and a serialization callback data model according to the data relay exchange request and the characteristic code routing table.

[0065] It should be noted that in the process of model determination, authentication is performed first to ensure the security of the data.

[0066] Further, in order to safely perform model determination and subsequent data processing, step S20 includes: generating an authentication data frame request according to the data relay exchange request and the characteristic code routing table; authenticating and addressing the source system characteristic code of the transmission source system and the target system characteristic code of the transmission target system according to the authentication data frame request; and determining a deserialization data model and a serialization callback model according to the authentication result.

[0067] It should be understood that, as Figure 3The process of data authentication is shown, and the test case data stored by different automated test systems is different. The solution to the problem of data asset retention and reuse can greatly reduce labor costs and improve efficiency. At the same time, the problem of data partial loss caused by data adaptation between multiple systems is also well solved, ensuring the integrity of the data.

[0068] In a specific implementation, the authentication data frame request SC|DC|SM mainly carries the request information, mainly including three parts: source system characteristic code SC, destination system characteristic code DC, and source system to be converted plaintext SM. The structure of the data composition of the source system to be converted plaintext SM can be agreed as JSON, XML, etc.

[0069] It should be noted that after receiving the authentication data frame request, the SC and DC are authenticated and addressed before the corresponding data message exchange is made. When the authentication data frame request is obtained, the JSON, XML, etc. are parsed according to the agreed format, and the characteristic codes SC and DC are obtained. The characteristic code field does not need to be offset, and the authentication and addressing are performed in a direct addressing manner, as shown in the example Figure 4 .

[0070] It should be understood that after the authentication data frame request, SC|DC|SM is authenticated according to the characteristic code routing table, and the data frame request is replaced with XXX|XXX|SM, where "XXX" is a specific ID, and the data serialization and deserialization processing is performed by the storage and forwarding middleware program. Finally, the source system to be converted plaintext SM, the public serialization data PM, and the destination system plaintext DM data are stored and forwarded.

[0071] Further, in order to determine the model according to the authentication result or other operations, the step of determining the deserialization data model and the serialization callback data model according to the authentication result includes: when the authentication result is authentication success, querying the characteristic code routing table according to the source system characteristic code and the target system characteristic code to obtain a data model number and a data callback model number; and determining the deserialization data model and the serialization callback data model according to the data model number and the data callback model number.

[0072] In a specific implementation, if SC or DC is not in the characteristic code routing table, the authentication fails, and there is an unregistered system, then the data model addressing is not performed; if the authentication is successful, the SC data model number and the DC data callback model number are found in the characteristic code routing table.

[0073] Step S30: processing the data of the transmission source system and the transmission target system through the deserialization data model and the serialization callback data model to obtain the data to be exchanged.

[0074] It should be noted that after the deserialization data model and serialization callback data model are determined, the data of the transmission source system and the transmission target system also need to be processed respectively to obtain the to-be-exchanged data that can be directly transmitted and exchanged.

[0075] It should be understood that the relay exchange of the interface test data describes the process of exchanging the interface test design data between multiple systems, as shown in Figure 5 As shown in the figure, the underlying middleware program device receives and stores the entire data request message before making any operation decision. This method is beneficial to maintaining the integrity and validity of the data and is the key technology in the present application, which is used to solve the circulation problem of test design data between different systems, thereby greatly reducing the labor cost and improving the efficiency; at the same time, the data adaptation and data discard problems between multiple systems are solved, and the integrity of the data is ensured.

[0076] In specific implementation, the data relay exchange in the present application mainly adopts an "MID+" intelligent exchange strategy model, as shown in Figure 5 The main strategy model is the MID model and the MID callback model, and the access control process of multiple system data nodes is stored in the feature code routing table. The intelligent modeling is used to automatically complete the construction of the system node data model and the like, so as to ensure the smooth storage and forwarding between multiple system node data. The system data resource attributes are saved in the NOSQL library in the JavaScript Object Notation (JSON) format.

[0077] It should be noted that assuming that an automated test system A forwards the test cases and test data based on a certain information system to another automated test system B using the present method. The feature code ID of each system is used to identify system A and system B, and the attributes and attribute values of the test cases and test data are stored respectively.

[0078] It should be understood that CnA is a set of test case attributes of system A, CnB is a set of test case attributes of system B, CnP is a set of test case attributes common to the middleware, and CnID is a system feature code ID. The model strategy ModelID (MnID) is an ID that identifies the data model strategy. In the present method, the feature code and the model strategy form a set (CnID, MnID) that is stored in the feature code routing table.

[0079] C n A={C n ID,{C n A1,value},...,{C n A n ,value}}

[0080] C nP = {C n ID, {C n P1, value},..., {C n P n , value}}

[0081] C n B = {C n ID, {C n B1, value},..., {C n B n , value}}

[0082] M n = [{ID, M n ID}, {C n A1, C n P1},..., {C n A n , C n P n}]

[0083] Define CnP as the attribute set of the middleware program public relay, assuming that the set has data, and the partial attribute example of CnP data is as follows:

[0084] C1P = {3251, {"name", "use case data name"}, {"validate", "assertion verification"}, {"headers": "header information"}}

[0085] Similarly, CnA and CnB are the test design attribute sets of system A and system B respectively, and assuming that the system library mainly stores test cases, the partial attribute examples of CnA and CnB are as follows:

[0086] C1A = {61881, {"record_name", "fast payment"}, {"assertName", "payment success"}, {"head": "Content-Type: application / json"}} C1B = {eed8966b, {"name", "privacy agreement"}, {"assert", "sign successfully"}, {"header": "Content-Type: application / json"}}

[0087] In specific implementation, when the middleware program receives a data request of system A, two data exchange models are constructed, and the data model is deserialized into M1 and serialized callback model M2, i.e. MID and MID+1:

[0088] M1 = [{ID, M1ID}, {C n A1, Cn P1},...,{C n A n ,C n P n}]

[0089] M2=[{ID,M2ID},{C n P1,C n A1},...,{C n P n ,C n A n}]

[0090] Similarly, the "MID+" strategy model of system B is:

[0091] M3=[{ID,M3ID},{C n B1,C n P1},...,{C n B n ,C n P n}]

[0092] M4=[{ID,M4ID},{C n P1,C n B1},...,{C n P n ,C n B n}]

[0093] Further, in order to accurately determine the model corresponding to each system, step S30 comprises: determining a data processing strategy according to the deserialization data model and the serialization callback data model; determining system corresponding model information of the transmission source system and the transmission target system according to the data processing strategy; calling the deserialization data model and the serialization callback data model according to the system corresponding model information to process the data of the transmission source system and the transmission target system respectively, and obtaining the data to be exchanged.

[0094] It should be noted that, continuing the above example, the data source to the destination data needs to be deserialized and serialized, first, the model corresponding to each system needs to be determined, that is, the system corresponding model information, and finally the data of the transmission source system and the data of the transmission target system are processed according to the corresponding relationship to obtain the data to be exchanged. Therefore, the data storage forwarding strategy of system A to system B is M1M4, that is, the data of system A is deserialized, and then the data of system B is serialized and called back, that is,

[0095] M1M4={C1ID,{Map(C n A1,Cn B1),value},...,{Map(C n A n C n B m ),value}}

[0096] For example:

[0097] M1M4 = {bb60a574, {"name", "Quick Payment"}, {"assert", "Payment Successful"}, {"header": "Content-Type: application / json"}}

[0098] Conversely, the store-and-forward strategy for data from system B to system A is M3M2.

[0099] It should be understood that the "MID+1" intelligent exchange strategy model allows middleware programs to store plaintext data (SM) from system A, public data (PM), and plaintext data (DM) from system B using NoSQL. This strategy model ensures data integrity, smooth data exchange, and data traceability, preventing client systems from distrusting the model strategy. Through the above process, a manually written test design, using this invention, can achieve cross-platform, cross-regional, and multi-different acceptance system testing while ensuring data integrity. This enables automated testing of business products, improving delivery efficiency and reducing labor costs.

[0100] Step S40: Perform data relay exchange between the transmission source system and the transmission target system based on the data to be exchanged.

[0101] In practice, after the data to be exchanged is determined, data relay exchange is carried out directly through middleware or direct transmission to transmit data from the source system to the target system and vice versa.

[0102] The embodiment determines a transmission source system and a transmission target system according to the data relay exchange request when receiving the data relay exchange request, determines a deserialization data model and a serialization callback data model according to the data relay exchange request and a feature code routing table, processes data of the transmission source system and the transmission target system through the deserialization data model and the serialization callback data model to obtain to-be-exchanged data, and performs data relay exchange of the transmission source system and the transmission target system according to the to-be-exchanged data. In this way, the serialization data model and the serialization callback data model are used in the process of data relay exchange between test systems, and quick query and data encryption and decryption are performed through the construction of the feature code routing table, so that a cross-platform automatic test program can be constructed without relying on an upper test system platform, thereby ensuring the effectiveness of data.

[0103] Reference Figure 6 , Figure 6 The figure is a flowchart of a second embodiment of a data relay exchange method of the application.

[0104] Based on the first embodiment, the data relay exchange method further includes the following steps before the step S20.

[0105] Step S201: Obtain plaintext data information of the transmission source system and the transmission target system.

[0106] It should be noted that the acceptance system is described as a process of intermediate storage and generation of a data model for test case data of different test systems or platforms, as shown in FIG. 2. Figure 7 The data field names of different system platforms can be customized, but the variable names are irrelevant to the automation program, for example, the system A serialization data field passwd and the system B serialization data field password both represent the meaning of password. In order to ensure the accurate relationship between data, data annotation is required in the system entry stage, that is, the serialization data of the system to be entered is one-to-one mapped with the public storage field, so as to complete the system entry process. At the same time, in order to avoid errors caused by changes of serialization data templates of different versions of the same system, a feature code authentication is added to ensure the accuracy of system data. The main process of system entry is shown in FIG. 3. Figure 7

[0107] It should be understood that the plaintext data of the transmission source system and the transmission target system is first obtained as the plaintext data information.

[0108] Step S202: Construct an identification system feature code according to the plaintext data information.

[0109] ​In a specific implementation, the key information of the system A, such as the key field, system name, system version and the like, which is extracted from the plaintext data M, is arranged and combined in a string concatenation manner, and is assigned to TO_ENCRYPT, and an information digest ciphertext data C is generated by a hash function, and is recorded as a feature code of the system, that is, an identification system feature code, that is, C = PKe(TO_ENCRYPT).

[0110] Step S203: constructing a feature code routing table according to the identification system feature code.

[0111] It should be noted that after obtaining the identification system feature code, the feature code routing table is constructed according to the predetermined format according to the identification system feature code.

[0112] Further, in order to construct the feature code routing table, step S203 includes: determining an identification data model strategy feature code through a preset model identification code strategy; constructing a feature code set according to the identification system feature code and the identification data model strategy feature code; and constructing a feature code routing table according to the feature code set.

[0113] It should be understood that the middleware program receives the plaintext data M, performs deserialization, and completes the conversion of the plaintext data M to the public serialization document, so that the system plaintext data M and the public serialization document data can be matched one by one. In this process, the data model function of the deserialization of the plaintext data M is numbered, that is, MID, and the data model callback function of the serialization of the system plaintext data M of the public serialization document data is numbered as MID self-increment + 1.

[0114] In a specific implementation, the feature code routing table, as shown in Table 1, records the feature code and the data model ID respectively, and is mainly used for free conversion of the custom model of the system data. The proposal defaults two system data models, that is, the data model MID of the system and the data callback model, which are recorded as MID and MID+1 respectively. The system A plaintext data M and the deserialized public plaintext data PM are sequentially stored in the NOSQL database, two records are added in the feature code routing table to represent the data model and the data callback model, that is, (feature code, MID) and (feature code, MID+1), and the feature code is returned to the system to complete the system registration.

[0115] Table 1

[0116] Feature code Data model ID d2107fd5b8923a38462ad7ed32afabbf 5486 d2107fd5b8923a38462ad7ed32afabbf 5487 e5674ui8w889se365472ed7e51jafdes 6548 ... ...

[0117] It should be noted that according to the feature code routing table, the data model and the callback model of the corresponding system of the feature code can be addressed to find the corresponding system of the feature code, so as to realize the bidirectional retroaction of the test design among multiple systems.

[0118] The embodiment obtains plaintext data information of the transmission source system and the transmission target system, constructs an identification system feature code according to the plaintext data information, and constructs a feature code routing table according to the identification system feature code. When there are multiple user systems, test framework programs, tools or platforms, it is difficult for a person to ensure that the same test design and use case can be used in different regions and different system tools at the same time. The system settling feature code routing table proposed in the application constructs a feature code for different systems and allocates a data model, thereby improving data exchange efficiency and accuracy.

[0119] In addition, the embodiment of the application further provides a storage medium, wherein the storage medium stores a data relay exchange program, and the data relay exchange program is executed by a processor to implement the steps of the data relay exchange method.

[0120] Since the storage medium adopts all the technical solutions of the above-mentioned embodiments, it at least has all the beneficial effects brought by the technical solutions of the above-mentioned embodiments, which will not be repeated here.

[0121] In addition, the embodiment of the application further provides a computer program product, comprising a data relay exchange program, and the data relay exchange program is executed by a processor to implement the steps of the data relay exchange method.

[0122] The computer program product embodiment of the application is basically the same as the above-mentioned data relay exchange method embodiments, which will not be repeated here.

[0123] Reference Figure 8 , Figure 8 The figure is a structural block diagram of the first embodiment of the data relay exchange device of the application.

[0124] As Figure 8 shown, the data relay exchange device provided by the embodiment of the application comprises:

[0125] The system determination module 10 is configured to determine a transmission source system and a transmission target system according to a data relay exchange request when the data relay exchange request is received.

[0126] The model determination module 20 is configured to determine a deserialization data model and a serialization callback data model according to the data relay exchange request and the feature code routing table.

[0127] The data processing module 30 is configured to process data of the transmission source system and the transmission target system through the deserialization data model and the serialization callback data model to obtain to-be-exchanged data.

[0128] The data exchange module 40 is configured to perform data relay exchange of the transmission source system and the transmission target system according to the to-be-exchanged data.

[0129] The embodiment determines a transmission source system and a transmission target system according to the data relay exchange request when receiving the data relay exchange request; determines a deserialization data model and a serialization callback data model according to the data relay exchange request and a feature code routing table; processes data of the transmission source system and the transmission target system through the deserialization data model and the serialization callback data model to obtain to-be-exchanged data; and performs data relay exchange of the transmission source system and the transmission target system according to the to-be-exchanged data. In this way, the serialization data model and the serialization callback data model are used in the process of data relay exchange between test systems, and quick query and data encryption and decryption are performed through the construction of the feature code routing table, so that a cross-platform automatic test program can be constructed without relying on an upper test system platform, thereby ensuring the effectiveness of data.

[0130] In an embodiment, the model determination module 20 is further configured to acquire plaintext data information of the transmission source system and the transmission target system; construct an identification system feature code according to the plaintext data information; and construct a feature code routing table according to the identification system feature code.

[0131] In an embodiment, the model determination module 20 is further configured to determine an identification data model strategy feature code through a preset model identification code strategy; construct a feature code set according to the identification system feature code and the identification data model strategy feature code; and construct a feature code routing table according to the feature code set.

[0132] In an embodiment, the model determination module 20 is further configured to generate an authentication data frame request according to the data relay exchange request and the feature code routing table; perform authentication and addressing on a source system feature code of the transmission source system and a target system feature code of the transmission target system according to the authentication data frame request; and determine a deserialization data model and a serialization callback model according to an authentication result.

[0133] In an embodiment, the model determination module 20 is further configured to, when the authentication result is authentication success, query the feature code routing table according to the source system feature code and the target system feature code to obtain a data model number and a data callback model number; and determine a deserialization data model and a serialization callback data model according to the data model number and the data callback model number.

[0134] In an embodiment, the data processing module 30 is further configured to determine a data processing strategy according to the deserialization data model and the serialization callback data model; determine system corresponding model information of the transmission source system and the transmission target system according to the data processing strategy; and call the deserialization data model and the serialization callback data model to process data of the transmission source system and the transmission target system respectively according to the system corresponding model information, to obtain the data to be exchanged.

[0135] Other embodiments or specific implementations of the data relay exchange device of the present application can refer to the above-mentioned method embodiments, which will not be described here.

[0136] It should be understood that the above is only for illustration, and does not constitute any limitation on the technical solutions of the present application. In specific applications, those skilled in the art can set it up according to the needs, and the present application does not limit it.

[0137] It should be noted that the above-described workflow is only illustrative and does not limit the scope of protection of the present application. In actual application, those skilled in the art can select part or all of them according to actual needs to achieve the purpose of the present embodiment, which is not limited here.

[0138] In addition, technical details not described in detail in the present embodiment can refer to the data relay exchange method provided by any embodiment of the present application, which will not be described here.

[0139] In addition, it should be noted that in this paper, the term "includes", "contains" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or system including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or includes elements inherent to such process, method, article or system. Without more limitations, the element defined by the statement "includes a" does not exclude the presence of other identical elements in the process, method, article or system including the element.

[0140] The above-mentioned serial number of the embodiments of the present application is only for description, not representing the advantages and disadvantages of the embodiments.

[0141] Those skilled in the art can clearly understand the above-mentioned embodiment method can be realized by means of software and the necessary general hardware platform, of course, can also be through hardware, but in many cases the former is a better embodiment. Based on such understanding, the technical solutions of the present application essentially or say the part of the prior art contribution can be embodied in the form of software products, the computer software product is stored in a storage medium (such as read only memory (Read Only Memory, ROM) / RAM, disk, optical disk), including a number of instructions to make a terminal device (may be a mobile phone, computer, server, or network equipment, etc.) executes the method described in various embodiments of the present application.

[0142] The above is only the preferred embodiment of the present application, not therefore limit the patent scope of the present application, any equivalent structure or equivalent flow transformation made by using the content of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A data relay switching method characterized by, The data relay exchange method comprises the following steps: Upon receiving a data relay exchange request, determining a transmission source system and a transmission target system according to the data relay exchange request; According to the data relay exchange request and the feature code routing table, determining a deserialization data model and a serialization callback data model; Processing data of the transmission source system and the transmission target system through the deserialization data model and the serialization callback data model to obtain data to be exchanged; According to the data to be exchanged, performing data relay exchange of the transmission source system and the transmission target system; Before determining the deserialization data model and the serialization callback model according to the data relay exchange request and the feature code routing table, the method further comprises the following steps: Obtaining plaintext data information of the transmission source system and the transmission target system; According to the plaintext data information, constructing an identification system feature code; According to the identification system feature code and the identification data model strategy feature code, constructing a feature code set; According to the feature code set, constructing a feature code routing table. According to the data relay exchange request and the feature code routing table, generating an authentication data frame request; 2. The data relay switching method of claim 1, wherein, According to the authentication data frame request, authenticating and addressing a source system feature code of the transmission source system and a target system feature code of the transmission target system; According to the authentication result, determining the deserialization data model and the serialization callback model. When the authentication result is authentication success, according to the source system feature code and the target system feature code, querying the feature code routing table to obtain a data model number and a data callback model number; According to the data model number and the data callback model number, determining the deserialization data model and the serialization callback data model.

3. The data relay switching method of claim 2, wherein, According to the deserialization data model and the serialization callback data model, determining a data processing strategy; According to the data processing strategy, determining system corresponding model information of the transmission source system and the transmission target system; According to the system corresponding model information, calling the deserialization data model and the serialization callback data model to process data of the transmission source system and the transmission target system, respectively, to obtain data to be exchanged.

4. The data relay switching method of claim 1, wherein, The data relay exchange device comprises: A system determination module, configured to, upon receiving a data relay exchange request, determine a transmission source system and a transmission target system according to the data relay exchange request; A model determination module, configured to determine a deserialization data model and a serialization callback data model according to the data relay exchange request and a feature code routing table; ​ 5. A data relay switching device, characterized by comprising: ​ ​ ​ The model determination module is further configured to acquire plaintext data information of the transmission source system and the transmission target system; construct an identification system characteristic code according to the plaintext data information; determine an identification data model strategy characteristic code through a preset model identification code strategy; construct a characteristic code set according to the identification system characteristic code and the identification data model strategy characteristic code; and construct a characteristic code routing table according to the characteristic code set. The data processing module is configured to process data of the transmission source system and the transmission target system through the deserialization data model and the serialization callback data model to obtain to-be-exchanged data. The data exchange module is configured to perform data relay exchange of the transmission source system and the transmission target system according to the to-be-exchanged data.

6. A data relay switching device, characterized by, The data relay exchange device comprises a memory, a processor, and a data relay exchange program stored in the memory and running on the processor, and the data relay exchange program is configured to implement the data relay exchange method in any one of claims 1 to 4.

7. A storage medium, characterized by The storage medium stores a data relay exchange program, and the data relay exchange program is executed by the processor to implement the data relay exchange method in any one of claims 1 to 5.

8. A computer program product, characterised in that, The computer program product comprises a data relay exchange program, and the data relay exchange program is executed by the processor to implement the steps of the data relay exchange method in any one of claims 1 to 4.

Images