- English
Who am I?
I've been working at Nokia for a long time in various positions. Last 3 years in technology marketing with full focus on energy and power consumption technologies and solutions.
Calendar
Recently...
- Nokia Battery Monitor 2.0 Published
- Optimizing the right thing - power consumption breakdowns
- Nokia Reader saves battery
- Notifications API now available for all Qt developers
- Nokia Battery Monitor – blog post part 2/2
- Nokia Battery Monitor – blog post part 1/2
- OVI Notifications API – intelligent way to stay connected to the network
- How to connect network?
- Energy saving tips via practical examples
- Color makes a difference
OVI Notifications API – intelligent way to stay connected to the network
powersave_mode | 29 September, 2010 10:54
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,
- 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
- 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
- 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.
- Optimized keep alive timer period by new, heuristic keep alive messaging solution
- Send data only when new data is available in the server
- 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
Connectivity
|
Next |
Previous |
Comments (2) |
Trackbacks (0)
Comments
Re: OVI Notifications API – intelligent way to stay connected to the network
powersave_mode | 23/11/2010, 11:32
Post edited due to our recent change in software platform strategy. Nokia will fully focus on Qt and HTML5 and that's why Notification API is now fully concentrating to Qt only.
Please read more at http://www.nokia.com/press/press-releases/showpressrelease?newsid=1453894
XMPP
vivainio | 29/09/2010, 12:37
You may wish to explain that it's using XMPP for client connections. The whole technology made little sense to me (as in, what *is* this thing anyway) until someone mentioned the XMPP angle - i.e. this is not about reinventing the wheel, rather it's a new car ;-).