Issue #2003 - 09
APPLICATION SOLUTIONS &
QUALCOMM Announces Java Technology Support for Mobile Station Modem Chipsets
SAN DIEGO -- March 13, 2003 -- QUALCOMM Incorporated,
pioneer and world leader of Code Division Multiple Access (CDMA) digital wireless technology, today announced an agreement with Sun Microsystems, Inc. to develop and distribute Java™ 2 Platform, Micro Edition (J2ME™Platform) virtual machine technologies.
These J2ME technologies will be compatible with select QUALCOMM CDMA Technologies (QCT) Mobile Station Modem (MSM™) chipsets, the Binary Runtime Environment for Wireless™ (BREW™) Application Programming Interface (BREWapi™) and system software for wireless devices. Support for J2ME will allow preexisting Java applications to run on select QCT MSM chipsets, beginning with members of the 6xxx family of chipset solutions, and will have optimized performance through the use of the MSM's Launchpad™ suite of multimedia and other advanced technologies. Support for the Java runtime environment will also make QCT's chipsets compatible with other Java technology-compliant devices.
"This agreement allows QCT to enable its customers to use exciting new wireless applications from Java developers," said Johan Lodenius, senior vice president of marketing and product management for QUALCOMM CDMA Technologies. "Sun Microsystems' J2ME technology is the ideal foundation to provide our customers with access to the wide variety of Java technology-based applications available today, and provides a platform for ongoing development of new functionality for our MSM solutions."
"Sun is delighted to collaborate with a CDMA leader like QUALCOMM to help enable their wireless vision," said Alan Brenner, vice president of Sun Microsystems, Consumer and Mobile Systems Group. "This agreement represents a new era of cooperation between QUALCOMM and Sun that will broaden the reach of the Java platform, and opens up tremendous opportunities for our customers as well as developers in the wireless data services market."
Along with QUALCOMM's existing development platform, BREWapi, J2ME support will allow QUALCOMM to offer handset manufacturers and developers around the world a broad range of solutions that will enable them to develop state-of-the-art embedded wireless applications more quickly and easily. The J2ME solution from QCT will be built entirely on the MSM chipset's BREWapi software layer. The Java runtime environment can be incorporated into phones in a consistent manner either by being statically loaded into the phone's system software by QCT, or by being dynamically downloaded over the air by carriers into QCT's MSM-enabled handsets.
All members of QUALCOMM's most recently sampled generation of chipsets, the MSM6xxx family, are designed using QUALCOMM's radioOne™ Zero Intermediate Frequency (ZIF) architecture, which eliminates the need for Intermediate Frequency (IF) components. With radioOne technology, MSM6xxx chipsets require less printed-circuit-board area than previous generations and enable reduced time-to-market development and bill-of-material costs.
Members of the MSM6xxx family of solutions also interface with QUALCOMM's Launchpad suite of applications and software, encompassing advanced multimedia, connectivity, position location, user interface and removable storage capabilities. Selected components of the Launchpad are integrated into all of QUALCOMM's MSM chipsets based on the market for which each chip is designed.
MobileInfo Comments and Advisory: We are happy to see Qualcomm
recognizing the need to work together with Sun's Java platform. That
shows maturity of its thinking. Let us use BREW where it fits best and
J2ME for other applications. Now there seems to be a way to use J2ME
applications on BREW handsets. This is good for the customer
community and we always vote for the customers.
Note: This news release may contain
forward-looking statements within the meaning of section 27A of the
Securities Act of 1933 and section 21E of Securities Exchange act of
1934 in USA. Similar provisions exist in other countries. There is no
assurance that the stipulated plans of vendors will be implemented.
MobileInfo does not warrant the authenticity of the information.
Readers should take appropriate caution in developing plans utilizing
these products, services and technology architectures. All
trademarks used in this summary are the property of their respective