BREW application distribution process

Brew has full control over application selection, management, pricing, user usage tracking, and billing through a Secure Enterprise external website. In terms of business model, there are two main types of BREW application distribution: one is the distribution of applications controlled by the operator, and the other is the distribution of typical authentication applications. A typical authentication application is an application that allows developers to encrypt digital signatures for mobile value-added services over the Internet. The applications controlled by the operator require the operator to encrypt the applications using digital signatures. The developer only needs to provide the applications to the operator.

To put it simply, the publishing process of a typical authentication application is as follows: a developer develops an application and submits a true brew test. After passing the true brew test, the developer submits the billing method of the application. Then the carrier can see the application. After the developer and the operator negotiate the price, the operator generates a download directory for the application, and then activates the download directory for the user to see. End users can use the BREW application manager on their mobile phones to browse the application download directory and freely download and use the application (Figure 5-5 ).

 

 

Figure 5-5: Release Process of a typical authentication Application

 

After a user downloads a mobile value-added service, the app download server receives the relevant transaction information and sends it to the brew distribution system. The Brew distribution system converts the related transaction information into the user's billing data information, similar to the CDR in the voice communication service. The carrier generates a user's bill receipt based on the billing data, and charges the application developer based on the negotiation result with the application developer (Figure 5-6 ).

 

 

Figure 5-6: developer's Payment Method

 

As a further service, carriers can generate various reports for developers and related applications. The application usage report can describe the application download and usage, as well as the application transaction analysis on each mobile phone every month. The application sales report summarizes the income of all developers, and billing splitting of extended applications. Application activity level reports can collect statistics on all applications of the carrier, including those on the test system. Based on the XML files that developers can extract, developers can further improve the analysis and research of business intelligence.

As a content delivery system, BDS can not only distribute developers' value-added mobile services, but also distribute mobile value-added services with proprietary intellectual property rights of mobile phone manufacturers or operators (Figure 5-7 and figure 5-8 ), the process is similar. Of course, industrial policy issues are different in different countries.

 

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/wireless_com/archive/2009/09/22/4579475.aspx