Push Service

You can use the Push Service to develop a push-enabled app that runs on a BlackBerry device and receives push messages from a Push Initiator. The Push Initiator can deliver up to 8 KB of content (images, text, or audio) to many devices at the same time.

To use the Push Service, you must register with BlackBerry. For more information about registering, visit Push Service in the Platform Services documentation. If you're using the Push Service with BES10 or later, you don't need to register with BlackBerry. For more information, see Push technology for the enterprise.


The architecture diagram below shows a complete Push Service solution that includes the server-side library and the client-side library. The libraries work together to deliver content from the Push Initiator to a push-enabled app.

Architectural diagram showing a complete push solution.

Push Initiator

The Push Initiator is the app that creates request messages using the server-side library and sends them to the push proxy gateway (PPG).

Server-side library

You can use the library of your choice to develop your server-side app. Some possibilities include:

Push Proxy Gateway

The PPG processes push request messages that it receives from the Push Initiator. After the PPG processes a push request message, it sends a response message that communicates the overall result of the push message. The response message contains a result code or a PAP error code.

Client-side library

The BlackBerry 10 Native SDK contains the client-side library. The client-side library provides the Qt-based APIs that the push-enabled app uses to create a PushService object, create and destroy a channel, and receive push messages.

Push-enabled app

The push-enabled app runs on a device and acknowledges the push request to the PPG. The push-enabled app uses the client-side library to create a PushService object, create and destroy a channel, and receive push messages.

What can the Push Service offer?

Increased efficiency

Using the Push Service, you can send content to:

  • Individual users (unicast)
  • Many users (multicast)
  • All of your users (broadcast)

The Push Initiator sends the content when it's available so that data traffic is generated only when necessary.

Runs in the background

The Push Initiator sends content as bandwidth becomes available so that it doesn't interfere with other apps.

Minimal battery drain

The Push Service minimizes the impact on device batteries because the push-enabled app listens in the background for the Push Initiator to send content to it. The app doesn't need to poll the push server for content.

Less coding

The Push Service SDK minimizes the amount of code that you need to write to create a Push Service solution. You can use the APIs in the server-side and client-side libraries to perform common tasks.

Related resources

Platform documentation


Last modified: 2015-06-03

Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus