Information processing method and device, terminal equipment, storage medium and program product

By storing target information in the operating system kernel space, the target application can directly obtain it from the kernel space, which solves the problem of low information interaction efficiency in terminal devices, realizes efficient information interaction and resource utilization, and improves user experience.

CN121996440APending Publication Date: 2026-05-08BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
BEIJING XIAOMI MOBILE SOFTWARE CO LTD
Filing Date
2024-11-05
Publication Date
2026-05-08

AI Technical Summary

Technical Problem

In existing technologies, when applications in terminal devices interact with the operating system, the information exchange efficiency is low, requiring cross-process communication, which leads to increased resource consumption and latency, affecting the user experience.

Method used

The target information is stored in the kernel space of the operating system. When the target application calls the service, it directly retrieves the information from the kernel space, reducing unnecessary interaction operations and realizing information exchange through system calls.

Benefits of technology

It improves the efficiency of application calls to services, reduces resource consumption and latency, enhances user experience, and avoids the overhead of cross-process communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121996440A_ABST
    Figure CN121996440A_ABST
Patent Text Reader

Abstract

The invention relates to an information processing method and device, terminal equipment, a storage medium and a program product. The information processing method comprises the steps that target information is stored in a kernel space; wherein the target information represents whether a target application program can call a target service in a system or not; and when the target application calls the target service, obtaining the target information from the kernel space. According to the technical scheme, the process of information interaction between the target application program and the target service through the kernel and the process of obtaining the target information from the target service are omitted, unnecessary interaction operation is saved, the interaction efficiency is improved, the efficiency of calling the target service by the target application program is improved, and the use experience of a user is further improved. In addition, the mode does not need cross-process communication, so that the overhead is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of information processing technology, and in particular to an information processing method, apparatus, terminal equipment, storage medium, and computer program product. Background Technology

[0002] With the development of technology, information processing is playing an increasingly important role. Information processing involves many aspects, including information transmission in different terminal devices, which in turn involves information processing; and information processing also occurs in different parts within the same device.

[0003] Typically, terminal devices have an operating system and applications installed. The applications and the operating system can interact to achieve the corresponding functions. Summary of the Invention

[0004] This disclosure provides an information processing method, apparatus, terminal equipment, storage medium, and computer program product.

[0005] A first aspect of this disclosure provides an information processing method, comprising: storing target information in kernel space; wherein the target information indicates whether a target application can call a target service in the system; and retrieving the target information from the kernel space when the target application calls the target service.

[0006] In one embodiment, storing the target information in the kernel space includes: determining the target information; and storing the target information in the kernel space.

[0007] In one embodiment, determining the target information includes: obtaining a configuration operation applied to a configuration control; wherein the configuration control is used to configure whether the target application can call the target service; and determining the target information based on the configuration result of the configuration operation.

[0008] In one embodiment, storing the target information in the kernel space includes: the target service storing the target information in the kernel space via a system call.

[0009] In one embodiment, obtaining the target information from the kernel space includes: the target application obtaining the target information from the kernel space via a system call.

[0010] In one embodiment, the method further includes updating the target information.

[0011] In one embodiment, updating the target information includes: detecting an update operation performed on a configuration control; wherein the configuration control is used to configure whether the target application can call the target service; and updating the target information according to the update result of the update operation on the configuration control.

[0012] In one embodiment, updating the target information includes: updating the target information already stored in the kernel space according to the update result via a system call.

[0013] In one embodiment, the target service includes at least one of the following: activity management service; package management service; window management service.

[0014] In one embodiment, the packet management service includes at least one of the following: location service; permission check service; network status acquisition service; device information acquisition service; update service; and information query service.

[0015] In one embodiment, the target information includes: first information for indicating the target application; second information for indicating whether the target application can call the target service; and third information for indicating the correspondence between the first information and the second information.

[0016] A second aspect of this disclosure provides an information processing apparatus, comprising: a storage module for storing target information in kernel space; wherein the target information indicates whether a target application can call a target service in the system; and an acquisition module for acquiring the target information from the kernel space when the target application calls the target service.

[0017] A third aspect of this disclosure provides a terminal device, including: a processor and a memory for storing executable instructions capable of running on the processor, wherein: when the processor runs the executable instructions, the executable instructions perform the method described in any of the above embodiments.

[0018] A fourth aspect of this disclosure provides a non-transitory computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the method described in any of the above embodiments.

[0019] A fifth aspect of this disclosure provides a computer program product, including a computer program or executable instructions, which, when executed by a processor, implement the method described in any of the above embodiments.

[0020] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0021] The solution of this disclosure stores target information indicating whether a target application can call a target service in the system in kernel space. When the target application calls the target service, it can directly obtain this target information from kernel space. Since the target information is stored in the operating system kernel, and the target application interacts directly with the operating system kernel, and the target application has the ability to interact directly with the kernel, this eliminates the process of the target application interacting with the target service through the kernel and obtaining the target information from the target service. This saves unnecessary interaction operations, improves interaction efficiency, and thus improves the efficiency of the target application calling the target service, further enhancing the user experience. In addition, this method does not require inter-process communication, thereby reducing overhead.

[0022] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

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

[0024] Figure 1 This is a schematic diagram illustrating an information processing method according to an exemplary embodiment;

[0025] Figure 2 This is a schematic diagram illustrating a comparison of the time taken for a target application to acquire target information, according to an exemplary embodiment.

[0026] Figure 3 This is a schematic diagram illustrating a method for storing target information according to an exemplary embodiment;

[0027] Figure 4 This is a schematic diagram illustrating the determination of target information according to an exemplary embodiment;

[0028] Figure 5 This is a schematic diagram illustrating an update of target information according to an exemplary embodiment;

[0029] Figure 6 This is a schematic diagram illustrating an information processing apparatus according to an exemplary embodiment;

[0030] Figure 7 This is a schematic diagram illustrating an embodiment of acquiring target information;

[0031] Figure 8 This is an example of a method of transmission shown in an exemplary embodiment. Figure 7A schematic diagram illustrating the data analysis performed in the manner shown.

[0032] Figure 9 This is a schematic diagram illustrating another method for acquiring target information according to an exemplary embodiment;

[0033] Figure 10 This is a schematic diagram illustrating another method for acquiring target information according to an exemplary embodiment;

[0034] Figure 11 This is a block diagram illustrating a terminal device according to an exemplary embodiment. Detailed Implementation

[0035] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses consistent with some aspects of this disclosure as detailed in the appended claims.

[0036] refer to Figure 1 This is a schematic diagram of an information processing method, which includes:

[0037] S100 stores the target information in the kernel space; the target information indicates whether the target application can call the target service in the system.

[0038] S200 retrieves target information from the kernel space when the target application calls the target service.

[0039] The solution in this embodiment can be applied to terminal devices, and the executing entity can be a terminal device, which can include mobile terminal devices and fixed terminal devices, etc. Mobile terminal devices can include mobile phones, tablets, in-vehicle central control devices, wearable devices, smart devices, and aircraft, etc. Smart devices can include smart office equipment, smart home equipment, and robots, etc.

[0040] Terminal devices have an operating system, and the type of operating system is not limited, including but not limited to: desktop operating systems, mobile terminal operating systems, server operating systems, etc., such as Android, Microsoft, HarmonyOS and Apple operating systems.

[0041] The target application can be any application installed on the terminal device, and the target application can be determined based on usage requirements. Here, we will use one of the target applications as an example for explanation.

[0042] For example, the target application is the application corresponding to user space. The operating system's memory can include kernel space and user space. Kernel space is the area in the operating system used to store core information about running the operating system, and processes with specific permissions can access kernel space.

[0043] User space and kernel space are isolated from each other. Applications running in user space can only use some system resources and cannot use certain specific system functions, nor can they directly access kernel data or resources in kernel space, nor can they directly call kernel functions executed in kernel space.

[0044] The target information can be predetermined, and after the target information is determined, it can be stored in the kernel space.

[0045] There are no limitations on how target information can be stored in kernel space. Any method that can store target information in kernel space is within the protection scope of this embodiment, including but not limited to: using system calls.

[0046] For example, the target service stores target information in kernel space.

[0047] For example, the method of determining the target information is not limited; the target information can be determined based on the configuration information of the target information.

[0048] For example, any target application has target information corresponding to each target service.

[0049] For example, the target service in the system can be any system service that can be invoked by the application, and can be determined according to business needs. In this embodiment, the target service is not limited; any service in the system that the target application can invoke can be used as the target service.

[0050] For example, the kernel space can store target information corresponding to each target application. Each piece of target information can indicate whether a target application can call at least one target service, or whether at least one target application can call the same target service. A piece of target information can indicate the calling permissions of the same target application to different target services, or it can indicate the calling permissions of multiple different target applications to the same target service.

[0051] After storing the target information in kernel space, if the target application needs to call the target service, it is necessary to determine whether the target application can call the target service. The target information can be used to indicate whether the target application can call the target service, so it can be determined whether the target application can call the target service by obtaining the target information.

[0052] For example, the target information obtained by the target application is the target information corresponding to the target service called by the target application. Thus, the target application can determine whether it can call the target service based on the target information, reducing the occurrence of mismatch or error in obtaining target information.

[0053] There are no limitations on how target information can be obtained from kernel space, including but not limited to obtaining target information through system calls.

[0054] Once the target application obtains the target information, it can determine whether it is capable of calling the target service. If it is capable of calling the target service, the target application can proceed with the call; otherwise, it will not.

[0055] refer to Figure 2 This is a diagram illustrating the time taken for a target application to acquire target information. Figure 2 The horizontal axis represents the number of times, and the vertical axis represents the delay time. The units can be picoseconds, nanoseconds, microseconds, or milliseconds, etc.

[0056] Figure 2 The relatively darker bars in the diagram represent the time spent obtaining target information without the described method, such as the time spent calling the target service via an API call. The relatively brighter bars represent the time spent obtaining target information using this solution, such as the time spent calling the target service via a native API call. The comparison shows that this solution can significantly reduce the time spent obtaining target information.

[0057] By storing target information indicating whether a target application can call a target service in the kernel space, this information can be directly retrieved from the kernel space when the target application calls the target service. Since the target information is stored in the operating system kernel, and the target application interacts directly with the kernel, this eliminates the need for the target application to interact with the target service through the kernel and retrieve the target information from the service. This saves unnecessary interaction operations, improves interaction efficiency, and consequently improves the efficiency of the target application calling the target service. It also reduces resource consumption, decreases latency in calling system services, reduces lag, and further enhances the user experience. Furthermore, this method eliminates the need for inter-process communication, thus reducing overhead.

[0058] In one embodiment, the target service includes at least one of the following:

[0059] Event management services;

[0060] Package management services;

[0061] Window management service.

[0062] For example, a package management service includes at least one of the following:

[0063] Location services;

[0064] Permission check service;

[0065] A service to obtain network status;

[0066] Services for obtaining device information;

[0067] Update service;

[0068] Information retrieval service.

[0069] For example, window management services may include various services for displaying windows and interfaces.

[0070] In one embodiment, reference Figure 3 This is a schematic diagram of storing target information. S100, storing the target information in the kernel space includes:

[0071] S101, Determine target information.

[0072] S102 stores the target information in the kernel space.

[0073] Before storing target information, it is necessary to determine whether the target application can call the target service. This can be determined through the corresponding configuration, which is related to user operations. This configuration can be preset or default.

[0074] Each target application can have corresponding target information for any target service, which makes it easier to determine the target application's access permissions to each target service.

[0075] Once the target information is determined, it can be stored in the kernel space.

[0076] For example, storing target information in kernel space includes:

[0077] The target service stores target information in kernel space via system calls.

[0078] System calls are special interfaces provided by the operating system to user programs. User programs can use system calls to notify the operating system that they need to execute kernel functions in kernel space, thereby accessing information in kernel space. User programs can include system service programs. Because kernel space and user space are isolated from each other, and user programs cannot directly and arbitrarily access kernel space, this method allows system service programs to obtain target information while ensuring the security and reliability of kernel space, provided they are permitted to access kernel space.

[0079] For example, refer to Figure 4 This is a schematic diagram of a method for determining target information, which includes:

[0080] S1011, obtain the configuration operation applied to the configuration control; wherein, the configuration control is used to configure whether the target application can call the target service.

[0081] S1012, Determine the target information based on the configuration result of the configuration operation.

[0082] The terminal device can display configuration controls for configuring whether the target application can call the target service. The properties of the configuration controls are not limited, such as size, style, color and position, which can be determined according to the display parameters of the controls or according to the usage requirements.

[0083] The terminal device can also detect configuration operations performed on the configuration control. These configuration operations are used to configure whether the target application can call the target service based on the configuration control.

[0084] For example, a configuration control can be a control for inputting configuration parameters, with different configuration parameters representing different configuration results. Based on the configuration parameters input during the configuration operation, the configuration result can be determined, thereby identifying the target information.

[0085] For example, configuration parameters can be represented by numbers or characters. For instance, if the configuration parameter input during the configuration operation is 1, the determined target information indicates that the target application can call the target service. If the configuration parameter input during the configuration operation is 0, the determined target information indicates that the target application cannot call the target service.

[0086] For example, a configuration control can be a control with an on state and an off state. The state of the configuration control can be determined according to the configuration operation. The state of the configuration control after configuration is the configuration result. The target information can be obtained based on the result.

[0087] If the configuration control is enabled after configuration, the target information indicates that the target application can call the target service. If the configuration control is disabled after configuration, the target information indicates that the target application cannot call the target service.

[0088] For example, the terminal device may display a configuration interface, which may include configuration controls.

[0089] In one embodiment, obtaining target information from kernel space includes:

[0090] The target application obtains target information from the kernel space through system calls.

[0091] System calls are special interfaces provided by the operating system to user programs. User programs can use system calls to notify the operating system that they need to execute kernel functions in kernel space, thereby accessing information in kernel space. User programs can include target applications. Because kernel space and user space are isolated from each other, and target applications cannot directly and arbitrarily access kernel space, this method allows target applications to obtain target information while ensuring the security and reliability of kernel space, even when they are permitted to access kernel space.

[0092] In one embodiment, the method further includes:

[0093] Update target information.

[0094] Whether a target application can call a target service is updatable. If the target application's permission to call the target service changes, it means that the target application has changed from being unable to call the target service to being able to call the target service, or vice versa.

[0095] When the result of the target application's ability to call the target service changes, the target information is updated. After the target information is updated, the target information previously stored in kernel space is also updated, and when the target application retrieves the target information, it obtains the updated target information. This ensures timely updates of the target information, guaranteeing that the target application receives the most up-to-date information. It reduces the likelihood of the target application obtaining abnormal target information due to untimely updates, thereby improving the accuracy of determining whether the target application can call the target service and enhancing the user experience.

[0096] In one embodiment, reference Figure 5 This is a schematic diagram of updating target information. The method includes:

[0097] S10, detect update operations performed on the configuration control; wherein, the configuration control is used to configure whether the target application can call the target service.

[0098] S20: Update the target information based on the update result of the update operation on the configuration control.

[0099] The terminal device can display a configuration control, which is the same as the configuration control used for configuration operations. Both are used to configure whether the target application can call the target service.

[0100] An update operation can be relative. An operation that configures an existing accessory control can be considered an update operation. Alternatively, the last configuration operation out of two consecutive configuration operations can be considered an update operation.

[0101] The update operation allows you to reconfigure the target application to call the target service through configuration controls. The configuration result is the update result, which can be used to update the previous target information, thereby updating the target information.

[0102] For example, the updated result can be used as the updated target information.

[0103] In one embodiment, updating target information includes:

[0104] The target information stored in the kernel space is updated based on the update result via system calls.

[0105] When updating target information, the target service can use system calls to store the updated target information in the kernel space, overwriting or replacing the previously stored target information, thereby updating the target information.

[0106] The target service can update the target information regarding whether the target application can call the target service through system calls. For example, by calling relevant functions, the previously stored target information can be deleted or replaced with the updated target information while the updated target information is being stored.

[0107] In one embodiment, the target information includes:

[0108] The first piece of information is used to indicate the target application;

[0109] The second piece of information is used to indicate whether the target application can call the target service;

[0110] The third piece of information is used to indicate the correspondence between the first and second pieces of information.

[0111] The first information can be represented in the form of characters, numbers, etc., and the second information can be represented in the form of characters or numbers, etc.

[0112] The correspondence represented by the third information may include:

[0113] One-on-one relationship;

[0114] One-to-many relationship;

[0115] A many-to-one relationship.

[0116] In a one-to-one relationship, this target information can indicate whether a target application can call a target service. In this case, each target application has its own separate target information for calling each target service.

[0117] In a one-to-many relationship, this target information can indicate whether multiple target applications can call the same target service. In a many-to-one relationship, this target information can indicate whether a single target application can call multiple target services. The same target information can represent multiple scenarios, thus reducing the amount of target information.

[0118] In one embodiment, reference Figure 6 This is a schematic diagram of an information processing device, which includes:

[0119] Storage module 1 is used to store target information in kernel space; wherein, the target information indicates whether the target application can call the target service in the system;

[0120] The acquisition module 2 is used to acquire the target information from the kernel space when the target application calls the target service.

[0121] In one embodiment, storage module 1 includes:

[0122] A determining unit is used to determine the target information;

[0123] A storage unit is used to store the target information in the kernel space.

[0124] In one embodiment, the determining unit includes:

[0125] A sub-unit is used to acquire configuration operations applied to a configuration control; wherein the configuration control is used to configure whether the target application can call the target service;

[0126] A determination subunit is used to determine the target information based on the configuration result of the configuration operation.

[0127] In one embodiment, the storage unit is used for: the target service storing the target information in the kernel space via a system call.

[0128] In one embodiment, module 2 is used to:

[0129] The target application obtains the target information from the kernel space via system calls.

[0130] In one embodiment, the apparatus further includes:

[0131] An update module is used to update the target information.

[0132] In one embodiment, the update module includes:

[0133] A detection unit is used to detect update operations performed on a configuration control; wherein the configuration control is used to configure whether the target application can call the target service;

[0134] An update unit is used to update the target information based on the update result of the configuration control in the update operation.

[0135] In one embodiment, the update unit is used for:

[0136] The target information stored in the kernel space is updated based on the update result via system calls.

[0137] In one embodiment, the target service includes at least one of the following:

[0138] Event management services;

[0139] Package management services;

[0140] Window management service.

[0141] In one embodiment, the package management service includes at least one of the following:

[0142] Location services;

[0143] Permission check service;

[0144] A service to obtain network status;

[0145] Services for obtaining device information;

[0146] Update service;

[0147] Information retrieval service.

[0148] In one embodiment, the target information includes:

[0149] The first piece of information is used to instruct the target application;

[0150] The second piece of information is used to indicate whether the target application can call the target service;

[0151] The third piece of information is used to represent the correspondence between the first piece of information and the second piece of information.

[0152] In one embodiment, another example of information processing is also provided.

[0153] With the increasing prevalence and functionality of Android devices, the probability of multiple applications accessing the same system interface simultaneously has increased. This can lead to performance degradation of the interface and a loss of latency guarantees. Therefore, performance optimization of system service interfaces has become extremely important. Common system services include checking permissions, obtaining network status, and retrieving basic phone information.

[0154] refer to Figure 7 This is a schematic diagram of how to acquire target information. Figure 7 The following explanation uses the target service for the permission check of the target application as an example.

[0155] The target application calls the Check Permission interface, which is passed to the server process (System_Server) via the kernel's Binder driver. The System_Server obtains information such as the activity management service lock, package management service lock, and permission management lock to determine the target information. Then, the System_Server, through the kernel's Binder driver, passes the target information to the target application. Finally, the target application receives information indicating whether it is allowed to call the target service. Figure 7 The numbers 1 to 9 shown represent the process by which the target application obtains target information, and the interaction process between the target application, the Binder driver in the kernel, and the target service.

[0156] refer to Figure 8 , as a kind of Figure 7 The diagram illustrates the data analysis performed in this manner. According to big data statistics, approximately 30% of the lag is caused by system service interface latency.

[0157] This embodiment optimizes the information interaction between system services and target applications. System service data is shared within the kernel space, and the target application accesses this data via system calls. For example, regarding permission checks... Figure 9 The diagram shown is a schematic representation of acquiring target information. (Refer to...) Figure 10 This is a schematic diagram of another method for obtaining target information, combined with... Figure 9 and Figure 10 The method includes:

[0158] 1. Add permission data in the kernel space (kernel side), and the target application accesses the data through system calls.

[0159] 2. When the target service in the system service updates data, it does so through a system call in the PermissionManager Service.

[0160] 3. The target application obtains target information from the kernel space through system calls.

[0161] Figure 10 The content shown is relative to Figure 9 The content shown adds a native library, combined with Ioctl system calls specifically for input / output operations, as a way to implement system calls.

[0162] This approach places the target service data from system services within the kernel, which is shared globally by all applications. Target applications do not need to access the data across processes when retrieving target information, reducing scheduling overhead. It optimizes the performance of applications calling system services and reduces the probability of occasional application stuttering.

[0163] It should be noted that the terms "first" and "second" in the embodiments of this disclosure are for ease of description and distinction only, and have no other specific meaning.

[0164] Figure 11 This is a block diagram illustrating a terminal device according to an exemplary embodiment. For example, the terminal device may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0165] Reference Figure 11 The terminal device may include one or more of the following components: processing component 902, memory 904, power component 906, multimedia component 908, audio component 910, input / output (I / O) interface 912, sensor component 914, and communication component 916.

[0166] Processing component 902 typically controls the overall operation of the terminal device, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 902 may include one or more processors 920 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 902 may include one or more modules to facilitate interaction between processing component 902 and other components. For example, processing component 902 may include a multimedia module to facilitate interaction between multimedia component 908 and processing component 902.

[0167] Memory 904 is configured to store various types of data to support operation on the terminal device. Examples of this data include instructions for any application or method operating on the terminal device, contact data, phonebook data, messages, pictures, videos, etc. Memory 904 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0168] Power component 906 provides power to various components of the terminal device. Power component 906 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the terminal device.

[0169] Multimedia component 908 includes a screen that provides an output interface between a terminal device and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a Touch Panel, the screen can be implemented as a touchscreen to receive input signals from the user. The Touch Panel includes one or more touch sensors to sense touches, swipes, and gestures on the Touch Panel. The touch sensors can sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 908 includes a front-facing camera and / or a rear-facing camera. When the terminal device is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera can receive external multimedia data. Each front-facing camera and rear-facing camera can be a fixed optical lens system or have focal length and optical zoom capabilities.

[0170] Audio component 910 is configured to output and / or input audio signals. For example, audio component 910 includes a microphone (MIC) configured to receive external audio signals when the terminal device is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 904 or transmitted via communication component 916. In some embodiments, audio component 910 also includes a speaker for outputting audio signals.

[0171] I / O interface 912 provides an interface between processing component 902 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0172] Sensor assembly 914 includes one or more sensors for providing status assessments of various aspects of the terminal device. For example, sensor assembly 914 can detect the on / off state of the terminal device, the relative positioning of components such as the display and keypad of the terminal device, changes in the position of the terminal device or a component of the terminal device, the presence or absence of user contact with the terminal device, the orientation or acceleration / deceleration of the terminal device, and temperature changes of the terminal device. Sensor assembly 914 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 914 may also include an optical sensor, such as a Complementary Metal Oxide Semiconductor (CMOS) or Charge Coupled Device (CCD) image sensor, for use in imaging applications. In some embodiments, sensor assembly 914 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0173] Communication component 916 is configured to facilitate wired or wireless communication between the terminal device and other devices. The terminal device can access wireless networks based on communication standards, such as Wi-Fi, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 916 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 916 also includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wide Band (UWB), Bluetooth (BT), and other technologies.

[0174] In an exemplary embodiment, the terminal device may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0175] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 904 including executable instructions or a computer program, which can be executed by the processor 920 of the device 900 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0176] A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by the processor of a terminal device, enables the terminal device to perform any of the information processing methods described in the embodiments of this disclosure.

[0177] This disclosure provides a computer program product comprising a computer program or executable instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or executable instructions from the computer-readable storage medium and executes the computer program or executable instructions, causing the computer device to perform any of the information processing methods described in this disclosure.

[0178] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0179] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. An information processing method, characterized in that, include: The target information is stored in the kernel space; wherein, the target information indicates whether the target application can call the target service in the system; When the target application calls the target service, the target information is obtained from the kernel space.

2. The method according to claim 1, characterized in that, The step of storing the target information in kernel space includes: Determine the target information; The target information is stored in the kernel space.

3. The method according to claim 2, characterized in that, Determining the target information includes: Obtain the configuration operation applied to the configuration control; wherein the configuration control is used to configure whether the target application can call the target service; The target information is determined based on the configuration result of the configuration operation.

4. The method according to claim 1 or 2, characterized in that, The step of storing the target information in kernel space includes: The target service stores the target information in the kernel space via system calls.

5. The method according to claim 1, characterized in that, The step of obtaining the target information from the kernel space includes: The target application obtains the target information from the kernel space via system calls.

6. The method according to claim 1, characterized in that, The method further includes: Update the target information.

7. The method according to claim 6, characterized in that, The updating of the target information includes: The system detects update operations performed on a configuration control; wherein the configuration control is used to configure whether the target application can call the target service. The target information is updated based on the update result of the update operation on the configuration control.

8. The method according to claim 7, characterized in that, The updating of the target information includes: The target information stored in the kernel space is updated based on the update result via system calls.

9. The method according to claim 1, characterized in that, The target service includes at least one of the following: Event management services; Package management services; Window management service.

10. The method according to claim 9, characterized in that, The package management service includes at least one of the following: Location services; Permission check service; A service to obtain network status; Services for obtaining device information; Update service; Information retrieval service.

11. The method according to claim 1, characterized in that, The target information includes: The first piece of information is used to instruct the target application; The second piece of information is used to indicate whether the target application can call the target service; The third piece of information is used to represent the correspondence between the first piece of information and the second piece of information.

12. An information processing device, characterized in that, include: A storage module is used to store target information in kernel space; wherein, the target information indicates whether the target application can call the target service in the system; The acquisition module is used to acquire the target information from the kernel space when the target application calls the target service.

13. A terminal device, characterized in that, include: A processor and a memory for storing computer programs or executable instructions capable of running on the processor, wherein: When the processor is used to run the computer program or the executable instructions, the executable instructions perform the method described in any one of claims 1 to 11.

14. A non-transitory computer-readable storage medium, characterized in that, The non-transitory computer-readable storage medium stores a computer program or computer-executable instructions, which, when executed by a processor, implement the method described in any one of claims 1 to 11.

15. A computer program product, comprising a computer program or executable instructions, characterized in that, When the computer program or executable instructions are executed by a processor, they implement the method of any one of claims 1 to 11.