DOCSLIB.ORG

EN 301 668-1 V1.1.2 (2000-05) European Standard (Telecommunications Series)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
EN 301 668-1 V1.1.2 (2000-05) European Standard (Telecommunications Series) Final draft ETSI EN 301 668-1 V1.1.2 (2000-05) European Standard (Telecommunications series) Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent Network Application Protocol (INAP); Part 1: Protocol specification for Camel Phase 2 2 Final draft ETSI EN 301 668-1 V1.1.2 (2000-05) Reference DEN/SPS-03053-1 Keywords IN, INAP, ISDN, mobile, protocol ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.:+33492944200 Fax:+33493654716 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 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/ If you find errors in the present document, send your comment to: [email protected] 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 2000. All rights reserved. ETSI 3 Final draft ETSI EN 301 668-1 V1.1.2 (2000-05) Contents Intellectual Property Rights................................................................................................................................6 Foreword ............................................................................................................................................................6 1 Scope........................................................................................................................................................7 2 References................................................................................................................................................7 3 Abbreviations ...........................................................................................................................................9 4 General .....................................................................................................................................................9 4.1 Definition methodology......................................................................................................................................9 4.2 Example physical scenarios................................................................................................................................9 4.3 INAP addressing.................................................................................................................................................9 4.3.1 Quality of service parameters .....................................................................................................................10 4.3.2 SCCP addressing ........................................................................................................................................10 4.4 Definition and usage of LegID .........................................................................................................................10 4.5 Detection Points ...............................................................................................................................................10 4.5.1 DP processing rules ....................................................................................................................................10 5 Reflection of TCAP Application Context (AC).....................................................................................11 6 Additional abstract syntax......................................................................................................................11 6.1 Operation types.................................................................................................................................................11 6.2 Operation timers...............................................................................................................................................12 6.3 Data types.........................................................................................................................................................12 6.4 Application Service Elements...........................................................................................................................18 6.4bis Application contexts.........................................................................................................................................18 6.5 Classes..............................................................................................................................................................19 7 Error procedures.....................................................................................................................................19 7.1 Operation related error procedures...................................................................................................................19 7.1.1 MissingCustomerRecord.............................................................................................................................19 7.1.1.1 Operations SSF->SCF...........................................................................................................................19 7.1.2 MissingParameter .......................................................................................................................................20 7.1.2.1 Operations SSF -> SCF.........................................................................................................................20 7.1.3 UnknownLegID ..........................................................................................................................................20 7.1.3.1 Operations SCF->SSF...........................................................................................................................20 7.2 Entity related error procedures .........................................................................................................................20 7.2.1 Expiration of TSSF ......................................................................................................................................20 7.2.1.1 Procedures SSF->SCF...........................................................................................................................20 8 Detailed operation procedures ...............................................................................................................20 8.1 ApplyCharging procedure ................................................................................................................................20 8.1.1 General description.....................................................................................................................................20 8.1.1.1 Parameters.............................................................................................................................................20 8.1.1.2 Normal procedure .................................................................................................................................21 8.1.1.3 Error handling .......................................................................................................................................21 8.2 ApplyChargingReport procedure......................................................................................................................22 8.2.1 General description.....................................................................................................................................22 8.2.1.1 Parameters.............................................................................................................................................22 8.2.2 Invoking entity (SSF)..................................................................................................................................23 8.2.2.1 Normal procedure .................................................................................................................................23 8.3 AssistRequestInstructions procedure................................................................................................................23 8.3.1 General description.....................................................................................................................................23 8.3.1.1 Parameters.............................................................................................................................................23 8.4 CallInformationReport procedure.....................................................................................................................23 8.4.1 General description.....................................................................................................................................23 8.4.1.1 Parameters.............................................................................................................................................24
Load more

Recommended publications
  • 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]
  • Implementing Intelligent Network Services with the Session Initiation Protocol
    Tech-Report Number CUCS-002-99 Implementing Intelligent Network Services with the Session Initiation Protocol Jonathan Lennox Henning Schulzrinne Thomas F. La Porta Department of Computer Science Department of Computer Science Bell Laboratories Columbia University Columbia University Lucent Technologies [email protected] [email protected] [email protected] Phone: (212) 939 7018 Phone: (212) 939 7042 Phone: (732) 949-2281 Abstract Internet telephony is receiving increasing interest as an alternative to traditional telephone networks. This article shows how the IETF’s Session Initiation Protocol (SIP) can be used to perform the services of traditional Intelligent Network protocols, as well as additional services. 0 Contents 1 Introduction 3 2Overview 3 2.1 Billing . ................................................. 4 3 Architecture of IPtel signaling 4 4 Capability Set 1: Service Features 4 4.1AbbreviatedDialing(ABD)........................................ 5 4.2 Attendant (ATT) . .......................................... 5 4.3Authentication(AUTC).......................................... 5 4.4Authorizationcode(AUTZ)....................................... 5 4.5Automaticcallback(ACB)........................................ 7 4.6Calldistribution(CD)........................................... 7 4.7Callforwarding(CF)........................................... 7 4.8 Call forwarding on busy/don’t answer (CFC) . ........................... 7 4.9Callgapping(GAP)............................................ 7 4.10 Call hold with announcement
    [Show full text]
  • The Evolution of Intelligent Networks to Mobile and Broadband
    WJ~ HEWLETT a:~ PACKARD The Evolution ofIntelligent Networks to Mobile and Broadband-Computers in the Network, Now and Tomorrow Ray Crispin, Martin Sadler HP Laboratories Bristol HPL-95-68 June, 1995 Current Intelligent Network solutions will undergo considerable evolution to support the mobile and broadband networks of tomorrow. The present generation of Service Control Points, Home Location Registers and Intelligent Peripherals will give way to generic IN computing platforms which are capable of supporting a wide range of services. Requirements will develop over time, suggesting the need for highly adaptable computing solutions. Three key properties are needed to enable this adaptability: scalability, programmability, and modularity. This paper outlines the argument that a distributed, component oriented, approach will emerge to meet the needs of the future. Internal Accession Date Only © Copyright Hewlett-Packard Company 1995 The Eyolution of Intelligent Networks to Mobile and Broadband - Computers in the Network. Now and Tomorrow I,CURRENT SITUATION 1.1 Digital Switching Computer control of the telecommunications network started with the introduction of stored program digital switches in the seventies. Creating these systems has been, and continues to be, a very substantial engineering undertaking, with typical switches having 10-30M lines of code. Needless to say this poses huge software engineering problems, particularly with configuration management and regression testing. It is interesting to note that much of the complexity arises from the need to manage the operation ofthe switches. Typical, 80-90% ofthe code is for management and only 10-20% to control the switching. Also, because of diverse world market conditions, there is the need to accommodate variations giving rise to the need for configuration.
    [Show full text]
  • INAP); Part 1: Protocol Specification for Camel Phase 2 2 Draft ETSI EN 301 668-1 V1.1.1 (1999-07
    Draft ETSI EN 301 668-1 V1.1.1 (1999-07) European Standard (Telecommunications series) Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1) extension; Intelligent Network Application Protocol (INAP); Part 1: Protocol specification for Camel Phase 2 2 Draft ETSI EN 301 668-1 V1.1.1 (1999-07) Reference DEN/SPS-03053-1 (fg090ico.PDF) Keywords IN, INAP, ISDN, mobile, protocol 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] Individual copies of this ETSI deliverable can be downloaded from http://www.etsi.org If you find errors in the present document, send your comment to: [email protected] 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 1999. All rights reserved. ETSI 3 Draft ETSI EN 301 668-1 V1.1.1 (1999-07) Contents Intellectual Property Rights ............................................................................................................................... 6 Foreword............................................................................................................................................................ 6 1 Scope.......................................................................................................................................................
    [Show full text]
  • Design and Implementation of an IP Multimedia Subsystem (IMS) Emulator Using Virtualization Techniques
    Design and Implementation of an IP Multimedia Subsystem (IMS) Emulator Using Virtualization Techniques F. Ga lán 1,2, E. García2, C. Chávarri2, M. Gómez3, D. Fernández2 1: Centre Tecnològic de Telecomunicacions de Catalunya (CTTC) Av. Canal Olimpic, s/n - Castelldefels, Spain [email protected] 2: Departamento de Ingeniería de Sistemas Telemáticos (DIT) Universidad Politécnica de Madrid (UPM) Av. Complutense, s/n - Madrid, Spain {galan,egarcia,chavarri,david}@dit.upm.es 3: Agora Systems, S. A. Velázquez, 46 - Madrid, Spain [email protected] Abstract Multimedia service provisioning in Packet-Switched networks is one of the most active research and standardization efforts nowadays, and constitutes the most likely evolution of current telecommunication networks. In this environment, the 3GPP IP Multimedia Subsystem (IMS) represents the service provisioning platform of choice for SIP-based content delivery in mobile and fixed environments. However, in spite of the advanced status of research and specification in this field, few IMS-based services have been defined or deployed, mainly due to the fact that production or experimental IMS platforms are scarcely available for service validation and testing. This paper addresses the design and implementation through virtualization techniques of an IMS testbed intended for the functional validation of services, presenting the involved technologies, the undertaken implementation strategy, and the experiences and tests carried out in the first stages of its development. Keywords IP Multimedia Subsystem, virtualization, VNUML, IMS, 3GPP 1. Introduction Given the current trend in telecommunications industry towards data packet switching (the so called all-IP approach), the IP Multimedia Subsystem (IMS) plays a key role as service provisioning platform in Next Generation Networks.
    [Show full text]
  • Release Notes Release 10.3.0.2 E98788-01
    Oracle® Communications Performance Intelligence Center Oracle Communications Performance Intelligence Center Release Notes Release 10.3.0.2 E98788-01 November 2019 Oracle® Communications Performance Intelligence Center Oracle Communications Performance Intelligence Center Release Notes, Release 10.3.0.2 Copyright © 2003, 2019 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, the following notices are 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]
  • 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]
  • EN 301 931-1 V1.1.2 (2001-09) European Standard (Telecommunications Series)
    ETSI EN 301 931-1 V1.1.2 (2001-09) European Standard (Telecommunications series) Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Protocol specification; Part 1: Common aspects 2 ETSI EN 301 931-1 V1.1.2 (2001-09) Reference DEN/SPAN-03063/1-1 Keywords CS3, CTM, IN, INAP, protocol, UPT ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.:+33492944200 Fax:+33493654716 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 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/ If you find errors in the present document, send your comment to: [email protected] 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 2001.
    [Show full text]
  • CAMEL User's Guide Contains the Following Information: No Title Description 1 Introduction to CAMEL Overview of CAMEL Protocols
    Document Part Number: P_EXCL_CAMEL_UG_2.5 COPYRIGHT Copyright © 2003 IntelliNet Technologies, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means electronic or mechanical, including photocopying and recording for any purpose other than the reader’s personal use without the written permission of IntelliNet Technologies, Inc. Information in this document is subject to change without notice. IntelliNet Technologies 1990 W. New Haven Ave., Suite 307 Melbourne, FL 32904 U.S.A. Phone: +1 321 726 0686 Fax: +1 321 726 0683 Web site: www.intellinet-tech.com TRADEMARKS IntelliNet Technologies and the IntelliNet Technologies logo are trademarks of IntelliNet Technologies, Inc. Other brands and their products are registered trademarks or trademarks of their respective owners. 2 CAMEL User’s Guide Revision History Revision Date Notes Rev. 1.0 7-9-2003 Begin document modification for Lucent Excel (P. Arteaga) Rev. 2.0 7-30-2003 Contents of the document reorganized per Gururaj and Santanu (Shobha). Rev. 2.1 9-10-2003 Added details of every message (Invoke and Response) along with the associated parameters and the header files in Chapter 3 (Shobha). Rev. 2.2 9-11-2003 Updated Chapter 5 (Shobha). Rev. 2.3 9-15-2003 Added licensing section (Shobha). Rev. 2.4 11-07-2003 Added section Building and Running CAMEL Application on HP-UX (Shobha). Rev. 2.5 11-10-2003 Added section Building and Running CAMEL Application on Linux (Shobha). 3 CAMEL User’s Guide Contents Revision
    [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]
  • (TISPAN); IP Multimedia Subsystem (IMS); Functional Architecture
    Final draft ETSI ES 282 007 V1.1.1 (2006-03) ETSI Standard Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture 2 Final draft ETSI ES 282 007 V1.1.1 (2006-03) Reference DES/TISPAN-02029-NGN-R1 Keywords architecture, functional, multimedia, system ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - 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 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]