Brew advanced and proficient-problems related to Ruim in 98-brew in the 3G mobile value-added business operation, customization and development

Before brew was introduced to China Unicom, brew-based value-added mobile services were all associated with the unique identifier (ESN) on mobile phones to achieve billing and authorization management. After the Ruim card is introduced to the brew mobile phone, the app ownership, purchase information, and authorization are linked to the unique identifier (imsi) provided by the Ruim card. A Ruim card with an imsi identifier can be inserted into different mobile phones, which leads to some unique billing situations.

Brew has added some features in version 2.x for device/card separation. The BDS distribution system also adds monthly charges to better solve the charges generated by downloading the same application to multiple mobile phones using one imsi. These Ruim-enabled features ensure user experience, prevent app piracy, and provide comprehensive billing support.

The most common situations that may cause changes to the mobile phone and Ruim combinations are as follows:

1. If the existing mobile phone is upgraded, the user changes the new mobile phone, which causes the existing Ruim card to be inserted into the new brew mobile phone.

2. The Ruim card is lost, which causes the new Ruim card to be inserted into the existing mobile phone.

3. Send existing mobile phones to friends/family members. This will cause the new Ruim card to be inserted into the existing mobile phone.

4. temporarily lend your phone to a friend or family member, and use your own Ruim card. This will cause the new Ruim card to be inserted into your current phone.

5. Some people hold the Ruim card of the city for every city they often go to so that they do not have to pay for roaming. Some people also hold multiple cards to distinguish between "private" and "public", which causes a mobile phone to use different Ruim cards at different times.

Without manual intervention, it is difficult for brew to distinguish between 2nd and 5th cases.

The ownership of the application and the use records of the carrier distribution system are generally associated with the imsi of the card used by the user when the application is downloaded (if imsi is Sid-subscriber ID ). If you use different Ruim cards to download applications, different applications on the same mobile phone may have different ownership.

Specifically, for pre-installed applications, the app ownership is owned by the first SID/imsi on the mobile phone.

By default, only the card used by the user (the original Sid) can be used to download the application. The monthly subscription application can be started for a limited number of times, and applications with a minute limit. When the application cannot start, the phone will display an error message. If necessary, the carrier may require that only original users can use brew-based mobile value-added services (no matter which authorization method is used) on their mobile phones ). This means that when you start an application, you need to use the Ruim card used to download the application. On a mobile phone, this function is implemented by setting the identifier (dif_sid_validate_all) in the device ID of the mobile phone.