CN116541185A

CN116541185A - Data interaction method and device, electronic equipment and storage medium

Info

Publication number: CN116541185A
Application number: CN202310518612.9A
Authority: CN
Inventors: 李铮; 李小成
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2023-05-09
Filing date: 2023-05-09
Publication date: 2023-08-04

Abstract

The disclosure relates to a data interaction method, a data interaction device, electronic equipment and a storage medium. The method is applied to terminal equipment of an android system and comprises a routing module arranged between an application framework layer and a local service layer, and the method comprises the following steps: receiving a first message sent by a sender through a first interface layer, wherein the sender is positioned on an application framework layer or a local service layer, and the first interface layer is a Java interface layer or a Native interface layer; selecting to send a first message to a receiver through a shared memory or a Java local interface based on a first preset rule, wherein the receiver is positioned in a communication layer different from a sender in an application framework layer and a local service layer; receiving a second message sent by a receiver through a second interface layer and through a shared memory or a Java local interface, wherein the second interface layer is a Java interface layer or a Native interface layer and is different from the first interface layer; and sending the second message to the sender through the first interface layer. The present disclosure improves the efficiency and performance of communications.

Description

Data interaction method and device, electronic equipment and storage medium

Technical Field

The disclosure relates to the field of computer technology, and in particular, to a data interaction method, a data interaction device, electronic equipment and a computer readable storage medium.

Background

Android (Android) is an operating system based on free and open source codes of Linux kernels, and is mainly used for mobile devices, such as smartphones, tablet computers and the like. Development of upper-layer applications in the Android system is generally completed based on Java programs, and therefore, an upper layer completed based on Java programs is referred to as a "Java layer".

Java is platform independent and therefore some underlying tasks are not easy to implement with Java programs. For example, when tasks are related to local services, link libraries, or hardware drivers, it is often necessary to run a C/c++ program to implement it, and the C/c++ program runs on the local service (Native) layer, so the corresponding bottom layer that needs to be implemented with the C/c++ program is called the "Native layer". Since the Java layer and Native layer are developed based on different computer languages, for example, the Java layer is written in Java language or Kotlin language, and the Native layer is generally written in C language or c++, communication between the Java layer and Native layer is realized by calling each other through a Java Native interface (Java Native Interface, JNI).

In the related art, JNI enables Java programs running on Java virtual machines (Java Virtual Machine, JVM) to call or be called by programs written in C/c++ or other languages (e.g., assembly language, etc.) specific to native hardware and operating systems. However, in the manner in which the Java layer calls the Native layer, since the Java program is running on the JVM, the JNI has much lower performance when the Java layer calls a cross-language interface, such as C/c++ or other languages, than when the Java layer calls Java methods (i.e., java layer internal calls). In the way that the Native layer calls the Java layer, since obtaining the call of the fields or methods of the Java object sometimes requires a lot of work to be done in the JVM, which makes the JVM traverse the class hierarchy upwards to find them, the call between the Java layer and the Native layer needs to be repeatedly performed through the JNI multiple times, which results in inefficiency and easily causes problems such as memory leakage or program crash.

Disclosure of Invention

In view of the above, the embodiments of the present disclosure provide a data interaction method, apparatus, electronic device, and computer readable storage medium, so as to solve the problem of memory leakage or program crash caused by frequent inter-call between a Java layer and a Native layer in the related art.

In a first aspect of the embodiments of the present disclosure, a data interaction method is provided, which is applied to a terminal device of an android system, where the terminal device includes a routing module, and the routing module is disposed between a Java layer and a Native layer, and the method includes: receiving a first message sent by a sender through a first interface layer, wherein the sender is positioned on an application framework layer or a local service layer, and the first interface layer is a Java interface layer or a Native interface layer; selecting to send a first message to a receiver through a shared memory or a Java local interface based on a first preset rule, wherein the receiver is positioned in a communication layer different from a sender in an application framework layer and a local service layer; receiving a second message sent by a receiver through a second interface layer and through a shared memory or a Java local interface, wherein the second interface layer is a Java interface layer or a Native interface layer and is different from the first interface layer; and sending the second message to the sender through the first interface layer.

A second aspect of the embodiments of the present disclosure provides a data interaction device, applied to a terminal device of an android system, where the terminal device includes a routing module, and the routing module is disposed between an application framework layer and a local service layer, and the device includes: the first receiving module is configured to receive a first message sent by a sender through a first interface layer, wherein the sender is positioned on an application framework layer or a local service layer, and the first interface layer is a Java interface layer or a Native interface layer; the selection module is configured to select to send a first message to a receiver through a shared memory or a Java local interface based on a first preset rule, wherein the receiver is located in a communication layer different from a sender in an application framework layer and a local service layer; the second receiving module is configured to receive a second message sent by a receiver through a second interface layer and through a shared memory or a Java local interface, wherein the second interface layer is a Java interface layer or a Native interface layer, and the second interface layer is different from the first interface layer; and the sending module is configured to send the second message to the sender through the first interface layer.

In a third aspect of embodiments of the present disclosure, an electronic device is provided, comprising at least one processor; a memory for storing at least one processor-executable instruction; wherein the at least one processor is configured to execute instructions to implement the steps of the above-described method.

In a fourth aspect of the disclosed embodiments, a computer-readable storage medium is provided, which when executed by a processor of an electronic device, enables the electronic device to perform the steps of the above-described method.

The above-mentioned at least one technical scheme that the embodiment of the disclosure adopted can reach following beneficial effect: the routing module arranged between the application framework layer and the local service layer receives the first message sent by the sender at the application framework layer or the local service layer through the Java interface layer or the Native interface layer, selects to send the first message to the receiver at a communication layer different from the sender in the application framework layer and the local service layer through the shared memory or the Java local interface based on the first preset rule, receives the second message sent by the receiver through the Native interface or the Java interface layer and through the shared memory or the Java local interface, and sends the second message to the sender through the Java interface layer or the Native interface layer, so that the self-adaptive switching can be performed between the shared memory and the Java local interface.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings that are required for the embodiments or the description of the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings may be obtained according to these drawings without inventive effort for a person of ordinary skill in the art.

Fig. 1 is a flowchart of a data interaction method according to an exemplary embodiment of the present disclosure.

Fig. 2 is a schematic architecture diagram of a Java layer calling Native layer according to an exemplary embodiment of the present disclosure.

Fig. 3 is a schematic architecture diagram of Native layer call Java layer according to an exemplary embodiment of the present disclosure.

Fig. 4 is a schematic diagram of an architecture of Java layer and Native layer interaction provided in an exemplary embodiment of the present disclosure.

Fig. 5 is a flowchart of another data interaction method according to an exemplary embodiment of the present disclosure.

Fig. 6 is a flowchart of yet another data interaction method according to an exemplary embodiment of the present disclosure.

Fig. 7 is a schematic structural diagram of a data interaction device according to an exemplary embodiment of the present disclosure.

Fig. 8 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present disclosure.

Fig. 9 is a schematic diagram of a computer system according to an exemplary embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below. It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.

It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.

The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

A data interaction method and apparatus according to embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

Fig. 1 is a flowchart of a data interaction method according to an exemplary embodiment of the present disclosure. Fig. 2 is a schematic architecture diagram of a Java layer calling Native layer according to an exemplary embodiment of the present disclosure. Fig. 3 is a schematic architecture diagram of Native layer call Java layer according to an exemplary embodiment of the present disclosure. Fig. 4 is a schematic diagram of an architecture of Java layer and Native layer interaction provided in an exemplary embodiment of the present disclosure.

The data interaction method of fig. 1 is applied to terminal equipment of an android system, and the terminal equipment comprises a routing module, wherein the routing module is arranged between an application framework layer and a local service layer. As shown in fig. 1, the data interaction method includes:

S101, receiving a first message sent by a sender through a first interface layer, wherein the sender is positioned on an application framework layer or a local service layer, and the first interface layer is a Java interface layer or a Native interface layer;

s102, selecting to send a first message to a receiver through a shared memory or a Java local interface based on a first preset rule, wherein the receiver is positioned in a communication layer different from a sender in an application framework layer and a local service layer;

s103, receiving a second message sent by a receiver through a second interface layer and through a shared memory or a Java local interface, wherein the second interface layer is a Java interface layer or a Native interface layer, and the second interface layer is different from the first interface layer;

s104, sending a second message to the sender through the first interface layer.

Specifically, for a terminal device using the android system, a routing module may be set between an application framework layer and a local service layer of the android system; the sender sends a first message to a routing module through a first interface layer, and after the first message is received, the routing module selects to send the first message to a receiver through a shared memory or a Java local interface based on a first preset rule; further, after receiving the first message and processing the first message, the receiver sends the second message to the shared memory or the Java local interface through the second interface layer, and then sends the second message to the routing module through the shared memory or the Java local interface; after receiving the second message, the routing module sends the second message to the sender through the first interface layer.

The Android system is also called an Android operating system, has the advantages of openness, development, rich hardware usability and the like, and is widely applied to various devices. The terminal equipment of the Android system refers to electronic equipment deployed with the Android system, for example, an Android mobile phone, an Android tablet computer, an Android watch, android smart glasses and the like.

The Android System framework is an Android System architecture, adopts a layered architecture, is divided into four layers, namely an application layer (systems Apps) from high to low, an application framework layer (Java API Framework), a System runtime layer (Native) and a Linux kernel layer. The new Android system architecture is subdivided into a hardware abstraction layer (Hardware Abstraction Layer, HAL), which is an interface layer between the operating system kernel and the hardware circuit, and is aimed at abstracting the hardware.

The application framework layer is a linking layer for linking the C/C++ program library layer of the next layer with the application layer, and the application layer can call the C/C++ program library layer of the bottom layer through the application framework layer. The application Framework layer provides an application program interface (Application Program Interface, API) for the application layer, which may be referred to as Java Framework since this layer is written in Java code. In the embodiment of the present disclosure, the application framework layer is a Java layer.

The local service layer, i.e. Native layer, refers to an Android dynamic link library written in C/c++, and is mainly used for realizing some local services and storing some link libraries, typically so files. Here, the so file is a library of program functions under Linux, i.e., compiled code and data that are available for other programs. In the Android system, the Native layer communicates with the Java layer, and is used for processing more complex operations and accessing the bottom layer of the operating system, for example, system hardware.

The development language used by the bottom layer of the Android system is C/C++, and the development language used by the application layer is Java, and as the two different languages cannot be directly communicated with each other, the communication between C/C++ and Java is realized by utilizing Java local interfaces (Java Native Interface, JNI). JNI refers to an interface between the Java layer and Native layer, which is implemented by providing several application program interfaces. For example, when a Java program needs to perform a complex operation, the Java code is implemented with low efficiency, and the C/c++ code is implemented with high efficiency, so that the Native layer can complete the complex operation, and return the operation result to the Java layer through the JNI.

JNI enables Java programs running on Java virtual machines (Java Virtual Machine, JVM) to call or be called by programs written in C/c++ or other languages (e.g., assembly language, etc.) specific to Native hardware and operating systems, and thus, in the Android system, communication between Java framework layers and Native layers in the application framework layers is enabled through JNI.

The sender refers to the party that sent the message. In the embodiment of the present disclosure, the sender may be located in a Java layer or may be located in a Native layer, which is not limited by the embodiment of the present disclosure. When the sender is located in the Java layer, the sender can be a Java layer module; when the sender is located in Native layer, the sender may be a Native layer module. The receiving party refers to the party receiving the message. In the embodiment of the present disclosure, the receiver may be located in a Java layer or a Native layer, which is not limited by the embodiment of the present disclosure. When the receiver is located in the Java layer, the receiver can be a Java layer module; when the receiver is located in Native layer, the receiver may be a Native layer module.

The sender (or receiver) is located in a different communication layer from the receiver (or sender) among the Java layer and the Native layer. For example, when the sender is located in the Java layer, the receiver is located in the Native layer; when the sender is located in Native layer, the receiver is located in Java layer.

In addition, it should be further noted that the embodiments of the present disclosure do not limit the number of senders and receivers. For example, the sender may include one Java module, may include two Java modules, or may include three or more Java modules; likewise, the receiver may include one Native module, may include two Native modules, or may further include three or more Native modules.

The first interface layer may be a Java interface layer or a Native interface layer, which is not limited by the embodiments of the present disclosure. When the first interface layer is a Java interface layer, the first interface layer receives the message from the Java layer, analyzes the message, records a callback function of the message, and sends the message to the routing module; meanwhile, the first interface layer also receives the message from the routing module, encapsulates the message according to the format, and sends the message to the corresponding Java layer module in a callback mode. When the first interface layer is a Native interface layer, the data transmission direction of the first interface layer is opposite to that of the Java layer, the first interface layer receives the message from the Native layer, records a callback function of the message, and sends the message to the routing module; meanwhile, the first interface layer also receives the message from the routing module, encapsulates the message according to the format, and sends the message to the corresponding Native layer module in a callback mode.

The second interface layer may be a Java interface layer or a Native interface layer, which is not limited by the embodiments of the present disclosure. When the second interface layer is a Java interface layer, the second interface layer receives the message from the Java layer, analyzes the message, records a callback function of the message, and sends the message to the routing module; meanwhile, the second interface layer also receives the message from the routing module, encapsulates the message according to the format, and sends the message to the corresponding Java layer module in a callback mode. When the second interface layer is a Native interface layer, the second interface layer receives the message from the Native layer, records a callback function of the message and sends the message to the routing module, wherein the data transmission direction of the second interface layer is opposite to that of the Java layer; meanwhile, the second interface layer also receives the message from the routing module, encapsulates the message according to the format, and sends the message to the corresponding Native layer module in a callback mode.

The second interface layer is a different communication layer from the first interface layer. For example, when the first interface layer is a Java interface layer, the second interface layer is a Native interface layer; when the first interface layer is a Native interface layer, the second interface layer is a Java interface layer.

The messages may include, but are not limited to, control messages, data messages, and the like. For example, if the Java layer sends a message to the Native layer informing the Native layer to start network downloading, the message is a control message; if the Native layer performs a series of actions to generate a log, and sends a message to report the log to the Java layer, the message is a data message. For another example, if the Java layer or Native layer actively initiates a message to report its own status, the message is also a data message. In the embodiment of the present disclosure, the first message and the second message may be control messages or data messages, which is not limited by the embodiment of the present disclosure.

The routing module is used for routing the message received from the Java/Native interface layer to the shared memory or the JNI and sending the message received from the shared memory or the JNI to the corresponding Java/Native interface layer. The routing module may be configured with a first preset rule to determine whether to route the message to the shared memory or the JNI based on the first preset rule. The number of routing modules may be one or two, and the embodiments of the present disclosure are not limited in this regard. For example, when the Java layer invokes the Native layer, a routing module may be provided between the Java interface layer and the shared memory or JNI, as shown in FIG. 2. When the Native layer invokes the Java layer, a routing module may be disposed between the Native interface layer and the shared memory or JNI, as shown in fig. 3. When the Java layer and the Native layer call each other, two routing modules, i.e., a first routing module and a second routing module, may be disposed between the Java layer and the Native layer, where the first routing module is located between the Java interface layer and the shared memory or JNI, and the second routing module is located between the Native interface layer and the shared memory or JNI, as shown in fig. 4.

The first preset rule may include, but is not limited to, whether a message length of the message body is greater than a preset threshold, whether a processing priority of the message is high priority, and the like. For example, if the message length of the message body is greater than a preset threshold, then the message is sent and received through the shared memory; otherwise, the message is sent and received through the JNI. For another example, if the processing priority of the message is high priority, the message is transceived through the JNI; otherwise, the message is transmitted and received through the shared memory.

It should be noted that, when the routing manner based on the message length conflicts with the routing manner based on the processing priority, the routing manner may be based on the principle of message length priority or the principle of processing priority, depending on the actual configuration. For example, if the message body has a message length exceeding a threshold (i.e., using a shared memory to send and receive messages), and the message has a high processing priority (i.e., using JNI to send and receive messages), a collision may occur, and at this time, it may be determined whether to use the shared memory or the JNI to send and receive messages according to the actual situation. For another example, if the shared memory is already occupied with unconsumed messages, then the JNI is used to send and receive messages.

The shared memory is actually a section of memory opened up by the operating system in the actual physical memory. The shared memory is the most efficient communication mode among the processes, and the processes can directly read and write the memory without copying any data among the processes. There are various implementations of shared memory. Taking a mmap mode as an example, distributing a Native memory during system initialization, and performing memory mapping in a mmap calling mode to enable the Native memory to be shared by a Java layer and a Native layer routing module; further, dividing the area of the shared memory according to a specified format to divide a block of area into a plurality of small areas, wherein each small area is used for storing a message; after filling the data, each small area corresponds to the current message state, sender, receiver, data length, data, etc.

It should be noted that when a message is placed in the shared memory, the validity time for the message may be set. When a message is not consumed for a valid time (i.e., the processing time of the message exceeds the valid time), the message is set to invalid and the corresponding region is set to an idle state for depositing a new message. Here, the effective time may be any value in the range of 1 second to 10 seconds. Preferably, in the presently disclosed embodiments, the effective time is 5 seconds.

According to the technical scheme provided by the embodiment of the disclosure, the routing module arranged between the application framework layer and the local service layer receives the first message sent by the sender at the application framework layer or the local service layer through the Java interface layer or the Native interface layer, selects to send the first message to the receiver at a communication layer different from the sender in the application framework layer and the local service layer through the shared memory or the Java local interface based on the first preset rule, receives the second message sent by the receiver through the Native interface or the Java interface layer and through the shared memory or the Java local interface, and sends the second message to the sender through the Java interface layer or the Native interface layer, so that the self-adaptive switching can be performed between the shared memory and the Java local interface.

In some embodiments, the first message includes a message header and a message body, the message header carrying message length information and priority information, the method further comprising: analyzing the message header to obtain message length information and priority information, wherein the message length information is used for indicating the message length of the message body, and the priority information is used for indicating the processing priority of the first message.

In particular, the first message may include a Header (Header) and a Body (Body). The message header refers to a common header of all messages for identifying a message type, sender information, and the like. The message header may include, but is not limited to, a message identification, a message length, a message type, a message sequence number, a time stamp, and the like. Message body refers to specific message content, which is defined differently according to different message types. It should be noted that, for some messages, the message body may be empty.

In the embodiment of the disclosure, message length information and priority information may be carried in the message header. The message length information is used to indicate the message length of the message body, and the unit of the message length is a byte. The priority information is used to indicate a processing priority of the first message, which may include, but is not limited to, a high priority and a low priority.

In some embodiments, selecting to send the first message to the recipient via the shared memory or the Java local interface based on the first preset rule includes: under the condition that the message length of the message body is larger than a preset threshold value, selecting to send a first message to a receiver through a shared memory; and under the condition that the message length of the message body is smaller than or equal to a preset threshold value, selecting to send the first message to the receiver through the Java local interface.

Specifically, the routing module may parse the message header to obtain a message length of the message body, and if the message length of the message body is greater than a preset threshold, the routing module selects to send the first message to the receiver through the shared memory; if the message length of the message body is smaller than or equal to a preset threshold value, the routing module selects to send a first message to the receiver through the JNI. Here, the preset threshold may be a threshold preset by the user according to empirical data, or may be a threshold obtained by the user adjusting the set threshold according to actual needs, which is not limited in the embodiment of the present disclosure. For example, the preset threshold may be any value in the range of 50 bytes to 100 bytes. Preferably, in the presently disclosed embodiment, the preset threshold is 80 bytes.

In some embodiments, selecting to send the first message to the recipient via the shared memory or the Java local interface based on the first preset rule includes: under the condition that the processing priority of the first message is high priority, selecting to send the first message to a receiver through a Java local interface; in the case that the processing priority of the first message is low priority, the first message is selected to be sent to the receiver through the shared memory.

Specifically, the routing module may parse the message header to obtain a processing priority of the first message, and if the processing priority of the first message is a high priority, the routing module selects to send the first message to the receiver through the JNI; if the processing priority of the first message is low, the routing module selects to send the first message to the receiver through the shared memory.

According to the technical scheme provided by the embodiment of the disclosure, the first message with high priority can be preferentially processed under the condition of limited processing capacity by acquiring the processing priority of the first message, so that the response speed of the first message is improved, and the experience effect of a user is further improved.

In some embodiments, the method further comprises: and sending a message reminding notification to the receiver under the condition that the first message is sent to the receiver through the shared memory, wherein the message reminding notification is used for reminding the receiver to process the first message.

Specifically, when the shared memory is selected to send the first message to the receiver, the routing module also sends a message reminding notification to the receiver so as to remind the receiver to timely process the first message, thereby avoiding the possibility that the receiver misses important messages.

In some embodiments, the terminal device further comprises a decision module connected to the routing module and comprising an offline mode and a real-time mode, the method further comprising: in an offline mode, receiving a second preset rule sent by a decision module, wherein the second preset rule is generated by the decision module based on first parameter information, and the first parameter information comprises at least one of statistical information of all sent first messages, performance information of terminal equipment and state information of a shared memory; wherein selecting to send the first message to the receiver through the shared memory or the Java local interface based on the first preset rule includes: and selecting to send the first message to the receiver through the shared memory or the Java local interface based on a second preset rule.

Specifically, in the terminal device, a decision module may also be provided, and the decision module interacts with the routing module and is used for guiding the routing module to make a routing decision. The number of decision modules may be one or two, and the embodiments of the present disclosure are not limited thereto. For example, when the Java layer invokes the Native layer, a decision module may be disposed between the Java interface layer and the shared memory or JNI, where the decision module is connected to the routing module to implement communication between the routing module and the decision module, as shown in fig. 2. When the Native layer invokes the Java layer, a decision module may be between the Native interface layer and the shared memory or JNI, where the decision module is connected to the routing module to implement communication between the routing module and the decision module, as shown in fig. 3. When the Java layer and the Native layer are called mutually, two decision modules, namely a first decision module and a second decision module, can be arranged between the Java layer and the Native layer, wherein the first decision module is connected with the first routing module so as to realize communication between the first routing module and the first decision module; the second decision module is connected to the second routing module to enable communication between the second routing module and the second decision module, as shown in fig. 4.

It should be noted that in fig. 4, only one decision module may be provided, where the decision module is connected to the first routing module and the second routing module, so as to implement communication with the first routing module and the second routing module, respectively.

Further, the decision module may include two modes, namely, an offline mode and a real-time mode. The offline mode refers to that the decision module periodically obtains message information from the routing module and generates a second preset rule based on the first parameter information. Here, the first parameter information may include one or more of statistical information of all the first messages that have been transmitted, performance information of the terminal device, and status information of the shared memory. For example, for a certain type of message, although the processing priority of the message is low, the message length of the message body is large and the message is sent more frequently, so in order to improve the efficiency, a routing mode of a shared memory may be adopted. For another example, for some messages meeting the requirements, a routing manner of a shared memory may be adopted in principle, but since it is predicted that the system resources of the terminal device are insufficient, in order to meet the more frequent and more important messages, a routing manner of JNI may be adopted.

According to the technical scheme provided by the embodiment of the disclosure, the second preset rule is generated based on the first parameter information, so that a proper routing mode can be selected under the condition of better balancing the throughput of communication and the delay of communication, and therefore, the communication efficiency and performance are improved, and the user experience is further improved.

In some embodiments, the method further comprises: in a real-time mode, sending a first message to the decision module in real time; receiving a decision result sent by a decision module and aiming at a first message, wherein the decision result is determined based on second parameter information, and the second parameter information comprises at least one of real-time requirement information of the first message, message length information of the first message, performance information of terminal equipment and receiving and transmitting frequency information of the first message; wherein selecting to send the first message to the receiver through the shared memory or the Java local interface based on the first preset rule includes: the first message is selected to be sent to the recipient via the shared memory or the Java native interface based on the decision result.

Specifically, the real-time mode refers to that the routing module sends a message to the decision module in real time, and the decision module determines a decision result for the first message based on the second parameter information and sends the decision result to the routing module. Here, the second parameter information may include one or more of real-time requirement information of the first message, message length information of the first message, performance information of the terminal device, and transceiving frequency information of the first message.

It should be noted that, the real-time requirement of the message is in a proportional relationship with the processing priority of the message, that is, the higher the real-time requirement of the message is, the higher the processing priority of the corresponding message is. In addition, it should be noted that the real-time requirements of the processing corresponding to the messages of different types are different, each message type corresponds to a processing priority, and the processing priorities corresponding to the different message types may be the same or different.

According to the technical scheme provided by the embodiment of the disclosure, the decision result for the first message is determined based on the second parameter information, so that a proper routing mode can be selected under the condition of better balancing the throughput of communication and the delay of communication, and therefore, the communication efficiency and performance are improved, and the user experience is further improved.

Any combination of the above-mentioned optional solutions may be adopted to form an optional embodiment of the present disclosure, which is not described herein in detail. In addition, the sequence number of each step in the above embodiment does not mean the sequence of execution sequence, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the disclosure.

Fig. 5 is a flowchart of another data interaction method according to an exemplary embodiment of the present disclosure. The data interaction method of fig. 5 is applied to terminal equipment of an android system, and the terminal equipment comprises a routing module, wherein the routing module is arranged between a Java layer and a Native layer. As shown in fig. 5, the data interaction method includes:

s501, receiving a first message sent by a Java layer (or Native layer) through a Java interface layer (or Native interface layer), wherein the first message comprises a message header and a message body;

s502, analyzing a message header in the first message to obtain message length information and priority information, wherein the message length information is used for indicating the message length of a message body in the first message, and the priority information is used for indicating the processing priority of the first message;

s503, determining whether to send a first message to a Native layer (or a Java layer) through a shared memory based on a first preset rule, wherein the first preset rule comprises whether the message length of a message body is greater than a preset threshold value or whether the processing priority of the first message is high priority;

s504, if the first message is sent to the Native layer (or Java layer) through the shared memory, sending a message reminding notification to the Native layer (or Java layer), and continuing to execute S505, otherwise, executing S506;

S505, receiving a second message sent by the Native layer (or Java layer) through the Native interface layer (or Java interface layer) and through the shared memory;

s506, if the first message is selected to be sent to the Native layer (or Java layer) through the JNI, receiving a second message sent by the Native layer (or Java layer) through the Native interface layer (or Java interface layer) and through the JNI;

s507, sending the second message to the Java layer (or Native layer) through the Java interface layer (or Native interface layer).

According to the technical scheme provided by the embodiment of the disclosure, the routing module is additionally arranged in the terminal equipment of the android system, and the first message is selected to be sent through the shared memory or the JNI based on the first preset rule of the routing module, so that the self-adaptive switching can be performed between the shared memory and the JNI, and the efficiency and performance of Java layer and Native layer communication are improved.

Fig. 6 is a flowchart of yet another data interaction method according to an exemplary embodiment of the present disclosure. The data interaction method of fig. 6 is applied to terminal equipment of an android system, the terminal equipment comprises a routing module and a decision module, the routing module is arranged between a Java layer and a Native layer, and the decision module is connected with the routing module. As shown in fig. 6, the data interaction method includes:

S601, a routing module receives a first message sent by a Java layer (or Native layer) through a Java interface layer (or Native interface layer), wherein the first message comprises a message header and a message body;

s602, the routing module analyzes a message header in the first message to obtain message length information and priority information, wherein the message length information is used for indicating the message length of a message body in the first message, and the priority information is used for indicating the processing priority of the first message;

s603, in an offline mode of the decision module, the routing module receives a second preset rule sent by the decision module, wherein the second preset rule is generated by the decision module based on the first parameter information;

s604, the routing module selects to send a first message to the Native layer (or Java layer) through the shared memory or the JNI based on a second preset rule;

s605, in a real-time mode of the decision module, the routing module sends a first message to the decision module in real time;

s606, the routing module receives a decision result for the first message sent by the decision module, wherein the decision result is determined based on the second parameter information;

s607, the routing module selects to send the first message to the Native layer (or Java layer) through the shared memory or JNI based on the decision result.

According to the technical scheme provided by the embodiment of the disclosure, the routing module and the decision module are additionally arranged in the terminal equipment of the android system, so that the routing decision can be known to be performed by the routing module based on the second preset rule or the determined decision result generated by the decision module, and therefore, the self-adaptive switching between the shared memory and the JNI is realized, and the communication efficiency and performance of the Java layer and the Native layer are improved.

In the case of dividing each functional module by adopting corresponding each function, the embodiment of the disclosure provides a data interaction device, which may be a server or a chip applied to the server. Fig. 7 is a schematic structural diagram of a data interaction device according to an exemplary embodiment of the present disclosure. The data interaction device of fig. 7 is applied to a terminal device of an android system, and the terminal device comprises a routing module, wherein the routing module is arranged between an application framework layer and a local service layer. As shown in fig. 7, the data interaction device 700 includes:

a first receiving module 701, configured to receive a first message sent by a sender through a first interface layer, where the sender is located in an application framework layer or a local service layer, and the first interface layer is a Java interface layer or a Native interface layer;

A selection module 702 configured to select, based on a first preset rule, to send a first message to a receiver through a shared memory or a Java local interface, where the receiver is located at a communication layer different from the sender among an application framework layer and a local service layer;

a second receiving module 703 configured to receive a second message sent by the receiver through a second interface layer and through a shared memory or a Java local interface, where the second interface layer is a Java interface layer or a Native interface layer, and the second interface layer is different from the first interface layer;

a sending module 704 configured to send the second message to the sender through the first interface layer.

In some embodiments, the first message includes a message header and a message body, where the message header carries message length information and priority information, and the data interaction device of fig. 7 further includes a parsing module 705 configured to parse the message header to obtain message length information and priority information, where the message length information is used to indicate a message length of the message body, and the priority information is used to indicate a processing priority of the first message.

In some embodiments, the selection module 702 of fig. 7 selects to send the first message to the recipient via the shared memory if the message length of the message body is greater than a preset threshold; in the case where the message length of the message body is less than or equal to the preset threshold, the selection module 702 of fig. 7 selects to send the first message to the recipient through the Java native interface.

In some embodiments, where the processing priority of the first message is high priority, the selection module 702 of fig. 7 selects to send the first message to the recipient over the Java native interface; in the case where the processing priority of the first message is low, the selection module 702 of fig. 7 selects to send the first message to the recipient through the shared memory.

In some embodiments, the sending module 704 of fig. 7 sends a message alert notification to the recipient in the event that the first message is selected to be sent to the recipient via the shared memory, wherein the message alert notification is used to alert the recipient to process the first message.

In some embodiments, the terminal device further includes a decision module, which is connected to the routing module and includes an offline mode and a real-time mode, in which the first receiving module 701 of fig. 7 receives a second preset rule sent by the decision module, where the second preset rule is generated by the decision module based on first parameter information, and the first parameter information includes at least one of statistics information of all sent first messages, performance information of the terminal device, and status information of the shared memory; the selection module 702 of fig. 7 selects to send the first message to the recipient via the shared memory or Java native interface based on a second preset rule.

In some embodiments, in real-time mode, the sending module 704 of fig. 7 sends the first message to the decision module in real-time; the first receiving module 701 of fig. 7 receives a decision result for the first message sent by the decision module, where the decision result is determined based on second parameter information, and the second parameter information includes at least one of real-time requirement information of the first message, message length information of the first message, performance information of the terminal device, and transceiving frequency information of the first message; the selection module 702 of fig. 7 selects to send the first message to the recipient via the shared memory or Java native interface based on the decision result.

The implementation process of the functions and roles of each module in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.

The embodiment of the disclosure also provides an electronic device, including: at least one processor; a memory for storing at least one processor-executable instruction; the at least one processor is configured to execute instructions to implement the steps of the data interaction method disclosed in the embodiments of the present disclosure.

Fig. 8 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present disclosure. As shown in fig. 8, the electronic device 800 includes at least one processor 801 and a memory 802 coupled to the processor 801, the processor 801 may perform corresponding steps in the above-described methods disclosed in the embodiments of the present disclosure.

The processor 801 may also be referred to as a central processing unit (Central Processing Unit, CPU), which may be an integrated circuit chip with signal processing capabilities. The steps of the above-described methods disclosed in the embodiments of the present disclosure may be accomplished by instructions in the form of integrated logic circuits or software in hardware in the processor 801. The processor 801 described above may be a general purpose processor, digital signal processor (Digital Signal Processing, DSP), ASIC, off-the-shelf programmable gate array (Field-programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present disclosure may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in memory 802 such as random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, and the like, as well known in the art. The processor 801 reads the information in the memory 802 and, in combination with its hardware, performs the steps of the method described above.

In addition, various operations/processes according to the present disclosure, in the case of being implemented by software and/or firmware, may be installed from a storage medium or network to a computer system having a dedicated hardware structure, for example, the computer system 900 shown in fig. 9, which is capable of performing various functions including functions such as those described above, and the like, when various programs are installed. Fig. 9 is a schematic diagram of a computer system according to an exemplary embodiment of the present disclosure.

Computer system 900 is intended to represent various forms of digital electronic computing devices, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 9, the computer system 900 includes a computing unit 901, and the computing unit 901 can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 902 or a computer program loaded from a storage unit 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the computer system 900 can also be stored. The computing unit 901, the ROM 902, and the RAM 903 are connected to each other by a bus 904. An input/output (I/O) interface 905 is also connected to the bus 904.

Various components in computer system 900 are connected to I/O interface 905, including: an input unit 906, an output unit 907, a storage unit 908, and a communication unit 909. The input unit 906 may be any type of device capable of inputting information to the computer system 900, and the input unit 906 may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the electronic device. The output unit 907 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, video/audio output terminals, vibrators, and/or printers. Storage unit 908 may include, but is not limited to, magnetic disks, optical disks. Communication unit 909 allows computer system 900 to exchange information/data with other devices over a network such as the internet and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers and/or chipsets, e.g., bluetooth (TM) devices, wiFi devices, wiMax devices, cellular communication devices, and/or the like.

The computing unit 901 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 901 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 901 performs the respective methods and processes described above. For example, in some embodiments, the above-described methods disclosed by embodiments of the present disclosure may be implemented as a computer software program tangibly embodied on a machine-readable medium, e.g., the storage unit 908. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 900 via the ROM 902 and/or the communication unit 909. In some embodiments, the computing unit 901 may be configured to perform the above-described methods disclosed by embodiments of the present disclosure by any other suitable means (e.g., by means of firmware).

The disclosed embodiments also provide a computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the above-described method disclosed by the disclosed embodiments.

A computer readable storage medium in embodiments of the present disclosure may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium described above can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specifically, the computer-readable storage medium described above may include one or more wire-based electrical connections, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

The disclosed embodiments also provide a computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements the above-described methods of the disclosed embodiments.

In an embodiment of the present disclosure, computer program code for performing the operations of the present disclosure may be written in one or more programming languages, including but not limited to an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of remote computers, the remote computers may be connected to the user computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to external computers.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules, components or units referred to in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a module, component or unit does not in some cases constitute a limitation of the module, component or unit itself.

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

The above description is merely illustrative of some embodiments of the present disclosure and of the principles of the technology applied. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).

Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It will be appreciated by those skilled in the art that modifications may be made to the above embodiments without departing from the scope and spirit of the disclosure. The scope of the present disclosure is defined by the appended claims.

Claims

1. The data interaction method is characterized by being applied to terminal equipment of an android system, wherein the terminal equipment comprises a routing module, and the routing module is arranged between an application framework layer and a local service layer, and the method comprises the following steps:

receiving a first message sent by a sender through a first interface layer, wherein the sender is positioned on the application framework layer or the local service layer, and the first interface layer is a Java interface layer or a Native interface layer;

selecting to send the first message to a receiver through a shared memory or a Java local interface based on a first preset rule, wherein the receiver is positioned at a communication layer different from the sender in the application framework layer and the local service layer;

receiving a second message sent by the receiver through a second interface layer and through the shared memory or the Java local interface, wherein the second interface layer is the Java interface layer or the Native interface layer and is different from the first interface layer;

and sending the second message to the sender through the first interface layer.

2. The method of claim 1, wherein the first message comprises a message header and a message body, the message header carrying message length information and priority information, the method further comprising:

Analyzing the message header to obtain the message length information and the priority information, wherein the message length information is used for indicating the message length of the message body, and the priority information is used for indicating the processing priority of the first message.

3. The method of claim 2, wherein the selecting to send the first message to the recipient via the shared memory or Java local interface based on the first preset rule comprises:

under the condition that the message length of the message body is larger than a preset threshold value, selecting to send the first message to the receiver through the shared memory;

and under the condition that the message length of the message body is smaller than or equal to the preset threshold value, selecting to send the first message to the receiver through the Java local interface.

4. The method of claim 2, wherein the selecting to send the first message to the recipient via the shared memory or Java local interface based on the first preset rule comprises:

selecting to send the first message to the receiver through the Java local interface in the case that the processing priority of the first message is high priority;

And under the condition that the processing priority of the first message is low, selecting to send the first message to the receiver through the shared memory.

5. The method according to claim 3 or 4, characterized in that the method further comprises:

and sending a message reminding notification to the receiver under the condition that the first message is sent to the receiver through the shared memory, wherein the message reminding notification is used for reminding the receiver to process the first message.

6. The method of claim 2, wherein the terminal device further comprises a decision module, the decision module being coupled to the routing module and comprising an offline mode and a real-time mode, the method further comprising:

in the offline mode, receiving a second preset rule sent by the decision module, wherein the second preset rule is generated by the decision module based on first parameter information, and the first parameter information comprises at least one of statistical information of all sent first messages, performance information of the terminal equipment and state information of the shared memory;

the selecting, based on a first preset rule, to send the first message to the receiver through a shared memory or a Java local interface, including:

And selecting to send the first message to the receiver through the shared memory or the Java local interface based on the second preset rule.

7. The method of claim 6, wherein the method further comprises:

in the real-time mode, sending the first message to the decision module in real time;

receiving a decision result sent by the decision module and aiming at the first message, wherein the decision result is determined based on second parameter information, and the second parameter information comprises at least one of real-time requirement information of the first message, message length information of the first message, performance information of the terminal equipment and receiving and transmitting frequency information of the first message;

and selecting to send the first message to the receiver through the shared memory or the Java local interface based on the decision result.

8. The utility model provides a data interaction device which characterized in that is applied to the terminal equipment of android system, terminal equipment includes route module, route module sets up between application frame layer and local service layer, the device includes:

The first receiving module is configured to receive a first message sent by a sender through a first interface layer, wherein the sender is located in the application framework layer or the local service layer, and the first interface layer is a Java interface layer or a Native interface layer;

the selection module is configured to select to send the first message to a receiver through a shared memory or a Java local interface based on a first preset rule, wherein the receiver is located in a communication layer different from the sender in the application framework layer and the local service layer;

the second receiving module is configured to receive a second message sent by the receiver through a second interface layer and through the shared memory or the Java local interface, wherein the second interface layer is the Java interface layer or the Native interface layer and is different from the first interface layer;

and a sending module configured to send the second message to the sender through the first interface layer.

9. An electronic device, comprising:

at least one processor;

a memory for storing the at least one processor-executable instruction;

wherein the at least one processor is configured to execute the instructions to implement the method of any one of claims 1 to 7.

10. A computer readable storage medium, characterized in that instructions in the computer readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method of any one of claims 1 to 7.