SIST ETS 300 817 E1:2003

• Abstract:

  To produce a draft ETS stage 2 description for CTM handover. Handover may only occur between Fixed Radio Parts (FRPs) at the same PINX;

• 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 817 ed.1 (1998-02) - Private Integrated Services Network (PISN); Cordless Terminal Mobility (CTM); Handover Additional Network Feature (ANF); Functional capabilities and information flows

SIST ETS 300 817 E1:2003 is the Slovenian version of ETS 300 817 Edition 1, published by SIST for Private Integrated Services Network (PISN) Cordless Terminal Mobility (CTM) handover. It specifies the Stage 2 functional capabilities and information flows for the Handover Additional Network Feature (ANF-CTH), so the network-side behaviour can be defined before signalling protocols are written. The document is aimed at people designing, implementing, or assessing CTM handover support in PISN equipment.

What does SIST ETS 300 817 E1:2003 specify?

SIST ETS 300 817 E1:2003 specifies the Stage 2 description of ANF-CTH for call handover in a PISN. It covers the case where a CTM user moves between overlapping location areas, and it limits handover to the same PINX, with the scope note also stating that handover occurs only between Fixed Radio Parts (FRPs) at the same PINX.

The document is organized around two main Stage 2 models:

Clause	Case covered
4	New location area selected by the CTM user
5	New location area selected by the network

In practice, Clause 4 and Clause 5 give the functional entities, the information flows, the entity behaviour, and the placement of the entities in the network. The air-interface information flow is outside the scope of the document, and the Stage 2 description is intended to guide Stage 3 signalling work.

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

SIST ETS 300 817 E1:2003 defines how ANF-CTH keeps an established call running while a CTM user moves to a new location area. The main practical point is that the feature is only for circuit mode basic services, and it is only meant for basic services where a brief interruption during handover is acceptable.

Clause 4 - CTM user selects the new location area

Clause 4 models handover with three Functional Entities (FEs): the CTM user's service agent, the CTM handover service execution entity, and the Security Parameter Storage entity. FE1 requests the handover, FE2 performs the reroute, and FE3 supplies security parameters on request. For implementers, this means the user-side agent starts the process, while the handover logic can fetch security data before deciding whether to continue.

Clause 4 uses the information flows ENQUIRE, HANDOVER, HO-ACCEPT, and HO-REJECT. ENQUIRE asks for current security parameters, HANDOVER carries the reroute request and result, and HO-ACCEPT or HO-REJECT confirm whether the user accepts the move or wants to stay on the old leg. The HANDOVER flow carries the CTM user's identity and may carry a call identifier, a cipher indication, and security parameters when needed.

Clause 4 also defines how the entities behave. FE2 can ask FE3 for security parameters, can accept or reject handover, and releases the old call leg after receiving HO-ACCEPT. For readers building protocol logic, this shows the decision points that control whether the call continues on the new location area or falls back to the old one.

Clause 5 - network selects the new location area

Clause 5 models handover with three different FEs: the CTM user's old service agent, the CTM handover service execution entity, and the CTM user's new service agent. FE6 selects a new location area, FE4 checks whether it can accept the call, and FE5 coordinates the user-side request. This matters in practice because the network, not the user, performs the location-area selection and the call setup to the new leg.

Clause 5 introduces HO-CHECK and HO-REQUEST in addition to HO-ACCEPT and HO-REJECT. HO-CHECK asks a candidate new service agent whether it can accept the call, while HO-REQUEST is the confirmed request to route the call through the new location area. HO-CHECK and HO-REQUEST both carry the CTM user's identity, may carry a call identifier, and include terminal information that is passed on for the handover process.

The behaviour rules in Clause 5 show how network handover proceeds in stages. FE6 can query one or more FE4 instances, select one that accepts the call, and then establish the new leg before waiting for HO-ACCEPT or HO-REJECT from FE5. For an implementer, this means the network must manage candidate selection, acceptance checking, and release of the old or new leg depending on the final outcome.

Stage 2 to Stage 3 relationship

SIST ETS 300 817 E1:2003 says Stage 3 standards must provide the Stage 2 information flows shown in the document, and they may add further flows for exceptional conditions. It also says conformance is achieved through a Stage 3 standard that satisfies the Stage 2 requirements relevant to the equipment. In practice, this means the document is the functional and signalling blueprint, not the final protocol specification.

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

• ANF-CTH - Cordless Terminal mobility Handover-Additional Network Feature, the feature that supports handover for a CTM user.
• CTM - Cordless Terminal Mobility, the mobility function for cordless terminals in the PISN.
• FE - Functional Entity, a logical block used to model responsibilities and exchanges in the handover process.
• FEA - Functional Entity Action, a numbered action tied to a point in the information flow sequence.
• PINX - Private Integrated services Network eXchange, the network exchange where the handover is controlled.
• VDB - Visitor Data Base, the database holding visitor-related information for a CTM user.
• location area - the coverage area in which a cordless terminal can make and receive calls after one location registration.
• visitor area - the coverage area associated with a CTM user's visit; in this standard, it is confined to a single PINX.

Who uses SIST ETS 300 817 E1:2003?

SIST ETS 300 817 E1:2003 is used by standards engineers and signalling protocol designers who need the Stage 2 model before writing Stage 3 behaviour. It is also relevant to PISN equipment vendors, CTM feature developers, and system integrators who have to map logical handover behaviour onto network entities and call-control functions.

Quality and conformance teams use it to check whether a Stage 3 implementation covers the right information flows, accepted and rejected handover paths, and entity placement scenarios. Buyers and technical reviewers can use it to judge whether a product supports CTM handover within the same PINX and for circuit mode basic services.

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

• CCITT Recommendation I.210 - provides the general principles for telecommunication services supported by ISDN and the terminology for supplementary services.
• ENV 41005 - gives the method used to specify basic and supplementary services of private telecommunication networks.
• ETS 300 171 - provides the functional model and information flows for control aspects of circuit mode basic services, which ANF-CTH builds on.
• ETS 300 415 - supplies the core PISN terms and definitions, including items such as PINX, FP, VDB, and visitor area.
• CCITT Recommendation Z.100 - defines Specification and Description Language (SDL), which the document uses for functional entity behaviour.
• ETS 300 816 - gives the service description for ANF-CTH at Stage 1, which Clause 2 says Stage 2 must fulfil.

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

The document contains two Stage 2 functional models, one for user-selected handover and one for network-selected handover. Each model includes SDL diagrams for entity behaviour, information flow sequence diagrams, and definitions of the flows exchanged between the entities.

It also contains tables for the contents of the key information flows, including which data items are mandatory or optional, and tables that allocate the Functional Entities to physical locations such as FP, end PINX, visitor PINX, and old or new FP. For implementers, these tables are the practical part of the standard because they show what each entity must send, receive, or decide during handover.

The document additionally uses numbered Functional Entity Actions to link the flow diagrams to implementation behaviour. That makes it useful for protocol design, software development, and conformance analysis, because the handover process is described as a sequence of explicit interactions rather than a general service statement.

SLOVENSKI STANDARD
01-december-2003
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,610RELOQRVWEUH]YUYLþQHJD
WHUPLQDOD&70'RGDWQDRPUHåQDIXQNFLMD$1)SUHGDMD)XQNFLMVNH]PRåQRVWL
LQLQIRUPDFLMVNLSUHWRNL
Private Integrated Services Network (PISN); Cordless Terminal Mobility (CTM);
Handover Additional Network Feature (ANF); Functional capabilities and information
flows
Ta slovenski standard je istoveten z: ETS 300 817 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 817
TELECOMMUNICATION February 1998
STANDARD
Source: BTC Reference: DE/BTC-01015
ICS: 33.020
Key words: Handover, mobility, PISN, stage 2, supplementary service
Private Integrated Services Network (PISN);
Cordless Terminal Mobility (CTM);
Handover Additional Network Feature (ANF);
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 1998. All rights reserved.

Page 2
ETS 300 817: February 1998
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 817: February 1998
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-CTH Stage 2 Description - new location area selected by the Cordless Terminal Mobility
(CTM) user .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 FEs.10
4.2.2.1 CTM user's service agent, FE1 .10
4.2.2.2 CTM handover service execution entity, FE2.10
4.2.2.3 Security Parameter Storage entity, FE3 .10
4.2.3 Relationship with a basic service .10
4.3 Information flows.10
4.3.1 Information flow sequences .10
4.3.2 Definition of information flows .13
4.3.2.1 ENQUIRE .13
4.3.2.2 HANDOVER .13
4.3.2.3 HO-ACCEPT .13
4.3.2.4 HO-REJECT .13
4.4 Functional entity behaviour .13
4.4.1 Behaviour of FE1.14
4.4.2 Behaviour of FE2.15
4.4.3 Behaviour of FE3.16
4.5 Functional Entity Actions (FEAs) .17
4.5.1 FEAs of FE1.17
4.5.2 FEAs of FE2.17
4.5.3 FEAs of FE3.17
4.6 Allocation of FEs to physical locations.17
4.7 Interworking considerations .17
5 ANF-CTH Stage 2 description for handover - new location area selected by the network .18
5.1 Description.18
5.2 Derivation of the functional model .18
5.2.1 Functional model description.18
5.2.2 Description of FEs.18
5.2.2.1 CTM user's old service agent, FE5.18
5.2.2.2 Handover service execution entity, FE6 .18
5.2.2.3 CTM user's new service agent, FE4.18
5.2.3 Relationship with a basic service .19
5.3 Information flows.19
5.3.1 Information flow sequences .19
5.3.2 Definition of information flows .24
5.3.2.1 HO-ACCEPT .24
5.3.2.2 HO-CHECK.25
5.3.2.3 HO-REJECT .25
5.3.2.4 HO-REQUEST.25
5.4 Functional entity behaviour .25
5.4.1 Behaviour of FE4.26
5.4.2 Behaviour of FE5.27

Page 4
ETS 300 817: February 1998
5.4.3 Behaviour of FE6 . 28
5.5 FEAs. 30
5.5.1 FEAs of FE4 . 30
5.5.2 FEAs of FE5 . 30
5.5.3 FEAs of FE6 . 30
5.6 Allocation of FEs to physical locations . 31
5.7 Interworking considerations . 31
History. 32

Page 5
ETS 300 817: February 1998
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: 23 January 1998
Date of latest announcement of this ETS (doa): 31 May 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1998
Date of withdrawal of any conflicting National Standard (dow): 30 November 1998

Page 6
ETS 300 817: February 1998
Blank page
Page 7
ETS 300 817: February 1998
1 Scope
This European Telecommunications Standard (ETS) describes the Stage 2 of the Cordless Terminal
Handover Additional Network Feature (ANF-CTH) for a Private Integrated Services Network (PISN).
ANF-CTH is an additional network feature that enables a Cordless Terminal Mobility (CTM) user to
maintain a call while moving between overlapping location areas belonging to the same visitor area.
This ANF is applicable to all circuit mode basic services as defined in ETS 300 171 [3].
NOTE 1: The HandOver (HO) procedures described in this ETS are only applicable on handover
between location areas controlled by the same Private Integrated services Network
eXchange (PINX).
Additional network feature specifications are produced in three stages according to the method specified
in ENV 41005 [2]. This ETS contains the Stage 2 specifications of ANF-CTH. It identifies the Functional
Entities (FEs) involved in the service and the information flows between them.
NOTE 2: The information flow across the air-interface is outside the scope of this ETS.
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 of ETS 300 816 [6]. Stages 1 and 3 are defined in
separate standards.
This ETS contains two Stage 2 specifications reflecting different ways of selecting the new location area:
selection of the new location area by the CTM user and selection of the new location area by the network.
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] CCITT Recommendation I.210 (1988): "Principles of telecommunication
services supported by an ISDN and the means to describe them".
[2] ENV 41005 (1989): "Method for the specification of basic and supplementary
services of private telecommunication networks".
[3] ETS 300 171 (1992): "Private Telecommunication Network (PTN) -
Specification, functional model and information flows - Control aspects of circuit
mode basic services".
[4] ETS 300 415 (1996): "Private Integrated Services Network (PISN); Terms and
definitions".
[5] CCITT Recommendation Z.100 (1988): "Functional Specification and
Description Language (SDL)".
[6] ETS 300 816 (1996): "Private Integrated Services Network (PISN); Cordless
Terminal Mobility (CTM); Handover Additional Network Feature; Service
Description".
Page 8
ETS 300 817: February 1998
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following terms, defined in other documents, apply:
address: See ETS 300 415 [4].
call (basic call): See ETS 300 171 [3].
Cordless Terminal Mobility (CTM): See ETS 300 415 [4].
Fixed Part (FP): See ETS 300 415 [4].
Private Telecommunication Network (PTN): See ETS 300 415 [4].
Private Integrated services Network eXchange (PINX): See ETS 300 415 [4].
PISN number: See ETS 300 415 [4].
supplementary service: See CCITT Recommendation I.210 [1].
Visitor Data Base: See ETS 300 415 [4].
visitor area: See ETS 300 415 [4].
NOTE: For the purpose of this ETS the visitor area is confined to the coverage area of a single
PINX.
This ETS refers to the following FEs defined for basic call control ETS 300 171 [3]:
Call Control (CC): Generic functional entity of Call Control.
Call Control Agent (CCA): Generic functional entity of Call Control Agent.
This ETS refers to the following inter-FE relationships defined for basic call control ETS 300 171 [3]:
r1: The access relationship between an Originating Call Control Agent functional entity and an Originating
Call Control functional entity.
r3: The access relationship between a Destination Call Control Agent functional entity and a Destination
Call Control functional entity.
For the purposes of this ETS, the following definitions apply:
CTM user: A PISN user whose calls are processed by the additional network feature ANF-CTH.
established call: A call for which communication between the end users is possible.
visitor PINX: The PINX which has direct access to the Visitor Data Base (VDB) entry associated with a
particular CTM user.
location area: The coverage area in which a cordless terminal may receive and make calls as a result of
a single location registration.
PISN user: A user whose terminal is directly attached to a PISN and therefore can directly use the bearer
services and teleservices of the PISN.
user: An entity which uses bearer services or teleservices of a PISN.

Page 9
ETS 300 817: February 1998
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
CC Call Control functional entity
CCA Call Control Agent functional entity
ANF Additional Network Feature
ANF-CTH Cordless Terminal mobility Handover-Additional Network Feature
CTM Cordless Terminal Mobility
FE Functional Entity
FEA Functional Entity Action
FP Fixed Part
HO HandOver
PISN Private Integrated Services Network
PINX Private Integrated services Network eXchange
SDL Specification and Description Language
VDB Visitor Data Base
4 ANF-CTH Stage 2 Description - new location area selected by the Cordless
Terminal Mobility (CTM) user
This clause defines the Stage 2 of the CTM Handover Additional Network Feature (ANF-CTH) where the
new location area is selected by the CTM user.
4.1 Description
ANF-CTH enables a CTM user involved in a call to continue with the call while moving between
overlapping location areas within the same visitor area.
NOTE: During handover, there may be a brief interruption to the established connection. This
ANF should only be used in conjunction with basic services where such a temporary
interruption is permissible.
4.2 Derivation of the functional model
4.2.1 Functional model description
The functional model shall comprise the following FEs:
FE1: CTM user's service agent.
FE2: CTM handover service execution entity.
FE3: Security parameter storage entity.
The following functional relationships shall exist between these FEs:
ra between FE1 and FE2.
rc between FE2 and FE3.
Figure 1 shows the FEs and relationships for the handover of a call involving a CTM user.
Figure 1: Functional model for the handover of a call involving a CTM user

Page 10
ETS 300 817: February 1998
4.2.2 Description of FEs
4.2.2.1 CTM user's service agent, FE1
This FE sends a request to FE2 to re-route the CTM user's call from its current location area to the new
location area.
4.2.2.2 CTM handover service execution entity, FE2
On request from FE1, this FE re-routes the user's call from its current location area to the new location
area. It is also responsible for retrieving security parameters from FE3.
4.2.2.3 Security Parameter Storage entity, FE3
This FE provides on request from FE2, information on the security parameters currently in use by the
CTM user.
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.
FE2
FE1 FE3
ra
rc
CC
CCA
CCA
r1/r3
r1/r3
Figure 2: Functional entity model relationship
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 5. It can
specify further information flows, e.g. to deal with additional exceptional conditions.
ANF-CTH 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-CTH functional entity, the numbers refer to FEAs listed in
subcl
...