32.0053G call and event data for the Circuit Switched (CS) domain3GPPCharging managementRelease 1999Telecommunications managementTS
6.1 Tariff and charging administration
The TMN Management Service "Tariff and Charging Administration", as defined in ITU-T M.3200 , covers those management activities related to the charging of service usage including both the data collection process and the administration of charging data within the Network Elements. The relationship between this and other management services and activities is illustrated in figure 1 and described in the following subclauses.
Figure 1: Tariff and charging administration
6.1.1 Subscriber billing
The call and event data collected from the Network Elements is employed to determine the network utilisation charges for the basic and supplementary services utilised by the home subscribers of the PLMN. The charges calculated are then combined with the network access (subscription) charges and billed to those customers directly serviced by the PLMN.
For those subscribers handled by Service Providers, the billing information is employed for both wholesale (Network Operator to Service Provider) and retail (Service Provider to Subscriber) billing. Consequently, having been processed by the PLMN Billing Centre, the call and event data collected from the Network Elements may also be sent to the Service Provider for further processing.
18.104.22.168 Inter-PLMN accounting
Inter-PLMN accounts for roaming traffic are determined in accordance with ITU-T principles (see ITU-T D.93 ) and are settled by means of the Transferred Account Procedure (TAP).
22.214.171.124.1 ‘Visitors’ from other PLMNs
The call and event data collected from the network also includes details of the services employed by visiting (roaming) subscribers. The charges for mobile originated calls (MOCs) and for supplementary services used are calculated as for home subscribers, converted to an agreed accounting currency (e.g. SDRs) and included in the call detail records for the TAP. Even if mobile terminated calls (MTCs) are zero-priced in the visited network (VPLMN), in the absence of ‘optimised routing’ the MTC TAP records are still required by the home network (HPLMN) in order to determine the re-routing charges from the HPLMN to the VPLMN.
The TAP records generated are exchanged with each HPLMN on a regular basis. These TAP records form the basis of the invoice submitted by the VPLMN for the traffic carried.
126.96.36.199.2 ‘Home’ subscribers roaming in other PLMNs
The HPLMN receives TAP records from each VPLMN for services employed by home subscribers whilst roaming. These records are employed to verify the invoices from the VPLMN and to bill the home subscribers for the services used. The charges contained in the TAP records are converted from the accounting currency to the local currency and a handling surcharge (mark-up) is added if required. The TAP records are subsequently passed to the subscriber billing process described in subclause 6.1.1.
188.8.131.52 Fixed network operators and other service providers
The settlement of accounts with the operators of fixed networks for traffic carried, is generally performed on a bulk basis according to the principles outlined in the ITU-T D-series of recommendations.
The traffic accounted for in this manner may include:
– outgoing (Mobile to Land) traffic;
– incoming (Land to Mobile) traffic;
– transit traffic, carried by intermediate networks;
– signalling (MAP/SCCP, CAP/SCCP) traffic e.g. location updates.
Accounting information may also be required for the use of services provided by other operators such as short message service centres and other value added service (VAS) providers.
The charges for the various traffic shares may be determined on the basis of the call records generated by the Network Elements or on the basis of bulk counters (accounting meter records) in the gateway MSCs (GMSCs). For the purpose of the present document, the management information required is assumed to be derived from call and event records. The management of accounting meters is outside the scope of the present document.
6.1.3 Service provision
The call and event data collected from the Network Elements may be used to provide statistical information concerning the use of services, by both home and visiting subscribers, within the network. In addition, the introduction of new services and/ or modifications to the tariffs of existing services may also require the distribution of the appropriate tariff information to the Network Elements for Advice of Charge purposes.
6.1.4 Customer administration
The call data collected from the NEs provides a historic record of subscriber activity and may be used for the handling of customer care enquiries and, in particular, billing complaints. For further details of customer administration services see GSM 12.02 .
6.2 Management of mobile equipment
The TMN Management Service "Management of Mobile Equipment" covers those management activities related to the International Mobile Station Equipment Identity (IMEI) of the mobile station (MS). The main objective of this management service is to administer the data of the Equipment Identity Register (EIR) thereby preventing the access by unauthorised or faulty equipment to the network.
Figure 2 illustrates the exchange of information between the OSF and the appropriate NEFs. The EIR Management Data exchanged takes the form of a number of lists (white, grey and black) which determine whether or not access to the network is permitted for a particular range of IMEIs. For further details concerning the content and use of the white, grey and black lists see GSM 22.016. For full details of the management of these lists see GSM 12.02 .
The Observed IMEI Ticket Data collected from the Network Elements may be used to identify unknown IMEIs, to gather statistics concerning the use of the network by unauthorised mobile stations and to detect the presence of cloned equipment. The present document is concerned with the control of the generation of IMEI tickets together with the collection of those tickets from the NEFs.
Figure 2: Management of mobile equipment