The GSM Association M-Services Initiative
The GSM Association M-Services Initiative
By: Richard Weeks
Jan. 1, 2000 12:00 AM
Throughout last year the single most talked about technology was WAP. This exciting new set of standards promised to free us from our desks by enabling us to access content on the Internet through our mobile phones wherever we were and whenever we wanted. The subsequent failure to deliver on this promise to the consumer with any degree of success has been well documented over the past year as, accompanied by what seemed at times to be a complete meltdown in the global telecoms economy, WAP suffered a series of often well-justified attacks and became simply and succinctly known as "crap."
This was unfortunate as WAP actually held - and indeed still does hold - a lot of promise. The problem with early WAP-capable handsets was that they were very consumer unfriendly. Unfriendly to use, unfriendly to look at, and a completely different experience between handsets. Users tended to use their handset's WAP feature once, if at all, before forgetting about it altogether.
The GSM Association, a group whose members include most of the world's GSM operators (see sidebar), realized that something had to be done...fast. Working with their members, they set about developing a series of guidelines that would give WAP a much friendlier consumer face.
WAP failed to excite mass consumer interest for a variety of reasons. These ranged from overenthusiastic hyping by advertisers, to high expectations from users, to dismal "knee-jerk" content offerings from content providers eager to steal the lead in the first-to-market race. Coupled with unintuitive menus, lackluster graphics, slow download speeds, and expensive bills, the reasons for the subsequent backlash, in hindsight, are now painfully apparent.
Looking to revitalize interest in WAP, the GSM Association asked Openwave to come up with a system that would allow GSM operators to provide engaging, fun content to their subscribers. A crucial part of this was to set about developing handsets that would conform to the same set of guidelines, thus ensuring a similar experience cross-network regardless of the handset - something that does not happen easily at present. The Mobile Services initiative (M-Services) was launched on June 13, 2001, and received universal support from GSM carriers and handset manufacturers alike.
M-Services Complement WAP
Although the guidelines and indeed the latest WAP specification provide for multiple language use, it's likely that developers will use WML (the language the WAP handsets understand) for some time to come. Luca Passani, tools development manager for Openwave (EMEA) believes WML will still be around for some time to come. WML is "the only language that has the necessary constructs to provide a decent user experience on a mobile phone," he says. (See Passani's article elsewhere in this issue.) With the still evolving specification, this lead is likely to be maintained.
First and foremost, the guidelines are not a standard designed to replace WAP. When originally announced to the world, the guidelines were indeed misread by many as a replacement for the ailing WAP standard. It was thought that the GSMA had reached the end of their patience and had designed a new standard to take over from WAP. The guidelines were in fact developed to coexist with the current WAP 1.2 standard and furthermore to be future aware for WAP 2.0. However, where WAP will work over GSM, handsets conforming to the guidelines will be explicitly required to support GPRS.
M-Services Uses Open-Source Guidelines
The M-Services guidelines are thus composed of three distinct areas: Graphical User Interface Let's face it. WAP as presented in current handsets is a pretty uninspiring beast - tiny monochrome images and text and nothing else. From a creative perspective, designing compelling content for such a basic display is a monumental effort. The guidelines lay out details for a graphical user interface (GUI) that offers the following graphics support:
The above qualities have been taken from the Openwave Graphical Browser 5.0, which is the first implementation of the guidelines. (Openwave may have helped the GSMA to draw up the guidelines, but is keen to point out their open and nonproprietary nature.) If the spirit of the guidelines is followed though, then this should be a fairly solid indication of how other devices containing M-Services-friendly non-Openwave microbrowsers will appear.
The GUI also contains elements such as pop-up menus, radio buttons, check boxes, push buttons, and horizontal rules to make formatting complicated content as simple as possible.
With 84% of respondents giving a resounding thumbs down to mobile operators' efforts to-date, the operators were accused of being part of the problem rather than the solution. The introduction of M-Services should give beleaguered operators a chance to remedy the situation.
This naturally involves the full cooperation of the carriers and it will come as somewhat of a relief that the majority of carriers worldwide have indicated their full support of the M-Services initiative. One of the more irksome problems that was encountered by developers and content providers was the near impossibility of integrating with carrier billing systems. The M-Services initiative seems to be taking an important first step toward solving this problem.
This is primarily due to the WAP standard's hazy definition of what form the interface on the phone should take. When putting together the WAP standards, the WAP Forum quite reasonably envisaged that WAP microbrowsers could appear in just about any sort of wireless device, not just the familiar mobile phone. However, this left the field wide open for interpretations of how things like forms and navigation worked, leading to all sorts of confusion and eventual recrimination.
Thus the guidelines seek to specify how the display should appear and function, which simultaneously makes them far more attractive to look at, easier to come to grips with, and once you tire of one manufacturer's phone, easy to pick up and use another's.
Handsets by Christmas?
With so many requirements, and given WAP's tortuously slow evolution, you could be forgiven for thinking that all this is some way away. However, many operators and manufacturers have pledged support for the GSMA M-Services guidelines and it was expected that some 12 handsets would be available as early as Christmas.
Here Openwave has a clear advantage. Although the guidelines and supporting intellectual property are freely available to anyone who requires them, Openwave is nearest to market with both conforming handset microbrowsers and the necessary network servers for the interactive portions. Those who pledged to release products to market in time for Christmas may have found that they needed to use Openwave products to achieve their goal. Although Openwave does not generate revenue from use of the microbrowser, they generate revenue from sales of the carrier-grade servers to operators - a key component.
Within WAP phones it's the microbrowser that takes care of the role of displaying and formatting content. Initial versions of the microbrowsers will have only basic support, but should still be much better to look at and easier to use than their current counterparts. Phones that may have hit the shelves for Christmas will support easier entry of data into forms, possibly some color, and better handling of images. As all of the phones will work over GPRS (where available), the browsing experience should be noticeably faster than that which is currently experienced over GSM.
Those that made it out in time for Christmas (if any) are likely to contain the microbrowser developed by Openwave as that's the one that's furthest along the development curve in terms of implementation of the guidelines. A similar situation exists for those who may want to take advantage of the more advanced features that require a server-side support of the guidelines, although this is unlikely to be a pressing requirement until the second quarter of 2002, when more advanced handsets capable of exploiting this level of functionality are released.
John Hoffman, director for technology evolution for the GSM Association, is confident that device manufacturers will be quick to take to M-Services. "Companies such as Siemens, Motorola, Sagem, Samsung, and others have indicated to some of our members that they will be offering devices." He adds, however, that devices expected in time for the Christmas season "may not be as robust as i-mode devices," a reflection of the level of maturity of the Japanese service. Mike Short, VP of BT Wireless, is similarly upbeat and expects demand for new M-Services-compliant devices to be strong.
It's expected that take-up of handsets with these new features will be quite high and that other manufacturers will develop their own M-Services solutions. Due to the nonproprietary nature of the guidelines, these handsets should be much more interoperable than previous ones, though this will require a degree of cooperation between the handset manufacturers and server/gateway suppliers. At this time though, Openwave has a clear advantage and only time will tell what effect this will have on the marketplace.
However, for those involved in providing wireless Internet services over non-GSM networks, the guidelines are unlikely to offer much solace. They were developed to address issues raised by conflicting standards and are applicable to GSM networks only. Although the GSMA has over 500 members in the U.S., the majority of users connect over the rival CDMA network.
The guidelines specify that the network must use GPRS, the high-speed GSM upgrade. Some U.S. network operators intend to deploy the rival technology CDMA2000 1x which will offer similar connectivity speeds to GPRS, but that's completely incompatible with GSM. However, not all of the U.S. is moving toward non-GSM networks as Mark Taguchi, Openwave Europe's director of M-Services points out: "With Deutsche Telekom acquiring Voicestream and Vodafone's presence in the U.S. and DoCoMo's investment in AT&T and moving to GPRS… with M-Services, it shifts the balance toward GPRS and W-CDMA."
Taguchi (please see his article elsewhere in this issue) is particularly excited about the contribution Asian handset manufacturers can make. "Manufacturers from Asia that have not had a big presence in Europe are developing M-Services handsets," he says. The testing for handsets on specific GPRS networks is taking a little longer than expected, but is understandable, since it is new for some of the Asian manufacturers."
Thus, M-Services looks set to further boost GSM as the world's most popular network.
Reader Feedback: Page 1 of 1
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week