CN103488478A - Device management framework based on android platform - Google Patents
Device management framework based on android platform Download PDFInfo
- Publication number
- CN103488478A CN103488478A CN201310394192.4A CN201310394192A CN103488478A CN 103488478 A CN103488478 A CN 103488478A CN 201310394192 A CN201310394192 A CN 201310394192A CN 103488478 A CN103488478 A CN 103488478A
- Authority
- CN
- China
- Prior art keywords
- interface
- dynamic base
- management
- function
- equipment
- 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
- 238000000034 method Methods 0.000 claims abstract description 16
- 230000008569 process Effects 0.000 claims abstract description 15
- 238000004458 analytical method Methods 0.000 claims abstract description 7
- 230000004044 response Effects 0.000 claims description 21
- 238000005538 encapsulation Methods 0.000 claims description 6
- 230000008859 change Effects 0.000 claims description 3
- 238000013507 mapping Methods 0.000 claims description 3
- 238000012544 monitoring process Methods 0.000 claims description 3
- 230000002452 interceptive effect Effects 0.000 abstract 1
- 238000004806 packaging method and process Methods 0.000 abstract 1
- 230000006870 function Effects 0.000 description 61
- 238000007726 management method Methods 0.000 description 57
- 238000011161 development Methods 0.000 description 6
- 239000011230 binding agent Substances 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 238000013497 data interchange Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a device management framework based on an android platform. The device management framework comprises an application program layer, a management service module, a management daemon process module, a function dynamic depot layer and an inner core drive layer, wherein the application program layer is used for realizing calling an interface of the device management framework; the management service module is used for converting the function interface into a command call, and transmitting a command by using a Local Socket client end of a Socket in an Android; the management daemon process module receives the command by using a Local Socket service end of the Socket in the Android, analyzes the command, and calls the function dynamic depot layer according to the analysis result; the function dynamic depot layer is used for packaging an interface which is interactive with the inner core drive layer; the inner core drive layer is used for providing a standard operation interface of a Linux operating system to be called by the function dynamic depot layer, and operating each hardware device.
Description
Technical field
The present invention is specifically related to a kind of device management framework based on the android platform.
Background technology
The Android platform is the general-purpose platform of a standard, and the equipment do not had increased the primary system of many Android newly in the multimedia vehicle mounted terminal project of Telematics in, as DVD, GPIO, audio frequency controller equipment etc.For the control and management of these equipment, adopt at present JNI(Java Native Interface, call Java this locality) mode controlled.
Residing code hierarchical position is as shown in Figure 1 in the Android platform for JNI, on the Android platform, JNI makes at the Java of Java Virtual Machine internal operation code and can carry out alternately with the application program of writing with other programming languages such as C/C++ and storehouse, thus by the Java code with together with other programming language codes such as C/C++ are closely connected.The shortcoming of using the JNI mode to carry out equipment control is:
Use the JNI mode to carry out the code that program development need to realize Java, JNI, tri-levels of C/C++ simultaneously, the development amount is large, and development difficulty is also larger; Application code is if be transplanted on other platform, and the C/C++ code need to be write again, and the workload of transplanting is larger, portable poor; From the logical organization aspect, a JNI dynamic base is only suitable for managing an equipment, along with the increase of equipment, is difficult to, by the JNI mode, these equipment are carried out to unified management; In use exist a plurality of application programs to access the possibility of an equipment simultaneously, cause device access uncontrollable, system stability is poor.
In addition, Java Virtual Machine makes the Java code can not cause program crashing, abuse data etc. for the Java code provides perfect security mechanism, once and used JNI, this security mechanism is just helpless.
Summary of the invention
Technical matters to be solved by this invention is to provide a kind of device management framework based on the android platform, has solved the problem of the primary equipment control confusion of numerous non-Android, has greatly improved the stability of equipment; The hidden danger such as safety of having avoided a plurality of application programs simultaneously the underlying device direct control to be existed, the security that has greatly improved equipment.
The present invention solves the problems of the technologies described above by the following technical programs: a kind of device management framework based on the android platform comprises the application layer, management services module, management finger daemon module, function dynamic base layer and the kernel-driven layer that arrange from top to bottom;
Described application layer: for realizing calling the interface of described device management framework; By binding interface binding management service module, call the functional interface that in management services module, the AIDL interface document provides simultaneously;
Described management services module: be used to each equipment to create the AIDL interface document; Change into command calls for the functional interface that the AIDL interface document is provided simultaneously, and transmit described order by Socket socket LocalSocket client in Android;
Described management finger daemon module: receive described order by Socket socket LocalSocket server end in Android, and resolve command, according to command analysis call by result function dynamic base layer;
Described function dynamic base layer: for encapsulation and kernel-driven layer, carry out mutual interface;
Described kernel-driven layer: call to function dynamic base layer for the standard operation interface that (SuSE) Linux OS is provided, can operate each equipment simultaneously.
Further, the format structure of described order is:
Device name@functional interface title # parameter 1# parameter 2#...# parameter N; N is greater than 2 integer.
Further, described function dynamic base layer comprises a plurality of function dynamic base, and described kernel-driven layer comprises a plurality of kernel-driven modules, and every described equipment is all to having a function dynamic base and a kernel-driven module; Be that each function dynamic base is corresponding one by one with each kernel-driven module.
Further, described management finger daemon module is as follows according to the specific implementation process of command analysis call by result function dynamic base layer:
Management finger daemon module is obtained device name, functional interface title and parameter from the format structure of described order, when calling this equipment for the first time, first value-added tax function dynamic base layer, and the initialization interface of this equipment in calling function dynamic base layer, carry out device initialize; When non-while calling for the first time this equipment, the direct command process interface of this equipment in calling function dynamic base layer.
Further, described function dynamic base layer encapsulation is as follows with the specific implementation process that the kernel-driven layer carries out mutual interface:
The function dynamic base of described equipment is obtained described functional interface title and parameter from management finger daemon module, while locating function interface name and functional interface function pointer mapping table from the function dynamic base of this equipment, according to described functional interface title, find the functional interface function pointer and call corresponding functional interface function, can realize calling the standard operation interface of (SuSE) Linux OS according to described functional interface function.
Further, when the functional interface called when described application layer need to obtain response data, the kernel-driven module of relevant device is returned to the function dynamic base of response data to this equipment, the function dynamic base of this equipment reports management finger daemon module by described response data with " functional interface title+' #'+ response data " form, management finger daemon module is uploaded to described management services module, application layer after response data being packaged into to " device name+'@'+functional interface title+' #'+ response data " form successively.
Further, the standard operation interface of described (SuSE) Linux OS is open interface, read interface, write interface, ioctl interface or close interface.
Further, described management services module also sends heartbeat packet to described management finger daemon module, for monitoring and renewal management services module connection.
Beneficial effect of the present invention is:
1, can well the primary equipment of non-Android in the Android system be unified to control and management;
2, can support well bottom (being each equipment) to upper strata the data interchange of (being application layer);
3, for application development provides unified interface, reduce the difficulty of application development, improve code reuse and the portability of application program;
4, the device management framework logical organization is clear, has solved the problem of the primary equipment control confusion of numerous non-Android, has greatly improved the stability of equipment;
5, by the unified control and management to equipment, the hidden danger such as safety of having avoided a plurality of application programs simultaneously the underlying device direct control to be existed, the security that has greatly improved equipment.
The accompanying drawing explanation
The invention will be further described in conjunction with the embodiments with reference to the accompanying drawings.
The theory diagram that Fig. 1 is the existing device management method based on the Android platform.
Fig. 2 is the block diagram that the present invention is based on the device management framework of android platform.
Fig. 3 is the process flow diagram that the present invention is based on the device management framework of android platform.
Embodiment
Refer to Fig. 2-3, a kind of device management framework based on the android platform, comprise the application layer, management services module, management finger daemon module, function dynamic base layer and the kernel-driven layer that arrange from top to bottom; Described function dynamic base layer comprises a plurality of function dynamic base, and described kernel-driven layer comprises a plurality of kernel-driven modules, and each equipment is all to having a function dynamic base and a kernel-driven module; Be that each function dynamic base is corresponding one by one with each kernel-driven module.Such as: the function dynamic base comprises: DVD function dynamic base, GPIO function dynamic base, AUDIO function dynamic base etc.; The kernel-driven module comprises: UART kernel-driven module, GPIO kernel-driven module, audio frequency controller device core driver module etc.; And described DVD function dynamic base is corresponding with UART kernel-driven module, described GPIO function dynamic base is corresponding with GPIO kernel-driven module, and described AUDIO function dynamic base is corresponding with audio frequency controller device core driver module.
Described application layer: for realizing the interface of the described device management framework of call operation, the call operation of device management framework is initiated by application layer; By binding interface binding management service module, call the functional interface that in management services module, the AIDL interface document provides simultaneously; Be that application layer passes through bindService interface binding management service module, can obtain the Binder service (Binder is a kind of inter-process communication mechanisms that the Android system provides) of relevant device in management services module after binding, can call the AIDL(Android Interface Definition Language that Binder provides after obtaining the Binder service, i.e. the Android interface description language) interface carries out required function.
Described management services module: be arranged in the Java ccf layer of Android system, be used to each equipment to create the AIDL interface document; The time change into command calls for functional interface that the AIDL interface document is provided, and transmit described order by Android LocalSocket client (being the Socket socket); Management services module also can send heartbeat packet to management finger daemon module, for monitoring and renewal management services module connection.
Described AIDL interface document is interface statement file, need management services module to complete the code realization of these AIDL interface documents, the functional interface that management services module is called application layer generates command format and also to management finger daemon module, sends this order.
The format structure of described order is:
Device name@functional interface title # parameter 1# parameter 2#...# parameter N; As: DeviceName@Function#parameter1#parameter2#...#parameterN, wherein, DeviceName indication equipment title, Function presentation function interface name, parameter1#parameter2#...#parameterN means Transfer Parameters, between parameter, use symbol ' #' separates.For example order " GPIO@GPIO_UP #fmpowon ", wherein, " GPIO " indication equipment title, " GPIO_UP " presentation function interface name, the parameter of " fmpowon " presentation function interface.
Described management finger daemon module: be arranged in the HAL layer (being hardware abstraction layer) of Android system, it receives described order by Android LocalSocket server end, and resolve command, according to command analysis call by result function dynamic base layer.
Described management finger daemon module is as follows according to command analysis call by result function dynamic base layer specific implementation process:
Management finger daemon module is obtained device name, functional interface title and parameter from the format structure of described order, when calling this equipment for the first time, first value-added tax function dynamic base layer, and in calling function dynamic base layer, the described XXX of initialization interface XXX_init(of this equipment resolves the device name obtained from order), carry out device initialize; When non-while calling for the first time this equipment, the direct command process interface XXX_processCmd of this equipment in calling function dynamic base layer.For example:
When the device name of obtaining is " GPIO " equipment, if call for the first time " GPIO " equipment, first value-added tax function dynamic base layer, and " GPIO " device initialize interface GPIO_init in calling function dynamic base layer, carry out device initialize, if not call for the first time " GPIO " equipment, the direct command process interface GPIO_processCmd of " GPIO " equipment in calling function dynamic base layer.
Described function dynamic base layer: for encapsulation and kernel-driven layer, carry out mutual interface, in the XXX_processCmd function, realize, described XXX_processCmd function is for realizing command process, and provides the command process calling interface for described management finger daemon module; The specific implementation process is as follows:
The function dynamic base of described equipment is obtained described functional interface title and parameter from management finger daemon module, while locating function interface name and functional interface function pointer mapping table from the function dynamic base of this equipment, according to described functional interface title, find the functional interface function pointer and call corresponding functional interface function, the standard operation interface of (SuSE) Linux OS can be realized calling according to described functional interface function, thereby described kernel-driven layer can be called.The standard operation interface of described (SuSE) Linux OS can be open interface, read interface, write interface, ioctl interface or close interface.
Described kernel-driven layer: call to function dynamic base layer for the standard operation interface that (SuSE) Linux OS is provided, can operate each equipment (being hardware) simultaneously; Relevant device is accepted operational order, carries out function, and returns to where necessary response data.
When the functional interface called when described application layer need to obtain response data, the kernel-driven module of relevant device is returned to the function dynamic base of response data to this equipment, the function dynamic base of this equipment reports management finger daemon module by described response data with " functional interface title+' #'+ response data " form, management finger daemon module is uploaded to described management services module, application layer after response data being packaged into to " device name+'@'+functional interface title+' #'+ response data " form successively.
For example: the response data encapsulation format is " AUDIO@GetMainVolume#80 ", and " AUDIO " means the audio frequency apparatus title, " GetMainVolume " presentation function interface name, and " 80 " mean that response data is volume value.
The present invention has the following advantages:
1, can well the primary equipment of non-Android in the Android system be unified to control and management;
2, can support well bottom (being each equipment) to upper strata the data interchange of (being application layer);
3,, for each application development provides unified interface (being the AIDL interface document in described management services module), reduce the difficulty of application development; Due to the unified interface of each application call, this has improved the rate of code reuse of application program, and has the portability between the Android different editions;
4, the device management framework logical organization is clear, has solved the problem of the primary equipment control confusion of numerous non-Android, has greatly improved the stability of equipment;
5, by the unified control and management to equipment, the hidden danger such as safety of having avoided a plurality of application programs simultaneously the underlying device direct control to be existed, the security that has greatly improved equipment;
6, device management framework employing standard and architecture Design flexibly, be highly susceptible to subsequent expansion and cutting peripherals (being the primary equipment of non-Android), is easy to popularization and multiplexing between the disparity items of Android platform simultaneously.
Claims (8)
1. the device management framework based on the android platform, is characterized in that: comprise the application layer, management services module, management finger daemon module, function dynamic base layer and the kernel-driven layer that arrange from top to bottom;
Described application layer: for realizing calling the interface of described device management framework; By binding interface binding management service module, call the functional interface that in management services module, the AIDL interface document provides simultaneously;
Described management services module: be used to each equipment to create the AIDL interface document; Change into command calls for the functional interface that the AIDL interface document is provided simultaneously, and transmit described order by Socket socket LocalSocket client in Android;
Described management finger daemon module: receive described order by Socket socket LocalSocket service end in Android, and resolve command, according to command analysis call by result function dynamic base layer;
Described function dynamic base layer: for encapsulation and kernel-driven layer, carry out mutual interface;
Described kernel-driven layer: call to function dynamic base layer for the standard operation interface that (SuSE) Linux OS is provided, can operate each equipment simultaneously.
2. the device management framework based on the android platform as claimed in claim 1 is characterized in that:
The format structure of described order is:
Device name@functional interface title # parameter 1# parameter 2#...# parameter N; N is greater than 2 integer.
3. the device management framework based on the android platform as claimed in claim 2, it is characterized in that: described function dynamic base layer comprises a plurality of function dynamic base, described kernel-driven layer comprises a plurality of kernel-driven modules, and every described equipment is all to having a function dynamic base and a kernel-driven module; Be that each function dynamic base is corresponding one by one with each kernel-driven module.
4. the device management framework based on the android platform as claimed in claim 3, it is characterized in that: described management finger daemon module is as follows according to the specific implementation process of command analysis call by result function dynamic base layer:
Management finger daemon module is obtained device name, functional interface title and parameter from the format structure of described order, when calling this equipment for the first time, first value-added tax function dynamic base layer, and the initialization interface of this equipment in calling function dynamic base layer, carry out device initialize; When non-while calling for the first time this equipment, the direct command process interface of this equipment in calling function dynamic base layer.
5. the device management framework based on the android platform as claimed in claim 4 is characterized in that: described function dynamic base layer encapsulation is as follows with the specific implementation process that the kernel-driven layer carries out mutual interface:
The function dynamic base of described equipment is obtained described functional interface title and parameter from management finger daemon module, while locating function interface name and functional interface function pointer mapping table from the function dynamic base of this equipment, according to described functional interface title, find the functional interface function pointer and call corresponding functional interface function, can realize calling the standard operation interface of (SuSE) Linux OS according to described functional interface function.
6. the device management framework based on the android platform as claimed in claim 5 is characterized in that:
When the functional interface called when described application layer need to obtain response data, the kernel-driven module of relevant device is returned to the function dynamic base of response data to this equipment, the function dynamic base of this equipment reports management finger daemon module by described response data with " functional interface title+' #'+ response data " form, management finger daemon module is uploaded to described management services module, application layer after response data being packaged into to " device name+'@'+functional interface title+' #'+ response data " form successively.
7. the device management framework based on the android platform as claimed in claim 1, it is characterized in that: the standard operation interface of described (SuSE) Linux OS is open interface, read interface, write interface, ioctl interface or close interface.
8. the device management framework based on the android platform as claimed in claim 1 is characterized in that:
Described management services module also sends heartbeat packet to described management finger daemon module, for monitoring and renewal management services module connection.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310394192.4A CN103488478A (en) | 2013-09-03 | 2013-09-03 | Device management framework based on android platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310394192.4A CN103488478A (en) | 2013-09-03 | 2013-09-03 | Device management framework based on android platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103488478A true CN103488478A (en) | 2014-01-01 |
Family
ID=49828735
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310394192.4A Pending CN103488478A (en) | 2013-09-03 | 2013-09-03 | Device management framework based on android platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103488478A (en) |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902389A (en) * | 2014-03-06 | 2014-07-02 | 厦门雅迅网络股份有限公司 | Equipment management method supporting bidirectional communication based on android platform |
| CN104102540A (en) * | 2014-06-30 | 2014-10-15 | 上海卓悠网络科技有限公司 | Operation process management method and mobile terminal |
| CN104216709A (en) * | 2014-08-20 | 2014-12-17 | 深圳光启创新技术有限公司 | Method and module for directly controlling hardware equipment in operating system |
| CN104267956A (en) * | 2014-09-28 | 2015-01-07 | 深圳光启创新技术有限公司 | Method and module for controlling hardware device in operating system |
| CN104636128A (en) * | 2014-09-10 | 2015-05-20 | 深圳光启创新技术有限公司 | Method and module for controlling hardware equipment in operating system |
| CN104932869A (en) * | 2014-03-18 | 2015-09-23 | 苏州市伏泰信息科技有限公司 | Embedded software platform for intelligent vehicle terminal |
| CN105183455A (en) * | 2015-08-13 | 2015-12-23 | 深圳市广和通无线股份有限公司 | Method and system for integrating JT/T808 program on Android platform |
| WO2016026449A1 (en) * | 2014-08-20 | 2016-02-25 | 深圳光启智能光子技术有限公司 | Method and module in operating system for controlling hardware device |
| CN105472462A (en) * | 2015-11-12 | 2016-04-06 | Tcl王牌电器(惠州)有限公司 | Television function processing method and system |
| CN105955829A (en) * | 2016-04-20 | 2016-09-21 | 青岛海信宽带多媒体技术有限公司 | Order processing method, device and terminal |
| JP2017520856A (en) * | 2014-07-10 | 2017-07-27 | ハーマン インターナショナル インダストリーズ インコーポレイテッド | Operating system startup acceleration |
| JP2017521789A (en) * | 2014-07-10 | 2017-08-03 | ハーマン インターナショナル インダストリーズ インコーポレイテッド | Operating system startup acceleration |
| JP2017521785A (en) * | 2014-07-10 | 2017-08-03 | ハーマン インターナショナル インダストリーズ インコーポレイテッド | Operating system startup acceleration |
| CN107450926A (en) * | 2017-07-31 | 2017-12-08 | 郑州云海信息技术有限公司 | The hardware adaptor management method and device of a kind of storage device |
| CN105975249B (en) * | 2015-12-31 | 2018-12-11 | 小米科技有限责任公司 | Application executing method and device based on hardware chip |
| CN109164996A (en) * | 2018-08-10 | 2019-01-08 | 深圳市智微智能科技开发有限公司 | A kind of realization android is from principal point screen method and Related product |
| CN109189566A (en) * | 2018-08-10 | 2019-01-11 | 深圳市智微智能科技开发有限公司 | A kind of method and Related product for realizing the upper layer android driving IO |
| CN109388581A (en) * | 2018-10-08 | 2019-02-26 | 郑州云海信息技术有限公司 | A kind of Nonvolatile memory reservoir management method and device |
| CN109660661A (en) * | 2018-12-03 | 2019-04-19 | 北京云测信息技术有限公司 | Remote real machine screenshot method suitable for android9.0 system |
| CN110879659A (en) * | 2018-09-05 | 2020-03-13 | 北京九天微星科技发展有限公司 | Low-power consumption method realized based on equipment management framework in embedded real-time operating system (RT-Thread) |
| CN112363769A (en) * | 2020-11-18 | 2021-02-12 | 许昌许继软件技术有限公司 | Adaptive hardware driving method and gateway equipment |
| CN115695088A (en) * | 2022-10-26 | 2023-02-03 | 中国第一汽车股份有限公司 | VLAN (virtual local area network) dividing method for Android system and vehicle-mounted Android system |
| CN116450385A (en) * | 2022-01-07 | 2023-07-18 | 荣耀终端有限公司 | Watchdog detection method, device and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102215432A (en) * | 2011-06-02 | 2011-10-12 | Tcl集团股份有限公司 | Television system, television system starting method and device |
| CN102520936A (en) * | 2011-11-30 | 2012-06-27 | 厦门雅迅网络股份有限公司 | Method for realizing sharing of Socket communication service on Android platform |
| CN102866921A (en) * | 2012-08-29 | 2013-01-09 | 惠州Tcl移动通信有限公司 | Method and system for regulating and controlling multi-core central processing unit (CPU) |
-
2013
- 2013-09-03 CN CN201310394192.4A patent/CN103488478A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102215432A (en) * | 2011-06-02 | 2011-10-12 | Tcl集团股份有限公司 | Television system, television system starting method and device |
| CN102520936A (en) * | 2011-11-30 | 2012-06-27 | 厦门雅迅网络股份有限公司 | Method for realizing sharing of Socket communication service on Android platform |
| CN102866921A (en) * | 2012-08-29 | 2013-01-09 | 惠州Tcl移动通信有限公司 | Method and system for regulating and controlling multi-core central processing unit (CPU) |
Cited By (32)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902389A (en) * | 2014-03-06 | 2014-07-02 | 厦门雅迅网络股份有限公司 | Equipment management method supporting bidirectional communication based on android platform |
| CN104932869A (en) * | 2014-03-18 | 2015-09-23 | 苏州市伏泰信息科技有限公司 | Embedded software platform for intelligent vehicle terminal |
| CN104102540A (en) * | 2014-06-30 | 2014-10-15 | 上海卓悠网络科技有限公司 | Operation process management method and mobile terminal |
| CN104102540B (en) * | 2014-06-30 | 2017-08-25 | 上海卓悠网络科技有限公司 | The management method and mobile terminal of a kind of operation process |
| JP2017520856A (en) * | 2014-07-10 | 2017-07-27 | ハーマン インターナショナル インダストリーズ インコーポレイテッド | Operating system startup acceleration |
| JP2017521785A (en) * | 2014-07-10 | 2017-08-03 | ハーマン インターナショナル インダストリーズ インコーポレイテッド | Operating system startup acceleration |
| JP2017521789A (en) * | 2014-07-10 | 2017-08-03 | ハーマン インターナショナル インダストリーズ インコーポレイテッド | Operating system startup acceleration |
| US10379871B2 (en) | 2014-07-10 | 2019-08-13 | Harman International Industries, Incorporated | Operating system startup acceleration |
| US10776130B2 (en) | 2014-07-10 | 2020-09-15 | Harman International Industries, Incorporated | Operating system startup acceleration |
| CN104216709B (en) * | 2014-08-20 | 2016-04-27 | 深圳光启智能光子技术有限公司 | The method and apparatus of direct control hardware equipment in operating system |
| WO2016026449A1 (en) * | 2014-08-20 | 2016-02-25 | 深圳光启智能光子技术有限公司 | Method and module in operating system for controlling hardware device |
| CN104216709A (en) * | 2014-08-20 | 2014-12-17 | 深圳光启创新技术有限公司 | Method and module for directly controlling hardware equipment in operating system |
| US10599493B2 (en) | 2014-08-20 | 2020-03-24 | Kuang-Chi Intelligent Photonic Technology Ltd. | Method and module in operating system for controlling hardware device |
| CN104636128A (en) * | 2014-09-10 | 2015-05-20 | 深圳光启创新技术有限公司 | Method and module for controlling hardware equipment in operating system |
| CN104636128B (en) * | 2014-09-10 | 2018-03-02 | 深圳光启智能光子技术有限公司 | The method and module of hardware device are controlled in operating system |
| CN104267956B (en) * | 2014-09-28 | 2016-05-11 | 深圳光启智能光子技术有限公司 | The method and apparatus of control hardware equipment in a kind of operating system |
| CN104267956A (en) * | 2014-09-28 | 2015-01-07 | 深圳光启创新技术有限公司 | Method and module for controlling hardware device in operating system |
| CN105183455A (en) * | 2015-08-13 | 2015-12-23 | 深圳市广和通无线股份有限公司 | Method and system for integrating JT/T808 program on Android platform |
| CN105183455B (en) * | 2015-08-13 | 2018-09-21 | 深圳市广和通无线股份有限公司 | A kind of method and system integrating JT/T808 programs under Android platform |
| CN105472462A (en) * | 2015-11-12 | 2016-04-06 | Tcl王牌电器(惠州)有限公司 | Television function processing method and system |
| CN105975249B (en) * | 2015-12-31 | 2018-12-11 | 小米科技有限责任公司 | Application executing method and device based on hardware chip |
| CN105955829A (en) * | 2016-04-20 | 2016-09-21 | 青岛海信宽带多媒体技术有限公司 | Order processing method, device and terminal |
| CN107450926A (en) * | 2017-07-31 | 2017-12-08 | 郑州云海信息技术有限公司 | The hardware adaptor management method and device of a kind of storage device |
| CN107450926B (en) * | 2017-07-31 | 2020-09-18 | 苏州浪潮智能科技有限公司 | Hardware peripheral management method and device of storage equipment |
| CN109164996A (en) * | 2018-08-10 | 2019-01-08 | 深圳市智微智能科技开发有限公司 | A kind of realization android is from principal point screen method and Related product |
| CN109189566A (en) * | 2018-08-10 | 2019-01-11 | 深圳市智微智能科技开发有限公司 | A kind of method and Related product for realizing the upper layer android driving IO |
| CN110879659A (en) * | 2018-09-05 | 2020-03-13 | 北京九天微星科技发展有限公司 | Low-power consumption method realized based on equipment management framework in embedded real-time operating system (RT-Thread) |
| CN109388581A (en) * | 2018-10-08 | 2019-02-26 | 郑州云海信息技术有限公司 | A kind of Nonvolatile memory reservoir management method and device |
| CN109660661A (en) * | 2018-12-03 | 2019-04-19 | 北京云测信息技术有限公司 | Remote real machine screenshot method suitable for android9.0 system |
| CN112363769A (en) * | 2020-11-18 | 2021-02-12 | 许昌许继软件技术有限公司 | Adaptive hardware driving method and gateway equipment |
| CN116450385A (en) * | 2022-01-07 | 2023-07-18 | 荣耀终端有限公司 | Watchdog detection method, device and storage medium |
| CN115695088A (en) * | 2022-10-26 | 2023-02-03 | 中国第一汽车股份有限公司 | VLAN (virtual local area network) dividing method for Android system and vehicle-mounted Android system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103488478A (en) | Device management framework based on android platform | |
| US10540190B2 (en) | Generic connector module capable of integrating multiple applications into an integration platform | |
| EP2566286B1 (en) | Wireless Internet Access Module, Communication Method for Host and Wireless Internet Access Module, and Data Card | |
| US9697085B2 (en) | Presenting a file system for a file containing items | |
| CN103747074B (en) | mobile monitoring system based on Web server | |
| CN101400164B (en) | Smart card, system and method for realizing deployment customized service | |
| US20160180563A1 (en) | Method and apparatus for establishing ultra-large character library and method and apparatus for displaying character | |
| CN105893038A (en) | Method for porting android Bluetooth protocol stack to Mint17 system | |
| CN102637210A (en) | Management platform of electronic files | |
| KR20120096741A (en) | Virtual device cloud network system and method for providing applications on heterogeneous device platform | |
| CN101860440B (en) | Wireless Internet access module, method for synchronizing data by using it, and data card | |
| CN103795814A (en) | Short message equipment universal communication interface based on fully domestic CPU and OS | |
| KR20220059814A (en) | Api request processing system | |
| CN109086147A (en) | Service interface call method, device and the storage medium of application program | |
| CN103207802A (en) | Software operating system and method | |
| CN105389180A (en) | Android platform-based USB (Universal Serial Bus) port configurable method | |
| CN111078104A (en) | Redirection method of multi-point touch equipment on cloud desktop and computer equipment | |
| CN102893560A (en) | Method and network device for transmitting data stream | |
| CN102609253B (en) | A kind of application implementation method of smart card and system | |
| CN100587705C (en) | Method for host to dynamically convert multi-vendor chip device data exchange protocol | |
| CN102999329B (en) | The Active Directory interface exploitation method of configuration is mapped based on extend markup language | |
| CN101938848B (en) | Host computer equipment wireless network access method and system | |
| CN103501341A (en) | Method and device for establishing Web service | |
| CN115174659A (en) | Vehicle-mounted service container, service calling method, device and medium | |
| KR101412310B1 (en) | Virtual device cloud network system and method for providing applications on heterogeneous device platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20140101 |