SIST ETS 300 240 E1:2005
(Main)Private Telecommunication Network (PTN); Signalling at the S-reference point; Generic feature key management protocol for the control of supplementary services
Private Telecommunication Network (PTN); Signalling at the S-reference point; Generic feature key management protocol for the control of supplementary services
Contains stage 3 of the generic feature key procedures for supplementary services at the S reference point. See ENV 41 005 for defintion of stage 3. See ENV 41 004 for definition of S reference point. To contain PICS proforma
Zasebno omrežje z integriranimi storitvami (PISN) - Signalizacija na referenčni točki S - Generična lastnost ključnega upravljavnega protokola za krmiljenje dopolnilnih storitev
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST ETS 300 240 E1:2005
01-marec-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL 3,61 6LJQDOL]DFLMDQDUHIHUHQþQL
WRþNL6*HQHULþQDODVWQRVWNOMXþQHJDXSUDYOMDYQHJDSURWRNROD]DNUPLOMHQMH
GRSROQLOQLKVWRULWHY
Private Telecommunication Network (PTN); Signalling at the S-reference point; Generic
feature key management protocol for the control of supplementary services
Ta slovenski standard je istoveten z: ETS 300 240 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST ETS 300 240 E1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 240 E1:2005
---------------------- Page: 2 ----------------------
SIST ETS 300 240 E1:2005
EUROPEAN ETS 300 240
TELECOMMUNICATION June 1993
STANDARD
Source: ETSI TC-ECMA Reference: DE/ECMA-0027
ICS: 33.080
Key words: PTN, SSIG-FK, ECMA-161
Private Telecommunication Network (PTN);
Signalling at the S-reference point
Generic feature key management protocol for the control of
supplementary services
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 1993. All rights reserved.
New presentation - see History box
---------------------- Page: 3 ----------------------
SIST ETS 300 240 E1:2005
Page 2
ETS 300 240:1993
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 240 E1:2005
Page 3
ETS 300 240:1993
Foreword 7
1 Scope 9
2 Conformance 9
3 References 9
4 Definitions 9
4.1 Access 9
4.2 Endpoint Identifier (EID) 9
4.3 Feature 9
4.4 Feature indication 9
4.5 Feature request 9
4.6 Private Telecommunication Network (PTN) 9
4.7 Private Telecommunication Network Exchange (PTNX) 9
4.8 Service profile 10
4.9 Service Profile Identifier (SPID) 10
4.10 Supplementary Service 10
4.11 Terminal Equipment (TE) 10
4.12 Terminal Identifier (TID) 10
4.13 User 10
4.14 User Service Identifier (USID) 10
5 Acronyms and Abbreviations 10
6 Feature Key Management Protocol 10
6.1 Messages 11
6.1.1 Messages used in association with a Call Reference 11
6.1.2 Messages used in association with the Dummy Call Reference 11
6.1.3 Additional information elements 12
6.2 Procedures 12
6.2.1 TE Requests 12
6.2.1.1 Feature requests in association with a Call Reference 12
6.2.1.2 Feature requests in association with the Dummy Call Reference 13
6.2.1.3 Switchhook indication 13
6.2.2 PTN responses 13
6.2.2.1 Return of a Feature indication 13
6.2.2.2 Prompting for further information 13
6.2.2.3 Implicit response 13
6.2.2.4 Return of Signal, Cause or Display information elements 13
6.2.2.5 Responses during error conditions 13
6.2.3 General aspects 13
6.2.3.1 Use of Feature indication information elements independent of a feature request 13
6.2.3.2 Deactivation procedures 13
6.2.3.3 Clearing of a call 14
6.2.3.4 Sending of multiple feature requests / indications 14
---------------------- Page: 5 ----------------------
SIST ETS 300 240 E1:2005
Page 4
ETS 300 240:1993
6.2.4 Error conditions 14
6.2.4.1 Invalid feature request 14
6.2.4.2 Invalid call reference 14
6.2.4.3 Invalid feature indication or PTN response 14
7 Coding of Information Elements 14
7.1 Dummy call reference 14
7.2 Calling party number 14
7.3 Cause14
7.4 Display 14
7.5 Endpoint identifier 15
7.6 Feature activation 15
7.7 Feature indication 16
7.8 Information request 17
7.9 Keypad facility 18
7.10 Signal 18
7.11 Service profile identification 18
7.12 Switchhook 19
Annex A (normative): 20
User Service Profiles and Terminal Identification 20
A.1 Introduction 20
A.2 User service profiles 22
A.3 Terminal identification 22
A.4 Initialization 22
A.4.1 Terminal requested initialization 22
A.4.2 PTN solicited initialization 23
A.4.3 Collision 23
A.5 Identification procedures 23
Annex B (normative): 24
Information Request Procedures 24
B.1 Introduction 24
B.2 Procedures 24
B.2.1 Normal procedures 24
B.2.2 Abnormal procedures 24
Annex C (informative): 25
Illustration of the Feature Key Management Protocol 25
---------------------- Page: 6 ----------------------
SIST ETS 300 240 E1:2005
Page 5
ETS 300 240:1993
Annex D (normative): 26
Protocol Implementation Conformance Statement (PICS) Proformas 26
D.1 Introduction 26
D.2 Instructions for Completing the PICS Proforma 26
D.2.1 General Structure of the PICS Proforma 26
D.2.2 Additional Information 26
D.2.3 Exception Information 27
D.3 PICS Proforma for ETS 300 240 PTNX Implementations 27
D.3.1 Implementation Identification 27
D.3.2 Protocol Summary 27
D.3.3 Procedures for the PTNX 28
D.3.4 Messages and information elements - PTNX Requirements 29
D.4 PICS Proforma for ETS 300 240 TE Implementations 30
D.4.1 Implementation Identification 30
D.4.2 Protocol Summary 30
D.4.3 Procedures for the TE 31
D.4.4 Messages and information elements - TE Requirements 32
Annex E (informative): 33
Relationship to Corresponding Standards for Public ISDNs 33
History 34
---------------------- Page: 7 ----------------------
SIST ETS 300 240 E1:2005
Page 6
ETS 300 240:1993
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 240 E1:2005
Page 7
ETS 300 240:1993
Foreword
This European Telecommunication Standard (ETS) has been produced by the European Computer Manufacturers
Association (ECMA) on behalf of its members and those of the European Telecommunications Standards Institute
(ETSI).
This ETS defines the feature key management stimulus protocol for use at the S reference point in support of the
basic circuit mode services.
The feature key management protocol for Private Telecommunication Networks selects options from and
complements the CCITT Recommendation Q.932. The differences between this ETS and the relevant section of
Q.932 and the impact of these differences on terminal interchangeability can be found in annex E.
This ETS was produced by ECMA using the ECMA guidelines for the production of standards and the ECMA
stylesheet. In order to avoid undue delays in the approvals procedure, it has been agreed that this ETS will not be
converted to the ETSI stylesheet.
---------------------- Page: 9 ----------------------
SIST ETS 300 240 E1:2005
Page 8
ETS 300 240:1993
Blank page
---------------------- Page: 10 ----------------------
SIST ETS 300 240 E1:2005
Page 9
ETS 300 240:1993
1 Scope
This ETS defines the Feature Key Management signalling protocol for the purpose of supplementary service
control at an interface at the S reference point between a Terminal Equipment (TE) and a Private
Telecommunication Network (PTN).
The Feature Key Management protocol operates in conjunction with the signalling protocol specified in
Standard ETS 300 192 for circuit-switched call control. It is based on the use of the two information
elements, Feature activation and Feature indication. While the procedures associated with feature key
invocation and indication are specified in this ETS, the allocation of actual codes used to designate
individual supplementary services is outside the scope of this ETS.
This ETS is applicable to the user accesses of PTNs and to TEs which are intended for connection to PTNs.
2 Conformance
In order to conform to this ETS, a PTNX shall satisfy the requirements identified in the Protocol
Implementation Conformance Statement (PICS) Proforma in sub-clause D.3 of Annex D.
In order to conform to this ETS, a TE shall satisfy the requirements identified in the Protocol
Implementation Conformance Statement (PICS) Proforma in sub-clause D.4 of Annex D.
3 References
ETS 300 102-1 (1990) ISDN User-Network Interface Layer 3 Specification for Basic Call
Control
I-ETS 300 169 (1992) Private Telecommunication Networks (PTN) - Signalling at the S
Reference Point - Data Link Layer Protocol
ETS 300 189 (1992) Private Telecommunication Networks (PTN) - Addressing
ETS 300 192 (1992) Private Telecommunication Networks (PTN) - Signalling Protocol at the S
Reference Point - Circuit Mode Basic Services
CCITT Rec. I.112 (1988) Vocabulary of terms for ISDNs
CCITT Rec. Q.932 (1988) Generic procedures for the control of ISDN supplementary services
ENV 41007 (1989) Definition of Terms in Private Telecommunication Networks
4 Definitions
For the purpose of this ETS the following definitions apply.
4.1 Access
The definition of CCITT Rec. I.112 for "user-network access" shall apply, with "telecommunication
network" being interpreted as "PTN".
4.2 Endpoint Identifier (EID)
Information used for terminal identification. The endpoint identifier parameters contain a USID and TID
and additional information used to interpret them.
4.3 Feature
A supplementary service or a user-initiated PTN action which constitutes one specific part of a
supplementary service.
4.4 Feature indication
An indication of the status of a feature from the PTN to the user.
4.5 Feature request
The initiation of a feature by the user.
4.6 Private Telecommunication Network (PTN)
The definition in ENV 41007 shall apply.
4.7 Private Telecommunication Network Exchange (PTNX)
The definition in ENV 41007 shall apply.
---------------------- Page: 11 ----------------------
SIST ETS 300 240 E1:2005
Page 10
ETS 300 240:1993
4.8 Service profile
The information that the PTN maintains for a given user to characterize the service offered by the PTN to
that user. As an example, this may contain the association of feature identifiers with specific
supplementary services. A service profile may for example be allocated to a PTN access interface or to a
particular TE or a group of TEs.
4.9 Service Profile Identifier (SPID)
Identifies a specific service profile in the case that a TE asks for automatic assignment of a USID and
TID by the PTN. The SPID allows the PTN to distinguish between different terminals that would
otherwise be indistinguishable (e.g. same PTN number). The SPID value is provided to the user when
installing a service profile and should uniquely identify that service profile.
4.10 Supplementary Service
A capability provided by a PTN to a PTN user over and above that of a basic call.
4.11 Terminal Equipment (TE)
The definition in ENV 41007 shall apply.
4.12 Terminal Identifier (TID)
Identifies a terminal uniquely within a given USID. If two TEs on an interface have the same service
profile the two TEs will be assigned the same USID. However, two different TIDs are required to
uniquely identify each of the two TEs.
4.13 User
The definition in ENV 41007 shall apply.
4.14 User Service Identifier (USID)
Uniquely identifies a service profile on a PTN access interface.
5 Acronyms and Abbreviations
CEI Connection Endpoint Identifier
CES Connection Endpoint Suffix
EID Endpoint Identifier
ISDN Integrated Services Digital Network
PICS Protocol Implementation Conformance Statement
PTN Private Telecommunication Network
PTNX Private Telecommunication Network Exchange
SAPI Service Access Point Identifier
SPID Service Profile Identifier
TE Terminal Equipment
TEI Terminal Endpoint Identifier
TID Terminal Identifier
USID User Service Identifier
6 Feature Key Management Protocol
Note 1:
The text in this clause is based on section 5 of CCITT Rec. Q.932. Differences are indicated by
emboldening.
The Feature Key management protocol is a mechanism allowing users to invoke supplementary services. As
these are stimulus procedures, the protocol elements do not directly identify the service invoked. To
determine the service invoked requires knowledge of the user's service profile maintained in the PTN. No
call state changes occur directly as a result of these procedures.
---------------------- Page: 12 ----------------------
SIST ETS 300 240 E1:2005
Page 11
ETS 300 240:1993
The Feature Key management protocol is based on two information elements: Feature activation and Feature
indication. The Feature activation information element is the means by which a user requests a
supplementary service. The Feature activation information element contains a feature identifier number
which the PTN maps to the corresponding service as indicated by that user's service profile. The TE need
not have any knowledge of what service is being indicated by the feature identifier number and the user may
send a feature request at any time.
Feature indication is the means by which a response to a feature request is indicated by the PTN. The
feature identifier number correlates the PTN's response with a user's request and/or an indicator associated
with a TE. The Feature indication information element also contains a status indicator. The status indicator
indicates the status of the requested service and may be used by the TE as appropriate with its man-machine
interface.
6.1 Messages
6.1.1 Messages used in association with a Call Reference
The Feature activation and Feature indication information elements may be present in several of the
messages defined in ETS 300 192. The Feature activation information element may appear in the
following messages in the direction TE to PTN:
a) SETUP
b) INFORMATION
c) ALERTING
d) CONNECT
e) DISCONNECT
f) RELEASE
g) RELEASE COMPLETE
The Feature activation information element may be repeated in a single message.
Note 2:
"Activation" as part of the name "Feature activation" should not be confused with the term
"activation" used elsewhere, e.g. in stage 1 descriptions. Depending on the context, "Feature
activation" can mean invocation, activation, deactivation, interrogation etc. of a supplementary
service.
The Feature indication information element may be sent in the direction PTN to TE in the following
messages:
a) SETUP
b) SETUP ACKNOWLEDGE
c) CONNECT
d) CALL PROCEEDING
e) ALERTING
f) INFORMATION
g) DISCONNECT
h) RELEASE
i) RELEASE COMPLETE
j) CONNECT ACKNOWLEDGE
The Feature indication information element may be repeated in a single message.
6.1.2 Messages used in association with the Dummy Call Reference
One or more Feature activation information elements may appear in an INFORMATION
message in the direction TE to PTN.
One or more Feature indication information elements may appear in an INFORMATION
message in the direction PTN to TE.
---------------------- Page: 13 ----------------------
SIST ETS 300 240 E1:2005
Page 12
ETS 300 240:1993
6.1.3 Additional information elements
Several messages may contain further information elements, in addition to those specified in
ETS 300 192, according to the following list:
Calling party number: May be included in an INFORMATION message with the
dummy call reference in the direction TE to PTN for multiple
subscriber number arrangements (see ETS 300 189).
Cause: May be included in an INFORMATION message in the
direction PTN to TE (as response to a feature request).
Display: May be included in every message in the direction PTN to TE.
Endpoint identifier: May be included in INFORMATION and in SETUP messages
(used for the optional terminal identification procedures
described in Annex A).
Information request: May be included in an INFORMATION message in the
direction PTN to TE (used for the optional information request
procedures described in Annex B).
Keypad facility: May be included in INFORMATION and SETUP messages in
the direction TE to PTN to provide additional information, e.g.
in conjunction with the information request procedures
according to Annex B.
Signal: May be included in the direction PTN to TE in the messages:
ALERTING
CONNECT
CONNECT ACKNOWLEDGE
DISCONNECT
INFORMATION
RELEASE
RELEASE COMPLETE
SETUP
SETUP ACKNOWLEDGE
Service profile identification: May be included in an INFORMATION message in the
direction TE to PTN (used for the optional automatic
assignment procedure described in sub-clause A.4 of Annex A).
Switchhook: May be included in the direction TE to PTN in the messages:
CONNECT
DISCONNECT
INFORMATION
RELEASE
SETUP
The coding of these information elements is specified in clause 7.
6.2 Procedures
6.2.1 TE Requests
6.2.1.1 Feature requests in association with a Call Reference
The TE may request a feature by including a Feature activation information element in any of the
messages defined in 6.1. The TE shall indicate the desired feature by specifying the appropriate
value in the feature identifier number field.
An INFORMATION message may be sent at any time after sending or receiving the first
response to the SETUP message and before sending or receiving a RELEASE or RELEASE
COMPLETE message.
---------------------- Page: 14 ----------------------
SIST ETS 300 240 E1:2005
Page 13
ETS 300 240:1993
6.2.1.2 Feature requests in association with the Dummy Call Reference
The Feature activation information element may be sent in an INFORMATION message
using the dummy call reference in situations where it is inappropriate to use an existing call
reference or to establish a new call reference for the purpose.
Before sending an INFORMATION message with the dummy call reference the TE must first
ensure that a Data Link connection exists between the TE and the PTN. If a Data Link
connection does not exist the TE shall establish a Data Link connection according to the
procedures described in sub-clause 6.1.1 of ETS 300 192.
6.2.1.3 Switchhook indication
The Switchhook information element may be used to indicate "on-hook" or "off-hook" to the
PTN.
6.2.2 PTN responses
The PTN may respond to a feature request in several ways. The action chosen is supplementary
service and implementation specific.
6.2.2.1 Return of a Feature indication
The PTN may return a Feature indication information element in an INFORMATION message or
any other appropriate call control message as defined in 6.1. The Feature indication may or may not
have the same feature identifier number as was present in the original feature request. The status
indicator shall be provided as appropriate to the specific supplementary service requested.
6.2.2.2 Prompting for further information
The PTN may prompt the user for more information (e.g. additional information related to a given
feature request). The procedures employed are implementation specific, possibilities including
the use of tones/ announcements, displays, etc.; the TE may send the required information in
Keypad facility or other suitable information elements. Optionally the information request
procedures defined in Annex B may be used.
6.2.2.3 Implicit response
The PTN, under certain situations, may not return any explicit indication to the TE after a feature
request. In this case the response is implicit, such as the acknowledgement inherent in providing the
service.
6.2.2.4 Return of Signal, Cause or Display information elements
The PTN may return any combination of Signal, Cause or Display information elements, also in
conjunction with other responses specified in 6.2.2. The use of these information elements is
supplementary service and implementation specific.
6.2.2.5 Responses during error conditions
When an error condition exists (as defined in 6.2.4) the PTN may:
−− React with one or more responses according to 6.2.2.1 - 6.2.2.4; or
− Ignore the feature request and not respond at all.
The PTN may also clear appropriate existing calls in conjunction with the above actions.
6.2.3 General aspects
6.2.3.1 Use of Feature indication information elements independent of a feature request
The PTN may choose to send Feature indication information at any time, independent of the status
of any call(s), either in an INFORMATION message or in an appropriate call control message as
specified in 6.1.1 and 6.1.2. Multiple Feature indication information elements may be included in
a single message if more than one indicator is to be updated.
6.2.3.2 Deactivation procedures
When explicitly deactivating a supplementary service, two methods may be used:
a) sending of a feature request with the same feature identifier may deactivate the supplementary
service; some supplementary services may be "toggled" on and off;
b) sending a feature request with a different feature identifier which is explicitly defined
(between the TE and the PTN) as the deactivator for that particular supplementary service.
---------------------- Page: 15 ----------------------
SIST ETS 300 240 E1:2005
Page 14
ETS 300 240:1993
6.2.3.3 Clearing of a call
If a Feature activation information element is sent using the call reference of an active call, and that
call is cleared for some reason, then there exists no call reference with which to correlate the feature
indication. If a Feature indication information element is to be returned, one of the following
options may be used:
a) The PTN may send a Feature indication information element in one of the call clearing
messages (i.e., DISCONNECT, RELEASE, or RELEASE COMPLETE).
b) The PTN may send a Feature indication information element in an INFORMATION message
after clearing has occurred, using the dummy call reference.
6.2.3.4 Sending of multiple feature requests / indications
If a sequence of feature requests is received, either in one message or in separate messages, so
rapidly that the PTN cannot respond to the first feature request prior to receiving a subsequent
feature request, the PTN shall act upon all feature requests in the order received by returning
multiple Feature indication information elements or other responses as detailed in 6.2.2. These may
be sent in a single message or in multiple messages.
If a TE receives a sequence of feature indications, either in one message or in separate
messages, it shall act upon each feature indication individually in the order received.
6.2.4 Error conditions
The error procedures specified in sub-clause 6.3 of ETS 300 192 shall also apply for the
messages and information elements specified in this ETS. Additionally, the following procedures
shall apply.
6.2.4.1 Invalid feature request
If a TE requests a feature using an invalid feature identifier number, the PTN shall take any of the
actions specified in 6.2.2.5, as appropriate. An invalid feature identifier number is one for which the
user is not provided a corresponding service, or the value is not understood by the service provider
(e.g. out of range).
6.2.4.2 Invalid call reference
If a TE uses the dummy call reference in a message other than INFORMATION, or if it sends
an INFORMATION message with the dummy call reference when the PTN expects an
existing call reference for a particular feature request, the PTN shall not provide the service
and shall respond as indicated in 6.2.2.5.
6.2.4.3 Invalid feature indication or PTN response
A TE may ignore an invalid Feature indication (e.g. an unknown feature identifier number)
or any PTN response which it did not expect or cannot handle correctly. Other actions of the
TE are implementation dependent.
7 Coding of Information Elements
Note 3:
This clause is based on section 8 of CCITT Rec. Q.932, with differences indicated by emboldening, and also
contains references to ETS 300 192 and ETS 300 102-1.
7.1 Dummy call reference
Sub-clause 4.3 of ETS 300 102-1 shall apply.
7.2 Calling party number
ETS 300 192, 11.5.10, shall apply.
7.3 Cause
ETS 300 102-1, 4.5.12, shall apply.
7.4 Display
ETS 300 102-1, 4.5.15, shall apply.
---------------------- Page: 16 ----------------------
SIST ETS 300 240 E1:2005
Page 15
ETS 300 240:1993
7.5 Endpoint identifier
The purpose of the Endpoint identifier information element is:
− to indicate the user service identifier and terminal identifier for the purpose of terminal
identification; and
− to indicate a specific terminal for the purpose of terminal selection.
See annex A for the associated procedures.
The Endpoint identifier information element is coded as shown in figure 1 and table 1. The default
maximum length of the Endpoint identifier information element is four octets.
8 7654 321
Endpoint identifier
0 0 1 1 1 0 1 1 Octet 1
information element identifier
Length of Endpoint identifier contents 2
1
User service identifier 3
ext
1
Inter Terminal identifier 4*
ext
pret.
* This octet is optional
Figure 1 - Endpoint identifier information element
Table 1 - Endpoint identifier information element
User service identifier (USID) (octet 3)
The USID is a selection parameter which identifies a group of terminals on an interface which
share a common service profile and which may be addressed together. Upon receipt of this
parameter a terminal will consider itself as being addressed if the value received matches its
stored value or if the value received is coded as all ONEs (127). When USID is coded 127,
octet 4 shall not be used.
Interpreter (octet 4, bit 7)
Bit 7 of octet 4 indicates how a terminal is to interpret the TID field received (see TID definition
below) if the value of this field is not 63. When set to ZERO the terminal is being addressed only
if the TID value matches. When set to ONE, the terminal is being addressed only if the TID
received does not match. In the direction TE to PTN this bit shall be set to ZERO.
Terminal identifier (TID) (octet 4, bits 1 to 6)
The TID is a selection parameter which identifies a single terminal within a group designated by
a USID value. For USID=127 the TID does not apply. Upon receipt of this field, a terminal will
consider itself addressed if one of the following is true:
− the interpreter bit is set to ZERO and the TID value received matches the terminal's stored
value;
− the interpreter bit is set to ONE and the TID value received does not match the terminal's
stored value;
− the TID value received is set to all ONEs (63).
7.6 Feature activation
The purpose of the Feature activation information element is to invoke a supplementary service as
identified by the feature identifier number. The service associated with the feature identifier number is
dependent on that particular user's service profile.
---------------------- Page: 17 ----------------------
SIST ETS 300 240 E1:2005
Page 16
ETS 300 240:1993
The default maximum length of this information element is four octets.
The Feature activation information element is coded as shown in figure 2 and table 2.
8 7654 321
Feature activation
0 0 1 1 1 0 0 0 Octet 1
information element identifier
Length of Feature activation contents 2
0/1
Feature identifier number 3
ext
1
Feature identifier number 3a
ext
(continuation)
Figure 2 - Feature activation information element
Table 2 - Feature activation information element
Feature identifier number (octet 3 and 3a)
The feature identifier number is a unique number assigned to a feature in a service profile. The
feature identifier number is part of both the Feature activation and Feature indication information
elements. This number identifies the feature that is being requested or updated. The association
of a particular number to a particular feature may be different for each user.
Bit 8 in octet 3 is used to extend the feature identifier field. If bit 8 is set to ZERO then another
octet follows; if bit 8 is set to ONE then octet 3 is the last octet. The identifier numbers for a one-
octet field range from 1 to 127. For a multi-octet field the order of bit values progressively
decreases as the octet number increases.
7.7 Feature indication
The purpose of the Feature indication information element is to allow the PTN to convey feature
indications to the user regarding the status of a supplementary service.
The default maximum length of this information element is 5 octets.
The coding of the Feature indication information element is shown in Figure 3 and Table 3.
---------------------- Page: 18 ----------------------
SIST ETS 300 240 E1:2005
Page 17
ETS 300 240:1993
8 7654 321
Feature indication
0 0 1 1 1 0 0 1 Octet 1
information element identifier
Length of Feature indication contents 2
0/1
Feature identifier number 3
ext
1
Feature identifier number 3a
ext
(continuation)
0 0 0 0 Status 4
Spare indicator
Figure 3 - Feature indication information element
Table 3 - Feature indication information element
Feature identifier number (octet 3 and 3a)
See table 2
Status indicator (octet 4)
The status indicator field identifies the current status of a supplementary service.
Bits Example of possible
4 3 2 1 Status Meaning TE implementation
0 0 0 0 Deactivated Feature is in the Lamp off
deactivated state
0 0 0 1 Activated Feature is in the active Lamp steady on
state
0 0 1 0 Prompt Feature prompt (waiting Lamp steady flash
for user input)
0 0 1 1 Pending Feature is pending Lamp steady wink
All other values are reserved.
7.8 Information request
The purpose of the Information request information element is to provide the capability for requesting
additional information and signalling completion of the information request (see annex B).
The information request information element is coded as shown in figure 4 and table 4.
The default maximum length of the Information request information element is three octets.
---------------------- Page: 19 ----------------------
SIST ETS 300 240 E1:2005
Page 18
ETS 300 240:1993
8 7654 321
Information request
0 0 1 1 0 0 1 0 Octet 1
information element identifier
Length of information request contents 2
1 Info
Type of information 3
ext Req.
Ind.
Figure 4 - Information request information element
Table 4 - Information request information element
Information request indicator (octet 3, bit 7)
Bit 7 = 0
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.