DOCSLIB.ORG

SSF) Management Information Model 2 Draft ES 201 386 V1.1.1 (1998-10)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SSF) Management Information Model 2 Draft ES 201 386 V1.1.1 (1998-10) Draft ES 201 386 V1.1.1 (1998-10) ETSI Standard Telecommunications Management Network (TMN); Service Switching Function (SSF) management information model 2 Draft ES 201 386 V1.1.1 (1998-10) Reference DES/TMN-00001 (cu000icp.PDF) Keywords IN, TMN, management, SSF ETSI Postal address F-06921 Sophia Antipolis Cedex - FRANCE Office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Internet [email protected] http://www.etsi.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. © European Telecommunications Standards Institute 1998. All rights reserved. ETSI 3 Draft ES 201 386 V1.1.1 (1998-10) Contents Intellectual Property Rights .................................................................................................................... 8 Foreword................................................................................................................................................. 8 1 Scope ............................................................................................................................................ 9 2 References .................................................................................................................................... 9 3 Abbreviations.............................................................................................................................. 10 4 Rationale..................................................................................................................................... 11 5 Overview..................................................................................................................................... 11 6 Technical approach..................................................................................................................... 12 6.1 SSF functional decomposition..............................................................................................................12 6.1.1 Rationale.........................................................................................................................................12 6.1.2 Method............................................................................................................................................13 6.2 SSF management requirements ............................................................................................................15 6.2.1 Rationale.........................................................................................................................................15 6.2.2 Method............................................................................................................................................15 6.3 SSF management information model....................................................................................................17 6.3.1 Rationale.........................................................................................................................................17 6.3.2 Method............................................................................................................................................17 7 Introduction to the SSF model.................................................................................................... 20 8 Management requirements for the SSF sub entities................................................................... 26 8.1 Introduction..........................................................................................................................................26 8.2 Operational Requirements and Activities.............................................................................................27 9 Informal description of Managed Object Classes ...................................................................... 40 9.1 SSF Object Model (informal)...............................................................................................................40 9.1.1 The Relationship diagrams .............................................................................................................40 9.1.1.1 SSF Overall Model....................................................................................................................40 9.1.1.2 Inheritance Hierarchy................................................................................................................42 9.1.1.3 Naming Hierarchy.....................................................................................................................42 9.1.2 Requirement: Configure triggering of IN based service feature control .........................................43 9.1.2.1 Information Model Diagram .....................................................................................................43 9.1.2.2 Informal description of managed objects ..................................................................................45 9.1.2.2.1 IN Trigger............................................................................................................................45 9.1.2.2.2 Origination Attempt Accepted Trigger................................................................................46 9.1.2.2.3 Information Collected Trigger.............................................................................................46 9.1.2.2.4 Information Analysed Trigger .............................................................................................47 9.1.2.2.5 Route Select Failure Trigger................................................................................................47 9.1.2.2.6 Busy Trigger........................................................................................................................47 9.1.2.2.7 No Answer Trigger..............................................................................................................48 9.1.2.2.8 Terminating Attempt Accepted Trigger...............................................................................48 9.1.2.2.9 Mid Call Event Trigger .......................................................................................................48 9.1.2.2.10 Disconnect Trigger ..............................................................................................................49 9.1.2.2.11 Line Trigger Base................................................................................................................49 9.1.2.2.12 OLT Base ............................................................................................................................50 9.1.2.2.13 TLT Base.............................................................................................................................50 9.1.2.2.14 Trunk Group Trigger Base ..................................................................................................50 9.1.2.2.15 OTT Base ............................................................................................................................51 9.1.2.2.16 TTT Base.............................................................................................................................51 9.1.2.2.17 Private Facility Trigger Base...............................................................................................52 9.1.2.2.18 Office Trigger Base .............................................................................................................52 9.1.2.2.19 Service Feature Control.......................................................................................................53 ETSI 4 Draft ES 201 386 V1.1.1 (1998-10) 9.1.3 Requirement: IN-Authorization ......................................................................................................54 9.1.4 Requirement: Configure SCF access ..............................................................................................55 9.1.4.1 SSF Application Process...........................................................................................................56 9.1.4.1.1 SCF-SSF AE........................................................................................................................57 9.1.4.1.2 TCAP ASE ..........................................................................................................................57 9.1.4.1.3 INAP ASE...........................................................................................................................57 9.1.4.1.4 Service Feature Control.......................................................................................................57 9.1.4.1.5 SCF access...........................................................................................................................57 9.1.4.1.6 Point Code based SCF access..............................................................................................57 9.1.4.1.7 Global Title based SCF access ............................................................................................58 9.1.5 Configure SRF/SCF relaying capabilities and Configure SRF assisting Relationships ..................59 9.1.5.1 SSF AP......................................................................................................................................60
Load more

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]
  • Nokia's in Solution for Fixed and Cellular Networks
    4 Nokia's IN solution for fixed and cellular networks Pekka Lehtinen Markus Warsta Nokia Telecommunications P.O. Box33 02601 Espoo, Finland 1. INTRODUCTION The development of Intelligent Networks (IN) was started by Bellcore in USA more than ten years ago in order to support the Regional Bell Operating Companies in the new deregulated telecommunications environment. The original goal was to enable the network operators to effectively introduce and manage new services by means of a centralized database in a Service Control Point (SCP). In the past years, several IN specifications have been developed, including IN 1, AIN Rel.O and AIN Rel.1. The Advanced Intelligent Network Release ·1 (AIN Rel.1) of Bellcore contains a service-independent standard interface for the queries sent from the Service Switching Points (SSPs) to the SCP. The International Telecommunications Union (ITU) has worked out its Intelligent Network Application Part (INAP) specifications for the SSP-SCP interface, the so-called Capability Set 1 (CS.1). The European Telecommunications Standards Institute (ETSI) has completed its corresponding ETSI CS.l Core specifications in 1993. It is expected that the CS.l recommendations will be adopted world-wide. This would offer open interfaces between the SSP and SCP resulting in vendor independence. Signalling System No.7 (SS7), fault-tolerant computing, on-line transaction processing, and today's database technology have enabled the development of efficient IN elements. This paper presents Nokia's IN solution. J. Harju et al. (eds.), Intelligent Networks © Springer Science+Business Media Dordrecht 1995 62 Intelligent Networks 2. FUNCTIONAL ARCHITECTURE OF INTELLIGENT NETWORKS The main e.lements of the IN architecture of the ITU and ETSI are: • Service Switching Point (SSP), • Service Control Point (SCP), • Service Management System (SMS), • Service Creation Environment (SCE), and • Intelligent Peripheral (IP).
    [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]
  • N2SCP CAMEL/INAP Conformance
    N-Squared Software N2SCP CAP/INAP Protocol Conformance Statement Version 2020-08 N2SCP CAP/INAP Protocol Conformance Statement Version 2020-08 1 Document Information 1.1 Scope and Purpose This document describes the implementation of the CAMEL (including INAP variants) protocol for real- time SCP flows for voice interaction control using the N-Squared Service Control Point (N2SCP) family of applications. The N2SCP family of applications includes: • N2DSG-SCP (CAMEL/Diameter Signalling Gateway) • N2NP-SCP (Number Portability translation application) • N2ACD-SCP (Advanced Call Distribution application for Toll-Free and other routing services) • …plus other custom SCP services that may be developed. All of these applications use the N2SCP framework. They do not typically use all of the framework. Please refer to the relevant technical guide ([R-N2-DSG-TG], [R-N2-NP-TG], [R-N2-ACD-TG]) for application-specific scenarios and configuration parameters. This document assumes a working knowledge of the relevant CAP/INAP and other telephony concepts, including the standard CAP/INAP interactions between an SCP, an SSP, and an SRP (or Intelligent Peripheral). 1.2 Definitions, Acronyms, and Abbreviations Term Meaning AC Apply Charging ACR Apply Charging Report ARI Assist Request Instructions ASN.1 Abstract Syntax Notation One AT Activity Test BCSM Basic Call State Model CAMEL Customized Applications for Mobile Network Enhanced Logic CAP CAMEL Application Part CIR Call Information Request/Report CTR Connect To Resource CWA Continue With Argument DFC
    [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]
  • IDP and Analyzed Information Features 910-5805-001 Revision a December 2009
    Tekelec EAGLE® 5 Integrated Signaling System Feature Manual - IDP and Analyzed Information Features 910-5805-001 Revision A December 2009 Copyright 2009 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.......................................................................9 Introduction.............................................................................................................................10 Scope and Audience...............................................................................................................10 Manual Organization..............................................................................................................10 Related Publications...............................................................................................................11 Documentation Availability, Packaging, and Updates.....................................................11 Documentation Admonishments..........................................................................................12 Customer Care Center............................................................................................................12 Emergency Response..............................................................................................................14 Locate Product Documentation on the Customer
    [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]
  • Finer Digit Analysis of Telephone Numbers for Routeing Purposes REPORT to OFCOM
    Finer Digit Analysis of Telephone Numbers for Routeing Purposes REPORT TO OFCOM 11 August, 2005 Issue 1.0 Ref: 00720/RT/818.1. Authors: Mark Norris & Peter Walker I N T E R C A I M O N D I A L E Registered in England, No: 3271854 Assessed and registered to ISO9001 Regatta House, High Street, Marlow, Bucks, UK SL7 1AB Tel: +44 (0) 1628-478470 Fax: +44 (0) 1628-478472 http://www.intercai.co.uk Table of Contents Summary of Findings ........................................................................................................................1 1 Introduction................................................................................................................................1 1.1 Specific objectives..............................................................................................................2 1.2 Contents of Report .............................................................................................................2 2 Background to numbering developments ..................................................................................3 3 Data decode – general findings..................................................................................................4 3.1 Outline of investigations ....................................................................................................4 3.2 Main findings.....................................................................................................................4 4 Geographic Numbers .................................................................................................................5
    [Show full text]