BREW is complement with J2ME
For wireless network operators, long-term voice services have always been the main source of their income. However, with the popularity of SMS, the huge business opportunities for non-voice value-added services (data applications) have also begun. In order to promote wireless data, it is important to adapt to the preferences and needs of the public market, efficient and general application development, download, billing and custom platforms are critical to breaking through wireless data bottlenecks. Due to the difficulty of application development on mobile phones, experience shows that the software development capability of mobile phone manufacturers, it is difficult to meet the needs of the market, and will also greatly restrict the promotion and popularization of new applications, so wireless data platforms should provide a mechanism. To enable the vast number of third-party software developers to intervene. From the perspective of improving mobile phone user experience, the platform should also have the ability to dynamically load the application, and can be upgraded, and the local storage area can be accessed, and the user can customize the management downloaded application. The platforms currently supported by operators have mainly available J2ME / CLDC / MIDP platforms launched by the Sun Microsystems and the Wireless Binary Runtime Environment (BREW) application platform launched by U.S. Qualcomm. Due to the similarity of J2ME and BREW functions, many industry people have always regarded these two platforms as competitors that are confrontational. In fact, J2ME is a useful supplement to BREW, not its competitors. Specifically, BREW is a complete open superchard consisting of clients, servers, and business model solutions that meet all wireless applications related manufacturers and consumers. In this frame, J2ME is only one subset, in the BREW environment, J2ME can make a better role. QUALCOMM and IBM are portrating IBM J2ME-based virtual machine (WME) to BREW, making Java and BREW two platforms complement. This article is intended to develop two platform system capabilities, client capabilities, server-end capabilities, and comparison of business models, have a competitive wireless data platform strategy. Two platform system capabilities Compare wireless operators grasp data value-added business business opportunities are to choose the appropriate technical platform, providing seamlessly consistent friendly user experience throughout the network, and provides a complete business model, quickly obtaining the advantages of scale economy . In the traditional sense, "standard" value-added data platform solutions are due to loose norms, and various manufacturers 'equipment are different due to hardware and software configuration. The operators' interoperable capacity and roaming ability are greatly reduced, and user satisfaction is also reduced, thus Limited the economic advantages of operators and the cultivation of new business. Therefore, wireless application solutions must be based on global unified standards, it should be independent of hardware and are able to deploy on any network, wireless standard, or mobile device. They must also provide end-to-end system capabilities, providing comprehensive support to discover, purchase, download, and manage application / content mechanisms to create a perfect experience for users. In terms of providing system end-to-end capabilities, BREW and J2ME comparison: From the above comparison, J2ME is difficult to provide a seamless operation of providing full end-to-end, but also supports support by means of third-party software . Therefore, in addition to WME and BREW, mobile Java solution is still far from achieving the applicability of "one write, four seas." The reason is that the MIDP can be defective in the phone design, and the implementation method has changed many. Manufacturers must write new APIs for specific model phones to obtain appropriate performance while also need to load MIDP libraries for specific operators. MIDP does not have application screening, purchase, billing or wireless upgrade, which requires more application discovery and management software, increasing the need for telephone memory, which is also in turn to J2ME initial design ideals. Finally, the phone manufacturer (OEM) needs to equip different virtual machines for different models. The BREW platform is designed to make up for J2ME insufficient.
In the design frame of BREW, the entire J2ME / CLDC / MIDP can be regarded as an extension (WME) of the BREW application, and it is necessary to run on a variety of phones without a separate transplant, and it is not necessary to return the device to the operator can be upgraded or replace. If you use the BREW platform supported virtual machine environment to write Java applications, the popularity of Java applications will be greatly accelerated. This is for the wireless communication industry that is determined today, BREW's support enables developing Java applications to get more market opportunities. In addition to the design, the BREW platform supports all application types (such as ringing music, images, graphics, multimedia, browser plugins, and voice, J2ME or source, etc.) to reduce developers, equipment manufacturers and operators. And deployment costs. This does not require a proprietary platform for each new business. WME makes full use of BREW to function in the telephone service, GPS, SMS, TAPI and other business deep chipset interfaces. The comparison of the two platform client-end capabilities BREW platform and J2ME are simplified the development of mobile applications by using the phone's CPU and providing running real-time environments, so that the programmer implements "one write, four seas." Sex. The client-based platform overcomes the shortcomings of online browsing platforms such as WAP, long delay, and browser need to use separate connections. BREW and J2ME are released from monotonous embedded system programming by providing an abstract layer, and ensuring that the program is not required to modify the code. Although BREW and J2ME solve these problems are different, it is ultimately compatible with each other. J2ME runs in a "sandboxed"? C virtual machine isolated from other parts of the device. This will increase performance cost, but it can support using a simpler Java programming language and provide better security. By rejecting access to the exterior of the sandbox, the sandbox can protect the local CPU from malicious Java applications. Although some people think that the sandbox allows J2ME applications without extensive testing, Japanese operators NTT DoCoMo have suffered network attacks after launching J2ME-based calls. The hacker uses J2ME's email function to send viruses to other calls, resulting in these telephone shutdown, loss of data, and call emergency services. QUALCOMM provides a service that can test all BREW applications for operators: Just before the operator launches application download services, the independent third-party national software test laboratory is fully inspected with vulnerabilities, viruses and quality. In contrast, the J2ME Telephone Manufacturer "Certificate" program does not provide unified standards for all J2ME applications. BREW applications (including J2ME) have to provide better security and reliability due to digital signatures that have been developers, Qualcomm and operators holding a VeriSign certificate. From the occupation of client resources, BREW takes up approximately 150 kB of memory and is tightly integrated with chipsets, providing all download, secure transactions, deep chipsets, and telephone service interfaces, and the necessary functions necessary. The BREW source program is written in the C / C programming language, and BREW can run on a low-end phone whose price is low in memory, which is a J2ME that cannot be comparable because MIDP needs to take up to about 500 kB of storage. Even the most fanatical J2ME fans are also ambitable in the active running speed than MIDlets. In the medium and high-end telephone market, BREW and J2ME can work together, provide the most comprehensive and standard solutions, as well as a wonderful end user experience. Unlike some requirement to use a wired computer to connect a third party based on J2ME-based solutions, BREW's "Mobile Shop" app enables users to quickly find and purchase J2ME and other applications through mobile phones. Customers can decide to apply the memory space you need to occupy, delete the application release memory space and restart the installation work. BREW provides functions such as discovery, purchase, download, billing and debugging required for a complete solution.
