Cross-platform data interaction method and device, equipment and medium

Abstract

The invention discloses a cross-platform data interaction method and device, equipment and a medium, is applied to a server side and relates to the field of network services, and the method comprises the steps that a data response request sent by a user side is analyzed to determine a corresponding data processing instruction and to-be-processed data; performing corresponding processing on the to-be-processed data based on the data processing instruction, and recording corresponding data processing information; converting the data processing information based on a preset data format to generate a target response body based on the obtained target response information, and encrypting the target response body to obtain an encrypted target response body; the encrypted target response body is fed back to the user side, so that the user side decrypts the encrypted target response body, and information display is carried out based on target response information obtained through decryption. Therefore, a unified data type description standard is adopted, the problem of incompatibility of data formats is effectively solved, and the accuracy and efficiency of data exchange are improved.

Description

Technical Field

[0001] This invention relates to the field of network services, and in particular to a cross-platform data interaction method, apparatus, device, and medium. Background Technology

[0002] As enterprise IT infrastructure development deepens, the demand for data interaction and functional integration between different systems is growing. Web Services, as a remote invocation technology that transcends programming languages ​​and operating system platforms, provides a convenient solution for integrating different systems because it uses the standard SOAP (Simple Object Access Protocol) protocol to transmit data and WSDL (Web Services Description Language) as its description language. However, traditional Web Service applications often lack unified data type description standards and efficient interaction mechanisms, leading to problems such as data format incompatibility and low interaction efficiency during cross-system integration. Summary of the Invention

[0003] In view of this, the purpose of this invention is to provide a cross-platform data interaction method, apparatus, device, and medium, which adopts a unified data type description standard, effectively solving the problem of data format incompatibility and improving the accuracy and efficiency of data exchange. The specific solution is as follows:

[0004] Firstly, this application discloses a cross-platform data interaction method, applied to the server side, including:

[0005] If a data response request sent by the user is detected, the data response request is parsed to determine the data processing instructions and the data to be processed corresponding to the data response request; the data response request is a request corresponding to a preset data format;

[0006] The data to be processed is saved to a local database, and then the data to be processed is processed accordingly based on the data processing instructions, and the corresponding data processing information is recorded.

[0007] The data processing information is converted based on the preset data format to generate a target response body based on the obtained target response information, and the target response body is encrypted to obtain an encrypted target response body.

[0008] The encrypted target response body is fed back to the user terminal so that the user terminal can decrypt the encrypted target response body and display information based on the decrypted target response information.

[0009] Optionally, before parsing the data response request to determine the data processing instruction and the data to be processed corresponding to the data response request, if a data response request sent by the user terminal is detected, the method further includes:

[0010] Collect the interface information corresponding to each local interface, and use the interface information as server information;

[0011] Based on the server-side information, a service description document corresponding to a preset data format is generated; the interface information includes the interface service, service location, service operation, and message format corresponding to each interface.

[0012] Optionally, if a data response request sent by the user terminal is detected, the data response request is parsed to determine the data processing instructions and the data to be processed corresponding to the data response request, including:

[0013] If a data response request is received from the user, the data response request is parsed to determine the request content corresponding to the data response request; the data response request is a data response request generated by the user based on the server information in the server's service description document;

[0014] The request content is read based on a preset field to determine the request information corresponding to the preset field in the request content, and the data processing instructions and data to be processed corresponding to the data response request are determined based on the request information.

[0015] Optionally, the step of saving the data to be processed to a local database, then processing the data to be processed according to the data processing instructions, and recording the corresponding data processing information includes:

[0016] The data to be processed is saved to a local database, and the processing action corresponding to the data processing instruction is determined.

[0017] Based on the processing action, the data to be processed is processed accordingly, and the processing operation information and processing result corresponding to the data to be processed are recorded;

[0018] The processing operation information and the processing result are used as data processing information.

[0019] Optionally, the step of converting the data processing information based on the preset data format to generate a target response body based on the obtained target response information includes:

[0020] The data processing information is converted based on the preset data format to convert the data processing information into target response information corresponding to the preset data format, and a response body to be determined is generated based on the target response information.

[0021] Redundant information in the response body is identified and removed to obtain the target response body.

[0022] Optionally, encrypting the target response body to obtain an encrypted target response body includes:

[0023] Identify the information to be signed in the target response information and calculate the hash value of the information to be signed;

[0024] The hash value is encrypted using a preset key, and the resulting encrypted hash information is stored in the response header of the target response body.

[0025] The target response body is encrypted using a preset encryption algorithm to obtain the encrypted target response body.

[0026] Optionally, the cross-platform data interaction method further includes:

[0027] If the encrypted target response body is not successfully fed back to the user terminal, the transmission error type is determined, and the retry waiting time is calculated based on the exponential backoff algorithm and the transmission error type.

[0028] The encrypted target response body is fed back based on the retry waiting time.

[0029] Secondly, this application discloses a cross-platform data interaction device, applied to a server, comprising:

[0030] The request parsing module is used to parse the data response request if a data response request sent by the user terminal is detected, so as to determine the data processing instruction and the data to be processed corresponding to the data response request; the data response request is a request corresponding to a preset data format.

[0031] The information recording module is used to save the data to be processed to a local database, then process the data to be processed according to the data processing instructions, and record the corresponding data processing information.

[0032] The data encryption module is used to convert the data processing information based on the preset data format to generate a target response body based on the obtained target response information, and to encrypt the target response body to obtain an encrypted target response body.

[0033] The data feedback module is used to send the encrypted target response body back to the user terminal, so that the user terminal can decrypt the encrypted target response body and display information based on the decrypted target response information.

[0034] Thirdly, this application discloses an electronic device, comprising:

[0035] Memory, used to store computer programs;

[0036] A processor for executing the computer program to implement the cross-platform data interaction method as described above.

[0037] Fourthly, this application discloses a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the cross-platform data interaction method as described above.

[0038] In this application, if a data response request sent by the user terminal is detected, the data response request is parsed to determine the data processing instruction and the data to be processed corresponding to the data response request; the data response request is a request corresponding to a preset data format; the data to be processed is saved to a local database, and then the data to be processed is processed accordingly based on the data processing instruction, and the corresponding data processing information is recorded; the data processing information is converted based on the preset data format to generate a target response body based on the obtained target response information, and the target response body is encrypted to obtain an encrypted target response body; the encrypted target response body is fed back to the user terminal so that the user terminal can decrypt the encrypted target response body and display information based on the decrypted target response information.

[0039] Therefore, the method of this application allows for the parsing of data response requests sent by the user client. Upon detection, the received request can be parsed to determine the corresponding data processing instructions and the data to be processed. This data is then saved to a local database. The data processing instructions are used to process the data, and the processing process itself (i.e., data processing information) is recorded. This information is then converted to a preset data format, and a target response body is generated based on the converted target response information. The target response body is then encrypted and sent back to the user client, allowing the client to understand whether the data processing is complete and to view the results. This approach utilizes a unified data type description standard, ensuring that Web Service interfaces written in different programming languages ​​adhere to the same format specifications during data transmission. This effectively solves the problem of data format incompatibility and improves the accuracy and efficiency of data exchange. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0041] Figure 1 This is a flowchart of a cross-platform data interaction method disclosed in this application;

[0042] Figure 2 This is a schematic diagram of a request transmission interaction disclosed in this application;

[0043] Figure 3 This is an architecture diagram of a Web Service disclosed in this application;

[0044] Figure 4 This is a schematic diagram of the structure of a cross-platform data interaction device disclosed in this application;

[0045] Figure 5 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0046] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. 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 making creative efforts are within the scope of protection of the present invention.

[0047] Traditional Web Service applications lack unified data type description standards and efficient interaction mechanisms, leading to problems such as data format incompatibility and low interaction efficiency during cross-system integration.

[0048] To overcome the aforementioned technical problems, this application discloses a cross-platform data interaction method, apparatus, device, and medium, which adopts a unified data type description standard, effectively solving the problem of data format incompatibility and improving the accuracy and efficiency of data exchange.

[0049] See Figure 1 As shown, this embodiment of the invention discloses a cross-platform data interaction method, applied to the server side, including:

[0050] Step S11: If a data response request sent by the user terminal is detected, the data response request is parsed to determine the data processing instruction and the data to be processed corresponding to the data response request; the data response request is a request corresponding to a preset data format.

[0051] In this embodiment, before detecting data requests sent by the user client, a service description document (WSDL) needs to be constructed. The WSDL document allows the user client to directly determine various interface information of the server. Specifically, it requires collecting interface information corresponding to each local interface and using this information as server information. For example, the server may have three interfaces: A, B, and C. Each interface corresponds to a specific interface service, service location, service operation, and message format. Therefore, it is necessary to collect this interface information and generate a service description document based on the collected server information. To ensure consistent formatting across interfaces and readability of the service description document, the generated document uses a predefined data format, namely the XSD (XML Schema Datatypes) standard defined by the W3C (World Wide Web Consortium). It should be noted that the WSDL in this application has been improved to automatically generate client code from the WSDL, avoiding errors from manually parsing interface documents, improving development efficiency, and expanding the WSDL description capabilities. <documentation>The label details the business rules (such as "order amount must be greater than 0"), and supports... <xs:annotation>The semantics of the labeled fields are specified, for example, "Customer ID (Identity document) is a globally unique identifier".

[0052] Further, such as Figure 2 As shown, if the user client generates a data response request and sends it to the server, and the server receives the data response request, it can parse the data response request to determine the corresponding request content. The data response request is generated by the user client based on the server information in the server's service description document. It should be noted that the user client needs to refer to the service description document when generating the data response request. Since the user client does not process data locally and needs to generate a data response request to send to the server for data processing, the user client needs to refer to the service description document when generating the data response request. It can determine the corresponding interface based on the action required from the server and generate the data response request based on the interface information corresponding to that interface in the service description document. For example, if the server needs to delete certain data, it needs to find the interface corresponding to the deletion operation in the service description document and generate the data response request based on the interface information of that interface in the service description document. After the request is parsed, the request content can be read based on preset fields to determine the request information corresponding to the preset fields. Based on this request information, the data processing instructions and data to be processed corresponding to the data response request can then be determined. It should be noted that reading the request content based on preset fields allows direct retrieval of operation-related information from the request content.

[0053] Step S12: Save the data to be processed to the local database, then process the data to be processed according to the data processing instructions, and record the corresponding data processing information.

[0054] In this embodiment, the data to be processed needs to be saved to a local database, and then processed accordingly. Specifically, the data to be processed needs to be saved to the local database, and the processing action corresponding to the data processing instruction needs to be determined. Based on the processing action, the data to be processed is processed accordingly. For example, if the processing action corresponding to the data processing instruction is a specific item among CRUD operations on the data, and the data to be processed is a user's user information, then the corresponding CRUD operations need to be performed on the user's user information locally on the server side. Furthermore, the processing operation information and processing results corresponding to the data to be processed need to be recorded, and then the processing operation information and processing results are used as data processing information. It should be noted that the recorded data processing information can reflect which processing steps the data has undergone, what its transformation logic is, what the final processing result is, and if a data processing error occurs, it can be traced back based on the data processing information, effectively reducing the risk of data processing.

[0055] Step S13: Convert the data processing information based on the preset data format to generate a target response body based on the obtained target response information, and encrypt the target response body to obtain an encrypted target response body.

[0056] In this embodiment, the data processing information needs to be converted according to a preset data format, and then a target response body is generated based on the converted target response information. Specifically, the data processing information needs to be converted based on the preset data format to convert it into target response information corresponding to the preset data format, and a response body to be determined is generated based on the target response information. It should be noted that, to ensure cross-platform data transmission, the data processing information needs to be converted using a preset data format, and the message body generated after the data processing information is converted strictly follows the W3C XSD standard. This ensures that Web Service interfaces generated in any language (Java, C#, Python, etc.) can be uniformly converted to XSD format, which is the cross-platform capability mentioned in this application. This eliminates data type ambiguities caused by language characteristics in traditional solutions, such as date formats and floating-point precision. This effectively reduces type conversion errors. Furthermore, after the response body is generated, it needs to be transmitted via the SOAP protocol. The SOAP protocol in this application is an improved SOAP protocol, which simplifies the SOAP envelope, removes duplicate namespace declarations and redundant header information, and reduces the size of the SOAP message. It also supports dynamic protocol adaptation, supporting multiple protocols such as HTTP (Hypertext Transfer Protocol) / HTTPS (Hypertext Transfer Protocol Secure), FTP (File Transfer Protocol), and MQTT (Message Queuing Telemetry Transport) through the abstraction layer, which can adapt to various scenarios.

[0057] Furthermore, the generated target response body needs to be encrypted. Specifically, the information to be signed in the target response information needs to be determined, and the hash value of the information to be signed needs to be calculated. This hash value needs to be encrypted using the private key in the preset key, and then the resulting encrypted hash information is stored in the response header of the target response body. Finally, the target response body is encrypted using a preset encryption algorithm, such as SSL (Secure Sockets Layer) or TLS (Transport Layer Security), to obtain the encrypted target response body. This ensures the security, integrity, and non-repudiation of message transmission.

[0058] Step S14: The encrypted target response body is fed back to the user terminal so that the user terminal can decrypt the encrypted target response body and display information based on the decrypted target response information.

[0059] In this embodiment, the encrypted target response body can be fed back to the user terminal so that the user terminal can decrypt the encrypted target response body and display the information based on the decrypted target response message. Specifically, after receiving the encrypted target response body fed back by the server, the user terminal needs to decrypt the encrypted response body using the local public key and the decryption algorithm corresponding to the encryption algorithm, and then display the content in the decrypted target response body. In this way, the user can be informed of the data processing status in real time, which effectively improves the user experience.

[0060] In this embodiment, if a data response request sent by the user terminal is detected, the received request can be parsed, and then the data processing instruction corresponding to the data response request and the corresponding data to be processed can be determined. The data to be processed is saved to the local database, and then the data to be processed is processed according to the data processing instruction. The data processing process, i.e., data processing information, also needs to be recorded. Then, the data processing information needs to be converted into a preset data format, and a target response body is generated based on the target response information obtained after conversion. Then, the target response body needs to be encrypted, and the encrypted target response body is fed back to the user terminal so that the user terminal can know whether the data has been processed and display the processing result. In this way, on the one hand, by adopting a unified XSD data type description standard, it is ensured that Web Service interfaces written in different programming languages ​​follow the same format specifications during data transmission, effectively solving the problem of data format incompatibility and improving the accuracy and efficiency of data exchange; on the other hand, by optimizing the SOAP protocol, redundant data during transmission is reduced, significantly improving data transmission efficiency, reducing network bandwidth consumption, and improving system response speed; and on the other hand, by using the WSDL description language to provide detailed interface specifications for Web Services, the complexity and risk of system integration are reduced, enabling developers to understand and integrate Web Services more quickly, thus improving development efficiency.

[0061] In a preferred embodiment, message transmission failures may occur in some situations. When such failures happen, the message can be retransmitted. Specifically, if the encrypted target response is not successfully sent to the user, the transmission error type is determined, such as network timeout or service unavailability. A retry waiting time is calculated based on the exponential backoff algorithm and the transmission error type, and this retry waiting time is used as the interval for retransmission. This retry waiting time can be dynamically adjusted, and the encrypted target response needs to be retransmitted according to the retry waiting time. In this way, by dynamically adjusting the retry waiting time, the avalanche effect caused by traditional fixed retries can be avoided.

[0062] Furthermore, to improve system reliability, a Web Service performance monitoring system needs to be established to monitor key performance indicators such as response time and throughput of the Web Service in real time. Based on the performance monitoring results, the Web Service can be optimized and adjusted, including adjusting the transmission protocol, optimizing data format, and adding caching mechanisms to improve overall performance. The Web Service performance monitoring system can also display information through a social real-time monitoring dashboard, visually displaying indicators such as response time, error rate, and throughput, and setting threshold alarms, such as triggering an alarm for a response time greater than 500ms.

[0063] See Figure 3 The diagram shown illustrates the architecture of the Web Service in this application. The client layer represents the clients using the Web Service, signifying different callers and demonstrating that the system can support simultaneous access from multiple clients. The Web Service layer is the core of the Web Service, defining various service interfaces provided externally. Clients send requests through these interfaces and receive returned data. The interface layer handles basic operations such as request format validation and parameter parsing, then forwards the request to the corresponding business logic processing module. The data synchronization module is responsible for data interaction and synchronization between the Web Service node and the storage layer. It ensures that the data processed by the Web Service is stored in the database in a timely and accurate manner, and can retrieve data from the database and return it to the client when needed.

[0064] See Figure 4 As shown, this embodiment of the invention discloses a cross-platform data interaction device applied to a server, comprising:

[0065] The request parsing module 11 is used to parse the data response request if a data response request sent by the user terminal is detected, so as to determine the data processing instruction and the data to be processed corresponding to the data response request; the data response request is a request corresponding to a preset data format.

[0066] The information recording module 12 is used to save the data to be processed to a local database, then process the data to be processed according to the data processing instructions, and record the corresponding data processing information.

[0067] The data encryption module 13 is used to convert the data processing information based on the preset data format to generate a target response body based on the obtained target response information, and to encrypt the target response body to obtain an encrypted target response body.

[0068] The data feedback module 14 is used to feed back the encrypted target response body to the user terminal, so that the user terminal can decrypt the encrypted target response body and display information based on the decrypted target response information.

[0069] In this embodiment, if a data response request sent by the user terminal is detected, the received request can be parsed to determine the corresponding data processing instructions and the data to be processed. The data to be processed is then saved to a local database. The data processing instructions are then used to process the data, and the data processing process (i.e., data processing information) is recorded. This data processing information is then converted to a preset data format, and a target response body is generated based on the converted target response information. The target response body is then encrypted and sent back to the user terminal so that the user can understand whether the data processing is complete and to see the processing result. This approach uses a unified data type description standard, ensuring that Web Service interfaces written in different programming languages ​​follow the same format specifications during data transmission, effectively solving the problem of data format incompatibility and improving the accuracy and efficiency of data exchange.

[0070] In some embodiments, the cross-platform data interaction device may further include:

[0071] An information collection unit is used to collect interface information corresponding to each local interface and use the interface information as server information.

[0072] The document generation unit is used to generate a service description document corresponding to a preset data format based on the server information; the interface information includes the interface service, service location, service operation and message format corresponding to each interface.

[0073] In some embodiments, the request parsing module 11 may specifically include:

[0074] The request parsing unit is used to parse the data response request sent by the user terminal if it receives the data response request, so as to determine the request content corresponding to the data response request; the data response request is a data response request generated by the user terminal based on the server information in the service description document of the server.

[0075] The content reading unit is used to read the request content based on a preset field to determine the request information in the request content corresponding to the preset field, and to determine the data processing instruction and the data to be processed corresponding to the data response request based on the request information.

[0076] In some embodiments, the information recording module 12 may specifically include:

[0077] The processing action determination unit is used to save the data to be processed to a local database and determine the processing action corresponding to the data processing instruction.

[0078] A data processing unit is used to process the data to be processed according to the processing action, and to record the processing operation information and processing results corresponding to the data to be processed.

[0079] An information determination unit is used to treat the processing operation information and the processing result as data processing information.

[0080] In some embodiments, the data encryption module 13 may specifically include:

[0081] The response body generation unit is used to convert the data processing information based on the preset data format to convert the data processing information into target response information corresponding to the preset data format, and generate a response body to be determined based on the target response information.

[0082] A redundancy removal unit is used to identify redundant information in the response body and remove the redundant information to obtain the target response body.

[0083] In some embodiments, the data feedback module 14 may specifically include:

[0084] A hash calculation unit is used to determine the information to be signed in the target response information and to calculate the hash value of the information to be signed.

[0085] An information storage unit is used to encrypt the hash value based on a preset key and store the resulting encrypted hash information in the response header of the target response body;

[0086] The response body encryption unit is used to encrypt the target response body based on a preset encryption algorithm to obtain the encrypted target response body.

[0087] In some embodiments, the cross-platform data interaction device may further include:

[0088] The time calculation unit is used to determine the transmission error type if the encrypted target response body is not successfully fed back to the user terminal, and to calculate the retry waiting time based on the exponential backoff algorithm and the transmission error type.

[0089] The feedback retry unit is used to re-feed back the encrypted target response body according to the retry waiting time.

[0090] Furthermore, embodiments of this application also disclose an electronic device, Figure 5 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.

[0091] Figure 5 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the cross-platform data interaction method disclosed in any of the foregoing embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0092] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0093] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon can include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0094] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including computer programs capable of performing the cross-platform data interaction method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0095] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned cross-platform data interaction method. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0096] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0097] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0098] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0099] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0100] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.< / xs:annotation> < / documentation>

Claims

1. A cross-platform data interaction method, characterized in that, Applied to the server side, including: If a data response request sent by the user is detected, the data response request is parsed to determine the data processing instruction and the data to be processed corresponding to the data response request; the data response request is a request corresponding to a preset data format; The data to be processed is saved to a local database, and then the data to be processed is processed accordingly based on the data processing instructions, and the corresponding data processing information is recorded. The data processing information is converted based on the preset data format to generate a target response body based on the obtained target response information, and the target response body is encrypted to obtain an encrypted target response body. The encrypted target response body is fed back to the user terminal so that the user terminal can decrypt the encrypted target response body and display information based on the decrypted target response information.

2. The cross-platform data interaction method according to claim 1, characterized in that, Before parsing the data response request to determine the data processing instruction and the data to be processed corresponding to the data response request, if a data response request is detected from the user terminal, the method further includes: Collect the interface information corresponding to each local interface, and use the interface information as server information; Based on the server-side information, a service description document corresponding to a preset data format is generated; the interface information includes the interface service, service location, service operation, and message format corresponding to each interface.

3. The cross-platform data interaction method according to claim 2, characterized in that, If a data response request sent by the user terminal is detected, the data response request is parsed to determine the data processing instructions and the data to be processed corresponding to the data response request, including: If a data response request is received from the user, the data response request is parsed to determine the request content corresponding to the data response request; the data response request is a data response request generated by the user based on the server information in the server's service description document; The request content is read based on a preset field to determine the request information corresponding to the preset field in the request content, and the data processing instructions and data to be processed corresponding to the data response request are determined based on the request information.

4. The cross-platform data interaction method according to claim 1, characterized in that, The process involves saving the data to be processed to a local database, then processing the data based on the data processing instructions, and recording the corresponding data processing information, including: The data to be processed is saved to a local database, and the processing action corresponding to the data processing instruction is determined. Based on the processing action, the data to be processed is processed accordingly, and the processing operation information and processing result corresponding to the data to be processed are recorded; The processing operation information and the processing result are used as data processing information.

5. The cross-platform data interaction method according to claim 1, characterized in that, The step of converting the data processing information based on the preset data format to generate a target response body based on the obtained target response information includes: The data processing information is converted based on the preset data format to convert the data processing information into target response information corresponding to the preset data format, and a response body to be determined is generated based on the target response information. Redundant information in the response body is identified and removed to obtain the target response body.

6. The cross-platform data interaction method according to claim 1, characterized in that, The step of encrypting the target response body to obtain the encrypted target response body includes: Identify the information to be signed in the target response information and calculate the hash value of the information to be signed; The hash value is encrypted using a preset key, and the resulting encrypted hash information is stored in the response header of the target response body. The target response body is encrypted using a preset encryption algorithm to obtain the encrypted target response body.

7. The cross-platform data interaction method according to any one of claims 1 to 6, characterized in that, Also includes: If the encrypted target response body is not successfully fed back to the user terminal, the transmission error type is determined, and the retry waiting time is calculated based on the exponential backoff algorithm and the transmission error type. The encrypted target response body is fed back based on the retry waiting time.

8. A cross-platform data interaction device, characterized in that, Applied to the server side, including: The request parsing module is used to parse the data response request if a data response request sent by the user terminal is detected, so as to determine the data processing instruction and the data to be processed corresponding to the data response request; the data response request is a request corresponding to a preset data format. The information recording module is used to save the data to be processed to a local database, then process the data to be processed according to the data processing instructions, and record the corresponding data processing information. The data encryption module is used to convert the data processing information based on the preset data format to generate a target response body based on the obtained target response information, and to encrypt the target response body to obtain an encrypted target response body. The data feedback module is used to send the encrypted target response body back to the user terminal, so that the user terminal can decrypt the encrypted target response body and display information based on the decrypted target response information.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the cross-platform data interaction method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, Used to store computer programs, wherein the computer programs, when executed by a processor, implement the cross-platform data interaction method as described in any one of claims 1 to 7.

Images