The Intelligent Network: A Joint Study by Bell Atlantic, IBM and Siemens

301 Pages·1989·9.118 MB·English

by  Wolf-Dietrich Ambrosch, Anthony Maher, Barry Sasscer (auth.), Wolf-Dietrich Ambrosch, Anthony Maher, Barry Sasscer (eds.)

W. D. Ambrosch A. Maher B. Sasscer (Eds.)
The Intelligent Network
A Joint Study by Bell Atlantic,
IBM and Siemens
With 48 Figures
Springer-Verlag
Berlin Heidelberg New York
London Paris Tokyo
Wolf-Dietrich Ambrosch
IBM Deutschland GmbH
Pascalstrasse 100
D-7000 Stuttgart 80
Anthony Maher
Siemens AG
Wittelsbacher Platz
D-8000 Munchen 1
Barry Sasscer
Bell Atlantic International
1300 N., 17th Street, Suite 1510
Arlington, VA 22209, USA
This document describes the results of a conceptual research study. This document does not
commit Bell Atlantic International Inc., IBM Deutschland GmbH, or Siemens AG to the
development of any product, service, requirements, or interconnection standard. This document
should not be construed as a suggestion to any manufacturer to modify or change any of its
products. Neither does this document commit Bell Atlantic, IBM, or Siemens to purchase any
product or service. No claim, expressed or implied, is made by Bell Atlantic, IBM, or Siemens
concerning the accuracy, completeness, or utility of the information contained herein, nor
concerning the technical feasibility or economic viability of the concepts described herein. No
representations of warranties, expressed or implied, are made with respect to the accuracy,
completeness, or utility of the information set forth herein. Liability to anyone arising out of use
or reliance upon any information set forth herein is expressly denied.
Bell Atlantic, IBM and Siemens reserve the rights to independently revise the information
contained herein. Nothing contained herein shall be construed as conferring by implication,
estoppel or otherwise any license or right under any patent, whether or not the use of any
information herein necessarily employs an invention of any existing or later issued patent.
Bell Atlantic's participation in this study was confined to reviewing generic feature requirements
for the Intelligent Network, describing pertinent features of Intelligent Network applications
software, and surveying marketing opportunities for the Intelligent Network. This publication is
not intended to constitute an endorsement by Bell Atlantic of the products or services of any
person or company.
ISBN-13: 978-3-540-50897-7 e-ISBN-13: 978-3-642-46663-2
DOl: 10.1007/978-3-642-46663-2
This work is subject to copyright. All rights are reserved, whether the whole or part of the
material is concerned, specifically the rights of translation, reprinting, re-use of illustrations,
recitation, broadcasting, reproduction on microfilms or in other ways, and storage in data
banks. Duplication of this publication or parts thereof is only permitted under the provisions of
the German Copyright Law of September 9, 1965, in its version of June 24, 1985, and a
copyright fee must always be paid. Violations fall under the prosecution act of the German
Copyright Law.
© Springer-Verlag Berlin Heidelberg 1989
The use of registered names, trademarks, etc. in this publication does not imply, even in the
absence of a specific statement, that such names are exempt from the relevant protective laws
and regulations and therefore free for general use.
2145/3140-54321 - Printed on acid-free paper
Preface
This report examines the findings of a study by Bell Atlantic, IBM, and Siemens
which investigated the role of the Intelligent Network in telecommunications. It
considers current trends and future developments, on a national and international
level.
This report defines and describes the concept of the Intelligent Network and
considers the operating requirements (including the hardware and software) and the
types of service a network user can expect.
Concepts, definitions, and terminology reflect the status of the Intelligent
Network in 1988. Actual implementation may differ due to the constantly changing
environment, new requirements, and experiences with existing solutions.
The report is divided into six parts:
Part 1 introduces the concept of the Intelligent Network, and describes elements
common to alLIN services. It considers the application program and network
management requirements, and provides examples of the hardware and software
proposed for implementing the network.
Parts 2 through 6 include detailed descriptions of specific IN services. In each
part there is a functional service description and an application description.
The reader is expected to have a general knowledge and understanding of
existing telecommunication networks.
A bibliography, glossary, and all appendices referred to in this report are
contained in the back of the document.
Contents
Introduction ............................. 1
Part 1. Overview of the Intelligent Network 3
Chapter 1. The Intelligent Network .......... . 5
1.1 IN Architecture and Capabilities 5
1.1.1 IN Goals ................... . 6
1.1.2 IN Technical Overview .......................... 8
1.2 IN Definition ............................... 9
1.2.1 IN Elements ............................... . 9
1.2.2 An IN Service Example ........................ . 12
1.3 IN"User Programmability ....................... . 14
1.4 IN Introduction Scenarios ...................... . 15
1.4.1 The Model .............................. . 15
1.4.2 Introduction Scenarios ........ . ..... . 17
1.5 IN Architecture Validation .................... . 19
Chapter 2. Functional Characteristics Common to Selected IN Services ... . 22
2.1 Overview ................................. . 22
2.2 Methodology .............................. . 22
2.3 Summary of Findings ......................... . 23
2.4 Standards ................................ . 24
2.5 Service Interaction ........................... . 24
2.5.1 Service User ................ .. 24
2.5.2 Service Subscriber ............. . 25
2.5.3 SMS Access Instrument ..... . 25
2.5.4 Network Operator ........................... . 26
2.6 Billing ..................... . ........... . 27
2.6.1 SSP ......... . ................... . 27
2.6.2 SCP .................................... . 27
2.6.3 SMS ................................... . 27
2.7 Service. Logic .............................. . 28
2.8 Databases ................................ . 31
2.8.1 Size .................................... . 31
VIII Contents
2.8.2 Database Integrity Requirements 32
2.8.3 Location of Databases ... 32
2.8.4 Database Administration 33
2.9 Transaction Rate Estimates 34
2.9.1 Methodology ....... . 34
2.9.2 Transactions Between SMS and its Users 35
2.9.3 SMS-SCP Transaction Rates 35
2.9.4 SCP- SSP Transaction Rates 35
2.10 Measurement Requirements 36
2.10.1 SSP 36
2.10.2 SCP ............. . 38
2.10.3 SMS ............ . 39
2.11 Performance and Dynamic Requirements 39
2.11.1 Response Time ......... . 39
2.11.2 Response Times for IN Elements 40
2.11.3 Overload Handling ....... . 43
2.12 Availability Requirements and Objectives 44
2.13 National Considerations 45
2.14 Future Considerations ...... . 45
Chapter 3. Network and Service Management 47
3.1 Overview ...... . 47
3.2 Methodology 48
3.2.1 Summary of Findings 48
3.3 NSMS Requirements 49
3.3.1 NSMS Global Qualities 49
3.3.2 Basic Operations, Administration and Management Functions 49
3.3.3 Network Management Users ......... . 52
3.4 Switching Layer and the OSS--an Example ....... . 53
3.5 Signaling Network and the SEAS ............. . 54
3.5.1 Management Functions Related to the Signaling Network 54
3.6 IN-Services and the SMS ....... . 57
3.6.1 Service Management System Overview ......... . 58'
3.6.2 SMS Function Description ................ . 59
3.7 Administrative System Functions and IN Requirements 62
3.7.1 IN- Wide Service Management Examples 62
3.8 Trends ............... . 63
3.8.1 Evolving Operations Architecture 63
Chapter 4. Network Components ...... . 66
4.1 Main Objectives of the IN Architecture 66
4.2 Network Topology ........... . 66
4.2.1 Performance and Throughput Requirements 67
4.2.2 Availability Requirements 68
4.2.3 IN Architecture ...... . 69
4.3 Service Control Point (SCP) 73
Contents IX
4.3.1 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 73
4.3.2 SCP Architecture ............................. 76
4.4 Signaling Transfer Point (STP) . . . . . . . . . . . . . . . . . . . .. 87
4.4.1 Functional STP Requirements ..................... 88
4.4.2 CCS7 Network Architecture and IN ................. 88
4.5 Service Switching Point (SSP) ..................... 94
4.6 Future Considerations .......................... 100
Part 2. Green Number Service 103
Chapter 5. GNS Service Description ...................... . 104
5.1 Overview ................................ . 104
5.2 Functional Description ....................... . 105
5.3 Standards ................................ . 107
5.4 Service Interaction ........................... . 107
5.5 Billing .................................. . 108
5.6 Service Logic .............................. . 109
5.6.1 Distribution ............................. . 109
5.6.2 Functional Flow ........................... . 109
5.7 Traffic Measurement Requirements ................ . 110
5.8 Dynamic Requirements and Performance . . . . . . . . . . . . 112
5.9 National Dependencies ......... . ......... . 112
5.10 Future Considerations ........................ . 113
Chapter 6. GNS Application Description ..................... . 114
6.1 Functional Requirements and Allocation ............. . 114
6.2 Functional Units in the EWSD SSP ............... . 117
6.3 Administrative Units in SSP 120
6.4 Functional Units in SCP 121
6.5 Administrative Units in SCP .................... . 129
Part 3. Alternate Billing Service 133
Chapter 7. ABS Service Description 134
7.1 Overview ........ . 134
7.2 Functional Description 135
7.3 Standards ....... . 137
7.4 Service Interaction ........... . . . . . . . . . . . . 137
7.5 Billing ................................ . 138
7.6 Service Logic ......................... . 139
7.6.1 Distribution .......................... . 139
7.6.2 Functional Flow ....................... . 140
7.7 Traffic Measurements Requirements ... 143
7.8 Dynamic Requirements and Performance 144
X Contents
7.9 National Dependencies 144
7.10 Future Considerations 144
Chapter 8. ADS Application Description ...................... 146
8.1 Functional Requirements and Allocation .............. 146
8.2 Functional Units in SSP ........................ 149
8.3 Administrative Units in SSP ...................... 152
8.4 Functional Units in SCP ....................... 153
8.5 Administrative Units in SCP ...................... 157
Part 4. Emergency Response Service .... 161
Chapter 9. ERS Service Description ........................ . 162
9.1 Overview ................................. . 162
9.2 Functional Description ........................ . 164
9.3 Standards ................................ . 166
9.4 Service Interaction ........................... . 167
9.5 Billing .............................. . 169
9.6 Service Logic .............................. . 169
9.6.1 Distribution .............................. . 169
9.6.2 Functional Flow ........................... . 170
9.7 Traffic Measurement Requirements ................ . 172
9.8 Dynamic Requirements and Performance ............ . 172
9.9 National Dependencies ...................... . 172
9.10 Future Considerations ....................... . 176
Chapter 10. ERS Application Description ....... . 178
10.1 Functional Requirements and Allocation 178
10.2 Functional Units·in SSP ......... . 181
10.3 Administrative Units in SSP 184
10.4 Functional Units in SCP ......... . 184
10.5 Administrative Units in SCP ......... . 194
Part 5. Private Virtual Network 199
Chapter 11. PVN Service Description ....................... . 200
11.1 Overview .............................. . 200
11.2 Functional Description ........................ . 202
11.3 Standards ................................ . 215
11.4 Service Interaction .. 216
11.5 Billing ..... . 217
11.6 Service Logic 218
11.6.1 Distribution 218
11.6.2 Functional Flow 221
Contents XI
11.7 Traffic Measurement Requirements .................. 226
11.8 Dynamic Requirements and Performance .............. 228
Chapter 12. PVN Application Description .................... . 230
12.1 Functional Requirements and Allocation ............. . 230
12.2 Functional Units in SSP ....................... . 241
12.3 Administrative Units in SSP 248
12.4 Functional Units in SCP 250
12.5 Administrative Units in SCP ..................... . 255
Part 6. Area Wide Centrex 257
Chapter 13. A WC Service Description ....................... . 258
13.1 Overview ................................. . 258
13.2 Functional Description ........................ . 259
13.3 Standards ................................ . 263
13.4 Service Interaction ........................... . 263
13.5 Billing .................................. . 265
13.6 Service Logic .............................. . 266
13.6.1 Distribution ............................... . 266
13.6.2 Functional Flow 267
13.7 Traffic Measurement Requirements ................. . 278
13.8 Dynamic Requirements and Performance ............. . 280
13.9 National Dependencies ........................ . 280
13.10 Future Considerations ......................... . 280
Appendix A. Supplementary Services 281
Appendix B. Bellcore Preliminary-Defined Functional
Components and Requests ................. 283
Glossary ....................................... 285
Bibliography .................................... 293
List of Figures
1. Access Lines and Corporate Revenue, 19852 ...- -. . . . . . . . . . . . . .. 7
2. IN Components ...........................:..... 8
3. IN Elements .................................... lO
4. Non-IN GNS Service ....... :.......... . . . . . . . . . . . .. 12
5. IN-Based Green Number Service ....................... . 13
6. IN-Pay-Per-View ................................ . 20
7. Database Distribution ............................. . 33
8. STP Message Delay13 ............................. . 40
9. SCP Response Time of SMS Generic Messages ............. . 41
10. SCP Response Time for SSP Messages (Service Specific) ........ . 42
11. Operation Systems within the United States' Intelligent Network
Operations .................................... . 50
12. Network User Categories ........................... . 51
13. Operations System Users ......... . ............ . 52
14. SEAS Control of CCS7 Network ...... . . . . . . . . . . . . . . 55
15. SMS Overview ................ . 58
16. Protocol Architecture in OA&M Networks 65
17. IN User-Interfaces 69
18. IN Components and their Related Interfaces ................ . 71
19. Basic Data Flow Between an SSP and SCP (for GNS Without Prompting
Option) .................................. 72
20. SCP Major Components ....................... 77
21. SCP Software Components ..................... 80
22. General STP Architecture for the EWSD ............. 90
23. Possible IN CCS7 Architecture for the EWSD .......... 91
24. Architecture for the EWSD ..............- ............. 92
25. Common Channel Network Control for the EWSD 93
26. CPl13 Coordination Processor for the EWSD ........... 94
27. The Operating System ......................... 95
28. SSP Components ............................ 96
29. EWSD System Structure and Information and Message Flow for the GNS 99
30. GNS Functional Flow-GNS without Prompting Option ...... 111
31. Functional Flow of ABS with Collect Call, Third Party Billing, and
Manual Calling Card Billing ....................... 141
32. Functional Flow of ABS with Automatic Calling Card Billing ...... 142