Challenge today

By saying that application is “always on”, we mean that
device is registered to IMS system all the time. Connection needs to be kept
alive by sending periodic “keep alive” messages. Typical examples are e-mail
and different kind of social network services. In addition to keep alive
messages, there will be data sent back and forth between client and servers
(e.g. e-mails).  Typical smart phone users have multiple
services like this. We have all this up and running so what’s the big deal?

Connecting of several always on services has two
major impacts,

1. High signaling loads in HSPA network. High
   signaling load caused by the always-on applications is the hottest topic
   among operators
   and network vendors at the moment
2. Smart phone operation time has become unacceptable. Customers are not satisfied with current smart phone operation times.
   Frequent accessing of WCDMA network consumes too much power

OVI
Notifications
API provides significant improvement for both challenges

The Ovi Notifications API makes it easy to add push
notifications to your applications. With up-to-the-moment, efficient delivery
of lightweight notifications, your apps stay at the forefront of users’
attention. At the same time, your mobile app will optimize bandwidth and
battery use, giving your customers increased functionality without higher
costs.

Key features of Notifications API network in order to reduce network signaling, data
transmission and device power consumption

1. One keep alive message for all the services using Notifications API. This is the most important battery saving feature and provides biggest savings when using Notifications API.
2. Optimized keep alive timer period by new, heuristic keep alive messaging solution
3. Send data only when new data is available in the server
4. Zlib compression algorithm enables lightweight notifications (up-to 1,5kB payload)

Taking
Notifications API into use

Ovi Notifications are enabled within the Qt SDK with simple, intuitive tools. For sending the notifications to
your clients there is an easy to use REST API

Got interested in? Read more and join us to use
Notifications API.

Register to participate in our Notifications API technology
preview

http://www.forum.nokia.com/General/API_Notification.xhtml

How to select correct bearer in order to get fastest connection but not forgetting the device battery life? We have several options available in smartphones and each one of those have their own characteristics.

Nokia has made this easy now in new Symbian^3 and feature will be first time introduced in N8. Nokia introduced One Click Connectivity (OCC) that simply does wisely the bearer selection and allows seamless bearer roaming during active use case e.g.  3G HSPA -> WLAN web browsing if authenticated WLAN access point is available.

One Click Connectivity key focuses on three areas

• Centralized connectivity settings
• Connectivity State Soft-Notes (Unified connectivity UI)
• WLAN usability

All these aim at one goal: Consistent connectivity behavior throughout the platform. OCC is not one new feature but several connectivity related improvements gathered under one umbrella

One of the characteristics is that WLAN is prioritized first in bearer selection when it is available. Not just making connection faster, this gives us great savings in energy consumption. See figure below.

Figure: Relative energy consumption comparison between WLAN, 2G data and 3G data connections. Source: Nokia

It is often advised that WLAN should be turned off in standby if you want to save energy in mobile device. True or False? False. Nokia N8 has a new intelligent, autonomous and yet very effective way to do WLAN scanning in device without sacrificing battery life or connectivity performance. Our internal measurements have proven very low figures (in typical user scenarios we have reached <1mA average over 24h measurement period) that won’t have any impact in practice to device standby times.

For developers Nokia has made this easy. Application developer should connect to network just by asking network connection instead of creating own connection management mechanisms.

Tips and hints:

OCC for developers

Are you planning to implement Qt application with network connection?

How to select correct bearer in order to get fastest connection but not forgetting the device battery life? We have several options available in smartphones and each one of those have their own characteristics.

Nokia has made this easy now in new Symbian^3 and feature will be first time introduced in N8. Nokia introduced One Click Connectivity (OCC) that simply does wisely the bearer selection and allows seamless bearer roaming during active use case e.g.  3G HSPA -> WLAN web browsing if authenticated WLAN access point is available.

One Click Connectivity key focuses on three areas

• Centralized connectivity settings
• Connectivity State Soft-Notes (Unified connectivity UI)
• WLAN usability

All these aim at one goal: Consistent connectivity behavior throughout the platform. OCC is not one new feature but several connectivity related improvements gathered under one umbrella

One of the characteristics is that WLAN is prioritized first in bearer selection when it is available. Not just making connection faster, this gives us great savings in energy consumption. See figure below.

Figure: Relative energy consumption comparison between WLAN, 2G data and 3G data connections. Source: Nokia

It is often advised that WLAN should be turned off in standby if you want to save energy in mobile device. True or False? False. Nokia N8 has a new intelligent, autonomous and yet very effective way to do WLAN scanning in device without sacrificing battery life or connectivity performance. Our internal measurements have proven very low figures (in typical user scenarios we have reached <1mA average over 24h measurement period) that won’t have any impact in practice to device standby times.

For developers Nokia has made this easy. Application developer should connect to network just by asking network connection instead of creating own connection management mechanisms.

Tips and hints:

OCC for developers

Are you planning to implement Qt application with network connection?