Mobile Application Part (MAP)

Total Page:16

File Type:pdf, Size:1020Kb

Mobile Application Part (MAP) 3GPP2 X.S0004-000-E v 6.0 Date: July 2007 Mobile Application Part (MAP) INTRODUCTION COPYRIGHT 3GPP2 and its Organizational Partners claim copyright in this document and individual OPs may copyright and issue documents or standards publications in individual Organizationial Partner’s name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizationial Part- ner’s documents should be directed to that Organizational Partner. See www.3gpp2.org for more information. X.S0004-000-E 1 2 Revision History 3 4 Revision Date Remarks 5 (IS-41) 0 February 1988 Initial publication. 6 7 (IS-41) A January 1991 8 9 (IS-41) B December 1991 10 (IS-41) C February 1996 11 12 TIA/EIA-41-D December 1997 Initial ANSI publication. 13 X.S0004-000-E v1.0 March 2004 Initial publication with new part 14 X.S0004-500 ••• 590-E v1.0 structure. 15 X.S0004-700 ••• 790-E 16 17 X.S0004-000-E v2.0 July 2005 Version 2.0. 18 X.S0004-400-E July 2005 Initial publication with new part 19 X.S0004-600 ••• 691-E structure. 20 21 X.S0004-000-E v3.0 October 2005 Version 3.0. 22 X.S0004-691-E v2.0 October 2005 Addition of Annex F: RECOVERY 23 FROM SCCP SEGMENTATION 24 FAILURE. 25 26 X.S0004-000-E v4.0 May 2006 Version 4.0. 27 X.S0004-200 and 290-E May 2006 Initial ANSI publication with new 28 part structure. 29 30 X.S0004-000-E v5.0 January 2007 Version 5.0. 31 32 X.S0004-321-E January 2007 Initial ANSI publication with new 33 part structure. 34 X.S0004-322-E January 2007 Initial ANSI publication with new 35 part structure. 36 37 X.S0004-323-E January 2007 Initial ANSI publication with new 38 part structure. 39 X.S0004-324-E January 2007 Initial ANSI publication with new 40 part structure. 41 42 X.S0004-000-E v6.0 July 2007 Version 6.0. 43 X.S0004-520-E v2.0 July 2007 Incorporated changes from Miscel- 44 laneous Rev. E standards. 45 46 47 X.S0004-540-E v2.0 July 2007 Incorporated changes from Miscel- 48 laneous Rev. E standards. 49 50 X.S0004-550-E v2.0 Incorporated changes from Miscel- 51 July 2007 laneous Rev. E standards. 52 53 54 X.S0004-630-E v2.0 July 2007 Incorporated changes from Miscel- 55 laneous Rev. E standards. 56 57 58 59 60 ii X.S0004-000-E 1 Revision Date Remarks 2 3 X.S0004-640-E v2.0 July 2007 Incorporated changes from Miscel- 4 laneous Rev. E standards. 5 6 7 X.S0004-641-E v2.0 July 2007 Incorporated changes from Miscel- 8 laneous Rev. E standards. 9 10 X.S0004-651-E v2.0 July 2007 Incorporated changes from Miscel- 11 laneous Rev. E standards. 12 13 14 X.S0004-690-E v2.0 July 2007 Incorporated changes from Miscel- 15 laneous Rev. E standards. 16 17 X.S0004-691-E v3.0 July 2007 Incorporated changes from Miscel- 18 laneous Rev. E standards. 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 iii X.S0004-000-E v6.0 Contents List of Tables .............................................................................................................. 0–xxxviii List of Figures .................................................................................................................. 0–xliii Part 000 - INTRODUCTION TO MAP 1 COMPARISON WITH N.S0005-0 v1.0/TIA/EIA-41-D ...............................................0–2 2 PART STRUCTURE ......................................................................................................0–8 2.1 OBJECTIVE..................................................................................................................... 0–11 2.2 SCOPE.............................................................................................................................. 0–11 2.3 REFERENCES ................................................................................................................. 0–11 2.3.1 Normative References ......................................................................................... 0–11 2.3.2 Informative References........................................................................................ 0–14 3 DEFINITIONS AND DOCUMENTATION CONVENTIONS ..................................0–16 3.1 DEFINITIONS ................................................................................................................. 0–16 4 SYMBOLS AND ABBREVIATIONS .........................................................................0–28 4.1 DOCUMENTATION CONVENTIONS ......................................................................... 0–50 4.1.1 Scenario Diagram Conventions ........................................................................... 0–50 4.1.2 Scenario Description Conventions ..................................................................... 0–53 4.1.3 TCAP Package Type Diagram Conventions ...................................................... 0–55 5 NETWORK REFERENCE MODEL ...........................................................................0–57 5.1 NETWORK ENTITY RELATIONSHIP DIAGRAM ..................................................... 0–57 6 CELLULAR INTERSYSTEM SERVICES .................................................................0–59 6.1 GENERAL BACKGROUND AND ASSUMPTIONS ................................................... 0–60 6.2 OTA ASSUMPTIONS ..................................................................................................... 0–61 6.3 NETWORK TMSI ASSUMPTIONS ............................................................................... 0–61 6.4 WIRELESS INTELLIGENT NETWORK ASSUMPTIONS.......................................... 0–62 6.5 SEGMENTATION AND REASSEMBLY ASSUMPTIONS ......................................... 0–62 6.6 PCS MULTI-BAND SUPPORT ASSUMPTIONS.......................................................... 0–63 6.7 IMSI SUPPORT ASSUMPTIONS................................................................................... 0–63 6.8 WIRELESS NUMBER PORTABILITY ASSUMPTIONS............................................. 0–65 6.9 CALLING NAME PRESENTATION ASSUMPTIONS ................................................ 0–66 6.10 AUTHENTICATION ENHANCEMENT ASSUMPTIONS........................................... 0–67 7 RESTRICTIONS ...........................................................................................................0–67 Part 200 1 Introduction..................................................................................................................200–1 1.1 OBJECTIVE................................................................................................................... 200–1 000-iii X.S0004-000-E v6.0 1.2 SCOPE ............................................................................................................................200–1 2 BASIC INTERSYSTEM HANDOFF SCENARIOS .................................................200–2 2.1 Successful Handoff-Forward ..........................................................................................200–3 2.2 Successful Handoff-Back ...............................................................................................200–5 2.3 Successful Handoff-Back with Tandem via FacilitiesDirective (Path Minimization is not supported) ..............................................200–7 2.4 Successful Handoff-Back with Tandem via FacilitiesDirective when HandoffToThird Fails ............................................................200–9 2.5 Successful Handoff-Forward with Tandem .................................................................200–12 2.6 Successful Handoff-Back with Tandem .......................................................................200–13 2.7 Successful HandoffToThird with Path Minimization ..................................................200–14 2.8 Successful HandoffToThird with Tandem and Path Minimization .............................200–16 2.9 Successful Handoff-Back with Tandem via HandoffToThird when the method of Handoff- ToThird with Tandem and Path Minimization is involved ..........................................200–18 2.10 Successful Call Release by Served MS ........................................................................200–21 2.11 Successful Call Release by Other Party .......................................................................200–22 2.12 Successful Handoff-Forward of an Originating MS Awaiting Answer .......................200–24 2.13 Successful Handoff-Forward of a Terminating MS While Alerting ............................200–26 Part 290 Annex A: Additional DMH Support for Intersystem Handoff in MAP (normative) .......290–1 Part 321 1 Call Delivery................................................................................................................321–1 1.1 CD Demand Activation or De-Activation.......................................................................321–1 1.2 CD Invocation to an Idle MS on Another MSC..............................................................321–1 1.3 CD Invocation to an Idle, Local MS ..............................................................................321–4 1.4 CD Invocation to a Busy MS .........................................................................................321–5 1.5 CD Invocation with No Page Response or No Answer .................................................321–6 1.6 CD Invocation to an Inaccessible MS ............................................................................321–7 1.7 CD Invocation with Intersystem Paging ........................................................................321–8 1.8 CD Invocation
Recommended publications
  • Miot Location in Roaming Version 1.0 20 May 2020
    GSM Association Confidential - Full, Rapporteur, Associate and Affiliate Members Official Document NG.120 - MIoT Location in Roaming MIoT Location in Roaming Version 1.0 20 May 2020 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Confidential - Full, Rapporteur, Associate and Affiliate Members Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the Association and 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. Copyright Notice Copyright © 2020 GSM Association Disclaimer 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. Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V1.0 Page 1 of 37 GSM Association Confidential - Full, Rapporteur, Associate and Affiliate Members Official Document NG.120 - MIoT Location
    [Show full text]
  • SS7 – Signaling System Number 7
    SS7 – Signaling System Number 7 818 West Diamond Avenue - Third Floor, Gaithersburg, MD 20878 Phone: (301) 670-4784 Fax: (301) 670-9187 Email: info@gl.com Website: https://www.gl.com 1 SS7 – A Brief Overview • Defined by ITU-T in its Q.700-series, ANSI, and ETSI • Out-of-band signaling system • Designed for call control, remote network management, and maintenance • Combines circuit-switched and packet-switched networks • Suitable for use on point-to-point terrestrial and satellite links • SS7 networks are flexible, reliable, with capacity up to 64 Kbps 2 T1 E1 Analyzer Hardware Platforms 3 TDM mTOP™ Solutions mTOP™ tProbe™ FXO FXS Dual UTA 1U tProbe™ w/ FXO FXS 4 Applications • Allows telecommunications networks to offer wide ranges of services such as telephony, fax transmission, data transfer • Setting up and tearing down circuit-switched connections • Support for Intelligent Network (IN) services such as toll-free (800) calling, SMS, EMS • Mobility management in cellular networks • Local Number Portability (LNP) to allow subscribers to change their service, service provider, and location without needing to change their telephone number • Support for ISDN 5 SS7 Network Architecture 6 Signaling Points • SS7 constitutes three different types of Signaling Points (SP) – ➢ Signaling Transfer Point ➢ Service Switching Point ➢ Service Control Point Signaling Transfer Points Service Switching Points Service Control Points Transfers SS7 messages between Capable of controlling voice circuits via a Acts as an interface between telecommunications other SS7 nodes voice switch databases and the SS7 network Acts as a router for SS7 messages Converts signaling from voice switch into Provide the core functionality of cellular networks SS7 format Does not originate SS7 messages Can originate and terminate messages, but Provides access to database cannot transfer them 7 Signaling Links Access Links connects SCP or SSP to an STP.
    [Show full text]
  • USSD Gateway Technical Guide
    Oracle® Communications Network Charging and Control USSD Gateway Technical Guide Release 12.0.0 December 2017 Copyright Copyright © 2017, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error- free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
    [Show full text]
  • Security for the Core Network of Third Generation Mobile Systems
    Security for the core network of third generation mobile systems GUNTER HORN, DIRK KROSELBERG Siemens AG, Corporate Technology, D-81730 Muenchen, Germany STEFANPUTZ T-Mobil, P.O. Box 300463, D-53184 Bonn, Germany ROLAND SCHMITZ T-Nova Technology Centre, D-64307 Darmstadt, Germany Keywords: UMTS, MAP Security, Multimedia domain, SIP, IPSec, IKE, Key Management Abstract: This contribution gives a survey of the present standardisation activities by 3GPP (3'd Generation Partnership Project1) in the area of security for signalling in the core network of third generation mobile systems. We give an overview of the protocols that need to be secured, present the basic principles behind the overall security architecture and describe the key management and format of secured messages, as far as they have already been finalised. In particular, we address core network security aspects of the 3GPP multimedia domain. 1 3GPP was formed by regional standards organisations from Europe, Asia and North America to produce specifications for a third generation mobile system named UMTS which is designed to evolve from GSM core network. There is a competing effort known as 3GPP2 with partners from North America and Asia. The original version of this chapter was revised: The copyright line was incorrect. This has been corrected. The Erratum to this chapter is available at DOI: 10.1007/978-0-387-35413-2_36 R. Steinmetz et al. (eds.), Communications and Multimedia Security Issues of the New Century © IFIP International Federation for Information Processing 2001 298 1. THREATS TO CORE NETWORK SECURITY FOR MOBILE RADIO NETWORKS The core network of mobile radio systems is the part of the network which is independent of the radio interface technology of the mobile terminal.
    [Show full text]
  • Teleware BT Proposition
    Private Mobile eXchange ™ PMX ™ GSM Mobile Switching Centre Product Highlights – IP softMSC 3GPP switching compliant Distributed Network Architecture Multiple processing units & redundancy, GSM Compliant ‘A’ Interface - IP High Availability, Scalability & Flexibility Multiple Vendor Radio Access Networks MSC, GMSC, HLR, VLR Central HLR (Network) supported MAP-C, MAP-D, MAP-E, MAP-F Call forwarding (conditional, unconditional), call waiting, call hold, call transfer IP: SS7 over SIGTRAN and SIP support TDM: SS7 over TDM via Gateway Calling party based routing, Intelligent call routing GTT translations, STP supported Caller Id; CLIP/CLIR Support for SMS (MT/MO) Connected Line Id; COLP/COLR Explicit/Implicit IMSI detach & VLR purge Operator determined barring GPRS & EDGE support (Gr over SS7) E.164 support CSD Support - secure phones + PSTN Gateway Support for Lawful Call intercept Optional built-in SMSC, AuC and EIR function SIP RFC 3261 Support Optional voicemail, conferencing and external WAP, multi-media message entity platforms Call Detail Recoding Optional Media Termination Point [Transcoding SOS: Default or LA originated intelligent routing outbound & Inbound] of emergency calls Enterprise Support Highlights Full PBX network node support Optional: Push-To-Talk – PMR replacement Translation table, Inbound & Outbound Private Mobile Office – Personal Number, Personal Assistant, Unified Messaging, Call recording, Extensive Routing Tables conferencing, IVR incl. Call Queuing etc Business Confidential Product
    [Show full text]
  • Mobile Application Part Interface (MAPI) Specification
    Mobile Application Part Interface (MAPI) Specification Mobile Application Part Interface (MAPI) Specification Version 1.1 Edition 7.20141001 Updated October 25, 2014 Distributed with Package openss7-1.1.7.20141001 Copyright c 2008-2014 Monavacon Limited All Rights Reserved. Abstract: This document is a Specification containing technical details concerning the imple- mentation of the Mobile Application Part Interface (MAPI) for OpenSS7. It contains recommendations on software architecture as well as platform and system applicability of the Mobile Application Part Interface (MAPI). It provides abstraction of the Mobile Application Part (MAP) interface to these components as well as providing a basis for Mobile Application Part control for other Mobile Application Part protocols. Brian Bidulock <bidulock@openss7.org> for The OpenSS7 Project <http://www.openss7.org/> Published by: OpenSS7 Corporation 1469 Jefferys Crescent Edmonton, Alberta T6L 6T1 Canada Copyright c 2008-2014 Monavacon Limited Copyright c 2001-2008 OpenSS7 Corporation Copyright c 1997-2000 Brian F. G. Bidulock All Rights Reserved. Unauthorized distribution or duplication is prohibited. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [GNU Free Documentation License], page 405. Permission to use, copy and distribute this documentation without modification, for any purpose and without fee or royalty is hereby granted, provided that both the above copyright notice and this permission notice appears in all copies and that the name of OpenSS7 Corporation not be used in advertising or publicity pertaining to distribution of this documentation or its contents without specific, written prior permission.
    [Show full text]
  • 3GPP TS 29.002 V3.14.0 (2002-09) Technical Specification
    3GPP TS 29.002 V3.14.0 (2002-09) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1999) R GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS rd TM The present document has been developed within the 3 Generation Partnership Project (3GPP ) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. TM Specifications and reports for implementation of the 3GPP system should be obtained via the 3GPP Organisational Partners' Publications Offices. Release 1999 2 3GPP TS 29.002 V3.14.0 (2002-09) Keywords GSM. UMTS, MAP, SS7, network 3GPP Postal address 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © 2002, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA, TTC). All rights reserved. 3GPP Release 1999 3 3GPP TS 29.002 V3.14.0 (2002-09) Contents Foreword ..........................................................................................................................................................25
    [Show full text]
  • Request for Comments on the Draft Outline for The
    International Telecommunication Union QUESTION 18/2 Strategy for migration of mobile networks to IMT-2000 and beyond ITU-D STUDY GROUP 2 RAPPORTEUR FOR QUESTION 18/2 IMT-2000 for developing countries” IMT-2000 “Mid-Term Guidelines (MTG) on the smooth transition of existing mobile networks to IMT-2000 for developing countries” “Mid-Term Guidelines (MTG) on the smooth transition of existing mobile networks to Guidelines (MTG) on the smooth transition of existing “Mid-Term QUESTION 18/2 International Telecommunication Printed in Switzerland Union Geneva, 2005 Photo credits: ITU Photo Library ITU-D THE STUDY GROUPS OF ITU-D The ITU-D Study Groups were set up in accordance with Resolutions 2 of the World Telecommunication Development Conference (WTDC) held in Buenos Aires, Argentina, in 1994). For the period 2002-2006, Study Group 1 is entrusted with the study of seven Questions in the field of telecommunication development strategies and policies. Study Group 2 is entrusted with the study of eleven Questions in the field of development and management of telecommunication services and networks. For this period, in order to respond as quickly as possible to the concerns of developing countries, instead of being approved during the WTDC, the output of each Question is published as and when it is ready. For further information Please contact: Ms Fidélia AKPO Telecommunication Development Bureau (BDT) ITU Place des Nations CH-1211 GENEVA 20 Switzerland Telephone: +41 22 730 5439 Fax: +41 22 730 5484 E-mail: fidelia.akpo@itu.int Placing orders for ITU publications Please note that orders cannot be taken over the telephone.
    [Show full text]
  • SIU Developers Manual
    Dialogic® DSI Signaling Servers SS7G41 SIU Developers Manual www.dialogic.com Copyright and Legal Notice Copyright© 2012. Dialogic Inc. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Inc. at the address provided below. All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Inc. and its affiliates or subsidiaries (“Dialogic”). Reasonable effort is made to ensure the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this document. INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY. Dialogic products are not intended for use in certain safety-affecting situations. Please see http://www.dialogic.com/about/legal.htm for more details. Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries, and thus may not function properly in other countries.
    [Show full text]
  • Siemens Documentation, Book A30828-X1121-A807-02-7671
    Theory of Operations Guide SURPASS hiQ 8000 Version 10.0 November 2005 A30828-X1121-A807-02-7671 No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, mechanical, electronic, photocopying, recording, or otherwise, without prior written permission of Siemens. The software described in this publication is furnished under a license agreement and may be used only in accordance with the terms of that agreement. Request Siemens publications from your Siemens representative or the Siemens branch serving you. Publications are not stocked at the address below. Siemens Network Convergence LLC 271 Mill Road Chelmsford, MA 01824 SURPASS and NetManager are trademarks of Siemens AG or its affiliates and subsidiaries. All other trademarks and company names are the property of their respective owners. © 2005 Siemens Communications, Inc. All rights reserved. bkhis.fm History of Changes History of Changes 0 Document Version Date Summary 01 August 2005 Initial issue for Version 10.0 02 November 2005 Modifications / additions A30828-X1121-A807-02-7671, November 2005 SURPASS hiQ 8000, Theory of Operations Guide 0-iii bkhis.fm History of Changes A30828-X1121-A807-02-7671, November 2005 0-iv SURPASS hiQ 8000, Theory of Operations Guide bkTOC.fm Contents Contents 0 History of Changes . 0-iii List of Figures . 0-x List of Tables . 0-xi 1 About This Guide . 1-1 1.1 Intended Audience. 1-1 1.2 What You Need to Know . 1-1 1.3 What’s New in This Guide . 1-1 1.4 How to Use This Guide .
    [Show full text]
  • SS7 Protocol Stack
    CHAPTER 3 SS7 Protocol Stack This chapter describes the components of the SS7 protocol stack. A stack is a set of data storage locations that are accessed in a fixed sequence. The SS7 stack is compared against the Open Systems Interconnection (OSI) model for communication between different systems made by different vendors. Figure 3-1 shows the components of the SS7 protocol stack. SS7 Level 1: Physical Connection This is the physical level of connectivity, virtually the same as Layer 1 of the OSI model. SS7 specifies what interfaces will be used, both Bellcore (Telecordia) and ANSI call for either the DS0A or the V.35 interface. Because central offices are already using DS1 and DS3 facilities to link one another, the DS0A interface is readily available in all central offices, and is preferred in the SS7 network. As the demands on the SS7 network increase (local number portability), and as the industry migrates toward ATM networks, the DS1 interface will become the link interface. SS7 Level 2: Data Link The data link level provides the network with sequenced delivery of all SS7 message packets. Like the OSI data link layer, it is only concerned with the transmission of data from one node to the next, not to its final destination in the network. Sequential numbering is used to determine if any messages have been lost during transmission. Each link uses its own message numbering series independent of other links. SS7 uses CRC-16 error checking of data and requests retransmission of lost or corrupted messages. Length indicators allow Level 2 to determine what type of signal unit it is receiving, and how to process it.
    [Show full text]
  • We Know Where You Are!
    2016 8th International Conference on Cyber Conflict Permission to make digital or hard copies of this publication for internal use within NATO and for personal or educational use when for non-profit or non-commercial Cyber Power purposes is granted providing that copies bear this notice and a full citation on the N.Pissanidis, H.Rõigas, M.Veenendaal (Eds.) first page. Any other reproduction or transmission requires prior written permission by NATO CCD COE. 2016 © NATO CCD COE Publications, Tallinn We Know Where You Are! Siddharth Prakash Rao Dr Silke Holtmanns Department of Computer Science Bell Labs, Nokia Aalto University, Finland Espoo, Finland siddharth.rao@aalto.fi silke.holtmanns@nokia.com Dr Ian Oliver Dr Tuomas Aura Bell Labs, Nokia Department of Computer Science Espoo, Finland Aalto University, Finland ian.oliver@nokia.com tuomas.aura@aalto.fi Abstract: Mobile network technologies require some degree of tracking of user location, specifically user equipment tracking, as part of their fundamental mechanism of working. Without this basic function, features such as hand-over between cells would not work. Since mobile devices are typically associated with a single person, this provides a potential mechanism for user location surveillance. Network operators are bound by strict privacy legislation. However, spying by certain agencies, hackers and even advertisers without the users’ or operators’ knowledge has become a serious issue. In this article, we introduce and explain all known recent attacks on mobile networks that compromised user privacy. We focus on attacks using the Signalling System 7 (SS7) protocol as the interconnection interface between operators mainly in GSM networks.
    [Show full text]