Brew advanced and proficient-3G mobile value-added business operation, customization and development-34-Pre-Installation of applications on mobile phones

Brew pre-installation is a service promotion method led by the operator to pre-provision brew applications on the mobile phone through dynamic pre-installation before the mobile phone leaves the factory. Brew pre-installation is technically divided into dynamic pre-Installation and static pre-installation. Static pre-installation refers to the compilation and release of applications as part of the system software of mobile phone manufacturers. Dynamic Pre-Installation means that an application is not part of the mobile phone system software and can be pre-loaded on the mobile phone through data lines or other methods. The application is included in the BDS app catalog of the carrier.

From the business point of view, brew pre-installation can also be divided into pre-Installation of mobile phone manufacturers and pre-Installation of sales channels. Pre-Installation of mobile phone manufacturers refers to the pre-Installation of mobile phone apps by mobile phone manufacturers before mobile phones enter commercial sales channels. Sales Channel pre-Installation means that after a mobile phone enters the distributor channel, the distributor pre-installs some applications on the mobile phone before selling the mobile phone to the user.

The operator generates and downloads the dynamic pre-installed application package through the management interface of the brew distribution system, and uploads the dynamic pre-installed application package developed by CP/SP to the brew distribution system. Upload the pre-installed application package in the Multi-card mode, and upload the upgrade/renewal application package in the single-card mode as the upgrade package. The application package will be placed in the directory for downloading in the air. Then, the carrier issues the dynamic pre-installation application package to the mobile phone manufacturer or channel for dynamic pre-installation.

The dynamic pre-installation solution is used. After an application is activated by a user, the user's billing information can be generated through the BDS system. Dynamic Pre-installation allows you to perform upgrades in the air or purchase licenses. For specific pre-installation models, dynamic pre-installation applications should include the preinstall pricing method. Currently, dynamic pre-installation supports the following billing modes:

Ø fixed number of days

Ø by fixed date of use

Ø based on actual use time

When the application expires, brew's application manager will prompt you whether to renew the new authorization. After the user permits the application, the mobile store will be started to connect to the normal download billing page of the application on the download server. Developers can provide users with various billing modes and prices on the download billing page.

When generating a pre-installation package for the developer, the carrier can select the following parameter configuration:

Ø application confirmation method (pending): After the application is started on the mobile phone or enters the BREW application manager for the first time, the application will be automatically activated, and application confirmation will be generated and the billing information will be uploaded to the BDS system.

Ø select the Ruim card mode as multi-card mode (any
Sid): You can use different Ruim cards to run the pre-installed application.

Ø Unprotected: allows users to delete the application from their mobile phones.

In principle, all brew applications can be dynamically pre-installed. To ensure program quality and billing, all dynamically pre-installed applications must undergo rigorous third-party testing (generally true brew testing ). After the pre-installation package is generated, the carrier still needs to perform the pre-Installation and billing test before the pre-installation package is officially released.

Generally, an application is activated when a pre-installed mobile phone enters the BREW application manager after the first plug-in card is started or enters the BREW application manager for the first time, at the same time, application validation is generated and 0 billing information is uploaded to the BDS system. If the registration fails, the program will continue to register every time the user uses brew until the registration is successful. During registration, the user cannot see the registration price prompt. When the user starts the application again after the application is used and consumed until the authorization is invalid, the application will prompt the user "the application has expired, whether to purchase". If the user chooses "yes ", the mobile phone will automatically guide the user to enter the BREW application download server, and the corresponding program purchase page will be displayed automatically, the user can continue to use the program after choosing to buy. The continued purchase fee will be associated with the Ruim card on the current host. For example:

If you select monthly subscription when using the card for the next purchase of machine A, the monthly subscription fee for the application on machine A will be associated with the card. When a user uses B card on machine A, the monthly subscription renewal of the application on machine A is still associated with the original a card. A user can still cancel the monthly subscription

If you select monthly subscription for continued purchase of a card on machine B, the monthly subscription fee for B will still be associated with card. In this way, both server a and server B will receive a monthly subscription fee. A and B users can still cancel the monthly subscription.

If you select a non-monthly subscription method when using the-card renewal method, the renewal fee will be associated with the-card. The user can still use the B card to run the application until the Usage Fee expires. When you use B card for renewal, the new renewal fee will be associated with B card.