In Overview

Intelligent Network Overview STUDENT GUIDE
Issue 8.2 May 1998 IN1000

Lucent Technologies Proprietary This document contains proprietary information of Lucent Technologies and is not to be disclosed or used except in accordance with applicable agreements Copyright 1998 Lucent Technologies Unpublished and Not for Publication All Rights Reserved Printed in U.S.A.
Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change.
Trademarks
1A ESS and 4ESS are trademark of Lucent Technologies, Inc. 5ESS is a registered trademark of Lucent Technologies, Inc. ANS is a registered trademark of Lucent Technologies, Inc. in the United states and other countries. BaseWorX is a trademark of AT&T. BSD is a trademark of Berkeley Software Design, Inc. Centronics is a registered trademark of Centronics Data Computer Corporation. Comsphere is a registered trademark of AT&T. DiskSuite is a trademark of Sun Microsystems, Inc. DMS is a registered trademark of Northern Telecom Limited. EMX is a registered trademark of Motorola, Inc. ESS is a trademark of Lucent Technologies, Inc. Ethernet is a registered trademark of Xerox Corporation. MAXELL is a trademark of Maxell Corporation of America. MIPS is a registered trademark of MIPS Computer Systems, Inc. NetMinder is a registered trademark of Lucent Technologies in various countries outside the United States NonStop V+ is a trademark of Tandem Computers, Inc. ODIN is a trademark of Lucent Technologies, Inc. OPEN LOOK is a registered trademark of Novell, Inc. OpenWindows is a trademark of Sun Microsystems, Inc. ORACLE is a registered trademark of Oracle Systems Corporation. Pentium is a registered trademark of Intel Corporation. PostScript is a registered trademark of Adobe Systems, Inc. SEAS is a trademark of Bell Communications Research, Inc. (Bellcore) Solaris is a registered trademark of Sun Microsystems, Inc. Solstice is a trademark of Sun Microsystems, Inc. SPARC is a registered trademark of SPARC International, Inc. SPARCompiler is a trademark of SPARC International, Inc., licensed exclusively to Sun Microsystems, Inc. SPARCworks is a trademark of SPARC International, Inc., licensed exclusively to Sun Microsystems, Inc. SQL Forms is a registered trademark of Oracle Systems Corporation. SQL Plus is a registered trademark of Oracle Systems Corporation. StarServer is a registered trademark of Lucent Technologies, Inc. Sun and SunOS are trademarks of Sun Microsystems, Inc. SunPro is a trademark of Sun Microsystems, Inc. SunSoft is a trademark of Sun Microsystems, Inc. Sun Microsystems is a registered trademark of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. X Window System is a trademark of the Massachusetts Institute of Technology.
Ordering Information
To order this document, s in countries outside the U.S. and Canada, call your Lucent Technologies Market Manager
Lucent Technologies Proprietary See notice on rst page
COURSE DESCRIPTION
This course is designed to provide introductory information on the Lucent Technologies Intelligent Network. Students learn about services and call routing features provided by the network. Students are introduced to the major elements within the network:
s s s s
Signal Transfer Point, Service Control Point (SCP) Signalling Transfer Point (STP) Service Management System (SMS) Service Creation Environment (SCE).
Students are also introduced to Common Channel Signalling and call routing through the Intelligent Network. Particular emphasis is given to the way in which services and service features work, giving students the broad IN background they will need when selling, building or maintaining services.
Issue 8.2
COURSE OBJECTIVES
This course is designed to enable students to:
s s s s s
Understand the concepts of Intelligent Networks Understand the fundamentals of IN call processing Name the Lucent Technologies network elements that process calls. Describe the functions of the network elements. Describe Intelligent Network services and features, such as Advanced Routing Services, Virtual Private Network (VPN), Televoting and Calling Card. The service features that make up these services will be described and students will be given a broad understanding of how the services and service features work. Describe the role that Common Channel Signalling plays in processing an IN call. Describe Call routing procedures common to all Intelligent Network calls.
ii
Issue 8.2
TARGET AUDIENCE
This course is designed for anyone new to the Lucent Technologies Intelligent Network and anyone who needs a general overview of how it works.
Issue 8.2
iii
COURSE CONTENTS
Lesson 1 INTELLIGENT NETWORK OVERVIEW Lesson 2 INTELLIGENT NETWORK SERVICES Lesson 3 NETWORK ELEMENTS Lesson 4 IN CCS NO. 7 OVERVIEW Appendix A INAP MESSAGES Appendix B GLOSSARY
iv
Issue 8.2
INTELLIGENT NETWORK OVERVIEW
1
1-1
1-1 1-1 1-2
Contents
Lesson Overview
s s s
Purpose Objectives Documentation
Users and Providers of IN Services

s
1-5
1-5
Advantages of IN
s
1-7
1-7
Advantages to the network provider
Advantages to the service provider Advantages to the service subscriber Advantages to the IN user IN Network Elements Brief History IN Call Example Functional Model Implementation of The Functional Model The Basic Call State Model The BCSM Including Detection Points
1-9 1-11 1-13 1-15 1-17 1-19 1-21 1-23 1-25 1-27
Issue 8.2 1-i
Types of Detection Points
1-29
Arming Static Detection Points

s
1-31
1-31
Static DP Criteria Table
IN Call Example Using the Basic Call State Model Service Control Function
s
1-33 1-35
1-35
Definition
SCP Deployment
s s
1-37
1-37 1-37
Mated Pairs Stand Alone SCPs
IN Call Example Using the SCF Service Management Function

s s
1-39 1-41
1-41 1-41
Definition Functions
Service Creation Environment Function

s s s
1-43
1-43 1-43 1-43
Definition Functions Service Packages
Service Creation Example Decision Graph The SRF

s s
1-45 1-47 1-49

1-49 1-49
Definition Functions
Configuration Operations Support Systems

s
1-51 1-53
1-53
Functions
Summary NOTES Exercise
1-55 1-56 1-57
1-ii
Issue 8.2
Lesson Overview
Purpose
This lesson provides a high level overview of the Intelligent Network as dened by the ITU-T and ETSI standardization bodies. The following items are discussed:
s s s s
The equipment needed for an Intelligent Network The Intelligent Network functional model The concept of triggering IN calls Intelligent network building blocks
Objectives
On completion of this lesson participants will be able to:

s s
state the advantages of Intelligent Networks understand which types of call are processed by an intelligent network understand the fundamentals of IN call processing dene the IN functional model and its implementation dene the concept of a detection point dene the concept of a building block list the hardware and related equipment used in an Intelligent Network. dene the IN functional model and its implementation. dene the purpose of the SCF. dene the function of Call Gapping. dene the function of Mated Pairs.
s s s s s
s s s s
Issue 8.2
1-1
s s s s
dene the function of the SCEF. dene the purpose of the SMF. dene the function of the SRF. dene the purpose of a system alarm. ITU-T Recommendations Q.121x series ETSI Specication ETS 300 374-1
Documentation
s s
1-2
Issue 8.2
Issue 8.2
1-3
Network Provider Service Provider Service Subscriber Calling Subscriber, Calling Party or A-Party Called Party or B-Party
Figure 1-1.
1-4
Issue 8.2

The Intelligent Network (IN) is an extension to the existing telephone network. This network is organized so that telephone calls received by the IN are interrupted to query a database in order to determine what to do with the call. The call can then be re-routed based on a number of predened conditions such as time of day or day of the week. Alternatively, an announcement can be played or information can be collected from the caller.
Throughout this course the following terms are used to refer to the users and providers of the Intelligent Network:
s
Network Provider the company that is responsible for the telephony network planning and maintenance (commonly known as the PTT (Post, Telephone and Telegraph). Service Provider the company or institution that purchases IN services from the network provider and provides it to Service Subscribers. Service Subscriber the company, institution or individual that purchases IN services from the service provider. For some services, such as Calling Card, the service subscriber is an individual. For others, such as Televoting or VPN, it is an organization. Calling Subscriber, Calling Party or A-Party the person who dials the IN number. Called Party or B-Party the person who answers the call.
The Calling Party and Called Party may collectively be referred as users.
Issue 8.2
1-5
Advantages to the network provider:
Additional network trafc Higher call completion rates
Figure 1-2.
Advantages of IN
1-6
Issue 8.2
Advantages of IN
Because of the structure and implementation of the IN in the existing telephony network, there are advantages to both users and providers of the IN:
Advantages to the network provider
IN services can signicantly increase the revenue generating potential of the public telephone network. Revenue derived from the IN falls into two general categories:
s
Additional network trafc IN services stimulate the use of the telephone network for new applications. This results in an increase in the number of telephone calls made. Higher call completion rates IN services target calls to destinations where they are most likely to be answered. The result is an increase in the number of telephone calls for which revenue is collected.
Issue 8.2
1-7
Advantages to the service provider:

s
Flexible and rapid deployment of new services Wide range of services New tariffed features
Figure 1-3.
Advantages to the Service Provider
1-8
Issue 8.2
Advantages to the service provider

s
IN gives service providers the exibility to create, customize and/or deploy new services rapidly. IN supports a wide range of advanced services, for example Calling Card, Televoting.
Issue 8.2
1-9
Advantages to the service subscriber:

s
Flexible charging Call queuing Flexibility in who maintains the database
Figure 1-4.
Advantages to the Service Subscriber
1-10
Issue 8.2
Advantages to the service subscriber

s
Due to the exible charging capabilities of IN the service subscriber can choose who pays for a call: the calling party the called party the service subscriber a combination of all three For example, in the freephone service the called party, who happens to be the service subscriber, pays. In the VPN service, the service subscriber pays.
IN has the ability to queue calls within the IN network. This allows the service subscriber to save personnel costs by queuing calls to a small number of personnel. IN allows the service subscriber to maintain their own data in the IN database, as well as allowing the service provider to maintain the database for the service subscriber. If the service subscribers data is dynamic it is difcult for the service provider to keep up with all the changes in the database so it is better for the service subscriber to maintain the database. Using IN it is possible to re-route calls that are busy or not answered, by routing to an alternative destination. The service subscriber also gains all the advantages described for the service provider.
Issue 8.2
1-11
Advantages to the IN user:

s
Ease of access Facilities of advanced services
Figure 1-5.
Advantages to the IN User
1-12
Issue 8.2
Advantages to the IN user

s
Easy access to service subscribers The service providers can use one nationwide telephone number and reroute calling subscribers to the actual telephone number of this provider. If the service provider has a number of ofces throughout the country, the actual re-routing number can vary depending on for example the geographical location of the calling subscriber. Facilities of advanced services The value of IN is the advanced services it makes available to callers. This is how users perceive the network.
Issue 8.2
1-13
= CCS No. 7 Signaling Link = Voice Trunk
SCE
SMS
X.25
SCP
STP
SCP
SSP
CCS
SSP
IP
CCS
CCS
Public Telephone Network
Legend: CCS = Common Channel Signaling IP = Intelligent Peripheral SCE = Service Creation Environment SCP = Service Control Point
SMS SSP STP X.25
= Service Management System = Service Switching Point = Signaling Transfer Point = ITU-T X.25 Recommendation
Figure 1-6.
IN Network Elements
1-14
Issue 8.2
IN Network Elements
IN has been in use for many years and is integrated in various ways within the public telephone network. Figure 1-6 is an example showing a telephony network supporting IN services. The network consists of several network elements. An explanation of these network elements can be found in the following paragraphs. SSP - Service Switching Point The SSP is a telephone exchange that recognizes IN calls. If a call is an IN call, the call is temporarily suspended, and extra information for the call is queried from the SCP. SCP - Service Control Point The SCP controls the database that is queried by the SSP for call information. It uses it to decide where the call should be routed to. IP - Intelligent Peripheral The IP is used when interaction between the SCP and the caller who dialed the IN telephone number is needed. It can also interact with the calling party. The interaction may be either via the SSF or direct. According to the ITU-T specication, the IP is capable of playing announcements, collecting digits, repeating the collected digits, recognizing voice and generating tones. The functions actually implemented depend on the supplier of the IP equipment. SCE - Service Creation Environment The creation of new IN services or modication of existing services is done on the SCE. The created services are downloaded to the SCP. SMS - Service Management System The SMS is used to provision services on the SCP. It provides a platform for administration and backup of the IN services. STP - Signaling Transfer Point The signaling transfer point is often used as a connection between the different SSPs and SCPs. The STP provides the capability of transferring signaling messages between the SSP and SCP.
Issue 8.2
1-15
Mapping old and new network element names SCP SSP IP

Network element nomenclature mapping
NCP ACP NSCX
Figure 1-7.
Brief History
1-16
Issue 8.2
Brief History
One of the earliest needs for intelligent services was the use of freephone calls. Whenever a freephone number was dialed the number was routed to its destination without the calling party having to pay charges for the call. The intelligence needed to recognize a freephone number was available in one of the exchanges used to route the call. In later years the need for additional services became evident. The solution to this problem was the introduction of one of the earliest intelligent networks. The exchange that recognized an IN call was called the Action Control Point (ACP). The ACP was able to re-route calls either using the information available within its own database or using information available in a separate, centralized database called the Network Control Point (NCP). If interaction between the NCP and the calling party was needed, the Network Services Complex (NSCX) was used. Whenever the ACP, NCP or NSCX needed to interact signaling messages were sent. Three of the most commonly used signaling protocols between the ACP and NCP were DCIS6, ECIS6 and CCS No. 7. The New Generation IN covered in this course is dened by the world standards organization ITU-T (International Telecommunications Union Telecommunication Standardization Sector), together with the European standards organization ETSI (European Telecommunications Standards Institute). This new version of IN does not use the names ACP, NCP or NSCX. The the SSP has replaced the ACP, the SCP has replaced the NCP and the IP has replaced NSCX. Through the years many terms have been introduced to explain the services provided by IN. A few of these services are listed and briey described below:
s
Basic Freephone Service The Basic Freephone service allows a service subscriber to have an IN number that routes all calls to one destination. The service subscriber pays for calls. Destination numbers are available on the exchange itself. The SCP is not queried to re-route these calls. Single Destination Number Service The Single Destination Number Service allows a service subscriber to have an IN number that will be re-routed by the SCP to one single nal destination. Advanced Freephone Service The Advanced Freephone Service allows a service subscriber to have an IN number re-routed by the SCP to one of several different destinations. The number to which this call is re-routed depends on, for example, the time of day, day of the week, date, or the calling subscribers geographical location.
Issue 8.2
1-17
CP SCP
STP
3 Request for Information
4 Re-Routing Information
SSP
SSP
0800-123123
Public Telephone Network Called Number 0800-123123 1 PSTN Number 022-4566543

6
PBX Calling Subscriber Service Provider
Figure 1-8.
IN Call Example
1-18
Issue 8.2
IN Call Example
In a country-wide advertising campaign an insurance company is giving a 10% discount to new customers. The company tells everybody to dial 0800-123123 and sign up as a customer. The insurance company has requested this telephone number from the service provider. The network provider has to translate the 0800-number to the actual telephone number of the insurance company (022-4566543). In Figure 1-8 an example is given of a person who calls the insurance company. The call is divided into the following stages: 1. The calling subscriber dials 0800-123123. 2. The call is routed through the Public Switched Telephone Network (PSTN) and sent to an exchange where more is known about this 0800-number (this exchange is the SSP). 3. The SSP exchange recognizes the call as an IN call and queries the SCP for more information. 4. The SCP responds by sending re-routing information (022-4566543) to the SSP. 5. After receiving this data the SSP connects the calling subscriber to the new received number using the PSTN. 6. The PSTN connects the call to the Private Branch Exchange (PBX) of the insurance company. The actual call is connected from the PSTN to the SSP and back again.
Issue 8.2
1-19
SCEF
SMF
SCF
SRF
SSF CCF
SSF CCF CCF
Figure 1-9.
Functional Model
1-20
Issue 8.2
Functional Model
ITU-T has dened a standard functional model for the Intelligent Network. The diagram opposite shows the functional entities and the relationships between them. The terminology of this model is often used in IN system documentation. The functional entities are as follows:
s
CCF (Call Control Function) This provides the basic call and connection handling in the exchange. It establishes, manipulates and releases a call. It recognizes IN calls and enables the SSF (see below) to take over processing of the call. It represents the functionality of the traditional switch. SSF (Service Switching Function) The SSF enables interaction between the CCF and the SCF. It recognizes service control triggers, through which it recognizes IN calls. It also manages signaling between the CCF and the SCF. SCF (Service Control Function) The SCF directs call control functions during the processing of an IN call. It contains the IN service call processing logic (or service provider plan) stored in centralized databases which species how to handle an IN service request. It interacts with the SSF and the SRF to obtain information (service or user data) required to process an IN call. The SCF and the SSF have a master-slave relationship; the SCF is the master and the SSF is the slave. Sometimes the SCF is split into two functional entities: SDF (Service Data Function) the database SCF (Service Control Function) Call processing and other logic
SRF (Specialized Resource Function) The SRF is used whenever an IN call requires direct interaction with the calling party in the speech path. It contains the logic and processing capability to send, receive and convert information. All SRF actions for a given call are determined by commands received from the SCF via the SSF. Examples of SRF actions are: The playing of a standard or customized announcement The collection of digits requested in an announcement (post-dialing digits)
SCEF (Service Creation Environment Function) This function enables service developers to develop service logic. SMF (Service Management Function) This function allows the provision and distribution of databases to the SCF equipment.
Issue 8.2
1-21
SCE
SCEF
SMS
SMF
SCP
SCF
SRF SSF
SSF
SRF
IP
SSP
CCF CCF
SSP
IP
PSTN
Figure 1-10. Implementation of the Functional Model
1-22
Issue 8.2
Implementation of The Functional Model

The functional model denes the entities in terms of functions and not in terms of physical network elements. The network elements which typically correspond to the different functional entities are as follows: SCF SRF CCF/SSF SCEF SMF SCP (Service Control Point) or NCP (Network Control Point) IP (Intelligent Peripheral) SSP (Service Switching Point) or ACP (ACtion Point) SCE (Service Creation Environment) SMS (Service Management System)
More than one of these functional entities may be implemented on one physical network element. Note that an IN need not consist entirely of equipment from a single vendor. An example network implementation of the IN functional model is shown in the gure opposite. The SSFs terminate trunks. They communicate with the SCF via a Common Channel Signaling (CCS) No. 7 network, using INAP (Intelligent Network Application Part) message.
Issue 8.2
1-23
Abandon
1. O_Null & Auth._Orig._Attempt
Resources released
2. Collect_Information
Time-out
3. Analyse_Information
Invalid information
4. Routing & Alerting
Route failure Authorization failure Busy No answer
5. O_Active
Disconnect
Exception
: Basic call transition : Basic call stage
Figure 1-11.
The Basic Call State Model
1-24
Issue 8.2
The Basic Call State Model

Any telephone call goes through a number of different stages, called states or Points-in-Call, when it enters or originates in a CCF. For the ITU-T specication each originating call follows the Basic Call State Model (BCSM). This is shown in Figure 1-11 and has the following states (the names in italics are the ITU-T terms, and those in parentheses are Lucent terms): 1. O_Null and Authorize_Origination_Attempt (Idle state) This is the normal, on-hook state, when no call is being made. This call state is left when an exchange trunk or line is activated as a result of a call or service request. For ISDN calls line activation implies the receipt of a SETUP message. For CCS No. 7 it implies the receipt of an Initial Address Message (IAM). 2. Collect_Information (Digit collection) The digits sent by the originating party are being collected. This call state is left when all digits have been received, the originating party abandons the call, or an error occurs during digit collection (for example, a time-out occurred). 3. Analyse_Information (Digit analysis) The dialed digits are being analyzed. This call state is left when digit analysis is successful, the originating party abandons the call, or an error occurs during digit analysis (for example, an invalid dial string is received). 4. Routing and Alerting (Routing and Terminal Allocation) RTA (Routing and Terminal Allocation) is performed, i.e. the call is routed to the B-Partys phone. This call state is left when: the terminating party goes off hook the originating party abandons the call the RTA fails (for example, due to network congestion), authority of the originating party to place the call is denied the called party is busy the called party does not answer the call within a specied time. 5. O_Active (Active state) The call is accepted and answered by the terminating party, and the two parties are talking to each other. This call state is left when a disconnect indication (for example, on hook, Q.931 disconnect message or CCS No. 7 release message) is received from the originating or terminating party, or a connection failure occurs.
Issue 8.2
1-25
Abandon
Resources released
DP 10 DP 1
Time-out
DP 2
Invalid information
DP 3
DP 4
Route failure Authorization failure

DP 5
Busy
DP 6 DP 7
No answer
DP 9
5. O_Active
Disconnect
DP 8 : Basic call transition : Additional IN transition DP x : Detection point x : Basic call stage
Figure 1-12.
The BCSM Including Detection Points
1-26
Issue 8.2

For calls to be recognized as IN calls, and to allow the SCF to deal with IN calls the Basic Call State Model has been expanded. During the transition from the idle to the active call state in the basic call handling process, instructions are sent to the CCF. The CCF will then either:
s s
interrupt the call and wait for further instructions from the SCF report the occurrence of an event to the SCF and continue processing the call
The point in the call at which call processing in the CCF is interrupted to await instructions or to report an event is called a detection point. Before a detection point can be used in this way, it must be activated or armed. This enables it to notify the SCF, via the SSF, that call processing has reached a certain call state. This provides the mechanism by which the SCF inuences subsequent call processing. If a detection point is not armed, the CCF continues call processing without involving the SCF. The different detection points are given in the basic call ow (or BCSM) in Figure 1-12. The following detection points are supported by the CCF: 1. Detection Point 1 (Orig_Attempt_Authorized) The call handling process has veried that the originating party is authorized to make specic types of calls for example: bearer service, and line restrictions. 2. Detection Point 2 (Collected_Info) The call handling process has collected the digits dialed by the originating party. 3. Detection Point 3 (Analysed_Info) The call handling process has collected all digits dialed by the originating party, performed digit analysis, and has determined the destination type. 4. Detection Point 4 (Route_Select_Failure) The call handling process has detected specic types of routing or setup failures. 5. Detection Point 5 (O_Called_Party_Busy) The call handling process has detected that the terminating party signaling has returned a busy indication. 6. Detection Point 6 (O_No_Answer) The call handling process has detected expiration of the answer timer or has received an indication of no answer from the succeeding exchange. 7. Detection Point 7 (O_Answer) The call handling process has detected that the terminating party has answered the call.
Issue 8.2
1-27
Abandon
Resources released
DP 10 DP 1
Time-out
DP 2
Invalid information
DP 3
DP 4
Route failure Authorization failure

DP 5
Busy
DP 6 DP 7
No answer
DP 9
5. O_Active
Disconnect
DP 8 : Basic call transition : Additional IN transition DP x : Detection point x : Basic call stage
Figure 1-13.
1-28
Issue 8.2
8. Detection Point 8 (O_Mid_Call) The call handling process has detected a service/service feature request from the originating party, examples are DTMF digits, hook ash, and ISDN feature activation. 9. Detection Point 9 (O_Disconnect) The call handling process has detected an originating or terminating party disconnect after answering by the terminating party. 10. Detection Point 10 (O_Abandon) The call handling process has detected a disconnect prior to answer or busy indication from the terminating party.
Types of Detection Points
The detection points given in the Basic Call State Model can be armed in two ways:
s
Static Detection Points These detection points are provisioned in the SSF and cannot be changed on a per call basis. Also called Trigger Detection Points (TDP)
Dynamic Detection Points Dynamic detection points are armed on a per call basis by the SCF. The SCF uses them to request the SSF to notify it when some event has occurred, such as the fact that a call cannot be routed because the destination number is busy or has not answered. Also called Event Detection Points (EDP)
If the SCF needs to arm a detection point during a call, the it has to know that a call is in progress. This is only possible after it has received notication from the SSF that a call is in progress. The SSF does this by arming a static detection point. The static detection point causes a message to be sent to the SCF. The SCF can arm the Dynamic Detection Points in the return message.
Issue 8.2
1-29
Conditionally armed static DPs:

s
Static DP criteria:
Received number Calling party number Called party nature of address Cause value Class of service ISDN bearer capability
Criteria assigned on:

Individual basis Group basis Exchange basis
Unconditionally armed static DPs:

s
No Static DP criteria Assigned on: Individual basis Group basis Exchange
Figure 1-14.
1-30
Issue 8.2

Static detection points are armed in the CCF by maintenance personnel. ITU-T has dened a set of conditions that can be assigned to a detection point. If a call in the CCF follows the Basic Call State Model and a Detection Point is encountered, the CCF determines whether this particular call matches the criteria dened for the detection point. If the call matches the criteria then the detection point is triggered and the call is treated as an IN call.
Static DP Criteria Table
The static DP criteria are stored per DP in the Static DP criteria table. To determine whether the static DP criteria are met, the following parameters are examined to see whether they match corresponding values in the static DP criteria table:
s
Received number: the match may be based on the complete number of received digits or on a number of received digits starting from the rst dialed digit. Calling party number: the number of the calling subscriber. The match may be based on the complete calling party number or on a number of digits starting from the rst dialed digit. Called party nature of address (for example, international number or national number) Cause value (for example, terminating party busy at Detection Point 5) Class of service (for example, coin phone or ETSI ISDN) ISDN bearer capability (for example, SPEECH or B-Channel Packet Switching (BCHPS))
s s s
These criteria are assigned to a static DP on an individual basis (subscriber line, trunk group and subscriber trunk), on a group basis (PBX, Private Branch Exchange) or on an exchange basis. Besides these conditionally armed static DPs, there are also unconditionally armed static DPs. An unconditionally armed static DP is used to inform the SCF that the DP has been encountered without any further criteria having to be satised. Unconditionally armed static DPs are assigned on an individual basis, on a group basis or on an exchange basis.
Issue 8.2
1-31
CCF
1. O_Null & Auth ._Orig._Attempt
SSF
Detection Point Processing
SCF
DP1
DP2
3. Analyse_Information Static DP DP3 Trigger request instructions Instruction: request for DP5-R
Service Logic
New Number
DP3
Arm DP5-R
4. Route & Alerting Event request instructions Dynamic DP
DP5
Figure 1-15.
IN Call Example Using the Basic Call State Model
1-32
Issue 8.2
IN Call Example Using the Basic Call State Model

In a previous section an example scenario was given for an IN call to an insurance company. In Figure 1-15 the same example is used and expanded. The insurance company wants to reroute calls to another destination if the original number is busy. The IN call in Figure 1-15 uses the Basic Call State Model, Static and Dynamic Detection Points. The call ow is given in steps 1 to 8: 1. The originating subscriber dials an 0800-number. The call is routed to an SSF. 2. The CCF receives the call as an incoming call. 3. At the moment this call arrives, authorization (BCSM O_Null and Authorize_Origination_Attempt) checks are done. If these checks do not fail the CCF checks if DP1 is armed. If DP1 is not armed the call continues. 4. Next the CCF starts collecting the digits dialed by the originating subscriber (BCSM Collect_Information). If enough digits are received the CCF checks if DP2 is armed. If DP2 is not armed the call continues as normal. 5. When the CCF has received enough digits, the digits can be analyzed (BCSM Analyse_Information). If in the CCF DP3 has been conditionally armed so as to cause the CCF to interrupt all calls that start with the digits 0800 and request further instructions from the SCF, then it will send a message to the SCF. 6. The message is received by the SCF, the SCF retrieves the correct destination number from its database. To ensure that the call is answered the SCF can dynamically activate detection point 5 (busy). The new telephone number and a request to dynamically arm the detection points are sent back to the CCF. 7. The request to arm detection point 5 causes the CCF to arm the DP for this particular call (dynamic). The new received number causes the CCF to return to the Analyse_Information call state. 8. The new number is analyzed and routed (BCSM Routing and Alerting) to its nal destination. If the destination is busy this causes DP5 to be red. The CCF sends a message to the SCF again, now indicating that the user was busy. The SCF accesses the database again to determine what to do next (play an announcement, re-route the call again, disconnect). Steps 6 to 8 can be repeated until a telephone number has been found which is not busy.
Issue 8.2
1-33
Functions of the SCF:

s
Routing of calls Collecting measurements Sending of status and service maintenance messages to the SMF Network management controls Sending of billing information to the SSF
Figure 1-16.
Service Control Function
1-34
Issue 8.2
Service Control Function

Denition
The primary purpose of the Service Control Function is to serve as the networks call routing facility. It contains service control login and a database which stores Service Subscriber Records that determine routing for Intelligent Network Services. Other functions are:
s s
Trafc and network measurements are collected and sent to the SMF. Status information and service maintenance messages are sent to the SMF. The placement of network management controls on the dialed number or the number of the calling party, known as the Calling Line Identity (CLI). These controls are sent to the SSF to tell it to limit the number of incoming calls requiring the SCF. This is called call gapping. The purpose of call gapping is to prevent the SCF from becoming overloaded. This is done by reducing the number of queries sent to it. Sending of Billing Data to the SSF The SCF sends billing data to the SSF. The data is recorded at the SSF and later processed before being sent to the billed party.
Issue 8.2
1-35
Primary SCP: 0800-1000 to 0800-4999 Secondary SCP: 0800-5000 to 0800-9999
Primary SCP: 0800-5000 to 0800-9999 Secondary SCP: 0800-1000 to 0800-4999
MATED PAIRS SCP B
SCP A
STP
STP
SSP
SSP
0800-1000 to 0800-9999
SCP STP SSP STAND ALONE

Figure 1-17. SCP Deployment
STP SSP
1-36
Issue 8.2
SCP Deployment
Mated Pairs
In the Intelligent Network SCPs may be deployed either singly or as mated pairs. A mated pair of SCPs is two SCPs that contain identical call routing plans for a particular Service Subscriber. Two SCPs are used for reliability. If one SCP fails, the other SCP can take over its mates share of the call processing load. Typically, each SCP of a mated pair is deployed in a different location. In the example shown, an Advanced Routing Services service provider has numbers 0800-1000 to 0800-9999. Each SCP contains all these numbers in its database. However, under normal conditions
s
SCP A only handles calls to numbers in the range 0800-1000 to 08004999 SCP B handles all numbers in the range 0800-5000 to 0800-9999. So SCP A is said to be the primary SCP for numbers 0800-1000 to 08004999, and SCP B the primary SCP for numbers 0800-5000 to 0800-9999. Similarly, SCP A is the secondary SCP for numbers 0800-5000 to 08009999, and SCP B the secondary SCP for numbers 0800-1000 to 08004999.
Stand Alone SCPs
Some IN congurations use a stand-alone SCP, that is an SCP that is not mated (see the diagram on the opposite page). In the example, the single SCP would handle calls to all numbers in the range 0800-1000 to 0800-9999.
Issue 8.2
1-37
CCF
1. O_Null & Auth_ .Orig._Attempt
SSF
Detection Point Processing
SCF
Service Logic
DP1 Trigger request instructions 2. Collect_ Information
DP2 What time is it?
3. Analyse_ Information
DP3 Request Instructions New Number 09:00 17:00 Local office 01666 832967 17:00 09:00 Main office 01666 832186
3. Analyse_ Information
DP3 Routing 4. Route & Alerting information
Figure 1-18.
IN Call Example Using the SCF.
1-38
Issue 8.2
IN Call Example Using the SCF

The SCF in an Intelligent Network contains a database which stores the routing logic for the service and the service subscribers call routing plans. Depending on the type of service, the call routing plans contain one or more possible routing destinations. Service features in effect at the time the call routing plan was accessed determine how the call is routed. For example, if the Time Of Day service feature is in effect, the SCF will check the time of day and route the call according to the time the call is made. After the SCP has accessed the call routing plan, it sends the routing instructions to the SSF. The call ow is as in Figure 1-18 and will not be repeated here. The caller has dialed a freephone number, 0800-123123, and this has been passed to the SCF as already described. The following explanation only describes what takes place in the SCF. 1. The message is received by the SCF. The SCF will nd the Subscriber Record for the called party in its database. This will contain the Call Routing Plan for the insurance company subscribing to the Freephone service. 2. The SCF will check the time of day according to the logic in the Call Routing Plan. In this example, it will route the call to the local ofce on 01666832967 between the hours of 08:00 to 17:00, and to the main ofce on 01666-832186 at all other times. 3. The number is sent back to the SSF and call processing continues as described in the preceding example.
Issue 8.2
1-39
Functions of the SMF:

s
Applying changes to service data Modication and downloading of service logic Collecting measurements Receiving and logging unsolicited status and service maintenance messages from the SCP Producing reports Service data audits
Figure 1-19.
Service Management Function
1-40
Issue 8.2
Service Management Function

Denition
The Service Management Function (SMF) is responsible for provisioning and managing Services created by the Service Creation Environment and downloading services and service-related data to the Service Control Point(s). It holds the master copy of all service-related databases. The SMF is not involved in call processing.
Functions
The primary purpose of the SMF is to provide the information needed to install, congure and manage new services on the SCF. This involves:
s
Applying changes to global (service-wide) or subscriber data and distributing the changed data to all SCFs that require it. This data includes service logic which is specic to individual subscribers. Downloading service logic onto all SCFs that require it. Collection of service subscription measurements. Producing reports on these measurements. The format and content of these reports are under the control of the user. Receiving and logging unsolicited status and service maintenance messages from the SCF. For example, if a caller changes their PIN, the change will be done in the SCF rst, and must then be sent to the SMF. Retrieving provisionable data for comparison of the data on the SCF and on the SMF. These comparisons are called service data audits. In addition to its facilities for managing subscriber and service data, the SMF also includes a data collection function for accumulating and reporting on service subscription measurements gathered by a network element.
s s s
Issue 8.2
1-41
FUNCTIONS OF THE SCEF:

s
Creation and modication of service logic Downloading of service logic to the SMS
Figure 1-20.
1-42
Issue 8.2

Denition
The Service Creation Environment Function (SCEF) is a network element used to create and modify network database services, for example the Freephone service. The SCEF allows Lucent Technologies, customer personnel or a third party vendor to create and customize IN services rapidly. The purpose of SCEF is to create service packages (SPs) and to send them to the SMF for deployment to one or more SCFs on which they will provide service. A Service Package is a container for one or more IN services. A Service Package contains:
s
Functions
Service Packages
service logic This is the program code which implements the call processing required of the service, and all the operational and maintenance functions associated with the service, such as collection of measurements and statistics. service data and service data schema Service data is the data which is needed to run the service. It includes data which is common to all subscribers and data which is specic to individual service subscribers. The service data schema species the structure of the service data. specication of which data and statistics to collect during service execution.
The SP contains this information for one or more services, such as the Advanced Routing service. SPs allow a set of interactive services to be encapsulated into a single SP. A service within a service package can interact with another service in same the SP. Services within one SP do not interact with services in any other SPs. Some of the benets of this are:
s s
New SPs can be developed and updated independently of existing SPs. The deployment of a new SP to a network element does not interfere with the execution of pre-existing SPs.
Multiple versions of the same service can coexist on the same network element.
Issue 8.2
1-43
LANGUAGES:
s
Service Logic Language (SLL) text-based programming language
Decision Graph Language (DGL) graphical language standard building blocks
Figure 1-21.
Service Creation
1-44
Issue 8.2
Service Creation
The Lucent Technologies Service Creation Environment (SCE) provides service developers with tools and standard building blocks of functionality for programming network services. These tools include Graphical User Interfaces (GUIs), Application Oriented Languages (AOLs), and Service Independent Building Blocks (SIBs) that allow the service developer to work in the application domain, focusing specically on the task at hand rather than on the underlying detailed programming steps required to accomplish the job. There are two AOLs:
s s
Service Logic Language (SLL) Decision Graph Language (DGL)
Typically, services are written using a combination of both. The DGL part of an IN service is made up of a number of SIBs. Each SIB provides some logic which controls the behavior of the service. For example, there are SIBs which control the routing of calls according to various criteria, such as the time of day, day of week, location of the caller etc. Others send charging information to the SSF. This logic is in the SCF. Services are built up from SIBs using a graphical editor. SIBs are put together to create structures called Decision Graphs (DGs). The graphical editor is called the Enhanced Decision Graph Editor (EDGE). Additional logic is written in a second AOL, called Service Logic Language (SLL). SLL is more like a traditional programming language, but contains features specic to the writing of telephony services. It provides an efcient means of providing the logic needed to link the DGs together. ITU-T Recommendation Q.1214 denes a set of standard SIBs. In addition, most equipment providers dene additional ones.
Lucent Technologies products

The minimum conguration for an SCE is one SUN SPARC to function as a server and client workstation, and one PC compile server. A typical conguration is one SUN SPARC to function as a server and client workstation, one PC compile server, and one or more additional SUNs to function as client workstations.
Issue 8.2
1-45
3
0800-1700 Connect
2
Mon.-Fri. Time_o f_Day
4
other Exit
1
Root Day_of _Week
4
other Exit
SLL program
Figure 1-22.
Example Decision Graph
1-46
Issue 8.2
Example Decision Graph

The decision graph shown opposite provides outgoing call screening. It only allows calls to be made between the hours of 08:00 to 17:00 on Mondays to Fridays. At all other times, the call is disallowed and terminates to an announcement. Logic in the SLL program has decided that Outgoing Call Screening is required. It therefore initiates the Outgoing Call Screening DG. Each numbered box represents a SIB. The logic is as follows: 1. Check the day of the week 2. If it is a weekday, check the time of day 3. If it is between 8:00 and 17:00, connect the caller to the called party 4. If either of these checks fails, disallow the call
Issue 8.2
1-47
Functions of the SRF:

s
Interact with the calling party, called party and the SCF Play Announcements Collect Digits Voice Recognition Voice Back
Figure 1-23.
The SRF
1-48
Issue 8.2
The SRF
Denition
The SRF (Specialized Resource Function) serves the SSF whenever an IN call requires direct interaction with the calling party in the speech path. The SRF contains the logic necessary to send, receive and convert information. All SRF actions for a given call are determined by commands received from the SCF. If the SCF needs interaction with the calling party or the called party, it requests the CCF to connect to the SRF. This request is sent via the SSF. Instructions as to what the SRF needs to do may be contained in the SCF request. If they are not, then the SRF can request instructions directly from the SCF (but only if a direct link is available between the SCF and SRF). When the interaction is nished a message is sent back to indicate this, and the connection between the SRF and the CCF is torn down. The SRF has the following functions:
s
Functions
Play Announcements An announcement can be used to inform the calling party that some event has occurred (for example: All lines are busy at the moment, please wait for an operator) or to prompt the calling party to enter digits (for example: Please enter your calling card number followed by your Personal Identication Number). If an announcement is used to prompt the calling party to dial digits, the SCF may allow the announcement to be interrupted. If the announcement is interruptible the calling subscriber is allowed to enter digits while the announcement is still playing. At the moment a digit is entered the announcement is stopped.
Collect Digits When the calling party has entered digits, the SRF checks whether the correct number of digits have been sent. If enough digits are entered the SRF sends these digits in a message to the SCF (using the SSF/CCF or a direct link). Voice Recognition If the SRF has voice recognition, the subscriber can speak to the SRF and the SRF translates the spoken digits to a digit string. For example, a caller is prompted for a PIN. The calling subscriber then speaks the digits in the PIN. These are recognized and translated by the SRF to the actual digits. The SRF then sends these digits in a message to the SCF (using the SSF/CCF or a direct link) Voice Back After all the digits have been entered by the calling party, the SRF can replay the digits to the calling party. This allows the user to verify if the correct digits have been entered.
Issue 8.2
1-49
SCF
SRF
SSF CCF
SSF SRF CCF
Integrated SRF, CCF and SSF
SCF SRF SSF CCF SSF CCF
Remote SRF Controlled by the SSF
SCF SRF SSF CCF SSF CCF
Remote SRF Controlled by the SCF Figure 1-24. Conguration
1-50
Issue 8.2
Conguration
The SRF is designed for maximum exibility, allowing the network provider to decide how many Intelligent Peripherals (IPs) are needed and where they should be. The top diagram on the page opposite shows an example of an SRF in the same exchange as the SSF and CCF. This conguration is used when the SSP and the IP are combined. This is most likely if there is a lot of interaction between the SSP and the IP. If the SCF wants to communicate with the SRF this is done using the SSF and CCF. The middle diagram on the page opposite shows an example where the SRF and SSF/CCF are not in the same exchange. This conguration still allows each SSP to have its own IP, but as shown in the gure a number of SSPs can use one IP. If the SCF wants to communicate with the SRF this has to be done using the SSF and CCF. The bottom diagram on the page opposite shows an example where the SRF and SSF/CCF are not in the same exchange. The difference from the previous example is that the SCF can communicate directly with the SRF without using the SSF. At the moment the SCF needs the SRF to interact with the customer, the SCF requests the SSF to connect to the SRF. As soon as the connection is made, the SRF queries the SCF using the direct communication link to ask what has to be done for this call. The connection between the SRF and the CCF can be either Integrated Services Digital Network (ISDN) or (Common Channel Signaling No. 7 (CCS No. 7). If the SCF and SRF are connected CCS No. 7 signaling is used. Which of these protocols is used depends on the suppliers of the SSP, SCP and IP.
Issue 8.2
1-51
SCE
Remote Network Operations Center
SMS
SCP SCP
STP
IP
SSP
SSP
FUNCTIONS
s
Monitoring, display and logging of alarms Performance and measurement reports User programming Network element maintenance
Figure 1-25.
Operations Support Systems
1-52
Issue 8.2

An Operations System (OSS) is not actually a part of the intelligent network. Its purpose is to monitor the health of every network element in the intelligent network, and to enable engineers to issue maintenance commands to network elements. An OSS is in a central location, and is linked to every network element.
Functions
The major functions are:

s
monitor, display and log alarms from network elements Alarms are a means of telling technicians of high priority events that need to be brought to their attention. They are generated at the site of any network element. The OSS, however, gives the network the ability to collect and display them via an audible and visual alarm and/or printout. These OSS generated displays will usually be found in work centers away from the network element itself. An OSS can provide a graphical, interactive display of the network. Using a point and click system users can display information associated with an alarm. Alternatively, a text-based interface can be used.
performance and measurement reports - an OSS is able to collect measurements from network elements and provide measurement reports on request or on a scheduled basis. user programming - An interface is provided to enable the user or a third party to develop new features. network element maintenance - an OSS provides on-line access to the SSPs STPs, and the SCPs. Authorized users can monitor these network elements and input maintenance commands. Reports are produced using data from the SSP. Users can remotely access the 5ESS Ofce Dependent Data to perform database updates, add and delete lines, trunks, signaling information etc. to the SSPs and STPs via Recent Change. It also allows access to the displays at the SSP and SCP, the running of diagnostics and access to the Emergency Access Interface (EAI) of the SSP and SCP. Users of an OSS are typically Operations, Administration, and Maintenance personnel. When specic tasks need to be performed, users access a particular network element using the appropriate subsystem.
Issue 8.2
1-53
= CCS No. 7 Signaling Link = Voice Trunk
SCE
SMS
X.25
SCP
STP
SCP
SSP
SSP
IP
CCS
CCS
Legend: CCS = Common Channel Signaling IP = Intelligent Peripheral SCE = Service Creation Environment SCP = Service Control Point
Figure 1-26. Summary
SMS SSP STP X.25
= Service Management System = Service Switching Point = Signaling Transfer Point = ITU-T X.25 Recommendation
1-54
Issue 8.2
Summary
s
An Intelligent Network gives the network provider, the service subscriber and the calling party a number of benets. The ITU-T Functional Model provides a generalized description for the functional components of an Intelligent Network. The Basic Call State Model is a means of representing the processing of a call. It consists of a number of call states and detection points. Call states represent points in a call. Detection points are used to temporarily halt call processing pending the sending or receiving of information. An Intelligent Network consists of the following network elements: Call Control Function (CCF) Service Switching Function (SSF) - SSP Special Resource Function (SRF) - IP Service Control Function (SCF) - SCP Service Management (SMF) - SMS Service Creation Environment Function (SCEF) - SCE
An Operations System (OSS) is used to monitor and maintain every network element in the IN.
Issue 8.2
1-55
NOTES
1-56
Issue 8.2
Exercise
Answer each question by selecting the most appropriate answer from the list of alternatives.
1. Which of the following are advantages of Intelligent Networks: a) The ability to make international calls more cheaply. b) The ability to reduce the load on the SCP when call trafc is heavy. c) Flexibility in routing and charging for calls. d) The ability to play announcements to the caller.
2. Which of the following hardware and related elements are used in an Intelligent Network? a) SSP b) STP c) SMS d) SCE e) IP f) All of the above
Issue 8.2
1-57
3. Which of the following best denes the IN functional model and its implementation: a) A standard building block of functionality for programming network services. b) The point in a call at which call processing in the CCF is interrupted to await instructions or to report an event. c) A conceptual representational of the functional entities of an intelligent network and the relationships between them. d) None of the above.
4. What does the BCSM describe: a) How the SCF handles call which require the use of an Advanced Service. b) The stages through which a call passes when it is processed at an exchange. c) How a service is created and provisioned. d) How messages are routed within the Intelligent Network.
5. What is a detection point: a) An element in the Intelligent Network. b) A type of message sent from the SSF to the SCF. c) A stage during the processing of a call when call processing is suspended to wait until information is received or to report the occurrence of an event. d) None of the above.
1-58
Issue 8.2
6.What is the purpose of the SCF: a) The detection of IN calls. b) Playing announcements. c) Setting up of voice connections. d) Routing of calls which require the use of advanced services.
7. What is call gapping: a) A means of reducing the load on an SCF by reducing the number of queries sent to it. b) A means of collecting measurements and statistics on the performance of the SCF. c) A facility for tracing the origin of a call. d) None of these.
8. What is a mated pair of SCPs: a) One SCP processing all calls for a service while the other is acting as a hot standby. b) One SCP processing all calls for a service while the other is acting as a cold standby. c) Two SCPs sharing a load. If one of them fails, the other SCP takes the load. d) None of the above.
Issue 8.2
1-59
9. What is the SCEF used for: a) Provisioning of service databases. b) Creation and maintenance of service logic. c) Collection of post-dialing digits. d) None of these.
10. What is the purpose of the SMF: a) Distributing service logic to all the SCFs. b) Collecting measurements, statistics and service maintenance messages and producing reports. c) Provisioning of service databases. d) All of the above.
11. What does the SRF do: a) Play announcements and collect digits. b) Route IN calls to an SCF. c) Initiate network management controls. d) Determine how much to charge for an IN call.
1-60
Issue 8.2
12. What is an alarm: a) An audible sound that is triggered at an appropriate time interval (e.g., change of maintenance shift). b) An audible sound that is triggered when the Alarm Relay Unit fails. c) A high priority incident or event that needs to be brought to the attention of maintenance staff. d) An event that is logged.
Issue 8.2
1-61
1-62
Issue 8.2
INTELLIGENT NETWORK SERVICES
2
2-1
2-1
Contents
Lesson Overview
s
Lesson Objectives
Introduction to IN Services Service Access Advanced Routing Services Advanced Routing Service Features Call Distribution
s s
2-3 2-5 2-7 2-9 2-11

2-11 2-11
Call Forward on Busy / Dont Answer Call Logging
Call Queuing
s
2-13
2-13
Call Limiter
One Number
s
2-15
2-15
Customised Terminating Announcements
Origin Dependent Routing

s
2-17
2-17
Originating Call Screening
Originating User Prompt Time Dependent Routing

s s
2-19 2-21
2-21 2-21
Routing by Time of Day Routing by Day of Week
Issue 8.2 2-i
s s
Routing by Day of Year Routing by Holiday
2-21 2-21
Single Destination Service Account Card Calling Service

s s
2-23 2-25
2-25 2-25
Basic Calling Card Destination Restricted Calling Card
Televoting Service VPN Service VPN Call Processing VPN Tables On-Net Calling
s
2-27 2-29 2-31 2-33 2-35

2-35
On-Net Call Screening
Closed User Groups Off-net Calling

s
2-37 2-39
2-39
Off-Net Call Screening
Abbreviated Dialing Authorization Code Off-Net Access Follow Me Update VPN Attendant
s
2-41 2-43 2-45 2-47 2-49

2-49
VPN Reports
Summary NOTES Exercise
2-51 2-52 2-53
2-ii
Issue 8.2
Lesson Overview
This lesson is designed to give the student an introduction to the Intelligent Network services as well as the features that make up these services.
Lesson Objectives
On completion of this lesson participants will be able to:

s s s s s s
state the function of the Advanced Routing service state the function of the Single Destination service state the function of the Account Card Calling service state the function of the Televoting service state the function of the VPN service Understand some of the features associated with these services: Call Distribution Origin Dependent Routing Originating User Prompt Originating User Prompt may be used Time Dependent Routing VPN On-Net Calling Call Screening Abbreviated Dialing
Issue 8.2
2-1
Advanced Routing services Single Destination service Account Card Calling service Televoting service Virtual Private Network service
Figure 2-1.
Introduction to IN Services
2-2
Issue 8.2
Introduction to IN Services
The Intelligent Network is a very exible network for designing, implementing and using services. These different services are built in the SCE. IN has been used for many years in many congurations. The most commonly used services are listed opposite. Each Service consists of one or more service features. A service feature is a unit of functionality, for example routing by time of day or call queuing. The following sections explain each of the services in more detail, as well as the IN service features used to build these services.
Issue 8.2
2-3
0..8..0..0......1..2..3..4 SAC
Figure 2-2.
Service Access
2-4
Issue 8.2
Service Access
A caller normally accesses a service by dialing a service access code (SAC). For example when a caller dials a Freephone number, they rst dial a sequence of digits such as 0800. This is a commonly used service access code for the Freephone service. Every service has a unique SAC. It is up to the network provider to decide what service access codes to use for each of the services they provide. This is a part of the numbering plan used by the network provider.
Issue 8.2
2-5
Freephone service Split Charging service Premium Charging service Universal Access service
Figure 2-3.
Advanced Routing Services
2-6
Issue 8.2
Advanced Routing Services

The Advanced Routing Services can be sub-divided into the following services:
s
Freephone Service Allows the calling party to call an IN service subscriber without incurring any charges. The call is paid for by the service subscriber. This is commonly used by, for example, insurance and mail order companies to sell their products. Split Charging Service Allows the calling party to call an IN service subscriber with reduced charges. The call is paid for by the calling subscriber and the service subscriber. In the UK, electricity companies use this to reduce nuisance calls. Premium Charging Service Allows the calling party to call an IN service subscriber and pay the cost of the call plus additional fees to the service provider for the information provided during the call. The calling party pays for the expertise of the service provider. The calling subscriber readily pays for this service, because the telephone offers easy access to valuable information, for example nancial advice. Universal Access service Allows the calling subscriber to dial a country wide access number and be routed to the appropriate service subscriber. The calling party pays normal PSTN charges for this call.
Issue 8.2
2-7
Call Distribution Call Forward on busy/Dont Answer Call Limiter Call Logging Call Queuing Customised Recorded Announcements One Number Origin Dependent Routing Originating Call Screening Originating User Prompt Single Destination Service Time Dependent Routing: Routing By Time Of Day Routing By Day Of Week Routing By Day Of Year Routing by Holiday
Figure 2-4.
Advanced Routing Service Features
2-8
Issue 8.2
Advanced Routing Service Features

The table shows the service features which can be used by the Advanced Routing Services services. These features are available for use by other services. Again, this is not an exhaustive list, but shows a representative sample only. They are described on the next several pages.
Issue 8.2
2-9
25%
REGIONAL OFFICE WHAT PERCENT ?
25%
REGIONAL OFFICE
50%
MAIN OFFICE
Figure 2-5.
Call Distribution
2-10
Issue 8.2
Call Distribution
The Call Distribution Service Feature allows the service subscriber to specify the percentage of calls to be distributed randomly among two or more service subscriber destinations or to alternate call handling treatments. This percentage can be specied to the nearest 1%. The sum of percentages must equal 100%.
Call Forward on Busy / Dont Answer Call Logging
The Call Forward on Busy/ Dont Answer Service Feature allows the service subscriber to nominate an alternate number to route calls to when the original destination is busy or does not answer. The Call Logging Service Feature allows the service subscriber to prepare a record each time a call is received at a particular destination. This count is logged at the SCP.
Issue 8.2
2-11
ALL LINES ARE BUSY. PLEASE STAY ON THE LINE AND THE NEXT AVAILABLE OPERATOR WILL TAKE YOUR CALL.
Figure 2-6.
Call Queuing
2-12
Issue 8.2
Call Queuing
The Call Queuing feature provides the service subscriber with the option of putting a caller onto a queue when all lines are busy. Callers receive an announcement from the Special Resource Function (Intelligent Peripheral) informing them, for instance, that all access lines are busy. The calls, held in the queue by the SSP under the direction of the SCP, are processed on a rst in rst out basis.
s
Service subscribers can specify the MCA (maximum number of calls allowed) for each destination. This MCA is based on the number of lines and attendants available at each service subscriber. A separate queue exists for each service subscriber destination. The number of calls allowed on queue and length of time an individual caller spends in queue is determined by network administrators. Queue slots, requested by the service subscriber, are reserved exclusively for that subscriber and for the telephone number (destination) designated.
s s
Call Limiter
The Call Limiter Service Feature allows a service subscriber to specify the maximum number of calls to a given destination. This allows the subscriber to reserve a dened number of access lines for IN calls, while the remaining lines can be used for normal non-IN trafc.
s
Service subscribers can specify the MCA (maximum number of calls allowed) for each destination. This MCA is based on the number of lines and attendants available at each service subscriber.
Issue 8.2
2-13
01666-456789
NORTHERN WAREHOUSE WHICH WAREHOUSE?
0800-123456
01666-987654 SOUTHERN WAREHOUSE
Figure 2-7.
One Number
2-14
Issue 8.2
One Number
This Service Feature allows subscribers with terminating lines in two or more destinations to advertise one number by which their customers can reach them from anywhere within a dened geographic area. This feature is most commonly associated with Universal Access Number service.
Customised Terminating Announcements
This Service Feature allows a call to be completed to a customized terminating announcement instead of a subscriber destination. The terminating announcements can be charged to the service subscriber or to the caller depending on the information provided in the announcement. For example, a courtesy response indicating that the ofce is closed for the day or an announcement giving important medical or nancial advice to a caller.
Issue 8.2
2-15
ALL POINTS NORTH
NORTHERN WAREHOUSE FROM WHAT AREA?
ALL OTHER CALLS SOUTHERN WAREHOUSE
Figure 2-8.
2-16
Issue 8.2

The Origin Dependent Routing service feature allows service subscribers to specify different call treatments based on the originating geographical area of the caller, and based on whether the call originated nationally or internationally.
Originating Call Screening
The Originating Call Screening service feature allows a service subscriber to bar calls from certain geographical areas or accept only those calls received from certain designated areas.
Issue 8.2
2-17
FOR FURTHER SERVICE, PLEASE PRESS... DIGIT #1
CATALOG ORDERING DIGIT #2 CUSTOMER SERVICE DIGIT #3 BILLING
WHAT DIGIT?
OTHER (NO RESPONSE) OPERATOR
Figure 2-9.
Originating User Prompt
2-18
Issue 8.2
Originating User Prompt

The Originating User Prompt service feature allows the service subscriber to play an announcement and collect digits from the caller. The announcement and digit collection capability is provided by the Special Resource Function (SRF). Digit collection is in the form of DTMF tones generated by a DTMF phone or a Tone Generator. The service provisioner will need to specify the number of digits to collect. The service provisioner can also specify whether digits are to be spoken back to the caller (voiceback) to conrm the digits that were entered. This feature is used in several ways by the IN, the most common being to collect a callers Personal ID, Authentication code or Calling Card number. It can also be used to decide what the next course of action will be as illustrated in the gure opposite.
Issue 8.2
2-19
0900 - 1700
REGIONAL OFFICE
1700 - 2000
MAIN OFFICE
2000 - 0900
TERMINATING ANNOUNCEMENT
Figure 2-10.
Time Dependent Routing
Issue 8.2
2-20
Time Dependent Routing

Time Dependent Routing allows a service subscriber to route a call based on the Time of Day, Day of Week, Day of Year or Holiday.
Routing by Time of Day
This feature allows the service subscriber to dene different call treatments based on the time of day. Intervals are dened in one minute increments and all hours of the day need to be accounted for. The call time is checked against the SCP system clock in determining when a call should go to a particular treatment. This service feature allows the service subscriber to apply different call treatments to a call based on the day of the week. A day is dened as a period from midnight to midnight. Call treatments need to be dened for every day of the week. This service feature allows the service subscriber to apply different call treatments based on the day of the year that the call is placed. Routing alternatives must be provided for all day of year groupings, there can be a maximum number of 366 branches based on the outcome of this decision. This service feature allows the service subscriber to apply different call treatments based on a holiday. Holidays are dened in a global holiday table. The difference between routing by holiday and routing by day of year is that routing by holiday allows the service subscriber to apply the same treatment to a range of holiday days, whereas the routing by day of year feature is unique for each day.
Routing by Day of Week
Routing by Day of Year
Routing by Holiday
2-21
Issue 8.2
MALMESBURY
CHIPPENHAM
Figure 2-11.
Single Destination Service
Issue 8.2
2-22
Single Destination Service

The Single Destination Service differs from the Advanced Routing Service in that it offers one destination (PSTN routing number or announcement) for calls to a service subscriber. The Single Destination Service may also be called the Basic Routing Service or Basic Freephone Service. The Single Destination Service does not have any service features.
2-23
Issue 8.2
BASIC CALLING CARD DESTINATION RESTRICTED CALLING CARD
CALLING CARD
CALLING CARD
89339BBB - XX - XXX - LPINN
Figure 2-12.
Account Card Calling Service
Issue 8.2
2-24
Account Card Calling Service

The Account Card Calling service allows a subscriber to bill calls to an account. This card will typically be issued by the telephone administration. There are two types of Account Card Calling service: Basic Calling Card and Destination Restricted Calling Card.
Basic Calling Card
Basic Calling Card works in the following way: 1. The caller dials the Calling Card Access number. 2. The call is routed to the SCP via the SSP. The SCP instructs the SSP to collect the callers Calling Card number and PIN (Personal Identier). 3. The caller enters a Calling Card number and PIN. The number is collected by the IP and a validity check on the number of digits dialled takes place. 4. If the No. of digits dialled is within range then the digits are forwarded via the SSP to the SCP. The SCP checks the validity of the Calling Card Number and PIN combination. 5. If the combination is valid the caller is prompted (via the SSP) for the destination number required. 6. The caller enters a destination number which is forwarded to the SCP. 7. The SCP checks that the destination is valid (against a pre-determined set of disallowed destinations). 8. If the destination is valid the call is routed to the nal destination. 9. The caller may invoke follow on calling (if the feature is subscribed to) after the call is terminated, by entering a follow on call digit. Follow On Calling - allows a caller to make further calls after the rst call is nished without having to re-enter his/her Calling Card Number and PIN. Invalidation on Reprompt - Allows the service provider to invalidate the card of a service subscriber after three invalid calling card number and PIN combinations have been attempted. The card can only be re-validated by an operation at the SMS (Service Management System).
Destination Restricted Calling Card
Destination Restricted calling card works in a similar way to Basic Calling Card except that after the callers calling card number and PIN are collected the call is routed to a pre-dened destination.
Issue 8.2
2-25
SMS
total counts to SMS
SCP
counts to SCP
lter commands from SCP
SSP
1, 2,3........ 24, 25, 26,27.....
yescount nocount
1,2,3....9,10,11,12...
Yes votes
No votes
PSTN
0991 242123 YES 0991 242124 NO
VOTING TONIGHT
Figure 2-13.
Televoting Service
2-26
Issue 8.2
Televoting Service
The Televoting service offers the service subscriber the capability to survey public opinion using the telephone network. The televoting service subscriber will advertise IN telephone numbers for each option solicited in the survey, callers will dial the numbers associated with their opinion. During a televoting event, it is not desirable to have the SCP provide routing instructions for all calls, because the high volume of queries would overload the SCP. Therefore the SCP will send a lter instruction to the SSP effectively limiting the number of calls that it receives. All calls ltered at the SSP will be counted and the results sent to the SCP. The SCP sums call counts received from each SSP and forwards them to the Service Management System. Typically, as shown in the gure opposite, callers will call one number to vote yes and a different number to vote no. However, as previously stated it is possible to call up to 20 different numbers and have the votes counted separately.
Issue 8.2
2-27
OFFICE
FACTORY
VPN SERVICE
REMOTE ACCESS USER
OFFICE
Figure 2-14.
VPN Service
2-28
Issue 8.2
VPN Service
The Virtual Private Network service allows service subscribers to connect together several ofces, factories and even home users in one virtual network. The connections between the users can use existing local and toll circuits in the telephone network. This gives the Service Subscriber several distinct advantages:
s s
Home users can share the facilities of the VPN. Administration of the network can be accomplished centrally, therefore users can be added and deleted with a minimum amount of effort. Telephone charges can be made simpler and more cost effective by having one billing point. VPN Users can have the ability to make calls from outside the network. Security checking can be applied.
s s
The following are some of the features that make up the Virtual Private Network:
s s s s s s s s s
VPN On-Net Calling VPN Closed User Groups VPN Off-Net Calling VPN Abbreviated dialing VPN Follow Me Diversion VPN Off-Net Access VPN Authorization Code VPN Attendant VPN Call Screening
Different service subscribers use different features, depending on their requirements. Some service subscribers use different names for some features. These service features will be explained on the next few pages.
Issue 8.2
2-29
CLI VPN
IS SERVICE KEY CLI OR Recd No? CLI DELETE SAC FROM DIALED DIGITS
RECD NO.
REMOTE ACCESS CALL
LOOK UP DIALED DIGITS IN FAC TABLE FOR VPN ACCOUNT
NO FAC FOUND?
ON NET FAC POPULATED?
NO ON-NET CALL
YES
YES
CHECK FAC YES TO DETERMINE VPN CALL TYPE
PLAY VACANT CODE ANNOUNCEMENT
OFF-NET CALL
FOLLOW ME . UPDATE ON-NET FOLLOW ME UPDATE DEFAULT GLOBAL ABBREV. DIALING
CUSTOM ABBREV. DIALING FOLLOW ME UPDATE OFF-NET
VPN ATTENDANT CALL
Figure 2-15.
VPN Call Processing
2-30
Issue 8.2
VPN Call Processing

The gure opposite represents the initial call ow for the VPN service. The Service Access Code (SAC) associated with the VPN service will be discarded and the next few digits will be analyzed. These constitute the Feature Access Code (FAC). If an unsubscribed feature is being requested the call is terminated to an announcement. If the call is to a subscribed feature then the call ow for the subscribed feature will be followed. The next few pages describe the VPN features. Most VPN service use the CLI (Calling Line Identity) as the key to determine which VPN the caller belongs to.
Issue 8.2
2-31
Table VPN Account Information Feature Access Code Table Authentication Table
Per VPN or Per User Per VPN Per VPN Per User or Group
Description This table defines the service features subscribed to by a given VPN subscriber Defines the Feature Access Codes that will be used to access particular service features Defines the VPN account that a given User or Group of users belongs to and the capabilities associated with the user or group Defines Authorization code information for users who are able to use this feature Defines privileges associated with the Off-Net Access feature Defines call termination permissions of an individual VPN user Defines a set of disallowed destinations that VPN users are not allowed to call Defines the permissions associated with each Closed User Group A set of Global and Custom abbreviated dialing tables that define short codes for on-net calling Call Screening tables that define caller restrictions for on-net and off-net calls
Authorization Code Privileges Off-Net Access Mapping VPN User Profile Disallowed Destination Prefix CUG permissions Abbreviated Dialing Tables Call Screening
Per VPN Per VPN Per User Per VPN Per VPN Per VPN Per VPN
Figure 2-16.
VPN Tables
2-32
Issue 8.2
VPN Tables
The VPN service uses a set of tables to dene per VPN subscriber variables and per VPN user variables. These tables (shown opposite) associates a given Calling Line Identity or Off-Net Access number with a given set of privileges or capabilities for that user:
Issue 8.2
2-33
OFFICE A
HOME USER
Telcos Network
PSTN
OFFICE B OFFICE C
Figure 2-17.
On-Net Calling
2-34
Issue 8.2
On-Net Calling
The On-Net service allows users to call other users within the dened network. As its name implies, an On-Net call is a call between one user and another user on the same Virtual Private Network. The VPN users can be located in the same location or in a different location, provided that they are both dened on the same VPN. That location can also be a home user via the PSTN. The user dials a VPN code, which may consist of a Feature Access Code + Location Code + Extension (FAC + LOC + EXTN). This is forwarded to the SCP, where it is translated into a Final Routing Number. In the example in the gure opposite: 1. a caller from Ofce A dials the VPN code of the person he/she wishes to reach. 2. The call is passed to the network which recognizes it as a VPN On-Net call, and checks to see if the caller has permission to make this call. 3. A check is then made to see if the VPN code dialed (in Ofce B) will accept calls from this VPN station. 4. If so, the caller is nally routed to the correct destination code.
On-Net Call Screening
On-Net calls can be screened against a set of allowed/disallowed user permissions. If a VPN user, who has On-Net permissions also subscribes to call screening then calls can be checked against one of two separate criteria:
s
Screening dened in a barred list - The user is allowed to make any On-Net calls except those dened in a table containing a set of barred codes. Barred calls will be sent to a terminating announcement. Screening dened as an allowed list - The user is only allowed to make calls to On-Net destinations as specied in the allowed list of On-Net destinations. Barred calls are sent to a terminating announcement.
Issue 8.2
2-35
VPN 123
USER A
USER C USER D
ACCOUNTS STORES
USER F USER E USER G USER H USER B
SALES
USER L
SERVICES
USER J USER I USER K USER M
USER N
Figure 2-18.
Closed User Groups
2-36
Issue 8.2
Closed User Groups

The Closed User Group feature allows the user to be a member of a set of users who are allowed to make calls only to each other, the advantage being that the Service Subscriber can restrict certain users from Off -Net privileges or from calling other users in the VPN who are not in the same Closed User Group. There are typically up to 16 Closed User Groups per VPN. A user can belong to more than one CUG and a CUG may contain all users. The SCP makes the following checks: It determines (from the CLI/CID Privileges table) if the calling party is authorized to make calls to the called party. If not, the call is terminated to an announcement. It determines (from the VPN User Prole Table) if the called party is authorized to receive calls from the calling party. If not the call is terminated to an announcement. Closed User Groups can be used for example to prevent calls across geographic boundaries or to prevent calls to Managing Directors or Chief Executives. The Closed User Group table denes a list of users associated with each Closed User Group.
Issue 8.2
2-37
Caller A
Telcos Network
PSTN
Called Party B
Figure 2-19.
Off-Net Calling
2-38
Issue 8.2
Off-net Calling
The Off-Net calling service allows the Service Subscriber to give users the ability to make calls to destinations which are outside the dened VPN network. An Off-Net call is dened as a call from within the VPN to a PSTN or International number outside the VPN. This capability is only available to callers who have Off-Net calling privileges dened in their Authentication table.
Off-Net Call Screening
Off-Net calls can be screened against a set of allowed/disallowed user permissions. If a VPN user, who has Off-Net permissions also subscribes to call screening then calls can be checked against one of two separate criteria:
s
Screening dened in a barred list - The user is allowed to make any Off-Net calls except those dened in a table containing a set of barred codes, this could be local, toll or International codes. Barred calls will be sent to a terminating announcement. Screening dened as an allowed list - The user is only allowed to make calls to Off-Net destinations as specied in the allowed list of Off-Net destinations. Again this could be local, toll, special or International codes. Barred calls are sent to a terminating announcement.
Issue 8.2
2-39
CUSTOM ABBREVIATED DIALING CALL
11 + 3 DIGIT ADN
To IN
TO PSTN
GLOBAL ABBREVIATED DIALING CALL
15 + 3 DIGIT ADN
To IN
TO PSTN
Figure 2-20.
Abbreviated Dialing
2-40
Issue 8.2
Abbreviated Dialing
The Abbreviated dialing feature allows a user to dial an ADN (Abbreviated Dialing Number) to reach a PSTN (Public Switched Telephone Network) number. ADNs are typically numbers frequently dialed by users. There are 2 types of Abbreviated Dialing:
s
Global Abbreviated Dialing, where the user dials an ADN which is shared by all of the other users on the same VPN. Custom Abbreviated Dialing, where the user can dial an ADN dened from a list that can be used by a single user or a group of users.
The Figure on the opposite page illustrates the FAC (Feature Access Code) necessary to use the Custom or Global Abbreviated Dialing service.
Issue 8.2
2-41
AUTHORISATION CODE CALL Play Announcement and collect A.C from user
Look up A. C and Validate
Reprompt and collect A.C
YES A.C Valid? YES Prompt and Collect Destination number
NO
Remaining retries > 0? NO Disallowed AC Call Announcement
On-net FAC Populated? YES
NO
Is Dest Number a valid FAC? YES
NO Unsubscribed Feature Announcement Analyze FAC to Determine whether On-Net or Off-Net
ON - NET CALL OFF - NET CALL
Figure 2-21.
Authorization Code
2-42
Issue 8.2
Authorization Code
The Authorization Code feature is used to provide an alternate set of privileges to override calling restrictions. This service feature allows multiple users to share the same set of privileges by using the same authorization code. On-Net and Off-Net calling restrictions may be overridden by the use of this feature. The Authorization Code feature relies on the Intelligent Peripheral requesting an authorization code from the caller. This code is looked up and if valid the caller will have permissions associated with the code. This is illustrated in the ow chart opposite.
Issue 8.2
2-43
RA - CALL
Prompt and collect Remote Access Code And PIN
Look up R A code and PIN and Validate
Prompt and collect R. A code and PIN YES
Prompt and Collect Destination Number
YES
R.A Code & PIN Valid?
NO
Remaining retries >0 NO Disallowed R.A Call Announcement
FAC Valid? YES Complete R.A Call
NO
Unsubscribed Feature Announcement Disallowed FollowMe Announcement
NO Primary SCP Available? On-Net CALL Off-Net CALL YES
VPN Attendant
Follow Me Update
Figure 2-22.
Off-Net Access
2-44
Issue 8.2
Off-Net Access
The Off-Net Access feature allows the user to access the VPN from the PSTN by dialing a Service Access Code associated with Off-Net access calling. Upon receipt of an Off-Net Access call, the SCP instructs the IP (Intelligent Peripheral) to prompt the caller for an Off-Net Access Authorization Code. The SCP will then ask the IP to play an announcement and collect the callers Off-Net Access PIN (Personal Identication Number), if the combination is not valid the call is terminated to a specic announcement, otherwise the caller is prompted for a destination number. The gure opposite illustrates the Off-Net Access call ow.
Issue 8.2
2-45
OFFICE A
OFFICE B
Telcos Network
PSTN
OFF-NET LOCATION C
Figure 2-23.
Follow Me Update
2-46
Issue 8.2
Follow Me Update
The Follow Me Update feature provides a remote call forwarding mechanism for users who move frequently and need a convenient way of receiving their telephone calls. Users specify the number (VPN station or PSTN) to which future calls will be routed.
s s s s
Three call types are possible for the Follow Me Update service feature: Follow Me Update to default destination. Follow Me Update to another VPN station. Follow Me Update to a PSTN Number.
Each type of update will have a separate and unique Feature Access Code. When a VPN user dials the digits associated with a Follow Me Update to a new VPN code or PSTN destination, the SCP instructs the IP to collect the callers VPN code (if the caller is at his or her home location they may dial 9# to override this), the SCP then instructs the IP to collect the users Follow Me Update Personal Identication Number (PIN) and then validates it. If the PIN is valid then the SCP instructs the IP to collect the new On-Net destination, or PSTN number (depending upon the Feature Access Code dialed). If the user is changing to a PSTN number then a check is made that the new destination number is allowed. If a VPN user dials the digits associated with a Follow Me Update to a default destination, the Follow Me Update PIN is requested as before. If it is valid the default destination is changed back to the users original network routing number. The gure opposite illustrates the Follow Me Update feature. Here the default destination at Ofce A, may be changed to a new VPN code at Ofce B, or to an Off-Net PSTN location C. Follow Me Update calls can also be made from Off-Net Access locations.
Issue 8.2
2-47
Attendant
Attendant
OFFICE
FACTORY
VPN X
REMOTE ACCESS USER
Attendant
OFFICE
Figure 2-24.
VPN Attendant
2-48
Issue 8.2
VPN Attendant
The VPN Attendant feature allows Service Subscribers to set up a position, or positions (as shown) within their network for a person(s) to provide service information to network users. VPN users can be assigned with or without Attendant calling. When a call is made to the Attendant the caller will be put through to the Attendant which he or she is dened as belonging to. The attendant can have a number of variable routing options dened. Some examples are shown below: Origin Dependent Routing - The call is routed to an Attendant who is located in the same location or a location that is the most cost effective to the caller. Routing by Day of Week - The call is routed based on the day of the week. Routing by Time of Day - The call is routed based on a dened start and end time. Routing by Holiday - Certain days of the year can be designated as holidays, during these times calls are normally rerouted to an announcement. Routing by Day of Year - On any given day of the year special call routing characteristics may be assigned. Call Distribution - Calls may be distributed to several VPN Attendants on a percentage basis.
VPN Reports
The VPN service has one report: VPN Daily Summary Report - contains a summary of VPN calls to the On-Net, Off-Net, Virtual On-Net, Attendant, Follow Me, Invalid Authorization code attempts, etc. This report is available via the SMS system.
Issue 8.2
2-49
OFFICE
FACTORY
VPN SERVICE
REMOTE USER
OFFICE
Figure 2-25.
Summary
2-50
Issue 8.2
Summary
The Lucent Technologies Intelligent Network offers a variety of services to the Service Subscriber. These include:
s s s s s
Advanced FreePhone Universal Access Televoting Account Card Calling Virtual Private Network
The following are some of the features that make up the Virtual Private Network:
s s s s s s s s s
On-Net calling Closed User Groups Abbreviated dialing Authorization code calling Off-Net calling Follow Me Diversion Off-Net Access calling Attendant Calls Call Screening
Issue 8.2
2-51
NOTES
2-52
Issue 8.2
Exercise
1. Which of the following are Intelligent Network Services: a) Calling Card. b) Virtual Private Network. c) Televoting. d) All of the above.
2. What are Call Distribution, Call Logging and Time Dependent Routing: a) IN services. b) Features of the VPN service only. c) Service features that are potentially available to all IN services. d) None of the above.
3. What does Call Distribution do: a) Route a number of calls to a set of alternative destinations, based on target percentages. b) Generate a number of IN calls automatically for testing purposes. c) Route calls based on the time of day. d) Re-route calls if the destination number is busy.
Issue 8.2
2-53
4. What does origin dependent routing do: a) Route a call to a destination number, depending on the callers location. b) Prevent calls from being made from certain locations. c) Route a call to the same location, regardless of whether the caller is calling from a national or international location. d) None of these.
5. What does originating user prompt do: a) Request a caller to enter his/her Calling Line Identity. b) Request a caller to enter additional digits if/she has dialed a digit string that is not a complete PSTN or IN number. c) Request a VPN user to enter a feature access code. d) Provide a general mechanism for collecting additional digits from a caller when required.
6. Which of the following are examples of where originating user prompt may be used: a) Entering a PIN for VPN Off-Net Access. b) Entering an account number for a calling card. c) Entering a VPN station for Follow Me Update (also known as Call Transfer Update). d) All of the above.
2-54
Issue 8.2
7. Which of the following are valid time dependent routing features: a) Routing by time of day only. b) Routing by day of week only. c) Routing by time of day, day of week, day of year, holiday. d) Routing by day of year only.
8. A VPN on-net call is: a) A call using the PSTN network. b) A call from one VPN user to another. c) A call from a users ofce to his/her home. d) A call using an ISDN network.
9. What is call screening: a) Where the SCP records all calls. b) A feature used by the VPN service to prevent calls to one or more nominated VPN stations. c) A general method of barring calls from one destination to another by provisioning sets of data tables for each service. d) Blocking calls at the SSP during high trafc usage, such as televoting-type services.
Issue 8.2
2-55
10. To use abbreviated dialing, a customer must enter: a) Service Access Code + Abbreviated Dialing Code. b) Service Access Code + Feature Access Code then wait for an announcement asking for the abbreviated dialing code. c) Abbreviated Dialing Code only. d) It may vary according to the telephone company but is either Service Access Code + Feature Access Code + Abbreviated Dialing Code or Feature Access Code + Abbreviated Dialing Code.
2-56
Issue 8.2
INTELLIGENT NETWORK ELEMENTS
3
3-1
3-1 3-1
Contents
Lesson Overview
s s
Lesson Flow Lesson Objectives
TYPES OF NETWORK ELEMENTS

s s s s s
3-3
3-3 3-3 3-3 3-3 3-3
Introduction Definition Call Processing Systems Service Creation and Management Systems Operations Support Systems
SERVICE SWITCHING POINT

s s s s
3-5
3-5 3-5 3-5 3-5
Introduction Definition SSP Deployment Detection Points Supported
SIGNALING TRANSFER POINT

s s s
3-7
3-7 3-7 3-7
Definition Characteristics STP Interfaces
SERVICE CONTROL POINT

s s s
3-9
3-9 3-9 3-9
Introduction Definition SCP Interfaces
INTELLIGENT PERIPHERAL
3-11
Issue 8.2 3-i
s s s s
Introduction Definition Supported Functions Announcements & Digits Reception
3-11 3-11 3-11 3-11
SERVICE MANAGEMENT SYSTEM

s s s
3-13
3-13 3-13 3-13
Introduction Definition Service Management System Interfaces
SERVICE CREATION ENVIRONMENT

s s
3-15
3-15 3-15
Introduction Definition
OPERATIONS SUPPORT SYSTEM

s s
3-17
3-17 3-17
Definition Major Functions
SEFM HARDWARE LUCENT TECHNOLOGIES IN PRODUCTS

s
3-19 3-21
3-21
IN Configuration
SAMPLE INTERFACES
s s
3-23
3-23 3-23
Signaling Links Data Links
LESSON SUMMARY
s s s s s
3-25
3-25 3-25 3-25 3-25 3-25
Network Elements Service Switching Point (SSP) Signal Transfer Point (STP) Service Control Point (SCP) Intelligent Peripheral (IP)
LESSON SUMMARY Cont.

s s s
3-27
3-27 3-27 3-27
Service Creation Environment (SCE) Service Management System (SMS) Operations Support System (OSS)
NOTES EXERCISE
3-28 3-29
3-ii
Issue 8.2
Lesson Overview
This lesson is intended for personnel who come into contact with the Lucent Technologies IN (Intelligent Network) product family. This lesson covers the major characteristics of each network element used in the Lucent Technologies IN (Intelligent Network).
Lesson Flow
The lesson describes the different categories of network elements, and introduces the Lucent Technologies elements in each category. For each of the Lucent Technologies network elements, the hardware architecture is briey described. This is followed by an introduction to any special features of the Lucent Technologies product. On completion of this lesson, you will be able to identify:
s
Lesson Objectives
the network elements that make up the Lucent Technologies Intelligent Network. where data and service logic for each IN service is dened. the network element used to run (execute) services. the functions of the SAS, RAF, and NSCX.
s s s
Issue 8.2
3-1
Call Processing Systems

Network Element SSP STP SCP IP Lucent Technologies Product 5ESS 5ESS Lucent SCP Lucent SAS
Service Creation and Management Systems

Network Element SCE SMS Lucent Technologies Product Lucent SCE Lucent SMS

Network Element OSS Lucent Technologies Product MFOS SEFM
Figure 3-1.
TYPES OF IN NETWORK ELEMENTS
3-2
Issue 8.2
TYPES OF NETWORK ELEMENTS

Introduction
This page lists each of the systems that make up the Lucent Technologies intelligent network. The following pages will describe each of them. The individual systems that make up an Intelligent Network are referred to as network elements These network elements can be divided into three categories:
s s s
Denition
call processing systems service creation and management systems operational support systems
Call Processing Systems
Call Processing Systems are network elements that process calls. These network elements include systems such as switches, peripherals, and network databases. The types and number of network elements for a particular application of the IN differs from customer to customer. For the purpose of this lesson, we shall look at the Intelligent Network as consisting of one or more of the network elements listed opposite.
Service Creation and Management Systems Operations Support Systems
These network elements are used for creating and administering services and service data used in the Intelligent Network.
Operations Support Systems (OSSs) are external systems that give support personnel the tools to administer, monitor, maintain, and track performance of the IN.
Issue 8.2
3-3
Table 1: Detection points supported

DP2 DP3 DP4 DP5 DP6 DP7 DP9 DP10 Collected_Info Analysed_Info Route_Select_Failure O_Called_Party_Busy O_No_Answer O_Answer Disconnect O_Abandon
Figure 3-2.
3-4
Issue 8.2

Introduction
SSPs perform several important functions for the Intelligent Network. The functions an SSP performs are in addition to those provided by the switch where the SSP function resides. The focus of this part of the lesson is on the SSP functions only. The Lucent Technologies 5ESS-2000 switch is a digital switching system. It acts as an entry and exit point to and from the Intelligent Network to process dialed digits associated with most types of Intelligent Network calls. The 5ESS-2000 switch contains software which enables it to process Intelligent Network calls.
Denition
SSP Deployment
An Intelligent Network may consist of only one SSP or several SSPs. Several SSPs spread across the country is a more typical application of an IN than just one SSP. Where several SSPs are deployed, each SSP serves a particular portion of the country for Intelligent Network calls. The 5ESS-2000 supports detection points 2-7, 9 and 10. It does not support detection point 1 (Origination_Attempt_Authorized), detection point 8 (O_Mid_call) or detection points 11-18.
Detection Points Supported
Issue 8.2
3-5
Figure 3-3.
SIGNAL TRANSFER POINT
3-6
Issue 8.2
SIGNALING TRANSFER POINT

Denition
STPs (Signaling Transfer Points) transfer Common Channel Signaling messages only (no voice) between SSPs and a network database or between SSPs.
s s
Characteristics
Physically, an STP is a 5ESS 2000 switch. STPs may be stand-alone network elements, as shown, or the STP function may be embedded in the switch where the Service Switching Point software resides. The term Signaling Transfer and End Point (STEP) signies an STP function embedded in the switch that also provides the SSP function.
STP Interfaces
The Signaling Transfer Point supports several types of interfaces to other network elements.
s
STPs interface with the Service Switching Points in order to transfer signaling messages from one network element to another. STPs interface with the Service Control Point (SCP) so that the SSP may access the call routing plans in the SCP. STPs interface with an OSS for surveillance, maintenance, trafc, and database administration.
Issue 8.2
3-7
Disks
CPU A
CPU B
Figure 3-4.
3-8
Issue 8.2

Introduction
The Lucent Technologies SCP runs on the Lucent Technologies Advantage hardware platform. An SCP-2000 consists of a pair of Pentium-based processors in an activestandby conguration and mirrored pairs of disks for the storage of service logic and data. The hardware consists of standard, off-the-shelf components which are assembled by Lucent Technologies. This enables the equipment to be upgraded when requirements change.
Denition
SCP Interfaces
The SCP supports several types of interfaces to other network elements:

s s
with the STPs in order to transfer signaling messages to and from SSPs. with the SMS so that service data and logic can be downloaded to the SCP, and data, measurements and exception reports can be sent to the SMS. with an OSS for surveillance, maintenance, trafc, and database administration.
Issue 8.2
3-9
Functions:
s
Play announcements Collect digits
SAS
5ESS-2000 Switch
Figure 3-5.
3-10
Issue 8.2
Introduction
The Lucent Technologies Intelligent Peripheral is called a Service Announcement System (SAS). The Lucent Technologies SAS consists of a fast processor and a number of ash memory cards. They are deployed as a rack within the 5ESS-2000 cabinet and not as a stand-alone system. The Lucent Technologies SAS supports the playing of announcements and the collection of digits only. It does not support voice recognition or the voicing back of digits. The 5ESS-2000 switch already supports basic tones and announcements. These remain the same when the SSP functionality is added to the switch. These announcements are called standard switch-based announcements. For Advanced IN services, additional announcements and digit reception capability following a prompt are required. The SAS supports this function. Customized announcements are IP announcements whose content meets the specic needs of a particular service subscriber. An example of a customized announcement is a recording that might say: Thank you for calling the ABC Company; however, all lines are busy, please wait... Announcements are recorded onto ash memory using a separate Announcement Workstation. This consists of a PC running Windows 95.
Denition
Supported Functions
Announcements & Digits Reception
Issue 8.2
3-11
SCE
SCE
Local Area Network
X.25
SMS
FTAM
SPA Service data
FTAM
SCP
Counts and
SCP
Figure 3-6.
3-12
Issue 8.2

Introduction Denition
The Lucent Technologies SMS uses the SMS-2000 platform. The SMS-2000 is based on a redundant Hewlett-Packard 9000 series processors and a large amount of disk storage space. SCE to SMS Interface - The purpose of the SMS/SCE interface is to provide the information needed to install, congure and manage new services on the SMS. SMS to SCP Interface - The SMS uses this interface to perform the following interactions with an SCP:
s s s s s
Service Management System Interfaces
Download decisions graphs. Apply recent changes. Retrieve provisionable data for service audits. Collect measurements. Receive unsolicited status and service maintenance messages from the SCP. SMS to OSS interface - in addition to these interfaces, there is also an interface to the OSS. For clarity, this interface is not shown in the gure.
Issue 8.2
3-13
Workstations
File server
Compile server
Printer
To SMS
Figure 3-7.
3-14
Issue 8.2

Introduction
The Lucent Technologies Service Creation Environment runs on a Sun network, with a PC-based compile server. The Lucent SCE platform consists of:
s s s s
Denition
A le server.based on a Sun SPARC processor A compile server based on a Pentium processor A diskless Sun workstation for each service developer. A Postscript printer for printing out program sources.
These are all on a local area network. The le server holds the service development environment and tools. However, because the service will actually run on a Pentium-based system, programs are passed to a separate, Pentium-based machine for compilation. After compilation, the compiled Service Package is passed back the le server. This is transparent to the service developer.
Issue 8.2
3-15
Alarm Call-out
Switch Element Fault Manager
Total Network Management Integration Module (TNM/TIM) Alarm and Commands maintenance messages Element Mediation Module (EMM)
Alarm and Commands maintenance messages
Network elements
Figure 3-8.
OPERATIONS SUPPORT SYSTEM (OSS)
3-16
Issue 8.2
OPERATIONS SUPPORT SYSTEM

Denition
The Lucent Technologies Operations Support System (OSS) is the Switching Element Fault Management System (SEFM). The SEFM consists of two subsystems:
s s
Major Functions
Total Network Management Integration Module (TNM/TIM) Element Mediation Module (EMM)
The TNN/TIM caries out all the functions of the OSS. The EMM provides the interface to the network elements.
Issue 8.2
3-17
Sun workstations
HP workstations
Hub Printer
TNM/TIM
Terminal server HP9000 H50 Asynchronous links Remote peripherals Network elements
Element Mediation Module
HP9000 H50
X.25 link
Figure 3-9.
SEFM HARDWARE
3-18
Issue 8.2
SEFM HARDWARE
The SEFM is based on two HP9000 processors, with a third (not shown in the gure opposite) available as a spare if one of the other two fails. One, the TNM/ TIM, provides the system functionality, the other (the EMM) provides the main interface to the network elements, via X.25 links. The workstations are used to provide a graphical interface for displaying alarms and information about the network elements in the form of schematic diagrams. A terminal server provides asynchronous links to the network elements, to terminals for character-based user interfaces and to printers. All the above are connected via a hub. Each HP9000 has its own console terminal and console printer (not shown).
Issue 8.2
3-19
IN Functional Component Service Switching Point (SSP) Service Control Point (SCP)
Lucent Technologies Product 5ESS-2000 Switch Network Control Point International (1NCPI) Service Control Point II (SCP II) Service Control Point (SCP)
Signal Transfer Point (STP) Intelligent Peripheral (IP)
5ESS Switch and 5ESS Switch software supports the STP functionality. Network Services Complex (NSCX) Recorded Announcement Facility (RAF) Service Announcement System (SAS)
Service Creation Environment (SCE) Service Management System (SMS)
Lucent SCE NETSTAR IN-SMS Service Management System (Lucent SMS) Multi-Function Operations System (MFOS) Switch Element Fault Manager (SEFM)
Operations Support Systems (OSS)
Figure 3-10.
LUCENT TECHNOLOGIES IN PRODUCTS
3-20
Issue 8.2
LUCENT TECHNOLOGIES IN PRODUCTS

The architectural platform that the IN is based on is the ITU-T dened IN architecture. The network elements that make up the ITU-T IN and the corresponding Lucent Technologies products are listed in the gure opposite. This table lists the main Lucent Technologies products, past and present, for each type of network element. The current generation of products is shown in bold type.
IN Conguration
There are several ways the Lucent Technologies IN can be congured. The IN can be deployed using Lucent Technologies products exclusively, or the IN can be deployed in a multi-vendor environment, mixing products from other vendors with Lucent Technologies products.
Issue 8.2
3-21
LEGEND:
Data Links Voice Links Signaling Links
SCE
X.25
SMS
X.25
SCP
TCAP/INAP TCAP/INAP TCAP/INAP C7
SSP3/STP
SSP2/STP
C7 C7
SAS SSP1/STP
Figure 3-11.
SAMPLE INTERFACES
3-22
Issue 8.2
SAMPLE INTERFACES
The Lucent Technologies Intelligent Network supports a variety of interfaces between the network elements. The gure on the opposite page shows a sample of some of the IN Supported interfaces. Generally, the interfaces are via three kinds of links:
Signaling Links
Signaling Links that transfer signaling messages used to process an Intelligent Network Call. The IN supports a variety of signaling protocols.
s
National C7, the protocol deployed by a particular country. These protocols are typically used for exchanging of SSP to SSP communication. (National C7 is referred to as C7 in Figure 3-11.). TCAP/INAP, a family of protocols dening how SSP to SCP signaling messages are structured. TCAP stands for Transaction Capabilities Application Part; INAP stands for Intelligent Network Application Part. There are a number of different INAP protocols in use or IN. The main ones are: ETSI-INAP The European and International standard INAP ASE-RI-INAP Used in Italy and Spain AIN used in the USA
NOTE: In the gure opposite, SSP1 denotes a sample 5ESS switch SSP showing the switch also has an STP function. When embedded in a 5ESS SSP, the STP function is also referred to as a Signal Transfer and End Point (STEP).
Data Links
Data Links transfer data between SMS and SCE and between SMS and SCP using the X.25 protocol.
Issue 8.2
3-23
SCE
SMS
SCP
SCP
STP IP SSP
STP SSP IP
PSTN
Figure 3-12.
LESSON SUMMARY
3-24
Issue 8.2
LESSON SUMMARY
Network Elements
The Lucent Technologies Intelligent Network consists of several types of systems, all of which are termed network elements. These network elements are used for either Call Processing, Operational Support or Service Creation/Service Management Systems. SSPs act as entry and exit points to and from the Lucent Technologies Intelligent Network. The SSPs may be located in switches manufactured by various vendors, including Lucent Technologies which uses the 5ESS-2000 switch as its SSP platform. The SSPs formulate and send signaling messages over the IN to nd out how to process an IN call. Additionally, the SSPs provide announcements for IN services and can prompt for and collect digits from the caller. STPs transfer signaling messages only (no voice) between the SSPs and the SCPs and from SSP to SSP. An STP may be deployed as a stand-alone network element using the 5ESS-2000 switch or it may be embedded in the 5ESS2000 switch along with the SSP. SCPs store the call routing plans for service subscribers who purchase Single Destination or Advanced IN Services. The Network Control Point (1NCPI), the SCP II and the SCP-2000 are SCPs. An Intelligent Peripheral (IP) such as the SAS-IP plays customized announcements and provides for post-dialing collection of touch tone digits.
Service Switching Point (SSP)
Signal Transfer Point (STP)
Service Control Point (SCP)
Intelligent Peripheral (IP)
Issue 8.2
3-25
SCE
SMS
SCP
SCP
STP IP SSP
STP SSP IP
PSTN
Figure 0-1.
LESSON SUMMARY
3-26
Issue 8.2
LESSON SUMMARY Cont.

Service Creation Environment (SCE) Service Management System (SMS) Operations Support System (OSS)
The SCE provides a Graphical User Interface where Lucent Technologies and Service Providers can develop new service logic and modify the logic of existing services. The SCE runs on a Sun based platform. The Lucent SMS is used to provision and load data for services created at the SCE. It can also audit this data. It also serves as a facility for the collection and reporting of data from the SCP. The OSS provides access to all other network elements. It provides for on-site and remote system maintenance, alarm processing, trafc data gathering and database administration for the IN. The current Lucent OSS is the SEFM (Switch Element Management System).
Issue 8.2
3-27
NOTES
3-28
Issue 8.2
EXERCISE
Answer each question by selecting the most appropriate answer from the list of alternatives. .
1. Which network elements and functions are a part of the Lucent Technologies Intelligent Network: a) SCE (Service Creation Environment). b) SMS (Service Management System). c) STP (Signal Transfer Point). d) SCP (Service Control Point). e) All of the above.
2. Where is the data and service logic for each IN service dened: a) At the SSP. b) At the LMT. c) The service logic is dened at the SCE and the data is provisioned at the SMS, with an emergency interface available at the SCP, using the LMT. d) The service logic is defined at the SMS and the data is provisioned at the SCE, with an emergency interface available at the LMT, using the SCP.
Issue 8.2
3-29
3. Which network element is used to run (execute) services: a) SCE. b) SMS. c) SSP. d) None of the above.
4. What are the SAS, RAF and NSCX: a) Types of SCP used on systems before 1960. b) Types of STP that can be embedded in a 5ESS-2000 switch. c) Types of intelligent peripherals. d) Specialized IN units used in the U.S. domestic market only.
5. Which protocol is used to transfer data between the SCP and the SMS: a) X.25. b) X.42. c) TCAP. d) SS7.
3-30
Issue 8.2
6. Where does the SCP send data collected for reports: a) The SSP. b) The SMS. c) Another SCP dedicated to report processing. d) The SCP does not actually send report data, it stores it in a set of les that can be accessed by the SMS using FTAM.
Issue 8.2
3-31
3-32
Issue 8.2
IN CCS NO. 7 OVERVIEW
4
4-1
4-1 4-1 4-1
Contents
Lesson Overview
s s s
Purpose Objectives Documentation
CCS No.7 Characteristics

s
4-3
4-3
Network Elements
Point Codes CCS No. 7 Functional Parts (1)

s s
4-5 4-7
4-7 4-7
Message Transfer Part User Parts
CCS No. 7 Functional Parts (2)

s s s
4-9
4-9 4-9 4-9
ISDN User Part Signaling Connection Control Part Transaction Capabilities Application Part
SCCP Message Types

s
4-11
4-11
Segmentation and Re-assembly
Simplified SCCP UDT Message Structure SCCP Message Routing Using Point Codes SCCP Message Routing Using a Global Title Intermediate and Final GTT
4-13 4-15 4-17 4-19
Issue 8.2 4-i
s s
Intermediate GTT Final GTT
4-19 4-19
SCCP and TCAP Users Recognizing Final and Intermediate GTT IN SCCP Message Routing TCAP Message Structure
s s
4-21 4-23 4-25 4-27

4-27 4-29
Transaction Sub-layer Component Sub-layer
INAP Messages IN Call Example Summary NOTES Exercise
4-31 4-33 4-34 4-35 4-36
4-ii
Issue 8.2
Lesson Overview
Purpose
IN (Intelligent Network) calls are triggered in the SSP (Service Switching Point) and processed in the SSP, the SCP (Service Control Point) and the IP (Intelligent Peripheral). The SSP, SCP and/or IP exchange IN information using CCS No.7 (Common Channel Signaling No. 7) and INAP (Intelligent Network Application Part) operations. This chapter explains the CCS No.7 network that is used to transport INAP messages.
Objectives
Upon completion of this lesson you will be able to:

s s
List the different types of signaling points in a typical C7 network. State the functions performed by each of the four levels associated with CCS No. 7 signaling. List the different user parts of CCS No.7. State the functions of SCCP (Signaling Connection Control Part) and Global Title Translation. State the function of TCAP (Transaction Capabilities Application Part). ITU-T Recommendations Q.700-Q767 ETSI Specications ETS 300 374-1
s s
Documentation
s s
Issue 8.2
4-1
SCP
STP
SEP
SEP
SEP
SEP
SEP
SEP
Legend: SEP - Signaling End Point STP - Signaling Transfer Point SCP - Service Control Point = Signaling Link = Voice Circuits
Figure 4-1.
CCS No. 7 Characteristics
4-2
Issue 8.2
CCS No.7 Characteristics

CCS No.7 is a signaling system that is dened by ITU-T (International Telecommunications Union Telecommunication Standardization Sector). It meets the requirements of call control signaling for telecommunications services such as ISDN (Integrated Services Digital Network) and circuit-switched data transmission. In a telephony network, CCS No. 7 provides an advanced method of signaling in which signaling messages are passed over a common channel. The common channel is dedicated to CCS No7. messages and it is called a signaling link. Transmission over these signaling links is faster than the conventional, in-band signaling methods. The signaling information is transmitted in the form of labeled messages called signal units. It is important to remember that the common channel is separate from the voice circuit.
Network Elements
The signaling network consists of two types of network elements:

s s
SEP (Signaling End Point) STP (Signaling Transfer Point)
Refer to the gure on the opposite page for an example of a CCS network. An SEP provides high speed, common channel signaling connections used for circuit-related signaling messages and non-circuit related signaling messages that are destined for the exchange. A circuit is a voice trunk. If signaling messages arriving at an SEP are circuit related they can for example be used to set up the necessary speech circuits to complete a telephone call to the end user. An SEP also terminates voice, whereas an STP does not. This is the difference between an SEP and an SEP. The STP transfers signaling messages that arrive on one signaling link to a second signaling link, where the message is routed towards the destination. An STP normally does not contain voice circuits. It has the important function of transferring messages (either to another STP or to an SEP) towards their nal destination.
Issue 8.2
4-3
PC= 800
SCP
DPC = 500 OPC = 100
STP
PC= 700
Signal Unit
OPC =100 DPC=500
SEP
SEP
PC= 500
PC= 600
SEP
PC= 100
SEP 200
PC=
SEP 300
PC=
SEP PC=
400
Legend: SEP - Signaling End Point STP - Signaling Transfer Point SCP - Service Control Point = Signaling Links = Voice Circuits
Figure 4-2.
Point Codes
4-4
Issue 8.2
Point Codes
For signaling information to move from one signaling point to another in the network, each signaling point in the network must be uniquely identied. Each CCS No. 7 network exchange is identied by a number called a point code. The point code is like an address that is used to transfer signaling information to that specic exchange. No two signaling points in the same network can have the same address. Each signal unit, containing circuit or non-circuit related data, that is sent from one exchange to the other, has an OPC (Originating Point Code) and a DPC (Destination Point Code). The OPC addresses the exchange that has sent the message, the DPC addresses the signaling point for which the message is destined. In the gure opposite an example of a network is provided in which a signal unit is sent from one signaling point to another. In the signal unit the OPC and the DPC are provided. An signaling point receiving a signal unit checks the DPC of the signal unit against its own point code, if:
s s
the DPC matches, the data is extracted from the signal unit. the DPC does not match, the signaling point acts as an Signal Transfer Point (STP) for the message and routes the signal unit to its destination.
Issue 8.2
4-5
OSI Layers
Users of ITU-T CCS No. 7 (including INAP)
TCAP Users
7
4-6
(Level 4)
TCAP
ISDN User Part (ISUP)

(Level 4)
Telephone User Part (TUP)

(Level 4)
(Level 4)
SCCP
2 1
MTP (Levels 1 - 3)
Figure 4-3.
4-6
Issue 8.2

The gure on the opposite page shows the CCS No.7 functional levels. The CCS No. 7 has two major parts of software in which signal processing functions are performed:
s s
Message Transfer Part (MTP) User Part (UP)
The CCS No. 7 has four functional levels. Levels 1-3 are within the MTP and level 4 is for the UP. These functional levels correspond to the OSI layers.
Message Transfer Part
The MTP is the hardware and software used to transfer messages between two CCS No. 7 signaling points. The MTP provides the transport system for the UP and has the following three functional levels:
s
Level 1 - Signaling Data Link Functions - includes the physical and electrical characteristics that make up the link between two signaling points. Level 2 - Signaling Link Functions - controls functions of the link, and is responsible for error free transport of signal units sent and received. Level 3 - Signaling Network Functions - handles procedures such as message routing and signaling network management.
User Parts
The CCS No. 7 Level 4, known as the MTP User functions, denes the functions of the signaling system that are specic to users. ITU-T has dened several user functions of CCS No. 7, but only the following are discussed:
s s s s
TUP - Telephone User Part ISUP - ISDN User Part SCCP - Signaling Connection Control Part TCAP - Transaction Capabilities Application Part
Telephone User Part

The TUP denes the circuit related signaling functions necessary for CCS No. 7 to control national and international telephone calls. Countries which only support POTS (Plain Old Telephone System) can use the TUP.
Issue 8.2
4-7
OSI Layers
Users of ITU-T CCS No. 7 (including INAP)
TCAP Users
7
(Level 4)
TCAP
4-6
ISDN User Part (ISUP)

(Level 4)
Telephone User Part (TUP)

(Level 4)
SCCP
(Level 4)
2 1
MTP (Levels 1 - 3)
Figure 4-4.
4-8
Issue 8.2

ISDN User Part
ISUP denes the circuit related signaling functions needed for basic and supplementary services for ISDN voice and non-voice applications. Countries supporting ISDN and POTS can use ISUP for both ISDN and POTS, or ISUP for ISDN, and TUP for POTS. The SCCP provides functions additional to the MTP. One additional service is the provision of connectionless and connection-oriented network services to transfer circuit related and non-circuit related signaling information. The advantage of SCCP is exible routing of messages through the network. The messages received from the MTP level do not need to be unpacked. SCCP is used by several applications, such as Intelligent Network (INAP), ISDN supplementary services and MAP (Mobile Application Part) which is used for wireless telephony. To transport INAP messages in a CCS No. 7 network the SCCP connectionless network services are used. The connectionless SCCP service provides the user TCAP with two primary functions:
s
Signaling Connection Control Part
The ability to transfer signaling messages in the signaling network without the setup of a signaling connection. The ability to transfer signaling messages in the network using a virtual network address. This address is called a Global Title.
Transaction Capabilities Application Part
Transaction Capabilities Application Part (TCAP) provides services for interactive applications distributed over exchanges and specialized centers (for example Service Control Points) in a CCS No. 7 telecommunication network. TCAP provides the means to establish non-circuit-related communication between two processes in the signaling network. TCAP interfaces between SCCP and the TCAP users. If a TCAP user sends non-circuit related information through the CCS No.7 network in an SCCP message, TCAP takes care of the non-circuit related message structure, as well as other applications. Examples of interactive applications in the exchange that use the services of TCAP are:
s s
Intelligent Network Application Part (INAP) Mobile Application Part (MAP)
Issue 8.2
4-9
SCCP Message Types: Unit Data (UDT) Unit Data Service (UDTS) Extended Unit Data (XUDT) Extended Unit Data Service (XUDS)
Figure 4-5.
SCCP Message Types
4-10
Issue 8.2
SCCP Message Types

Four types of connectionless messages are used in a CCS No. 7 network for transporting INAP messages: 1. UDT (Unit Data) The UDT is used to transport user data and SCCP Management messages in the connectionless mode. The maximum length of an UDT message is 272 octets. 2. UDTS (Unit Data Service) The UDTS indicates to the originating SCCP user that a UDT message cannot be delivered to the specied destination. The data eld of the UDT message and the reason for the return are included in the UDTS message. 3. XUDT (Extended Unit Data) The XUDT is used to support segmentation and re-assembly of user data blocks up to 2048 octets. It also supports the HOP Counter which can be used to prevent network problems such as circular routing. An XUDT can also be used when segmentation and re-assembly is not required to take advantage of the hop counter. 4. XUDTS (Extended Unit Data service) The XUDTS is similar to the UDTS except that it is used to respond to an XUDT failure condition.
Segmentation and Reassembly
SCCP connectionless segmentation is a service provided transparently to the SCCP user. It allows the connectionless transfer of a larger block of user data than can be contained in a single UDT or XUDT message. The messages are identied by their routing label. The SCCP provides the service by breaking up a large block of user data into smaller blocks called segments, transmitting the segments as user data in XUDT messages, and re-combining the segments before passing the original block of user data to the destination SCCP user. At the originating SCCP, the process is called segmentation. At the destination SCCP, this process is called re-assembly.
Issue 8.2
4-11
Order of bit transmission 8 7 6 5 4 3 2 1
Order of octet transmission
Routing label (DPC,OPC,SLS)
Message type code (UDT)
Called party address
Calling party address
Length indicator of user data
TCAP User data
Figure 4-6.
Simplied SCCP UDT Message Structure
4-12
Issue 8.2
Simplied SCCP UDT Message Structure

The gure on the opposite page shows the simplied format of an SCCP UDT message. It includes the following parameters:
s
Routing label This contains the following parts: Destination Point Code (DPC) Originating Point Code (OPC) Signaling Link Selection (SLS) Message type code This identies the message type. Called party address This contains the address indicating to whom the SCCP message is destined. The called party address includes the following elds: point code subsystem number global title Calling party address This contains the address of the exchange that has created the SCCP message. The structure of the calling party address is the same as the called party address. When an SCCP message is received at its destination and a response message is sent back, the calling party address of the received message is copied into the called party address. The calling address is now lled with the address of the exchange sending the response message. Data The data parameter eld is a variable length eld containing TCAP information to be transferred transparently between the SCCP user functions, i.e. application data.
s s s s
s s s s
Issue 8.2
4-13
TCAP
TCAP
SEP
SCCP
A STP 1 B 2
TCAP
STP C 3
SEP D
SCCP
DPC = D OPC = A
DPC= D OPC= A
Figure 4-7.
SCCP Message Routing Using Point Codes
4-14
Issue 8.2
SCCP Message Routing Using Point Codes

If an exchange has a non-circuit related message for another exchange, it sends a (X)UDT SCCP message towards the other exchange. The message can be delivered to the exchange using either point codes or a virtual network address (Global Title). How SCCP messages are delivered using both methods is described in the following sections.
Routing Using Point Codes

Refer to Figure 4-7. Exchange A has a non-circuit related message for Exchange D. Exchange A sends the data in an SCCP message to Exchange D. The SCCP message is routed based on the destination point code (DPC=D), that is available in the message. Each exchange receiving the message checks if the destination point code in the message is its own. If this is not true the exchange functions as an STP for the message and sends it to the next exchange. The message is sent from exchange to exchange until the destination (PC=D) is reached. For an SCCP message all exchanges in the network must be aware of where every other point code in the network is located. If a point code is added or removed changes have to be made to every exchange. Using Point Code routing is satisfactory for a network similar to that shown in Figure 4-7. In reality, however, networks are very much larger and more complex, and Point Code routing is therefore very difcult to implement.
Issue 8.2
4-15
TCAP
TCAP
SEP A
SCCP
SEP 1 B 2
TCAP TCAP
DPC = B OPC = A GT = 301
SEP C 3
SEP D
SCCP
TCAP
DPC = C OPC = B GT = 301
DPC = D OPC = C GT = 301
DPC= B OPC= A GT = 301
DPC= C OPC= B GT = 301
DPC= D OPC= C GT = 301
Figure 4-8.
SCCP Message Routing Using a Global Title
4-16
Issue 8.2
SCCP Message Routing Using a Global Title

An alternative way of routing the SCCP message to its nal destination is by using a virtual network address for each exchange. The virtual network address for an exchange is called a Global Title (GT). The SCCP message is routed to the nal exchange using the GT. In each exchange that receives an SCCP message, a translation of the GT is performed to nd the destination for the message. The process of looking at a GT and translating the GT to a destination is called Global Title Translation (GTT). The gure opposite shows a simplied example of an SCCP message that is routed by global title from Exchange A to Exchange D. In this example Exchange D has a Global Title1 = 301. The process by which the SCCP message is routed to Exchange D is explained in the following steps: 1. In Exchange A an SCCP message is created containing the GT for Exchange D (GT = 301). Because Exchange A does not know the location of exchange D, it sends the message to an exchange that probably does. The GTT for Exchange A is set so that all GTs = 3xx are sent to Exchange B. This is done by setting the destination point code of the SCCP message to B. In the message a bit called the Routing Indicator (RI) is set to indicate that the message has not reached its nal destination. The message also includes the GT to indicate the nal destination of the message. 2. Exchange B receives the CCS No.7 message with a destination point code that is equal to the point code of exchange B. It therefore unpacks the message. If the RI indicates that the exchange is not the nal exchange for the SCCP message, it performs a GTT to nd the destination. The GTT for Exchange B for the GT= 30x is set to Exchange C. The SCCP message together with the RI and the GT are sent to Exchange C. 3. Exchange C receives a CCS No.7 message from Exchange B and performs GTT to nd that the message is to be sent to D. Because Exchange D is the nal exchange, the GTT translation in Exchange C can have two outputs to send the message to Exchange D. They are called an Intermediate GTT and a nal GTT. The difference between these two GTTs is explained in the following sections. The SCCP message that is received in Exchange D, either a nal or intermediate GTT is unpacked. The non-circuit related data from Exchange A is received at its destination.
1.
The global title that is used by the SCCP does not only consist of a value as given in the example, but contains other values.The explanation of SCCP and these other values are not given here. Actually the GT in the lesson should be read as the GT-Address.
Issue 8.2
4-17
Intermediate GTT:
s
Final destination not yet found
Final GTT:
s
Final destination found
Figure 4-9.
Intermediate and Final GTT
4-18
Issue 8.2
Intermediate and Final GTT

Intermediate GTT
An intermediate GTT is a GTT in which the nal destination for the SCCP message has not yet been found, and that another exchange or entity still has to perform a GTT to nd the nal destination for the message. This is indicated to the next exchange by setting the RI to zero. In the example on the previous page the GTT translations of Exchange A and B were intermediate GTTs. A nal GTT is a GTT in which the nal destination for the SCCP message is found. A nal GTT can be performed in one of two ways:
s
Final GTT
An exchange performs GTT and knows that the message is for the next exchange (in Figure 4-8 the GTT in Exchange C). The message is sent to the nal exchange and the RI is set to the value one. This already indicates to the receiving exchange that a nal GTT is done in the previous exchange and that the receiving exchange does not have to perform GTT again. An exchange receives an SCCP message with the RI set to zero (an intermediate GTT having been performed in the previous exchange). After performing GTT the exchange recognizes that the SCCP message is for itself.
The second option of GTT has the result that for every message received an extra GTT is done. If a lot of messages are received this costs a lot of extra processor time. Therefore the rst is preferred.
Issue 8.2
4-19
SSN 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14-254 255
Application SSN not known SCCP Management reserved/CCITT ISUP OMAP MAP HLR VLR MSC EIR AUC ISDN Sup. Service spare TC Test Responder spare reserved/expansion
Figure 4-10.
SCCP and TCAP Users
4-20
Issue 8.2
SCCP and TCAP Users

In the introduction to this lesson it was explained that SCCP/TCAP can be used by different users such as INAP, ISDN supplementary Services and MAP. If an SCCP message is received at its nal destination (a nal GTT is received or performed) the contents of the SCCP message must be delivered to the correct user: INAP messages to the INAP software, MAP messages to the MAP software, etc. This is why in the SCCP message a parameter is also sent to indicate the contents of the SCCP message. The parameter is called a SSN (SubSystem Number). At the moment that an exchange receives a message with a nal GTT the SSN must be available. The table opposite lists the SSN numbers that are predened by ITUT. HLR (Home Location Register) and VLR (Visiting Location Register) are SSNs that are used by MAP for the registration of mobile subscribers. For INAP one of the remaining SSNs is selected. The values of the SSNs depend on the network supplier.
Issue 8.2
4-21
TCAP
TCAP
SEP SEP A
SCCP
STP 1
TCAP TCAP
DPC = B OPC = A RI = 0 GT = 301 SSN = 0 DPC = C OPC = B RI = 0 GT = 301 SSN = 0
STP C 2 3
TCAP
SEP D
SCCP
DPC = D OPC = C RI = 1 SSN = 1-255
DPC= B OPC= A RI = 0 GT = 301 SSN = 0
DPC= C OPC= B RI = 0 GT = 301 SSN = 0
DPC= D OPC= C RI = 1 SSN = 1-255
Figure 4-11.
Recognizing Final and Intermediate GTT
4-22
Issue 8.2
Recognizing Final and Intermediate GTT

A nal or intermediate GTT is recognized by the value of the Routing Indicator in the called party address of an (X)UDT or (X)UDTS message. If a nal GTT is done the SSN and the nal DPC must also be available. This leads to the following differences between a nal and intermediate GT. The result of an Intermediate GTT can be recognized by an RI set to 0 (Routing on GT) and the following data being available:
s s s
The Global Title of the nal exchange DPC = not Final DPC SSN = 0-255 (unknown or known)
The result of a nal GTT is recognized by an RI set to 1 (Routing on DPC) and the following:
s s
The Global Title of the nal destination is not available DPC = Final DPC SSN = 1-255 (known)
In Figure 4-11 an example is provided of an SCCP message routed from Exchange A to Exchange D. In Exchanges A and B intermediate GTTs are performed. In Exchange C a nal GTT is performed.
Issue 8.2
4-23
TCAP
DPC= SCP OPC= STP RI = 1 SSN = INAP
DPC = SCP OPC = STP RI = 1 SSN = INAP
CP
TCAP
STP
SCP
DPC = STP OPC = SSP RI = 0 GT = 0800123123 SSN =0-255
DPC= STP OPC= SSP RI = 0 GT = 0800123123 SSN = 0-255
SSP
SSP
Public Telephone Network Called Number 0800-123123 PBX Calling Subscriber 020-1234567 Service Provider
Figure 4-12.
IN SCCP Message Routing
4-24
Issue 8.2
IN SCCP Message Routing

The SCCP message that is created after triggering an IN call in the SSP is routed towards the SCP using the SCPs Global Title. The Global Title used to address the SCP is determined on a per call basis. For example it may be the same as the dialed number that is received in the SSP or the A-party number (CLI - Calling Line Identity). Figure 4-12 is an example of an SCCP message that is routed to the SCP after triggering an IN call in the SSP. The number received in the SSP (0800-123123) is used as the Global Title. If the STP performs GTT, then the SCCP message is sent from the SSP to the STP using an intermediate GTT. In the STP GTT is performed on the Global Title = 0800123123 where the GTT has been set to send all Global Titles starting with 0800 to the SCP with a nal GTT.
Issue 8.2
4-25
MTP Data
User Part Data
MTP Data
MTP
EOF User Message/Data
SCCP Message Header
Message Type
Routing Label
SCCP
CSL Component N Component 2 Component 1 TSL
TCAP
Parameter(s)
Operation
INAP
Figure 4-13.
TCAP Message Structure (1)
4-26
Issue 8.2
TCAP Message Structure

A TCAP message is used as an interface between SCCP and the users of TCAP. Each message that is received from the TCAP user is formatted to the TCAP structure and packed into the SCCP message. If a TCAP message is received TCAP extracts the TCAP user data in the order in which it was sent. A TCAP message consists of two layers:
s
Transaction Sub-layer (TSL) this deals with the exchange of messages containing between two TCusers. Component Sub-layer (CSL) this deals with components. These are the application protocol data units that exchange remote operations and their responses and, optionally, the dialogue portion for exchanging information related to application context or user information. INAP operations and parameters are packed into the component sub-layer.
Transaction Sublayer
In the transaction sub-layer data is available about each TCAP dialog. For each IN call there is a dialog between the two TCAP entities (SSP and SCP). The following TCAP Transaction Sub-layer messages are transferred between the entities: Begin Continue End Abort Unidirectional initiates a transaction. continues a transaction. terminates a transaction. terminates a transaction in an abnormal situation. is sent without initiating a transaction.
When a TCAP communication has been established (that is, after the calling TCAP user received the rst Continue message), either side may send any number of Continue messages. Either side may terminate the transaction.
Issue 8.2
4-27
MTP Data
User Part Data
MTP Data
MTP
EOF User Message/Data
SCCP Message Header
Message Type
Routing Label
SCCP
CSL Component N Component 2 Component 1 TSL
TCAP
Parameter(s)
Operation
INAP
Figure 4-14.
TCAP Message Structure (2)
4-28
Issue 8.2
Component Sub-layer
The Component Sub-Layer (CSL) is responsible for all communication with the applications using the services of TCAP (TC Users), i.e. Intelligent Network Application Part (INAP) or Mobile Application Part (MAP). The CSL maintains information about operations invoked by TC Users and correlates responses from remote applications. The exchange of messages between a local and a remote application is called a dialog. CSL is the user of the Transaction services provided by Transaction Sub-layer. The CSL supports the following ve component types: Invoke request operation to be performed at the remote end. The operations invoked can be classied as follows: Class-1 - Both Success/ Failure reported Class-2 - Only Failure is reported Class-3 - Only Success is reported Class-4 - No reply is required or allowed Return Result (Last) successful completion of operation. It contains the last or only result.
Return Result (Not Last) contains part of the result of the operation. Return Error Reject reports unsuccessful completion of operation. incorrect component received at the remote end.
If an INAP operation is sent to another entity this is done in an Invoke component. Depending on the class of the operation a Return Result or Return Error is expected. If a received message is not understood at all, a Reject component is sent back.
Issue 8.2
4-29
= CCS No. 7 Signaling Link = Voice Trunk = INAP messages
CP SCP
STP
SSP
SSP
PBX Calling Subscriber Service Provider
Figure 4-15.
INAP Messages
4-30
Issue 8.2
INAP Messages
This section provides information about the types of messages sent between the SSP, SCP and the IP. SSP, SCP and IP messages for queries and responses for IN calls are called INAP (Intelligent Network Application Protocol) operations. Each INAP operation may be regarded as a command sent to an application at the destination. Each operation has a number of associated parameters. These constitute data required by the receiving application. The contents and use of each INAP operation is dened by the ITU-T, as well as by ETSI. The ITU-T and ETSI recommendations are quite similar, because the ETSI recommendations are an extension of the ITU-T ones. What ETSI did was to dene a "core subset" of the ITU-T Capability Set 1 (CS-1) recommendations for implementation. The ETSI recommendations supplement the ITU-T recommendations, but their real value is in dening a core subset of the ITU-T recommendations for implementation. In this course the ETSI INAP messages are used. The ETS 300 374-1 recommendation is a complete list with explanations of each ETSI INAP operation, as well as a mapping table of ETSI INAP operations to ITU-T operations. Appendix A provides a brief description of each ETSI INAP operation and parameters. The following list provides examples of different INAP messages:
s
InitialDP An INAP message from the SSP to the SCP indicating that an IN call has been triggered. In this message the following data is available: Called Party number (the B-number) Calling Party number (the A-number) Connect This INAP message is sent from the SCP to the SSP. In this message a new B-number is provided. After receiving this message the SSP reroutes the A-party to the new B-number. PlayAnnouncement This INAP message is sent from the SCP to the SSP indicating that an announcement has to be played after the A-party has been connected to the IP. PromptAndCollectUserInformation This message is sent from the SCP to the SSP. After the A-party has been connected to the IP, the A-party is prompted to enter digits. The IP collects these digits and sends them back in an INAP message to the SCP.
s s s
Issue 8.2
4-31
TCAP
DPC= SCP OPC= STP RI = 1 SSN = INAP
DPC = SCP OPC = STP RI = 1 SSN = INAP
CP
TCAP
STP
SCP
DPC = STP OPC = SSP RI = 0 GT = 0800123123 SSN =0-255
DPC= STP OPC= SSP RI = 0 GT = 0800123123 SSN = 0-255
SSP
SSP
0800-123123 Public Telephone Network Called Number 0800-123123 PBX Calling Subscriber 020-1234567 Service Provider
Figure 4-16.
IN Call Example
4-32
Issue 8.2
IN Call Example
The gure opposite shows CCS No.7 messages sent between the SSP and the SCP after an IN call is triggered in the SSP. Subscriber A dials 0800-123123 to call an insurance company. The 0800 call is routed through the PSTN network to the SSP. In the SSP the following steps are performed: 1. After the call arrives at the SSP the call follows the Basic Call State Model. Because the 0800-123123 number must be recognized as an IN call, Detection Point 3 (Analysed_Info) is armed in the SSP. 2. The Basic Call State Model is interrupted and the SSP formulates an INAP message to query the SCP as to what is to be done for this particular call. 3. The INAP message sent to the SCP is called InitialDP. The InitialDP consists of a number of parameters. In this example: ServiceKey = 200 calledPartyNumber = 0800123123 callingPartyNumber = 020123456 callingPartysCategory = 0A eventTypeBCSM = 3 type of service used (for example freephone) dialed number A-party number ordinary calling subscriber The detection point that is hit is DP3
4. The INAP information is passed to TCAP and placed in the Component Sub-layer of the TCAP message. On top of the Component Sub-layer the Transaction Sub-layer is placed. Because this is the rst TCAP message between the SSP and SCP for this call, it is a TCAP Begin message. 5. The TCAP message is placed in the user data eld of the SCCP (X)UDT message. 6. The SCCP message is sent using Global Title Translation towards its destination. If GTT is to be performed in the STP the message is sent to the STP containing an intermediate GT. 7. The STP performs GTT and sends the SCCP message to the SCP using a nal GTT. 8. The message is received at the SCP and the TCAP data is extracted from the SCCP message. 9. The TCAP message is split into the Transaction Sub-layer and the Component Sub-layer. The INAP data is processed by the SCP. 10. The SCP translates the freephone telephone number of the service subscriber to their actual telephone number. The SCP responds by sending an INAP connect operation to the SSP. This INAP operation is packed in a TCAP Continue or TCAP End message. The SCCP address used to return the message to the SSP is retrieved from the Calling Party Address in the received SCCP message.
Issue 8.2
4-33
Summary
s
The CCS No.7 Network is subdivided into two network elements: SEP - the SEP receives messages that are destined to himself. STP - the STP receives messages that are not destined to himself.
s s
The CCS No.7 messages are called signaling units The MTP level within CCS No.7 is responsible for the error-free transport of the User Parts (UP) The different CCS No.7 User Parts are: TUP ISUP SCCP TCAP
SCCP messages are routed throughout the network using a virtual network address. This virtual network address is better known as the Global Title. The translation of a Global Title to a network address is called Global Title Translation (GTT). If the nal destination is found during GTT it is a nal GTT; if the nal destination is not found during GTT it is an intermediate GTT. The SCCP used for IN carries TCAP data. TCAP is the application part that is used for the transfer of INAP messages. It is used for the setup of a dialog and it is used to structure INAP messages sent between two entities.
s s
4-34
Issue 8.2
NOTES
Issue 8.2
4-35
Exercise
1. Which of the following are signaling points in a typical SS7 network: a) SSP b) STP c) SCP d) All of the above
2. What is an STP: a) An exchange that performs GTT b) An exchange that transfers signaling units towards their destination c) An exchange that receives signaling units with a DPC equal to their own Point Code d) An exchange that combines the SSP and IP functionality
3. Which of the following are functions of MTP Level 3: a) Denition of the physical and electrical characteristics that make up the link between two signaling points b) Error free transport of signal units sent and received c) Message routing and signaling network management d) None of the above
4-36
Issue 8.2
4. Which of the following are MTP Level 4 User Parts: a) TCAP b) ISUP c) SCCP d) All of the above
5. What does the abbreviation OPC stand for: a) Ofcial Point Code b) Other Point Code c) Originating Point Code d) Old Point Code
6. What is the function of SCCP in an intelligent network: a) The routing of calls to a destination PSTN number b) The transfer of signaling messages in the network. using a virtual address c) The transmission of voice and data d) None of the above
Issue 8.2
4-37
7. What is the function of GTT in an intelligent network: a) The translation of a virtual address to a physical address b) To provide a reliable means of reassembling the segments of an XUDT or XUDTS message c) The translation of a dialed number to a PSTN number d) To indicate whether or not the next destination of a message is its nal destination.
8. How can an intermediate GTT be recognized: a) The Routing Indicator is set to the same value as the DPC b) The Routing Indicator is set to zero c) The Routing Indicator is set to one d) It cannot be recognized
9. Where is the Global Title located: a) In the Called Party Address of the UDT message b) In the Called Party Address of the XUDT message c) In the Called Party Address of the XUDTS message d) All of the above
4-38
Issue 8.2
10. What is the function of TCAP messages in an intelligent network: a) The routing of circuit-related signaling messages. b) The routing of non-circuit-related signaling messages. c). The transport of INAP messages. d) None of the above.
11. Which of the following are INAP messages a) InitialDP b) PlayAnnouncement c) Connect d) All of the above
Issue 8.2
4-39
4-40
Issue 8.2
INAP MESSAGES
Purpose
This appendix describes the ETSI INAP operations (messages) and includes all parameters for each operation. It is provided for reference for the lesson on CCS 7 signaling only. For up-to-date information on ETSI INAP operations for service development, the appropriate AEX documentation should be consulted. The list of operations and parameter values is dened by ETSI. This list can be changed to meet the local needs of individual customers.
Issue 8.2
A-1
INAP MESSAGES
ETSI INAP Operations

CS-1 ETSI Operation Name ActivateServiceFiltering ActivityTest ApplyCharging ApplyChargingReport AssistRequestInstructions CallGap CallInformationReport CallInformationRequest Cancel CollectInformation Connect ConnectToResource Continue DisconnectForwardConnection EstablishTemporaryConnection EventNoticationCharging EventReportBCSM FurnishChargingInformation InitialDP InitiateCallAttempt PlayAnnouncement PromptAndCollectUserInformation ReleaseCall RequestNoticationChargingEvent Class* Timeout 1 3 2 2 2 4 4 2 2 2 2 2 4 2 2 4 4 2 2 2 2 1 4 2 2 sec. 2 sec. 2 sec. 2 sec. 4 sec. 2 sec. 2 sec. 2 sec. 2 sec. 4 sec. 2 sec. 2 sec. 2 sec. 2 sec. 2 sec. 2 sec. 2 sec. 2 sec. 4 sec. 2 sec. 5 min. 5 min. 2 sec. 2 sec. Sending Operation Entity Code (hex) SCF SCF SCF SSF SSF SCF SSF SCF SCF SCF SCF SCF SCF SCF SCF SSF SSF SCF SSF SCF SCF SCF SCF SCF 2a 37 23 24 10 29 2c 2d 35 1b 14 13 1f 12 11 1a 18 22 00 20 2f 30 16 19
A-2
Issue 8.2
INAP MESSAGES
CS-1 ETSI Operation Name RequestReportBCSMEvent ResetTimer SendChargingInformation ServiceFilteringResponse SpecializedResourceReport Figure 1-1.
Class* Timeout 2 2 2 4 4 2 sec. 2 sec. 2 sec. 2 sec. 2 sec.
Sending Operation Entity Code (hex) SCF SCF SCF SSF SSF 17 21 2e 2b 31
ETSI INAP Operation Codes
* The class value is explained in the section TCAP and INAP.
Operations From SSF to SCF
The following sections give a description of the different operations which are sent from the SSF tot the SCF.
ApplyCharging Report Operation

This operation is used by the SSF to report charging-related information to the SCF as requested by the SCF using the ApplyCharging operation.
Item 1
Parameter Name CallResult
AssistRequestInstructions
This operation is sent to the SCF by the assisting SSF in an assist or hand-off procedure. The operation is sent when the assisting SSF receives a message from the initiating SSF containing information indicating an assist or hand-off procedure.
Item 1 2 3 4
Parameter Name correlationID iPAvailable iPSSPCapabilities extensions
Issue 8.2
A-3
INAP MESSAGES
CallInformationReport Operation
This operation is used to send specic call information for a single call to the SCF as requested by the SCF in a previous CallInformationRequest operation.
Item 1 1.1 1.2 2
Parameter Name requestedInformationList requestedInformationType requestedInformationValue extensions
EventNoticationCharging
This operation is used by the SSF to report to the SCF the occurrence of a specic charging event type as requested by the SCF using the RequestNoticationChargingEvent operation.
Item 1 2 3 3.1 4 5
Parameter Name eventTypeCharging eventSpecicInformationCharging legID receivingSideID extensions monitorMode
EventReportBCSM
This operation is used to notify the SCF of a call related event previously requested by the SCF in a RequestReportBCSMEvent operation. The monitoring of more than one event could be requested with a RequestReportBCSMEvent operation, but each of these requested events is reported in a separate EventReportBCSM operation.
Item 1 2 2.1
Parameter Name eventTypeBCSM eventSpecicInformationBCSM collectedInfoSpecicInfo
A-4
Issue 8.2
INAP MESSAGES
Item 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 3 3.1 4 4.1 5
Parameter Name analyzedInfoSpecicInfo routeSelectFailureSpecicInfo oCalledPartyBusySpecicInfo oNoAnswerSpecicInfo oAnswerSpecicInfo oMidCallSpecicInfo oDisconnectSpecicInfo tCalledPartyBusySpecicInfo tNoAnswerSpecicInfo tMidCallSpecicInfo tdisconnectSpecicInfo legID receivingSideID miscCallInfo messageType extensions
InitialDP
This operation is sent by the SSF after detection of an armed TDP, to request the SCF for instructions to complete the call. The SCF uses the data provided in the associated parameters to determine the correct instructions.
Item 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Parameter Name serviceKey calledPartyNumber callingPartyNumber callingPartysCategory cGEncountered iPSSPCapabilities iPAvailable locationNumber originalCalledPartyID extensions highLayerCompatibility serviceInteractionIndicators additionalCallingPartyNumber forwardCallIndicators
Issue 8.2
A-5
INAP MESSAGES
Item 15 15.1 16 17 18
Parameter Name bearerCapability bearerCap eventTypeBCSM redirectingPartyID redirectionInformation
ServiceFilteringResponse
The SSF uses this operation to report to the SCF the values of counters specied in a previously received ActivateServiceFiltering operation.
Item 1 1.1 1.2 2 2.1 2.2 2.2.1 2.2.2 2.2.3 2.2.4 3
Parameter Name countersValue counterID counterValue lteringCriteria serviceKey addressAndService calledAddressValue serviceKey callingAddressValue locationNumber extensions
SpecializedResourceReport
This operation is used as the response to a PlayAnnouncement operation when the announcement completed indication is set. This operation does not contain any parameters.
Operations From SCF to SSF
The following sections give a description of the different operations which are sent from the SCF to the SSF.
A-6
Issue 8.2
INAP MESSAGES
ActivateServiceFiltering
When receiving this operation, the SSF handles calls made to a specic destination without any request for instructions from the SCF. In the case of service ltering, the SSP executes a specic service ltering algorithm. For the transfer of service ltering results, refer to the operation ServiceFilteringResponse.
Item 1 1.1 1.2 1.2.1 1.2.1.1 1.2.1.1.1 1.2.1.1.2 1.2.1.1.3 1.2.1.1.4 1.2.1.2 1.2.1.3 1.2.1.4 1.2.2 1.2.2.1 1.2.2.2 1.2.3 1.3 1.4 2 2.1 2.2 3 3.1 3.2 4 4.1 4.2 4.2.1 4.2.2 4.2.3 4.2.4
Parameter Name lteredCallTreatment sFBillingChargingCharacteristics informationToSend inbandinfo messageID elementaryMessageID text elementaryMessageIDs variableMessage numberOfRepetitions duration interval tone toneID duration displayInformation maximumNumberOfCounters releaseCause lteringCharacteristics interval numberOfCalls lteringTimeOut duration stopTime lteringCriteria serviceKey addressAndService calledAddressValue serviceKey callingAddressValue locationNumber
Issue 8.2
A-7
INAP MESSAGES
Item 5 6
Parameter Name startTime extensions
ActivityTest
This operation is used to check for the continued existence of a relationship (active dialogue) between the SCF and the SSF. If the relationship is still in existence, then the SSF will respond. If no reply is received (i.e. operation time-out), then the SCF will assume that the SSF has failed in some way and will take the appropriate action. This operation does not contain any parameters.
ApplyCharging
This operation is used by the SCF to request charging related information from the SSF. Upon termination of the call, the SSF responds with the requested charge for the call.
Item 1 2 3 3.1 4
Parameter Name aChBillingChargingCharacteristics sendCalculationToSCPIndication partyToCharge sendingSideID extensions
CallGap
This operation is used to request the SSF to reduce the rate at which specic service requests are sent to the SCF.
Item 1 1.1 1.2 1.3 1.3.1 1.3.2
Parameter Name gapCriteria calledAddressValue gapOnService calledAddressAndService calledAddressValue serviceKey
A-8
Issue 8.2
INAP MESSAGES
Item 1.4 1.4.1 1.4.2 1.4.3 2 2.1 2.2 3 4 4.1 4.1.1 4.1.1.1 4.1.1.1.1 4.1.1.1.2 4.1.1.1.3 4.1.1.1.4 4.1.1.2 4.1.1.3 4.1.1.4 4.1.2 4.1.2.1 4.1.2.2 4.1.3 4.2 4.3 4.3.1 4.3.1.1 4.3.1.1.1 4.3.1.1.1.1 4.3.1.1.1.2 4.3.1.1.1.3 4.3.1.1.1.4 4.3.1.1.2 4.3.1.1.3 4.3.1.1.4 4.3.1.2 4.3.1.2.1 4.3.1.2.2 4.3.1.3
Parameter Name callingAddressAndService callingAddressValue serviceKey locationNumber gapIndicators duration gapInterval controlType gapTreatment informationToSend inbandinfo messageID elementaryMessageID text elementaryMessageIDs variableMessage numberOfRepetitions duration interval tone toneID duration displayInformation releaseCause both informationToSend inbandinfo messageID elementaryMessageID text elementaryMessageIDs variableMessage numberOfRepetitions duration interval tone toneID duration displayInformation
Issue 8.2
A-9
INAP MESSAGES
Item 4.3.2 5
Parameter Name releaseCause extensions
CallInformationRequest
This operation is used to request the SSF to record specic information about a single call and report it to the SCF using the CallInformationReport operation.
Item 1 2
Parameter Name requestedInformationTypeList extensions
Cancel
The Cancel operation is sent by the SCF to cancel a specic previous PlayAnnouncement or PromptAndCollectUserInformation operation, or to cancel all active EventReportBCSM requests for a particular IN relationship. Canceling of all EventReportBCSM requests also includes the transition of the call to the idle state.
Item 1 2
Parameter Name invokeID allRequests
CollectInformation
This operation is used to request the SSF to perform the basic originating call processing actions which will collect destination information from a calling party (it is normally associated with a RequestReportBCSMEvent operation to arm Detection Point number 2 (DP2) and to specify the number of digits to be collected). This operation uses only the resources of the SSF/CCF to collect the information, unlike the PromptAndCollectUserInformation, which uses the capabilities of the SRF. It follows that the use of this operation is appropriate only for a call which has not yet left the setup phase.
Item 1
Parameter Name extensions
A-10
Issue 8.2
INAP MESSAGES
Connect
This operation is used to request the SSF to perform the call processing actions to route a call to a specic destination. To do so, the SSF may use destination information from the calling party (for example dialed digits) and existing call setup data depending on the information provided by the SCF. This operation is also used in the hand-off procedure.
Item 1 2 3 4 5 6 7 8 9 10 11 12 13
Parameter Name destinationRoutingAddress alertingPattern correlationID cutAndPaste originalCalledPartyID routeList scfID extensions serviceInteractionIndicators callingPartyNumber callingPartysCategory redirectingPartyID redirectionInformation
ConnectToResource
This operation is used to connect a call from the SSF to a specialized resource. After successful connection to the SRF, the interaction with the caller can take place. The SSF relays all operations to the SRF and all responses from the SRF.
Item 1 1.1 1.2 2 3
Parameter Name resourceAddress ipRoutingAddress none extensions serviceInteractionIndicators
Continue
This operation is used to request the SSF to proceed with call processing at the detection point at which it previously suspended call processing to await SCF instructions (i.e. proceed to the next state in the call ow). The SSF continues call processing without substituting new data from the SCF.
Issue 8.2
A-11
INAP MESSAGES
This operation does not contain any parameters.
DisconnectForwardConnection
This operation is used in the following two cases: 1. To clear a connection to the SRF. The operation is used to explicitly disconnect a connection to a resource (SRF) established previously with a ConnectToResource operation. It is used for a forward disconnection from the SSF. 2. To clear a connection to an assisting SSF. The operation is sent to the non-assisting SSF of a pair of SSFs involved in an assist procedure. It is used to disconnect the temporary connection between the initiating SSF and the assisting SSF, and the assisting SSF and its associated SRF. This operation does not contain any parameters.
EstablishTemporaryConnection
This operation is used to create a connection between an initiating SSF and an assisting SSF as part of a service assist procedure. It can also be used to create a connection between a SSF and a SRF, for the case where the SRF exists in a separately addressable entity.
Item 1 2 3 4 5
Parameter Name assistingSSPIPRoutingAddress correlationID scfID extentions serviceInteractionIndicators
FurnishChargingInformation
This operation is used to request the SSF to generate a call record or to include some information in the default call record.
Item 1
Parameter Name FCIBillingChargingCharacteristics
A-12
Issue 8.2
INAP MESSAGES
InitiateCallAttempt
This operation is used to request the SSF to create a new call to a called party using address information provided by the SCF. An Event Detection Point Request (EDP-R) shall be armed on answer and on all call failure events, in order to have the SCF treat this call appropriately when one of these events is encountered.
Item 1 2 3 4 5
Parameter Name destinationRoutingAddress alertingPattern extensions serviceInteractionIndicators callingPartyNumber
PlayAnnouncement
This operation is used for in-band interaction with a public telephone network user. It indicates that an announcement must be played to the caller.
Item 1 1.1 1.1.1 1.1.1.1 1.1.1.2 1.1.1.3 1.1.1.4 1.1.2 1.1.3 1.1.4 1.2 1.2.1 1.2.2 1.3 2 3 4
Parameter Name informationToSend inbandinfo messageID elementaryMessageID text elementaryMessageIDs variableMessage numberOfRepetitions duration interval tone toneID duration displayInformation disconnectFromIPForbidden requestAnnouncementComplete extensions
Issue 8.2
A-13
INAP MESSAGES
PromptAndCollectUserInformation
This operation is used to interact with the calling party in order to collect information. It instructs the SSF to play a prompting announcement and to collect additional digits from the calling party.
Item 1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 2 3 3.1 3.1.1 3.1.1.1 3.1.1.2 3.1.1.3 3.1.1.4 3.1.2 3.1.3 3.1.4 3.2 3.2.1 3.2.2 3.3 4
Parameter Name collectInfo minimumNbOfDigits maximumNbOfDigits endOfReplyDigit cancelDigit startDigit rstDigitTimeout interDigitTimeout errortreatment interruptibleAnnInd voiceInformation voiceBack disconnectFromIPForbidden informationToSend inbandinfo messageID elementaryMessageID text elementaryMessageIDs variableMessage numberOfRepetitions duration interval tone toneID duration displayInformation extensions
A-14
Issue 8.2
INAP MESSAGES
ReleaseCall
This operation is used by the SCF to tear down an existing call at any phase of the call for all parties involved in the call. This operation may not be sent to an assisting SSF, except in the case of a hand-off procedure.
Item 1
Parameter Name Cause
RequestNoticationChargingEvent
This operation is used to instruct the SSF how to manage the charging events which are received from other functional entities not under the control of the service logic instance.
Item 1 2 3 3.1
Parameter Name eventTypeCharging monitorMode legID sendingSideID
RequestReportBCSMEvent
This operation is used to request the SSF to arm a particular EDP-R or EDP-N in order to monitor for a call-related event (for example busy or no answer), then send a request or notication back to the SCF when the event is detected.
Item 1 1.1 1.2 1.3 1.3.1 1.4 1.4.1 1.4.2 2
Parameter Name bcsmEvents eventTypeBCSM monitorMode legID sendingSideID dpSpecicCriteria numberOfDigits applicationTimer extensions
Issue 8.2
A-15
INAP MESSAGES
ResetTimer
This operation is used by the SCF to refresh the SSF application level timer in order to avoid a time-out at the SSF. The timer determines the length of time to wait for messages from the SCF. If it expires, the IN call is torn down.
Item 1 2 3
Parameter Name timerID timerValue extensions
SendChargingInformation
This operation is used to instruct the SSF on the charging information to be sent by the SSF. The sending of charging information can be charge pulses or signaling or internal if the SSF is located in a local exchange. In the local exchange, either the charge meter can be updated or a standard call record created.
Item 1 2 2.1 3
Parameter Name sCIBillingChargingCharacteristics legID sendingSideID extensions
A-16
Issue 8.2
ACRONYMS
B
Purpose
This appendix expands all the acronyms used in this course.
Lesson Overview
Issue 8.2
B-1
ACRONYMS
ACRONYMS AND ABBREVIATIONS

ACP ADN ADOB AOL ASCII BCC BCHPS BCSM CAS CC CCIS6 CCF CCS CCS7 CCS7NA Action Control Point Abbreviated Dialing Number Alternate Destination on Busy Application Oriented Language American Standard Code for Information Interchange Basic Calling Card B-Channel Packet Switching Basic Call State Model Channel Associated Signalling Calling Card Common Channel Interofce Signaling, system 6 Call Control Function Common Channel Signaling Common Channel Signaling, system 7 Common Channel Signaling system 7, North American version Calling Line Identity Component Sub-Layer Closed Users Group District Code Direct Common Channel Interofce Signaling, system 6 Disallowed Destination Number Prex Decision Graph Dialed Number
CLI CSL CUG DC DCIS6 DDNP DG DN
B-2
Issue 8.2
ACRONYMS
DP DPC DRCC DTMF EBCDIC EDGE EMM ETSI FAC FDOC GTT GUI ICLI INAP IP ISDN ISUP ITU-T
Detection Point Destination Point Code Destination Restricted Calling Card Dual Tone Multi Frequency Extended Binary-Coded Decimal Interchange Code Enhanced Decision Graph Editor Element MediationModule European Telecommunications Standards Institute Feature Access Code Focused Destination Overload Controls Global Title Translation Graphical User Interface International Calling Line Identity Intelligent Network Application Part Intelligent Peripheral Integrated Services Digital Network Integrated Services digital network User Part International Telecommunications Institute Telecommunications sector International Virtual Private Network Maximum Calls Allowed Multi Function Operations System Mobility Routing Mobility Routing Update Message Transfer Part Network Access Code
IVPN MCA MFOS MR MRU MTP NAC
Issue 8.2
B-3
ACRONYMS
NCP NETSTAR
Network Control Point Network Subscriber Transaction, Administration, and Recording system Network Management Network Management System Network Services CompleX Origination Point Code Private Branch eXchange Point Code Pulse Code Modulation Personal Identication Number Periodic Pulse Metering Personal Number Personal Number UpdaTe Public Switched Network Public Switched Telephone Network Post, Telephone and Telegraph Remote Access Code Routing Indicator Service Access Code Service Announcememt System Signaling Connection and Control Part Service Creation Environment Service Creation Environment Service Control Function Service Control Point Function
NM NMS NSCX OPC PBX PC PCM PIN PMM PN PNUT PSN PSTN PTT RAC RI SAC SAS SCCP SCE SCEF SCF SCP
B-4
Issue 8.2
ACRONYMS
SCCP SEFM SEP SIB SLL SLS SMF SMS SP SPA SRF SS6 SS7 SSF SSN SSP STEP STP TC TCAP TNM/TIM TSL TT TUP UDT
Signaling Connection and Control Part Switch Element Fault Management System Signaling End Point Service Independent Building block Service Logic Language Signaling Link Selection Service Management Function Service Management System Service Package Service Package Application Specialized Resource Function Signaling System 6 Signaling System 7 Service Switching Function SubSystem Number Service Switching Point Signal Transfer and End Point Signal Transfer Point Transaction Capability Transaction Capability Application Part Total Network Management Integration Module Transaction Sub-Layer Translation Type Telephony User Part Unit DaTa
Issue 8.2
B-5
ACRONYMS
UDTS UP VPN VPNID XUDT XUDTS
Unit DaTa Service User Part Virtual Private Network Virtual Private Network IDentication number eXtended Unit DaTa eXtended Unit DaTa Service
B-6
Issue 8.2

In Overview

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

In Overview

Hochgeladen von

Copyright:

Verfügbare Formate

Intelligent Network Overview STUDENT GUIDE

Issue 8.2 May 1998 IN1000

Lucent Technologies Proprietary See notice on rst page

Lucent Technologies Proprietary See notice on rst page

Lucent Technologies Proprietary See notice on rst page

Lucent Technologies Proprietary See notice on rst page

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Purpose Objectives Documentation

Users and Providers of IN Services

Users and Providers of IN Services

Advantages to the network provider

Lucent Technologies Proprietary See notice on rst page

Issue 8.2 1-i

Types of Detection Points

Arming Static Detection Points

Static DP Criteria Table

Mated Pairs Stand Alone SCPs

IN Call Example Using the SCF Service Management Function

Service Creation Environment Function

Definition Functions Service Packages

Service Creation Example Decision Graph The SRF

1-45 1-47 1-49

Configuration Operations Support Systems

Summary NOTES Exercise

1-55 1-56 1-57

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

On completion of this lesson participants will be able to:

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Users and Providers of IN Services

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Users and Providers of IN Services

Users and Providers of IN Services

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Advantages to the network provider:

Additional network trafc Higher call completion rates

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Advantages to the network provider

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Advantages to the service provider:

Advantages to the Service Provider

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Advantages to the service provider

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Advantages to the service subscriber:

Flexible charging Call queuing Flexibility in who maintains the database

Advantages to the Service Subscriber

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW

Advantages to the service subscriber

Lucent Technologies Proprietary See notice on rst page

INTELLIGENT NETWORK OVERVIEW