SIST ETS 300 692 E1:2003

Private Integrated Services Network (PISN); Cordless Terminal Mobility (CTM); Location handling services; Functional capabilities and information flows

To produce a draft ETS stage 2 description for CTM roaming. Location handling aspects

Zasebno omrežje z integriranimi storitvami (PISN) - Mobilnost brezvrvičnega terminala (CTM) - Storitve obdelave lokacij - Funkcijske zmožnosti in informacijski pretoki

General Information

• 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 692 ed.1 (1996-04) - Private Integrated Services Network (PISN); Cordless Terminal Mobility (CTM); Location handling services; Functional capabilities and information flows

Standards Content (Sample)

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

---------------------- Page: 1 ----------------------

SIST ETS 300 692 E1:2003

---------------------- Page: 2 ----------------------

SIST ETS 300 692 E1:2003
EUROPEAN ETS 300 692
TELECOMMUNICATION March 1996
STANDARD
Source: ETSI TC-BTC Reference: DE/BTC-01011
ICS: 35.120
Key words: PISN, CTM, mobility, location, supplementary service, ANF, stage 2, PTN
Private Integrated Services Network (PISN);
Cordless Terminal Mobility (CTM);
Location handling services;
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: 3 ----------------------

SIST ETS 300 692 E1:2003
Page 2
ETS 300 692: 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: 4 ----------------------

SIST ETS 300 692 E1:2003
Page 3
ETS 300 692: 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 SS-CTLR.9
4.1 Description.9
4.2 Functional model.9
4.2.1 Functional model description.9
4.2.2 Description of functional entities.10
4.2.2.1 Served user agent, FE1.10
4.2.2.2 VDB function control, FE2 .10
4.2.2.3 HDB function control, FE3 .10
4.2.2.4 Old VDB function control, FE4.10
4.2.2.5 Old served user agent, FE5.10
4.2.2.6 Identification mapping entity, FE6.10
4.2.3 Relationship with basic service .10
4.3 Information flows.10
4.3.1 Information flow sequences .10
4.3.1.1 Location Registration to a new VA using the CTM user's
identity.11
4.3.1.2 Location registration to a new VA using an alternative
identifier .11
4.3.1.3 Location registration within the same VA.12
4.3.1.4 Location deregistration .12
4.3.1.5 Location registration rejected by FE3 .12
4.3.1.6 Location registration using the PISN number rejected by
FE2 .13
4.3.1.7 Location registration rejected by FE6 .13
4.3.1.8 Location registration using an alternative identifier
rejected by FE2.13
4.3.1.9 Location deregistration rejected by FE2 .14
4.3.1.10 Location deregistration rejected by FE3 .14
4.3.2 Definition of individual information flows .14
4.3.2.1 L-REG.14
4.3.2.2 L-DREG .15
4.3.2.3 LOC-DREG.15
4.3.2.4 LOC-DEL .15
4.3.2.5 LOC-UPD.16
4.3.2.6 PISN-ENQ .16
4.4 SDL diagrams for functional entities.16
4.4.1 Behaviour of FE1.17
4.4.2 Behaviour of FE2.18
4.4.3 Behaviour of FE3.20
4.4.4 Behaviour of FE4.21
4.4.5 Behaviour of FE5.22
4.4.6 Behaviour of FE6.22
4.5 Functional Entity Actions (FEAs) .23
4.5.1 FEAs of FE1.23
4.5.2 FEAs of FE2.23
4.5.3 FEAs of FE3.24
4.5.4 FEAs of FE4.24

---------------------- Page: 5 ----------------------

SIST ETS 300 692 E1:2003
Page 4
ETS 300 692: March 1996
4.5.5 FEAs of FE5 . 24
4.5.6 FEAs of FE6 . 24
4.6 Allocation of functional entities to physical locations. 24
5 ANF-CTSP. 25
5.1 Description . 25
5.2 Functional model. 25
5.2.1 Functional model description. 25
5.2.2 Description of functional entities. 25
5.2.2.1 VDB function control entity, FE1 . 25
5.2.2.2 HDB function control entity, FE2. 25
5.2.3 Relationship with basic service. 25
5.3 Information flow. 26
5.3.1 Information flow diagrams . 26
5.3.1.1 Service profile transfer . 26
5.3.1.2 Service profile update . 26
5.3.1.3 Service profile modification . 26
5.3.2 Definition of individual information flows. 26
5.3.2.1 SP-MOD. 26
5.3.2.2 SP-UPD. 27
5.3.2.3 SP-XCHG. 27
5.4 SDL diagrams for functional entities . 27
5.4.1 Behaviour of FE1 . 28
5.4.2 Behaviour of FE2 . 29
5.5 Functional Entity Actions (FEAs). 29
5.5.1 FEAs of FE1 . 29
5.5.2 FEAs of FE2 . 30
5.6 Allocation of functional entities to physical locations. 30
Annex A (informative): User identifiers. 31
A.1 CTM user's identity . 31
A.2 Alternative identifiers . 31
History. 32

---------------------- Page: 6 ----------------------

SIST ETS 300 692 E1:2003
Page 5
ETS 300 692: 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: 7 ----------------------

SIST ETS 300 692 E1:2003
Page 6
ETS 300 692: March 1996
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 692 E1:2003
Page 7
ETS 300 692: March 1996
1 Scope
This European Telecommunication Standard (ETS) describes the stage two of the location handling
services for Private Integrated Services Networks (PISNs) which provide Cordless Terminal Mobility
(CTM) user mobility capability.
The Cordless Terminal Location Registration Supplementary Service (SS-CTLR) enables a CTM user to
register at, or deregister from, the current location within the PISN. The ability to register at different
locations in the PISN at different times enables the CTM user to maintain the provided services (including
the ability to make and receive calls) at different access points. Deregistration is used to inform the PISN
that the CTM user is temporarily unable to make use of the provided services (including the receipt of
incoming calls).
The Transfer of Service Profile Additional Network Feature (ANF-CTSP) enables different parts of the
PISN to transfer or access service profiles, thereby allowing CTM users to maintain their service profiles
when changing location within the PISN.
Supplementary service specifications are produced in three stages according to the method specified in
ETS 300 387 [3]. Stage 2 identifies the functional entities involved in the feature and the information flows
between them.
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.
This ETS applies to CTM only within a single PISN. The specification of information flows between the
PISN and cordless terminals is beyond the scope of this ETS.
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 415 (1995): "Private Telecommunication Network (PTN); Terms and
definitions".
[2] 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)".
[3] ETS 300 387 (1994): "Private Telecommunication Network (PTN); Method for
the specification of basic and supplementary services".
[4] ITU-T Recommendation I.210 (1993): "Principles of telecommunication services
supported by an ISDN and the means to describe them".
[5] ITU-T Recommendation Z.100 (1993): "Specification and description language
(SDL)".
[6] ISO/IEC 11571 (1994): "Information technology - Telecommunications and
information exchange between systems - Numbering and Sub-addressing in
Private Integrated Services Network".

---------------------- Page: 9 ----------------------

SIST ETS 300 692 E1:2003
Page 8
ETS 300 692: March 1996
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 [1].
authentication: See ETS 300 415 [1].
Cordless Terminal Mobility (CTM): The ability of a cordless terminal to be in continuous motion whilst
accessing and using the telecommunication 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 information: The information for a CTM user managed by a VDB.
CTM user: The user of Supplementary Service "Cordless Terminal Location Registration" (SS-CTLR).
directory PINX: A PINX which provides a mapping function to a CTM user's PISN number from another
type of identity indicating the same CTM user.
fixed part: A physical grouping of some or all of the fixed component parts of mobile radio system. These
would include one or more radio equipments attached to an antenna system. It could also include
common control functions and interfaces to the PINX.
Home Data Base (HDB): See ETS 300 415 [1].
home PINX: The PINX which has direct access to the HDB entry for a particular CTM user.
Location Area (LA): The coverage area in which a cordless terminal may receive and make calls as a
result of a single location registration.
Network Assigned Identity (NAI): A temporary identity assigned by the PISN to a CTM user. This identity
comprises:
- a PISN number sufficient to identify the PINX assigning the NAI; and
- a local identity valid while the user is registered.
Private Integrated ServicesNetwork (PISN): See ISO/IEC 11579-1 [2].
Private Integrated Services Network Exchange (PINX): See ISO/IEC 11579-1 [2].
PISN number: See ISO/IEC 11571 [6].
PISN user: The user of the network layer services provided by a PISN.
service profile: The specific collection of PISN services and service options which a PISN user can
utilize.
supplementary service: See ITU-T Recommendation I.210 [4].
Visitor Area (VA): See ETS 300 415 [1].
Visitor Data Base (VDB): See ETS 300 415 [1].
visitor PINX: The PINX which is serving a CTM user in a visitor area.

---------------------- Page: 10 ----------------------

SIST ETS 300 692 E1:2003
Page 9
ETS 300 692: March 1996
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ANF-xxx "xxx" Additional Network Feature
CTLR Cordless Terminal Location Registration
CTM Cordless Terminal Mobility
CTSP Transfer of Service Profile
FE Functional Entity
FEA Functional Entity Action
FP Fixed Part
HDB Home Data Base
LA Location Area
NAI Network Assigned Identity
PINX Private Integrated Services Network Exchange
PISN Private Integrated Services Network
SDL Specification and Description Language
SP Service Profile
SS-xxx "xxx" Supplementary Service
VA Visitor Area
VDB Visitor Data Base
4 SS-CTLR
4.1 Description
SS-CTLR makes the location of a CTM user known to the PISN. By updating location information in the
PISN, incoming calls can be routed to a CTM user, and the CTM user can access the PISN services from
the current location area. SS-CTLR also enables a CTM user to inform the PISN that the current location
area is no longer to be used to make and receive calls.
The network may allow the CTM user to perform location registration using a permanent identifier.
Alternatively, for security reasons, a procedure supporting the use of temporary identifiers may be used.
SS-CTLR may cause the invocation of ANF-CTSP in order to provide a consistent service to a CTM user
independent of the CTM user's location area.
SS-CTLR may use an authentication procedure in order to validate the identity provided by the CTM user
to the PISN before completing the location registration.
4.2 Functional model
4.2.1 Functional model description
The functional model for SS-CTLR shall be as shown in figure 1.
rc
rc
FE5 FE4 FE3
rb
rc
ra rd
FE1 FE2 FE6
Figure 1: Functional model for SS-CTLR

---------------------- Page: 11 ----------------------

SIST ETS 300 692 E1:2003
Page 10
ETS 300 692: March 1996
The functional model for SS-CTLR shall comprise the following Functional Entities (FEs):
FE1: Served user agent;
FE2: VDB function control;
FE3: HDB function control;
FE4: Old VDB function control;
FE5: Old served user agent;
FE6: Identification mapping entity.
The following functional relationships shall exist between these FEs:
ra: between FE1 and FE2;
rb: between FE2 and FE3;
rc: between FE3 and FE4, between FE4 and FE5 and between FE2 and FE5;
rd: between FE2 and FE6.
4.2.2 Description of functional entities
4.2.2.1 Served user agent, FE1
This FE detects the request for location registration and deregistration procedures.
NOTE: The possible information transfer on the radio interface causing FE1 to invoke
SS-CTLR is out of scope for this ETS.
4.2.2.2 VDB function control, FE2
This FE is responsible for the maintenance of CTM information while the CTM user is registered at the
visited location by inserting an entry in the VDB when the CTM user first registers in the visitor area,
updating the entry when the CTM user registers to a location area within the same visitor area, and
deleting the entry when the CTM user deregisters.
4.2.2.3 HDB function control, FE3
This FE registers the new visitor area of the CTM user and requests the deletion of location information at
the old visited location.
4.2.2.4 Old VDB function control, FE4
This FE is the VDB function control at the previous visited location and is responsible for the deletion of
location information that is no longer required.
4.2.2.5 Old served user agent, FE5
This FE is the served user agent at the previously visited location and is responsible for the release of
resources that are no longer required.
4.2.2.6 Identification mapping entity, FE6
This FE converts an identity supplied by the CTM user for location registration to the CTM user's PISN
number.
4.2.3 Relationship with basic service
All information flows are independent of basic call flows.
4.3 Information flows
4.3.1 Information flow sequences
A stage 3 standard shall be capable of providing the information flows shown in this subclause. It can
specify further information flows, e.g. to deal with additional exceptional conditions.

---------------------- Page: 12 ----------------------

SIST ETS 300 692 E1:2003
Page 11
ETS 300 692: March 1996
4.3.1.1 Location Registration to a new VA using the CTM user's identity
Figure 2 shows the information flow for a location registration to a new visitor area when the CTM user's
identity is used.
rd
rc
FE1 FE2 FE3 FE4 FE5 FE6
rc rc
ra rb
L-REG
101
req/ind
201 LOC-UPD
req/ind
301
LOC-UPD
LOC-DEL
202 LOC-DEL
L-REG resp/conf 401
req/ind
req/ind
resp/conf
102
501
LOC-DEL
LOC-DEL
402 resp/conf
resp/conf
303
NOTE: Authentication procedures can be activated as part of FEA-201 before allowing the registration
to take effect.
Figure 2: Location registration to a new VA using the CTM user's identity
4.3.1.2 Location registration to a new VA using an alternative identifier
Figure 3 shows the information flow for a location registration to a new visitor area when an alternative
identifier is used.
rd
rc
FE1 FE2 FE3 FE4 FE5 FE6
rc rc
ra rb
L-REG
101
PISN-ENQ
201
req/ind
req/ind
601
PISN-ENQ
resp/conf
203
LOC-UPD
req/ind
301
LOC-DEL
LOC-UPD
L-REG
LOC-DEL
202
resp/conf 401
req/ind
req/ind
102 resp/conf
501
LOC-DEL
LOC-DEL
402
resp/conf
303
resp/conf
NOTE: Authentication procedures can be activated as part of FEA-203 before allowing the registration
to take effect.
Figure 3: Location registration to a new VA using an alternative identifier

---------------------- Page: 13 ----------------------

SIST ETS 300 692 E1:2003
Page 12
ETS 300 692: March 1996
4.3.1.3 Location registration within the same VA
Figure 4 shows the information flow for a location registration within the current visitor area.
rd
rc
FE1 FE2 FE3 FE4 FE5 FE6
rc
rc
ra rb
101 L-REG
req/ind
201
L-REG LOC-DEL
resp/conf
req/ind
102
501
LOC-DEL
resp/conf
209
Figure 4: Location registration within the current VA
4.3.1.4 Location deregistration
Figure 5 shows the information flow for a location deregistration.
rd
rc
FE1 FE2 FE3 FE4 FE5 FE6
rc
rc
ra rb
103 L-DREG
req/ind 204 LOC-DREG
req/ind
302
LOC-DREG
L-DREG
207
resp/conf
resp/conf
104
Figure 5: Location deregistration
4.3.1.5 Location registration rejected by FE3
Figure 6 shows the information flow for a failure in location registration using the CTM user's identity when
the failure was caused by "User identity not known" or "CTM user not permitted to register in the current
LA" detected by FE3.
rd
rc
FE1 FE2 FE3 FE4 FE5 FE6
rc rc
ra rb
L-REG
101
201 LOC-UPD
req/ind
req/ind
301
LOC-UPD
L-REG
205
resp/conf
(rejected)
105 resp/conf
(rejected)
Figure 6: Location registration rejected by FE3

---------------------- Page: 14 ----------------------

SIST ETS 300 692 E1:2003
Page 13
ETS 300 692: March 1996
4.3.1.6 Location registration using the PISN number rejected by FE2
Figure 7 shows the information flow for a failure in location registration using the CTM user's identity. The
information flow assumes that the failure was caused by "Location registration temporarily not possible" or
"CTM user failed authentication" detected by FE2.
rd
rc
FE1 FE2 FE3 FE4 FE5 FE6
rc
rc
ra rb
L-REG
101
req/ind
201
L-REG
105 resp/conf
(rejected)
Figure 7: Location registration using the CTM user's identity rejected by FE2
4.3.1.7 Location registration rejected by FE6
Figure 8 shows the information flow for a failure in location registration using an alternative identifier. The
information flow assumes that the failure was caused by "User identity not known" detected by FE6.
rd
rc
FE1 FE2 FE3 FE4 FE5 FE6
rc
rc
ra rb
101
L-REG
201 PISN-ENQ
req/ind
req/ind
601
PISN-ENQ
206
L-REG resp/conf
(rejected)
resp/conf
105
(rejected)
Figure 8: Location registration rejected by FE6
4.3.1.8 Location registration using an alternative identifier rejected by FE2
Figure 9 shows the information flow for a failure in location registration when using an alternative identifier.
The information flow assumes that the failure was caused by "CTM user failed authentication" detected by
FE2.
rd
rc
FE1 FE2 FE3 FE4 FE5 FE6
rc rc
ra rb
101 L-REG
req/ind 201 PISN-ENQ
req/ind
601
PISN-ENQ
L-REG
203
resp/conf
resp/conf
105
(rejected)
Figure 9: Location registration using an alternative identifier rejected by FE2

---------------------- Page: 15 ----------------------

SIST ETS 300 692 E1:2003
Page 14
ETS 300 692: March 1996
4.3.1.9 Location deregistration rejected by FE2
Figure 10 shows the information flow for a failure in location deregistration. The information flow assumes
that the failure occurred because the CTM user was not registered.
rd
rc
FE1 FE2 FE3 FE4 FE5 FE6
rc rc
ra rb
L-DREG
103
req/ind
204
L-DREG
106 resp/conf
(rejected)
Figure 10: Location deregistation rejected by FE2
4.3.1.10 Location deregistration rejected by FE3
Figure 11 shows the information flow for a failure in location deregistration. The information flow assumes
that the request was rejected by FE3.
rd
rc
FE1 FE2 FE3 FE4 FE5 FE6
rc
rc
ra rb
L-DREG
103
204 LOC-DREG
req/ind
req/ind
302
LOC-DREG
L-DREG 208
resp/conf
(rejected)
106 resp/conf
(rejected)
Figure 11: Location deregistation rejected by FE3
4.3.2 Definition of individual information flows
4.3.2.1 L-REG
This confirmed information flow is used to cause FE2 to perform a location registration of the CTM user. It
shall be sent across relationship ra from FE1 to FE2.

---------------------- Page: 16 ----------------------

SIST ETS 300 692 E1:2003
Page 15
ETS 300 692: March 1996
Table 1: Contents of L-REG
Service elements Allowed values Request Confirm
CTM user's identity M
Basic Service Indicator M
CTM user's PISN number O (note 1)
CTM user's new NAI O (note 2)
Result Accepted or rejected M
Cause of rejection - User identity not known O (note 3)
- CTM user not permitted to register in
the current LA
- CTM user failed authentication
- Location registration temporarily not
possible
NOTE 1: Mandatory if the request is accepted.
NOTE 2: The new NAI shall be provided if NAI assignment is implemented.
NOTE 3: This service element shall only be included in cases of rejection.
4.3.2.2 L-DREG
This confirmed information flow is used to perform a deregistration of the CTM user from the current
location. It shall be sent across relationship ra from FE1 to FE2.
Table 2: Contents of L-DREG
Service elements Allowed values Request Confirm
CTM user's identity M
Basic Service Indicator M
Result Accepted or Rejected M
4.3.2.3 LOC-DREG
This confirmed information flow is used to perform a deregistration of the CTM user from the current
location. It shall be sent across relationship rb from FE2 to FE3.
Table 3: Contents of LOC-DREG
Service elements Allowed values Request Confirm
CTM user's PISN number M
Basic Service Indicator M
Result Accepted or Rejected M
4.3.2.4 LOC-DEL
This confirmed information flow is used to request the release of resources allocated to a CTM user. It
shall be sent across relationship rc from FE3 to FE4, or from FE2 or FE4 to FE5.
Table 4: Contents of LOC-DEL
Service elements Allowed values Request Confirm
CTM user's PISN number M
Basic Service Indicator M
Result Accepted or Rejected M

---------------------- Page: 17 ----------------------

SIST ETS 300 692 E1:2003
Page 16
ETS 300 692: March 1996
4.3.2.5 LOC-UPD
This confirmed information flow is used to request an update of the location information in FE3 for a CTM
user. It shall be sent across relationship rb from FE2 to FE3.
Table 5: Contents of LOC-UPD
Service elements Allowed values Request Confirm
CTM user's PISN number
M
Basic Service Indicator M
Visitor PINX PISN number M
Result Accepted or Rejected M
Cause of rejection - User identity not known O (note)
- CTM user not permitted to register in
the current LA
NOTE: This service element shall only be included in cases of rejection.
4.3.2.6 PISN-ENQ
This confirmed information flow is a request for the PISN number of a CTM user identified by an NAI or
similar. It shall be sent across relationship rd from FE2 to FE6.
Table 6: Con
...