Upload folder using huggingface_hub
Browse filesThis view is limited to 50 files because it contains too many changes. See raw diff
- files/AID/AID.02 2.1/doc.md +0 -0
- files/AID/AID.02 2.1/images/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg +3 -0
- files/AID/AID.02 2.1/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg +3 -0
- files/AID/AID.02 2.1/images/26d664119ad25250780f554633444e54_img.jpg +3 -0
- files/AID/AID.02 2.1/images/27b06ec9f42b5d727a2630f61a5f1861_img.jpg +3 -0
- files/AID/AID.02 2.1/images/30a26f2d17ca95672702bf50fb4f0242_img.jpg +3 -0
- files/AID/AID.02 2.1/images/35a7554182eb055209552843f341a1ae_img.jpg +3 -0
- files/AID/AID.02 2.1/images/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg +3 -0
- files/AID/AID.02 2.1/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg +3 -0
- files/AID/AID.02 2.1/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg +3 -0
- files/AID/AID.02 2.1/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg +3 -0
- files/AID/AID.02 2.1/images/9e8ebf03cae78f4f81b697548c2d7250_img.jpg +3 -0
- files/AID/AID.02 2.1/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg +3 -0
- files/AID/AID.02 2.1/images/b5335262987c819d7f71ce40f99cb71b_img.jpg +3 -0
- files/AID/AID.02 2.1/images/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg +3 -0
- files/AID/AID.02 2.1/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg +3 -0
- files/AID/AID.02 2.1/images/dd5771673aececa53d42ece89218299d_img.jpg +3 -0
- files/AID/AID.02 2.1/images/df82d77a0d2637cbf2da9ea920a554fa_img.jpg +3 -0
- files/AID/AID.02 2.1/images/e394c2b5c61344f6a12397f430086072_img.jpg +3 -0
- files/AID/AID.02 2.1/images/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg +3 -0
- files/AID/AiD.02 v1.1/doc.md +0 -0
- files/AID/AiD.02 v1.1/images/27b06ec9f42b5d727a2630f61a5f1861_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/2cde062fd82833415971a8bd1a2cafab_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/30a26f2d17ca95672702bf50fb4f0242_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/32acdaad6c921e80fd17e42562858b80_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/35a7554182eb055209552843f341a1ae_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/366a77fdefb0097b3289b4a011911390_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/552328a9daaf3bc0069424b500025880_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/5d76c2e9976aaf97001ee189908830fb_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/90ddb84c323b956e2d50a54d3f870566_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/e9b43ac020435f8121e8592f31afdc52_img.jpg +3 -0
- files/AID/AiD.02 v1.1/images/fb4274c4b7882a4059103f1dbca9b111_img.jpg +3 -0
- files/FASG/FS.01 v1.1/doc.md +471 -0
- files/FASG/FS.01 v1.1/images/562f471e8153729557e6a4ee6343c32c_img.jpg +3 -0
- files/FASG/FS.01 v1.1/images/64662465bba247703fdec49c8f3309f9_img.jpg +3 -0
- files/FASG/FS.01 v1.1/images/990567efebf979be51f56d1150012c9d_img.jpg +3 -0
- files/FASG/FS.01 v1.1/images/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg +3 -0
- files/FASG/FS.01 v1.1/images/a738993919a50143787084ee7ce6e2f2_img.jpg +3 -0
- files/FASG/FS.01 v1.1/images/a7d78d22e465dea388b31d0739f9d0cd_img.jpg +3 -0
- files/FASG/FS.01 v1.1/images/e394c2b5c61344f6a12397f430086072_img.jpg +3 -0
- files/FASG/FS.01 v1.1/images/e9314c83043183351ed74908e9bf2f90_img.jpg +3 -0
- files/FASG/FS.01 v1.1/images/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg +3 -0
- files/FASG/FS.13 Network Equipment Security Assurance Scheme - Framework/doc.md +0 -0
- files/FASG/FS.13 Network Equipment Security Assurance Scheme - Framework/images/007b053fe94a8348f75128a584503fd0_img.jpg +3 -0
- files/FASG/FS.13 Network Equipment Security Assurance Scheme - Framework/images/0c08e48c08f96934cd6bc6911f3069dc_img.jpg +3 -0
files/AID/AID.02 2.1/doc.md
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
files/AID/AID.02 2.1/images/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/26d664119ad25250780f554633444e54_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/30a26f2d17ca95672702bf50fb4f0242_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/35a7554182eb055209552843f341a1ae_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/9e8ebf03cae78f4f81b697548c2d7250_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/b5335262987c819d7f71ce40f99cb71b_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/dd5771673aececa53d42ece89218299d_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/e394c2b5c61344f6a12397f430086072_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AID.02 2.1/images/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/doc.md
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
files/AID/AiD.02 v1.1/images/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/2cde062fd82833415971a8bd1a2cafab_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/30a26f2d17ca95672702bf50fb4f0242_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/32acdaad6c921e80fd17e42562858b80_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/35a7554182eb055209552843f341a1ae_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/366a77fdefb0097b3289b4a011911390_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/552328a9daaf3bc0069424b500025880_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/5d76c2e9976aaf97001ee189908830fb_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/90ddb84c323b956e2d50a54d3f870566_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/e9b43ac020435f8121e8592f31afdc52_img.jpg
ADDED
|
Git LFS Details
|
files/AID/AiD.02 v1.1/images/fb4274c4b7882a4059103f1dbca9b111_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.01 v1.1/doc.md
ADDED
|
@@ -0,0 +1,471 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+

|
| 4 |
+
|
| 5 |
+
The GSMA logo is displayed in a bold, red, sans-serif font. The letters 'GSMA' are stylized, with the 'G' and 'S' connected at the top by a single horizontal bar.
|
| 6 |
+
|
| 7 |
+
GSMA logo
|
| 8 |
+
|
| 9 |
+
# Use of SIM Boxes to bypass interconnect communicationsVersion 1.121 April 2023
|
| 10 |
+
|
| 11 |
+
###### --- Security Classification: Non-confidential
|
| 12 |
+
|
| 13 |
+
Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association.
|
| 14 |
+
|
| 15 |
+
## Copyright Notice
|
| 16 |
+
|
| 17 |
+
Copyright © 2015 GSM Association
|
| 18 |
+
|
| 19 |
+
## Disclaimer
|
| 20 |
+
|
| 21 |
+
The GSM Association ("Association") makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice.
|
| 22 |
+
|
| 23 |
+
## Antitrust Notice
|
| 24 |
+
|
| 25 |
+
The information contained herein is in full compliance with the GSM Association's antitrust compliance policy.
|
| 26 |
+
|
| 27 |
+
## Table of Contents
|
| 28 |
+
|
| 29 |
+
| | | |
|
| 30 |
+
|----------------|---------------------------------------------------------------------|-----------|
|
| 31 |
+
| <b>1</b> | <b>Introduction</b> | <b>4</b> |
|
| 32 |
+
| <b>2</b> | <b>Description of SIM Boxes</b> | <b>4</b> |
|
| 33 |
+
| 2.1 | Introduction – Original purpose of GSM Gateways (SIM Boxes) | 4 |
|
| 34 |
+
| 2.2 | On-net Bypass | 6 |
|
| 35 |
+
| 2.3 | Off-net Bypass | 7 |
|
| 36 |
+
| 2.4 | Leaky PBX | 8 |
|
| 37 |
+
| 2.5 | International Off-net Bypass | 9 |
|
| 38 |
+
| <b>2.6</b> | <b>SMS bypass scenario</b> | <b>10</b> |
|
| 39 |
+
| <b>3</b> | <b>Impact on Radio and Network Planning</b> | <b>10</b> |
|
| 40 |
+
| 3.1 | Inefficiency of Radio planning | 10 |
|
| 41 |
+
| 3.2 | Network Planning and Operation | 11 |
|
| 42 |
+
| <b>4</b> | <b>Consumer Impact</b> | <b>11</b> |
|
| 43 |
+
| 4.1 | Detriment Due to Non-delivery of Signalling Data | 11 |
|
| 44 |
+
| 4.2 | Inbound roamers not reachable | 11 |
|
| 45 |
+
| 4.3 | Service Disturbance | 12 |
|
| 46 |
+
| 4.4 | Ability of mobile customers near SIM Boxes to make or receive calls | 13 |
|
| 47 |
+
| 4.5 | Lost Calls and Call Routing Problems | 13 |
|
| 48 |
+
| 4.6 | Increased Call Set-up Time | 13 |
|
| 49 |
+
| 4.7 | Deterioration in Voice Quality | 14 |
|
| 50 |
+
| 4.8 | Privacy Issues | 14 |
|
| 51 |
+
| <b>5</b> | <b>License obligations and other legal issues</b> | <b>14</b> |
|
| 52 |
+
| <b>6</b> | <b>Fraudulent Revenue Losses Caused by SIM Boxes</b> | <b>14</b> |
|
| 53 |
+
| 6.1 | Service Revenue | 14 |
|
| 54 |
+
| 6.2 | Radio Investment | 14 |
|
| 55 |
+
| 6.3 | Cost of Sales | 15 |
|
| 56 |
+
| <b>7</b> | <b>Mechanisms to Detect SIM Boxes</b> | <b>15</b> |
|
| 57 |
+
| 7.1 | Manual testing | 15 |
|
| 58 |
+
| 7.2 | Passive detection | 15 |
|
| 59 |
+
| 7.3 | Active detection | 15 |
|
| 60 |
+
| 7.4 | Combination of detection mechanisms | 16 |
|
| 61 |
+
| <b>8</b> | <b>Evolutions in SIM Box bypassing</b> | <b>16</b> |
|
| 62 |
+
| 8.1 | Human behaviour simulation | 16 |
|
| 63 |
+
| 8.2 | Automatic SIM replacement | 16 |
|
| 64 |
+
| 8.3 | Moving equipment | 16 |
|
| 65 |
+
| 8.4 | Multiplexers | 16 |
|
| 66 |
+
| 8.5 | Time Windows | 17 |
|
| 67 |
+
| 8.6 | New IMEI send with every new SIM card/call | 17 |
|
| 68 |
+
| 8.7 | Subscription Fraud | 17 |
|
| 69 |
+
| <b>9</b> | <b>Summary and Recommendations</b> | <b>17</b> |
|
| 70 |
+
| <b>Annex A</b> | <b>Document Management</b> | <b>19</b> |
|
| 71 |
+
| A.1 | Document History | 19 |
|
| 72 |
+
| | Other Information | 19 |
|
| 73 |
+
|
| 74 |
+
# 1 Introduction
|
| 75 |
+
|
| 76 |
+
SIM Boxes (also known as GSM Gateways), are used to bypass the regular interconnect traffic towards mobile operators affecting the quality that customers experience. SIM Boxes have a major impact on the network quality, perceived by end-customers and on the traffic flows of mobile operators for termination of international traffic.
|
| 77 |
+
|
| 78 |
+
Mobile operators in different countries worldwide still suffer from high amounts of bypassed calls. In certain countries where mobile operators are taking actions against this issue for many years, the problem is under control. While in other countries, bypass issues are still increasing. Although the GSM Association has given a lot of attention in the past years towards SIM Boxes and SIM Box Detection, it needs to be noted that the problem is still highly affecting mobile networks, and only with rapid action of the mobile operators against SIM Boxes, the issues can be challenged.
|
| 79 |
+
|
| 80 |
+
In this document, GSMA defines the different forms of bypass via SIM Boxes. The impact SIM Boxes have on the traffic flows of mobile operators for termination of international traffic, the radio and network planning of mobile operators, as well as the quality degradations consumers perceive are presented. The document continues with a description of the mechanisms to detect SIM Boxes and some information on the evolutions in bypassing.
|
| 81 |
+
|
| 82 |
+
The figures and charts in this document are examples and for presentation purposes only.
|
| 83 |
+
|
| 84 |
+
**Note:** There is an IMQ General Document available that presents the Business Case for implementing the prevention of the GSMA Gateways abuse (SIM boxes): [IMQ Gen Doc 005](#).
|
| 85 |
+
|
| 86 |
+
# 2 Description of SIM Boxes
|
| 87 |
+
|
| 88 |
+
## 2.1 Introduction – Original purpose of GSM Gateways (SIM Boxes)
|
| 89 |
+
|
| 90 |
+
GSM Gateways are devices whose original purpose was to allow fixed line telephones to interface with mobile networks. The purpose is to provide fix telephone coverage in areas where no fixed coverage is available or in areas with temporary capacity problems due to different reasons (temporary headquarters, buildings construction, special events, and so on). The fixed line telephones are connected to the device that contains one or more SIMs. The SIM Box then connects calls made by the fixed line telephones to the GSM network using the SIMs contained within. Today SIM Boxes can interface via VoIP, PRI, fixed line, E1 and other means to collect the incoming traffic.
|
| 91 |
+
|
| 92 |
+

|
| 93 |
+
|
| 94 |
+
The diagram, titled "SIM Box 'legal' use", illustrates a specific network configuration. On the left, a cluster of blue buildings represents an office or enterprise environment with "Fix lines". These lines are connected via "Local Wire connectivity" to a "SIM Box" device. The SIM Box is shown with two green SIM cards inserted. An arrow indicates the signal path from the SIM Box to a mobile base station (cell tower) icon. From the tower, another arrow points to a green cloud labeled "Mobile Network".
|
| 95 |
+
|
| 96 |
+
Diagram titled 'SIM Box 'legal' use' showing call routing from fixed lines through a SIM Box to a mobile network.
|
| 97 |
+
|
| 98 |
+
**Figure 1: Sim Box legal use**
|
| 99 |
+
|
| 100 |
+
Standard call routing between networks is shown in the figure below. This is the classical way of transmitting calls that maximises network efficiencies and call quality through industry standardised interfaces and processes. It is also consistent with standard international and national regulatory obligations relating to network interconnection.
|
| 101 |
+
|
| 102 |
+

|
| 103 |
+
|
| 104 |
+
The diagram, titled "Standard Interconnect Scenario", depicts the conventional path for cross-network calls. On the left, icons for a mobile phone and a landline handset represent "Any origin". Arrows from these icons lead into a blue cloud labeled "Other Network". A central arrow labeled "Interconnect Path" connects the "Other Network" cloud to a green cloud labeled "Mobile Network". Below each network cloud is a mobile base station icon. Finally, an arrow from the "Mobile Network" cloud points to a destination mobile phone icon on the right.
|
| 105 |
+
|
| 106 |
+
Diagram titled 'Standard Interconnect Scenario' showing call routing from an external origin through an 'Other Network' to a 'Mobile Network'.
|
| 107 |
+
|
| 108 |
+
**Figure 2: Interconnect Scenario**
|
| 109 |
+
|
| 110 |
+
The set-up of calls via a SIM Box is shown below. In this case, calls from another network are made to appear as mobile-to-mobile calls on the GSM network. This is likely to create significant quality issues for mobile networks. Especially since such arrangements are established without the prior knowledge of the mobile network operator.
|
| 111 |
+
|
| 112 |
+

|
| 113 |
+
|
| 114 |
+
The diagram illustrates the 'SIM Box basic scenario'. At the top, a box contains the title 'SIM Box basic scenario'. Below it, two clouds represent 'Other Network' (blue) and 'Mobile Network' (green). A phone icon on the left points to the 'Other Network' cloud with the label 'Any origin'. A dashed arrow labeled 'Avoided Interconnect path' points from the 'Other Network' cloud to the 'Mobile Network' cloud. Below the clouds, a large oval labeled 'BYPASS' contains a 'Transmission path, e.g. VoIP' leading to a 'SIM Box' (represented by a device icon with two SIM cards). From the 'SIM Box', a dashed green arrow labeled 'On-net call' points to a phone icon on the right, which is connected to the 'Mobile Network' cloud via a base station icon. At the bottom, a green box contains the text: 'Each SIM card is seen by the Mobile Operator as a 'single retail customer''.
|
| 115 |
+
|
| 116 |
+
Diagram titled 'SIM Box basic scenario' showing call routing from an 'Other Network' through a 'BYPASS' path (Transmission path, e.g. VoIP) to a 'SIM Box', which then connects to a 'Mobile Network' via an 'On-net call' path. A dashed line indicates the 'Avoided Interconnect path'. A note at the bottom states: 'Each SIM card is seen by the Mobile Operator as a 'single retail customer''.
|
| 117 |
+
|
| 118 |
+
**Figure 3: Sim Box basic scenario**
|
| 119 |
+
|
| 120 |
+
Some networks allow corporate customers this type of access to provide direct connection with the customer's private network, creating a sort of virtual private network (**Note:** corporate customers do not have an Operator's Licence and may not be able to ask for Interconnection to the mobile network). In such cases, services are normally restricted to closed user groups under the control and knowledge of the mobile operators. Due to these restrictions, quality losses are minimised.
|
| 121 |
+
|
| 122 |
+
However, SIM Boxes are increasingly being used by national and international voice carriers via third parties or re-sellers, to bypass traffic. These may not have an operator's licence to route calls to GSM networks or even use subscription fraud.
|
| 123 |
+
|
| 124 |
+
Some vendors of GSM Gateway equipment are now specialised in the equipment used for this kind of bypass traffic, in order to optimize the use of SIM Boxes worldwide. More information about the specific features of these installations can be found under Chapter 8.
|
| 125 |
+
|
| 126 |
+
Mobile operators are unaware of the deployment of such SIM Boxes, resulting in unpredicted network behaviour and quality problems. With this type of connection, customers may be denied the normal industry standard quality guarantees expected of public networks.
|
| 127 |
+
|
| 128 |
+
## 2.2 On-net Bypass
|
| 129 |
+
|
| 130 |
+
Bypassers use the best on-net retail calling rates (for example promotions to attract new customers) to terminate calls via a SIM Box instead of via the regular interconnect. The way a bypasser uses these local promotions to terminate international traffic is illustrated in following example:
|
| 131 |
+
|
| 132 |
+

|
| 133 |
+
|
| 134 |
+
```
|
| 135 |
+
|
| 136 |
+
graph LR
|
| 137 |
+
subgraph "Other Network"
|
| 138 |
+
Origin((Any origin))
|
| 139 |
+
Cloud1[Other Network]
|
| 140 |
+
end
|
| 141 |
+
subgraph "Mobile Network"
|
| 142 |
+
Cloud2[Mobile Network]
|
| 143 |
+
Antenna1(( ))
|
| 144 |
+
Antenna2(( ))
|
| 145 |
+
Phone(( ))
|
| 146 |
+
end
|
| 147 |
+
Origin --> Cloud1
|
| 148 |
+
Cloud1 -- "Interconnect path = X" --> Cloud2
|
| 149 |
+
Cloud1 -- "Transmission path, e.g. VoIP" --> SIMBox[SIM Box]
|
| 150 |
+
SIMBox -- "On-net calls = Y" --> Cloud2
|
| 151 |
+
Cloud2 --> Antenna1
|
| 152 |
+
Cloud2 --> Antenna2
|
| 153 |
+
Antenna2 -- "On-net call" --> Phone
|
| 154 |
+
SIMBox -.-> Phone
|
| 155 |
+
|
| 156 |
+
```
|
| 157 |
+
|
| 158 |
+
The diagram titled "ON NET BYPASS" shows two primary network clouds: "Other Network" on the left and "Mobile Network" on the right. A call originating from "Any origin" (represented by a mobile phone icon) enters the "Other Network". There are two paths to the "Mobile Network":
|
| 159 |
+
1. A direct dashed arrow labeled "Interconnect path = X".
|
| 160 |
+
2. An alternative path where traffic goes from the "Other Network" through a "Transmission path, e.g. VoIP" to a "SIM Box". From the SIM Box, an arrow labeled "On-net calls = Y" points to the "Mobile Network".
|
| 161 |
+
Inside the "Mobile Network", there are two cell tower icons and a mobile phone icon. A dashed green arrow labeled "On-net call" connects the SIM Box to the final mobile phone. A note at the bottom left states "Y is less than X".
|
| 162 |
+
|
| 163 |
+
Diagram illustrating 'ON NET BYPASS' where international traffic is routed through a SIM Box to appear as local on-net calls.
|
| 164 |
+
|
| 165 |
+
**Figure 4: Bypass On Net**
|
| 166 |
+
|
| 167 |
+
In the above example, the rate for termination of international traffic equals $X$ . The *other network* on the left, is sending the traffic via an alternative interconnect path, namely a SIM Box towards the *mobile network* (the SIM Boxer will stay anonymous, so the *other network* will often send the traffic through a third party, without the knowledge that it is a SIM Box).
|
| 168 |
+
|
| 169 |
+
If traffic is sent via the alternative path, it looks for the mobile operator like two regular customers are making an on-net local call on his network. Instead of $X$ , the International Termination Rate, the applicable rate will be $Y$ . ( $Y$ equals a local tariff, subject to specific promotions and conditions that are applicable to the retail market, not to the interconnect market).
|
| 170 |
+
|
| 171 |
+
If SIM Boxes are in operation, a shift occurs from minutes terminating at the termination rate for international traffic ( $X$ ) to minutes at on-net retail tariffs ( $Y$ ). The charge per minute for on-net calls will by definition be lower than the termination rate ( $Y$ is less than $X$ ) otherwise the SIM Box phenomenon would not occur.
|
| 172 |
+
|
| 173 |
+
## 2.3 Off-net Bypass
|
| 174 |
+
|
| 175 |
+
In a number of cases, mobile operators have tariff plans that offer low rates to all mobile operators of the country, on-net and off-net. In case this rate is lower than the interconnect rate for one or more other mobile operators, SIM Cards of one operator might be used to terminate calls to other operators also. The way this set up is organized by a bypasser is illustrated in the following example:
|
| 176 |
+
|
| 177 |
+

|
| 178 |
+
|
| 179 |
+
The diagram illustrates the 'OFF NET BYPASS' method. It shows three main components: 'Other Network' (blue cloud), 'Mobile Network B' (red cloud), and 'Mobile Network A' (green cloud). A call from 'Any origin' in 'Other Network' is sent via a 'Transmission path, e.g. VoIP' to a 'SIM Box'. The SIM Box then routes the call to 'Mobile Network A' under 'Tariff plans = Y'. From 'Mobile Network A', the call is forwarded to 'Mobile Network B' via an 'Interconnect path = X'. The call is then delivered to the final recipient in 'Mobile Network B'. A dashed red arrow at the bottom indicates the 'Off-net call' path. A note states 'Y is less than X'.
|
| 180 |
+
|
| 181 |
+
Diagram illustrating the 'OFF NET BYPASS' method. A call from 'Any origin' in 'Other Network' is sent via a 'Transmission path, e.g. VoIP' to a 'SIM Box'. The SIM Box then routes the call to 'Mobile Network A' under 'Tariff plans = Y'. From 'Mobile Network A', the call is forwarded to 'Mobile Network B' via an 'Interconnect path = X'. The call is then delivered to the final recipient in 'Mobile Network B'. A dashed red arrow at the bottom indicates the 'Off-net call' path. A note states 'Y is less than X'.
|
| 182 |
+
|
| 183 |
+
**Figure 5: Bypass Off Net**
|
| 184 |
+
|
| 185 |
+
In the above example, the rate for termination of international traffic equals $X$ . The *other network* on the left, is sending the traffic via an alternative interconnect path, namely a SIM Box towards the *mobile network B*.
|
| 186 |
+
|
| 187 |
+
The SIM Boxer terminates the call via tariff plan $Y$ , on the *Mobile Network B* ( $Y$ equals a local tariff, subject to specific promotions and conditions that are applicable to the retail market between customers of A and B, not to the interconnect market). For network A, it looks like a regular customer is making a call from his network towards network B. Mobile network A only receives $Y$ via the local tariff plan, while Network A has to pay $X$ towards Network B.
|
| 188 |
+
|
| 189 |
+
## 2.4 Leaky PBX
|
| 190 |
+
|
| 191 |
+
A Leaky PBX follows the same principle as a SIM Box but instead of a SIM card, the bypassers use a fixed line to terminate the traffic. Leaky PBX operators use the difference between the lowest fixed to mobile tariff and the interconnect rates. In some cases the corporate PBX's are used for this purpose. Leaky PBX exists in both forms on-net and off-net. The on-net form is illustrated in following example:
|
| 192 |
+
|
| 193 |
+

|
| 194 |
+
|
| 195 |
+
Diagram titled 'SIM Box through PABX' illustrating a call routing bypass. An 'Other Network' cloud on the left has an 'Any origin' call. A dashed arrow labeled 'Interconnect path = X' points from the 'Other Network' cloud to a 'Mobile Network' cloud on the right. A solid arrow labeled 'Transmission path, e.g. VoIP' points from the 'Other Network' cloud down to a 'PABX/ SIM Box' icon. From the 'PABX/ SIM Box', a solid arrow labeled 'E1 or ISDN' and 'Tariff plans = Y' points up to the 'Mobile Network' cloud. A dashed green arrow labeled 'Corporate Customer Call' points from a mobile phone icon in the 'Mobile Network' cloud back to the 'PABX/ SIM Box'. A solid arrow points from the 'Mobile Network' cloud down to another mobile phone icon. A green box at the bottom right contains the text 'Each call is seen as a corporate call by the Mobile Operator, but it isn't!'. A text label 'Y is less than X' is in the bottom left corner.
|
| 196 |
+
|
| 197 |
+
**Figure 6: Sim Box through PABX**
|
| 198 |
+
|
| 199 |
+
In the above example, the rate for termination of international traffic equals $X$ . The *Other Network* on the left, is sending traffic via an alternative interconnect path, namely a Leaky PBX, towards the *mobile network*.
|
| 200 |
+
|
| 201 |
+
The Leaky PBX terminates the call on the *mobile network* via a local tariff plan. Instead of the regular rate for termination of international traffic, $X$ , the mobile operator only receives $Y$ from the local call at a local tariff plan.
|
| 202 |
+
|
| 203 |
+
The quality issues due to the use of an extra radio channel explained in the following chapters are not valid in this case. However, remarks on lower voice quality, unsuccessful calls and longer call setup times remain applicable due to the extra PBX interface. Please note it is possible to spoof the CLI (Calling Line Identity) with a PBX (in case it is permitted by the fixed network).
|
| 204 |
+
|
| 205 |
+
## 2.5 International Off-net Bypass
|
| 206 |
+
|
| 207 |
+
The globalized telecommunications market and increased competition forced operators to become more creative in creating retail tariffs plans that are offered to customers. Some operators introduced a low cost or even flat rate tariffs towards some international destinations that could be lower than the international termination rate (retail rate $<$ international termination rate of a particular country). This might be used to terminate calls to other networks, as illustrated in the following example:
|
| 208 |
+
|
| 209 |
+

|
| 210 |
+
|
| 211 |
+
The diagram illustrates an 'International OFF NET BYPASS' scenario. It shows a call originating from 'Any origin' in the 'Other Network'. The standard 'Interconnect path = X' goes from the 'Other Network' through an 'International Carrier' to 'Mobile Network B'. A 'Transmission path, e.g. VoIP' (where 'Y is less than X') diverts the call from the 'Other Network' to a 'SIM Box'. From the 'SIM Box', the call is routed to 'Mobile Network A' via a local interconnect (labeled 'Y'). From 'Mobile Network A', the call is then routed to 'Mobile Network B' through the 'International Carrier' (labeled 'X'). A dashed red double-headed arrow at the bottom is labeled 'International Off-Net Call'.
|
| 212 |
+
|
| 213 |
+
Diagram titled 'International OFF NET BYPASS' showing a call routing path from an 'Other Network' through an 'International Carrier' to 'Mobile Network B', with a 'SIM Box' diverting traffic to 'Mobile Network A' via a 'Transmission path, e.g. VoIP'. The diagram includes labels for 'Any origin', 'Interconnect path = X', 'Y is less than X', and 'International Off-Net Call'.
|
| 214 |
+
|
| 215 |
+
**Figure 7: Bypass International Off Net**
|
| 216 |
+
|
| 217 |
+
The impact on Mobile Network A and Mobile Network B is comparable to the national off-net bypass scenario.
|
| 218 |
+
|
| 219 |
+
Mobile network A receives Y via the local tariff plan, while Network A has to pay X towards the next interconnect partner, in which case Y is less than X.
|
| 220 |
+
|
| 221 |
+
As a result of the diverted call via a SIM Box, the customers of Mobile Network B will suffer quality losses. The impact on the quality for end customers is explained in detail under paragraph 4.
|
| 222 |
+
|
| 223 |
+
## 2.6 SMS bypass scenario
|
| 224 |
+
|
| 225 |
+
In addition to bypassing voice traffic, SMS traffic can be bypassed via different methods.
|
| 226 |
+
|
| 227 |
+
For more information regarding the different fraud scenarios and measures that can be taken by mobile operators to reduce their level of exposure we refer to the following documents:
|
| 228 |
+
|
| 229 |
+
- [IR.70 SMS SS7 Fraud](#)
|
| 230 |
+
- [IR.71 SMS SS7 Fraud prevention](#)
|
| 231 |
+
- [FF 09 Introduction to SMS Fraud](#)
|
| 232 |
+
|
| 233 |
+
# 3 Impact on Radio and Network Planning
|
| 234 |
+
|
| 235 |
+
## 3.1 Inefficiency of Radio planning
|
| 236 |
+
|
| 237 |
+
The use of SIM Boxes significantly reduces bandwidth efficiency, as a SIM Box uses two radio channels for mobile to mobile calls, while normally only one radio channel is required. Using additional radio resources, where it is not required, may be inconsistent with statutory duties of radio authorities.
|
| 238 |
+
|
| 239 |
+
## 3.2 Network Planning and Operation
|
| 240 |
+
|
| 241 |
+
SIM Boxes are fixed and contain large quantities of SIM cards making large volumes of calls. The network therefore experiences abnormally high demand on individual cells, causing network congestion. Cell sizes are becoming very small in the areas where SIM Boxes are located. High concentrations of users may be unsupportable as it is likely to be impossible to shrink cell sizes any further and add additional infrastructure (capacity). Therefore, **mobile users can be denied service**, particularly since SIM Boxes often 'grab' the available cell capacity from early in the morning until late at night.
|
| 242 |
+
|
| 243 |
+
# 4 Consumer Impact
|
| 244 |
+
|
| 245 |
+
## 4.1 Detriment Due to Non-delivery of Signalling Data
|
| 246 |
+
|
| 247 |
+
Bypassed calls via SIM Boxes do not allow the delivery of the correct and original CLI of the calling party. This results in consumers being unable to use services that they would expect to be able to use. These services include:
|
| 248 |
+
|
| 249 |
+
- Returning a missed call through voice or SMS
|
| 250 |
+
- Screening unwanted or malicious calls
|
| 251 |
+
- Using an anonymous call rejection system (if offered by the operator)
|
| 252 |
+
- Managing roaming costs (customers may use CLI to decide whether to accept the call)
|
| 253 |
+
- Other CLI based services offered by the operator, such as: seamless access to voice mail, the development of a virtual home environment, and in general the roll out of all services based on an authentication of the customer and cross reference to network databases
|
| 254 |
+
- Voice mail retrieval when roaming abroad (direct or via short code)
|
| 255 |
+
- Voice mail deposit when roaming abroad
|
| 256 |
+
|
| 257 |
+
These limitations need to be considered against regulatory and industry guidelines for the delivery of CLI. Furthermore, there is legislation concerning the processing of personal data and the protection of privacy in the electronic communications sector dealing with calling CLI. In line with this legislation there are certain obligations on service providers regarding the provision of CLI.
|
| 258 |
+
|
| 259 |
+
It is GSMA's view that SIM Boxes compromise the integrity of CLI and as a result, service providers may not be able to fulfil their regulatory obligations in this regard.
|
| 260 |
+
|
| 261 |
+
## 4.2 Inbound roamers not reachable
|
| 262 |
+
|
| 263 |
+
Customers roaming on foreign networks may be unable to receive calls if incoming calls have been routed via a SIM Box. Retail SIM Cards are prohibited to phone the MSRN directly due to network security basics, which results in unreachable inbound roamers.
|
| 264 |
+
|
| 265 |
+
This is illustrated with the following example:
|
| 266 |
+
|
| 267 |
+

|
| 268 |
+
|
| 269 |
+
The diagram illustrates a call routing scenario between a UK Operator and a Belgian Operator.
|
| 270 |
+
- **UK Operator (left):** Contains a VLR (Visited Location Register) and an MSRN (Mobile Station Roaming Number). SIM Card B is shown in the UK.
|
| 271 |
+
- **Belgian Operator (right):** Contains an HLR (Home Location Register) and SIM Card A.
|
| 272 |
+
- **Interconnect Path:** A series of three carriers (Carrier 1, Carrier 2, Carrier 3) connect the Belgian Operator to the UK Operator.
|
| 273 |
+
- **SIM Box:** Located in the UK, it intercepts the call from Carrier 3.
|
| 274 |
+
- **Routing Steps:**
|
| 275 |
+
1. A call from SIM Card A to SIM Card B is initiated in the Belgian Operator's network.
|
| 276 |
+
2. The Belgian Operator sends a 'Provision of MSRN' request to the UK Operator's VLR.
|
| 277 |
+
3. The call is routed from the Belgian Operator's HLR to the MSRN.
|
| 278 |
+
4. The call is routed from the MSRN to the SIM Box.
|
| 279 |
+
5. The SIM Box attempts to call the MSRN (SIM Box SIM Card -> MSRN), but the UK network blocks this call, indicated by a red 'X' over the connection to SIM Card B.
|
| 280 |
+
|
| 281 |
+
Diagram illustrating the use of a SIM Box to bypass interconnect communications between a UK Operator and a Belgian Operator. The diagram shows five steps: 1. A call from SIM Card A (Belgian Operator) to SIM Card B (UK Operator) is initiated. 2. The Belgian Operator requests an MSRN from the UK Operator's VLR. 3. The call is routed from the Belgian Operator's HLR to the MSRN. 4. The call is routed from the MSRN to the SIM Box. 5. The SIM Box attempts to call the MSRN, but the UK network blocks the call due to network security.
|
| 282 |
+
|
| 283 |
+
Figure 8: Sim Box use: Inbound roamers not reachable
|
| 284 |
+
|
| 285 |
+
Description:
|
| 286 |
+
|
| 287 |
+
- **Step 1: A calls B (A -> B):** SIM Card A is calling SIM Card B (dialling the MSISDN associated with the SIM Card B).
|
| 288 |
+
- **Step 2: Obtaining MSRN:** As SIM Card B is roaming in UK, the Belgian operator needs to ask for a visited network' MSRN in order to route the call to the visited network.
|
| 289 |
+
- **Step 3: Normal international routing A calls MSRN (A->MSRN):** the Belgian mobile operator routes the call (UK MSISDN belonging to the visited operator) through their selected carrier.
|
| 290 |
+
- **Step 4: Bypassing the regular interconnect routes:** The last carrier in the interconnect path passes the call via a SIMBoxer instead of using the regular interconnection with the UK visited operator.
|
| 291 |
+
- **Step 5: SIM Box calls MSRN (SIM Box SIM Card -> MSRN):** The SIMBoxer tries to set up a call to reach the MSRN but the UK network will not allow the call due to network security; a retail SIM card from the visited operator is not able to call to the same operator MSRN directly. By this way, SIM Card B is not able to receive an international call if this call is routed via a SIM Box.
|
| 292 |
+
|
| 293 |
+
## 4.3 Service Disturbance
|
| 294 |
+
|
| 295 |
+
Customers may not be able to establish a call (or an existing live call may be terminated) if this call passes through a SIM Box using prepaid SIMs which are not recharged in real time. In case a prepaid SIM card in a SIM Box is out of credit, the calling party from abroad, may receive the following network message: *“Your account balance doesn’t allow the call completion”* There is no sense in receiving this message for post-paid customers.
|
| 296 |
+
|
| 297 |
+
In addition, quality issues can arise when customers try to use certain supplementary services while SIM Boxes do not support this service. A good example is video telephony, which will never reach its destination because SIM Boxes were not configured or do not support that type of service. The same issue applies with fax and circuit switch data.
|
| 298 |
+
|
| 299 |
+
Mobile operators cannot control the above-mentioned situations and are subjected to high levels of complaints, churn, diminished service reputation in the market and customer requests for financial credits (for example: a customer being unable to conduct business while abroad, and so on).
|
| 300 |
+
|
| 301 |
+
This seriously affects the reputation of GSM mobile networks and the service quality experienced by users (which may also affect the operators' ability to satisfy license obligations).
|
| 302 |
+
|
| 303 |
+
## **4.4 Ability of mobile customers near SIM Boxes to make or receive calls**
|
| 304 |
+
|
| 305 |
+
The use of SIM Boxes on mobile networks will have an adverse impact on customers' experiences as the excessive demand placed by SIM Boxes on certain cells will result in poor network coverage in some areas. Mobile customers may be unable to make or receive calls during the hours when SIM Boxes operate at full capacity and use all, or nearly all, of the cell capacity.
|
| 306 |
+
|
| 307 |
+
This will also affect the operators' ability to fulfil its obligations in respect of emergency calling.
|
| 308 |
+
|
| 309 |
+
## **4.5 Lost Calls and Call Routing Problems**
|
| 310 |
+
|
| 311 |
+
Interconnection capacity is monitored and adjusted according to the utilisation levels and the availability of overflow routes. In case of usage of SIM Boxes, this monitoring cannot take place, resulting in congestion due to bypass, which results in the loss of calls. Calls to mobile subscribers can also fail under certain call scenarios where the called subscriber is roaming or where the called number has been ported to another network within a country where a mobile portability solution has been adopted. This damages the customer experience and makes it difficult for network operators to identify the causes of such call failures.
|
| 312 |
+
|
| 313 |
+
## **4.6 Increased Call Set-up Time**
|
| 314 |
+
|
| 315 |
+
Due to the call set-up process of SIM Boxes, the post dial delay will significantly increase. In most cases the customer is unaware that the call is being routed through a SIM Box, resulting in an incorrect perception of poor network quality. The originating network, the international voice carrier and the terminating network, can be affected by these perceptions, resulting in loss of reputation for any of them.
|
| 316 |
+
|
| 317 |
+
In addition, a long call setup time will decrease the usage of consumers of their handset, resulting in lost calls due to quality issues.
|
| 318 |
+
|
| 319 |
+
Furthermore, it is significant to highlight the importance of long call set-up time on emergency calling.
|
| 320 |
+
|
| 321 |
+
Finally there are some countries where the quality standards promoted by Governments may be by-passed and cause penalties.
|
| 322 |
+
|
| 323 |
+
## **4.7 Deterioration in Voice Quality**
|
| 324 |
+
|
| 325 |
+
In general, cellular voice quality is very good. In the case of SIM Boxes however, the well-known transmission difficulties of the radio environment are likely to cause an increase in dropped calls and noise. This is an undesirable consequence to both the called and calling parties. The reason therefore is that due to the use of SIM Boxes, two radio legs rather than one are involved. Again, this will have an impact on emergency calling.
|
| 326 |
+
|
| 327 |
+
## **4.8 Privacy Issues**
|
| 328 |
+
|
| 329 |
+
If a call is routed through a SIM Box it may tumble upon the SIM Box's SIM voicemail. As the calling consumer believes he has reached the voicemail of the requested destination number, he may leave a confidential message on that SIM Box's SIM voicemail.
|
| 330 |
+
|
| 331 |
+
# **5 License obligations and other legal issues**
|
| 332 |
+
|
| 333 |
+
In cases where calls are routed via SIM Boxes, the CLI of the originating party is not transferred and the called party will receive the CLI of the SIM card that is used in the SIM Box.
|
| 334 |
+
|
| 335 |
+
Most operators have licence obligations to co-operate with the law enforcement agencies who have the authority to request identification and monitoring of mobile traffic (using the GSM MSISDN number/CLI). When there is use of SIM Boxes without the Mobile operator's knowledge and permission then the real CLI of the originating party is not known. Therefore, the mobile operators cannot fulfil these obligations. In some cases (for example in Belgium) the police authorities have already contacted mobile operators requesting clarification of this problem.
|
| 336 |
+
|
| 337 |
+
The absence of a correct CLI also prevents an operator from detecting the origin of malicious calls and thus prevents helping the affected consumers. Finally, the incorrect CLI compromises the correct handling of emergency calls (normally a licence obligation) where CLI is used to detect the victim's location. This is a subject of general interest where the mobile operator cannot take up his responsibilities of 'good corporate citizenship'.
|
| 338 |
+
|
| 339 |
+
# **6 Fraudulent Revenue Losses Caused by SIM Boxes**
|
| 340 |
+
|
| 341 |
+
## **6.1 Service Revenue**
|
| 342 |
+
|
| 343 |
+
These are indirect revenue losses caused by the service disturbances & customer dissatisfaction as described in chapter 4 of this document.
|
| 344 |
+
|
| 345 |
+
## **6.2 Radio Investment**
|
| 346 |
+
|
| 347 |
+
Some SIM Boxes use more than 32 SIMs simultaneously at one location. Operators may need to install extra radio equipment or even new antenna sites only to compensate for the SIM Boxes, leading to large investments merely to generate quality, revenue and service disturbances.
|
| 348 |
+
|
| 349 |
+
## **6.3 Cost of Sales**
|
| 350 |
+
|
| 351 |
+
Fabrication and distribution of SIM cards to be used in SIM Boxes to bypass traffic (and thus generate revenue losses), costs money. In some cases (for low credit pre-paid cards) the SIMs are thrown away within 30 minutes.
|
| 352 |
+
|
| 353 |
+
# 7 Mechanisms to Detect SIM Boxes
|
| 354 |
+
|
| 355 |
+
## 7.1 Manual testing
|
| 356 |
+
|
| 357 |
+
This mechanism is reflected on each IR21 test numbers database and consists on a simple test call for numbers which can only be accessed from the “true” Network-to-Network interface, and which cannot be accessed from a mobile station.
|
| 358 |
+
|
| 359 |
+
These test number are made available by IREG and therefore by all PLMN, through a directory number on Auto-Answer Circuits. It is suggested that these number could be from fragments of a range used for MSRN and HONs (Hand-over Numbers), but not actually assigned to a particular MSC.
|
| 360 |
+
|
| 361 |
+
As mentioned, these numbers cannot be accessed from a Mobile Station, but is accessible from genuine Network-to-Network interconnection points only. Therefore provides carriers with an easy test so that they can check to see if a downstream carrier is using a SIM Box device.
|
| 362 |
+
|
| 363 |
+
This procedure is described in GSMA document [IR.21](#). More information about manual testing and the comparison with other detection mechanisms can be found in [IN.22](#).
|
| 364 |
+
|
| 365 |
+
## 7.2 Passive detection
|
| 366 |
+
|
| 367 |
+
Mobile operators can detect SIM Boxes by using multiple criteria on traffic & customer data. These are some examples of common criteria to trigger bypass alarms:
|
| 368 |
+
|
| 369 |
+
- Only outgoing calls
|
| 370 |
+
- No SMS
|
| 371 |
+
- No GPRS
|
| 372 |
+
- High volume of traffic
|
| 373 |
+
- Small company but high call costs
|
| 374 |
+
- Suddenly lots more traffic in one antenna cell
|
| 375 |
+
- All calls from the same antenna cell
|
| 376 |
+
- SIMs using a blacklisted IMEI
|
| 377 |
+
- Activation of a lot of pre-paid SIMs without using them immediately
|
| 378 |
+
|
| 379 |
+
Operators can develop an in-house solution or use one of the fraud management systems available on the market.
|
| 380 |
+
|
| 381 |
+
## 7.3 Active detection
|
| 382 |
+
|
| 383 |
+
These detection systems actively set up international calls and compare the CDR created on both sides to detect SIM Boxes. A-side can be fixed, mobile, VoIP, calling card, carrier, call back and so on. There are multiple solutions available on the market.
|
| 384 |
+
|
| 385 |
+
In the selection of an active detection system, mobile operators should be aware that the active detection system supports countermeasures, in order to avoid detection of the test calls by SIM Box operators.
|
| 386 |
+
|
| 387 |
+
In case the active detection system does not support countermeasures, there is a high possibility that SIM Box operators will soon discover the calls made for test purposes and
|
| 388 |
+
|
| 389 |
+
avoid being detected. More information on advanced SIM Box bypassing can be found under Chapter 8.
|
| 390 |
+
|
| 391 |
+
## 7.4 Combination of detection mechanisms
|
| 392 |
+
|
| 393 |
+
It should be noted that both an active detection system and a passive detection system can be used in combination. Often the results of an active detection system can be used and extrapolated to feed the internal passive detection system of a Mobile operator.
|
| 394 |
+
|
| 395 |
+
# 8 Evolutions in SIM Box bypassing
|
| 396 |
+
|
| 397 |
+
The equipment and software, used for bypassing the regular interconnect has seriously evolved in the last few years. In this paragraph, we define some of the most important features SIM Box operators make use of during their activities.
|
| 398 |
+
|
| 399 |
+
## 8.1 Human behaviour simulation
|
| 400 |
+
|
| 401 |
+
SIM Boxes can simulate human behaviour in order to avoid being detected by mobile operators. Therefore, they will ensure their call behaviour is not suspicious.
|
| 402 |
+
|
| 403 |
+
Some examples of human behaviour simulation are the following:
|
| 404 |
+
|
| 405 |
+
- Each SIM card in the SIM Box is only used for a few hours per day. Multiple SIM cards are used and often switched, in order to ensure normal call patterns;
|
| 406 |
+
- Free minutes are used to phone from SIM card to SIM card within the SIM Box. In this way, the call behaviour of the SIM cards is not limited to outgoing calls only;
|
| 407 |
+
- Free SMSs are used to send SMS towards the SIM cards in the SIM Box. In this way, not only voice services are used.
|
| 408 |
+
|
| 409 |
+
## 8.2 Automatic SIM replacement
|
| 410 |
+
|
| 411 |
+
SIMs are automatically rotated, for example, once their prepaid credit is zero.
|
| 412 |
+
|
| 413 |
+
## 8.3 Moving equipment
|
| 414 |
+
|
| 415 |
+
Bypassers are known to move their equipment. Changing antenna cell simulates human behaviour.
|
| 416 |
+
|
| 417 |
+
## 8.4 Multiplexers
|
| 418 |
+
|
| 419 |
+
Some bypass operators have multiple SIM Boxes at different locations, but only one centralized storage point for the SIMs. They use multiplexers to virtually copy the SIMs to the SIM Box equipment. This avoids the need of a human presence in each SIM Box location, and allows moving SIMs to another antenna regularly.
|
| 420 |
+
|
| 421 |
+
## 8.5 Time Windows
|
| 422 |
+
|
| 423 |
+
SIM Boxes can use a different selection of SIMs during peak and off-peak hours, week and weekend. The choice of SIM cards used during certain time frames depends on the promotion of that moment. By using specific software, SIM Box operators have the possibility to manage the timeslots per SIM card. Via this optimal usage of promotions, profits can be maximized.
|
| 424 |
+
|
| 425 |
+
## 8.6 New IMEI send with every new SIM card/call
|
| 426 |
+
|
| 427 |
+
Advanced SIM Box equipment provides the SIM Box operator with the possibility to spoof the IMEI (International Mobile Equipment Identity) of the SIM Box equipment. By this way, some SIM Box operators send a different IMEI for every SIM card used and sometimes even for every call made. Meaning, the mobile operator is not able to extrapolate the results of the detection of one SIM, to block all SIMs with that same IMEI number. Invisible customer
|
| 428 |
+
|
| 429 |
+
Bypassers may use third parties or multiple people to buy the SIMs, making it nearly impossible to identify SIM Boxes through customer profiling.
|
| 430 |
+
|
| 431 |
+
## 8.7 Subscription Fraud
|
| 432 |
+
|
| 433 |
+
Some SIM Boxers maximize their profits by using SIMs purchased with false IDs, cloned SIMs, stolen SIMs, and so on. In certain countries fraud and criminality are closely linked with interconnect bypass.
|
| 434 |
+
|
| 435 |
+
# 9 Summary and Recommendations
|
| 436 |
+
|
| 437 |
+
For the reasons outlined in this document, mobile operators should be concerned about the congestion, quality and user experience impairments associated with the use of SIM Boxes. This particularly applies to the uncontrolled use by carriers where mobile operators may have no prior knowledge and have to make unpredictable network planning and optimisation changes.
|
| 438 |
+
|
| 439 |
+
A first possibility being implemented by most operators is to ensure that **commercial terms and conditions exclude the use of SIM Boxes** for routing third party traffic. Operators should then also be free to detect, identify and terminate such subscriptions which are in breach of contract or in breach of any national legislation preventing the use of such devices.
|
| 440 |
+
|
| 441 |
+
Mobile operators should be free to define reasonable commercial terms and conditions to protect the integrity and quality of their networks.
|
| 442 |
+
|
| 443 |
+
It is possible that to disincentive the use of SIM Boxes, mobile operators could explicitly exclude the use of unauthorized SIM Boxes (different from private and corporate users) from special traffic discounts given to their customers.
|
| 444 |
+
|
| 445 |
+
Mobile operators can also sign Roaming Service Level Agreement's (RSLA). Further information about RSLAs are described in [BA.51](#). Both Roaming and Interconnection departments should work closely to prevent Gateway bypass, as this interconnect scheme reduces roaming and international interworking quality.
|
| 446 |
+
|
| 447 |
+
Furthermore, National Regulatory Authorities (NRA) may promote the interests of the citizens by ensuring that the integrity and security of public communications networks are maintained. It is argued that the use of SIM Boxes compromises the integrity and security of our members' networks and as a result our members' regulatory obligations may be called into question by the relevant NRA.
|
| 448 |
+
|
| 449 |
+
Customer Care Impacts should be taken into consideration in the detection method of SIM Boxes. **The operator must ensure an MSISDN is not identified incorrectly as a SIM Box**, irrespective of the detection method applied.
|
| 450 |
+
|
| 451 |
+
Operators must foresee procedures to ensure customers are refunded for damage caused in case their MSISDN has been deactivated incorrectly.
|
| 452 |
+
|
| 453 |
+
## Annex A Document Management
|
| 454 |
+
|
| 455 |
+
## A.1 Document History
|
| 456 |
+
|
| 457 |
+
| Version | Date | Brief Description of Change | Approval Authority | Editor / Company |
|
| 458 |
+
|---------|-------------|----------------------------------------|--------------------------|----------------------|
|
| 459 |
+
| 1.0 | 30 Jan 2015 | New PRD FSG.01 derived from IN.02 v5.2 | Fraud and Security Group | Nick Cheung (GSMA) |
|
| 460 |
+
| 1.1 | 21 Apr 2023 | Updated GSMA logo | N/A | David Maxwell (GSMA) |
|
| 461 |
+
|
| 462 |
+
## Other Information
|
| 463 |
+
|
| 464 |
+
| Type | Description |
|
| 465 |
+
|------------------|----------------------|
|
| 466 |
+
| Document Owner | FASG |
|
| 467 |
+
| Editor / Company | David Maxwell (GSMA) |
|
| 468 |
+
|
| 469 |
+
It is our intention to provide a quality product for your use. If you find any errors or omissions, please contact us with your comments. You may notify us at [prd@gsma.com](mailto:prd@gsma.com)
|
| 470 |
+
|
| 471 |
+
Your comments or suggestions & questions are always welcome.
|
files/FASG/FS.01 v1.1/images/562f471e8153729557e6a4ee6343c32c_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.01 v1.1/images/64662465bba247703fdec49c8f3309f9_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.01 v1.1/images/990567efebf979be51f56d1150012c9d_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.01 v1.1/images/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.01 v1.1/images/a738993919a50143787084ee7ce6e2f2_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.01 v1.1/images/a7d78d22e465dea388b31d0739f9d0cd_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.01 v1.1/images/e394c2b5c61344f6a12397f430086072_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.01 v1.1/images/e9314c83043183351ed74908e9bf2f90_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.01 v1.1/images/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.13 Network Equipment Security Assurance Scheme - Framework/doc.md
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
files/FASG/FS.13 Network Equipment Security Assurance Scheme - Framework/images/007b053fe94a8348f75128a584503fd0_img.jpg
ADDED
|
Git LFS Details
|
files/FASG/FS.13 Network Equipment Security Assurance Scheme - Framework/images/0c08e48c08f96934cd6bc6911f3069dc_img.jpg
ADDED
|
Git LFS Details
|