What is TAP3?
Roaming is a key feature of GSM, giving consumers seamless same-number contactability in over a hundred countries. Operators exchange call event details on these roaming subscribers.
TAP is the process that allows a visited network operator (VPMN) to send billing records of roaming subscribers to their respective home network operator (HPMN). TAP3 is the latest version of the standard and will enable billing for a host of new services that networks intend to offer their customers.
For more detailed information on TAP3, read the article Tapping the Potential of Roaming by TADIG Chair, Christer Gullstrand.
Additional Service Support
Such services include new Internet driven information services, new levels of fraud and security protection as well as new international prepaid roaming services and much more.
TAP3 Releases
|
|
|
Download Documents |
TAP3 Release |
Implementation Date |
Brief Description |
TD.57 |
TD.58 |
TD.60 |
TD.32 |
3.1 |
4 June 2000 |
Old |
3.5.2 |
- |
3.1.2 |
- |
3.2 |
4 December 2000 |
Old |
3.6.1 |
- |
3.2.0 |
- |
3.2 |
1 February 2001 |
Old |
3.6.2 |
- |
3.2.1 |
- |
RAP1.1 |
1 April 2001 |
Old |
- |
- |
- |
3.4.0 |
3.3 |
1 May 2001 |
Old |
3.7.1 |
- |
- |
- |
| 3.4 |
1 November 2001 |
Old |
3.8.2 |
- |
3.3.1 |
- |
| RAP1.1 |
1 November 2001 |
Old |
- |
- |
- |
3.5.1 |
| 3.9 |
1 May 2002 |
Old |
3.9.0 |
- |
3.9.0
|
- |
RAP1.2 |
1
May 2003 |
Old |
- |
-
|
-
|
3.6.4
|
3.10
|
1
May 2003 |
Old
|
3.10.1 |
-
|
3.10.3
|
-
|
RAP 1.3 |
1 May 2005 |
Old |
- |
- |
- |
3.11 |
3.11.11
|
1 May 2008
|
Current
|
3.11.11 |
1.7
|
3.11.7
|
-
|
RAP 1.4
|
1 May 2008
|
Current
|
- |
-
|
-
|
4.2
|
Current version highlighted in blue
Access to the TAP3 Specification documents can be gained
by completing the required information.
More
on this...
Improved Rejects Handling
In some cases inpidual erroneous call event details are rejected, resulting in loss of revenue to operators. The new Rejects & Returns process deals with this by providing an automated, standardised method for handling erroneous TAP files.
The Home Network will validate incoming TAP transfers and reject call event details that do not conform to the TAP standard or to the terms of the agreement.
The incorrect call event details will be returned to the Visited Network so that valid call event details can be processed in the billing system of the Home Network and be billed to the subscriber in a timely manner.
This will allow the Visited Network to recoup roaming revenue from the Home Network for corrected, resubmitted TAP files and call event details.
Key benefits
Rejects and Returns process includes the ability to:
- Maximise the collection of revenue for both Home Networks and Visited Networks
- Allow the Home Networks to bill their subscribers in a timely manner
- Deliver fewer call event details in the reclaims process allowing for a simpler invoicing process, which could help to facilitate any future net settlement requirement
- Support non-standard validation checks which may have been agreed bilaterally between roaming partners
The implementation of the Rejects & Returns process requires TAP3
For all TAP-related queries, please contact tadig@gsm.org
| 
