SIST EN 301 069-1 V1.2.2:2005

• Abstract:

  The definition of extensions to the NNI protocols (ISUP) to enable the introduction of a Transport Mechanism for use by applications requiring a bearer in conjunction with the support of the Application s signalling information flows.

• Status: Published
• Publication Date: 30-Jun-2005
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jul-2005
• Due Date: 01-Jul-2005
• Completion Date: 01-Jul-2005
• Ref Project: ETSI EN 301 069-1 V1.2.2 (1998-07) - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP); Application transport mechanism; Part 1: Protocol specification [ITU-T Recommendation Q.765, modified]

SIST EN 301 069-1 V1.2.2:2005 is the Slovenian adoption of ETSI EN 301 069-1 V1.2.2 for Integrated Services Digital Network (ISDN) signalling. It specifies the ISDN User Part (ISUP) Application Transport Mechanism (APM), which lets applications carry signalling information flows with a bearer over Signalling System No. 7 (SS7). The standard is used by telecom engineers, switch vendors, operators, and test teams that implement or verify ISUP-based transport and interworking.

What does SIST EN 301 069-1 V1.2.2:2005 specify?

SIST EN 301 069-1 V1.2.2:2005 specifies extensions to the Network-Network Interface (NNI) protocols in ISUP so that applications can use a transport mechanism together with application signalling information flows. In practice, it defines how application data is carried, segmented, reassembled, and reported inside ISUP call control messaging.

The EN is part 1 of a four-part series covering APM:

Annex / appendix	What it covers
Temporary Annex A	Modifications to ITU-T Recommendation Q.765
Appendix I	Example sequence diagrams of APM segmentation, informative

The body of the standard covers references, abbreviations, transport procedures, signalling congestion, unidentified context handling, remote and local error handling, and Application Transport Notification Information.

What are the key requirements of SIST EN 301 069-1 V1.2.2:2005?

SIST EN 301 069-1 V1.2.2:2005 focuses on how APM data is carried inside ISUP messages and how nodes react when transport or context handling fails. The most important points are the segmentation rules, the message order, and the way notifications are mapped to the correct APM-user.

Segmentation and message order

• Clause 10.2.1 limits APM segmentation to cases where all parameters cannot fit in IAM, ACM, CPG, CON, ANM or PRI, or where simple segmentation would exceed the 272 octet MTP limit. This tells implementers when segmentation is allowed, rather than leaving it to local choice.
• Clause 10.2.4 says the initial segment for each context goes in the first message and may be zero length. This matters because the receiving node must be able to associate the application data with the first ISUP call-control message.
• Clause 10.2.4 also allows the first segment message to be IAM, ACM, CPG, CON, ANM or PRI, and limits a context to one associated call-control message. That gives a clear binding between call setup and segmented application data.
• For segmented data carried with ACM, CPG, CON, ANM or PRI, the message is sent first, then SGM if simple segmentation applies to remaining ISUP information, then APM messages with later segments. If PRI is used, REL follows the last APM segment. This fixes the transmission order during call control.

Error handling and context handling

• Clause 10.2.4 requires the PIN to wait for a first backward message containing an empty APP before sending later segments for an IAM case. In practice, this prevents application data from being sent before a return path is confirmed.
• Clauses 13.1.2 and 13.4.1 use the Context Identifier to decide whether information is passed on or whether an APM_Error indication primitive is sent to the relevant APM-user. If the target APM-user does not exist, the notification is discarded and the maintenance function is notified.
• Clause 11.2.2 updates the signalling congestion wording by using Remote_Status primitive. This keeps the primitive naming consistent for implementations that handle congestion reporting.

Notification information

• Clause 14 places Application Transport Notification Information in the Encapsulated Application Information field of the Application Transport Parameter (APP) when the context identifier value is set to UCEH ASE. This tells engineers where the notification data is carried in the ISUP message structure.
• Clause 9.1 defines primitive flow direction between ISUP ASE and SACF. That matters for implementation and test work because it shows which primitives travel forward or backward.

What terms does SIST EN 301 069-1 V1.2.2:2005 define?

• Application Transport Mechanism (APM) - the ISUP-based transport defined by this standard for carrying application data with signalling.
• ISDN User Part (ISUP) - the SS7 protocol part modified here to support APM.
• Initial Address Message (IAM) - a call-control message that can carry the first segment of application data.
• Application Transport Parameter (APP) - the parameter that carries Application Transport Notification Information when needed.
• Application Transport Mechanism User Application (APM-user) - the application entity selected by the Context Identifier for notification or transport handling.
• Context Identifier - the value used to identify the relevant APM-user or pass-on handling for a notification.
• Segmentation Message (SGM) - the ISUP message used when simple segmentation applies to remaining information.

Who uses SIST EN 301 069-1 V1.2.2:2005?

Telecom engineers use SIST EN 301 069-1 V1.2.2:2005 when designing or integrating SS7 and ISUP signaling functions that need application transport. Switch and network vendors use it to implement message handling, segmentation, and reassembly in node software. Operators and quality teams use it to specify conformance expectations for ISUP-based services and to plan interoperability tests. Test labs use the companion parts for PICS, TSS&TP, and ATS when building conformance test coverage.

What changed in SIST EN 301 069-1 V1.2.2:2005 from the previous edition?

SIST EN 301 069-1 V1.2.2:2005 adopts ITU-T Recommendation Q.765 with agreed ETSI modifications. The listed changes update references to EN 300 356-1 and ITU-T Recommendation Q.1400, revise segmentation and reassembly wording, adjust remote and local error handling, and keep Appendix I as an informative source of example segmentation diagrams.

Which standards are used with SIST EN 301 069-1 V1.2.2:2005?

• EN 300 356-1 - provides the ISUP version 3 basic services reference used instead of ITU-T Recommendations Q.761 to Q.764, and it also replaces Annex T references.
• ITU-T Recommendation Q.1400 - gives the architecture framework for signalling and OA&M protocols using OSI concepts.
• Part 2 of this EN series - supplies the Protocol Implementation Conformance Statement (PICS) proforma specification.
• Part 3 of this EN series - supplies the Test Suite Structure and Test Purposes (TSS&TP).
• Part 4 of this EN series - supplies the Abstract Test Suite (ATS).

What does the SIST EN 301 069-1 V1.2.2:2005 document contain?

The document contains the protocol specification for APM, plus the ETSI modifications to ITU-T Recommendation Q.765. It includes the abbreviation list, message and primitive mapping, segmentation and reassembly procedures, and the handling rules for unidentified context and remote errors. Table 14/Q.765 describes primitive flows between ISUP ASE and SACF, and Appendix I gives example sequence diagrams for APM segmentation. Temporary Annex A collects the agreed text changes that were applied to the recommendation.

SLOVENSKI STANDARD
01-julij-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'16LJQDOL]DFLMDãW±,6'1
XSRUDEQLãNLGHO,683$SOLNDFLMVNLSUHQRVQLPHKDQL]HP$30GHO
6SHFLILNDFLMDSURWRNROD>SULSRURþLOR,7874VSUHPHQMHQR@
Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part
(ISUP); Application transport mechanism; Part 1: Protocol specification [ITU-T
Recommendation Q.765, modified]
Ta slovenski standard je istoveten z: EN 301 069-1 Version 1.2.2
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 301 069-1 V1.2.2 (1998-07)
European Standard (Telecommunications series)
Integrated Services Digital Network (ISDN);
Signalling System No.7;
ISDN User Part (ISUP);
Application transport mechanism;
Part 1: Protocol specification
[ITU-T Recommendation Q.765, modified]

2 EN 301 069-1 V1.2.2 (1998-07)
Reference
DEN/SPS-01042-1 (9wc90ipc.PDF)
Keywords
ISDN, SS7, ISUP, NNI, protocol
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: [phone]  Fax: [phone]
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Internet
[e-mail]
http://www.etsi.fr
http://www.etsi.org
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.
ETSI
3 EN 301 069-1 V1.2.2 (1998-07)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Signalling
Protocols and Switching (SPS).
The present document is part 1 of a multi-part EN covering Integrated Services Digital Network (ISDN); Signalling
System No.7; ISDN User Part (ISUP); Application Transport Mechanism (APM), as identified below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP)";
Part 4: "Abstract Test Suite (ATS)";
National transposition dates
Date of adoption of this EN: 17 April 1998
Date of latest announcement of this EN (doa): 31 July 1998
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 January 1999
Date of withdrawal of any conflicting National Standard (dow): 31 January 1999
Endorsement notice
The text of ITU-T Recommendation Q.765 was approved by ETSI as an EN with agreed modifications as given below.
NOTE 1: New or modified text is indicated using sidebars. In addition, underlining and/or strike-out are used to
highlight detailed modifications where necessary.
NOTE 2: ITU-T Recommendation Q.765 had not yet been adopted by ITU-T prior to the submission for Vote of
the present document. This endorsement is based upon the draft of that Recommendation which
accompanies the present document, located in an archive file named 9wc90ipc.lzh.
ETSI
4 EN 301 069-1 V1.2.2 (1998-07)
Clause 2, References
Replace this clause by:
Normative references
References may be made to:
a)  specific versions of publications (identified by date of publication, edition number, version number, etc.), in
which case, subsequent revisions to the referenced document do not apply; or
b)  all versions up to and including the identified version (identified by "up to and including" before the version
identity); or
c)  all versions subsequent to and including the identified version (identified by "onwards" following the version
identity); or
d)  publications without mention of a specific version, in which case the latest version applies.
A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1]            EN 300 356-1 (V3.1): "Integrated Services Digital Network (ISDN); Signalling System No. 7;
ISDN User Part (ISUP) version 3 for the international interface; Part 1: Basic services [ITU-T
Recommendations Q.761 to Q.764 (1997), modified]".
[2]            ITU-T Recommendation Q.1400 (1993): "Architecture framework for the development of
signalling and OA&M protocols using OSI concepts".
Throughout the text of ITU-T Recommendation Q.765
Replace references as shown below.
Reference in ITU-T Recommendation Q.765 Modified reference
ITU-T Recommendation Q.761 [1] EN 300 356-1 [1]
ITU-T Recommendation Q.762 [2] EN 300 356-1 [1]
ITU-T Recommendation Q.763 [3] EN 300 356-1 [1]
ITU-T Recommendation Q.764 [4] EN 300 356-1 [1]
Annex T EN 300 356-1 [1]
Annex T (temporary), Changes to ITU-T Recommendations Q.761,
Q.762, Q.763 and Q.764
Not supported, see EN 300 356-1 [1].
Appendix I, Example sequence diagrams of APM segmentation
Appendix I has the status of an informative annex.
ETSI
5 EN 301 069-1 V1.2.2 (1998-07)
Temporary Annex A (normative):
Modifications to ITU-T Recommendation Q.765
This annex contains the proposed changes to the text of the ITU-T Recommendation Q.765 as agreed by TC SPS in the
meeting which addressed the national comments received following PE9748. The complete text of this annex will be
contributed to the ITU-T resolution 1 procedure for approval of Q.765. Once this procedure is finished, it is intended
that the annex be removed from this EN.
Since it is possible that some of the modifications below will not be included in Q.765 those that will not create any
compatibility problems in the case of mismatch between Q.765 and the present docuement are to become a part of the
main body of this EN. The modifications that do not become part of Q.765 and may result in an incompatibility when a
Q.765 based service and an EN 301 069-1 based service interwork will be removed from this EN. Each of the proposals
below is, therefore, marked appropriately in one of the following two ways:
- if the item is to be removed from the EN "remove"
- if the item is to be included in the EN "keep"
Clause 4, Abbreviations keep
Modify in the following way:
ACM                Address Complete Message
APM-user Application Transport Mechanism User Application
CPG                 Call Progress Message
IAM                 Initial Address Message
PRI                 Pre-Release Information Message
Subclause 7.2.1, Introduction keep
Add the following note just before the third bullet point:
NOTE:   In the case that no such acknowledgement is received by the PIN before reception of either:
an ACM indicating "subscriber free", or
a CPG indicating "alerting", or
an ANM or CON
with no APP (for the appropriate context) then if the application association for the call was essential, the
call shall be release and the maintenance function shall be notified.
Subclause 8.3, Information flows related to messages received by
keep
the node
Modify the 2nd sentence of the 2nd paragraph as follows:
For received messages, the mapping of APM_U_Data, APM_Data and APM_Transfer (tables 4, 5 and 6) primitives is
the reverse to that described in the tables for outgoing messages sent by the node in subclause 6.28.2.
ETSI
6 EN 301 069-1 V1.2.2 (1998-07)
Subclause 9.1, Table 14/Q.765 - Primitives between ISUP ASE and
SACF keep
Replace note of table 14 by:
NOTE:   Primitive flow from SACF to ISUP ASE - ‹
Primitive flow from ISUP ASE to SACF - fi
Subclause 10.2.1, Normal Procedures - Sending keep
Replace the sentence "How this is determined is implementation specific" by:
APM segmentation procedures shall only apply if it is not possible to transfer all parameters in the IAM, ACM, CPG,
CON, ANM or PRI message and SGM, if simple segmentation procedures are used, because the 272 octet MTP limit
would be exceeded.
Subclause 10.2.4, Segmentation keep
Modify the 2nd paragraph as follows:
The initial segment for each context must be transported in the first message and this initial segment size may be of zero
lengt
...