mPay is a standards based secured mobile payment framework. It leverages existing industry standards to create an easy and secure way to transact on mobile, without dis-intermediating the Mobile Network Operator (MNO).
The subscriber visits a popular gaming site, due to a standards based arrangement (GAA ID-FF, Identity Federation ), between the MNO and the gaming site, the subscriber gets access the basic free games. The advantage to the subscriber is that she does not need to register nor needs to remember yet another user-id and password. The gaming web site, gains by immediately getting potential access to all the MNO subscribers, which may be in millions. The user is hooked to a game and want to play the next level, which is not free and thus she chooses to pay say Rs 10.
The VAS application calls the Parlay-X gateway of the MNO. After authenticating the the VAS application as per WS-Secuirty profile, the Parlay-X gateway checks the HSS through AAA (3GPP TS 29.109) to ensure that the user has subscribed to be charged for VAS, then uses the AAA procedures (see, section 184.108.40.206 of 3GPP TS 32.299 version 8.7.0 Release 8 ) to charge the user Rs 10 and the Parlay-X Web Service procedure call returns success to the VAS application and the subscriber gains access to the premium gaming content.
The charging specifications are defined in a hierarchical documentation structure [see: 3GPP TS 32.240 ] , The hierarchy is displayed below ( page 7 of TS 32.240)
In the above use-case, to trace the route from Parlay-X function call to Online Charging System (OCS) in the billing domain, refer to figure 4.2 on page 17 of 3GPP TS 32.240 version 8.5.0 Release 8.
The flow is [AF (Application Function)] <--> [ PCRF ( Policy and Charging Rules Function)} <--> [PCEF (Policy and Charging Enforcement Function)] <--> [OCS (Online Charging System)]