WES operating system lithium battery power supply solution


  Author :Iflowpower – Portable Power Station Supplier

With the enhancement of 32-bit RISC systems, desktop X86 architecture is gradually reduced to electrical energy demand. Today, these two platforms can be used to design battery-powered mobile devices. However, when the desktop application is actually used for mobile devices, it is necessary to make special considerations in some respects, and the emergence of the WindowEmbeddedStandard operating system solves this problem.

WindowembeddedStandard (referred to as WES) is not just a releasing desktop operating system, which is a different environment with new features designed for low power, mobile, and no continuous operation. This article will introduce how to use these features efficiently. Desktops and mobile devices are different from security perspectives, people may lose mobile devices, resulting in threats of data security.

There may be many phone numbers in a cellular phone. A WES device may contain American national phone books. And there is a particular important data, ie biometric data.

The account or phone number is stolen, can be modified; and once the biological identification database is destroyed, then the problem is not small. For "stationary data" security, WES supply disk-level, directory level, or file-level data encryption technology, because EFS (encrypted file system) is part of the basic NTFS file system. Although WES did not use Vista-level "BitLocker" encryption, other methods were used to establish an equivalent security system.

In addition, the system also supplies a variety of third-party '' integration 'encryption solutions, some of which meet the FIP140-2 standards, and some methods are integrated with hard disk technology. All of these security solutions are starting from authentication, and the identity spoofing of mobile devices is a real threat. We hope that mobile devices can be used outside of the security zone, so we have to understand whether it is really the device who called home '.

About mobile devices may have another 'spoofed' - clone or twin equipment that can be switched with target device. Perhaps an unknowing partner will not intend to bring this 'evil twin equipment' into the safe area, as well as the hard drive in the mobile device is taken out into another computer to analyze and attack. To pay attention, good user safety three elements (what do you have - tag, who - biometric identification, what do you know - passwords) Not enough to overcome this kind of fraud.

Users who take legal authentication can still log in to the network by leaking devices (for example, using installed keyboard logger) to destroy security. The device itself (not only software on the hard disk) is part of the security path to transmit data on the network. This is the best to implement some hardware solutions specified by TCG (Trusted Computer Group).

Implementing important features such as hardware components such as Atmel's TPM (Trusted Platform Module), especially "Safe Start", which has received support for third-party integration encrypted file systems. The idea here is that with the loading of the boot software, the only software and equipment identity hash code will appear. This hash code is stored in the depths of the module, even if the user or manager cannot know.

Only the system understands what software to start, and the software understands only on this hardware. The TPM module is also a password, a password, key, and certificate supply security repository. 'Still' Save Data on the RAM or on disk sectors (such as password) can be extracted by commercial tools such as WinHex and restore it.

If these data is located in sectors that are not encrypted by basic NTFS (such as offline processing areas, temporary districts, switches, or printing areas), it may be clear. But even after encryption, by using a fast offline computer, you can have millions of bright strings until they match the hash result ', thereby obtaining a password or key. The best way to ensure that important key data is to store it the deepest point of the chip, because there is tamper detection and response circuit, protect data from intrusion.

Even if it is not national security, it is often powerful data protection, such as HD media. Many mobile X86 devices are planning, while HD video playback is usually one of the target applications of these devices. In fact, all commercial HD video content is protected by powerful DRM (such as Sony Blu-ray technology), but whether it is in the laboratory or court, you can often see content owners and those who have copied and distribute them without paying royalty.

The content of the person "struggle". So far, the HD content owner seems to be larger by using the smart and easy update security VM (virtual machine), and similar to WIPO Copyright Treaty (1996) 1. For the establishment of software in embedded equipment and must be used in cross-borders, the debate has not ended.

The download version "crack" software can be run on the PC, maybe in the Norwegian courts still arguing the focus. A ban, you can prevent equipment with infringing software on the national boundary line, but this will cause serious cash flow issues in manufacturers and importers. "MolecularExpressions" in Florida State University, I accidentally discovered a message when checking the cutting line channel on the DigitalMicrovax computer.

The message text is a Russian phrase: "VAX - If you are really care, you will steal the best thing. "This sentence often appears in the black hat hacker battle in the 1970s. These DRM methods typically require multi-faceted device authentication, from the media to the player, then to the computer, then display the display device displayed.

Chip protection identity (such as TCG approval module) is required for this system. Works like Vista can work with this software and compatible with DMC1998. Microsoft is working hard to prevent Linux from being "TiVo" 3.

Designers for mobile WES devices should carefully consider the human-machine interface (HMI) problem. Even if there is a graphical processing capability of the Atom chipset, the device can still be re-designed for some HMI due to the display size limit of the display size. Of course, ordinary "XP" desktops are available, and can be paid to different color themes, if you want, you can also modify graphics and functions.

People who want to complete the custom interface for their equipment should take a look at Siverlight. SiverLight is important for Microsoft's so-called RIA (rich interactive application). Silverlight is developed in VisualStudio under .

Net 3.5, SilverLight can be used to supply direct interfaces for databases and programming languages ​​in a single IDE. .

Net3.5 is a new feature of WES supply, not part of the old version of Xpembedded. But Silverlight is a browser-based technology, so it may not be suitable for mobile handheld devices.

In this example, the preferred interface can be WindowsPresentationFoundation (WPF). WPF can serve all features of Silverlight - embedded video, animation, scalable vector images, etc., but do not use browser all of these features.

Finally, another detail of mobile devices: They generally use resistive touch screens, no mouse or trackball. This is a different interface - such as no 'hover' characteristics. Both WindowsMobile and Windows are accustomed to keeping, click drag and drop, and double-click the feature supply to the screen, but these features must be embedded in the touch screen driver, and these drivers are different, and each touch screen vendor is different.

Not a part of the ready-made WES. You have to create this driver, or get it from the OEM supplier. To remind everyone, this driver can make resources and power if it is not good.

It is best to use excellent low-power, interrupt drive design technology to create these drivers. The networked function about a real mobile device, the networked function is different. Although the laptop is also movable, it is usually working in a fixed location and maintains a link to a single WiFi access point.

However, hand-held WES devices may be used in mobile (such as workers carrying RFID reader / tablet in the warehouse), may jump from an access point 'to another access point, but also keep a session Connectivity and security. WindowsCommunicationFoundation (WCF) can supply this flexibility. WCF is part of the .

NET framework, can be used to build an application that communicates with each other. WCF is built into Vista, the OEM for developing WCF devices can download and install. WCF is Microsoft's comprehensive solution for communications, but this area is not a Microsoft's big company.

Cisco almost monopolizes the access point market, and their various standards (famous CCX) are also a factor in the OEM equipment development environment. Fortunately, these communication technologies are based on a common point with XP / Vista, so they can be installed as a plug-and-play driver with the WES system. OEM vendors should pay attention to mobile devices, the supplier is not enough.

There are strict industrial and government standards for different types of medical equipment, DOD information and various safety (economic) services. Fortunately, all these standards are developed and verified using WindowsPC devices, so OEMs adapt to WES devices is usually easy. However, all answers are not in software.

Mobile device designers should especially understand which part of his equipment is in communication scenario. For example, the laptop is almost all USB hosts. However, mobile devices may be a USB slave, or may also have the function of host and slave.

Such changes may be adjusted by BIOS. Power consumption power is used, more specifically is the energy consumption of each unit operation, and it is critical to battery power supply. In the end, we want "use days (DOU)" in the minimum battery cost and volume.

Clock rate or MIPS measurement does not indicate a device's 'Dou'. The measurement of power consumption is not strictly related to DOU. MIPs per watt have a certain degree of association, but the premise is constant sustained use - very small for mobile devices.

But the truly valuable is the Wattosecond (Eger) each operation. Mobile applications are interrupts and event-driven applications. For example, mobile devices may have a built-in RFID reader.

Its battery life may not be a small hour, but a number of reading. If the design is reasonable, this kind of device should always consume almost no power, unless you want to read the label. It should then trigger a job, send an RF pulse, read the returned data, troubleshoot, apply some business logic, and transfer the data to a local or remote database, the intermediate may start network connection.

As you can see, integration of hardware, operating systems, and application software, you can achieve optimal Erg value. Further Eger / Operation Optimization directly depends on the operation of the execution and the network used. For example, short SMS sends via CDMA or GPRS may have a high energy efficiency (each word galge).

Larger documents, computers, can have the highest efficiency when transferring with Wi-Fi (10-megabytes). Wes supplies such platforms to the application designer: can choose from the network based on the requirements of the required bandwidth, security and service quality. Power management with ACPI, existing WES Supply and Power Interface (ACPI) on XPRO Computer Computer.

With this built-in and ready-made ACPI, you can get many basic functions such as sleep. And you can achieve additional power management functions from the application layer. ACPI-level power management is based on simple monitoring of running time idle, as shown in Table 1.

This basic ACPI function contained in WES is the same as used in your laptop, just the start of mobile device power management. Control ACPI 'The' Pressure 'Setting Value is often much larger than the interval time for character-time device event drive operation. Extended power management WES2009 has a new feature, a sleep, multiple start (Horm).

Horm enables system quickly (nominal value of 1 second) to start to sleep in advance. For example, this feature enables the automation system to quickly enter the working state after a short power supply. For some devices, the OEM business should prepare for the basic ACPI level power management function that moves in the past, integrating them into the application.

OEM or its first-line vendor, can extend the BIOS to supply API to convert CPU or even related electronic devices to lower power states. Interestingly, there is enough space to achieve power consumption in a short period of time, there is sufficient space for us. For example, MPEG playback requires a variety of consumption power: one is to send data from the data, one is decoding, one is a fill frame cache, and then very low power consumption (but the screen backlight is always open) Wait a next frame.

This variable power consumption between MPEG frames and frames is true on high speed current measurement oscilloscope. Battery charging is only half of the problem, first of all, you must charge the battery. Lithium chemical raw materials have certain hazards, generally using smart batteries.

Control the battery charging requirements Access the I2C or SPI bus interface, and is the charge and discharge process from the application layer to the management battery. Battery management is a daunt hardware and software design challenge, and integration with the operating system is the foundation of any mobile device success. Figure 1: Comparison of "Laptops" and "Mobile Equipment" design standards.


Just tell us your requirements, we can do more than you can imagine.
Send your inquiry
Chat with Us

Send your inquiry

Choose a different language
Ōlelo Hawaiʻi
Kreyòl ayisyen
bahasa Indonesia
Basa Jawa
Қазақ Тілі
Kurdî (Kurmancî)
latviešu valoda‎
Bahasa Melayu
Af Soomaali
Tiếng Việt
èdè Yorùbá
Current language:English