TADIG

Manage Operators

Operators are defined uniquely by 2 constrains:

  • Each has a Unique TADIG CODE (such as VNMVT, VNMMO, VNMVN, FRAF1, FRAF2…)
  • Each has a unique MCCODE + MNCODE. All and every subscribers belong to that Operator must have the same prefix in its IMSI.
  • For example: VNMVT is 45204XXXXXXXXXX, VNMMO is 45201XXXXXXXXXX.

Beside unique constrains, each Operator has several important characteristics:

  • Thresholds
  • Status for Inbound Voice Roaming
  • Status for Inbound GPRS Roaming
  • List of Chargeable call type
  • Sequence of High Usage Alert Report
  • Sequence of TAP-out file
  • Schedule for Export TAP-out file
  • Status for Outbound Roaming
  • Sequence of expected TAP-in file
  • Sequence of RAP file
  • VAT status.
Chargeable TAP Data

TAP files containing chargeable data must follow the following naming convention: CDxxxxxyyyyySEQNO

where

CD                   identifies the file as containing chargeable data

xxxxx              contains the sender PLMN

yyyyy              contains the recipient PLMN

SEQNO                        contains the File Sequence Number

Store on table TAPEXCLOG.

Test Tap Data

TAP files containing test data must follow the following naming convention: TDxxxxxyyyyySEQNO

where

TD                   identifies the file as containing test data

xxxxx              contains the sender PLMN

yyyyy              contains the recipient PLMN

SEQNO                       contains the File Sequence Number

The TAP Testing Process

  • Process Definition
  • The general TAP Testing Process is shown hereafter:

The TAP Testing Process

Depending on the applicability of the Cloning Procedure, the process described above includes:

The creation of a new original TAP Test File (1.A) based on the Roaming Traffic Test Data or the creation of a “clone” from an existing valid one (1.B).

The validation of the TAP Test File (2) according the applicable validation rules. This should avoid the submission of syntactically wrong TAP Test Files, in which case the process should restart.

The creation of applicable TAP Test Reports (3.A) based on the reports of IREG Tests executed in the VPMN’s Roaming Environment or the creation of “cloned” TAP Test Reports (3.B) from the existing ones.

The submission of the TAP Test File (4) by the VPMN to the HPMN via the TAP Public Interface.

The submission of the TAP Test Reports related to the TAP Test File (5) by the VPMN to the HPMN.

The validation of the TAP Test File received by the HPMN (6) according to the applicable validation rules (e.g. for testing purpose, certain validation rules are irrelevant and should not apply). In case the TAP Test File does not pass the validation process, the HPMN should contact the VPMN and ask for clarifications.

The verification of the TAP Test File at a Call Event Detail level against the received TAP Test Reports (7) with specific reference to the performed TAP Test Cases. In case of any problem, the HPMN should contact the VPMN and ask for clarifications.

The submission of the TAP Testing Completion Certificate (8) by the HPMN to the VPMN in case of successful completion of the Testing Process.

TAP Testing Completion Certificate

The TAP Testing Completion Certificate shall be exchanged to certify the successful execution of the applicable TAP Testing Procedure.

It shall be provided by the each Party, in its quality of HPMN, to the Roaming Partner under test, in its quality of VPMN. The recommended form is given hereafter.

TAP Testing Completion Certificate

This certificate confirms the successful completion of the TAP Testing Procedure

Between

< Party (a) Name>, <Country>, in its quality as VPMN

And

<Party (b) Name>, <Country>, in its quality as HPMN

The tests were completed on   <dd / mm / yyyy>.

Comments:




On behalf of <Party (b) Name>:

Date                                            Name                                                                Signature

___________                    _____________________                                  _____________________

TAP Test Cases (TTC)

Diagram of involved parties

This diagram gives an overview of all involved parties during TAP testing.

Parameters:

PMN(A)

Home PMN of MS1(A) and MS2(A)

PMN(B)

Visited PMN of MS1(A) and MS2(A)

MS1(A), MS2(A)

Mobile Subscribers from HPMN(A) roaming in the VPMN(B)

HMSC

HPMN’s Mobile Switching Centre

VMSC

VPMN’s Mobile Switching Centre

PSTN telephone (B), (B1), (B2)

PMN(B)’s PSTN telephones

PSTN telephone (A)

PMN(A)’s PSTN telephone

PSTN telephone not PMN (A), not PMN (B)

PSTN telephones belonging not to the PMN(A) nor the PMN(B)

The Conditionality of the raised Call Event Details will be as following:

Conditionality

Abbreviation Explanation

Mandatory

M

Must be present.

Conditional C

In general, must be present.  However in certain circumstances the element may not occur because the particular circumstance is not relevant or the information is not available (e.g. from the network).

Optional

O

Does not need to be present.  Inclusion/exclusion of optional elements is at the discretion of the Sender PMN, no specific agreements need to be in place to allow the PMN to include these elements.

Not applicable N

Must NOT be transferred on the TAP.

Further Study F

For further study.