5. Push Paradigm
• The data is on the device when the user needs it
• The data is delivered as soon as it is available
• Application is always actively listening for data arrival
• The user is alerted
The user experience is that it just happened,
automatically and reliably
6. Push Paradigm(Contd.)
→ Mail
The original push infrastructure
Enterprise (BlackBerry® Enterprise Server) and BIS-E
→ Enterprise through MDS
Enterprise version of Data Push infrastructure
Supports PAP and MDS push interfaces
→ Web Signals
Push browser icon to home screen (for web sites)
Predecessor to Data Push infrastructure
→ BlackBerry Push Service
Push any data type to a specific, registered java-application or web widget on the device
7. The BlackBerry Push Service
→ Provides transport infrastructure for
Server to Device pushed data
→ Primary focus on consumer applications
Can be used for cross company
applications (Enterprises)
→ Server to Server interface for the push
initiator
Server-side application is required
→ Pushes are initiated on the Server
Utilizes Research In Motions push
infrastructure
→ Sends data to a specified Port on the
device
Client side Java® application required
8. Basic Flow
1. Content provider sends a push request
2. BlackBerry service returns a response
3. BlackBerry service pushes data to an
assigned, specific port on device(s)
4. Device returns response to BlackBerry
service
5. BlackBerry service forwards
acknowledgement to content provider
6. Read notification is returned to the
BlackBerry service
9. Core Competencies
→ Allows up to 8kB payload
→ Dedicated application ports avoid port collisions
→ Uses standard push protocols (WAP PAP 2.2)
→ Supported requests (via HTTPS XML):
Submit Push (to PIN) , Cancel Push
Query for Status
Query for Device Capabilities
10. Core Competencies(Contd.)
→ Response:
Result notification
→ Different submission modes:
Point-to-Point (submit push to single PIN)
Multicast (submit push to list of PINs)
Broadcast (submit to all PINs for a registered application)
→ Developer-controlled expiry time (Push system will
automatically store push requests until expiry time)
11. Core Competencies(Contd.)
→ Supports delivery notifications
→ Developer-set quality of service:
Application (“message reached application” )
Transport (“message reached port on device”)
Fire & Forget (no acknowledgements)
12. Competitive Advantage
• Fast Moving Advantage(FMA)
• Collaborations
• Security of the data
• Ease of use
▫ Designed to quick, intuitive and easy to use
▫ Ease of E-mail, calendar updates & documents and
user data straight to the internet
• BlackBerry Enterprise Server
13. Current issues with RIM
• India, Indonesia, UAE, Saudi Arabia have
blocked BlackBerry services.
• Issues which were raised by governments,
▫ National Security
▫ Decryption of the data
▫ Monitoring the data traffic
14. Solution by RIM to India
• Impossible to break the encrypted data without
encrypted key
• Allowing SOME access of the data
• Share the IP address of BES and the IMEI and PIN
numbers of BlackBerry Mobiles
• Helps in monitoring the data traffic