WO2023134411A1

WO2023134411A1 - Information transmission method, terminal apparatus, and storage medium

Info

Publication number: WO2023134411A1
Application number: PCT/CN2022/140518
Authority: WO
Inventors: 侯志鹏
Original assignee: 闻泰通讯股份有限公司
Priority date: 2022-01-17
Filing date: 2022-12-21
Publication date: 2023-07-20
Also published as: CN114416402A

Abstract

Disclosed in embodiments of the present disclosure are an information transmission method, a terminal apparatus, and a storage medium, applied to the technical field of data storage, and capable of solving the problem that the standard normalization degree of storage of hardware module information by each application is low. The memory space of the terminal apparatus comprises: user space and kernel space. The method comprises: in user space, obtaining application information corresponding to a first application, the application information comprising: device information and a device operation state; and transmitting the application information from the user space to kernel space by means of a preset data write interface between the user space and the kernel space, and storing the application information in the kernel space.

Description

Information transmission method, terminal device and storage medium

related cross reference

This disclosure claims the priority of the Chinese patent application with the application number 202210051915.X and the title of the invention "information transmission method, terminal equipment and storage medium" submitted to the China Patent Office on January 17, 2022, the entire contents of which are incorporated by reference in this disclosure.

technical field

The embodiments of the present disclosure relate to the technical field of data storage, and in particular, to an information transmission method, a terminal device, and a storage medium.

Background technique

In the development and application process of terminal equipment and systems, each application program will obtain multiple pieces of information corresponding to multiple hardware modules when it is running. The storage method is not uniform, so each application program stores hardware module information in a different way, which will lead to a low degree of standardization for each application program to store hardware module information.

Contents of the invention

(1) Technical problems to be solved

In the prior art, since each application program stores hardware module information in a different way, this will lead to a problem of low standardization of each application program for storing hardware module information.

(2) Technical solution

According to various embodiments of the present disclosure, an information transmission method, a terminal device, and a storage medium are provided.

An information transmission method, applied to a terminal device, the memory space of the terminal device includes: a user space and a kernel space, the method includes: in the user space, obtaining application information corresponding to a first application program, the Application information includes: device information and device operating status;

Transmitting the application information from the user space to the kernel space through a preset data writing interface between the user space and the kernel space, and saving the application information in the kernel space middle.

As an optional implementation manner, in the user space, before obtaining the application information through the first application program, the method further includes:

In the memory space, register a device node corresponding to the terminal device, the device node is located between the user space and the kernel space;

On the device node, a data writing interface between the user space and the kernel space is set.

As an optional implementation manner, the kernel space includes: a first memory area and a second memory area, and storing the application information in the kernel space includes:

storing the device information in the first memory area, and storing the device operating state in the second memory area;

Wherein, the first memory area and the second memory area are different memory areas in the kernel space.

As an optional implementation manner, the storing the device information in the first memory area, and storing the device operating state in the second memory area includes:

Setting a plurality of enumeration variables in the kernel space, each enumeration variable corresponding to a hardware module;

defining a first position index and a second position index in the kernel space of the hardware module corresponding to each enumerated variable;

storing the device information of each hardware module in the first memory area according to the corresponding first location index, and saving the device running state of each hardware module in the second memory area according to the corresponding second location index middle;

Wherein, the first location index is used to define the storage location of the device information of each hardware module in the first memory area, and the second location index is used to define the device operation status of each hardware module in the The storage location in the second memory area.

As an optional implementation, the method also includes:

When the second application program needs to call the application information, the application information is transmitted from the kernel space to the user through the preset data readout interface between the user space and the kernel space. space;

transmitting the application information to the second application via the user space;

Wherein, the first application program and the second application program are different application programs, and the data read interface and the data write interface are different data interfaces provided in the device node.

As an optional implementation manner, when the second application program needs to call the application information, through the preset data read interface between the user space and the kernel space, from the kernel space Transmitting the application information to the user space, including:

When the second application program needs to call the application information, obtain the permission list of the device node;

If it is detected that the permission list includes the second application program, the application program is read from the kernel space through the preset data read interface between the user space and the kernel space. Information is transferred to the user space.

As an optional implementation manner, the data readout interface includes: a first data readout interface and a second data readout interface, and when the second application program needs to call the application information, the pre-set The data readout interface between the user space and the kernel space, which transmits the application information from the kernel space to the user space, includes:

When the second application program needs to call the application information, the device information is read from the first memory area of the kernel space through the first data readout interface and transmitted to the user space, And through the second data readout interface, read the operating state of the device from the second memory area of the kernel space and transmit it to the user space;

Wherein, the first data readout interface and the second data readout interface are different data readout interfaces provided in the device node.

In another aspect, an embodiment of the present disclosure provides a terminal device, the memory space of the terminal device includes: user space and kernel space, and the terminal device includes:

An acquisition module configured to acquire application information corresponding to the first application program in the user space, where the application information includes: device information and device operating status;

A processing module configured to transmit the application information from the user space to the kernel space through a preset data writing interface between the user space and the kernel space, and save the application information in the kernel space.

As an optional implementation manner, the processing module is further configured to register a device node corresponding to the terminal device in the memory space, and the device node is located between the user space and the kernel space between;

The processing module is further configured to set a data writing interface between the user space and the kernel space on the device node.

As an optional implementation manner, the kernel space includes: a first memory area and a second memory area;

The processing module is further configured to save the device information in the first memory area, and save the device operating state in the second memory area;

As an optional implementation manner, the processing module is further configured to set a plurality of enumeration variables in the kernel space, and each enumeration variable corresponds to a hardware module;

The processing module is further configured to define a first location index and a second location index of the hardware module corresponding to each enumerated variable in the kernel space;

The processing module is further configured to save the device information of each hardware module in the first memory area according to the corresponding first location index, and store the device operating state of each hardware module according to the corresponding second location index stored in the second memory area;

As an optional implementation manner, the processing module is further configured to, when the second application program needs to call the application information, through the preset data readout interface between the user space and the kernel space , transmitting the application information from the kernel space to the user space;

The processing module is further configured to transmit the application information to the second application program through the user space;

As an optional implementation manner, the obtaining module is further configured to obtain the permission list of the device node when the second application program needs to call the application information;

The processing module is further configured to, if it is detected that the permission list includes the second application program, through the preset data read-out interface between the user space and the kernel space, read from the The application information is transmitted from the kernel space to the user space.

As an optional implementation manner, the data readout interface includes: a first data readout interface and a second data readout interface;

The processing module is further configured to read the device information from the first memory area of the kernel space through the first data readout interface when the second application program needs to call the application information And transmit to the user space, and read the operating state of the device from the second memory area of the kernel space through the second data readout interface and transmit to the user space;

A terminal device, the memory space of the terminal device includes: user space and kernel space, the terminal device includes:

a memory storing executable program code;

a processor coupled to the memory;

The processor invokes the executable program code stored in the memory to execute the above information transmission method.

A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned information transmission method is realized.

A computer program product, when the computer program product is run on a computer, it can realize some or all steps of any one of the above-mentioned methods.

An application distribution platform, which is used to distribute computer program products, wherein, when the computer program products run on a computer, part or all of the steps of any one of the above-mentioned methods are realized.

Additional features and advantages of the disclosure will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the disclosure. The objectives and other advantages of the disclosure will be realized and attained by the structure particularly pointed out in the written description, claims hereof as well as the accompanying drawings, the details of one or more embodiments of the disclosure being set forth in the accompanying drawings and the description below.

In order to make the above objects, features and advantages of the present disclosure more comprehensible, optional embodiments are given below and described in detail in conjunction with the accompanying drawings.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description serve to explain the principles of the disclosure.

In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, In other words, other drawings can also be obtained from these drawings without paying creative labor.

FIG. 1 is a first schematic flowchart of an information transmission method provided by one or more embodiments of the present disclosure;

FIG. 2 is a second schematic flowchart of an information transmission method provided by one or more embodiments of the present disclosure;

Fig. 3 is a schematic structural diagram of a memory space of a terminal device provided by one or more embodiments of the present disclosure;

FIG. 4 is a first structural schematic diagram of a terminal device provided by one or more embodiments of the present disclosure;

Fig. 5 is a second schematic structural diagram of a terminal device provided by one or more embodiments of the present disclosure.

Detailed ways

In order to more clearly understand the above objects, features and advantages of the present disclosure, the solutions of the present disclosure will be further described below. It should be noted that, in the case of no conflict, the embodiments of the present disclosure and the features in the embodiments can be combined with each other.

The following will clearly and completely describe the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are part of the embodiments of the present disclosure, not all of them. Based on the embodiments in the present disclosure, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present disclosure.

The terms "first" and "second" and the like in the specification and claims of the present disclosure are used to distinguish different objects, not to describe a specific order of objects. For example, the first application program and the second application program are used to distinguish different application programs, rather than to describe a specific order of the application programs.

The terms "comprising" and "having" and any variations thereof in the embodiments of the present disclosure are intended to cover a non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to expressly instead of those steps or elements listed, may include other steps or elements not explicitly listed or inherent to the process, method, product or apparatus.

It should be noted that, in the embodiments of the present disclosure, words such as "exemplary" or "for example" are used as examples, illustrations or illustrations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present disclosure shall not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete manner.

The solution provided by the present disclosure can be used in the scenario of synchronizing data from different data sources in daily life. For ease of understanding, some terms and application scenarios involved in the embodiments of the present application are briefly introduced below.

Kernel: It belongs to the kernel of the operating system and provides the most basic functions of the operating system. Manage system processes, memory, device drivers, etc.

Proc: It is a directory of a file system in the Linux system, which can provide corresponding information through various file nodes.

ioctl: In the Linux system code, the user space controls the kernel space of the device node, and realizes functions such as parameter setting and data transmission.

misc_register: A function to register devices in the Linux system kernel, so that the system generates corresponding device nodes.

With the development of science and technology, a variety of terminal devices appear in people's daily life, and various applications are installed in the terminal devices. Different applications can provide various functions. Terminal devices start these applications This makes it easier for users to use the provided functions.

Optionally, the terminal device involved in this embodiment of the present disclosure may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle-mounted terminal device, a wearable device, an Ultra-Mobile Personal Computer (Ultra-Mobile Personal Computer, UMPC), a netbook, or a personal Digital Assistant (Personal Digital Assistant, PDA) and other electronic devices. Wherein, the wearable device may be a smart watch, a smart bracelet, a watch phone, a smart anklet, a smart earring, a smart necklace, a smart earphone, etc., which are not limited in this embodiment of the present disclosure. Optionally, the operating system of the terminal device can be an Android system, an iOS system, a Linux system, etc.,

Wherein, different operating systems can be used for the development of the terminal equipment. For example, the application program can be compiled based on different operating systems, run on the corresponding operating systems, and provide the basic functions that it can provide. In addition to completing the functional operation of the system itself, the operating system of the terminal device can also monitor relevant information in the operating system, such as processes, memory usage, driver information of the terminal device, operating system operation or abnormal records, etc. These information are provided by the operating system and managed by the operating system, and can be used in the process of system application and development. Basically, it is also some routine information. For example, in the development and application process of terminal equipment and systems, data synchronization between different databases is a common application.

For different applications, they are usually applied in different application scenarios. For example, for some terminal manufacturers’ self-made tools during the development process, they will be used in application scenarios such as engineering mode, device debugging, and detection. In addition to the above operations For the basic information that the system can obtain, the operating system also needs to obtain specific content (determined by the design of the terminal manufacturer), and pass these basic information and specific content to the manufacturer's own application program. Usually, when an application program obtains specific content, it is often obtained based on a module created by the manufacturer itself, that is, through the interaction between this module and the operating system, the content of the above-mentioned features that need to be obtained is obtained.

For example, if you want to obtain platform-related information in an application project developed by a manufacturer, you can first use some methods provided by the operating system platform: read node information in the proc directory; call system-specific attributes; view system logs, etc. wait. Then transmit the read information through some interfaces or file systems provided by the operating system, and on this basis, developers add the information they need to obtain. Among them, in the process of obtaining customized information through the developer's customized module, the corresponding character string is generally generated in the driver application program according to the detection of the corresponding device or event, and saved to the developer's customized module for maintenance. Finally, the module will also provide a function interface to pass the information in this memory to the application program.

For the above solution, the interface and file system provided by the current operating system platform cannot meet the customization information of all application program manufacturers. Application program manufacturers need to customize their own modules and function interfaces, and the terminal device driver-related information that needs to be customized is not very good. When customizing, application vendors usually only care about the information they need to obtain, and do not pay much attention to the reuse of this information (such as allowing other applications or function calls) and compatibility. For example, for application scenarios in For the device information obtained in engineering mode, the device information may need to be obtained in another detection application scenario, but there is no unified interface between the manufacturers of the two application programs, and the device information needs to be obtained again for the detection application scenario.

Moreover, in the above-mentioned application program, it is not clear whether the interface for transmitting information corresponding to the customized module is done in the user space or the kernel space. For example, some information that needs to be obtained is more convenient to obtain from the kernel, and some information that needs to be obtained is more suitable to be obtained from user space, so different companies and projects may have different methods, and the kernel driver and user space are not suitable. The interaction method is not conducive to standardization and normalization. For example, in the platform software, the device will be detected in the kernel driver first, and after the detection is successful, the specific model and manufacturer of the device used can be corresponding to the information. So for most devices, if you want to obtain customized information, you can customize the interface in the kernel driver. Some devices have a special software process (such as a camera), because this part of the device driver already has a complete process, and the detection result is returned to the user space and a corresponding string has been generated. At this time, it is relatively easy to obtain customized information in the user space. convenient. If the interface is made in the kernel driver, it will cause a lot of repetitive work of judging and generating strings (because several cameras are used in the project, and each camera may have two or three suppliers), and the code quality is not high.

Therefore, for the modules customized by each manufacturer in the above scheme, because the storage methods for hardware module information formulated by different developers or application developers are not uniform, there is no standard, resulting in the standard for each application to store hardware module information The degree of unification is low, most of the achieved results are poor in compatibility, and the code structure is chaotic.

The execution subject of the information transmission method provided by the embodiments of the present disclosure may be the above-mentioned terminal device, or may be a functional module and/or a functional entity in the terminal device capable of implementing the information transmission method, which may be specifically determined according to actual usage requirements, The embodiments of the present disclosure are not limited. The following uses a terminal device as an example to illustrate the information transmission method provided by the embodiments of the present disclosure.

In order to solve the problems existing in the above technologies, please refer to FIG. 1 , which is a first schematic flowchart of an information transmission method provided by one or more embodiments of the present disclosure. As shown in Figure 1, the information transmission method may include the following steps:

101. In a user space, obtain application information corresponding to a first application program.

In this embodiment of the present disclosure, the terminal device may obtain application information corresponding to the first application program when running the first application program.

It should be noted that since the application programs are stored in the user space in a file format, the application information corresponding to the first application program acquired by the terminal device is stored in the user space.

Among them, the application information includes: device information and device operating status; the device can include various hardware modules in the terminal device, such as: display screen, camera, gyroscope, acceleration sensor, etc.; when each application is running, it may Call the function of a device in the terminal device, correspondingly, the terminal device can also obtain the device information and device running status corresponding to the device. Optionally, the device information may include information such as the device number, model, and manufacturer of the hardware module. The running state of the device is the state of the hardware module during operation, such as: working state, pause state, etc. If a fault occurs , then the device operating status may include: fault type, fault cause, etc.

Optionally, the memory space of the terminal device includes: user space and kernel space, wherein the user space is the memory area where the user process is located, and the kernel space is the memory area occupied by the operating system. All data of user processes and operating system processes are kept in the memory space.

Before the terminal device is started, the memory space is a piece of original physical memory. After the system of the terminal device is started, the physical memory is divided. Of course, this division is the logical division of the operating system. There is no well-divided address and space range on the physical memory stick, and the division results of different versions of the operating system are different.

Then the basis for the division is that the data of different objects are stored in different places, that is, the data of the operating system is generally stored in the kernel space, and the data of the user process is generally stored in the user space. If the data of the operating system and the user If the data of the process is stored together, it will affect the operation of the system; if the data of the system and the data of the user are stored separately, the data of the system and the data of the user can not interfere with each other, ensuring the stability of the operating system . And if the user data is separated from the system data, access to the two parts of the data can also be controlled to ensure that the user program cannot casually access the data of the operating system, thereby preventing the user program from misoperation or maliciously destroying the system.

102. Transmit application information from the user space to the kernel space through a preset data writing interface between the user space and the kernel space.

In the embodiment of the present disclosure, the terminal device can transmit the application information from the user space to the kernel space through the data writing interface. The data writing interface is an interface set in advance, and the data writing interface is located between the user space and the kernel space. During the period, the data writing interface is an interface for transferring information in the user space to the kernel space.

103. Save the application information in the kernel space.

In the embodiment of the present disclosure, after the terminal device transmits the application information from the user space to the kernel space, the application information can be stored in the kernel space.

Optionally, after the terminal device transfers the application information from the user space to the kernel space, it can delete the application information in the user space, that is, the application information is only stored in the kernel space; the terminal device can also not delete the application information in the user space , that is, application information is stored in both the kernel space and the user space.

To sum up, in the embodiment of the present disclosure, the memory space of the terminal device includes: user space and kernel space, and the terminal device can obtain application information corresponding to the first application program in the user space, and the application information includes: device information and Device running state; then the terminal device can transfer application information from user space to kernel space through the pre-set data writing interface between user space and kernel space, and save the application information in kernel space. Through this solution, the terminal device can pre-set the data writing interface in the user space and the kernel space, so that the terminal device can write the application information obtained in the user space through the data writing interface, transmit and store it in the kernel space , so as to ensure that all application information is saved in the kernel space, so that no matter what application information the terminal device obtains in the user space, it can be stored in the kernel space through the data writing interface, and there will be no part of the information stored in the user space. Partial information is stored in the kernel space, which effectively improves the degree of standardization of terminal equipment storage hardware module information.

Please refer to FIG. 2, which is a schematic flow diagram II of an information transmission method provided by one or more embodiments of the present disclosure. As shown in FIG. 2, the information transmission method may include the following steps:

201. In the memory space, register a device node corresponding to the terminal device.

In the embodiment of the present disclosure, the terminal device may first register the device node of the terminal device in the memory space.

It should be noted that devices under the Linux operating system are generally divided into three categories: character devices, block devices, and network devices. The corresponding device drivers are also divided into three categories: character device drivers, block device drivers, and network device drivers. Common character devices include mouse, keyboard, serial port, console, etc. Common block devices include various hard disks, flash disks, random access memory (RAM) disks, and the like.

The device node is created in the /dev directory, which is the hub connecting the kernel space and the user space. It can be used to indicate that the terminal device is connected to a certain ID of a certain interface. The device node can be equivalent to the index node of the hard disk (inode), which records the location and information of the hardware device.

In the Linux operating system, all devices are stored in the /dev directory in the form of files, and are accessed through files. The device node is an abstract description of the device in the Linux operating system. A device node is a file, that is, a A device node is just a device. Applications access devices through standardized call functions that are independent of any particular driver.

Optionally, registering the device node corresponding to the terminal device may specifically include: in the memory space, first generate according to the string format based on the device driver name, device node name and related parameters related to device driver loading and device node creation The device driver file list, and then pre-store the device driver file list in a device file storage independent of the memory space; the terminal device can read the files in the device driver file list, and create a device node according to the device driver file list, The device node is then saved in the device file memory.

Wherein, the device file storage may be a flash storage, or a RAM storage, and the like.

It should be noted that the terminal device can first obtain the device node name of the device node to be created from the device driver file list, then load the device driver according to the device driver name in the device driver file list, and obtain the device node allocated by the Linux operating system number, and then the terminal device can create a device node according to the device node name, related parameters, and device node number.

Wherein, the device node number may include: a major device number and a slave device number.

Furthermore, before the terminal device reads the files in the device driver file list, it can also judge whether the device node has been created according to the mark on the device file storage. If the device node has been created, then the terminal device can directly call the storage device node; if no device node has been created, then the terminal device needs to read the file in the device driver file list, and create a device node according to the device driver file list, and then save the device node in the device file memory for future use follow-up needs.

It should be noted that if a device node has been created, but the files in the device driver file list have been updated, then the terminal device needs to delete all device nodes stored in the device file storage, and then read the device file list, and repeat According to the device driver name, device node name and related parameters related to device driver loading and device node creation, the step of generating a device driver file list in a string format is used to obtain the device node corresponding to the new device driver file list.

Through the above optional implementation method, the terminal device only needs to create a device node for the first time when the Linux operating system is started. The terminal device only needs to call the previously stored device node, which not only saves the dynamic process of device node creation, but also ensures the startup speed of the Linux operating system.

202. On the device node, set a data writing interface between the user space and the kernel space.

In the embodiment of the present disclosure, after the terminal device registers the device node, a data writing interface can be set on the device node. The data writing node is a data transmission channel between the kernel space and the user space. The terminal device can pass The data writing interface transfers application information from the user space to the kernel space, and the data writing interface is located between the user space and the kernel space.

For example, please refer to FIG. 3 , which is a schematic structural diagram of a memory space of a terminal device provided by one or more embodiments of the present disclosure. As shown in FIG. 3 , the memory space 31 of the terminal device includes user space and In the kernel space, a device node 32 is set between the user space and the kernel space, and a data writing interface 321 is set on the device node 32. The terminal device can write the application information in the user space to the kernel space through the data writing interface 321 middle.

203. In the user space, obtain application information corresponding to the first application program.

204. Transmit the application information from the user space to the kernel space through the preset data writing interface between the user space and the kernel space.

205. Save the application information in the kernel space.

In the embodiment of the present disclosure, for the description of steps 203-205, please refer to the detailed description of steps 101-103 in the embodiment, which will not be repeated in the embodiment of the present disclosure.

Optionally, storing the application information in the kernel space may specifically include: storing the device information in the first memory area, and storing the device running state in the second memory area.

Wherein, the first memory area and the second memory area are two different memory areas in the kernel space of the terminal device, which are respectively used to store device information and device operating status.

It should be noted that the terminal device stores application information in the kernel space, and can store device information and device running status separately, that is, the terminal device can divide two memory areas in the kernel space, and one memory area is used to store the device information, another memory area is used to hold the device operating state.

Exemplarily, as shown in FIG. 3, the terminal device can write the application information in the user space into the kernel space through the data writing interface 321, and save the device information in the first memory area 33, and save the device operating state stored in the second memory area 34.

Optionally, when the terminal device divides the two memory areas, it divides by applying for memory; the applied memory may include: static memory and dynamic memory.

Among them, static memory refers to the memory allocated by the compiler when the program starts to run. Its allocation is completed when the program starts to compile and does not occupy CPU resources; when the user cannot determine the size of the space, or the space is too large, the memory on the stack When allocation is not possible, dynamic memory allocation is used. In the embodiment of the present disclosure, the terminal device may apply for a static memory to store application information.

Through the above optional implementation, the terminal device can store the device information and device running status of the hardware module separately in two memory areas in the kernel space, so that the terminal device can quickly make differentiated calls and reduce the workload of the terminal device.

Further, the terminal device saves the device information in the first memory area, and saves the device operating state in the second memory area, which may specifically include:

Set a plurality of enumeration variables in the kernel space, each enumeration variable corresponds to a hardware module; define the first position index and the second position index of the hardware module corresponding to each enumeration variable in the kernel space; set each The device information of each hardware module is stored in the first memory area according to the corresponding first position index, and the device operation status of each hardware module is stored in the second memory area according to the corresponding second position index.

Among them, the first location index is used to define the storage location of the device information of each hardware module in the first memory area, and the second location index is used to define the storage location of the device operating state of each hardware module in the second memory area .

It should be noted that after the terminal device divides the kernel space into two memory areas, it can store device information and device operating status in the two memory areas respectively, and the terminal device needs to store according to the preset location index when storing , so the terminal device can set multiple enumeration variables in the kernel space, each enumeration variable corresponds to a hardware module, that is, corresponds to a device, and the enumeration variable can be used to identify the location index of the hardware module, that is, to identify the hardware module's The location and order in which application information is stored in memory.

After the enumeration variables are set on the terminal device, the position index of the corresponding hardware module can be defined for each enumeration variable. The position index can be divided into: a first position index and a second position index. The first position index can be used for Define the storage location of the device information of each hardware module in the first memory area, and the second location index is used to define the storage location of the device running state of each hardware module in the second memory area, that is, each hardware module has There are two parameters of device information and device operating status. When the terminal device stores the device information and device operating status in the kernel space, it can save the device information of the hardware module in the first memory area in the kernel space according to the first position index , and save the device running state of the hardware module in the second memory area in the kernel space according to the second position index.

It should be noted that each hardware module corresponds to two location indexes, which respectively indicate the storage location of the device information of the hardware module in the first memory area, and the storage location of the device operating state of the hardware module in the second memory area. Location.

Wherein, the location index of each hardware module is different.

Through the above optional implementation method, the location index of its application information stored in the kernel space can be defined for each hardware module, so that the terminal device can store the application information in the kernel space according to the location index corresponding to each hardware module. This can prevent the terminal device from saving the application information at will, and make the application information stored in the kernel space more orderly.

206. When the second application program needs to call the application information, transmit the application information from the kernel space to the user space through the preset data readout interface between the user space and the kernel space.

In the embodiment of the present disclosure, after the terminal device saves the application information in the kernel space in advance, if the second application program in the user space needs to call the application information, then the terminal device can transfer the application information from the kernel space to the user space .

Among them, the terminal device transmits the application information through the data readout interface, the data readout interface is an interface set in advance, the data readout interface is located between the user space and the kernel space, and the data readout interface is used Used to transfer information from kernel space to user space.

It should be noted that the first application program and the second application program are different application programs, and the data read interface and the data write interface are different data interfaces set in the device node.

It can be understood that when the first application program is running, the terminal device can save the application information from the user space to the kernel space through the data writing interface; when another application program, that is, the second application program needs to call the application information, The terminal device can transmit application information from the kernel space to the user space through the data readout interface.

Optionally, when the second application program needs to call the application information, the application information is transferred from the kernel space to the user space through the preset data readout interface between the user space and the kernel space, which may specifically include:

When the second application program needs to call the application information, obtain the permission list of the device node; if it is detected that the permission list includes the second application program, then through the pre-set data readout interface between the user space and the kernel space, from the kernel The application information is transferred from the user space to the user space.

In this optional implementation, if the second application program needs to call the application information when it is running, then the terminal device needs to call the application information from the kernel space. Before calling, it needs to check the application permission first. Therefore, the terminal device The permission list of the device node can be obtained. The permission list is set when the device node is registered. If the permission list includes the second application program, it means that the second application program can call the application information from the kernel space. Therefore, the terminal device The application information can be transferred from the kernel space to the user space through the data readout interface; if the second application program is not included in the permission list, it means that the second application program cannot call the application information from the kernel space, then the terminal device There is no need to call application information from kernel space.

Through the above optional implementation, the terminal device can set permissions for the device node, and only the application program with the permission can call the application information from the kernel space. It can also guarantee the security of application information.

When the second application program needs to call the application information, it reads the device information from the first memory area of the kernel space through the first data readout interface and transmits it to the user space, and through the second data readout interface, reads the device information from the kernel space The device operating state is read from the second memory area of the device and transferred to user space.

It should be noted that since the application information includes: device information and device operating status, and the device information is stored in the first memory area of the kernel space, and the device operating status is stored in the second memory area of the kernel space, therefore When the terminal device calls the application information from the kernel space, it can respectively read the device information and the device operation status through the two data readout interfaces; that is, the terminal device can read the device information through the first data readout interface and transfer the device information from the The first memory area of the kernel space is transmitted to the user space, and then the operating state of the device is read through the second data readout interface, and the operating state of the device is transferred from the second memory area of the kernel space to the user space.

Wherein, the data readout interface may include: a first data readout interface and a second data readout interface, the first data readout interface and the second data readout interface are different data readout interfaces set in the device node .

Optionally, in this embodiment of the present disclosure, the device node may include at least three data interfaces, which are: a data write interface, a first data read interface, and a second data read interface. Wherein, the data writing interface is a data interface for the terminal device to transfer application information from the user space to the kernel space; the first data readout interface is a data interface for the terminal device to transfer device information from the first memory area of the kernel space to the user space ; The second data readout interface is a data interface for the terminal device to transmit the operating state of the device from the second memory area of the kernel space to the user space.

Exemplarily, as shown in Figure 3, a device node 32 is provided between the user space and the kernel space, and a data write interface 321, a first data read interface 322 and a second data read interface are provided on the device node 323. The terminal device can write the application information in the user space into the kernel space through the data writing interface 321, and can also read the device information from the first memory area 33 in the kernel space to the user space through the first data readout interface 322. In the space, the operating status of the device can also be read from the second memory area 34 in the kernel space to the user space through the second data readout interface 323 .

Optionally, taking the Linux operating system as an example of the terminal device, the data writing interface 321, the first data reading interface 322 and the second data reading interface 323 in FIG. 3 above can all be implemented by ioctl. For example, this solution can configure a device-related information and operation function through the kernel code, call misc_register(&devInfo_device) to register the device node, and implement the ioctl driven by the device. For the driven ioctl, the first interface is the data write interface 321, the second interface is the first data read interface 322, and the third interface is the second data read interface 323.

Among them, the data writing interface 321 is equivalent to an interface for setting user space strings (that is, application information can be expressed in the form of strings) into the kernel, and saving them to the memory managed by the devInfo module (equivalent to the dev directory) , and sorted by defined module index.

The first data readout interface 322 is an interface for transferring the memory managed by the devInfo module storing device information to the user space. When the operating system starts, the driver part will complete the detection of each module, and also call the devInfo interface to write the detection result string into the memory of the devInfo module, so the user space can obtain the memory of the devInfo module in the kernel through this interface. The desired device information is obtained.

The second data readout interface 323 is an interface for transferring the memory managed by the devInfo module and storing the operating state of the device to the user space. This interface is similar to the first data readout interface 322 . It is just that the first data readout interface 322 stores information such as device model and manufacturer, which have been stored during the startup process of the operating system. The information transmitted by the second data readout interface 323 is the running status stored in the devInfo module in the kernel, which will be used for monitoring applications during the entire cycle of operating system running. For example, this part of the logic is generally that if some abnormality occurs during the operation of the driver software, the abnormality is recorded and summarized, and a corresponding character string is generated and stored in the allocated memory, which can also be realized through the second data readout interface 323. Abnormal monitoring of device operation.

Optionally, the first data readout interface 322 and the second data readout interface 323 are designed independently of each other and can be used for different applications. Therefore, both interfaces may be used in an application development project, or only one of them may be selected.

That is to say, through the content in Figure 3 above, when an application or process in the operating system needs to obtain hardware information or device operation status, it can directly call the devInfo module: first, it is necessary to configure the permission to access the device node in the code, and then run it in the Open the dev/devInfo device node in the system, and then call the interface provided by ioctl to transfer memory information to get the string information. You don’t need to implement a set of driver codes to do these tasks. In this way, if there are multiple applications or processes in the operating system that want to obtain hardware-related information, they can directly open dev/devInfo to use, reducing related code work, and the overall code structure is relatively simple.

207. Transmit the application information to the second application program through the user space.

In the embodiment of the present disclosure, after the terminal device transmits the application information from the kernel space to the user space through the data readout interface, the application information may be transmitted to the second application program for calling when the second application program is running.

To sum up, in the embodiment of the present disclosure, the terminal device can first set up a device node in the memory space, and then set a data writing interface on the device node, and then obtain the application information corresponding to the first application program in the user space, The application information includes: device information and device running status; the terminal device can transmit the application information from the user space to the kernel space through the data writing interface, and save the application information in the kernel space; then if the second application program needs to call The application information can be transmitted from the kernel space to the user space through the data readout interface, and then transmitted to the second application program. Through this solution, the terminal device can pre-set the data writing interface in the user space and the kernel space, so that the terminal device can write the application information obtained in the user space through the data writing interface, transmit and store it in the kernel space , if the second application program wants to call the application information, it does not need to obtain the application information again, it can be obtained directly from the kernel space; and no matter what application information the terminal device obtains in the user space, it can pass the data The write interface is stored in the kernel space, so there will be no situation where the user space stores part of the information and the kernel space stores part of the information, which effectively improves the standardization of terminal equipment storage hardware module information.

In addition, this solution organizes hardware-related information into a highly standardized module, making the software structure clearer and more concise, enabling the kernel space to directly access the existing information in the user space during the normalization work, avoiding duplication and confusion The result is that the code is clearer and easier to use, which improves the clarity of the code implemented on the software after the unified interface, and the code quality is higher.

Please refer to FIG. 4 , which is a schematic structural diagram of a terminal device provided by one or more embodiments of the present disclosure. As shown in FIG. 4 , the memory space of the terminal device includes: user space and kernel space, and the terminal device includes :

An acquisition module 401, configured to acquire application information corresponding to the first application program in user space, where the application information includes: device information and device operating status;

The processing module 402 is configured to transfer the application information from the user space to the kernel space through a preset data writing interface between the user space and the kernel space, and store the application information in the kernel space.

Optionally, the processing module 402 is also configured to register a device node corresponding to the terminal device in the memory space, and the device node is located between the user space and the kernel space;

The processing module 402 is further configured to set a data writing interface between the user space and the kernel space on the device node.

Optionally, the processing module 402 is specifically configured to save the device information in the first memory area, and save the device operating state in the second memory area;

Optionally, the processing module 402 is specifically configured to set multiple enumeration variables in the kernel space, each enumeration variable corresponds to a hardware module;

The processing module 402 is specifically configured to define a first position index and a second position index in the kernel space of the hardware module corresponding to each enumerated variable;

The processing module 402 is specifically configured to save the device information of each hardware module in the first memory area according to the corresponding first location index, and save the device running state of each hardware module in the first memory area according to the corresponding second location index. In the second memory area;

Optionally, the processing module 402 is also used to transmit the application information from the kernel space to the user space through the preset data readout interface between the user space and the kernel space when the second application program needs to call the application information ;

The processing module 402 is further configured to transmit the application information to the second application program through the user space;

Wherein, the first application program and the second application program are different application programs, and the data read interface and the data write interface are different data interfaces set in the device node.

Optionally, the obtaining module 401 is specifically used to obtain the permission list of the device node when the second application program needs to call the application information;

The processing module 402 is specifically configured to transmit application information from the kernel space to the user space through a preset data readout interface between the user space and the kernel space if it is detected that the permission list includes the second application program.

Optionally, the processing module 402 is specifically configured to read the device information from the first memory area of the kernel space and transmit it to the user space through the first data readout interface when the second application program needs to call the application information, and Read the operating state of the device from the second memory area of the kernel space and transmit it to the user space through the second data readout interface;

In the embodiments of the present disclosure, each module can implement the information transmission method provided by the above method embodiments, and can achieve the same technical effect. To avoid repetition, details are not repeated here.

Please refer to FIG. 5 , which is a second structural diagram of a terminal device provided by one or more embodiments of the present disclosure. As shown in FIG. 5 , the memory space of the terminal device includes: user space and kernel space, and the terminal device can include:

A memory 501 storing executable program codes;

a processor 502 coupled to the memory 501;

Wherein, the processor 502 invokes the executable program code stored in the memory 501 to execute the information transmission method performed by the terminal device in the foregoing method embodiments.

Embodiments of the present disclosure provide a computer-readable storage medium, which stores a computer program, wherein when the computer program is executed by a processor, some or all steps of the methods in the above method embodiments are implemented.

Embodiments of the present disclosure also provide a computer program product, wherein when the computer program product is run on a computer, some or all of the steps of the method in the above method embodiments are implemented.

Embodiments of the present disclosure also provide an application distribution platform, wherein the application distribution platform is used to distribute computer program products, wherein, when the computer program products run on the computer, part or all of the methods in the above method embodiments are implemented step.

It should be understood that reference throughout the specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic related to the embodiment is included in at least one embodiment of the present disclosure. Thus, appearances of "in one embodiment" or "in an embodiment" in various places throughout the specification are not necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments. Those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present disclosure.

In various embodiments of the present disclosure, it should be understood that the sequence numbers of the above-mentioned processes do not necessarily mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, and should not be used in the implementation of the present disclosure. The implementation of the examples constitutes no limitation.

The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, located in one place, or distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the above-mentioned integrated units are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-accessible memory. Based on this understanding, the technical solution of the present disclosure, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a memory , including several requests to make a computer device (which may be a personal computer, a server, or a network device, etc., specifically, a processor in the computer device) execute part or all of the steps of the above-mentioned methods in various embodiments of the present disclosure.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, and the storage medium includes read-only Memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), programmable read-only memory (Programmable Read-only Memory, PROM), erasable programmable read-only memory (Erasable Programmable Read Only Memory, EPROM), One-time Programmable Read-Only Memory (OTPROM), Electronically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc (Compact Disc Read-Only Memory, CD-ROM) or other optical disk storage, magnetic disk storage, tape storage, or any other computer-readable medium that can be used to carry or store data.

Industrial Applicability

In the information transmission method provided by this disclosure, the terminal device writes the application information obtained in the user space into the interface through the data, transmits and stores it in the kernel space, and when it is necessary to obtain the stored information, it can be directly obtained from the kernel space and any application information acquired by the terminal device in the user space can be stored in the kernel space through the data writing interface, so there will be no situation where the user space stores part of the information and the kernel space stores part of the information. It effectively improves the standard unification degree of terminal equipment storage hardware module information, and has strong industrial applicability.

Claims

An information transmission method, applied to a terminal device, the memory space of the terminal device includes: user space and kernel space, the method includes:

In the user space, the application information corresponding to the first application program is obtained, and the application information includes: device information and device running status;

Transmitting the application information from the user space to the kernel space through a preset data writing interface between the user space and the kernel space, and saving the application information in the kernel space middle.
The method according to claim 1, wherein, before obtaining the application information through the first application program in the user space, the method further comprises:

In the memory space, register a device node corresponding to the terminal device, where the device node is located between the user space and the kernel space;

On the device node, a data writing interface between the user space and the kernel space is set.
The method according to claim 1, wherein the kernel space includes: a first memory area and a second memory area, and storing the application information in the kernel space includes:

storing the device information in the first memory area, and storing the device operating state in the second memory area;

Wherein, the first memory area and the second memory area are different memory areas in the kernel space.
The method according to claim 3, wherein storing the device information in the first memory area and storing the device operating state in the second memory area comprises:

Setting a plurality of enumeration variables in the kernel space, each enumeration variable corresponding to a hardware module;

defining a first position index and a second position index in the kernel space of the hardware module corresponding to each enumerated variable;

storing the device information of each hardware module in the first memory area according to the corresponding first location index, and saving the device running state of each hardware module in the second memory area according to the corresponding second location index middle;

Wherein, the first location index is used to define the storage location of the device information of each hardware module in the first memory area, and the second location index is used to define the device operation status of each hardware module in the The storage location in the second memory area.
The method according to any one of claims 1 to 4, wherein the method further comprises:

When the second application program needs to call the application information, the application information is transmitted from the kernel space to the user through the preset data readout interface between the user space and the kernel space. space;

transmitting the application information to the second application via the user space;

Wherein, the first application program and the second application program are different application programs, and the data read interface and the data write interface are different data interfaces provided in the device node.
The method according to claim 5, wherein, when the second application program needs to call the application information, through the preset data readout interface between the user space and the kernel space, from the The application information is transferred to the user space in the kernel space, including:

When the second application program needs to call the application information, obtain the permission list of the device node;

If it is detected that the permission list includes the second application program, the application program is read from the kernel space through the preset data readout interface between the user space and the kernel space. Information is transferred to the user space.
The method according to claim 5, wherein the data readout interface comprises: a first data readout interface and a second data readout interface, and when the second application needs to call the application information, the The data readout interface between the user space and the kernel space is set, and the application information is transferred from the kernel space to the user space, including:

When the second application program needs to call the application information, the device information is read from the first memory area of the kernel space through the first data readout interface and transmitted to the user space, And through the second data readout interface, read the operating state of the device from the second memory area of the kernel space and transmit it to the user space;

Wherein, the first data readout interface and the second data readout interface are different data readout interfaces provided in the device node.
A terminal device, the memory space of the terminal device includes: user space and kernel space, including:

An acquisition module configured to acquire application information corresponding to the first application program in the user space, where the application information includes: device information and device operating status;

A processing module configured to transmit the application information from the user space to the kernel space through a preset data writing interface between the user space and the kernel space, and save the application information in the kernel space.
The terminal device according to claim 8, wherein,

The processing module is further configured to register a device node corresponding to the terminal device in the memory space, where the device node is located between the user space and the kernel space;

The processing module is further configured to set a data writing interface between the user space and the kernel space on the device node.
The terminal device according to claim 8, wherein the kernel space includes: a first memory area and a second memory area;

The processing module is further configured to save the device information in the first memory area, and save the device operating state in the second memory area;

Wherein, the first memory area and the second memory area are different memory areas in the kernel space.
The terminal device according to claim 10, wherein,

The processing module is further configured to set a plurality of enumeration variables in the kernel space, each enumeration variable corresponds to a hardware module;

The processing module is further configured to define a first location index and a second location index of the hardware module corresponding to each enumerated variable in the kernel space;

The processing module is further configured to save the device information of each hardware module in the first memory area according to the corresponding first location index, and store the device operating state of each hardware module according to the corresponding second location index stored in the second memory area;

Wherein, the first location index is used to define the storage location of the device information of each hardware module in the first memory area, and the second location index is used to define the device operation status of each hardware module in the The storage location in the second memory area.
The terminal device according to any one of claims 8 to 11, wherein,

The processing module is further configured to, when the second application program needs to call the application information, through the preset data read interface between the user space and the kernel space, from the kernel space transmitting the application information to the user space;

The processing module is further configured to transmit the application information to the second application program through the user space;

Wherein, the first application program and the second application program are different application programs, and the data read interface and the data write interface are different data interfaces provided in the device node.
The terminal device according to claim 12, wherein,

The obtaining module is further configured to obtain the permission list of the device node when the second application program needs to call the application information;

The processing module is further configured to, if it is detected that the permission list includes the second application program, through the preset data read-out interface between the user space and the kernel space, read from the The application information is transmitted from the kernel space to the user space.
The terminal device according to claim 12, wherein the data readout interface comprises: a first data readout interface and a second data readout interface;

The processing module is further configured to read the device information from the first memory area of the kernel space through the first data readout interface when the second application program needs to call the application information And transmit to the user space, and read the operating state of the device from the second memory area of the kernel space through the second data readout interface and transmit to the user space;

Wherein, the first data readout interface and the second data readout interface are different data readout interfaces provided in the device node.
A terminal device, the memory space of the terminal device includes: user space and kernel space, including:

a memory storing executable program code;

a processor coupled to the memory;

The processor invokes the executable program code stored in the memory to execute the information transmission method according to any one of claims 1 to 7.
A computer-readable storage medium storing a computer program, wherein the computer program implements the information transmission method according to any one of claims 1 to 7 when executed by a processor.