CN113590365A - Cross-process communication method and Binder driver - Google Patents
Cross-process communication method and Binder driver Download PDFInfo
- Publication number
- CN113590365A CN113590365A CN202111168280.3A CN202111168280A CN113590365A CN 113590365 A CN113590365 A CN 113590365A CN 202111168280 A CN202111168280 A CN 202111168280A CN 113590365 A CN113590365 A CN 113590365A
- Authority
- CN
- China
- Prior art keywords
- binder
- service manager
- client process
- name space
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/541—Client-server
Abstract
The application provides a cross-process communication method, a Binder driver, electronic equipment and a storage medium, wherein the method comprises the following steps: when receiving a service acquisition request sent by a client process, the Binder driver sends the service acquisition request to a target service manager, so that the target service manager determines a Binder reference based on the service acquisition request and sends the Binder reference to the Binder driver; the Binder driver sends the Binder reference to the client process so that the client process can acquire the service provided by the server process through the Binder reference; the target service manager is determined according to the following method: after the client process opens the Binder driver, the Binder driver determines a target service manager by inquiring the corresponding relation between the preset name space and the service manager based on the name space where the client process is located, wherein the number of the name spaces in the corresponding relation is at least two, and cross-process communication under a multi-container environment can be realized.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a cross-process communication method, a Binder driver, electronic equipment and a storage medium.
Background
With the increasing application of Android (Android) devices to various industries, people have an increasing demand for Android systems, including a multi-container operation of an Android system, that is, a plurality of Android containers are operated in one Android system.
The Android system is based on a Linux operating system, but the inter-process communication (IPC) technology of the Android system does not adopt the original Linux mode, but adopts a Binder mechanism, a virtual character device driver/dev/Binder is created in a Linux kernel, the init, open, mmap, ioctl and other interfaces are provided for the outside, user-mode processes access the kernel mode through the interfaces, and other user-mode processes are accessed through the Binder driver of the kernel, so that cross-process communication is realized.
But the Binder driver does not support cross-process communication in a multi-container environment. Specifically, for implementation in the Android system kernel, there is only one binder _ context _ mgr _ node (the binder _ context _ mgr _ node is used to store the binder entity corresponding to the service manager ServiceManager). When a plurality of Android containers run, when each container initializes the service manager, the service manager registers as a binder _ context _ mgr _ node in the binder driver, which may cause execution failure and thus a system running error.
Therefore, how to provide a scheme to implement cross-process communication in a multi-container environment is a technical problem to be solved urgently.
Disclosure of Invention
To solve the technical problems in the prior art, embodiments of the present application provide a cross-process communication method, a Binder driver, an electronic device, and a storage medium.
In a first aspect, an embodiment of the present application provides a cross-process communication method, including:
when receiving a service acquisition request sent by a client process, a Binder driver sends the service acquisition request to a target service manager, so that the target service manager determines a Binder reference based on the service acquisition request and sends the Binder reference to the Binder driver;
the Binder driver sends the Binder reference to the client process so that the client process can obtain the service provided by the server process through the Binder reference;
wherein the target service manager is determined according to the following method:
after the Binder driver is opened by the client process, the Binder driver determines the target service manager by inquiring a preset name space and the corresponding relation of the service managers based on the name space where the client process is located, wherein the number of the name spaces in the corresponding relation is at least two.
In a second aspect, an embodiment of the present application further provides a Binder drive, including:
the system comprises a first sending unit, a second sending unit and a third sending unit, wherein the first sending unit is used for sending a service acquisition request to a target service manager when receiving the service acquisition request sent by a client process, so that the target service manager determines a Binder reference based on the service acquisition request and feeds back the Binder reference;
a second sending unit, configured to send the Binder reference to the client process, so that the client process obtains, through the Binder reference, a service provided by a server process;
wherein the target service manager is determined by a query unit;
the query unit is configured to:
after the Binder driver is opened by the client process, determining the target service manager by inquiring a preset name space and the corresponding relation of the service managers based on the name space where the client process is located, wherein the number of the name spaces in the corresponding relation is at least two.
In a third aspect, this application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the cross-process communication method according to the first aspect.
In a fourth aspect, an embodiment of the present application further provides an electronic device, including: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the electronic device is running, the processor executing the machine-readable instructions to perform the steps of the cross-process communication method according to the first aspect.
To sum up, according to the cross-process communication method, the Binder driver, the electronic device, and the storage medium provided in the embodiment of the present application, first, when receiving a service acquisition request sent by a client process, the Binder driver sends the service acquisition request to a target service manager, so that the target service manager determines a Binder reference based on the service acquisition request, and sends the Binder reference to the Binder driver; then, the Binder driver sends the Binder reference to the client process, so that the client process obtains the service provided by the server process through the Binder reference, and in one aspect of the whole scheme, based on the preset corresponding relationship between the namespace and the service manager, the Binder driver can support distinguishing the service manager by the dimension of the namespace, so that the service managers of the containers are isolated from each other in the Binder driver: the target service manager is a service manager corresponding to a namespace in which the client process is located, namely, a service manager corresponding to a container to which the client process belongs in a multi-container environment, so that a correct service manager can be determined from the service managers corresponding to a plurality of containers in the process of cross-process communication in the multi-container environment, and cross-process communication in the multi-container environment is realized based on the service manager; on the other hand, the target service manager is predetermined by the Binder driver, so that the target service manager can be directly found when the client process accesses the service provided by the server process each time, and the efficiency of cross-process communication in a multi-container environment can be improved.
Drawings
Fig. 1 is a schematic flowchart of a cross-process communication method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a Binder drive according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it should be understood that the drawings in the present application are for illustrative and descriptive purposes only and are not used to limit the scope of protection of the present application. Additionally, it should be understood that the schematic drawings are not necessarily drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be performed out of order, and steps without logical context may be performed in reverse order or simultaneously. One skilled in the art, under the guidance of this application, may add one or more other operations to, or remove one or more operations from, the flowchart.
In addition, the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that in the embodiments of the present application, the term "comprising" is used to indicate the presence of the features stated hereinafter, but does not exclude the addition of further features.
Referring to fig. 1, a schematic flow chart of a cross-process communication method provided in an embodiment of the present application specifically includes:
s10, when receiving a service acquisition request sent by a client process, the Binder driver sends the service acquisition request to a target service manager, so that the target service manager determines a Binder reference based on the service acquisition request and sends the Binder reference to the Binder driver;
s11, the Binder driver sends the Binder reference to the client process, so that the client process obtains the service provided by the server process through the Binder reference;
wherein the target service manager is determined according to the following method:
s12, after the Binder driver is opened by the client process, the Binder driver determines the target service manager by inquiring the corresponding relation between the preset name space and the service manager based on the name space where the client process is located, wherein the number of the name spaces in the corresponding relation is at least two.
The implementation basis of the embodiment is a name space mechanism of a Linux system kernel, which is a mechanism for isolating resources in the kernel. Each user process runs in a certain namespace and in the kernel it can be distinguished by the namespace to which container the process belongs. It should be noted that the preset corresponding relationship between the name space and the service manager stores the name space and the service manager corresponding to the name space. The service managers corresponding to the namespaces can be recorded through the corresponding relation, and the condition that the service managers are registered as binder _ context _ mgr _ node in a binder driver when the service managers are initialized in the prior art is avoided, so that the problem that a plurality of Android containers in the prior art can run is solved.
According to the cross-process communication method provided by the embodiment of the application, firstly, when a Binder driver receives a service acquisition request sent by a client process, the Binder driver sends the service acquisition request to a target service manager, so that the target service manager determines a Binder reference based on the service acquisition request and sends the Binder reference to the Binder driver; then, the Binder driver sends the Binder reference to the client process, so that the client process obtains the service provided by the server process through the Binder reference, and in one aspect of the whole scheme, based on the preset corresponding relationship between the namespace and the service manager, the Binder driver can support distinguishing the service manager by the dimension of the namespace, so that the service managers of the containers are isolated from each other in the Binder driver: the target service manager is a service manager corresponding to a namespace in which the client process is located, namely, a service manager corresponding to a container to which the client process belongs in a multi-container environment, so that a correct service manager can be determined from the service managers corresponding to a plurality of containers in the process of cross-process communication in the multi-container environment, and cross-process communication in the multi-container environment is realized based on the service manager; on the other hand, the target service manager is predetermined by the Binder driver, so that the target service manager can be directly found when the client process accesses the service provided by the server process each time, and the efficiency of cross-process communication in a multi-container environment can be improved.
On the basis of the foregoing method embodiment, the method may further include:
if the target service manager is not determined by inquiring a preset name space and the corresponding relation of the service managers based on the name space where the client process is located, the Binder driver determines the service manager corresponding to the name space where the client process is located, and generates the corresponding relation between the name space where the client process is located and the service manager corresponding to the name space where the client process is located.
In this embodiment, it should be noted that, if the Binder driver does not determine the target service manager by querying a preset name space and a corresponding relationship between the preset name space and the service manager based on the name space where the client process is located, it is necessary to determine the service manager corresponding to the name space where the client process is located, and generate a corresponding relationship between the name space where the client process is located and the service manager corresponding to the name space where the client process is located. Then, the client process can determine a target service manager based on the corresponding relation, and then access the service provided by the server process based on the target service manager.
On the basis of the embodiment of the method, a service manager corresponding to a namespace in which the client process is located is taken as a first service manager;
wherein determining the first service manager may include:
the Binder driver creates a Binder entity of the first service manager;
the corresponding relationship between the namespace in which the client process is located and the service manager corresponding to the namespace in which the client process is located may include: the identification of the namespace in which the client process is located and the Binder entity of the first service manager.
After android8.0, in order to facilitate transplanting, upgrading and improving system stability, the Binder equipment is expanded into three parts: the symbol/dev/binder,/dev/hwbinder and/dev/vndbinder. And correspondingly, a plurality of Binder entities are arranged in the kernel, wherein each Binder device corresponds to one Binder entity. This mechanism also does not support multiple containers.
To solve the above problem, on the basis of the foregoing method embodiment, the determining, by the Binder driver, the target service manager by querying a preset namespace and a corresponding relationship between service managers based on a namespace in which the client process is located may include:
and the Binder driver determines the target service manager by inquiring the corresponding relation among the preset Binder driver, the name space and the service manager based on the Binder driver and the name space where the client process is located, wherein the number of the Binder drivers in the corresponding relation is at least two.
In this embodiment, it can be understood that a triplet of the Binder driver, the namespace, and the service manager may be stored in a preset corresponding relationship of the Binder driver, the namespace, and the service manager. The triplet may include the Binder driven identity, the identity of the namespace, and the Binder entity of the service manager. When the client process wants to acquire the service provided by the server process, a service acquisition request can be sent to the Binder driver. After receiving a service acquisition request, the Binder driver queries the corresponding relation among the preset Binder driver, the name space and the service manager, determines the service manager corresponding to the name space to which the Binder driver and the client process belong as a target service manager, and sends the service acquisition request to the target service manager. After receiving the service acquisition request, the target service manager can determine a Binder reference of a Binder object of the server process, send the Binder reference to the Binder driver, and send the Binder reference to the client process by the Binder driver. And then the client process can utilize the Binder reference to communicate with the server process to obtain the service provided by the server process.
And if the preset corresponding relation among the Binder drive, the namespace and the service manager is inquired, and the target service manager is not determined, determining the service manager (namely a first service manager) corresponding to the Binder drive and the namespace in which the client process is located, and generating the corresponding relation among the Binder drive, the namespace in which the client process is located and the first service manager. Specifically, the first service manager may be determined by creating a Binder entity of the first service manager. And then, a target service manager can be determined through the corresponding relation, and then the communication between the client process and the server process is realized through the target service manager.
In addition, the at least two Binder drives may include: the symbol/dev/binder,/dev/hwbinder and/dev/vndbinder.
In this embodiment, the preset mapping relationship between the namespace and the service manager is expanded to the preset mapping relationship between the Binder driver, the namespace, and the service manager, so that the service manager of the Binder driver and the namespace dimension can be recorded, and then the cross-process communication isolation scheme of the Binder driver and the namespace dimension (i.e., in a multi-device multi-container scenario) is realized through the service manager of the Binder driver and the namespace dimension.
Referring to fig. 2, a schematic structural diagram of a Binder drive provided in an embodiment of the present application is shown, where the Binder drive specifically includes:
a first sending unit 20, configured to send a service acquisition request to a target service manager when receiving the service acquisition request sent by a client process, so that the target service manager determines a Binder reference based on the service acquisition request and feeds back the Binder reference;
a second sending unit 21, configured to send the Binder reference to the client process, so that the client process obtains, through the Binder reference, a service provided by a server process;
wherein the target service manager is determined by the querying element 22;
the querying unit 22 is configured to:
after the Binder driver is opened by the client process, determining the target service manager by inquiring a preset name space and the corresponding relation of the service managers based on the name space where the client process is located, wherein the number of the name spaces in the corresponding relation is at least two.
In the Binder driver provided in the embodiment of the present application, first, when receiving a service acquisition request sent by a client process, a first sending unit 20 sends the service acquisition request to a target service manager, so that the target service manager determines a Binder reference based on the service acquisition request and feeds back the Binder reference; then, the Binder reference is sent to the client process by means of the second sending unit 21, so that the client process obtains the service provided by the server process through the Binder reference, in the whole scheme, on one hand, based on the preset namespace and the corresponding relationship of the service managers, the Binder driver can support to distinguish the service managers in the dimension of the namespace, so that the service managers of the containers are isolated from each other in the Binder driver: the query unit 22 determines the process of the target service manager, and the target service manager is a service manager corresponding to a namespace where the client process is located, that is, a service manager corresponding to a container to which the client process belongs in a multi-container environment, so that in the process of cross-process communication in the multi-container environment, a correct service manager can be determined from the service managers corresponding to multiple containers, and cross-process communication in the multi-container environment is realized based on the service manager; on the other hand, the target service manager is predetermined by the Binder driver, so that the target service manager can be directly found when the client process accesses the service provided by the server process each time, and the efficiency of cross-process communication in a multi-container environment can be improved.
On the basis of the foregoing Binder driving embodiment, the Binder driving may further include:
and the generating unit is used for determining the service manager corresponding to the name space of the client process and generating the corresponding relation between the name space of the client process and the service manager corresponding to the name space of the client process if the target service manager is not determined by inquiring the preset name space and the corresponding relation between the service managers based on the name space of the client process.
On the basis of the Binder driving embodiment, recording a service manager corresponding to a namespace in which the client process is located as a first service manager;
the generating unit is configured to:
creating a Binder entity of the first service manager;
the corresponding relationship between the namespace in which the client process is located and the service manager corresponding to the namespace in which the client process is located includes: the identification of the namespace in which the client process is located and the Binder entity of the first service manager.
On the basis of the foregoing Binder driving embodiment, the query unit may be configured to:
and determining the target service manager by inquiring the preset corresponding relation among the Binder driver, the name space and the service manager based on the Binder driver and the name space where the client process is located, wherein the number of the Binder drivers in the corresponding relation is at least two.
The implementation process of the Binder driver provided in the embodiment of the present application is the same as that of the cross-process communication method provided in the embodiment of the present application, and the achieved effect is also the same as that of the cross-process communication method provided in the embodiment of the present application, and details are not described here.
As shown in fig. 3, an electronic device provided in an embodiment of the present application includes: a processor 30, a memory 31 and a bus 32, wherein the memory 31 stores machine-readable instructions executable by the processor 30, when the electronic device is operated, the processor 30 communicates with the memory 31 via the bus 32, and the processor 30 executes the machine-readable instructions to perform the steps of the cross-process communication method as described above.
Specifically, the memory 31 and the processor 30 can be general-purpose memories and processors, which are not limited in particular, and the processor 30 can execute the cross-process communication method when executing the computer program stored in the memory 31.
Corresponding to the cross-process communication method, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the computer program is executed by a processor to perform the steps of the cross-process communication method.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system and the apparatus described above may refer to corresponding processes in the method embodiments, and are not described in detail in this application. In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. The above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and there may be other divisions in actual implementation, and for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or modules through some communication interfaces, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method of cross-process communication, comprising:
when receiving a service acquisition request sent by a client process, a Binder driver sends the service acquisition request to a target service manager, so that the target service manager determines a Binder reference based on the service acquisition request and sends the Binder reference to the Binder driver;
the Binder driver sends the Binder reference to the client process so that the client process can obtain the service provided by the server process through the Binder reference;
wherein the target service manager is determined according to the following method:
after the Binder driver is opened by the client process, the Binder driver determines the target service manager by inquiring a preset name space and the corresponding relation of the service managers based on the name space where the client process is located, wherein the number of the name spaces in the corresponding relation is at least two.
2. The method of claim 1, further comprising:
if the target service manager is not determined by inquiring a preset name space and the corresponding relation of the service managers based on the name space where the client process is located, the Binder driver determines the service manager corresponding to the name space where the client process is located, and generates the corresponding relation between the name space where the client process is located and the service manager corresponding to the name space where the client process is located.
3. The method of claim 2, wherein the service manager corresponding to the namespace in which the client process is located is the first service manager;
wherein determining the first service manager comprises:
the Binder driver creates a Binder entity of the first service manager;
the corresponding relationship between the namespace in which the client process is located and the service manager corresponding to the namespace in which the client process is located includes: the identification of the namespace in which the client process is located and the Binder entity of the first service manager.
4. The method of any one of claims 1 to 3, wherein the Binder driver determines the target service manager by querying a preset namespace and a service manager correspondence based on a namespace in which the client process is located, and comprises:
and the Binder driver determines the target service manager by inquiring the corresponding relation among the preset Binder driver, the name space and the service manager based on the Binder driver and the name space where the client process is located, wherein the number of the Binder drivers in the corresponding relation is at least two.
5. A Binder drive, comprising:
the system comprises a first sending unit, a second sending unit and a third sending unit, wherein the first sending unit is used for sending a service acquisition request to a target service manager when receiving the service acquisition request sent by a client process, so that the target service manager determines a Binder reference based on the service acquisition request and feeds back the Binder reference;
a second sending unit, configured to send the Binder reference to the client process, so that the client process obtains, through the Binder reference, a service provided by a server process;
wherein the target service manager is determined by a query unit;
the query unit is configured to:
after the Binder driver is opened by the client process, determining the target service manager by inquiring a preset name space and the corresponding relation of the service managers based on the name space where the client process is located, wherein the number of the name spaces in the corresponding relation is at least two.
6. The Binder drive of claim 5 further comprising:
and the generating unit is used for determining the service manager corresponding to the name space of the client process and generating the corresponding relation between the name space of the client process and the service manager corresponding to the name space of the client process if the target service manager is not determined by inquiring the preset name space and the corresponding relation between the service managers based on the name space of the client process.
7. The Binder driver as claimed in claim 6, wherein the service manager corresponding to the namespace where the client process is located is taken as a first service manager;
the generating unit is configured to:
creating a Binder entity of the first service manager;
the corresponding relationship between the namespace in which the client process is located and the service manager corresponding to the namespace in which the client process is located includes: the identification of the namespace in which the client process is located and the Binder entity of the first service manager.
8. The Binder drive according to any one of claims 5 to 7 wherein the query unit is configured to:
and determining the target service manager by inquiring the preset corresponding relation among the Binder driver, the name space and the service manager based on the Binder driver and the name space where the client process is located, wherein the number of the Binder drivers in the corresponding relation is at least two.
9. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, performs the steps of the cross-process communication method according to any one of claims 1 to 4.
10. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the electronic device is operating, the processor executing the machine-readable instructions to perform the steps of the cross-process communication method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111168280.3A CN113590365A (en) | 2021-10-08 | 2021-10-08 | Cross-process communication method and Binder driver |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111168280.3A CN113590365A (en) | 2021-10-08 | 2021-10-08 | Cross-process communication method and Binder driver |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113590365A true CN113590365A (en) | 2021-11-02 |
Family
ID=78242921
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111168280.3A Pending CN113590365A (en) | 2021-10-08 | 2021-10-08 | Cross-process communication method and Binder driver |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113590365A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114461157A (en) * | 2021-12-23 | 2022-05-10 | 天翼云科技有限公司 | IDV client multi-screen division and treatment method and system |
| CN114615546A (en) * | 2022-02-08 | 2022-06-10 | 武汉光庭信息技术股份有限公司 | Video playing method and device, electronic equipment and storage medium |
| CN116048744A (en) * | 2022-08-19 | 2023-05-02 | 荣耀终端有限公司 | Image acquisition method and related electronic equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107172197A (en) * | 2017-06-26 | 2017-09-15 | 努比亚技术有限公司 | A kind of method for processing business, system and equipment |
| CN111290827A (en) * | 2018-12-07 | 2020-06-16 | 华为技术有限公司 | Data processing method and device and server |
| CN112073448A (en) * | 2019-06-11 | 2020-12-11 | 成都鼎桥通信技术有限公司 | Service isolation method and device for dual-system terminal |
-
2021
- 2021-10-08 CN CN202111168280.3A patent/CN113590365A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107172197A (en) * | 2017-06-26 | 2017-09-15 | 努比亚技术有限公司 | A kind of method for processing business, system and equipment |
| CN111290827A (en) * | 2018-12-07 | 2020-06-16 | 华为技术有限公司 | Data processing method and device and server |
| CN112073448A (en) * | 2019-06-11 | 2020-12-11 | 成都鼎桥通信技术有限公司 | Service isolation method and device for dual-system terminal |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114461157A (en) * | 2021-12-23 | 2022-05-10 | 天翼云科技有限公司 | IDV client multi-screen division and treatment method and system |
| CN114461157B (en) * | 2021-12-23 | 2023-11-03 | 天翼云科技有限公司 | IDV client multi-screen divide-and-conquer method and system |
| CN114615546A (en) * | 2022-02-08 | 2022-06-10 | 武汉光庭信息技术股份有限公司 | Video playing method and device, electronic equipment and storage medium |
| CN114615546B (en) * | 2022-02-08 | 2024-04-12 | 武汉光庭信息技术股份有限公司 | Video playing method and device, electronic equipment and storage medium |
| CN116048744A (en) * | 2022-08-19 | 2023-05-02 | 荣耀终端有限公司 | Image acquisition method and related electronic equipment |
| CN116048744B (en) * | 2022-08-19 | 2023-09-12 | 荣耀终端有限公司 | Image acquisition method and related electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113590365A (en) | Cross-process communication method and Binder driver | |
| CN101206581B (en) | System and method for guiding using external memory device | |
| US9223975B2 (en) | Data identification system | |
| US8970350B2 (en) | Maintaining RFID information for virtual machines | |
| EP3432549A1 (en) | Method and apparatus for processing user requests | |
| CN102799464A (en) | Virtual machine creation method, virtual machine creation system, virtual machine resetting method and virtual machine resetting system | |
| CN106886429B (en) | Method for loading driver and server | |
| CN109445902B (en) | Data operation method and system | |
| US10282120B2 (en) | Method, apparatus and system for inserting disk | |
| US10229010B2 (en) | Methods for preserving state across a failure and devices thereof | |
| CN113835644B (en) | Complete machine migration method, device, equipment and storage medium | |
| CN109240800B (en) | Hypervisor-based multi-system shared memory management method | |
| CN107193491B (en) | Virtual environment disk operation method and device | |
| US11347541B2 (en) | Methods and apparatus for virtual machine rebalancing | |
| CN108667750B (en) | Virtual resource management method and device | |
| CN110515540B (en) | Method and device for topology of hard disk | |
| CN111177053B (en) | Data communication method, device and system and computer readable storage medium | |
| CN111845143B (en) | Method and device for printing by handheld device | |
| US11226775B2 (en) | Extracting drive letters for partitions in an offline virtual disk | |
| JP2003067206A (en) | Method of dynamically assigning device in lpar system | |
| US11829813B2 (en) | Recognizing and discovering new services provided by a cloud service provider | |
| CN116737513B (en) | Computer hardware information acquisition method, system and computer equipment | |
| US11687431B2 (en) | Determining changes to components of a computing device prior to booting to a primary environment of the computing device | |
| US20230333875A1 (en) | Recognizing and discovering new services provided by a cloud service provider | |
| CN116244038A (en) | Virtual machine eBPF program management method, system, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211102 |
|
| RJ01 | Rejection of invention patent application after publication |