SIST ETS 300 175-6:1999

SLOVENSKI STANDARD
01-julij-1999
'LJLWDOQHL]EROMãDQHEUH]YUYLþQHWHOHNRPXQLNDFLMH'(&76NXSQLYPHVQLN&,
GHO,GHQWLWHWHLQQDVODYOMDQMH
Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 6:
Identities and addressing
Ta slovenski standard je istoveten z: ETS 300 175-6 Edition 2
ICS:
33.070.30 'LJLWDOQHL]EROMãDQH Digital Enhanced Cordless
EUH]YUYLþQHWHOHNRPXQLNDFLMH Telecommunications (DECT)
'(&7
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 175-6
TELECOMMUNICATION September 1996
STANDARD Second Edition
Source: ETSI TC-RES Reference: RE/RES-03027-6
ICS: 33.060, 33.060.50
Key words: DECT, radio
Radio Equipment and Systems (RES);
Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI);
Part 6: Identities and addressing
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: secretariat@etsi.fr
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
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 175-6: September 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 175-6: September 1996
Contents
Foreword .5
1 Scope.7
2 Normative references.8
3 Definitions and abbreviations .9
3.1 Definitions.9
3.2 Abbreviations .12
4 General description of FP and PP identities.13
4.1 Combinations of ARIs, PARKs and IPUIs .14
5 FP identities.14
5.1 ARI class A.17
5.2 ARI class B.17
5.3 ARI class C.18
5.4 ARI class D.19
5.5 ARl class E.20
5.6 SARI list structure .20
5.6.1 ARI list length.21
5.6.2 TARIs.21
5.6.3 Black.21
5.6.4 ARI.21
5.6.5 Black-ARI .21
5.6.6 TARI messages.22
5.6.6.1 Request message from the PP .22
5.6.6.2 Response message from the FP.22
6 PP identities.23
6.1 PARK.24
6.1.1 PARK A.24
6.1.2 PARK B.24
6.1.3 PARK C.25
6.1.4 PARK D.25
6.1.5 PARK E.25
6.2 IPUI.25
6.2.1 Portable user identity type N (residential/default).25
6.2.2 Portable user identity type S (PSTN/ISDN) .26
6.2.3 Portable user identity type O (private).26
6.2.4 Portable user identity type T (private extended) .26
6.2.5 Portable user identity type P (public/public access service).27
6.2.6 Portable user identity type Q (public/general).27
6.2.7 Portable user identity type U (public/general).27
6.2.8 Portable user identity type R (public/GSM).27
6.3 Individual and group TPUIs.28
6.3.1 General .28
6.3.2 Individual TPUI .29
6.3.3 Group TPUIs.30
7 Coding of identities .31
7.1 RFPI E-bit.31
7.2 Access rights codes .31
7.3 Portable user identity types.31

Page 4
ETS 300 175-6: September 1996
7.4 EMC, EIC and POC.31
8 Rules for the usage of FP and PP identities .32
8.1 General principles.32
8.2 PARI, SARI and TARI usage.32
9 Connection related identities.34
9.1 MAC identities (see ETS 300 175-3 [3], subclause 11.7) .34
9.1.1 FMID.34
9.1.2 PMID.34
9.2 DLC identities (see ETS 300 175-4 [4], subclause 10.3.1).35
9.3 NWL identities (see ETS 300 175-5 [5]) .35
10 Equipment related identities.35
11 Subscription and registration procedures .35
Annex A (informative): Examples of usage of FP and PP identities.36
A.1 Residential ID usage.36
A.2 Public ID usage .36
A.2.1 Primary.36
A.2.2 Secondary .37
A.2.3 Tertiary.37
A.3 Private ID usage.37
A.3.1 Primary.37
A.3.2 Secondary .38
A.4 Mixed private and public ID usage.38
A.4.1 Public in private environments.38
A.4.2 Private in public environments.38
Annex B (normative): Identities and addressing timers .39
Annex C (normative): Representation of IPEI as printed text.40
Annex D (informative): Bibliography.41
History.42

Page 5
ETS 300 175-6: September 1996
Foreword
This second edition European Telecommunication Standard (ETS) has been produced by the Radio
Equipment and Systems (RES) Technical Committee of the European Telecommunications Standards
Institute (ETSI).
Annexes B and C to this ETS are normative. Annexes A and D to this ETS is informative.
Further details of the DECT system may be found in the ETR 015, ETR 043 and ETR 056.
This ETS forms part 6 of a series of 9 laying down the arrangements for the Digital Enhanced Cordless
Telecommunications (DECT) Common Interface (CI).
Part 1: "Overview".
Part 2 "Physical layer (PHL)".
Part 3 "Medium Access Control (MAC) layer".
Part 4 "Data Link Control (DLC) layer".
Part 5: "Network (NWK) layer".
Part 6: "Identities and addressing".
Part 7: "Security features".
Part 8: "Speech coding and transmission".
Part 9: "Public Access Profile (PAP)".
Transposition dates
Date of adoption of this ETS: 6 September 1996
Date of latest announcement of this ETS (doa): 31 December 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 June 1997
Date of withdrawal of any conflicting National Standard (dow): 30 June 1997

Page 6
ETS 300 175-6: September 1996
Blank page
Page 7
ETS 300 175-6: September 1996
1 Scope
This second edition European Telecommunication Standard (ETS) specifies the identities and addressing
structure of the Digital Enhanced Cordless Telecommunications (DECT) Common Interface. It is Part 6 of
a series of 9 parts.
There are four categories of identities to be used for identification and addressing in a general DECT
environment. These four categories are:
- Fixed Part (FP) identities;
- Portable Part (PP) identities;
- connection-related identities;
- equipment-related identities.
Fixed part identities and portable part identities are used for:
- access information from fixed parts to portable parts;
- access requests from portable parts;
- identification of portable parts;
- identification of fixed parts and radio fixed parts;
- paging;
- billing.
These identities support:
- different environments, such as residential, public or private;
- supply to manufacturers, installers, and operators of globally unique identity elements with a
minimum of central administration;
- multiple access rights for the same portable;
- large freedom for manufacturers, installers, and operators to structure the fixed part identities, e.g.
to facilitate provision of access rights to groups of DECT systems;
- roaming agreements between DECT networks run by the same or different owners/operators;
- indication of handover domains;
- indication of location areas, i.e. paging area;
- indication of subscription areas of a public service.
This ETS also provides for length indicators and other messages that can override the default location
and/or paging area and domain indications given by the structure of the identities.
Connection related identities are used to identify the protocol instances associated with a call and are used
for peer-to-peer communication.
Equipment related identities are used to identify a stolen PP and to derive a default identity coding for PP
emergency call set-up.
Coding of identity information elements for higher layer messages is found in ETS 300 175-5 [5],
subclause 7.7.
User authentication and ciphering need additional key information and is outside the scope of this ETS, but
is covered in other Parts of ETS 300 175 Parts 1 to 8 [1] to [8], e.g. Part 7.

Page 8
ETS 300 175-6: September 1996
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 to this ETS
only when incorporated in it by amendment or revision. For undated references the latest edition of the
publication referred to applies.
[1] ETS 300 175-1 (1996): "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI); Part 1:
Overview".
[2] ETS 300 175-2 (1996): "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI); Part 2: Physical
Layer (PHL)".
[3] ETS 300 175-3 (1996): "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI); Part 3: Medium
Access Control (MAC) layer".
[4] ETS 300 175-4 (1996): "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI); Part 4: Data
Link Control (DLC) layer".
[5] ETS 300 175-5 (1996): "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI); Part 5: Network
(NWK) layer".
[6] ETS 300 175-7 (1996): "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI); Part 7: Security
features".
[7] ETS 300 175-8 (1996): "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI); Part 8: Speech
coding and transmission".
[8] ETS 300 175-9 (1996): "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI); Part 9: Public
Access Profile (PAP)".
[9] CCITT Recommendation E.163 (1988): "Numbering Plan for the ISDN Era".
[10] CCITT Recommendation E.164 (1988): "Numbering Plan for the International
Telephone Service".
[11] ETS 300 523: "Numbering, addressing, and identification" (GSM 03.03).

Page 9
ETS 300 175-6: September 1996
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
Access Rights Class (ARC): This shows the type of access to a DECT network, such as public,
residential or private.
Access Rights Details (ARD): This is a unique number within one ARC.
Access Rights Identity (ARI): This is, to a service provider, a globally unique identity that shows the
access rights related to that service provider. The ARI consists of an ARC and an ARD. There are three
categories of ARIs:
- PARI = Primary ARI;
- SARI = Secondary ARI;
- TARI = Tertiary ARI.
attach: See ETS 300 175-1 [1].
authentication (of a subscriber): See ETS 300 175-1 [1].
bearer: See ETS 300 175-1 [1].
bearer handover: See ETS 300 175-1 [1].
cell: See ETS 300 175-1 [1].
Central Control Fixed Part (CCFP): See ETS 300 175-1 [1].
cluster: See ETS 300 175-1 [1].
connection: See ETS 300 175-1 [1].
connection handover: See ETS 300 175-1 [1].
Cordless Radio Fixed Part (CRFP): See ETS 300 175-1 [1].
coverage area: See ETS 300 175-1 [1].
DECT Network (DNW): See ETS 300 175-1 [1].
Data Link Control (DLC): Layer 2b of the DECT protocol stack.
external handover: See ETS 300 175-1 [1].
Fixed Part (DECT Fixed Part) (FP): See ETS 300 175-1 [1].
Fixed Radio Termination (FT): See ETS 300 175-1 [1].
frame: See ETS 300 175-1 [1].
geographically unique: See ETS 300 175-1 [1].
Global Network (GNW): See ETS 300 175-1 [1].
globally unique identity: See ETS 300 175-1 [1].

Page 10
ETS 300 175-6: September 1996
handover: See ETS 300 175-1 [1].
intercell handover: See ETS 300 175-1 [1].
internal handover: See ETS 300 175-1 [1].
International Portable User Identity (IPUI): This is an identity that uniquely defines one user within the
domain defined by his access rights related to this IPUI. The IPUI consists of a Portable User Type (PUT)
and a Portable User Number (PUN).
NOTE 1: The IPUI may be locally unique or globally unique depending on type of PUT.
interoperability: See ETS 300 175-1 [1].
interoperator roaming: See ETS 300 175-1 [1].
intracell handover: See ETS 300 175-1 [1].
intraoperator roaming: See ETS 300 175-1 [1].
Local Network (LNW): See ETS 300 175-1 [1].
locally unique identity: See ETS 300 175-1 [1].
location area: See ETS 300 175-1 [1].
location registration: See ETS 300 175-1 [1].
Medium Access Control (MAC): Layer 2a of the DECT protocol stack.
multiframe: See ETS 300 175-1 [1].
network (telecommunication network): See ETS 300 175-1 [1].
operator (DECT operator): See ETS 300 175-1 [1].
paging: See ETS 300 175-1 [1].
paging area: See ETS 300 175-1 [1].
PARK Length Indicator (PLI): Associates a group of FP ARIs to the PARK, by indicating how many of
the first ARC + ARD bits are relevant. The rest have "don't care" status.
NOTE 2: The PLI is programmed into a PP as part of the subscription process.
Physical (PHL): Layer 1 of the DECT protocol stack.
Plain Old Telephone (Service) (POT(S)): The basic analogue telephony teleservice.
Primary Access Rights Identity (PARI): This is the most frequently transmitted ARI. Every DECT RFP
must transmit a PARI.
Portable Access Rights Key (PARK): This states the access rights for a PP.
Portable Handset (PHS): See ETS 300 175-1 [1].
Portable Part (DECT Portable Part) (PP): See ETS 300 175-1 [1].
Portable radio Termination (PT): See ETS 300 175-1 [1].

Page 11
ETS 300 175-6: September 1996
Portable User Number (PUN): This is a globally or locally unique number within one PUT.
Portable User Type (PUT): This shows the numbering plan structure of a PUN.
private: See ETS 300 175-1 [1].
public: See ETS 300 175-1 [1].
Public Access Profile (PAP): See ETS 300 175-1 [1].
public access service: See ETS 300 175-1 [1].
radio end point: A physical grouping that contains one radio transceiver (transmitter/receiver), fixed or
portable.
Radio Fixed Part (RFP): See ETS 300 175-1 [1].
Radio Fixed Part Identity (RFPI): Every RFP frequently transmits this identity, that is geographically
unique. The RFPI shows:
- PARI;
- the RFPs local identity within that FP;
- domains for handover and location areas.
registration: An ambiguous term, that should always be qualified. See either location registration or
subscription registration.
Repeater Part (REP): See ETS 300 175-1 [1].
roaming: See ETS 300 175-1 [1].
roaming service: See ETS 300 175-1 [1].
Secondary Access Rights Identity (SARI): This is less frequently broadcast than the PARI.
service provider (telecommunications service provider): See ETS 300 175-1 [1].
Single Radio Fixed Part (SRFP): See ETS 300 175-1 [1].
subscriber (customer): See ETS 300 175-1 [1].
subscription registration: See ETS 300 175-1 [1].
Tertiary Access Rights Identity (TARI): This is not broadcast at all and is available as a Yes/No answer
upon a request including the wanted ARI.
TDMA frame: A time-division multiplex of 10 ms duration, containing 24 successive full slots. A TDMA
frame starts with the first bit period of full slot 0 and ends with the last bit period of full slot 23.
TPUI domain: See ETS 300 175-1 [1].
user (of a telecommunication network): See ETS 300 175-1 [1].
Wireless Relay Station (WRS): See ETS 300 175-1 [1].

Page 12
ETS 300 175-6: September 1996
3.2 Abbreviations
For the purposes of this ETS the following abbreviations apply.
ACK Acknowledgement
ARC Access Rights Class
ARD Access Rights Details
ARI Access Rights Identity
BCD Binary Coded Decimal
CCFP Central Control Fixed Part. See definitions
CBI Collective Broadcast Identifier
CI Common Interface
CRFP Cordless Radio Fixed Part
DECT Digital Enhanced Cordless Telecommunications
DLC Data Link Control
DNW DECT Network
FMID Fixed Part MAC IDentity (MAC layer)
FP Fixed Part. See definitions
FT Fixed radio Termination
GNW Global Network
IPEI International Portable Equipment Identity
IPUI International Portable User Identity
ISDN Integrated Services Digital Network
LAL Location Area Level
LNW Local Network
MAC Medium Access Control.
NWK Network. Layer 3 of the DECT protocol stack
PARI Primary Access Rights Identity
PARK Portable Access Rights Key
PARK{y} PARK with value y for its park length indicator
PBX (PABX) Private (Automatic) Branch Exchange
PHL Physical
PHS Portable Handset
PLI Park Length Indicator
PMID Portable Part MAC Identity (MAC layer)
POT(S) Plain Old Telephone (Service)
PP Portable Part
PSPDN Packet Switched Public Data Network
PSTN Public Switched Telephone Network
PT Portable radio Termination
PTN Private Telecommunication Network
PUN Portable User Number
PUT Portable User Type
REP Repeater Part
RFP Radio Fixed Part
RFPI Radio Fixed Part Identity
RPN Radio fixed Part Number
SARI Secondary Access Rights Identity
TARI Tertiary Access Rights Identity
TDMA Time Division Multiple Access
TPUI Temporary Portable User Identity

Page 13
ETS 300 175-6: September 1996
4 General description of FP and PP identities
Every radio FP broadcasts for its purpose a unique identity which contains a globally unique (to a service
provider) Access Rights Identity (ARI). Every PP has both a Portable Access Rights Key (PARK) and an
International Portable User Identity (IPUI). These operate as a pair. A PP is allowed to access any radio
FP which broadcasts an ARI that can be identified by any of the portable access rights keys of that PP.
The IPUI is used to identify the portable in the domain defined by its related ARI. The IPUI can either be
locally unique or globally unique.
The following figure illustrates the identity structure.
�‚¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶„‚¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶„���������‚¶¶¶¶¶¶¶¶¶¶„‚¶¶¶¶¶¶¶¶¶¶„
�•�$FFHVV�5LJKWV�&ODVV�••�$FFHVV�5LJKWV�’HWDLOV•���������•�3RUWDEOH�••�3RUWDEOH�•
�•��������$5&����������••���������$5’����������•���������•���8VHU���••���8VHU���•
�”¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶»”¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶»���������•���7\SH���••��1XPEHU��•
�����������”¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶»��������������������•���387����••���381����•
��������������‚¶¶¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶„��”¶¶¶¶¶�¶¶¶¶»”¶¶¶¶¶�¶¶¶¶»
�‚¶¶¶¶¶¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶„‚¶¶¶¶¶¶¶¶„���������•��������”¶¶¶¶¶�¶¶¶¶¶»
�•�����$FFHVV�5LJKWV�,GHQWLW\�����••�5DGLR��•���������•��������������•
�•��������������$5,���������������••�)L[HG��•���������•��������������•
�…¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶‰•��3DUW��•���������•��������������•
�•�3ULPDU\�•�6HFRQGDU\�•�7HUWLDU\�••�1XPEHU�•���������•��������������•
�•���3$5,��•����6$5,���•���7$5,���••��531���•���������•��������������•
�”¶¶¶¶¶�¶¶¶¿¶¶¶¶¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶¶¶¶»”¶¶¶¶�¶¶¶»��‚¶¶¶¶¶¶¿¶¶¶¶¶„‚¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶„
�������”¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶»������•��3RUWDEOH��••�,QWHUQDWLRQDO�•
�‚¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶¶¶¶¶¶„�����������•���$FFHVV���••���3RUWDEOH����•
�•����5DGLR�)L[HG�3DUW�,GHQWLW\����•�����������•�5LJKWV�.H\�••�8VHU�,GHQWLW\�•
�•�������������53),����������������•�����������•����3$5.����••�����,38,������•
�”¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶»�����������”¶¶¶¶¶¶¶¶¶¶¶¶»”¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶»
���¶¶¶¶¶¶¶�)3�,GHQWLWLHV�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶!�¶�¶�¶�¶�33�,GHQWLWLHV�¶�¶�¶�¶�¶�¶!
Figure 1: General identity structure
The common base for the DECT identity structure is the Access Rights Class (ARC) and Access Rights
Details (ARD). These must be known by both the FP and the PPs. In the FP the ARC and ARD are called
Access Rights Identity (ARI), and in the PP they are called Portable Access Rights Key (PARK). The
distinction between PARK and ARI is that each PARK can have a group of ARDs allocated, PARK{y}. "y"
is the value of the PARK length indicator given in the PP subscription process.
�����������������‚¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶„
�����������������•�$5&�•�����������$5’����������������������������•
�����������������…¶¶¶¶¶¿¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶‰
�����������������•������������\�ELWV�����������•��GRQ�W�FDUH��ELWV•
�����������������•�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶!•�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶!
Figure 2: Structure of PARK{y}
If the ARI is a primary ARI, i.e. PARI, it will form, together with a RFP number, the broadcast identity
RFPI. ARIs can also be less frequently broadcast as Secondary Access Rights Identities (SARIs) and may
also be available as Tertiary Access Rights Identities (TARIs), which are not broadcast, but are accessible
upon request.
The PUT and PUN form the PP user's identity, IPUI. This identity can either be globally unique or locally
unique. IPUIs can be replaced by temporary and shorter identities, TPUIs for paging.
A PP is identified by its pairs of PARK{y} and IPUI. A PP is only allowed to access a FP if one of its
PARKs includes one of the ARIs of the FP, i.e. the PARI, a SARI or a TARI.

Page 14
ETS 300 175-6: September 1996
4.1 Combinations of ARIs, PARKs and IPUIs
DECT provides a flexible radio access technology for a large variety of private and public networks or
systems. This leads to different requirements on e.g. sub-system grouping, distribution and installation of
equipment, identity allocations and subscription.
Therefore five access rights classes A - E and a number of IPUIs have been defined to meet the need for
a differentiation in the identity structures.
The following table gives an overview of the combinations of the main identities. As described in
subclause 6.2 some flexibility is allowed in combinations of the IPUI types, e.g. IPUI type N could be used
by a service provider in combination with any ARC.
Table 1: Combinations of identities ARI, PARK and IPUI
‚¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶„
•��$5,��•�(QYLURQPHQW������������•�6$5,��•�3$5.��•�,38,����•
•�FODVV�•������������������������•�7$5,��•�FODVV�•�W\SH����•
…¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶‰
•�$�����•�5HVLGHQWLDO�DQG��������•�1R����•�$�����•�1�6�����•
•�������•�SULYDWH��3%;��VLQJOH���•�������•�������•���������•
•�������•�DQG�VPDOO�PXOWLSOH�����•�������•�������•���������•
•�������•�FHOO�V\VWHPV�����������•�������•�������•���������•
…¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶‰
•�%�����•�3ULYDWH����������������•� •�������•��3$%;V��PXOWLSOH�FHOO��•�������•�������•���������•
…¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶‰
•�&�����•�3XEOLF�VLQJOH��DQG�����•� •�������•�PXOWLSOH�FHOO�V\VWHPV��•�������•�������•���������•
…¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶‰
•�’�����•�3XEOLF�’(&7�DFFHVV�WR��•� •�������•�D�*60�RSHUDWRU�QHWZRUN�•�������•�������•���������•
…¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶�¶¶¶¶¶¶¶¶¶‰
•�(�����•�33�WR�33�GLUHFW��������•� •�������•�FRPPXQLFDWLRQ��SULYDWH�•�������•�������•���������•
”¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶¶¶»
5 FP identities
FP identities are used to inform PPs about the identity of a DECT FP and the access rights to that DECT
FP and thereby reduce the number of access attempts from unauthorised portables.
A DECT FP broadcasts this information on the N -channel via all its radio FPs, at least once per
T
multiframe. A PP must be able to interpret necessary parts of this broadcast information to detect the
access rights to a system or even access rights agreements between system operators, i.e. operators A
and B have a bilateral agreement permitting their users to roam between their systems. These agreements
can change and cannot therefore be stored in PPs without updating them frequently. Therefore the FP
handles access rights information which is embedded in the identity structure.
The DECT identity structure provides solutions for residential, public and private environments. This can
also be extended to combinations between these environments, e.g. private groups of users within a public
DECT network, and e.g. public users access to private DECT networks.
The base for the identity structure is formed by the ARCs and the ARDs.
ARC: shows the type of access to a DECT network, such as public, private or residential.
ARD: this number is unique to the service provider. Its structure depends on the ARC.
The ARC and ARD together form the basic identity, the ARI:
ARI: this identity is globally unique to a service provider, and shows the access rights related to this
service provider. This identity may be applied to any number of FP installations. There are three
categories of ARIs.
Page 15
ETS 300 175-6: September 1996
PARI: primary ARI has to be broadcast. This is also the most frequently broadcast ARI in order to give a
higher grade of service to users with these access rights. The PARI is broadcast over the N -
T
channel. See note below. The PARI (in conjunction with RPN) also carries information about
domains of handover and location areas.
SARI: secondary ARI. SARIs are less frequently broadcast than PARIs. They are sent as a SARI-list on
the Q -channel. The message used for SARIs (there could be more than one SARI) is described in
T
subclause 5.6.
TARI: tertiary ARI. The TARI is not broadcast at all and is only available as a (or in a) "TARI accept"
message, which is an answer to a "TARI request" message including the relevant PARK{y}. See
subclause 5.6.6 and ETS 300 175-3 [3], subclauses 7.2.5.10 and 7.3.6.2.
NOTE: Several FPs may apply the same ARI. However, as a PARI it has to be geographically
unique.
The classification of primary, secondary and tertiary access rights gives the possibility for operators or
system owners to offer their subscribers/users an almost unlimited list of roaming agreements. This
classification can be seen as an iceberg with the PARI visible on the top followed by a less visible SARI list
and in the depth the invisible TARIs. The PP procedure for handling PARIs, SARIs and TARIs is described
in subclause 8.2.
Structure of ARI, see figure 3:
‚¶¶¶¶¶�¶¶¶¶¶„
•�$5&�•�$5’�•
”¶¶¶¶¶¿¶¶¶¶¶»
Figure 3: Structure of ARI
ARC: 8 available classes named A - H. Only classes A - E are currently defined.
ARD: details, depends on the ARC.
One ARI together with a radio FP number, forms the RFPI. The ARI embedded in the RFPI is the PARI.
The RFPI has three purposes:
- to carry the PARI;
- to uniquely identify RFPs geographically;
- to show domains for handover and location areas.
The RFPI is frequently transmitted as bits a8 to a47 in the A-field using the N -channel and has therefore a
T
limitation of 40 bits. See ETS 300 175-3 [3], subclause 7.2.2.
���������������‚¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶„
���������������•�(�•��������������3$5,�������������•��531��•�����ELWV
���������������”¶¶¶¿¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶»
���������������_D���������������������������������������D��_
Figure 4: Structure of RFPI
E: this field indicates if there are any SARIs available. Value yes or no.
RPN: Radio fixed Part Number used for geographical separation.

Page 16
ETS 300 175-6: September 1996
Handover domains:
For DECT two handover domains are defined: internal handover (bearer and connection handover) to be
within a FP, and external handover to be between FPs. Internal handover is possible between RFPs that
have the same PARI in their RFPIs, i.e. only have changes in the RPN. See figure 5.
������������������������������‚¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶„
������������������5)3,��������•�(�•�������3$5,���������•��531��•
������������������������������”¶¶¶¿¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶¶¶»
����������������������������������������������([WHUQDO�•�,QWHUQDO
����������������������������������������������KDQGRYHU�•�KDQGRYHU
Figure 5: Indication of internal handover domain
The connection handover domain is always identical to the internal handover domain. The cluster size
defines the bearer handover domain. A PP regards the cluster size as identical with the internal handover
domain, if not else has been indicated by the optional P "Bearer handover information", see
T
ETS 300 175-3 [3], subclause 7.2.4.3.8. The RFPI for access rights classes A and C is also used for
limited information on handover domains, see subclauses 5.1 and 5.3.
External handover provision (by the external network) is indicated in ETS 300 175-3 [3],
subclause 7.2.3.4.2 "Standard capabilities, higher layer information" and ETS 300 175-5 [5], annex F
"Broadcast Attributes Coding", A PP can request the FP for information on PARIs of close by FPs to
which external handover is supported. The information also indicates for each FP if it is synchronised to
their own system or not.
Location Areas (LAs):
A Location Area (LA) is defined as x bits of the PARI plus RPN part of the RFPI, see figure 6. As soon as
any of these x bits change the PP has entered into a new LA and should do a location update. The x bits
are indicated by the Location Area Level (LAL) indicator.
Location area with LAL = x bits.
����5)3,��������‚¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶„
����������������•��(��•���������������3$5,�������������������•�531�•
����������������”¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¿¶¶¶¶¶»
����������������������•���������������[�ELWV������������•
����������������������•�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶!•
�������������������/RFDWLRQ�$UHD� �[�ELWV�RI�3$5,�DQG�531
Default location area.
����5)3,��������‚¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶„
����������������•��(��•���������������3$5,�������������������•�531�•
����������������”¶¶¶¶¶�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶�¶¶¶¶¶»
����������������������•�¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶!•
��������������������������������/RFDWLRQ�$UHD� �3$5,�
Figure 6: Location areas
LAL is submitted to a PP as a result of a successful location registration. See ETS 300 175-5 [5]. The PP
uses the default location area in the absence of a LAL.
A location registration at a FP can be permanent or temporary. If the location registration indicates
"temporary user" all registration data shall be cleared from a PP if the PP leaves the locked state with that
FP (fails to receive the PARI) for more than T601 minutes. See subclause 6.3.
Four different ARCs have been defined. The structure and layout of ARIs and RFPIs related to these
groups are described in the following subclauses.

Page 17
ETS 300 175-6: September 1996
5.1 ARI class A
This class is intended to be used for small residential and private (PBX) single cell FPs and small multi-cell
FPs with a maximum of 7 RFPs. Equipment belonging to this class will probably be sold by non-expert
retailers. Therefore the allocation process of class details must be delegated to manufacturers by a
common administration.
������������������������������•�$5&�•����$5’�����•
��������������$5,�������������…¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶¶‰
������������������������������•��$��•�(0&�•�)31��•
������������������������������”¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¶»
�������������������������������������������������� ����ELWV
�������������������������•��(����•��3$5,�����������•�531�•
��������������5)3,�$�����…¶¶¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶‰
�������������������������•��<�1��•�$���•�(0&�•�)31�•�531�•
�������������������������…¶¶¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶‰
������������������������������������������������������������ ����ELWV
Figure 7: Access rights class A, ARI and RFPI
EMC: Equipment Manufacturer's Code, is allocated to each manufacturer by ETSI, or by a provider
authorised by ETSI. Upper limit of EMC is 65 535. EMC = 0 shall not be used. The reason why the
EMC has 16 bits is to avoid small manufacturers contending with a long number series. Larger
manufacturers could have more than one EMC allocated.
FPN: Fixed Part Number, shall be allocated by the manufacturer as a unique number for each EMC. It has
an upper limit of 131 071, which gives a total of over 8,5 billion globally unique ARIs. FPN = 0 shall
not be used.
RPN: Radio fixed Part Number, this number is allocated by the manufacturer/installer and is used to
separate a maximum of 7 different cells from each other. In case of single cell FPs, RPN = 0. This
indicates for a PP that this FP does not have intercell handover, since there is only one RFP.
This class provides enough FP identities for single cell FPs and small multi cell FPs. This results in a longer
ARI than for all other classes. This ARI is therefore restricted only to be used as a PARI and not as SARI
or TARI, see subclause 5.6.
The class A DECT FP identity is the ARI part of the RFPI and it shall be globally unique.
5.2 ARI class B
This access rights class is reserved for more complex private installations such as LANs and various types
of multi-cell PABXs. In these environments it is necessary to be able to install new, or replace old,
equipment without changing ARIs or RFPIs. This indicates that ARI B is mainly a system identity that
follows a system and not a specific equipment.
The RFPIs could be allocated directly by the manufacturer, or by dealers, or installers authorised by the
manufacturer.
The manufacturer is responsible for distributing ARIs to authorised dealers/installers.
������������������������������•�$5&�•��$5’������������•
�������������$5,�%������������…¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶‰
������������������������������•�%���•�(,&�•�)31���)36�•
������������������������������”¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶»
��������������������������������������������������������� ����ELWV
������������������������•�(���•�3$5,������������������•�531�•
�������������5)3,�%�����…¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶‰
������������������������•�<�1�•�%���•�(,&�•�)31���)36�•�531�•
������������������������”¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶»
�������������������������������������������������������������� ����ELWV
Figure 8: Access right class B, ARI, RFPI

Page 18
ETS 300 175-6: September 1996
EIC: Equipment Installer's Code, is allocated by ETSI to each manufacturer, or by a provider authorised
by ETSI. Large manufacturers could have more than one EIC allocated. The same can also apply
for users, i.e. big companies can have their own EIC codes to be used at their different sites. Upper
limit of EIC is 65535. EIC = 0 shall not be used.
FPN: Fixed Part Number, is distributed together with the EIC by the manufacturer to authorised installers.
Upper limit of FPN is nominally 255. The value FPN = 0 shall not be used as a part of the RFPI.
FPS: Fixed Part Subnumber, is allocated by the system operator or installer. There are nominally 15
numbers available, FPS = 0 is reserved for future use, and shall not be used as a part of the RFPI.
A PP may be given access rights to all FPs with the same FPN, by use of a PARK{y}, where y includes
only the FPN, see clause 6. The border between FPN and FPS bits may vary, but the sum shall be 12 bits,
and FPN + FPS shall be unique for each EIC.
RPN: Radio fixed Part Number, is allocated by the operator or installer from the range 0-255. The number
of RFPs per system can be larger than 256 through geographical separation.
The class B DECT FP identity is the ARI part of the RFPI. In most cases, the ARI is globally unique.
Within the domain of a network of FPs controlled by one owner/operator, ARIs do not need to be globally
unique, but shall be geographically unique, to avoid ambiguity at call set-up and handover.
5.3 ARI class C
This ARC is reserved for public access such as 1-and 2-way public access service or local loop.
������������������������������•�$5&�•�$5’�������������•
�������������$5,�&������������…¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶‰
������������������������������•��&��•�32&�•�)31���)36�•
������������������������������”¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶»
������������������������������������������������������� ����ELWV
������������������������•�(���•�3$5,������������������•�531�•
�������������5)3,�&�����…¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶�¶¶¶¶¶‰
������������������������•�<�1�•��&��•�32&�•�)31���)36�•�531�•
������������������������”¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶¿¶¶¶¶¶»
������������������������������������������������������������� ����ELWV
Figure 9: Access right class C, ARI, RFPI
POC: Public Operator Code, is allocated by ETSI, authorised by ETSI, or by a provider authorised by
ETSI and is assigned to each operator as single codes or, if necessary, in blocks. The upper limit is
65 535. POC = 0 shall not be used. The operator shall provide a means for a PP user to
discriminate between a mobile and a fixed FP, using the "non-static FP" broadcast attribute.
FPN: is assigned by the FP operator and can be used to define different areas of subscription. Upper limit
of FPN is nominally 255. The value FPN = 0 shall not be used as a part of the RFPI. FPNs can be
chosen so that a wanted group of subscription areas is accessed by a PP by one PARK{y}, see
clause 6.
FPS: is allocated by the FP system operator or installer. FPS = 0 shall not be used as a part of the RFPI.
There are nominally 15 numbers available per subscription area, FPN, for geographical separation
of multiple cell FPs. See below on RPN for single cell FPs.
RPN: is allocated by the operator/installer. Single cell RFPIs have the least significant bit = 0, which is
used to ind
...