7 Charging

03.573GPPFunctional descriptionMobile Station Application Execution Environment (MExE)Release 1998Stage 2TS

7.1 Generic charging support

The standard GSM/UMTS charging records contain information sufficient to associate bearer usage and SMS/USSD messages with a subscriber.

Third party service providers and/or service providers may define charging regimes for MExE services (e.g. on a MExE or WAP server), however they are outside the scope of standardisation.

7.2 WAP charging support

The WAP protocol suite in [6], with upgrades as identified in this specification, does not specify mechanisms for charging (e.g. charging records) or subscription management. WAP is bearer independent and is running as an application on top of the bearer network. However the WAP architecture suggests that appropriate charging information can be collected in the WAP Gateway; the point of convergence for all WAP traffic.

The WAP security protocol can be used for authentication of the subscriber.

7.3 Java charging support

MExE Java devices do not require any additional specific charging (e.g. charging records) or subscription management. Java usage of network resources is bearer independent and runs as applications on top of the bearer network.