[MobileMind]

When defining groups or roles for an OTASL strategy I understand I need to factor in that different carriers from different countries have different policies regarding OTA Firmware and software provision.

1) If a carrier consents, can I do OTA Firmware and software to the multiple European carriers that allow this from the BES using groups or roles to define firmware packages appropriate for specific devices and software bundles appropriate to group membership and work roles to decide who gets what?

2) Or must I ask the Carrier to set a list in the Application centre instead and give the various alx files I want loaded to them so that they appear for my users in each individual carrier there?

3) Or must I arrange some kind of web portal with the European office of my Carrier so that my users can collect firmware updates and new software from there.

Obviously 2) is a lot more work and 3) is far less convenient than 1) . What are peoples experiences here?

[MobileMind]

RIM Literature e.g. deploying Java apps is good on this one.

They give and explain 5 main options so people can just pick one that works for their environment:

• BlackBerry Desktop Software (BlackBerry device connected to a user’s computer)
• BlackBerry Application Web Loader (BlackBerry device connected to a user’s computer)
• Standalone Application Loader, also referred to as Application Loader Lite (BlackBerry device connected to a
user’s computer)
• web browser (wireless download)
• Application Control policies (wireless push)