The Open Mobile Alliance (OMA) has just released two significant enabler specifications, one for stopping viruses and worms finding their way onto the mobile handset as it opens up for business on the mobile web and a game client server spec that is supposed to make it easier for handsets to talk to remote games servers.
While the two enabler releases are unrelated, as more complex content, such as games and video find their way more and more onto a phone, the mobile industry doesn’t want to go through the same virus torture that the PC community has gone through, and the security spec includes a content screening process and the management of virus signature updates, just like your average anti-virus software on the PC.
The two specs are now entering their interoperability testing phase to check they work with other OMA components, before they become approved standards.
Both working group programs have been operational for a while, but this is the first time the specifications have gone on release and both are expected to come into common use during 2007.
“As richer content becomes available, we have seen the need for an effective counter-measure to the growing amount of malicious content delivered to handsets,” said Mark Cataldo, Chairman of the OMA Technical Plenary. “Before more dangerous variants, such as self-spreading viruses and worms create havoc on networks and users, the goal of the OMA Client Side Content Screening Framework is to facilitate the development of client-side content screening technologies for the mobile environment.’
The OMA has already had one release of a games specification and this is its second edition which is all about getting games to run on multiple handsets and operating systems, and both behave the same on each of them, and also communicate in a standard way with a remote game server.
This is all about the OMA Game Services Working Group bringing multi-player gaming to mobiles complete with chat, and other shared information like high scores and tournament progress reports.
At the moment gaming on the mobile is a little suspect. Games don’t look the same on each handset, and often games suppliers have to target 200 separate client designs. The bulk of mobile games are written in Java, but always have to assume the lowest common denominator in the hardware in order to work on as wide a number of handsets as possible and until basic issues of interoperability are solved, the games community won’t take off on handsets. This also accounts for the lack of sophistication of games on mobile handsets.
Some would argue that mobile games are doing well enough at present, but that’s just because some decent revenue figures have been enjoyed by a handful of minor players. What’s really needed in mobile games are two things; the ability to simply join in suddenly popular multiplayer games on virtually any phone, using a simple download, and the ability to play it, interacting with mobile owners that are on other handsets, attached to other networks, on devices that have different physical characteristics.
Handsets really lend themselves to games where players interact with one another, using chat and even voice messaging, as they play, with the consumer able to dip in and out of a game as they have spare moments. Provide that to gamers without making them rack up a huge bill and operators will generate a new layer of hard core gamers. But that’s really not happened so far.
Back in February a cluster of mobile game interests including Activision, Digital Chocolate, Electronic Arts, Ideaworks3D, Konami, Microsoft, MontaVista Software, Nokia, Samsung, SK Telecom, Square Enix,
Symbian Limited, Tao Group, and Texas Instruments got together to define a gaming architecture for more complex mobile games.
Their focus was to present a common set of minimum capabilities that game developers can rely upon, making game porting easier and less costly.
The aim is to create an agreed set of hardware specifications that everyone making premium-quality games can aim for, and so cut down the time spent reworking games for different handsets, or at least make it easier.
Now that cry seems to have been taken up by the OMA Gaming services Working Group, as many of the same companies have joined and contributed to this enabler specification.
One way that the OMA seems to be doing this is to standardize the common functions that exist in almost all games
The OMA working group is considering standardized ways of managing the showing of advertisements during games, managing virtual goods ordered during games, standardizing on instant messaging style chat and a standard way of using location information in games. These can then be set up as a set of common services, and the games creators can just focus on game graphics and logic.