PCS Network Signaling Using SS7

Total Page:16

File Type:pdf, Size:1020Kb

PCS Network Signaling Using SS7 Supporting interconnection with the PSTN PCS Network Signaling Using SS7 YI-BINGLIN AND STEVEN K. DEVRIES ersonal Communications Services this article is based on EIA,TIA IS-41 Revision B. We also describe , (PCS) facilitates the exchange of information (voice, data, video, some potential extensions of the IS-41 protocol based on a image, etc.) for mobile users independent of time, location, draft of IS-41Revision C. In this article, “IS-41.C”refers to EIAlTIA -and access arrangement. Tosupport PCS, mobile communications PN-2991, the Baseline Text Draft 3 9-2-94of IS-41 Revision C 1191. protocols such as EIWIAInterim Standard 41 (IS-41) 112-161 or Global System for Mobile Communications (GSM) [20] have been defined for PCS Network (PCN) inter-system oper- Signaling System No. 7 ations. To support interconnection between a PCN and the Public Switched Telephone Network (PSTN), it is essential ommon Channel Signaling (CCS) is a signaling method that the mobile communicationsprotocol interactswith the PSTN which provides control and management in the telephone signaling system for mobility management and call control. Cnetwork. CCS consists of supervisory functions, address- This article describes the interactions between a PCN and ing, and providing call information. A CCS channel conveys the PSTN in four aspects: messages to initiate and terminate calls, check on the status of some Interconnection Interfaces -What are the network inter- part of the network, and control the amount of traffic allowed. faces between a PCN and the PSTN? CCS uses a separate out-of-band signaling network to carry Message Routing - How is the information exchanged signaling messages. In all figures of this article, the signal links among the PCNPSTN network elements? will be represented by dashed lines, and the trunks will be Mobility Management - How d0es.a PCN recognize the represented by solid links. SS7 is a CCS system developed to locations of the mobile users? satisfy the telephone operating companies’ requirements for an Call Control - How are the calls set up between the mobile improvement to the earlier signaling systems (which lacked the users and the wireline users? sophistication required to deliver much more than Plain Old Mobility management merits further discussion. In a PCN Telephone Service or POTS). the current location of a mobile user is usually maintained by a This section provides a brief introduction to the SS7 network two-level hierarchical strategy with two types of databases. The architecture and protocol from the perspective of PCN inter- Home Location Register (HLR) is the location register to which connection. The reader is referred to [ 11 for a more complete a mobile user identity is assigned for record purposes such as mobile SS7 tutorial. user information (e.g., directory number, profile information, cur- rent location,validationperiod). The Visitor Location Register (VLR) The SS7 Network Architecture is the location register other than the HLR used to retrieve infor- Figure 1 illustrates an example of the SS7 signaling network. mation for handling of calls to or from a visiting mobile user [14]. The figure only shows the parts that involve the interconnec- When a mobile moves from the home PCN to a visited PCN, its tion between a PCN and the PSTN. The network consists of location is registered at the VLR of the visited PCN. The VLR then three distinct components. informs the mobile’s HLR of its current location. The details of the *Service Switching Point (SSP) is a telephone switch inter- registration processwill be discussed in asubsequent section. When connectedbySS7links.TheSSPsperformcallprocessingoncallsthat a call is delivered to a mobile, the HLR is first queried to find originate, tandem, or terminate at that node. In this article, an SSP its location (i.e., the VLR corresponding to its current location). in a PCN are called a Mobile Switching Center (MSC). The details of location tracking can be found in 1121, and the call *Signal Transfer Point (STP) is a switch that relays SS7 mes- setuphelease process is discussed in the section on PCN/PSTN sages between network switches and databases. Based on the address call control using ISUP. Since it is likely that two PCNs are fields of the SS7 messages, the STPs route the messages to the connected through the PSTN, it is important to understand correct outgoing signaling links. To meet the stringent reliability how the PSTN is involved in PCS mobility management. requirements, STPs are provisioned in mated pairs. To address these four aspects, we consider IS-41 as the mobile Service Control Point (SCP) contains databases for pro- communications protocol and Signaling System No. 7 (SS7) [2-51 viding enhanced services. An SCP accepts queries from an SSP as the PSTN signaling protocol. The IS-41 protocol considered in and returns the requested information to the SSP. In mobile 44 1070-9916/95/$04.000 1995 IEEE IEEE Personal Communications June 1995 1, applications,an SCP may contain an HLRor a VLR. There are six types of SS7 signaling links. Two types of the links are introduced in this article. Other types of links can be found in [7]. Each SSP and SCP will have a minimum of one signal link to each STP pair. The signal link is referred to as the Access Link (A-link). The number of A-links between an SSP and an STP pair can be up to 128 though most switch suppli- A-Link A-Link ers have limited the number to 16. I Signaling links that connect STPs of different networks (e.g., PCN and PSTN in our example) are called Diagonal Links (D-links). D-links are deployed in a quad arrangement with three-waypath diversity. The maximum link set size is 64. I 1 The SS7 Protocol ~~------ ~- ~~ The basic parts of the SS7 protocol and the cor- W Figure 1. An example of the SS7 network architecture. responding OS1 layers are shown in Fig. 2. In the protocol hierarchy, the Operations, Maintenance, and AdministrationPart (OW)and Mobile Appli- cation Part (MAP) are TCAP (i.e., Transaction OS1 layers The SS7 layers Capabilities Application Part; to be defined) applications. The details of the OMAP are omit- -/I ted and can be found in [7]. Application The MAP will be elaborated based on the IS- *I I 41 protocol. The other parts of the SS7 protocol are described below. ...__________-.--..-.~-~~ ISDN-UP *The Message Transfer Part (MTP) consists of Presentation three levels corresponding to the OS1 physical layer, session data link layer, and network layer, respectively. transport The MTP Level 1 defines the physical, electrical, and functional characteristics of the signaling links connecting SS7 components. The MTP Level 2 provides reliable transfer of signaling messages between two directly connected signaling points. The MTP Level 3 provides the functions and procedures related to message routing and network manage- ment. I MTP level 3 I *The Signaling Connection Control Part (SCCP) provides additional functions such as Data link MTP level 2 Global Title Translation to the MTP to transfer I I non-circuit-related signaling information such as PCS registration and cancellation. Physical MTP level 1 *The Transaction Capabilities Application I I Part (TCAP) provides the ability to exchange information between applications using non-circuit .~ _.~ related signaling. W Figure 2. The SS7signalingprotocol.~ ~ *Integrated Services Digital Network User Part (ISUP) establishes circuit-switched network connections (e.g., call setupirelease). Pass-alongsig- two for SS7 signaling, and two for trunk (voice naling service sends the signaling information to each circuit) connections [8]. The signaling interfaces rep- switching point involved in a call connection. resents the physical signalinglink connectionbetween The IS-41 protocol [12, 1.51 is implemented in a PCN and the PSTN. The SS7 signaling inter- the MAP as an application of the TCAP. The connection methods are described as follows: wireless call setup/release is completed by using A-link signaling interface involves A-links from the ISUP. The MTP and the SCCP provide rout- an MSC to a PSTN STP pair (Figs. 3a and c). ing services between a PCN and the PSTN. OD-linksignaling interface involves D-links from a PCN STP pair to a PSTN STP pair (Figs. 3b and d). lnterconnection and Message The trunk interfaces represents a physical SS7- supported trunkconnection between aPCN and the Routing between PSTN. The types of the SS7 trunk interconnections PCN and PSTN are described as follows: *Type 2A with SS7 trunk interface provides everal types of interconnections between a connection between a PCN and a PSTN tandem PCN and the PSTN have been described in switch. The Type 2A with SS7 interfaces are shown S [8, 171. We describe four types of SS7 inter- in Figs. 3a and b. connection between a PCN and the PSTN (specif- *Type 2B with SS7 trunk interface provides ically, the local telephone networks) using SS7: connection between a PCN and a PSTN end office IEEE Personal Communications June 1995 45 IS-41 Revisions B and C, but not in IS-41 Revision A. The ISUP messages for wireless call control FacilitiesDirective INVOKE(Last) QUERYWITHPERMISSION (see the section on PCN/PSTN call control using FacilitiesDirective RETURN RESULT(Last) CONVERSATIONWITHPERMISSIONISUP) are not delivered with GTT. Details of IS- FacilitiesDirective RETURN ERROR RESPONSE 41 message routing can be found in Appendix B. The FacilitiesDirective REJECT RESPONSE - appendix describes the fields of an IS-41 message HandoffMeasurementRequest INVOKE(Last) QUERYWITHPERMISSION which are used for the routing purpose and how HandoffMeasurementRequest RETURN RESULT(Last) RESPONSE the routing procedure is performed. HandoffMeasurementRequest RETURN ERROR RESPONSE HandoffMeasurementReauest REJECT RESPONSE Mobility Management MobileOnChannel I INVOKE ]RESPONSE ~ Using TCAP QualificationRequest INVOKE(Last) QUERYWITHPERMISSION QualificationRequest RETURN RESULT(Last) RESPONSE wenty six TCAP operations2 are defined in QualificationRequest RETURN ERROR RESPONSE IS-41.B [ 131 for three purposes: Inter-MSC QualificationRequest REJECT RESPONSE T Handoff [15], Automatic Roaming [12], and Operations, Administration, and Maintenance RegistrationCancellation INVOKE(Last) QUERYWITHPERMISSION [16].
Recommended publications
  • SGSN in a 2.5G GPRS Network
    SGSN in a 2.5G GPRS Network • SGSN in a 2.5G GPRS Network, on page 1 • 2.5G SGSN Configuration Components, on page 2 • How the 2.5G SGSN Works , on page 4 • Information Required for the 2.5G SGSN, on page 6 SGSN in a 2.5G GPRS Network This chapter outlines the basic configuration and operation of the Serving GPRS Support Node (SGSN) in 2.5G GPRS wireless data networks. The simplest configuration that can be implemented on the system to support SGSN functionality in a 2.5G network requires one context but we recommend a minimum of two: one for the SGSN service (required) and another for the charging context. The service context organizes the following: • GPRS service configuration • MAP (Mobile Application Part) configuration • DNS (Domain Naming System) configuration for resolution of APN (Access Point Name) domain names • SGTP (SGSN GPRS Tunneling Protocol) configuration The charging context facilitates the following: • Configuration of connectivity to the CGF (Charging Gateway Function) The following functionality is configured at the global or system level in the local management context: • NSEI (Network Service Entity Identity) configuration • SCCP (Signalling Connection Control Part) network configuration • SS7 (Signaling System 7) connectivity configuration • GTT (Global Title Translation) configuration To simplify configuration management, more contexts can be created to categorize the service configuration. Each context can be named as needed. The contexts listed above can be configured as illustrated in the figure on the next page. SGSN in a 2.5G GPRS Network 1 SGSN in a 2.5G GPRS Network 2.5G SGSN Configuration Components 2.5G SGSN Configuration Components In order to support 2.5G SGSN functionality, the system must be configured with at least one context for the GPRS service (2.5G SGSN service).
    [Show full text]
  • N-Squared Software N2SRP INAP Protocol Conformance Statement
    N-Squared Software N2SRP INAP Protocol Conformance Statement Version 2020-02 N2SRP INAP Protocol Conformance Statement Version 2020-02 1 Document Information 1.1 Scope and Purpose This document describes the implementation of the INAP (including CAMEL variants) protocols for real-time SRP flows for voice interaction control using the N-Squared (N2) SIP Specialized Resource Platform (SRP) when used in conjunction with an INAP Service Control Platform (SCP). It should be read in conjunction with the N2SRP Technical Guide [R-1]. This document assumes a working knowledge of the relevant INAP and other telephony concepts, including the standard INAP interactions between an SCP, an SSP, and an SRP (or Intelligent Peripheral). 1.2 Definitions, Acronyms, and Abbreviations Term Meaning AC Application Context (in TCAP) ARI Assist Request Instructions AS Application Server ASP Application Server Process ASPAC ASP Active ASPTM ASP Traffic Maintenance ASN.1 Abstract Syntax Notation One CAMEL Customized Applications for Mobile Network Enhanced Logic CAP CAMEL Application Part DTMF Dual Tone Multi-Frequency ETSI European Telecommunications Standards Institute GT Global Title GTI Global Title Indicator IETF Internet Engineering Task Force INAP Intelligent Networking Application Part IP Internet Protocol ITU-T International Telecommunication Union Telecommunication Standardization Sector M3UA MTP3 User Adaption Layer MTP3 Message Transfer Part Level 3 N2 N-Squared OCNCC Oracle Communications Network Charging & Control PA Play Announcement PACUI Prompt
    [Show full text]
  • A-Port User's Guide, Release 46.2 Copyright © 1993, 2015, Oracle And/Or Its Affiliates
    Oracle® Communications EAGLE A-Port User©s Guide Release 46.2 E63583 Revision 1 July 2015 Oracle® Communications EAGLE A-Port User's Guide, Release 46.2 Copyright © 1993, 2015, 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.
    [Show full text]
  • Technical Architecture Alternatives for Open Connectivity Roaming Hubbing Model
    GSM Association Non-confidential Official Document IR.80 - Technical Architecture Alternatives for Open Connectivity Roaming Hubbing Model Technical Architecture Alternatives for Open Connectivity Roaming Hubbing Model Version 2.0 26 February 2015 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Non-confidential 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 © 2015 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. V2.0 Page 1 of 95 GSM Association Non-confidential Official Document IR.80 - Technical Architecture Alternatives for
    [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: [email protected] 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]
  • Database Administration Manual - Global Title Translation 910-6277-001 Revision a January 2012
    Tekelec EAGLE® 5 Release 44.0 Database Administration Manual - Global Title Translation 910-6277-001 Revision A January 2012 Copyright 2012 Tekelec. All Rights Reserved. Printed in USA. Legal Information can be accessed from the Main Menu of the optical disc or on the Tekelec Customer Support web site in the Legal Information folder of the Product Support tab. Table of Contents Chapter 1: Introduction.....................................................................13 Overview..................................................................................................................................14 Scope and Audience...............................................................................................................15 Manual Organization..............................................................................................................15 Documentation Admonishments..........................................................................................15 Customer Care Center............................................................................................................16 Emergency Response..............................................................................................................18 Related Publications...............................................................................................................19 Documentation Availability, Packaging, and Updates.....................................................19 Locate Product Documentation on the Customer Support Site.......................................19
    [Show full text]
  • SCCP Signalling Aspects for Roaming Version 3.2.1 10 October 2005
    GSM Association Non-confidential Official Document IR.22 - SCCP Signalling Aspects for Roaming SCCP Signalling Aspects for Roaming Version 3.2.1 10 October 2005 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Non-confidential 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 © 2015 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. V3.2.1 Page 1 of 11 GSM Association Non-confidential Official Document IR.22 - SCCP Signalling Aspects for Roaming Table of Contents 1 Introduction 3 1.1 Scope 3 1.2 Abbreviations 3 2 Numbering Plan Indicator of Global Title 3 3 SCCP Requirement for a Node in the International ISDN 4 4 Process for the Establishment of PLMN Signalling Relationships 5 4.1 Message Routing 6 4.2 Establishment Process 6 5.
    [Show full text]
  • Virtual Signaling Transfer Point User©S Guide Release 8.1 E86290 Revision 01
    Oracle® Communications Diameter Signaling Router Virtual Signaling Transfer Point User©s Guide Release 8.1 E86290 Revision 01 July 2017 Oracle Communications Diameter Signaling Router Virtual Signaling Transfer Point User's Guide, Release 8.1 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.
    [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]
  • 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 [email protected]. 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.
    [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]