In September last year in an article titled “M2M in the Cloud: a logical development”, I said that, “applying the intrinsic functionality of all-IP networks to M2M tasks will take time, but the constraints are more likely to come on the business side.” Most Tier 1 mobile network operators (MNOs) are finding their feet in the M2M space. Nothing much has changed on that front, other than a lot of window dressing on the Web sites.

The article also included the following schematic. 

Figure 1. A high-level, generic view of a next-generation network and its layered architecture.

I stuck my neck out and said that, “This model is based on connectivity and service enablement, but it triggered the idea of employing the network functionality that goes with the NGN as a de facto M2M platform.”

A key feature of NGN networks is the ability to share system components such as presence and deploy them in different applications, so it should work for MSM. Experts told me I was wrong: I thought they were simply protecting their legacy positions, but now I know that I was partially right and partially wrong.

Look at this schematic, which comes from Nokia Siemens (News - Alert) Networks (NSN). It shows the company’s “M2M software suit for GSM networks” solution that was released on July 8. Now ask yourself if figure 2 doesn’t look a lot like figure 1?

Figure 2. Here have the same four-layers as figure 1. Applications at the top, followed by service enablement and then connectivity, which is the baseline function of cellular networks. The only difference is NSN’s use of the term “smart M2M objects”. In M2M parlance they are known as devices.

Enablement versus Creation

I was definitely wrong when last year I referred to the architecture of figure 1 as an MSM platform because at the time I was thinking of service creation, but figure 2 clearly represents an M2M enablement platform. At the end of the day it’s just a word and as a latter day Humpty Dumpty might say, “When I use words they mean just what I choose them to mean – neither more nor less.”

The key point that NSN’s software suite comprises the delivery mechanisms — e.g. object management, data management as well as charging and billing — that would be provided in a proprietary silo solution. That means that when this seriously smart software (SSS, my acronym) solution simplifies and speeds up the creation process, which will result in more cost-effective applications in future.

Simplification and speeding up comes from the fact that today’s proprietary vertical solutions include functionality that is already in the network, an obvious example is being finding devices, which is done by the HLR (home location register). Let’s keep things simple but not too simple. Now application developers don’t have create the requisite service enablement tasks.

NSN puts it this way: “Providing connectivity for smart objects is the first step.” In addition to facilitating service creation, SSS will: enable MNOs to extend their reach across applications and industries; to expand their role as managed service providers (NSN is also a managed service provider as well as a network equipment provider); and finally allow them to become smart service providers.

Smart network functionality

MNOs have recognized the need to move up the M2M value chain, i.e. do more than merely transport bits, but one can question the added value that comes via partnerships and acquisitions. What do these developments bring to the market? Instead they should have looking at ways of releasing the full potential of their communication infrastructure assets and that is what NSN’s solution delivers.

In addition, it facilitates the transportation of mobile data — makes it more efficient — and also introduces new functionality that will reduces the potential impact that M2M objects will have on GSM networks, which are severely stressed.

The software suite is based on a precise paging feature, invented by NSN, that efficiently reduces the amount of signaling information between M2M mobile stations and base transceiver stations. As a result, GSM operators with M2M service businesses don’t require additional base station sites to accommodate more M2M users. This results in a 70 percent reduction in the M2M signaling load.

In addition, priority class based QoS is included. Urgent M2M transactions such as health and security related information could be given a high QoS class. Other M2M objects that handle non-urgent transactions, which constitute the great majority, would be given a low QoS class. NSN states that this can increase data throughput for other users by 50 percent, and it also allows operators to manage less critical loads better during peak hours.

Use case example

M2M fleet management solutions enable more efficient allocation of taxis and there are other benefits. But locations needed to reported periodically, typically every 10 to 15 seconds, and this adds up to 5720 transactions a month and a transaction payload of up to 200 MB a month. And of course there are many other examples of regular, low-priority transactions. Smart meters will typically transmit every day and this adds up to a monthly payload of more than 0.1 MB per user. Therefore it is clear that NSN’s solution come at the right time and it will be interesting to see when and where it is deployed.

Want to learn more about M2M technologies? Then be sure to check out the M2M Evolution conference, collocated with TMC’s (News - Alert) (News - Alert) ITEXPO West 2011, taking place Sept. 13-15, 2011, in Austin, Texas. The M2M Evolution Conference is for those industry professionals interested in capitalizing on a rapidly growing segment of the telecom industry. The M2M Evolution Conference embraces the any-to-any strategy of the Internet today. Co-sponsored by TMC Partner Crossfire Media, it showcases the solutions, and examines the data strategies and technological requirements that enterprises and carriers need to capitalize on a market segment that is estimated to grow to $300 Billion in the year ahead. To register, click here.