A data interaction method, device and medium for different architecture applications

By setting up middleware in the terminal to receive, store and forward Socket encrypted messages, the permission problem of data interaction between cross-architecture applications is solved, and secure and flexible data transmission is realized, which is suitable for systems with strict permissions.

CN117061205BActive Publication Date: 2024-12-06INSPUR GENERSOFT CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311111181.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-08-30
Publication Date
2024-12-06
Estimated Expiration
2043-08-30

AI Technical Summary

Technical Problem

In systems with strict user system permissions, traditional registry protocols are difficult to achieve data interaction between different types of applications, especially when cross-architecture data transmission between C/S architecture and B/S architecture.

Method used

By setting up middleware in the terminal, receiving and forwarding Socket encrypted messages, using message parser, message receiver, message memory and message sender for message processing and storage, and auditing and monitoring through message monitors, ensuring the security of messages Pass and parse.

Benefits of technology

It realizes data interaction between cross-architecture applications, avoids modification of the system registry, ensures the security and flexibility of data exchange, and is suitable for systems with strict permissions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117061205B_ABST
    Figure CN117061205B_ABST
Patent Text Reader

Abstract

The present application discloses a data interaction method, device and medium for different architecture applications, the method includes: determining multiple applications and middleware set in the terminal; receiving the Socket encrypted message sent by the sender through the middleware; storing the Socket encrypted message and forwarding the Socket encrypted message to the receiving end; parsing the Socket encrypted message based on the agreed form through the receiving end to obtain the interaction message. There is no need to change the system registry, and cross-architecture data interaction can be completed. As a middleware, it is not coupled with the browser page application and the local client application to be integrated. The browser page application and the local client application that need to interact only need to send the Socket encrypted message to the middleware in the form agreed by the middleware. The middleware will not perceive the content of the message body and feedback the corresponding Socket encrypted message. After receiving the Socket encrypted message, the receiving end can parse and process the message according to the agreement with the sending end to ensure the security of data exchange.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a data interaction method, device and medium for different architecture applications. Background Art

[0002] As enterprise informatization deepens, users will use both local client applications with C / S architecture and browser applications with B / S architecture in their office work. When completing tasks supported by different business systems, users may need to transfer intermediate results between applications with different architectures.

[0003] In the traditional solution, the registry protocol can be used in the Windows operating system to achieve data interaction between different types of applications. The local client application writes the registry protocol, and the browser calls the custom registry protocol to complete the data interaction. However, in some systems with strict user system permission restrictions, there may be situations where applications are not allowed to modify the registry. In this case, this solution is difficult to implement. Summary of the invention

[0004] In order to solve the above problems, this application proposes a data interaction method for different architecture applications, including:

[0005] Determine a plurality of applications and middlewares set in the terminal, wherein the plurality of applications at least include applications implemented by different architectures, including a C / S architecture and a B / S architecture;

[0006] Receiving, through the middleware, a Socket encrypted message sent by a sender, the sender belonging to an application in the multiple applications, the Socket encrypted message being obtained by encrypting an interactive message based on an agreed form;

[0007] The Socket encrypted message is stored, and the Socket encrypted message is forwarded to a receiving end, where the receiving end belongs to an application among the multiple applications and is implemented by a different architecture from the sending end;

[0008] The receiving end parses the Socket encrypted message based on the agreed form to obtain the interactive message.

[0009] In one example, before receiving the Socket encrypted message sent by the sender through the middleware, the method further includes:

[0010] Determine a message parser included in the middleware;

[0011] The message parser provides a definition of the message format and a meaning rule analysis, so that the sender and the receiver can generate an agreed form based on the definition of the message format and the meaning rule analysis.

[0012] In one example, storing the Socket encrypted message specifically includes:

[0013] Determine the message receiver and message storage included in the middleware;

[0014] Receiving the Socket encrypted message through the message receiver, and sending the Socket encrypted message to the message storage;

[0015] The Socket encrypted message is stored in a persistent manner in a classified queue according to the message header through the message storage.

[0016] In one example, forwarding the Socket encrypted message to a receiving end specifically includes:

[0017] Determining a message sender included in the middleware;

[0018] Through the message transmitter, the Socket encrypted message is extracted in the message storage according to the first set frequency, and the extracted Socket encrypted message is sent to the receiving end. After the Socket encrypted message is delivered to the receiving end, message delivery confirmation information is provided, and after the Socket encrypted message is not successfully delivered to the receiving end, a retry mechanism is provided.

[0019] In one example, the method further includes:

[0020] For high-frequency message interactions, the message storage provides message queue support to store the Socket encrypted message in the message queue, wherein the high frequency refers to the frequency corresponding to the number of message interactions within a preset time period being higher than a preset number;

[0021] Extracting, by the message transmitter, Socket encrypted messages in the message memory at a second set frequency, and sending the extracted Socket encrypted messages to a receiving end, wherein the second set frequency is faster than the first set frequency;

[0022] After the Socket encrypted message is delivered to the receiving end, message delivery confirmation information is provided, and after the Socket encrypted message is not successfully delivered to the receiving end, a retry mechanism is provided, and the corresponding number of retries in the retry mechanism is configured based on the message header matching rule.

[0023] In one example, the method further includes:

[0024] determining a message monitor included in the middleware;

[0025] The storage and consumption of the Socket encrypted message are monitored and audited through the message monitor.

[0026] In one example, the storage and consumption of the Socket encrypted message are monitored and audited by the message monitor, specifically including:

[0027] When the storage and consumption status of the Socket encrypted message are monitored through the message monitor, the storage status and the consumption status are recorded. The storage status includes: determining that the message receiver has received the Socket encrypted message, determining that the message storage stores the Socket encrypted message, and the consumption status includes: determining that the message sender extracts the Socket encrypted message, determining that the message sender has completed sending the Socket encrypted message, determining that the message sender has received a response, and determining that the message sender has timed out due to not receiving a response.

[0028] In one example, the method further includes:

[0029] Through the message monitor, the corresponding severity level is determined according to the monitored storage and consumption conditions, and when the monitored storage and consumption conditions are displayed to the user, the corresponding severity level is displayed simultaneously, wherein multiple severity levels are set for the storage conditions or the consumption conditions.

[0030] On the other hand, the present application also proposes a data interaction device for different architecture applications, including:

[0031] at least one processor; and,

[0032] a memory communicatively connected to the at least one processor; wherein,

[0033] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the data interaction method for different architecture applications as described in any of the above examples.

[0034] On the other hand, the present application also proposes a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured as: a data interaction method for different architecture applications as described in any of the above examples.

[0035] The data interaction method proposed in this application for different architecture applications can bring the following beneficial effects:

[0036] Compared with the traditional registry protocol, this application does not need to change the system registry and can also complete cross-architecture data interaction. As a middleware, it is not coupled with the browser page application and local client application to be integrated. The browser page application and local client application that need to interact only need to send Socket encrypted messages to the middleware in the form agreed by the middleware. The middleware will not perceive the content of the message body and feedback the corresponding Socket encrypted message. After receiving the Socket encrypted message, the receiving end can parse and process the message according to the agreement with the sending end to ensure the security of data exchange. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0038] Figure 1 A flowchart of a data interaction method for different architecture applications in an embodiment of the present application;

[0039] Figure 2 A schematic diagram of the architecture composed of various terminals and middleware in an embodiment of the present application;

[0040] Figure 3 This is a schematic diagram showing the simultaneous display of severity levels in an embodiment of the present application;

[0041] Figure 4 This is a schematic diagram of a data interaction method and device for different architecture applications in an embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0043] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0044] like Figure 1 As shown, the embodiment of the present application provides a data interaction method for different architecture applications, including:

[0045] S101: Determine a plurality of applications and middlewares set in a terminal, wherein the plurality of applications at least include applications implemented by different architectures, including a C / S architecture and a B / S architecture.

[0046] like Figure 2 As shown, the middleware can be set up locally in the terminal and belong to the same terminal with multiple other applications. C / S architecture refers to the server-client architecture, that is, the Client-Server (C / S) architecture. The C / S architecture usually adopts a two-layer structure. The server is responsible for data management, and the client is responsible for completing the interactive tasks with the user. The B / S structure (Browser / Server, browser / server mode) is a network structure model after the rise of WEB. The WEB browser is the most important application software on the client.

[0047] S102: receiving, through the middleware, a Socket encrypted message sent by a sender, where the sender belongs to an application among the multiple applications, and the Socket encrypted message is obtained by encrypting an interactive message based on an agreed form.

[0048] The sending end can be an application based on a C / S architecture or an application based on a B / S architecture.

[0049] like Figure 2 As shown, it is determined that the middleware contains a message parser. The message parser provides the definition of the message format and the parsing of the meaning rules. At this time, the sender and the receiver can generate an agreed form based on the definition of the message format and the parsing of the meaning rules. The message parser only provides the definition of the format and the meaning rules, but does not provide a specific agreed form. The agreed form is customized and generated between the two, so the final Socket encrypted message can only be parsed between the two. The sender encrypts the interactive message through the agreed form to obtain the Socket encrypted message.

[0050] S103: storing the Socket encrypted message, and forwarding the Socket encrypted message to a receiving end, where the receiving end belongs to an application among the multiple applications and is implemented through a different architecture from the sending end.

[0051] like Figure 2 As shown, the middleware includes a message receiver and a message storage. The message receiver receives the Socket encrypted message and sends the Socket encrypted message to the message storage. The message storage performs persistent storage of the Socket encrypted message in a classified queue according to the message header.

[0052] like Figure 2As shown, the middleware includes a message transmitter. Through the message transmitter, the Socket encrypted message is extracted in the message storage according to the first set frequency, and the extracted Socket encrypted message is sent to the receiving end. After the Socket encrypted message is delivered to the receiving end, the receiving end will return the feedback information received. The middleware can provide message delivery confirmation information (for example, a dialog box pops up on the front-end interface to show that it has been delivered, or a corresponding delivery column is set on the front-end interface for display), and after the Socket encrypted message is not successfully delivered to the receiving end, a retry mechanism is provided. If the user clicks retry, the Socket encrypted message that was not successfully delivered can be resent.

[0053] Furthermore, for high-frequency message interactions (high frequency refers to the frequency corresponding to the number of message interactions within a preset time period being higher than the preset number), message queue support is provided through the message storage to store Socket encrypted messages in the message queue, thereby preventing the impact of high-frequency interactions from spreading to the message sender and even affecting the receiving application system.

[0054] Through the message transmitter, in the message storage, the Socket encrypted message is extracted according to the second set frequency (since it is aimed at high-frequency message interaction at this time, the second set frequency is faster than the first set frequency), and the extracted Socket encrypted message is sent to the receiving end, thereby achieving faster message sending.

[0055] After the Socket encrypted message is delivered to the receiving end, message delivery confirmation information is provided. After the Socket encrypted message is not successfully delivered to the receiving end, a retry mechanism is provided. The corresponding number of retries in the retry mechanism is configured based on the message header matching rules. For example, different message headers represent the behavior of the message, so the behavior of the message can be judged based on the message header, so that different retry times can be set in advance for different behaviors. The more important the behavior, the more retries.

[0056] S104: Parsing the Socket encrypted message based on the agreed format through the receiving end to obtain the interactive message.

[0057] Since the agreed form is agreed upon between the receiving end and the sending end, the receiving end can parse the Socket encrypted message to obtain the interactive message.

[0058] Compared with the traditional registry protocol, this application does not need to change the system registry and can also complete cross-architecture data interaction. As a middleware, it is not coupled with the browser page application and local client application to be integrated. The browser page application and local client application that need to interact only need to send Socket encrypted messages to the middleware in the form agreed by the middleware. The middleware will not perceive the content of the message body and feedback the corresponding Socket encrypted message. After receiving the Socket encrypted message, the receiving end can parse and process the message according to the agreement with the sending end to ensure the security of data exchange.

[0059] In one embodiment, Figure 2 As shown in FIG. 1 , the middleware includes a message monitor, through which the storage and consumption of the socket encrypted messages are monitored and audited, so as to facilitate the tracing of the complete interaction process.

[0060] Specifically, when the storage and consumption status of the Socket encrypted message are monitored through the message monitor, the storage and consumption status are recorded, wherein the storage status includes: determining that the message receiver receives the Socket encrypted message, determining that the message storage stores the Socket encrypted message, and the consumption status includes: determining that the message sender extracts the Socket encrypted message, determining that the message sender completes sending the Socket encrypted message, determining that the message sender receives a response, and determining that the message sender times out due to not receiving a response.

[0061] Furthermore, the message monitor determines the corresponding severity level according to the monitored storage and consumption conditions, and Figure 3 As shown, when displaying the monitored storage and consumption situations to the user, the corresponding severity levels are displayed synchronously, wherein multiple severity levels are set for the storage situation or the consumption situation. For example, two severity levels, "serious" and "normal", are set, corresponding to different storage situations and situations when different events occur in the consumption situation. Of course, the interactive message name, type, recording time, module, sending source (corresponding to the sending end), receiving party (corresponding to the receiving end), operation details and other contents can also be displayed to the user. A filtering module is also provided so that users can quickly filter the content they need to query through keywords or drop-down menus.

[0062] like Figure 4 As shown, the embodiment of the present application also provides a data interaction device for different architecture applications, including:

[0063] at least one processor; and,

[0064] a memory communicatively connected to the at least one processor; wherein,

[0065] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the data interaction method for different architecture applications as described in any of the above embodiments.

[0066] An embodiment of the present application further provides a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured as: the data interaction method for different architecture applications described in any of the above embodiments.

[0067] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0068] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0069] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0070] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0071] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0072] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0073] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0074] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0075] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0076] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0077] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A data interaction method for different architecture applications, characterized in that: include: Determine a plurality of applications and middlewares set in the terminal, wherein the plurality of applications at least include applications implemented by different architectures, including a C / S architecture and a B / S architecture; Receiving, through the middleware, a Socket encrypted message sent by a sender, the sender belonging to an application in the multiple applications, the Socket encrypted message being obtained by encrypting an interactive message based on an agreed form; The Socket encrypted message is stored, and the Socket encrypted message is forwarded to a receiving end, where the receiving end belongs to an application among the multiple applications and is implemented through a different architecture from the sending end; Parsing the Socket encrypted message based on the agreed form by the receiving end to obtain the interactive message; Before receiving the Socket encrypted message sent by the sender through the middleware, the method further includes: Determine a message parser included in the middleware; The message parser provides a definition of the message format and a meaning rule analysis, so that the sender and the receiver can generate an agreed form based on the definition of the message format and the meaning rule analysis; Storing the Socket encrypted message specifically includes: Determine the message receiver and message storage included in the middleware; Receiving the Socket encrypted message through the message receiver, and sending the Socket encrypted message to the message storage; The Socket encrypted message is stored in a persistent manner in a classified queue according to the message header by using the message storage; Forwarding the Socket encrypted message to the receiving end specifically includes: Determining a message sender included in the middleware; Extracting the Socket encrypted message in the message memory according to the first set frequency through the message transmitter, and sending the extracted Socket encrypted message to the receiving end, and providing message delivery confirmation information after the Socket encrypted message is delivered to the receiving end, and providing a retry mechanism after the Socket encrypted message is not successfully delivered to the receiving end; The method further comprises: For high-frequency message interactions, the message storage provides message queue support to store the Socket encrypted message in the message queue, wherein the high frequency refers to the frequency corresponding to when the number of message interactions within a preset time period is higher than a preset number; Extracting, by the message transmitter, Socket encrypted messages in the message memory at a second set frequency, and sending the extracted Socket encrypted messages to a receiving end, wherein the second set frequency is faster than the first set frequency; After the Socket encrypted message is delivered to the receiving end, message delivery confirmation information is provided, and after the Socket encrypted message is not successfully delivered to the receiving end, a retry mechanism is provided, and the corresponding number of retries in the retry mechanism is configured based on the message header matching rule.

2. The method according to claim 1, characterized in that The method further comprises: determining a message monitor included in the middleware; The storage and consumption of the Socket encrypted message are monitored and audited through the message monitor.

3. The method according to claim 2, characterized in that The storage and consumption of the Socket encrypted message are monitored and audited by the message monitor, specifically including: When the storage and consumption status of the Socket encrypted message are monitored through the message monitor, the storage status and the consumption status are recorded. The storage status includes: determining that the message receiver has received the Socket encrypted message, determining that the message storage stores the Socket encrypted message, and the consumption status includes: determining that the message sender extracts the Socket encrypted message, determining that the message sender has completed sending the Socket encrypted message, determining that the message sender has received a response, and determining that the message sender has timed out due to not receiving a response.

4. The method according to claim 3, characterized in that The method further comprises: Through the message monitor, the corresponding severity level is determined according to the monitored storage and consumption conditions, and when the monitored storage and consumption conditions are displayed to the user, the corresponding severity level is displayed simultaneously, wherein multiple severity levels are set for the storage conditions or the consumption conditions.

5. A data interaction device for different architecture applications, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the data interaction method for different architecture applications as described in any one of claims 1 to 4.

6. A non-volatile computer storage medium storing computer executable instructions, characterized in that: The computer executable instructions are configured as: a data interaction method for different architecture applications as described in any one of claims 1 to 4.