SIST ETS 300 695 E1:2003

• Abstract:

  ETS stage 2 description for the processing of PISN calls to and from a CTM user

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 695 ed.1 (1996-03) - Private Integrated Services Network (PISN); Cordless Terminal Mobility (CTM); Call handling additional network features; Functional capabilities and information flows

SIST ETS 300 695 E1:2003 is the Slovenian adoption of ETS 300 695 Edition 1, published by SIST from the European Telecommunications Standards Institute (ETSI). It specifies stage 2 functional capabilities and information flows for Cordless Terminal Mobility (CTM) call handling in Private Integrated Services Networks (PISNs), covering both incoming and outgoing call handling additional network features. The document is aimed at people who design, integrate, or assess PISN call control and signaling for CTM users.

What does SIST ETS 300 695 E1:2003 specify?

SIST ETS 300 695 E1:2003 specifies the stage 2 description for processing PISN calls to and from a CTM user. It defines two related services - ANF-CTMI for incoming calls and ANF-CTMO for outgoing calls and supplementary service requests - and shows how the network should behave around location-dependent CTM users.

The standard applies to circuit-mode basic services. It focuses on the functional entities inside the PISN and the information flows between them, while the detailed information exchange between the PISN and cordless terminals is outside its scope.

The document is organized into a short front matter, Scope, Normative references, Definitions and abbreviations, then two technical parts:

• Clause 4 for ANF-CTMI
• Clause 5 for ANF-CTMO

Each of those parts contains a functional model, information flows, SDL diagrams, functional entity actions, and allocation of functional entities to physical locations. A key practical point is that this is a stage 2 standard: it is meant to guide stage 3 signaling protocol work, not to provide a testing method.

What are the key requirements of SIST ETS 300 695 E1:2003?

The core requirement of SIST ETS 300 695 E1:2003 is that a stage 3 standard shall be able to provide the information flows shown for ANF-CTMI and ANF-CTMO, and that the stage 3 behavior must remain consistent with the stage 2 models. In practice, implementers use this document to define how location-aware CTM calls are routed, verified, accepted, redirected, or released.

ANF-CTMI: incoming calls to a CTM user

Clause 4 defines five functional entities for ANF-CTMI:

• FE1 - CTM incoming call execution
• FE2 - CTM incoming call detection and control
• FE3 - Routing information provision
• FE4 - Visited location control and execution
• FE5 - CTM service access agent

These entities are connected by the relationships ra, rb, and rc. In practice, this means the network first detects an incoming call, asks where the CTM user is located, then redirects the call to that location if the user is known and accessible.

Clause 4.3 defines the main information flows:

• DIVERT carries the redirection request from FE2 to FE1
• ENQUIRE asks FE3 for the CTM user's current location
• INFORM passes the CTM user's identity between the home and visitor functions

The DIVERT flow includes items such as the visitor PINX, connection type, caller number, CTM user number, and the divert result. The ENQUIRE flow returns the location result and may include data such as the visitor PINX or diversion-related information when relevant. The practical effect is that the incoming call cannot simply be routed by a fixed address; the network needs current location data before it can complete the call.

Clauses 4.4 and 4.5 show how the entities behave in success and failure cases. FE2 queries FE3, FE1 creates the redirected call, FE4 checks whether the user is registered at the visitor location, and FE5 checks whether the CTM user is accessible. If the user is not known, not registered, or not accessible, the original call is released or rejected.

Clause 4.6 allocates the functional entities to physical locations such as originating PINX, home PINX, visitor PINX, terminating PINX, and fixed part (FP). This matters because a real network implementation has to place the functions at the right node.

ANF-CTMO: outgoing calls from a CTM user

Clause 5 defines three functional entities for ANF-CTMO:

• FE1 - CTM outgoing call detection and control
• FE2 - Visited location information provision
• FE3 - Home location CTM call control

Here, FE1 checks the CTM user's identity, FE2 looks up the visitor data base, and FE3 handles remote processing at the home location when needed. In practice, this supports either local call handling or redirection to the home location if the visitor location should not process the request.

Clause 5.3 defines two key information flows:

• VERIFY, used by FE1 to check the calling user's number against the VDB
• INFORM1, used when a call is redirected to the home location for remote processing

VERIFY can return a positive result with a service profile or a negative result when no matching record is found. INFORM1 can carry the original destination number so the home location can continue normal outgoing call control. This is the practical mechanism that lets the network decide whether to process a call locally or at home, while preserving the destination information needed for completion.

Clauses 5.4 and 5.5 show the normal behavior and functional entity actions. If verification succeeds, FE1 can either continue locally or redirect the call to FE3. If verification fails, the basic call request is rejected. Clause 5.6 places FE1 at the originating PINX, FE2 at the visitor PINX, and FE3 at the home PINX, which is important for network design and node mapping.

What terms does SIST ETS 300 695 E1:2003 define?

• Additional Network Feature (ANF) - a network feature treated as a separate service capability, such as ANF-CTMI or ANF-CTMO.
• Cordless Terminal Mobility (CTM) - the ability of a cordless terminal to keep using PISN services while moving, with the network tracking its location.
• CTM user - a PISN user whose calls are handled by CTMI, CTMO, or both.
• home PINX - the PINX that has direct access to the Home Data Base (HDB) entry for a CTM user.
• visitor PINX - the PINX that has direct access to the Visitor Data Base (VDB) currently associated with a CTM user.
• Private Integrated Services Network (PISN) - the private integrated services network environment for which the CTM features are specified.
• PINX - a Private Integrated Services Network Exchange, the network node used in the model.
• Functional Entity (FE) - a logical network function used to describe the service behavior.

Who uses SIST ETS 300 695 E1:2003?

SIST ETS 300 695 E1:2003 is used by telecommunications engineers, signaling protocol designers, and PISN or PBX vendors who need to implement CTM call handling. It is also relevant to network architects and system integrators who must place the home, visitor, and call-control functions in the correct nodes.

Quality managers and buyers can use it to check whether a product supports location-aware incoming and outgoing CTM handling in a way that matches the stage 2 model. Operators and service planners can use it when deciding how CTM users should be routed, verified, or redirected in a PISN.

Which standards are used with SIST ETS 300 695 E1:2003?

SIST ETS 300 695 E1:2003 relies on these normative references and companion standards:

• ETS 300 171 - gives the control aspects of circuit mode basic services, which CTMI and CTMO use as the basic-call foundation.
• ETS 300 415 - provides PTN terms and definitions, including several terms used for ANF, HDB, and VDB.
• ETS 300 237 - provides name identification supplementary services, including the calling user's name used in CTMI.
• ETS 300 387 - defines the method for specifying basic and supplementary services, including the stage approach used here.
• ITU-T Recommendation I.210 - provides the service principles used to describe telecommunication services.
• ITU-T Recommendation Z.100 - defines SDL, the notation used for the functional behavior diagrams.
• ISO/IEC 11579-1 - gives reference configurations for PISN exchanges (PINX).
• ISO/IEC 11571 - defines numbering and sub-addressing in PISN.

What does the SIST ETS 300 695 E1:2003 document contain?

The document contains two complete service descriptions, one for ANF-CTMI and one for ANF-CTMO. Each service description includes a functional model, descriptions of the functional entities, information flow sequences, definitions of the information flows, SDL diagrams, functional entity actions, and allocation of the entities to physical locations.

It also includes tables that describe the content of the main flows, including DIVERT, ENQUIRE, INFORM, INFORM1, and VERIFY. The physical-location tables show how the functional entities can be mapped to originating, home, visitor, terminating, and fixed-part positions in different scenarios.

For implementation work, the most useful parts are the flow sequences and the SDL diagrams, because they show how the network should react in successful and unsuccessful cases. For architecture work, the allocation tables show where each function belongs in the PISN.

SLOVENSKI STANDARD
01-december-2003
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,610RELOQRVWEUH]YUYLþQHJD
WHUPLQDOD&70'RGDWQHRPUHåQHIXQNFLMHUDYQDQMHVNOLFHP)XQNFLMVNH
]PRåQRVWLLQLQIRUPDFLMVNLSUHWRNL
Private Integrated Services Network (PISN); Cordless Terminal Mobility (CTM); Call
handling additional network features; Functional capabilities and information flows
Ta slovenski standard je istoveten z: ETS 300 695 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 695
TELECOMMUNICATION March 1996
STANDARD
Source: ETSI TC-BTC Reference: DE/BTC-01036
ICS: 35.120
Key words: PISN, CTM, mobility, ANF, stage 2, PTN
Private Integrated Services Network (PISN);
Cordless Terminal Mobility (CTM);
Call handling additional network features;
Functional capabilities and information flows
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1996. All rights reserved.

Page 2
ETS 300 695: March 1996
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 695: March 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 Definitions .8
3.2 Abbreviations .9
4 ANF-CTMI .9
4.1 Description.9
4.2 Derivation of the functional model .9
4.2.1 Functional model description.9
4.2.2 Description of functional entities.10
4.2.2.1 CTM incoming call execution, FE1.10
4.2.2.2 CTM incoming call detection and control, FE2.10
4.2.2.3 Routing information provision, FE3 .10
4.2.2.4 Visited location control and execution, FE4.10
4.2.2.5 CTM service access agent, FE5.10
4.2.3 Relationship with a basic service .10
4.3 Information flows.11
4.3.1 Information flow sequences .11
4.3.2 Definition of information flows .13
4.3.2.1 DIVERT.13
4.3.2.2 ENQUIRE .14
4.3.2.3 INFORM.14
4.4 SDL diagrams for functional entities.14
4.4.1 Behaviour of FE1.15
4.4.2 Behaviour of FE2.16
4.4.3 Behaviour of FE3.17
4.4.4 Behaviour of FE4.18
4.4.5 Behaviour of FE5.19
4.5 Functional Entity Actions (FEAs) .19
4.5.1 FEAs of FE1.19
4.5.2 FEAs of FE2.19
4.5.3 FEAs of FE3.19
4.5.4 FEAs of FE4.20
4.5.5 FEAs of FE5.20
4.6 Allocation of functional entities to physical locations .20
4.7 Interworking considerations .20
5 ANF-CTMO .21
5.1 Description.21
5.2 Derivation of the functional model .21
5.2.1 Functional model description.21
5.2.2 Description of functional entities.21
5.2.2.1 CTM outgoing call detection and control, FE1.21
5.2.2.2 Visited location information provision, FE2.21
5.2.2.3 Home location CTM call control, FE3.21
5.2.3 Relationship with a basic service .21
5.3 Information flows.22
5.3.1 Information flow sequences .22
5.3.2 Definition of information flows .23
5.3.2.1 INFORM1.23
5.3.2.2 VERIFY.23
5.4 SDL diagrams for functional entities.24

Page 4
ETS 300 695: March 1996
5.4.1 Behaviour of FE1 . 24
5.4.2 Behaviour of FE2 . 25
5.4.3 Behaviour of FE3 . 25
5.5 Functional Entity Actions (FEAs). 25
5.5.1 FEAs of FE1 . 26
5.5.2 FEAs of FE2 . 26
5.5.3 FEAs of FE3 . 26
5.6 Allocation of functional entities to physical locations. 26
5.7 Interworking considerations . 26
History. 27

Page 5
ETS 300 695: March 1996
Foreword
This European Telecommunication Standard (ETS) has been produced by the Business
Telecommunications (BTC) Technical Committee of the European Telecommunications Standards
Institute (ETSI).
Transposition dates
Date of adoption of this ETS: 15 March 1996
Date of latest announcement of this ETS (doa): 30 June 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 December 1996
Date of withdrawal of any conflicting National Standard (dow): 31 December 1996

Page 6
ETS 300 695: March 1996
Blank page
Page 7
ETS 300 695: March 1996
1 Scope
This European Telecommunication Standard (ETS) describes the stage two of the Cordless Terminal
Mobility (CTM) call handling services for Private Integrated Services Networks (PISNs). It comprises two
related but distinct service descriptions, CTM Incoming Call Handling Additional Network Feature
(ANF–CTMI) and CTM Outgoing Call Handling Additional Network Feature (ANF-CTMO).
ANF-CTMI directs incoming calls to a CTM user within a PISN regardless of the CTM user's geographical
location within the PISN, provided the CTM user's location is known.
ANF-CTMO detects an outgoing call or request for a supplementary service from a CTM user and
establishes it as a basic call or signalling connection, respectively, regardless of the user's geographical
location within the PISN. It also provides the CTM user's service profile for use by outgoing call control, or
alternatively passes the call to the CTM user's home location for processing.
These ANFs are applicable to all circuit-mode basic services as defined in ETS 300 171 [1].
This ETS contains the stage 2 specifications of ANF-CTMI and ANF-CTMO. It identifies the functional
entities involved in the feature and the information flows between them. The specification of information
flows between the PISN and cordless terminals is beyond the scope of this ETS. ANF specifications are
produced in three stages according to the method specified in ETS 300 387 [4].
The purpose of the stage 2 specification is to guide and constrain the work on signalling protocols at
stage 3, while fulfilling the requirements of stage 1. Stage 1 and stage 3 are defined in separate
standards.
Conformance to this ETS is met by conforming to a stage 3 standard which fulfils the requirements of this
ETS that are relevant to the equipment for which the stage 3 standard applies. Therefore, no method of
testing is provided for this ETS.
2 Normative references
This ETS incorporates by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply only when incorporated in it by amendment or revision. For undated references the latest edition of
the publication referred to applies.
[1] ETS 300 171 (1992): "Private Telecommunication Network (PTN); Specification,
functional models and information flows; Control aspects of circuit mode basic
services".
[2] ETS 300 415 (1995): "Private Telecommunication Network (PTN); Terms and
definitions".
[3] ETS 300 237 (1993): "Private Telecommunication Network (PTN) –
Specification, functional model and information flows - Name identification
supplementary services".
[4] ETS 300 387 (1994): "Private Telecommunication Network (PTN); Method for
the specification of basic and supplementary services ".
[5] ITU-T Recommendation I.210 (1993): "Principles of telecommunication services
supported by an ISDN and the means to describe them".
[6] ITU-T Recommendation Z.100 (1993): "Specification and description language
(SDL)".
[7] ISO/IEC 11579-1 (1994): "Information technology - Telecommunications and
information exchange between systems - Private Integrated Services
Network - Part 1: Reference configurations for PISN exchanges (PINX)".

Page 8
ETS 300 695: March 1996
[8] ISO/IEC 11571 (1994): "Information technology - Telecommunications and
information exchange between systems - Numbering and Sub-addressing in
Private Integrated Services Network".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
Additional Network Feature (ANF): See ETS 300 415 [2].
address: See ETS 300 415 [2].
call; basic call: See ETS 300 171 [1].
calling user’s name: See ETS 300 237 [3]
Cordless Terminal Mobility (CTM): The ability of a cordless terminal to be in continuous motion whilst
accessing and using the telecommunications services offered by the PISN as well as the capability of the
network to keep track of the location of the cordless terminal within the coverage area of the radio system
used.
CTM user: A PISN user whose calls are processed by either or both of the CTMI and CTMO ANFs.
fixed part: A physical grouping of some or all of the fixed component parts of mobile radio system. These
would include one or more items of radio equipment attached to an antenna system. It could also include
common control functions and interfaces to the PTNX.
Home Data Base (HDB): See ETS 300 415 [2].
home PINX: The PINX which has direct access to the HDB entry for a particular CTM user.
Private Integrated Services Network (PISN): See ISO/IEC 11579-1 [7] .
Private Integrated Services Network Exchange (PINX): See ISO/IEC 11579-1 [7].
PISN number: See ISO/IEC 11571 [8].
signalling connection: A means of conveying supplementary service requests, independent of a basic
call.
supplementary service: See ITU-T Recommendation I.210 [5].
Visitor Data Base (VDB): See ETS 300 415 [2].
visitor PINX: The PINX which has direct access to the VDB currently associated with a particular CTM
user.
This ETS Refers To The Following Functional Entities (FES) Defined For Basic Call Control (see
ETS 300 171 [1]):
Call Control (CC);
Call Control Agent (CCA).
This ETS refers to the following inter-FE relationships defined for basic call control (see ETS 300 171 [1]):
r1;
r2;
r3.
Page 9
ETS 300 695: March 1996
This ETS refers to the following service elements defined for basic call control (see ETS 300 171 [1]):
- call history;
- connection type;
- destination number;
- destination subaddress;
- originating category;
- originating number;
- originating subaddress.
3.2 Abbreviations
For the purposes of this ETS the following abbreviations apply:
ANF-xxx "xxx" Additional Network Feature
CC Call Control functional entity
CCA Call Control Agent functional entity
CTM Cordless Terminal Mobility
CTMI CTM Incoming Call Handling
CTMO CTM Outgoing Call Handling
FE Functional Entity
FEA Functional Entity Action
FP Fixed Part
HDB Home Data Base
PINX Private Integrated Services Network Exchange
PISN Private Integrated Services Network
SDL Specification and Description Language
VDB Visitor Data Base
4 ANF-CTMI
4.1 Description
ANF-CTMI enables calls to be directed to a CTM user within the PISN. As there is no predetermined
access for the connection of a CTM user to the PISN, the directing of such calls requires that information
regarding the location of the user is available.
4.2 Derivation of the functional model
4.2.1 Functional model description
The functional model for ANF-CTMI shall be as shown in figure 1.
Home Functions
ra rb
FE1 FE2 FE3
rc
rc
FE4 FE5
Visitor Functions CTM service access
Figure 1: Functional model for ANF-CTMI

Page 10
ETS 300 695: March 1996
The functional model for ANF-CTMI shall comprise the following Functional Entities (FEs):
FE1: CTM incoming call execution;
FE2: CTM incoming call detection and control;
FE3: Routing information provision;
FE4: Visited location control and execution;
FE5: CTM service access agent.
The following functional relationships shall exist between these FEs:
ra: between FE1 and FE2;
rb: between FE2 and FE3;
rc: between FE1 and FE4 and between FE4 and FE5.
4.2.2 Description of functional entities
4.2.2.1 CTM incoming call execution, FE1
On request from FE2, this FE directs an incoming call to the CTM user by initiating a new call
establishment towards the CTM user's location and passing the CTM user's identity.
4.2.2.2 CTM incoming call detection and control, FE2
This FE detects an incoming call to a CTM user and requests FE1 to redirect the call to the CTM user's
location on the basis of information obtained from FE3.
4.2.2.3 Routing information provision, FE3
This FE provides details of the CTM user's location within the PISN to FE2 on request.
4.2.2.4 Visited location control and execution, FE4
This FE detects the incoming call and directs it to the CTM user's indicated PISN access.
4.2.2.5 CTM service access agent, FE5
This FE extends the incoming call to the appropriate CTM user using the identity provided by FE4.
4.2.3 Relationship with a basic service
An example of the relationship between the functional model and a basic service is shown in figure 2. This
example is used as the basis for the information flow sequence diagrams in subclause 4.3.1.
Hom e functions
rb
ra
FE1 FE2 FE3
r1 r2
CC CC
CCA
C allin g
rc
user
r2 rc
FE4 FE5
r3
CC
CCA
Visitor functions CTM service access
Figure 2: Functional entity model relationship

Page 11
ETS 300 695: March 1996
4.3 Information flows
4.3.1 Information flow sequences
A stage 3 standard shall be capable of providing the information flows shown in figures 3 to 7. It can
specify further information flows, e.g. to deal with additional exceptional conditions.
ANF-CTMI information flows are shown as solid arrows and basic call information flows are represented
by broken arrows. An ellipse embracing two information flows indicates that these flows occur together.
Within a column representing an ANF-CTMI functional entity, the numbers refer to functional entity actions
listed in subclause 4.5.
The information flow sequence for successful CTMI operation is shown
...