8 Security Requirements between HPLMN and VPLMN
22.0313G Security3GPPFraud Information Gathering System (FIGS)Service descriptionStage 1TS
It is expected that there will be a need for authentication, data integrity and confidentiality of the communication made between PLMNs.
These issues are for study under other work items within the SMG 10 work programme.
Annex A (normative):
Information transferred by the VPLMN
The reports generated by the VPLMN shall take the form of "call information” records for each monitored subscriber. The content of the call information will depend on the type of event (call start, end etc.). To simplify matters, there will be one format for both MO and MT calls with an MO/MT indicator within the call information to distinguish between the two.
A partial call information will be sent to the HPLMN when there is an mid-call invocation of a supplementary service and when a call in progress has exceeded a defined duration.
Justification is given for the content of the call information message.
Table A.1: Call information content
|
Information |
|
Dialled digits |
|
A subscriber |
|
B subscriber |
|
C subscriber |
|
CGI |
|
IMSI |
|
IMEI |
|
Call Start Time/Date |
|
Call Duration |
|
Call Reference |
|
MO/MT indicator |
|
Visited MSC address |
|
Type of SS event |
|
Type of Basic Service |
The Dialled digits are required as these are an important indicator in deciding if a call is fraudulent or not – certain call destinations are more likely to be called fraudulently than others.
A subscriber can be used to identify the subscriber
B, C subscriber are relevant as some call destinations are more subject to fraud than others.
Cell Global Identifier (CGI) is relevant as some cells in a PLMN are more subject to fraud than others.
The IMSI is used to reference the subscriber.
The IMEI can be used to check if a stolen handset has been used.
The Call Start Time/Date is required so that the call duration can be calculated (if the call end time and not call duration is given at call conclusion) and because the call start time can also an important indicator of fraudulency.
The Call Duration gives the duration of the call at the sending of the partial call information – call duration can be an important indicator of fraudulency. If call end is sent instead, the duration can be calculated using the call start and end times.
The Call Reference is used to reference a particular call.
The MO/MT indicator is required because call charging is different for MO and MT calls.
The Visited MSC address gives the PLMN on which the call was made.
The Type of SS event record is sent if the “call” start is actually the invocation of a supplementary service, e.g. ECT. The Type of SS event is required as this can help to indicate if the mobile is being fraudulently used or not.
The Type of Basic Service indicates whether a teleservice or bearer service is being used and which sort of teleservice or bearer service is being used and is sent if the event is a call and not a supplementary service. The Type of Basic Service is required as this can help to indicate if the mobile station is being fraudulently used or not.
Annex B (normative):
Message flow in FIGS monitoring, normal procedure
Figure B.1: Message flow in FIGS monitoring, normal procedure
Annex C (informative):
Change history
|
Change history GSM 02.31 |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
No Phase 1 version |
|||||||
|
06-1997 |
SMG#22 |
To SMG#22 for information |
1.0.0 |
||||
|
10-1997 |
SMG#23 |
To SMG#23 for approval |
2.0.0 |
||||
|
10-1997 |
SMG#23 |
TS approved by SMG#23 |
2.0.0 |
5.0.0 |
|||
|
03-1998 |
SMG#25 |
The specification was converted to version 7.0.0 because the work item is related to Release 98; version 5.0.0 withdrawn. (SMG#25) |
5.0.0 |
7.0.0 |
|||
|
06-1998 |
SMG#26 |
A001 |
1 |
CR 02.31-A001r1 (correction) approved by SMG#26 |
7.0.0 |
7.1.0 |
|
|
08-1999 |
Publication version |
7.1.0 |
7.1.1 |
||||
|
04-2000 |
Release 1999 publication version |
7.1.1 |
8.0.0 |
||||
|
06-2001 |
ETSI Publication |
8.0.0 |
8.0.1 |
||||
|
Change history 3GPP TS 42.031 |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
03-2001 |
SA#11 |
Upgrade to Release 4 (3GPP numbering) |
02.31 V8.0.0 |
42.031 V4.0.0 |
|||
|
06-2002 |
SA#16 |
Upgrade to Release 5 |
4.0.0 |
5.0.0 |
|||
|
Change history 3GPP TS 22.031 |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
12-2002 |
SA#18 |
Agreed to convert to 3GPP/GSM joint numbering scheme. 42.031 WITHDRAWN. Technically equivalent to 42.031 version 5.0.0 |
42.031 v5.0.0 |
22.031 v5.0.0 |
|||
|
12-2004 |
SA#26 |
– |
– |
– |
Upgrade to Release 6 |
5.0.0 |
6.0.0 |
|
06-2007 |
SA#36 |
– |
– |
– |
Upgrade to Release 7 |
6.0.0 |
7.0.0 |
|
12-2008 |
SA#42 |
– |
– |
– |
Upgrade to Release 8 |
7.0.0 |
8.0.0 |
|
12-2009 |
SA#46 |
– |
– |
– |
Upgrade to Release 9 |
8.0.0 |
9.0.0 |
|
2011-03 |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.0.0 |
10.0.0 |
|
2012-09 |
– |
– |
– |
– |
Update to Rel-11 version (MCC) |
10.0.0 |
11.0.0 |
|
2014-09 |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.0.0 |
12.0.0 |
|
2015-12 |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
||||
|
2017-03 |
– |
– |
– |
– |
Update to Rel-14 version (MCC) |
13.0.0 |
14.0.0 |
|
2018-06 |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
14.0.0 |
15.0.0 |
|
2020-07 |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
15.0.0 |
16.0.0 |
|
2022-03 |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
16.0.0 |
17.0.0 |