Ultra-miniature intelligent device and method for running operating system
By embedding a system-on-a-chip (SoC) and storage module within a very small smart device, running an operating system independently, and sharing peripheral resources with the host device through an interface module, the problem of balancing privacy and data security with device convenience in existing technologies is solved, achieving complete isolation of the operating system and an efficient and convenient user experience.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- SHENZHEN PINGBO INFORMATION TECHNOLOGY CO LTD
- Filing Date
- 2024-12-09
- Publication Date
- 2026-05-15
AI Technical Summary
Existing technologies struggle to balance the security of privacy data with the efficiency and convenience of mobile devices. Dual-system or multi-system solutions present security risks due to hardware resource sharing. USB-booted operating systems lack sufficient host machine resources for reuse, and cloud terminal solutions offer a poor user experience.
It adopts a very miniature intelligent device with a built-in system-on-a-chip (SoC) and storage module. It connects to the host device through an interface module, runs an operating system independently, and shares peripheral resources with the host device through a hardware abstraction layer to achieve physical isolation and data security.
It achieves complete isolation of the operating system, eliminates the security risks of hardware resource sharing, simplifies the user experience, improves convenience and compatibility, and solves the problem of inconvenient device carrying and management.
Smart Images

Figure CN2024137714_15052026_PF_FP_ABST
Abstract
Description
Methods for using very small intelligent devices and their operating systems
[0001] This application claims priority to Chinese Patent Application No. 202411601320.2, filed on November 11, 2024, entitled “Very Miniature Intelligent Device and Method for Operating an Operating System”, the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of operating systems, and more specifically, to a very small intelligent device and a method for running an operating system. Background Technology
[0003] With the widespread adoption of mobile internet and smart devices, mobile devices (such as smartphones and tablets) have become the primary carriers of personal privacy and sensitive data. These devices contain a large amount of personal information, financial data, work documents, and more. However, due to technological and cost limitations, achieving complete isolation and protection of this private and sensitive data remains a challenge.
[0004] To solve this technical challenge, the following technological development roadmap exists in the market:
[0005] (1) Dual-system or multi-system solution:
[0006] Deploying two or more operating systems on the same mobile device, one for work and another for personal use, offers the advantage of partial data isolation at the software level. However, because these systems share the same hardware resources (such as CPU, memory, and storage), the risk of information leakage remains in the face of malicious attacks or system vulnerabilities. Incomplete security isolation cannot completely eliminate cross-contamination of data.
[0007] (2) Booting the operating system from a USB flash drive:
[0008] This method involves placing a Windows or other operating system image file on a USB drive, allowing the user to boot the operating system from the USB drive. The advantage of this approach is that a standalone operating system can run on the host computer without compromising the host system's data security. However, this method reuses most of the host machine's resources (such as CPU, memory, and network), resulting in poor security and difficulty in supporting mobile terminals (mobile devices do not support booting an operating system from an external device).
[0009] (3) Cloud terminal solution:
[0010] Cloud terminals host data and applications on cloud servers, with users running clients only on their mobile devices, and all operations are completed remotely over the network. This approach achieves good data isolation because all computation and storage are in the cloud. However, its disadvantage lies in a poor user experience, especially when the network is unstable or has high latency, leading to frequent issues such as lag and slow response, failing to meet users' daily needs.
[0011] Therefore, it is evident that the above solutions cannot simultaneously guarantee the security of privacy data and ensure the efficiency and convenience of the device. Summary of the Invention
[0012] The purpose of this application is to provide a very small intelligent device and a method for running an operating system.
[0013] In a first aspect, a very small intelligent device according to this application includes: a system-on-a-chip (SoC) with a built-in preset operating system;
[0014] An interface module is electrically connected to the system-on-a-chip (SoC), through which the SoC transmits data with an external host device.
[0015] The storage module is electrically connected to the system-on-a-chip (SoC).
[0016] The operating system interacts with the user through the input / output devices of the host device.
[0017] In one possible implementation, the host device includes a display screen, through which the operating system provides a visual graphical user interface.
[0018] In one possible implementation, the very miniature intelligent device further includes any one or more of the following components: a battery module, a display screen, a WIFI module, a cellular communication module, a Bluetooth module, a microphone, a speaker, a camera, or a sensor.
[0019] In one possible implementation, the host device further includes any one or more of the following components: a battery module, a WIFI module, a cellular communication module, a Bluetooth module, a microphone, a speaker, a camera, or a sensor;
[0020] The very miniature intelligent device shares the components through the interface module. One possible implementation is that the interface module includes a USB module;
[0021] The system-on-a-chip (SoC) interacts with the external host device through the interface module and draws power from the host device.
[0022] One possible implementation is that after establishing a connection with the host device, the very miniature intelligent device first detects the peripherals configured on itself and the host device to obtain the peripheral configuration information of both parties, and then selects peripherals based on the peripheral configuration information of both parties.
[0023] One possible implementation method includes selecting a peripheral device corresponding to the host device when the very miniature intelligent device itself does not have the required type of peripheral device.
[0024] Furthermore, when both parties have the required type of peripherals, the performance parameters of the peripherals of both parties are compared, and the peripheral with better performance parameters is selected based on the comparison results.
[0025] One possible implementation is that, during operation, the very miniature intelligent device uses the host device's speaker to play sound when it needs to.
[0026] When network communication is required, the host device's WIFI module or cellular communication module is used for network communication; when sound needs to be collected, the host device's microphone is used for sound collection.
[0027] When images and videos need to be acquired, the host device's camera is used to acquire them; when GPS and sensor data are needed, the host device's GPS and sensors are used to acquire the data.
[0028] Secondly, according to the present application, a method for running an operating system on the very miniature intelligent device includes: installing client software that controls the operation of the operating system on the host device;
[0029] With the interface module connected to the host device, the operating system is started.
[0030] The operating system encodes and compresses the content to be transmitted into a data packet and transmits it to the client software through the interface module. The client software decompresses and decodes the data packet and outputs it through the host device.
[0031] The client software sends control commands based on the user's operations. These control commands are transmitted to the operating system through the interface module to control the operating system.
[0032] One possible implementation is that the client software includes a resolution adaptive module;
[0033] The resolution adaptive module compares the preset resolution of the operating system with the resolution of the host device. When the preset resolution of the operating system and the resolution of the host device are the same, the interface of the operating system is displayed normally. When the preset resolution of the operating system and the resolution of the host device are different but the ratio is the same, the resolution of the operating system is scaled up or down proportionally to the resolution of the host device. When the preset resolution of the operating system and the resolution of the host device are different and the ratio is different, the resolution of the operating system is scaled up or down proportionally based on the wider or taller side of the smaller resolution size of the host device, and the corresponding other side is displayed in the center. The excess part is displayed as black borders on the top, bottom or left and right sides of the screen.
[0034] In one possible implementation, the client software includes a coordinate transformation module; the host device's display includes a touchscreen.
[0035] When the preset resolution of the operating system and the resolution of the host device are different, the coordinate transformation module converts the screen touch coordinates of the host device into the touch coordinates of the operating system.
[0036] One possible implementation is that the coordinate transformation module compares the preset resolution of the operating system with the resolution of the host device. When the preset resolution of the operating system and the resolution of the host device are the same, the touch coordinates of the operating system and the touch coordinates of the host device are the same. When the preset resolution of the operating system and the resolution of the host device are different but the ratio is the same, the touch coordinates of the host device are enlarged or reduced proportionally. When the preset resolution of the operating system and the resolution of the host device are different and the ratio is different, the wider or taller side of the smaller resolution of the host device is used as a reference, and the corresponding wider or taller side of the operating system is enlarged or reduced proportionally. The enlargement or reduction factor is the enlargement or reduction factor of the touch coordinates of the host device. The other side is displayed in the center of the screen, and the excess part is displayed as a black border. The excess part is removed in the corresponding touch coordinate calculation.
[0037] One possible implementation is that, after the operating system starts, the very miniature intelligent device establishes a data connection with the host device through the interface module;
[0038] The operating system encodes and compresses audio and video data into data packets for transmission.
[0039] One possible implementation is that the operating system includes upper-layer application software, a hardware abstraction layer, and virtualization device drivers;
[0040] When the upper-layer application software needs to use the host device's input / output devices during operation, it sends a request to the operating system's virtualization device driver through the hardware abstraction layer. After receiving the request, the virtualization device driver transmits the request to the host device's client software through the interface module. The client software then uses the host device's driver to complete the corresponding functions with the input / output devices.
[0041] One possible implementation is that after establishing a connection with the host device, the very miniature intelligent device first detects the peripherals configured on itself and the host device to obtain the peripheral configuration information of both parties, and then selects peripherals based on the peripheral configuration information of both parties.
[0042] One possible implementation method includes selecting a peripheral device corresponding to the host device when the very miniature intelligent device itself does not have the required type of peripheral device.
[0043] Furthermore, when both parties have the required type of peripherals, the performance parameters of the peripherals of both parties are compared, and the peripheral with better performance parameters is selected based on the comparison results.
[0044] One possible implementation is that, during the operation of the very miniature intelligent device, when sound needs to be played, the operating system initiates a network connection request to the virtualization device driver through the hardware abstraction layer, which is then sent to the client software via the data transmission channel of the interface module. The client software then uses the host device's speaker to play the sound.
[0045] When network communication is required, the operating system initiates a network connection request to the virtualization device driver through the hardware abstraction layer, which is then sent to the client software via the data transmission channel of the interface module, and the host device's WIFI module or cellular communication module is used for network communication.
[0046] When sound needs to be collected, the operating system initiates a network connection request to the virtualization device driver through the hardware abstraction layer, which is then sent to the client software via the data transmission channel of the interface module, and the host device's microphone is used to collect the sound.
[0047] When images and videos need to be captured, the operating system initiates a network connection request to the virtualization device driver through the hardware abstraction layer, which is then sent to the client software via the data transmission channel of the interface module, and the host device's camera is used to capture images and videos.
[0048] When GPS and sensor data are needed, the operating system initiates a network connection request to the virtualization device driver through the hardware abstraction layer. This request is then sent to the client software via the data transmission channel of the interface module, where the host device's GPS and sensors collect the data.
[0049] This application has the following beneficial effects:
[0050] Compared with dual-system or multi-system technical solutions, this application achieves true physical isolation by completely encapsulating the operating system in an independent hardware device, thus completely eliminating the security risks brought about by hardware resource sharing.
[0051] This application operates independently, without relying on the host machine's CPU, memory, or storage, ensuring the security of data processing. Furthermore, since the device only needs to connect to the host machine via a USB interface, it reuses the host machine's peripheral resources (such as screen and touchscreen), greatly simplifying the user experience and improving convenience and compatibility.
[0052] This application simplifies the device structure, reduces weight, and ensures the integrity of functions, solving problems such as inconvenient device carrying and management, limited user experience, high cost and maintenance, and complex upgrades. Attached Figure Description
[0053] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:
[0054] Figure 1 is an overall architecture diagram of this application;
[0055] Figure 2 shows the internal connection diagram of a very small intelligent device;
[0056] Figure 3 shows another overall architecture diagram of this application.
[0057] In the diagram: 1-Very miniature intelligent device; 2-Host device; 101-System-on-a-Chip (SoC); 102-Storage module; 103-Operating system; 104-Interface module. Detailed Implementation
[0058] The present application will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present application, but do not limit the present application in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present application. These all fall within the protection scope of the present application.
[0059] As shown in Figures 1 and 2, this application provides a very miniature intelligent device, which is portable, such as a USB flash disk. The very miniature intelligent device 1 internally includes a system-on-chip (SoC) 101, an interface module 104, and a storage module 102. The very miniature intelligent device 1 has a built-in pre-installed operating system 103, which can be Android, or other versions or types, such as Linux, HarmonyOS, Ubuntu, etc., further expanding its applicability and supporting more application scenarios. After the device is connected to an external host device 2 through the interface module 104, a complete operating system can run independently on the very miniature intelligent device 1. The host device 2 displays the operating system interface, and the operating system can be run through simple plug-and-play operations, simplifying the user's operation process. During use, the very small intelligent device 1 does not rely on the CPU, GPU, memory or storage resources of the host device 2. All computing, data processing and storage are completed inside the device, but it can share the input / output devices of the host device 2. This achieves complete isolation between the operating system 103 and the host device 2 in a low-cost and highly portable manner, ensuring data security and system stability.
[0060] In this application, the system-on-a-chip (SoC) 101 preferably uses a high-performance, low-power SoC as the central processing unit (CPU). The storage module 102 may include memory and flash memory to meet the data storage needs of different users. The interface module 104 may be a USB module, such as USB 3.x or USB 4. It supports high-speed data exchange standards for fast transfer of multimedia files and other large datasets, and can also power the very small smart device 1 through the host device. Users only need to connect the device to the host device 2 (such as a smartphone, tablet, or computer) to start using it. The host device 2 includes a display screen (which may be a touch screen), and the operating system provides a visual graphical user interface through the display screen of the host device 2.
[0061] As shown in Figure 3, in addition to the basic system-on-a-chip (SoC) 101, storage module 102, and interface module 104, other non-core hardware components can be flexibly selected according to specific application scenarios. To better ensure the normal operation of the operating system, guarantee complete functional applications, and provide a better user experience, the very miniature intelligent device 1 can also include core components of a mobile device such as a battery module, Wi-Fi module, cellular communication module, microphone, speaker, camera, and various sensors. Depending on the scenario requirements, the very miniature intelligent device 1 can add one or more core components of a mobile device. For example, if the very miniature intelligent device requires independent power and does not draw power from the host device, it can include a battery module electrically connected to the SoC. If an independent cellular communication module is required for communication, the very miniature intelligent device can include a cellular communication module. To reduce the size of the very miniature intelligent device and maximize portability, the core components such as the battery module, Wi-Fi module, cellular communication module, microphone, speaker, camera, and various sensors can fully utilize the existing peripherals of the host device, allowing the very miniature intelligent device to share these core component peripherals. Various sensors include common smartphone sensors such as light sensors, GPS sensors, proximity sensors, gravity sensors, accelerometers, gyroscopes, barometers, and magnetic field sensors.
[0062] This application achieves both the independence of the device's operating system by using an independent system-on-a-chip (SoC) 101, interface module 104, and storage module 102, and pre-installing a complete operating system 103. This allows the device to operate independently without relying on the computing and data processing resources of the host device 2, thus protecting user privacy and sensitive data. Furthermore, it shares hardware resources such as the battery module, WIFI module, cellular communication module, microphone, speaker, camera, and various other types of sensors with the host device 2 through USB communication and power supply. This fully utilizes the existing core peripheral components of the host device 2, simplifies the device structure, reduces weight, and ensures the integrity of functions. It solves problems such as inconvenient device carrying and management, limited user experience, high cost, and complex maintenance and upgrades.
[0063] This application also provides a method for running an operating system on a very small intelligent device, including:
[0064] The very miniature intelligent device uses the device described in Example 1. Client software is installed on the host device to control the operating system and enable interaction between the very miniature intelligent device and the host device. When the host device uses different operating system platforms, the installation package of the corresponding client software differs; for example, it is an exe file for Windows systems and an apk file for Android systems.
[0065] After the interface module connects to the host device, the host device recognizes the device through the interface module and provides power. The user can then wait for the operating system of the very miniature smart device to start running through the client software. A data connection is established between the very miniature smart device and the host device through the interface module. After successful startup, the operating system of the very miniature smart device will be displayed on the screen of the host device. An audio and video connection channel is established between the very miniature smart device and the host device through the interface module. The interface image or video of the operating system is compressed and encoded into data packets and transmitted to the host device at a custom frequency through the audio and video connection channel. After receiving the data packets, the host device decodes and decompresses them through the client software, restoring them as image or video images, which are then displayed visually on the host device. In addition, to improve display quality, the client software also includes a resolution adaptive module to ensure that the operating system interface can be displayed correctly regardless of the screen size of the host device.
[0066] When the host device's screen displays the operating system interface of the very miniature smart device, the user operates the operating system on the very miniature smart hardware device using the host device's screen touch information. The client software obtains the host device's screen touch information and transmits the data packets of the screen touch information to the very miniature smart device through the data connection channel at a custom frequency. The very miniature smart device issues control commands based on the screen touch information and executes them, thereby realizing user interaction and controlling the operating system.
[0067] The custom frequency can be set based on time, such as 1ms. The compression and encoding technologies used can be H.264 or H.265, which can compress high-definition audio and video signals into smaller data packets, thereby reducing the amount of data transmitted.
[0068] The operating system interface of a very small smart device can be preset with a fixed resolution. Due to the diversity of host devices, such as smartphones, tablets, or computers, when the resolution of the very small smart device is different from that of the host device, there may be problems such as incomplete screen display or incorrect aspect ratio. The client software has a built-in resolution adaptive module to provide optimized screen display and ensure that the host device screen displays the operating system interface of the very small smart device in the best display mode without distortion.
[0069] The resolution adaptive module compares the operating system's preset resolution with the host device's resolution. When the resolutions are the same, the operating system's interface is displayed normally. When the resolutions are different but the aspect ratio is the same, the operating system's resolution is scaled up or down proportionally. When the resolutions are different and the aspect ratios are also different, the operating system's resolution is scaled up or down proportionally based on the smaller side of the host device's resolution, and the other side is displayed in the center. Any excess parts are displayed as black borders on the top, bottom, left, or right sides of the screen. If the operating system's default fixed resolution is 1920*1080, and the host device's screen resolution is 1920*1080, the operating system interface will be displayed normally. If the host device's screen resolution is 3840*2160, the resolution adaptation module will change the operating system's resolution to 3840*2160 and display it on the host device's screen. If the host device's screen resolution is 2048*1080, the operating system's resolution will remain 1920*1080, but when the operating system interface is displayed on the host device's screen, there will be a black border of (2048-1920) / 2 = 64 pixels on each side of the host device's screen. If the host device's screen resolution is 1920*960, the operating system's resolution will be proportionally reduced to 1707*960 by the adaptation module and then displayed in the center on the host device's screen, resulting in a black border of (1920-1707) / 2 = 106.5 pixels on each side of the host device's screen.
[0070] The host device's client software can also obtain the host device's screen touch information and transmit the data packets of the screen touch information to the operating system of the very miniature smart device at a custom frequency through the data connection channel. The operating system of the very miniature smart device issues control commands based on the screen touch information and executes them, thereby realizing user interaction.
[0071] The client software acquires screen touch information as screen touch coordinates, represented in pixels. The client software includes a coordinate conversion module. When the operating system's preset resolution differs from the host device's resolution, this module converts the host device's screen touch coordinates to the operating system's. The module compares the operating system's preset resolution with the host device's resolution. If they are the same, the operating system's touch coordinates and the host device's touch coordinates are identical. If they differ but the scale is the same, the host device's touch coordinates are proportionally enlarged or reduced to the operating system's touch coordinates. When both the resolution and the resolution scale differ, the smaller side (wide or high) of the host device's resolution is used as a reference, and the corresponding side (wide or high) of the operating system's coordinates is proportionally enlarged or reduced. The enlargement or reduction factor is the same as the enlargement or reduction factor for the host device's touch coordinates. The other side is centered on the screen, and any excess portion is displayed as a black border. This excess portion is removed during the corresponding touch coordinate calculation, ensuring the accuracy of the screen touch coordinate position information and enabling precise user interaction. If the operating system's default fixed resolution is 1920*1080, the obtained touch point coordinates of the host device's screen are (1000, 500). If the host device's screen resolution is 1920*1080, the operating system's touch point coordinates remain the same, also (1000, 500). If the host device's screen resolution is 3840*2160, the operating system's touch point coordinates are halved, becoming (500, 250). If the host device's screen resolution is 2048*1080, the coordinate transformation module converts the horizontal coordinate to 1000 - (2048 - 1920) / 2 = 936, resulting in (936, 500) touch point coordinates, ensuring that the operating system obtains the correct touch point coordinates.
[0072] The operating system of a very small intelligent device includes upper-layer application software, a hardware abstraction layer, and virtualization device drivers. Upper-layer application software refers to the various apps commonly used by users. The Hardware Abstraction Layer (HAL) is the software layer between the operating system runtime environment and hardware device drivers. It acts as a bridge connecting upper-layer software and hardware devices, describing the hardware functions available to upper-layer application software, providing a consistent interface, and allowing upper-layer software to interact with hardware whose implementation details are hidden. Virtualization device drivers are hardware device drivers simulated in the virtualization environment created within the operating system. The operating system provides virtualization device capabilities to upper-layer application software through the HAL layer, sharing the host machine's hardware peripheral component resources with the upper-layer application software. When the upper-layer application software needs to use corresponding peripheral resources during operation, it sends a request to the virtualization device driver through the HAL layer. Upon receiving the request, the virtualization device driver transmits it to the host device's client software through an interface module. The client software then uses the host device's driver to interact with the hardware and complete the corresponding function. After the hardware device completes its corresponding functional operation, the client software returns the execution result to the virtualization device driver of the operating system through the interface module. The virtualization device driver then encapsulates these execution results into a format that upper-layer application software can understand and returns them to the upper-layer application software through the HAL layer. This enables direct and efficient use of the host machine's hardware peripheral component resources while ensuring compatibility with various upper-layer application software. During the operation of the operating system of the very miniature intelligent device, if an application software needs to play sound, it can use the host device's speaker through the interface module. If it needs to use network functions such as a browser, it can use the host device's WIFI module or cellular network for network communication. If it needs to collect sound data, it uses the host device's microphone to collect sound data. If it needs to use functions such as photography and videography, it uses the host device's camera to collect image or video data. If it needs to use some GPS or sensor data, it uses the host device's GPS and sensors to collect data.
[0073] This embodiment enables the independent operation of a complete operating system with minimal hardware, achieving complete isolation of privacy and sensitive data at a low cost, while ensuring data security and operating system stability. Furthermore, it provides a unified security solution across platforms, which can be used not only on mobile terminals but also on traditional computing devices (such as laptops and desktops), meeting the needs of different application scenarios.
[0074] As shown in Figure 3, the very miniature intelligent device itself can also be configured with the necessary peripherals, which technicians can select and configure according to the actual situation. If the very miniature intelligent device is configured with one or more of the following components: battery module, WIFI module, cellular communication module, microphone, speaker, camera, and sensor, the operating system can directly use the very miniature intelligent device's own peripherals when the very miniature intelligent device uses network, audio and video data, location information, sensor data, etc. for data interaction. If the host device is also configured with one or more of the following components: battery module, WIFI module, cellular communication module, microphone, speaker, camera, and sensor, the operating system can choose between the peripherals of the very miniature intelligent device and the peripherals of the host device. Specifically, it can detect whether the device itself has the corresponding peripherals; if not, it will use the shared peripherals of the host device. After establishing a connection with the host device, the very miniature intelligent device first detects the peripherals configured on itself and the host device to obtain the peripheral configuration information of both parties, and then selects the peripherals based on the peripheral configuration information of both parties. The selected strategies are as follows: (1) If the miniature smart device itself does not have the required type of peripheral, select the peripheral corresponding to the host device; (2) If both have the required type of peripheral, compare the performance parameters of the peripherals of both parties, and select the peripheral with better performance parameters based on the comparison results to achieve a better user experience and functional application.
[0075] 1. During the operation of the operating system of a very small intelligent device, if an application requires sound playback, it can use the speaker of the host device to play the sound.
[0076] When the operating system of a very small intelligent device is running, if sound needs to be played, the upper-layer application software sends a corresponding sound playback request. This request is initiated to the virtualization device driver through the HAL layer. After receiving the sound playback request, the virtualization device driver transmits it to the host device's client software through the data connection channel of the interface module. The operating system of the very small intelligent device then compresses and encodes the sound data into data packets and transmits them to the host device at a custom frequency through the audio-video connection channel. The host device obtains the data packets through the audio-video connection channel and decodes and decompresses the audio data from the data packets through the client software, thereby playing the audio data using the host device's speaker.
[0077] Custom frequencies can be set in time units, such as 1ms.
[0078] 2. During the operation of the operating system, if you need to use network applications such as browsers, you can use the host device's WIFI module or cellular communication module for network communication.
[0079] When the operating system of a very small intelligent device is running, and network functions are used, the operating system initiates a network connection request to the virtualization device driver through the HAL layer. This request is then sent to the client software via the data transmission channel of the interface module. The client software establishes a connection with the server using the host device's Wi-Fi module or mobile network. After the connection is established, the host device sends or receives packet data based on TCP. The packet data sent by the host device originates from the upper-layer application software data of the very small intelligent device's operating system transmitted via the data transmission channel. The packet data received by the host device is also sent to the upper-layer application software of the very small intelligent device's operating system via the data transmission channel. This enables the very small intelligent device's operating system to conduct network communication using the host device's Wi-Fi module or mobile network.
[0080] 3. During the operation of the operating system of a very small intelligent device, if sound collection is required, the host device's microphone is used to collect sound data.
[0081] During the operation of the operating system of a very small intelligent device, if an upper-layer application software needs to collect sound, the upper-layer application software sends a corresponding sound collection request. This request is initiated to the virtualization device driver through the HAL layer. After receiving the sound collection request, the virtualization device driver transmits it to the host device's client software through the data connection channel of the interface module. The client software collects sound data through the microphone of the host device, compresses and encodes the sound data into data packets, and transmits them at a custom frequency through the audio-video connection channel to the virtualization device driver of the operating system of the very small intelligent device. The virtualization device driver then decodes and decompresses the audio data of the data packets and encapsulates them into a format that the upper-layer application software can understand. Finally, it returns the data to the upper-layer application software through the HAL layer, thus completing the sound data collection function.
[0082] 4. During the operation of the operating system of a very small intelligent device, applications using functions such as photography and video recording may use the host device's camera to collect image or video data.
[0083] During the operation of the operating system of a very small intelligent device, if an upper-layer application software needs to acquire image or video data, the upper-layer application software sends a corresponding image or video data request. This request is initiated to the virtualization device driver through the HAL layer. After receiving the image or video data request, the virtualization device driver transmits it to the host device's client software through the data connection channel of the interface module. The client software acquires image or video data through the host device's camera, compresses and encodes the image or video data into data packets, and transmits these data packets to the virtualization device driver of the very small intelligent device's operating system at a custom frequency through the audio / video connection channel. The virtualization device driver then decodes and decompresses the image or video data in the data packets, encapsulates them into a format that the upper-layer application software can understand, and returns them to the upper-layer application software through the HAL layer, thus completing the image or video data acquisition function.
[0084] 5. During the operation of the operating system of a very small intelligent device, if an application uses some GPS and sensor data, it may collect data using the GPS and sensors of the host device.
[0085] During the operation of the operating system of the very miniature intelligent device, if an upper-layer application software needs GPS or sensor data, the upper-layer application software sends a corresponding request to the virtualization device driver through the HAL layer. After receiving the request, the virtualization device driver transmits the request to the host device's client software through the data connection channel of the interface module. The client software obtains the corresponding data collected by the sensor device on the host device, compresses and encodes it into a data packet, and sends the data packet to the virtualization device driver of the operating system of the very miniature intelligent device through the data connection channel. The virtualization device driver then decodes and decompresses the data packet, encapsulates it into a format that the upper-layer application software can understand, and returns it to the upper-layer application software through the HAL layer. The upper-layer application software then obtains the corresponding GPS or sensor data.
[0086] This embodiment provides users with a wider range of choices. If special needs arise, after adding one or more core components to the miniature intelligent device, users can dynamically and flexibly choose whether to use independent peripherals or reuse peripherals from the host device, thereby further expanding the application scope of the device and supporting more application scenarios.
[0087] The specific embodiments of this application have been described above. It should be understood that this application is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the substantive content of this application. Unless otherwise specified, the embodiments and features described in the embodiments of this application can be arbitrarily combined with each other.
Claims
1. A very miniature intelligent device, characterized in that, include: System-on-a-chip (SoC) with a built-in pre-installed operating system; An interface module is electrically connected to the system-on-a-chip (SoC), through which the SoC transmits data with an external host device. The storage module is electrically connected to the system-on-a-chip (SoC). The operating system interacts with the user through the input / output devices of the host device.
2. The ultra-miniature intelligent device according to claim 1, characterized in that, The host device includes a display screen, through which the operating system provides a visual graphical user interface.
3. The ultra-miniature intelligent device according to claim 1, characterized in that, The very miniature intelligent device also includes any one or more of the following components: battery module, display screen, WIFI module, cellular communication module, Bluetooth module, microphone, speaker, camera or sensor.
4. The ultra-miniature intelligent device according to claim 1, characterized in that, The host device also includes any one or more of the following components: battery module, WIFI module, cellular communication module, Bluetooth module, microphone, speaker, camera or sensor; The very miniature intelligent device shares the components through the interface module.
5. The ultra-miniature intelligent device according to claim 1, characterized in that, The interface module includes a USB module; The system-on-a-chip (SoC) interacts with the external host device through the interface module and draws power from the host device.
6. The ultra-miniature intelligent device according to claim 1, characterized in that, After establishing a connection with the host device, the very miniature intelligent device first detects the peripherals configured on itself and the host device to obtain the peripheral configuration information of both parties, and then selects peripherals based on the peripheral configuration information of both parties.
7. The ultra-miniature intelligent device according to claim 6, characterized in that, The selection methods include: when the very small intelligent device itself does not have the required type of peripheral, selecting the peripheral corresponding to the host device; Furthermore, when both parties have the required type of peripherals, the performance parameters of the peripherals of both parties are compared, and the peripheral with better performance parameters is selected based on the comparison results.
8. The ultra-miniature intelligent device according to claim 1, characterized in that, During operation, the very miniature intelligent device uses the host device's speaker to play sound when it needs to play sound. When network communication is required, the host device's WIFI module or cellular communication module is used for network communication. When sound needs to be captured, use the host device's microphone to capture the sound; When it is necessary to capture images and videos, use the host device's camera to capture images and videos; When GPS and sensor data are needed, the host device's GPS and sensors are used to collect data.
9. A method for running an operating system on a very miniature intelligent device according to any one of claims 1-8, characterized in that, include: Install client software that controls the operation of the operating system on the host device; With the interface module connected to the host device, the operating system is started. The operating system encodes and compresses the content to be transmitted into a data packet and transmits it to the client software through the interface module. The client software decompresses and decodes the data packet and outputs it through the host device. The client software sends control commands based on the user's operations. These control commands are transmitted to the operating system through the interface module to control the operating system.
10. The method according to claim 9, characterized in that, The client software includes a resolution adaptive module; The resolution adaptive module compares the preset resolution of the operating system with the resolution of the host device. When the preset resolution of the operating system and the resolution of the host device are the same, the interface of the operating system is displayed normally. When the preset resolution of the operating system and the resolution of the host device are different but the ratio is the same, the resolution of the operating system is scaled up or down proportionally to the resolution of the host device. When the preset resolution of the operating system and the resolution of the host device are different and the ratio is different, the resolution of the operating system is scaled up or down proportionally based on the wider or taller side of the host device resolution, and the other side is displayed in the center, with the excess part displayed as black borders on the top, bottom or left and right.
11. The method according to claim 9, characterized in that, The client software includes a coordinate transformation module; The host device's display includes a touchscreen; When the preset resolution of the operating system and the resolution of the host device are different, the coordinate transformation module converts the screen touch coordinates of the host device into the touch coordinates of the operating system.
12. The method according to claim 11, characterized in that, The coordinate transformation module compares the preset resolution of the operating system with the resolution of the host device. When the preset resolution of the operating system and the resolution of the host device are the same, the touch coordinates of the operating system and the touch coordinates of the host device are the same. When the preset resolution of the operating system and the resolution of the host device are different but the ratio is the same, the touch coordinates of the host device are enlarged or reduced proportionally. When the preset resolution of the operating system and the resolution of the host device are different and the ratio is different, the wider or taller side of the smaller resolution of the host device is used as a reference, and the corresponding wider or taller side of the operating system is enlarged or reduced proportionally. The enlargement or reduction factor is the enlargement or reduction factor of the touch coordinates of the host device. The other side is displayed in the center of the screen, and the excess part is displayed as a black border. The excess part is removed in the corresponding touch coordinate calculation.
13. The method according to claim 9, characterized in that, After the operating system starts, the very miniature intelligent device and the host device establish a data connection through the interface module; The operating system encodes and compresses audio and video data into data packets for transmission.
14. The method according to claim 9, characterized in that, The operating system includes upper-layer application software, a hardware abstraction layer, and virtualization device drivers; When the upper-layer application software needs to use the host device's input / output devices during operation, it sends a request to the operating system's virtualization device driver through the hardware abstraction layer. After receiving the request, the virtualization device driver transmits the request to the host device's client software through the interface module. The client software then uses the host device's driver to complete the corresponding functions with the input / output devices.
15. The method according to claim 9, characterized in that, After establishing a connection with the host device, the very miniature intelligent device first detects the peripherals configured on itself and the host device to obtain the peripheral configuration information of both parties, and then selects peripherals based on the peripheral configuration information of both parties.
16. The method according to claim 15, characterized in that, The selection methods include: when the very small intelligent device itself does not have the required type of peripheral, selecting the peripheral corresponding to the host device; Furthermore, when both parties have the required type of peripherals, the performance parameters of the peripherals of both parties are compared, and the peripheral with better performance parameters is selected based on the comparison results.
17. The method according to claim 14, characterized in that, During operation, when the very miniature intelligent device needs to play sound, the operating system initiates a network connection request to the virtualization device driver through the hardware abstraction layer, which is then sent to the client software via the data transmission channel of the interface module. The client software then uses the host device's speaker to play the sound. When network communication is required, the operating system initiates a network connection request to the virtualization device driver through the hardware abstraction layer, which is then sent to the client software via the data transmission channel of the interface module, and the host device's WIFI module or cellular communication module is used for network communication. When sound needs to be collected, the operating system initiates a network connection request to the virtualization device driver through the hardware abstraction layer, which is then sent to the client software via the data transmission channel of the interface module, and the host device's microphone is used to collect the sound. When images and videos need to be captured, the operating system initiates a network connection request to the virtualization device driver through the hardware abstraction layer, which is then sent to the client software via the data transmission channel of the interface module, and the host device's camera is used to capture images and videos. When GPS and sensor data are needed, the operating system initiates a network connection request to the virtualization device driver through the hardware abstraction layer. This request is then sent to the client software via the data transmission channel of the interface module, where the host device's GPS and sensors collect the data.