Network Requirements for

BlackBerry 10 devices and 3G+, 4G,

and 4G LTE BlackBerry PlayBook
tablets

Research In Motion (RIM)

January 18, 2013

RIM Confidential – Disclosed Under NDA – Do Not Distribute

RIM Confidential and Proprietary Information

Owner: Research In Motion (RIM)

Audience: Authorized partners only

Document Number: ALL-EXT-PROC-1355954899f

Document Version: 2.2

Security: External document for authorized RIM partners only, Disclosed under NDA

Issue Date: March 23, 2012

Revision Date: January 18, 2013

The contents of this document are proprietary and confidential and are restricted to Research In Motion Limited’s (“RIM”) partners
only. This document is provided for information purposes only, and does not constitute a binding legal agreement. Nothing
contained in this document can be construed as RIM granting a warranty or making a representation. All dates contained in this
document are tentative. This information is shared under Non-Disclosure Agreement and may not be shared with any third party
without the express written consent of RIM.

RIM Confidential – Disclosed Under NDA – Do Not Distribute

Contents

1 Introduction ........................................................................... 4

2 Network Requirements Comparison................................... 5

2.1 Comparison: Primary APN ........................................................ 6
2.2 Comparison: Communications with BlackBerry
Infrastructure .............................................................................. 6
2.3 Comparison: Internet Connectivity and Domain Name
System 7

2.4 Comparison: Content Filtering .................................................. 7

3 BlackBerry 10 IP Networking and Content Handling ........ 8

3.1 Network Access ......................................................................... 8
3.2 Connection and Translation Idle Timeouts .............................. 8

3.3 IPv4 Addressing & IPv4 NAT ..................................................... 8

3.4 IPv6 Addressing ......................................................................... 8

3.5 HTTP Content Caching and Filtering ........................................ 9

3.6 HTTP Header Injection for BlackBerry App World Billing ....... 9

4 BlackBerry 10 Primary APN Requirements ........................ 9

4.1 Primary APN Option A: Multi-tenant Internet APN ................. 10
4.2 Primary APN Option B: New BlackBerry-Exclusive APN ...... 10
RIM Confidential – Disclosed Under NDA – Do Not Distribute 2
 4.3 Primary APN Option C: “blackberry.net” ............................... 11

5 BlackBerry 10 BlackBerry Network and Mobile Network

Interconnectivity Requirements ........................................ 12
5.1 Routing Option A: Internet Connectivity ................................ 13
5.1.1 Optional Enhancement for Internet Connectivity Routing:
Internet Peering......................................................................... 13

5.2 Routing Option B: Existing WAN Solution ............................. 14

5.3 Routing Option C: New WAN Connections ............................ 14

5.3.1 Traditional BlackBerry WAN ............................................................ 14
5.3.2 Private Internet Peering ................................................................... 15

6 BlackBerry 10 Implementation: Next Steps ..................... 15

7 Appendix ............................................................................. 16

RIM Confidential – Disclosed Under NDA – Do Not Distribute 3

1 Introduction
This document describes the network connectivity requirements for BlackBerry® 10 devices and
3G+, 4G, and 4G LTE™ BlackBerry® PlayBook™ tablets. It compares these device
requirements against the existing BlackBerry network configurations, and then describes the
requirements for the BlackBerry 10 devices and 3G+, 4G, and 4G LTE BlackBerry PlayBook
tablets in more detail.

For the purpose of this document, BlackBerry 10 devices and 3G+, 4G, and 4G LTE BlackBerry
PlayBook tablets will be referred to as “BlackBerry 10” devices. BlackBerry devices running
software versions 4.0-7.1 will be referred to as “BlackBerry OS” devices.

IMPORTANT: BlackBerry 10 devices use a different connectivity strategy than BlackBerry

OS devices; therefore, network and system changes are required.

RIM Confidential – Disclosed Under NDA – Do Not Distribute 4

2 Network Requirements Comparison
BlackBerry 10 devices have different network connectivity requirements than BlackBerry OS
devices. The differences are summarized in the table below:

BlackBerry 10 BlackBerry OS

Mobile Network Operator

blackberry.net
Primary APN (MNO) choice, 3 options
Persistent connection to APN
Persistent connection to APN

Transport: WAN connectivity

Communications Transport: WAN or Internet mandatory
with BlackBerry
Infrastructure NAT supported in network path NAT not supported in network
path

Internet
Optional for full-tariff users
Connectivity and Mandatory
Blocked for low-tariff users
DNS services

Optional, very limited Internet

Content Filtering Optional
access

BlackBerry 10 BlackBerry OS
Communications Communications

Primary BlackBerry Alternate

APN APN APN

Content/Traffic
Mgmt
MNO Isolated MNO
PDN
Internet Content/Traffic blackberry.net PDN Multi-Purpose PDN
DNS Management
WAN

BlackBerry Network Internet BlackBerry Network Internet

BlackBerry Services Browsing & Internet On-Demand Connection Persistent Connection

Services

RIM Confidential – Disclosed Under NDA – Do Not Distribute 5

2.1 Comparison: Primary APN
“Primary APN” is the APN that the device will be connected to for the longest duration, and will
transmit/receive the most data across.

BlackBerry OS
BlackBerry OS architecture mandates use of “blackberry.net” as the Primary APN. BlackBerry
OS devices will maintain persistent connections to the blackberry.net APN for purposes of
exchanging data with the BlackBerry Infrastructure. The bulk of the data transferred by
BlackBerry OS devices is to/from the BlackBerry Infrastructure.

BlackBerry 10
BlackBerry 10 architecture allows the MNO to choose the Primary APN. There are three general
options for the Primary APN discussed in section 4 of this document called BlackBerry 10
Primary APN Requirements. BlackBerry 10 devices will maintain persistent connections to the
Primary APN, and will exchange data with both the BlackBerry® Infrastructure, and the Internet
from that APN.

2.2 Comparison: Communications with BlackBerry Infrastructure

The BlackBerry Infrastructure is the collection of servers and services located on the BlackBerry
Network.

Wi-Fi coverage with Internet access is the preferred network path for communications between
BlackBerry devices and the BlackBerry Infrastructure. In cellular-only coverage communications
will be through the Primary APN. To ensure service continuity and quality, the Primary APN
must have highly available connectivity to the BlackBerry Network. Connectivity options for
BlackBerry 10 devices are detailed later in the document.

BlackBerry OS
Network Address Translation (NAT) and Port Address Translation (PAT) support for
communications between BlackBerry OS devices and the BlackBerry Infrastructure depends on
the access network being used for the communications:

Wi-Fi: NAT/PAT is supported in network path

Cellular: NAT/PAT is NOT supported in network path
BlackBerry OS web browsing and other Internet content is requested through the BlackBerry
Infrastructure.

BlackBerry 10
Communications between BlackBerry 10 devices and the BlackBerry Infrastructure can traverse
through NAT and/or PAT.

RIM Confidential – Disclosed Under NDA – Do Not Distribute 6

 BlackBerry 10 web browsing and other Internet content does not traverse the BlackBerry
Infrastructure. BlackBerry 10 devices have much less user traffic (bytes) traversing the
BlackBerry Network/Mobile Network interconnections when compared to BlackBerry OS users.

2.3 Comparison: Internet Connectivity and Domain Name System

BlackBerry 10 and BlackBerry OS devices in Wi-Fi coverage will test for existence of Internet
connectivity and Internet Domain Name System (DNS) services. If both are found, the devices
will prefer the Wi-Fi path for all communications.

Internet connectivity and DNS requirements are different for devices in cellular-only coverage:

BlackBerry 10
Internet connectivity and Internet DNS services are required to be available from the primary
APN used for BlackBerry 10 devices. The majority of the traffic (bytes transferred) by a
BlackBerry 10 device will be to/from the Internet.

BlackBerry OS
Note that if BlackBerry Service Tiering has been/will be implemented, it is highly
recommended that subscribers of the “BIS-Lite” or “BIS-Social” BlackBerry service tiers are
not provided Internet connectivity. Availability of Internet access for these subscription levels
may result in revenue leakage.
Otherwise, availability of Internet connectivity and Internet DNS services on the
blackberry.net APN is optional for BlackBerry OS devices.

2.4 Comparison: Content Filtering

Content filtering is optional and can be added where Internet access is provided.

BlackBerry 10
BlackBerry applications on BlackBerry 10 devices generally retrieve Internet content directly
from the Internet using standard protocols. HTTP and other traffic can be intercepted and
filtered by the MNO’s content filtering systems.
MNO content filtering will not be able to filter BlackBerry® Mobile Fusion traffic, as it is
encrypted between the BlackBerry 10 device and the customer’s BlackBerry Mobile Fusion
server.

BlackBerry OS
BlackBerry applications on BlackBerry OS devices generally request Internet content
through the BlackBerry Infrastructure, as the BlackBerry Infrastructure offers efficiencies
through transcoding, compression and other technologies.
Communications between BlackBerry OS devices and the BlackBerry Infrastructure use a
BlackBerry-proprietary protocol, and cannot be easily filtered by MNO content filtering
systems.

RIM Confidential – Disclosed Under NDA – Do Not Distribute 7

3 BlackBerry 10 IP Networking and Content
Handling
3.1 Network Access
For full data functionality, BlackBerry 10 devices require access to both the Internet and the
BlackBerry network.

In cases where a BlackBerry subscriber is temporarily or permanently not entitled to data

services (voice-only or over data limit), access to both the Internet and the BlackBerry network
must be blocked. This may be accomplished by removing the subscriber’s access to the
Primary APN or by blocking data packets.

3.2 Connection and Translation Idle Timeouts

BlackBerry 10 devices maintain one or more persistent TCP connections to BlackBerry and
Internet services. Connections established to the BlackBerry services have anti-idle functions
where a “keep alive” packet will be transmitted at regular intervals to keep the connection alive.

It is recommended that all idle timeouts in the network path are configured 15 minutes or longer.
These connection/translation timeouts may be found on equipment such as GGSNs/PGWs,
firewalls, and NAT/PAT gateways.

3.3 IPv4 Addressing & IPv4 NAT

All BlackBerry 10 IPv4 communications to the Internet or BlackBerry Network must be sourced
from public/registered IPv4 addresses.

BlackBerry 10 devices may be assigned a private (RFC-1918) IP address(es), and the traffic
passed through a NAT/PAT function where the device’s source address is changed to a
public/registered address before travelling to the Internet or BlackBerry network.

Internet-facing NAT/PAT functions for UDP traffic should utilize endpoint independent mapping
to ensure that Session Traversal Utilities for NAT (STUN) mechanisms function; STUN
mechanisms are used by many peer-to-peer communications, including video conferencing.

3.4 IPv6 Addressing

BlackBerry 10 devices support IPv6 over Wi-Fi, and cCllular. When assigned both an IPv4 and
an IPv6 address, BlackBerry 10 devices will prefer to use IPv6 when possible.

Considering that BlackBerry Network and much of the Internet are IPv4-only, when introducing
IPv6, it is a common and recommended practice to assign the BlackBerry 10 device IPv4 and
IPv6 addresses.
RIM Confidential – Disclosed Under NDA – Do Not Distribute 8
3.5 HTTP Content Caching and Filtering
BlackBerry 10 devices use standard protocols for accessing Internet content. This creates an
opportunity for content caching and/or filtering proxies to be added to the path. These proxies
must be inserted in the path using a “transparent proxy” configuration, where the network
performs the HTTP traffic interception and forwarding to the proxies.

3.6 HTTP Header Injection for BlackBerry App World Billing

In cases where RIM and MNOs have implemented Operator Billing for BlackBerry® App
World™ purchases, HTTP header injection is required. The App World client has a few
configuration options:

1. Transparent proxy on Mobile Network

No proxy/gateway configuration required in App World client
App World client can use Primary APN (default), or be configured to use Alternate
APN for the billing request

2. Configured to make HTTP request through configured HTTP proxy

Multiple HTTP proxy authentication options are supported
App World client can use Primary APN (default), or be configured to use Alternate
APN for the billing request.
Operator must provide proxy network and authentication details to RIM

3. Application configured to make HTTP request through WAP gateway

Multiple WAP gateway authentication options supported
App World client can use Primary APN (default), or be configured to use Alternate
APN for the billing request.
WAP gateway may be accessed via HTTP proxy using CONNECT method
Operator must provide gateway network and authentication details to RIM

4 BlackBerry 10 Primary APN Requirements

The BlackBerry 10 device architecture requires that BlackBerry and Internet data
communications occur through the same Primary APN. This change has been introduced to
simplify provisioning, bearer management and troubleshooting.

There are three options for the Primary APN, all of which are detailed in this section. MNOs may
decide which of the three options is most appropriate by taking into consideration their network,
systems, and business models.

The APN used as the Primary APN must be home-routed in roaming scenarios. Local breakout
on visited network is not supported.

BlackBerry 10 devices maintain a persistent connection to a Primary APN, and one or more
persistent TCP connections to BlackBerry and Internet services. Connections established to the
RIM Confidential – Disclosed Under NDA – Do Not Distribute 9
 BlackBerry services have anti-idle functions where a “keep alive” packet will be transmitted after
15 minutes of idle time. It is recommended that the Primary APN, firewalls, and NAT/PAT
gateways are configured with session/bearer, connection, and translation idle-timeouts of 15
minutes or longer.

Most of the communications (bytes) to/from a BlackBerry 10 device is direct with the Internet.

4.1 Primary APN Option A: Multi-tenant Internet APN

The premise of this option is to use a (new or existing) APN
that also serves non-BlackBerry mobile devices.
Note: This option is preferred by MNOs because of its
operational and subscriber administration benefits.

Implementation Considerations
This option may use an existing APN, which may result in
fewer core network, transport network, billing system, and
user provisioning system changes.

Existing traffic management systems/functions may be

used, such as: content filtering, data rate control, content
insertion/manipulation.

This option potentially allows for common rate-plans/tariffs and SIM swapping between mobile
platforms.

This option limits/eliminates the capability to implement BlackBerry-specific configurations and

policies on the APN.

Usage of the existing BlackBerry Network/Mobile Network WAN solution may be more difficult.
Interconnectivity information is detailed in section 5 of this document.

The MNOs that use dual-IMSI/multi-IMSI technologies for roaming should select a globally
unique APN name to avoid APN name conflicts with “sponsor networks”. Name conflicts can
affect the ability of the “sponsor network” to route roaming PDP Contexts/PDN bearers to “home
network” packet gateways.

4.2 Primary APN Option B: New BlackBerry-Exclusive APN

The premise of this option is to build a new APN, exclusively for BlackBerry 10 devices.

RIM Confidential – Disclosed Under NDA – Do Not Distribute 10

 Implementation Considerations
This option requires creation of a new APN, which
typically will require changes to the core network,
transport network, billing systems, and user provisioning
systems.

This option offers the MNO excellent configuration and

policy control specifically for BlackBerry devices.

This option also allows the ability for the MNO to separate
new mobile devices from existing devices: new APN on
new core network, and blackberry.net APN remains on
legacy network core.

Implementation of content filtering solution and other MNO services on the APN may be
required.

Usage of the existing BlackBerry Network/Mobile Network WAN solution may be more difficult.
Interconnectivity information is detailed in section 5 of this document.

The MNOs that use dual-IMSI/multi-IMSI technologies for roaming should select a globally
unique APN name to avoid APN name conflicts with “sponsor networks”. Name conflicts can
affect the ability of the “sponsor network” to route roaming PDP Contexts/PDN bearers to “home
network” packet gateways.

4.3 Primary APN Option C: “blackberry.net”

The premise of this option is use of the existing blackberry.net APN as the Primary APN for
BlackBerry OS and BlackBerry 10 devices.

Implementation Considerations
This option uses an existing APN. When compared to other
APN options, this option may have fewer core network,
transport network, billing system, and user provisioning
system changes.

For BlackBerry OS devices, the blackberry.net APN already

has high-quality, high-availability connectivity to the
BlackBerry Network. This same connectivity could be used for
BlackBerry 10 devices. Interconnectivity information is
detailed in section 5 of this document.

Beneficially, the blackberry.net APN is already planned and

managed as an always-on APN.

RIM Confidential – Disclosed Under NDA – Do Not Distribute 11

 On most Mobile Networks, blackberry.net APN does not offer Internet connectivity and Internet
DNS services; they will need to be added. Impact of providing BlackBerry OS users Internet
connectivity from the blackberry.net APN must be considered carefully, as some subscription
levels (example: BlackBerry Social subscribers) may not be entitled to Internet access.

Addition of Internet access may also require implementation of content filtering solutions on the
APN.

The MNOs that use dual-IMSI/multi-IMSI technologies for roaming should avoid using the
blackberry.net APN for BlackBerry 10 devices, as the common APN name can affect the ability
of the “sponsor network” to route roaming PDP Contexts/PDN bearers to “home network” packet
gateways.

5 BlackBerry 10 BlackBerry Network and Mobile

Network Interconnectivity Requirements
Wi-Fi coverage with Internet access is the preferred network path for communications between
BlackBerry devices and the BlackBerry Infrastructure.

In cellular-only coverage communications will be through the Primary APN. To ensure service
continuity and quality, the Primary APN must have highly available connectivity to the
BlackBerry Network. There are three options for network connectivity between the Primary APN
and the BlackBerry Network, which are detailed in this section.

All IPv4 traffic from BlackBerry 10 devices bound for the Internet or the BlackBerry Network
must pass through a NAT/PAT function such that the IPv4 addresses assigned by the Primary
APN are changed to public IPv4 addresses that are registered to the MNO. The BlackBerry 10
devices may simultaneous maintain one or more persistent TCP sessions to BlackBerry
Services or Internet Services. Assuming 64,000 connections per IP address, NAT/PAT IP pool
sizing may start with 256 IP addresses for 1,000,000 BlackBerry 10 users, and then adjusted as
usage profile is better understood.

Note that BlackBerry 10 web browsing and other Internet content does not traverse the
BlackBerry Infrastructure. BlackBerry 10 devices have much less user traffic (bytes) traversing
the BlackBerry Network/Mobile Network interconnections when compared to BlackBerry OS
users.

RIM Confidential – Disclosed Under NDA – Do Not Distribute 12

5.1 Routing Option A: Internet Connectivity
The MNO may choose to route all of the BlackBerry Service
traffic via the Internet.

This option may be the easiest to deploy quickly, but there

may be risk to BlackBerry service quality if the Internet quality
(capacity, latency, reliability) between the Mobile Network and
the BlackBerry Network is poor. The MNO is responsible for
evaluating and understanding the quality of the Internet path
between the networks before choosing this option.

All of the BlackBerry Infrastructure IPv4 subnets have been

listed in Appendix 7 of this document titled BlackBerry 10
Infrastructure IP Addresses – Internet Peering. If there are
tariffs where subscribers are not to receive open Internet
access, the MNO may still choose to permit access to the
BlackBerry Infrastructure IP addresses listed in that table.

5.1.1 Optional Enhancement for Internet Connectivity Routing: Internet Peering

An efficient option to improve the quality of the Internet connectivity between the Mobile
Network and the BlackBerry Network is to establish Internet peering between the networks. This
solution will carry all of the Mobile Network’s traffic exchanged with BlackBerry services hosted
on the BlackBerry Network.

There are two types of Internet Peering available: public and private.

Private peering requires a dedicated connection between Mobile Network Internet segment
and the BlackBerry Network Internet segment. See section 5.3.
Public peering requires connectivity from the Mobile Network Internet segment to an Internet
Peering Exchange.

The BlackBerry Network Public Internet Peering Policy is open – the BlackBerry Network will
peer with any network at the exchanges listed below. Additional exchanges will be considered if
there is sufficient interest from MNOs to meet at those exchanges.

The BlackBerry Network has connectivity to the following public peering Internet Exchanges:

AMS-IX, Amsterdam
Equinix Chicago
Equinix Dallas
Equinix Paris

RIM Confidential – Disclosed Under NDA – Do Not Distribute 13

 Private Internet peering between the BlackBerry Network and Mobile Networks is also an option
at the BlackBerry Network Nodes and some BlackBerry data center locations.

MNOs that participate or are interested in Internet peering are encouraged to contact at
peering@rim.com.

5.2 Routing Option B: Existing WAN Solution

Existing BlackBerry Network/Mobile Network interconnects
currently used for BlackBerry OS traffic may also be used for
communications between BlackBerry 10 devices and the
BlackBerry Infrastructure.

The MNO must implement the appropriate routing and

NAT/PAT between the Primary APN and the WAN solution to
establish connectivity between BlackBerry 10 devices and
services.

The BlackBerry Infrastructure IP addresses that should cross

private-line, MPLS, or NSP-based interconnection solution
are listed in Appendix 7 of this document titled BlackBerry 10
BlackBerry Infrastructure IP Addresses – Private WAN
Solution. This configuration will cause BlackBerry® Messenger (BBM™), BlackBerry Mobile
Fusion, BlackBerry® Enterprise Service, and some BlackBerry device configuration traffic to
cross the WAN solution.

The remainder of the BlackBerry and non-BlackBerry traffic will traverse the Internet

5.3 Routing Option C: New WAN Connections

There are two options if the MNO requires new WAN connections for BlackBerry 10:

5.3.1 Traditional BlackBerry WAN Traditional BlackBerry WAN

Redundant Connections from MNO network into a

private, isolated network segment on the BlackBerry
network. PDN
This is the “Traditional BlackBerry WAN” solution Internet Content/Traffic
used for connecting blackberry.net APN to the DNS Management

BlackBerry Network for BlackBerry OS devices.

This solution can only carry limited BlackBerry traffic
types Mobile Network
Operator Internet
BlackBerry Carrier Service Manager (CSM) will
provide the MNO with the “Carrier Connectivity BlackBerry
Internet
Options” document. The document details the Network

available BlackBerry OS WAN connectivity solution Browsing & Internet Services

BlackBerry Services
RIM Confidential – Disclosed Under NDA – Do Not Distribute 14
 options, all of which can be used for BlackBerry 10 traffic.

Private Internet Peer

5.3.2 Private Internet Peering
Implement one or more connections between
Mobile Network Internet segment and BlackBerry
Internet segments.
PDN
This solution will carry all of the Mobile Network’s
traffic exchanged with BlackBerry services hosted Internet Content/Traffic
DNS Management
on the BlackBerry Network.
This solution allows for a single circuit with
Internet failover.
The BlackBerry Network has private peering Mobile Network
Operator Internet
available at the following locations
o Equinix Amsterdam BlackBerry
Internet
Internet
o Equinix Chicago
Browsing & Internet Services
o Equinix Dallas BlackBerry Services

o Equinix Paris

6 BlackBerry 10 Implementation: Next Steps

MNOs must provide the following details to BlackBerry support teams:

APN Details
APN
Credentials
IP addressing
APN Idle timers
Confirm DNS service availability
Rate-plan details (if available)

Connectivity Details
Routing option selected (Existing WAN Solution, New WAN Solution, Internet)
NAT IP Pool

Header-Enrichment Configuration Preferences

Method (Transparent Proxy, HTTP Proxy, WAP Gateway)
Authentication details
Networking details
RIM Confidential – Disclosed Under NDA – Do Not Distribute 15
7 Appendix
BlackBerry 10 Administrative Services
Wi-Fi and URL-Based Zero-Rate
Service IP-Based Zero-Rate Protocol
Hostname
68.171.232.64/27
Device Activation Service das.sl.blackberry.com 93.186.18.64/27 HTTP, HTTPS
173.247.58.64/27
68.171.232.64/27
Control: cse.doc.blackberry.com
End-User Licence Agreement 93.186.18.64/27 HTTP, HTTPS
File: cdn.fs.sl.blackberry.com (Akamai) 173.247.58.64/27
68.171.232.64/27
Control: cse.dcs.blackberry.com
Device Configuration System 93.186.18.64/27 HTTP, HTTPS
File: cdn.fs.sl.blackberry.com (Akamai) 173.247.58.64/27
68.171.232.64/27
Control: cs.sl.blackberry.com
Software Loads 93.186.18.64/27 HTTP, HTTPS
File: cdn.fs.sl.blackberry.com (Akamai) 173.247.58.64/27
BlackBerry ID blackberryid.blackberry.com N/A HTTP, HTTPS
68.171.232.64/27
Contextual Content Collection ccl.blackberry.com 93.186.18.64/27 HTTP, HTTPS
173.247.58.64/27
Network Time time.blackberry.com N/A NTP

GPS Ephemeris Data Server N/A N/A HTTP

RIM Confidential – Disclosed Under NDA – Do Not Distribute

 BlackBerry Infrastructure IP Addresses for BlackBerry 10 Devices
Serving Region RIM Prefixes Direction Description Connection Behavior

216.9.240.176/28, 216.9.240.56/29,
Asia Pacific (AP) 216.9.240.64/28, 68.171.240.80/28, WAN or Internet BlackBerry Registration Transactional
180.149.149.16/28
68.171.240.96/27, 216.9.240.96/27,
BlackBerry Data - PIM, Push, BBM,
AP 216.9.240.128/27, 216.9.240.192/27, WAN or Internet Persistent
Mobile Fusion
180.149.149.96/27, 180.168.204.96/27
United States,
206.53.154.64/28, 206.53.154.80/28,
Canada, Latin
216.9.242.176/29, 68.171.242.240/29, WAN or Internet BlackBerry Registration Transactional
America and
216.9.242.160/28, 68.171.242.160/28
Caribbean (US/CLA)
68.171.242.64/27, 68.171.242.96/27,
216.9.242.128/27, 216.9.242.64/27, BlackBerry Data - PIM, Push, BBM,
US/CLA WAN or Internet Persistent
216.9.242.96/27, 206.53.154.0/27, Mobile Fusion
206.53.154.32/27
Europe 178.239.81.64/27, 93.186.17.176/28,
Middle East 93.186.17.8/29, 93.186.25.8/29, WAN or Internet BlackBerry Registration Transactional
Africa (EMEA) 131.117.168.32/28, 5.100.168.32/28
93.186.17.96/27, 93.186.17.192/27,
93.186.27.160/27, 178.239.81.0/27, BlackBerry Data - PIM, Push, BBM,
EMEA WAN or Internet Persistent
178.239.81.32/27, 131.117.168.96/27, Mobile Fusion
5.100.168.96/27

RIM Confidential – Disclosed Under NDA – Do Not Distribute 17

Legal
This document is provided for informational purposes only. All data and information contained in this document is the confidential
and proprietary information of Research In Motion Limited (RIM), and all rights are expressly reserved. By accepting this document,
you agree that the information contained in this document is for your internal use only, and must not be reproduced or disclosed, in
whole or in part, without the express written consent of RIM. For greater certainty, this document is to be treated as Confidential
Information for the purposes of any Non-Disclosure Agreement between you and RIM.

RIM ON BEHALF OF ITSELF AND ITS AFFILIATES MAKES NO REPRESENTATIONS ABOUT THE SUITABILITY OF THE
INFORMATION OR GRAPHICS CONTAINED IN THIS DOCUMENT FOR ANY PURPOSE. THE CONTENT CONTAINED IN THIS
DOCUMENT, INCLUDING RELATED GRAPHICS, ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. RIM HEREBY
DISCLAIMS ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION, INCLUDING ALL IMPLIED
WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-
INFRINGEMENT. IN NO EVENT SHALL RIM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR
ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF INFORMATION CONTAINED HEREIN. THIS DOCUMENT, INCLUDING ANY GRAPHICS CONTAINED
WITHIN THE DOCUMENT, MAY CONTAIN TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. UPDATES ARE
PERIODICALLY MADE TO THE INFORMATION HEREIN AND RIM MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE
PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED HEREIN AT ANY TIME.
This document may contain references to third party sources of information. Such third party information is not under the control of
RIM, and RIM is not responsible for the contents of any such information, including without limitation the accuracy or any other
aspect of such third party information. The inclusion of any third party information does not imply endorsement or disparagement by
RIM of the third party in any way. RIM shall not be responsible or liable for any part of any dealings that you may have with such
third parties, nor for any inferences that you may draw from such third party information.
© 2012 Research In Motion Limited. All rights reserved. BlackBerry®, RIM®, Research In Motion®, SureType®, SurePress™ and
related trademarks, names and logos are the property of Research In Motion Limited and are registered and/or used in the U.S. and
countries around the world. All other trademarks are the property of their respective owners.

RIM Confidential – Disclosed Under NDA – Do Not Distribute