CN117194068A - Cross-process data transmission method, system, equipment and storage medium - Google Patents

Abstract

The embodiment of the invention discloses a cross-process data transmission method, a system, equipment and a storage medium, which comprise the following steps: when receiving a data transmission instruction, the software application end generates data transmission request information according to the data transmission instruction and sends the data transmission request information to a local server through inter-process communication; the local server analyzes the data transmission request information, if the data transmission request information contains a preset data acquisition identifier, the local server is configured according to the data transmission request information, and the data transmission request information is sent to the data providing end; the data providing end returns the request data corresponding to the data transmission request information to the local server end, and the local server end returns the request data to the software application end through inter-process communication. Management authority is not required to be provided for the software application end, and independent three-party application is not required to be added, so that the logic of data cross-process transmission is simplified, and the stability of the software application in data calling is improved.

Description

A cross-process data transmission method, system, device and storage medium

Technical field

The present invention relates to the field of data communication technology, and in particular to a cross-process data transmission method, system, equipment and storage medium.

Background technique

The Android operating system is mainly used in mobile devices, such as smartphones or platform computers. Android software developed based on the Android system has also been further used in various industries.

In some special usage scenarios, due to security and other considerations, the target objects that Android software needs to access are moved into an isolated namespace. Only local applications that have entered the corresponding network namespace can use the network to access the target objects. This makes it impossible for Android applications to directly use the HTTP protocol to access target objects through the external network.

In the existing technology, Android software often directly calls the core application program interface to move the Android application itself into the same namespace as the target object; or by setting up other transfer terminals other than the target object for data transfer, so as to ultimately realize Android Software access to target objects. However, directly calling the core application program interface requires granting management rights to the Android software, which poses a major security risk; and relaying through other relays will double the Ethernet data traffic, reduce data transmission performance, and cause failure at the relay end. This will directly affect the access functions of Android software and make it difficult to meet the stability requirements of software applications.

Contents of the invention

The present invention provides a cross-process data transmission method, system, equipment and storage medium. Through the local server in the system, data communication between mutually isolated software application terminals and data providing terminals is realized without providing management authority for the software application terminals. , there is no need to add independent third-party applications, avoiding security loopholes caused by direct permission elevation at the application layer, enabling cross-process data transmission without requiring more traffic, simplifying the logic of data cross-process transmission, and improving the performance of software applications. Stability when making data calls.

In the first aspect, embodiments of the present invention provide a cross-process data transmission method, which is applied in a cross-process data transmission system. The cross-process data transmission system includes a software application end, a local server end and a data provider end; wherein, the software application end Inter-process communication can be performed with the local server; methods include:

When the software application receives the data transfer instruction, it generates data transfer request information according to the data transfer instruction, and sends the data transfer request information to the local server through inter-process communication;

The local server parses the data transfer request information. If the data transfer request information contains the preset data acquisition identifier, the local server is configured according to the data transfer request information and sends the data transfer request information to the data provider;

The data provider transmits the request data corresponding to the data transmission request information back to the local server, and the local server transmits the request data back to the software application through inter-process communication.

In a second aspect, embodiments of the present invention also provide a cross-process data transmission system, including a software application end, a local server end, and a data provider end; wherein, inter-process communication is possible between the software application end and the local server end;

The software application end is used to generate data transfer request information according to the data transfer instruction when receiving the data transfer instruction, and send the data transfer request information to the local server through inter-process communication;

The local server is used to parse the data transfer request information. If the data transfer request information contains the preset data acquisition identifier, the local server is configured according to the data transfer request information and sends the data transfer request information to the data provider;

The data provider is used to transmit the request data corresponding to the data transmission request information back to the local server, and the local server transmits the request data back to the software application through inter-process communication.

In a third aspect, embodiments of the present invention also provide a cross-process data transmission device, including:

at least one processor; and

A memory communicatively connected to at least one processor; wherein,

The memory stores a computer program that can be executed by at least one processor, and the computer program is executed by at least one processor, so that at least one processor can execute the cross-process data transmission method provided by any embodiment of the present invention.

In a fourth aspect, embodiments of the present invention also provide a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform the cross-process data transmission method provided by any embodiment of the present invention.

Embodiments of the present invention provide a cross-process data transmission method, system, device and storage medium. When receiving a data transmission instruction through a software application end, the data transmission request information is generated according to the data transmission instruction, and the data transmission request information is passed through Inter-process communication is sent to the local server; the local server parses the data transfer request information. If the data transfer request information contains the preset data acquisition identifier, the local server is configured according to the data transfer request information and sends the data transfer request information. to the data provider; the data provider transmits the request data corresponding to the data transmission request information back to the local server, and the local server transmits the request data back to the software application through inter-process communication. By adopting the above technical solution, before carrying out cross-process data transmission, a cross-process data transmission system including a software application end, a local server end and a data provider end is constructed. By setting up the local server end and inter-process communication function in the system itself, it makes When the software application receives the data transfer instruction, it can parse the data transfer request information through the local server, and then send the data transfer request information to the data provider if it contains a preset data acquisition identifier, and then the data provider The provided data is transmitted back to the software application that needs the data through the local server. Without the need to add a separate third-party application, through the local server and inter-process communication technology built in the system itself, software applications that cannot interoperate are realized. The transfer of data transmission requests between the client and the data provider eliminates the need to provide management permissions to the software application, and does not require the addition of independent third-party applications. This avoids security vulnerabilities caused by direct permission elevation at the application layer and can be achieved without the need for more traffic. The cross-process transmission of data simplifies the logic of cross-process data transmission and improves the stability of software applications when making data calls.

It should be understood that what is described in this section is not intended to identify key or important features of the embodiments of the invention, nor is it intended to limit the scope of the invention. Other features of the present invention will become easily understood from the following description.

Description of the drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without exerting creative efforts.

Figure 1 is a schematic flow chart of a cross-process data transmission method provided by Embodiment 1 of the present invention;

Figure 2 is a flow chart of a cross-process data transmission method provided in Embodiment 2 of the present invention;

Figure 3 is a schematic structural diagram of a cross-process data transmission system provided in Embodiment 3 of the present invention;

Figure 4 is a schematic structural diagram of a cross-process data transmission device provided in Embodiment 4 of the present invention.

Detailed ways

In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only These are some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the scope of protection of the present invention.

It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the invention described herein are capable of being practiced in sequences other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus that encompasses a series of steps or units and need not be limited to those explicitly listed. Those steps or elements may instead include other steps or elements not expressly listed or inherent to the process, method, product or apparatus.

Embodiment 1

Figure 1 is a schematic flowchart of a cross-process data transmission method provided in Embodiment 1 of the present invention. This embodiment of the present invention can be applied to connect data between an application and a server that cannot be directly accessed through a real network address, so that the application In the case of cross-process data transmission between the server and the server, this method can be performed by a cross-process data transmission system. The cross-process data transmission system can be implemented by software and/or hardware. The cross-process data transmission system can be configured on the cross-process data transmission system. Process data transfer equipment. Optionally, the cross-process data transmission device can be a notebook, a desktop computer, a smart tablet, and other devices with data computing functions, which are not limited in this embodiment of the present invention.

In embodiments of the present invention, the cross-process data transmission method can be applied to a cross-process data transmission system, where the cross-process data transmission system includes a software application end, a local server end, and a data provider end.

Among them, inter-process communication can be carried out between the software application end and the local server end.

In this embodiment, the software application can be specifically understood as an application developed under Android or other systems and suitable for HTTP protocol access. Optionally, the software application is often a Java application or other third-party application. The local server can be specifically understood as a server written in C++ or C code in the Android system for remote calling by Java. It is a program created directly in the system that can start automatically when the system starts. The data provider can be specifically understood as an application or data storage module that provides data support for the software application. The URL where the data is stored in the data provider can be considered a real network address. For example, assuming that the cross-process data transmission method is applied to the driving recorder, the software application end can be the Android application software used for video playback in the driving recorder, and the data provider can be the electronic control in the driving recorder. The video data collected by the driving recorder can be stored in the electronic controller. If the video playback software wants to play the video collected by the driving recorder, it needs to access the photo album in the electronic controller and obtain the video data in the album. For playback, embodiments of the present invention do not impose restrictions on software applications and data providers in different scenarios. Optionally, the software application and the local server can communicate between processes through Unix Domain Socket.

As shown in Figure 1, an embodiment of the present invention provides a cross-process data transmission method, which specifically includes the following steps:

S101. When receiving the data transfer instruction, the software application generates data transfer request information according to the data transfer instruction, and sends the data transfer request information to the local server through inter-process communication.

In this embodiment, the data transmission instruction can specifically be understood as an instruction input from the outside and used to determine whether data transmission needs to be performed or to control the start and end of data transmission. The data transmission request information can be specifically understood as being generated after localization processing of the real network address, including the required real network address information and other information used to determine whether data transmission is required.

Specifically, when the software application receives the data transfer instruction, it determines the specific type of the data transfer instruction, and processes the real network address for the instruction that requires data transmission to make it suitable for inter-process communication with the local server. The processed network address and the information used to represent the need for data transmission are combined to generate data transmission request information, and then the software application sends the data transmission request information to the local server through inter-process communication. In response to the instruction that needs to stop data transmission, the software application will generate data transmission request information using the information indicating that data transmission needs to be stopped, and then the software application will send the data transmission request information to the local server through inter-process communication.

S102. The local server parses the data transmission request information. If the data transmission request information contains the preset data acquisition identifier, configures the local server according to the data transmission request information and sends the data transmission request information to the data provider.

In this embodiment, the preset data acquisition identifier can specifically be understood as preset identification information used to represent the software application end's need for the data provider end to provide data.

Specifically, after receiving the data transfer request information through inter-process communication, the local server will parse the data transfer request information. If the prefix part of the field obtained after parsing contains the preset data acquisition identifier, it can be regarded as the data transfer request information. It is the information used to request data from the data provider. At this time, the local server needs to forward the data transmission request information. Since the local server is a server that plays a forwarding role, in order to better connect with the data provider under the real network address, the local server needs to be configured according to the real network address contained in the data transmission request information, and after the configuration The local server sends the data transfer request information to the data provider.

In the embodiment of the present invention, by directly building a local server in the system that can perform local inter-process communication with the software application, it is possible to connect the software application and the data provider that cannot be directly accessed by the real network address through the local server. , there is no need to introduce an external server, which reduces data traffic consumption during data transmission and improves data transmission security and efficiency.

S103. The data provider returns the request data corresponding to the data transmission request information to the local server, and the local server returns the request data to the software application through inter-process communication.

Specifically, after receiving the data transmission request, the data provider transmits the request data corresponding to the data transmission request back to the local server, and then transmits the request data back to the local server through inter-process communication between the local server and the software application. The software application end is used to realize the transmission and call of data from the data provider end that cannot be directly accessed by the software application end.

The technical solution of this embodiment is that when the software application receives a data transfer instruction, it generates data transfer request information according to the data transfer instruction, and sends the data transfer request information to the local server through inter-process communication; the local server processes the data The transfer request information is parsed. If the data transfer request information contains the preset data acquisition identifier, the local server is configured according to the data transfer request information and the data transfer request information is sent to the data provider; the data provider will communicate with the data transfer request information. The corresponding request data is sent back to the local server, and the local server sends the request data back to the software application through inter-process communication. By adopting the above technical solution, before carrying out cross-process data transmission, a cross-process data transmission system including a software application end, a local server end and a data provider end is constructed. By setting up the local server end and inter-process communication function in the system itself, it makes When the software application receives the data transfer instruction, it can parse the data transfer request information through the local server, and then send the data transfer request information to the data provider if it contains a preset data acquisition identifier, and then the data provider The provided data is transmitted back to the software application that needs the data through the local server. Without the need to add a separate third-party application, through the local server and inter-process communication technology built in the system itself, software applications that cannot interoperate are realized. The transfer of data transmission requests between the client and the data provider eliminates the need to provide management permissions to the software application, and does not require the addition of independent third-party applications. This avoids security vulnerabilities caused by direct permission elevation at the application layer and can be achieved without the need for more traffic. The cross-process transmission of data simplifies the logic of cross-process data transmission and improves the stability of software applications when making data calls.

Embodiment 2

Figure 2 is a flow chart of a cross-process data transmission method provided in Embodiment 2 of the present invention. The technical solution of the embodiment of the present invention is further optimized based on the above optional technical solutions. By receiving the data transmission at the software application end, Before the instruction, install the inter-process communication server and inter-process communication client in the local server and software application side respectively, and build the communication connection between the inter-process communication server and the inter-process communication client to realize the software application side and local service Communication between terminals. At the same time, by creating a local proxy server in the software application, the localized configuration of inputting the real network address of the data transmission port is realized, making it suitable for transmission to the local server. Then, when the software application receives the data transmission instruction, According to the instruction type of the data transfer instruction, complete the address configuration of the data transfer port and the generation of data transfer request information for requesting data, or complete the generation of data transfer request information for stopping data transfer, so that the software application end and the local The server can perform appropriate address configuration when data transmission is required, and can complete resource release as soon as possible when data transmission is not performed. This improves the efficiency and stability of cross-process data transmission, simplifies the logic of cross-process data transmission, and improves the efficiency of cross-process data transmission. The stability of software applications when making data calls.

As shown in Figure 2, a cross-process data transmission method provided by an embodiment of the present invention specifically includes the following steps:

S201. Create an inter-process communication server in the local server according to the preset inter-process communication name.

In this embodiment, the preset inter-process communication name can specifically be understood as a name that is set in advance according to the actual situation and is used to express the personalized identity of the built inter-process communication (Unix Domain Socket, UDS). For example, assuming that the media data is acquired and played, that is, the data requirements corresponding to the software application are provided by MediaPlayer, the inter-process communication name can be set to "MediaPlayerUDS", or it can be set according to the actual situation. The corresponding inter-process communication name is preset according to the situation, and the embodiment of the present invention does not limit this.

Specifically, before the cross-process data transmission system is put into use, a local server Native Service can be launched locally in the system, and then the preset inter-process communication name is used as a parameter on the local server to create inter-process communication that natively supports UDS in Android. Server-side LocalServerSocket, and then the accept method of LocalServerSocket can be called in the child thread to block the connection with the client corresponding to the inter-process communication server.

S202. Create an inter-process communication client in the software application according to the preset inter-process communication name.

Specifically, before the cross-process data transmission system is put into use and after the inter-process communication server is established in the local server, the preset inter-process communication name can be used in the software application side based on the same preset inter-process communication name as the inter-process communication server name. Corresponds to the creation of Android's native inter-process communication client LocalSocket that supports UDS.

S203. The software application determines the socket address according to the preset inter-process communication name and the preset address creation instruction, and passes the socket address to the inter-process communication client to complete the inter-process communication client and the inter-process communication server. Communication connection.

Specifically, after the software application completes the creation of the inter-process communication client, since the inter-process communication client and the inter-process communication server have the same preset inter-process communication name, the corresponding relationship between the two can be constructed based on it, and then The software application can use the preset inter-process communication name and the preset address creation instruction preconfigured in the Android system as parameters to create a socket address under the Unix domain socket abstract namespace that supports USD, and then use the socket address The address is passed to the inter-process communication client, so that the inter-process communication client can use the socket address as a parameter to call its corresponding connet method to complete the communication connection between the inter-process communication client and the inter-process communication server. Optional, the preset address creation instruction can be

LocalSocketAdress.Namespace.ABSTRACT, the created socket address can be expressed as LocalSocketAdress.

S204. Create a local proxy server in the software application.

In this embodiment, the local proxy server can be specifically understood as a socket that is established locally and adapted to the local network address, used to monitor clients that need to request data, and can be connected to other servers.

Specifically, when the local proxy needs to perform data requests and data transmission, when the request comes from the real network address, the server socket ServerSocket under the local HTTP protocol needs to be created on the software application end, and the resulting server end will be created. The socket is identified as the local proxy server.

S205. Bind the local proxy server to the preset local domain name and the preset idle port number.

In this embodiment, the preset local domain name can be specifically understood as the domain name of the preset local network IP address. The preset idle port number can specifically be understood as a preset idle port number.

For example, assuming that the local IP address is "127.0.0.1" and the default idle port number is 9090, the built local proxy server can be bound to the local IP address and the default idle port number, and then the built-in local proxy server can be bound to the local IP address and the default idle port number. Call the accept method of ServerSocket in the child thread to block and wait for the data transmission request of MediaPlayer that provides data requirements.

S206. Generate a local network address based on the preset local domain name, the preset free port number and the preset real network address.

In this embodiment, the preset real network address can be specifically understood as a real network address that is preconfigured according to the calling requirements of the software application, and the data provider stores the real network address of the data that needs to be called.

Continuing from the above example, assume that in the usage scenario of a driving recorder, the software application is a video playback software that needs to obtain video data, and the preset real network address is the address of the photo album in the electronic controller, which can be expressed as DVR_REAL_MP4_PATH, then the Replace the domain name in the preset real network address with the preset local domain name "127.0.0.1", and replace the port number of the preset real network address with the default idle port number 9090 used by the local proxy server.

S207: Initialize the data transmission port, and have the local proxy server monitor the initialized data transmission port.

Specifically, after completing the construction of inter-process communication between the software application and the local server, and the configuration of the local proxy server, it can be considered that the software application can be used to request the data transmission port given the data transmission requirements. Receive and perform subsequent processing of data transfer requests. At this time, the data transmission port in the software application end for receiving external data transmission instructions can be initialized to complete the cross-process data transmission preparation, and then the local proxy server can monitor the initialized data transmission port, so that the local proxy service The terminal can obtain the data transmission instructions input by the data transmission port in time.

Continuing from the above example, assuming that in the usage scenario of the driving recorder, the software application end is video playback software that needs to obtain video data, then the data transmission port of the software application end can be considered to be the SDK port related to MediaPlayer. After completing the software application end After establishing the inter-process communication with the local server and configuring the local proxy server, you can set the callback monitoring of the player onPrepared by calling the setOnPreparedListener method of MediaPlayer, and then realize the input in the data transmission port through the local proxy server. Monitoring of data transfer instructions.

S208. When the software application terminal receives the data transfer instruction input from the data transfer port, if the instruction type of the data transfer instruction is the request type, execute S209; if the instruction type of the data transfer instruction is the stop type, execute S215.

Specifically, when the software application receives an input data transfer instruction through the data transmission port, it can be considered that the software application may have a need to make a data call or stop a data call. At this time, the instruction type of the data transfer instruction can be analyzed. If the instruction type is a request type, it can be considered that the software application needs to complete the cross-process data call to the data provider through the local server, and step S209 is performed at this time; if the instruction type is a stop type, it can be considered that the software application needs Stop the cross-process data call from the local server to the data provider, and execute step S215 at this time.

S209. Set a local network address for the data transmission port.

Specifically, after it is determined that the software corresponding to the data transmission port needs to call and transmit data, in order to meet the needs of local communication, the predetermined local network address is set to the data transmission port in the software application end.

Following the above example, the software application can use the generated local network address as a parameter, call the setDataSource method of the MediaPlayer corresponding to the data transmission port, and then call the prepareAsync method of the MediaPlayer to trigger the initialized MediaPlayer to issue a data transmission request, so that the The data transmission request can be monitored by the local proxy server corresponding to the local network address via the data transmission port.

S210. When the local proxy server monitors the local data transmission request, update the local data transmission request by presetting the real network domain name, the preset real port number and the preset data acquisition identifier, and determine the updated local data transmission request. Requests information for the data transfer and sends the data transfer request information to the interprocess communication client.

In this embodiment, the local data transmission request can be specifically understood as a request for data invocation issued by software with data transmission requirements through the data transmission port after completing initialization and local network address configuration.

Specifically, when the local proxy server monitors the local data transmission request, it can be considered that the service accessing the software application through the data transmission port has data transmission requirements, and because the address information contained in the local data transmission request is replaced The local network address needs to be sent to the local server to make a data request to the data provider with a real address through the local server. The information sent to the local server needs to carry the information related to the real network address. information, so at this time, the local data transmission request can be updated through the preset real network domain name and the preset real port number corresponding to the preset real network address. At the same time, the local server can make the local data transmission request clear based on the input data transmission request information. Whether you want to obtain data, you need to add a preset data acquisition identifier to the updated local data transfer request to indicate the need for data acquisition, and determine the local data transfer request that completes all the above updates and information addition as a data transfer request. The information is sent by the local proxy server to the inter-process communication client of the software application.

Following the above example, when the local proxy server ServerSocket obtains the local data transmission request passed in by MediaPlayer through the data transmission port, the local network domain name and port number in the local data transmission request are replaced with the real preset real network address. The network domain name and port number are generated to generate data transmission request information for the real network. At the same time, a preset data acquisition identifier is added to the request information, such as "real_socket_request", and the added request information is determined as a data transmission request. information, and sends the data transfer request information to the inter-process communication client LocalSocket.

S211. The inter-process communication client sends the data transmission request information to the inter-process communication server.

S212. The local server parses the data transmission request information. If the data transmission request information contains the preset data acquisition identifier, create data on the local server based on the preset real network domain name and the preset real port number in the data transmission request information. transmission end.

Specifically, when the local server receives the data transfer request information, it will parse the data transfer request information. If it is determined after the analysis that the data transfer request information contains the preset data acquisition identifier, the data transfer request information can be considered to be a desired one. To access the data provider and obtain the request information for feedback data, you can create a data transmission end in the local server to access the data provider, and use the preset real network domain name in the data transmission request information. Configure the data transmission end with the preset real port number, so that the data transmission end can directly transmit data with the data provider with a real address after configuration.

Following the above example, after the local server Native Service receives the data transfer request information through the inter-process communication server LocalServerSocket, it parses it to determine whether the data transfer request information starts with the preset data acquisition identifier. If so, it will Create a Socket in the server Native Service as the data transmission end, and then complete the connection between the data transmission end and the data provider based on the preset real network domain name and preset real port number in the data transmission request information, and then use the inter-process communication server LocalServerSocket The received data transfer request information is passed to the data provider.

S213. The data transmission terminal sends the data transmission request information to the data provider.

S214. The data provider returns the request data corresponding to the data transmission request information to the local server, and the local server returns the request data to the software application through inter-process communication.

Specifically, after receiving the data transmission request information, the data provider will provide corresponding request data according to the data transmission request information. Since the data provider establishes a connection with the data transmission end in the local server, the data can be transferred through this connection. The request data is sent back to the data transmission end, and then the data transmission end transmits the request data to the inter-process communication server, so that the inter-process communication server can receive the local server based on the communication connection with the inter-process communication client. The received request data is sent back to the inter-process communication client of the software application, and then transmitted to the data transmission port with data transmission requirements through the local proxy server in the software application to complete the transmission and call of the data.

S215. Generate data transmission request information including a preset data release identifier.

Specifically, when the software application determines that the data transmission instruction it receives is of the stop type, it can be considered that the software application needs to stop the cross-process data transmission provided to it by the local server. In order to allow the local server to determine whether to obtain data based on the data transmission request information input therein, a data transmission request information containing a preset data release flag indicating that the data acquisition needs to be stopped can be generated.

For example, the preset data release identifier may be expressed as "stop_socket_request", which is not limited in this embodiment of the present invention.

S216. The inter-process communication client sends the data transmission request information to the inter-process communication server, and releases the resources of the inter-process communication client.

Specifically, the software application sends the data transfer request information containing the preset data release identification to the local server through the inter-process communication client. At the same time, the software application has clearly needs to stop processing the data after receiving the data transfer instruction. Obtain, so the resources of the inter-process communication client can be released at this time to reduce memory consumption.

S217. The local server parses the data transmission request information. If the data transmission request information contains the preset data release identifier, the resources of the inter-process communication server are released.

Specifically, when the local server receives the data transfer request information, it will parse the data transfer request information. If it is determined after analysis that the data transfer request information contains the preset data release identification, the data transfer request information can be considered to be a desired one. Request information to stop obtaining data from the data provider and release resources in the local server. At this time, the data transmission end can stop receiving data from the data provider and release the resources of the inter-process communication server.

The technical solution of this embodiment is that before the software application receives the data transmission instruction, the inter-process communication server and the inter-process communication client are respectively installed in the local server and the software application, and the inter-process communication server and the inter-process communication client are constructed. The communication connection of the inter-process communication client realizes communication between the software application and the local server. At the same time, by creating a local proxy server in the software application, the localized configuration of inputting the real network address of the data transmission port is realized, making it suitable for transmission to the local server. Then, when the software application receives the data transmission instruction, According to the instruction type of the data transfer instruction, complete the address configuration of the data transfer port and the generation of data transfer request information for requesting data, or complete the generation of data transfer request information for stopping data transfer, so that the software application end and the local The server can perform appropriate address configuration when data transmission is required, and can complete resource release as soon as possible when data transmission is not performed. This improves the efficiency and stability of cross-process data transmission, simplifies the logic of cross-process data transmission, and improves the efficiency of cross-process data transmission. The stability of software applications when making data calls.

Embodiment 3

Figure 3 is a schematic structural diagram of a cross-process data transmission system provided in Embodiment 3 of the present invention. As shown in Figure 3, the cross-process data transmission system 1 includes: a software application end 11, a local server end 12 and a data provider end 13. Among them, the software application terminal 11 and the local server terminal 12 can perform inter-process communication.

The software application terminal 11 is configured to generate data transmission request information according to the data transmission instruction when receiving the data transmission instruction, and send the data transmission request information to the local server 12 through inter-process communication;

The local server 12 is used to parse the data transmission request information. If the data transmission request information contains the preset data acquisition identifier, configure the local server 12 according to the data transmission request information and send the data transmission request information to the data provider. 13;

The data providing end 13 is used to transmit the request data corresponding to the data transmission request information back to the local server 12, and the local server 12 transmits the request data back to the software application end 11 through inter-process communication.

The technical solution of this embodiment is to build a cross-process data transmission system including a software application end, a local server end and a data provider end before performing cross-process data transmission. Through the local server end and inter-process communication function set in the system itself, When the software application receives the data transfer instruction, it can parse the data transfer request information through the local server, and then send the data transfer request information to the data provider when it contains the preset data acquisition identifier, and then provide the data. The data provided by the client is transmitted back to the software application that needs the data through the local server. Without the need to add a separate third-party application, through the local server and inter-process communication technology built in the system itself, software that cannot interoperate is realized The transfer of data transmission requests between the application end and the data provider eliminates the need to provide management permissions to the software application end, and does not require the addition of independent third-party applications. This avoids security vulnerabilities caused by direct permission elevation at the application layer without requiring more traffic. Realizing cross-process data transmission simplifies the logic of data cross-process transmission and improves the stability of software applications when making data calls.

Optionally, the software application terminal 11 includes: a data transmission port 110, a local proxy server 111 and an inter-process communication client 112. The local server 12 includes: inter-process communication server 120.

Among them, the inter-process communication server 120 is created in the local server 12 according to the preset inter-process communication name; the inter-process communication client 112 is created in the software application 11 according to the preset inter-process communication name.

Software application end 11, specifically used for:

Determine the socket address according to the preset inter-process communication name and the preset address creation instruction, and pass the socket address to the inter-process communication client 112 to complete the communication between the inter-process communication client 112 and the inter-process communication server 120 connect;

Bind the local proxy server 111 to the preset local domain name and the preset idle port number;

Generate a local network address based on the preset local domain name, preset free port number and preset real network address;

The data transmission port 110 is initialized, and the local proxy server 111 monitors the initialized data transmission port 110 .

Optionally, when the software application end 11 receives the data transfer instruction input from the data transfer port 110, if the instruction type of the data transfer instruction is a request type, then set a local network address for the data transfer port 110;

When the local proxy server 111 monitors the local data transmission request, it updates the local data transmission request by presetting the real network domain name, the preset real port number and the preset data acquisition identifier, and determines the updated local data transmission request as Data transfer request information, and send the data transfer request information to the inter-process communication client 112;

The inter-process communication client 112 sends the data transmission request information to the inter-process communication server 120 .

Optionally, configure the local server 12 according to the data transmission request information, and send the data transmission request information to the data provider 13, including:

Create a data transmission terminal 121 on the local server 12 according to the preset real network domain name and the preset real port number in the data transmission request information;

The data transmission terminal 121 sends the data transmission request information to the data providing terminal 13 .

Optionally, when the software application end 11 receives the data transfer instruction input from the data transfer port 110, if the instruction type of the data transfer instruction is a stop type, data transfer request information containing a preset data release identifier is generated;

The inter-process communication client 112 sends the data transmission request information to the inter-process communication server 120 and releases the resources of the inter-process communication client 112.

The local server 12 parses the data transmission request information. If the data transmission request information contains a preset data release identifier, the resources of the inter-process communication server 120 are released.

The cross-process data transmission system provided by embodiments of the present invention can execute the cross-process data transmission method provided by any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

Embodiment 4

Figure 4 is a schematic structural diagram of a cross-process data transmission device provided in Embodiment 4 of the present invention. Cross-process data transfer device 40 may be an electronic device intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computer. Electronic devices may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (eg, helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are examples only and are not intended to limit the implementation of the invention described and/or claimed herein.

As shown in Figure 4, the cross-process data transmission device 40 includes at least one processor 41, and a memory communicatively connected to the at least one processor 41, such as a read-only memory (ROM) 42, a random access memory (RAM) 43, etc., where , the memory stores a computer program that can be executed by at least one processor. The processor 41 can be based on a computer program stored in a read-only memory (ROM) 42 or loaded from a storage unit 48 into a random access memory (RAM) 43. program to perform various appropriate actions and processing. In the RAM 43, various programs and data required for the operation of the cross-process data transmission device 40 may also be stored. The processor 41, ROM 42 and RAM 43 are connected to each other through a bus 44. An input/output (I/O) interface 45 is also connected to bus 44 .

Multiple components in the cross-process data transmission device 40 are connected to the I/O interface 45, including: input unit 46, such as keyboard, mouse, etc.; output unit 47, such as various types of displays, speakers, etc.; storage unit 48, such as Disk, optical disk, etc.; and communication unit 49, such as network card, modem, wireless communication transceiver, etc. The communication unit 49 allows the cross-process data transfer device 40 to exchange information/data with other devices through computer networks such as the Internet and/or various telecommunications networks.

Processor 41 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 41 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processing processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 41 performs various methods and processes described above, such as the cross-process data transmission method.

In some embodiments, the cross-process data transmission method may be implemented as a computer program, which is tangibly embodied in a computer-readable storage medium, such as storage unit 48. In some embodiments, part or all of the computer program may be loaded and/or installed onto the cross-process data transfer device 40 via the ROM 42 and/or the communication unit 49. When the computer program is loaded into RAM 43 and executed by processor 41, one or more steps of the above-described cross-process data transfer method may be performed. Alternatively, in other embodiments, the processor 41 may be configured to perform the cross-process data transfer method in any other suitable manner (eg, by means of firmware).

Various implementations of the systems and techniques described above may be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip implemented in a system (SOC), load programmable logic device (CPLD), computer hardware, firmware, software, and/or a combination thereof. These various embodiments may include implementation in one or more computer programs executable and/or interpreted on a programmable system including at least one programmable processor, the programmable processor The processor, which may be a special purpose or general purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device. An output device.

Computer programs for implementing the methods of the invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that the computer program, when executed by the processor, causes the functions/operations specified in the flowcharts and/or block diagrams to be implemented. A computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. Computer-readable storage media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, laptop disks, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having a display device (eg, a CRT (cathode ray tube) or LCD (liquid crystal display)) for displaying information to the user monitor); and a keyboard and pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and may be provided in any form, including Acoustic input, voice input or tactile input) to receive input from the user.

The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., A user's computer having a graphical user interface or web browser through which the user can interact with implementations of the systems and technologies described herein), or including such backend components, middleware components, or any combination of front-end components in a computing system. The components of the system may be interconnected by any form or medium of digital data communication (eg, a communications network). Examples of communication networks include: local area network (LAN), wide area network (WAN), blockchain network, and the Internet.

Computing systems may include clients and servers. Clients and servers are generally remote from each other and typically interact over a communications network. The relationship of client and server is created by computer programs running on corresponding computers and having a client-server relationship with each other. The server can be a cloud server, also known as cloud computing server or cloud host. It is a host product in the cloud computing service system to solve the problems of difficult management and weak business scalability in traditional physical hosts and VPS services. defect.

It should be understood that various forms of the process shown above may be used, with steps reordered, added or deleted. For example, each step described in the present invention can be executed in parallel, sequentially, or in different orders. As long as the desired results of the technical solution of the present invention can be achieved, there is no limitation here.

The above-mentioned specific embodiments do not constitute a limitation on the scope of the present invention. It will be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions are possible depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention shall be included in the protection scope of the present invention.

Claims (10)

1. A cross-process data transmission method, characterized in that it is applied in a cross-process data transmission system. The cross-process data transmission system includes a software application end, a local server end and a data provider end; wherein, the software application end Inter-process communication can be performed with the local server; the method includes: When the software application terminal receives the data transmission instruction, it generates data transmission request information according to the data transmission instruction, and sends the data transmission request information to the local server through inter-process communication; The local server parses the data transmission request information. If the data transmission request information contains a preset data acquisition identifier, configures the local server according to the data transmission request information and transmits the data The request information is sent to the data provider; The data provider transmits the request data corresponding to the data transmission request information back to the local server, and the local server transmits the request data back to the software application through inter-process communication. . 2. The method according to claim 1, characterized in that, before the software application terminal receives the data transmission instruction, it further includes: Create an inter-process communication server in the local server according to the preset inter-process communication name; Create an inter-process communication client in the software application according to the preset inter-process communication name; The software application terminal determines the socket address according to the preset inter-process communication name and the preset address creation instruction, and passes the socket address to the inter-process communication client to complete the inter-process communication. The communication connection between the client and the inter-process communication server. 3. The method according to claim 2, characterized in that, after completing the communication connection between the inter-process communication client and the inter-process communication server, further comprising: Create a local proxy server in the software application; Bind the local proxy server to a preset local domain name and a preset idle port number; Generate a local network address based on the preset local domain name, the preset idle port number and the preset real network address; The data transmission port is initialized, and the local proxy server monitors the initialized data transmission port. 4. The method according to claim 3, characterized in that when the software application terminal receives a data transfer instruction, it generates data transfer request information according to the data transfer instruction, and passes the data transfer request information through the process. Communication is sent to the local server, including: When the software application terminal receives the data transmission instruction input by the data transmission port, if the instruction type of the data transmission instruction is a request type, the local network address is set for the data transmission port; When the local proxy server monitors the local data transmission request, it updates the local data transmission request by presetting the real network domain name, the preset real port number and the preset data acquisition identifier, and updates the local data transmission request. The data transmission request is determined as data transmission request information, and the data transmission request information is sent to the inter-process communication client; The inter-process communication client sends the data transmission request information to the inter-process communication server. 5. The method according to claim 4, characterized in that configuring the local server according to the data transmission request information and sending the data transmission request information to the data provider includes: Create a data transmission terminal on the local server according to the preset real network domain name and the preset real port number in the data transmission request information; The data transmission end sends the data transmission request information to the data providing end. 6. The method according to claim 3, characterized in that when the software application terminal receives a data transfer instruction, it generates data transfer request information according to the data transfer instruction, and passes the data transfer request information through the process. Communication is sent to the local server, including: When the software application terminal receives the data transfer instruction input from the data transfer port, if the instruction type of the data transfer instruction is a stop type, generate data transfer request information including a preset data release identifier; The inter-process communication client sends the data transmission request information to the inter-process communication server, and releases the resources of the inter-process communication client. 7. The method according to claim 6, characterized in that, after the local server parses the data transmission request information, it further includes: If the data transmission request information includes the preset data release identifier, the resources of the inter-process communication server are released. 8. A cross-process data transmission system, characterized in that it includes a software application end, a local server end and a data provider end; wherein the software application end and the local server end are capable of inter-process communication; The software application end is configured to, when receiving a data transfer instruction, generate data transfer request information according to the data transfer instruction, and send the data transfer request information to the local server through inter-process communication; The local server is used to parse the data transmission request information. If the data transmission request information contains a preset data acquisition identifier, configure the local server according to the data transmission request information and transfer the data transmission request information to the local server. The data transmission request information is sent to the data provider; The data provider is configured to transmit request data corresponding to the data transmission request information to the local server, and the local server transmits the request data back to the local server through inter-process communication. Software application side. 9. A cross-process data transmission device, characterized by including: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor, so that the at least one processor can execute any one of claims 1-7. The cross-process data transfer method described above. 10. A storage medium containing computer-executable instructions, characterized in that, when executed by a computer processor, the computer-executable instructions are used to perform the cross-process data transmission method according to any one of claims 1-7 .