Help Center

Local Navigation

Mobile data process flows

Process flow: Requesting BlackBerry Browser content on a BlackBerry device

This diagram shows the components that are described in the following text.
  1. A user requests Internet or intranet content from your organization's content server using the BlackBerry® Browser on a BlackBerry device.
  2. The BlackBerry device sends the request to the BlackBerry® Enterprise Server over port 3101.
  3. The BlackBerry Dispatcher sends the request to the BlackBerry MDS Connection Service over port 3200.
  4. The BlackBerry MDS Connection Service creates an HTTP session for the user and retrieves the requested Internet or intranet content from the content server.

    The BlackBerry MDS Connection Service converts the content so that the user can view it on the BlackBerry device, and sends the content to the BlackBerry Dispatcher over port 3200.

  5. The BlackBerry Dispatcher compresses the content, encrypts it using the device transport key of the BlackBerry device, and sends the encrypted content to the BlackBerry Router.
  6. The BlackBerry Router sends the encrypted content to the wireless network over port 3101.
  7. The wireless network verifies that the PIN belongs to a valid BlackBerry device that is registered with the wireless network and sends the encrypted content to the BlackBerry device.
  8. The BlackBerry device sends a delivery confirmation to the BlackBerry Router, and decrypts and decompresses the content so that the user can view it in the BlackBerry Browser.

    If the BlackBerry MDS Connection Service does not receive a delivery confirmation within the flow control timeout limit, it sends a message to the wireless network to delete the pending content.

Process flow: Requesting BlackBerry Browser content while access control is turned on for the BlackBerry MDS Connection Service

This diagram shows the components that are described in the following text.
  1. A user requests Internet or intranet content from your organization's content server using the BlackBerry® Browser on a BlackBerry device.
  2. The BlackBerry device sends the request to the BlackBerry® Enterprise Server over port 3101.
  3. The BlackBerry Dispatcher sends the request to the BlackBerry MDS Connection Service over port 3200.
  4. The BlackBerry MDS Connection Service checks the BlackBerry Configuration Database to verify whether pull authorization is turned on, and whether the user has permission to pull content from the specified content server.

    If the user does not have permission to pull content from the specified content server, the BlackBerry MDS Connection Service rejects the request and sends an error message to the BlackBerry device.

  5. The BlackBerry MDS Connection Service creates an HTTP session for the user and sends the user’s authentication credentials to the content server. If the user authenticates, the BlackBerry MDS Connection Service sends the HTTP request to the content server. If the user does not authenticate, the BlackBerry Browser displays an "HTTP 403 Error" message, and prompts the user to type the correct credentials.
  6. The BlackBerry MDS Connection Service retrieves the content from the content server, converts it so that the user can view it on the BlackBerry device, and sends the content to the BlackBerry Dispatcher over port 3200.
  7. The BlackBerry Dispatcher compresses the content, encrypts it using the device transport key of the BlackBerry device, and sends the encrypted content to the BlackBerry Router.
  8. The BlackBerry Router sends the encrypted content to the wireless network over port 3101.
  9. The wireless network verifies that the PIN belongs to a valid BlackBerry device that is registered with the wireless network and sends the encrypted content to the BlackBerry device.
  10. The BlackBerry device sends a delivery confirmation to the BlackBerry Router, and decrypts and decompresses the content so that the user can view it in the BlackBerry Browser.

    If the BlackBerry MDS Connection Service does not receive a delivery confirmation within the flow control timeout limit, it sends a message to the wireless network to delete the pending content.

Process flow: Requesting BlackBerry Browser content with two-factor authentication turned on

This diagram shows the components that are described in the following text.
  1. A user requests Internet or intranet content from your organization's content server using the BlackBerry® Browser on a BlackBerry device.
  2. The BlackBerry device sends the request to the BlackBerry® Enterprise Server over port 3101.
  3. The BlackBerry Dispatcher sends the request to the BlackBerry MDS Connection Service over port 3200.
  4. The BlackBerry MDS Connection Service checks whether the user's BlackBerry device is running an authenticated connection that can support the content request.

    If the BlackBerry device is not running an authenticated connection, the BlackBerry MDS Connection Service redirects the user to a login web page. If the user logs in, using an RSA SecurID® user name and passcode, the BlackBerry MDS Connection Service creates a connection to the content server. By default, the BlackBerry device caches the user’s information for 24 hours of activity on the authenticated connection, or 60 minutes of inactivity.

    The BlackBerry MDS Connection Service creates an HTTP session for the user and retrieves the Internet or intranet content from the content server. The BlackBerry MDS Connection Service converts the content so that the user can view it on the BlackBerry device, and sends the content to the BlackBerry Dispatcher over port 3200.

  5. The BlackBerry Dispatcher compresses the content, encrypts it using the device transport key of the BlackBerry device, and sends the encrypted content to the BlackBerry Router.
  6. The BlackBerry Router sends the encrypted content to the wireless network over port 3101.
  7. The wireless network verifies that the PIN belongs to a valid BlackBerry device that is registered with the wireless network and sends the encrypted content to the BlackBerry device.
  8. The BlackBerry device sends a delivery confirmation to the BlackBerry Router, and decrypts and decompresses the content so that the user can view it in the BlackBerry Browser.

    If the BlackBerry MDS Connection Service does not receive a delivery confirmation within the flow control timeout limit, it sends a message to the wireless network to delete the pending content.

Process flow: Pushing application content to a BlackBerry device

This diagram shows the components that are described in the following text.
  1. A push application on an application server or a content server behind your organization's firewall sends an HTTP POST request to a central push server over the listen port for the content server. The default port number is 8080.

    You can define one or more instances of the BlackBerry® MDS Connection Service in a BlackBerry Domain as a central push server. A push application specifies the BlackBerry® Enterprise Server host name and the connection port number that the BlackBerry MDS Connection Service listens on.

  2. The central push server checks the BlackBerry Configuration Database for the following information about the intended recipients of the application content: the PINs that are associated with the user accounts, whether the PINs are enabled for the BlackBerry MDS Connection Service, and the active BlackBerry Enterprise Server instances that the users are located on.

    User accounts that do not appear in the BlackBerry Configuration Database, or that are pending deletion, cannot receive the push content.

    The central push server responds to the push application to acknowledge that it is processing the request, and sends the push content to the BlackBerry MDS Connection Service instances that have active, primary connections to the BlackBerry Enterprise Server instances.

  3. The BlackBerry MDS Connection Service converts the content so that the user can view it on the BlackBerry device, and sends the content to the BlackBerry Dispatcher over port 3200.
  4. The BlackBerry Dispatcher compresses the content, encrypts it using the device transport key of the BlackBerry device, and sends the encrypted content to the BlackBerry Router.
  5. The BlackBerry Router sends the encrypted content to the wireless network over port 3101.

    The wireless network verifies that the PIN belongs to a valid BlackBerry device that is registered with the wireless network, and sends the encrypted content to the BlackBerry device.

  6. The BlackBerry device sends a delivery confirmation to the BlackBerry Router.

    If the BlackBerry MDS Connection Service does not receive a delivery confirmation within the flow control timeout limit, it sends a message to the wireless network to delete the pending content.

  7. The BlackBerry device decrypts and decompresses the content.

    The BlackBerry Application detects the incoming content by listening on a port number that the application developer specified. For example, the BlackBerry® Browser listens for push application connections on port 7874. The application displays the content on the BlackBerry device when the user runs the application.

Process flow: Installing a BlackBerry Java Application on a BlackBerry device over the wireless network

This diagram shows the elements that are described in the following process flow.
  1. A developer creates a BlackBerry® Java® Application using the BlackBerry® Java® Development Environment or another Java authoring tool. The developer produces an application bundle.

    The application bundle contains an .alx file that stores information about the attributes of the BlackBerry Java Application, including the author name, a description of the application, and copyright information.

  2. In the BlackBerry Administration Service, you publish the application bundle to the application repository.
  3. You create a software configuration and add the BlackBerry Java Application to the software configuration. You specify that the application is required, assign an application control policy to the application, and specify wireless delivery to BlackBerry devices.

    You assign the software configuration to a group.

  4. The BlackBerry Administration Service creates a deployment job.

    A deployment job represents the objects that must be sent to each user's BlackBerry device and consists of multiple tasks. Each task manages the delivery of an object (for example, a BlackBerry Java Application, an access control policy, or an IT policy) to a BlackBerry device.

  5. The delivery manager component of the BlackBerry Administration Service receives tasks to send a BlackBerry Java Application to BlackBerry devices.
  6. The BlackBerry Administration Service exports the files for the BlackBerry Java Application to a shared network folder.
  7. The delivery manager converts the tasks into send module commands, queues send module commands into logical groups for each user, and sends the send module commands to the BlackBerry Policy Service. Separate applications are queued in separate groups.
  8. The BlackBerry Policy Service processes the send module commands in the queue in sequence. When the BlackBerry Policy Service processes a group of send module commands, it retrieves the data for the BlackBerry Java Application from the shared network folder, and sends the send module commands with the application data to the BlackBerry Dispatcher.

    If the send module commands are less than 56 KB, the BlackBerry Policy Service sends them in one data packet. If the send module commands exceed 56 KB, the BlackBerry Policy Service sends them in multiple data packets.

  9. The BlackBerry Dispatcher sends the send module commands to the BlackBerry Router.
  10. The BlackBerry Router sends the send module commands to a BlackBerry device over the wireless network.
  11. The BlackBerry device installs the BlackBerry Java Application. The BlackBerry device sends an acknowledgement packet for the BlackBerry Java Application to the BlackBerry Router.
  12. The BlackBerry Router sends the acknowledgement packet to the BlackBerry Dispatcher.
  13. The BlackBerry Dispatcher delivers the acknowledgement packet to the BlackBerry Policy Service.
  14. The BlackBerry Policy Service clears the send module commands for the BlackBerry device from the queue and processes the next group of send module commands that are in the queue.
  15. The BlackBerry Administration Service displays that the BlackBerry Java Application was delivered to the BlackBerry device.

If the BlackBerry device does not receive all of the send module commands within 4 hours, the BlackBerry device sends a failure acknowledgement packet to the BlackBerry Policy Service. The BlackBerry Administration Service detects the failure acknowledgement packet and displays an installation failure message for the BlackBerry device.

Process flow: Installing a BlackBerry MDS Runtime Application on a BlackBerry device over the wireless network

This diagram shows the elements that are described in the following process flow.
  1. A developer creates a BlackBerry® MDS Runtime Application using the latest version of BlackBerry® MDS Studio or the BlackBerry® Plug-in for Microsoft® Visual Studio®. The developer produces an application bundle and publishes it to the BlackBerry MDS Application Repository.
  2. The BlackBerry MDS Application Console displays the application as available for installation in the application directory view.
  3. Using the BlackBerry MDS Application Console, you assign the BlackBerry MDS Runtime Application to the members of a group.
  4. The BlackBerry MDS Application Console sends an installation request to the BlackBerry MDS Integration Service that you assign BlackBerry devices to.
  5. The BlackBerry MDS Integration Service retrieves the files for the BlackBerry MDS Runtime Application from the BlackBerry MDS Application Repository. The BlackBerry MDS Integration Service repackages the files so that they can be sent to the BlackBerry device over the wireless network, and sends an installation request to the BlackBerry MDS Connection Service using the Push Access Protocol.
  6. The BlackBerry MDS Connection Service sends the installation request to the BlackBerry Dispatcher.
  7. The BlackBerry Dispatcher sends the installation request to the BlackBerry Router.
  8. The BlackBerry Router sends the installation request to the BlackBerry device over the wireless network.
  9. The BlackBerry device receives the installation request on the port number that the BlackBerry MDS Runtime uses to listen for incoming messages from the BlackBerry MDS Integration Service.

    If the BlackBerry device does not receive the installation request (for example, if the BlackBerry device is outside of a wireless coverage area), the BlackBerry MDS Integration Service tries to send the request up to two more times before it sends an installation failure message to the BlackBerry MDS Application Console.

  10. The BlackBerry MDS Runtime on the BlackBerry device verifies that the BlackBerry MDS Runtime Application can be installed on the BlackBerry device.

    The BlackBerry MDS Runtime sends a confirmation message to the BlackBerry MDS Integration Service and retrieves the files that are required to install the BlackBerry MDS Runtime Application. The BlackBerry MDS Integration Service sends other information about the application to the BlackBerry device, including identification information, signing information, and the URI version.

    The BlackBerry MDS Runtime installs the BlackBerry MDS Runtime Application on the BlackBerry device and sends a delivery confirmation message to the BlackBerry MDS Integration Service.

    If the BlackBerry MDS Runtime cannot install the BlackBerry MDS Runtime Application on the BlackBerry device, it sends an installation failure message to the BlackBerry MDS Integration Service, which sends the message to the BlackBerry MDS Application Console.

  11. The BlackBerry MDS Integration Service reports the status of the installation to the BlackBerry MDS Application Console.
  12. The BlackBerry MDS Application Console displays that the BlackBerry MDS Runtime Application is installed on the BlackBerry device.

Process flow: Installing a BlackBerry Browser Application on a BlackBerry device over the wireless network

This diagram shows the elements that are described in the following process flow.
  1. A developer creates a BlackBerry® Browser Application using a template. The developer produces an application bundle that contains two .xml files.

    The ApplicationAttributes.xml file contains application attributes. The deployment .xml file contains deployment information and specifies the web address to push to and display on BlackBerry devices.

  2. Using the BlackBerry MDS Application Console, you publish the application bundle to the BlackBerry MDS Application Repository.

    Using the BlackBerry MDS Application Console, you assign a BlackBerry Browser Application to a group.

  3. The BlackBerry MDS Application Console sends an installation message to the BlackBerry MDS Integration Service that BlackBerry devices are assigned to.
  4. The Browser Push Engine on the BlackBerry MDS Integration Service sends the installation message to the BlackBerry MDS Connection Service using Push Access Protocol.
  5. The BlackBerry MDS Connection Service sends the installation message to the BlackBerry Dispatcher.
  6. The BlackBerry Dispatcher sends the installation message to the BlackBerry Router.
  7. The BlackBerry Router sends the installation message to a BlackBerry device over the wireless network.

    The BlackBerry device receives the installation message on the port number that it uses to listen for browser updates.

  8. The BlackBerry Browser Application installs on the BlackBerry device. Depending on the type of BlackBerry Browser Application, one of the following occurs on the BlackBerry device:
    • If the application is a browser channel push application, an "unread" icon displays on the Home screen of the BlackBerry device. After the user clicks the icon to view the web page in the BlackBerry® Browser, the icon becomes a "read" icon.
    • If the application is a browser cache push application, the web page is stored in the cache of the BlackBerry Browser. To access the web page, the user can browse to the web address using the BlackBerry Browser.
    • If the application is a browser message push application, an email message that includes the web address appears in the message list.

The Browser Push Engine on the BlackBerry MDS Integration Service polls the web page that is specified in the BlackBerry Browser Application for changes. The configuration that is specified in the deployment .xml file specifies the frequency of the polling interval. When the Browser Push Engine detects changes to the web page, it pushes a browser update to the BlackBerry device. Depending on the type of BlackBerry Browser Application, the updated web page is displayed through an "unread" icon on the home screen, updated in the BlackBerry Browser cache, or linked to a new message in the messages list on the BlackBerry device.


Was this information helpful? Send us your comments.