SIST EN 301 069-1:2000

• Abstract:

  Cosmetic update to remove underlining from revised (compared with ITU-T) text.

• Status: Published
• Publication Date: 31-Dec-1999
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2000
• Due Date: 01-Jan-2000
• Completion Date: 01-Jan-2000
• Ref Project: ETSI EN 301 069-1 V1.2.3 (1998-08) - 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:2000 is the Slovenian adoption of ETSI EN 301 069-1 V1.2.3 for Integrated Services Digital Network (ISDN) signalling. It specifies the Application Transport Mechanism (APM) for the ISDN User Part (ISUP) in Signalling System No. 7 (SS7), including how application data is carried, segmented, reassembled and reported by signalling equipment.

What does SIST EN 301 069-1:2000 specify?

SIST EN 301 069-1:2000 specifies the protocol for transporting application information in ISUP. In practice, it tells implementers how APM behaves when it is carried in call-control signalling, how errors are reported, and how the application context is identified.

The document is organized as a protocol specification with supporting references, abbreviations, message-flow clauses, segmentation and reassembly procedures, congestion handling, context handling, and a definition of Application Transport Notification Information. It also includes a temporary normative annex with modifications to ITU-T Recommendation Q.765 and an informative appendix with example segmentation diagrams.

Part of the document	What it covers
Temporary Annex A	Modifications to ITU-T Recommendation Q.765
Appendix I	Example sequence diagrams of APM segmentation

What are the key requirements of SIST EN 301 069-1:2000?

Transported information and context handling

SIST EN 301 069-1:2000 requires APM to carry application data together with a context identifier. Clause 14 defines Application Transport Notification Information as information carried in the Encapsulated Application Information field of the Application Transport Parameter (APP) when the context identifier is set to UCEH ASE. In practice, the context tells the receiving side which application user or handling path the data belongs to.

Message and primitive mapping

SIST EN 301 069-1:2000 maps APM primitives between the ISUP ASE and the SACF. Clause 8.3 states that received-message mapping is the reverse of the outgoing-message mapping, and clause 9.1 defines the primitive flow between the two functional blocks. For implementers, this means the send and receive paths must be wired consistently in both directions.

Segmentation and reassembly

SIST EN 301 069-1:2000 allows segmentation only when all parameters cannot fit in IAM, ACM, CPG, CON, ANM or PRI, including SGM where simple segmentation is used because the 272 octet MTP limit would be exceeded. Clause 10.2.4 requires the initial segment for each context to be transported first, and it may be zero length. In practice, this means the first message must establish the association before later segments are accepted.

Call-control ordering

SIST EN 301 069-1:2000 ties segmented application data to the first call-control message used for transport. The first segment may be carried in IAM, ACM, CPG, CON, ANM or PRI when available, and only one call-control message can be associated with segmented application data. Clause 10.2.4 also requires the sender to wait for an empty APP in the first backward message before sending later segments when the first segment is sent in IAM.

Error, acknowledgement and congestion handling

SIST EN 301 069-1:2000 sets behaviour when expected acknowledgement is not received and when congestion or remote errors occur. The note in 7.2.1 says that if no acknowledgement arrives before certain call-progress or answer messages, and the application association was essential, the call is released and maintenance is notified. Clause 11.2.2 and clauses 13.1.2 and 13.4.1 describe signalling congestion and remote or local error handling using primitives such as APM_Error, UCEH_Release and Remote_Status.

Notification content

SIST EN 301 069-1:2000 defines how notification information is structured. Clause 14 shows that the notification carries an APM-user Context Identifier and a Reason, with values used for unidentified context and reassembly error handling. In practice, this is the information returned to the application user when transport or context processing fails.

What terms does SIST EN 301 069-1:2000 define?

• Application Transport Mechanism (APM) - The ISUP mechanism used to transport application information across the signalling network.
• ISDN User Part (ISUP) - The SS7 signalling part that carries call-control and related information for ISDN.
• Signalling System No. 7 (SS7) - The signalling system used to exchange control information between network nodes.
• Application Transport Parameter (APP) - The ISUP parameter that carries application transport information and notification data.
• Initial Address Message (IAM) - The first call-control message used to start call setup and, when applicable, carry the first segment.
• Address Complete Message (ACM) - A backward call-control message used in the signalling flow and mentioned in segmentation and acknowledgement rules.
• Call Progress Message (CPG) - A call-progress message used in the signalling flow and referenced for acknowledgement and segmentation behaviour.

Who uses SIST EN 301 069-1:2000?

SIST EN 301 069-1:2000 is used by signalling protocol engineers, switch and network equipment designers, and test teams working on ISDN/SS7 interworking. It matters to implementers who need APM to carry application data through ISUP messages, especially where segmentation, reassembly, context handling and error reporting must match between vendors.

Quality managers and conformance testers use it to check message mapping, primitive behaviour and the handling of special cases such as congestion and unidentified context. Network operators and integrators use it when validating interoperability between nodes that exchange APM traffic.

Which standards are used with SIST EN 301 069-1:2000?

• EN 300 356-1 - Provides the ISUP basic services reference used by this document, and replaces the ITU-T Q.761 to Q.764 references inside the text.
• ITU-T Recommendation Q.1400 - Gives the architecture framework for signalling and OA&M protocols using OSI concepts.
• Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification - Companion part for declaring implementation conformance.
• Part 3: Test Suite Structure and Test Purposes (TSS&TP) - Companion part for defining conformance tests and their purposes.
• Part 4: Abstract Test Suite (ATS) - Companion part for formal test cases.

What does the SIST EN 301 069-1:2000 document contain?

The document contains the protocol specification for APM, including the message and primitive mappings, the segmentation and reassembly procedures, congestion handling and error handling rules. It also contains the definition and structure of Application Transport Notification Information in clause 14.

A temporary normative annex lists the agreed modifications to ITU-T Recommendation Q.765. An informative appendix gives example sequence diagrams for APM segmentation, which helps readers understand the order of messages during transport and reassembly.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija št. 7 – ISDN-uporabniški del (ISUP) - Aplikacijski prenosni mehanizem (APM) - 1. del: Specifikacija protokolaIntegrated 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]33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 069-1 V1.2.33SIST EN 301 069-1:en01-QRYHPEHU-3SIST EN 301 069-1:SLOVENSKI
STANDARD
EN 301 069-1 V1.2.3 (1998-08)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]SIST EN 301 069-1:2000

ETSIEN 301 069-1 V1.2.3 (1998-08)2ReferenceREN/SPS-01042-1 (9wc90iq0.PDF)KeywordsISDN, SS7, ISUP, NNI, protocolETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail]://www.etsi.frhttp://www.etsi.orgCopyright NotificationNo 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.SIST EN 301 069-1:2000

ETSIEN 301 069-1 V1.2.3 (1998-08)3Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI 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 guaranteecan 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.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document is part 1 of a multi-part EN covering Integrated Services Digital Network (ISDN); SignallingSystem 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 datesDate of adoption of this EN: 17 April 1998Date of latest announcement of this EN (doa): 31 July 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e): 31 January 1999Date of withdrawal of any conflicting National Standard (dow): 31 January 1999Endorsement noticeThe 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 tohighlight detailed modifications where necessary.NOTE 2:ITU-T Recommendation Q.765 had
not yet been adopted by ITU-T prior to Publication ofthe present document. This endorsement is based upon the draft of that Recommendation whichaccompanies the present document, located in an archive file named 9wc90iq0.zip.SIST EN 301 069-1:2000

ETSIEN 301 069-1 V1.2.3 (1998-08)4Clause 2, ReferencesReplace this clause by:Normative referencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)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 samenumber.[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-TRecommendations Q.761 to Q.764 (1997), modified]".[2]ITU-T Recommendation Q.1400 (1993): "Architecture framework for the development ofsignalling and OA&M protocols using OSI concepts".Throughout the text of ITU-T Recommendation Q.765Replace references as shown below.Reference in ITU-T Recommendation Q.765Modified referenceITU-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 TEN 300 356-1 [1] Annex T (temporary), Changes to ITU-T Recommendations Q.761, Q.762, Q.763 andQ.764Not supported, see EN 300 356-1 [1].Appendix I, Example sequence diagrams of APM segmentationAppendix I has the status of an informative annex.SIST EN 301 069-1:2000

ETSIEN 301 069-1 V1.2.3 (1998-08)5Temporary 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 themeeting which addressed the national comments received following PE9748. The complete text of this annex will becontributed to the ITU-T resolution 1 procedure for approval of Q.765. Once this procedure is finished, it is intendedthat 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 anycompatibility problems in the case of mismatch between Q.765 and the present docuement are to become a part of themain body of this EN. The modifications that do not become part of Q.765 and may result in an incompatibility when aQ.765 based service and an EN 301 069-1 based service interwork will be removed from this EN. Each of the proposalsbelow 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, AbbreviationskeepModify in the following way: ACM
Address Complete Message APM-userApplication Transport Mechanism User Application CPG
Call Progress Message IAM
Initial Address Message PRI
Pre-Release Information MessageSubclause 7.2.1, IntroductionkeepAdd 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", ora CPG indicating "alerting", oran ANM or CONwith no APP (for the appropriate context) then if the application association for the call was essential, thecall shall be release and the maintenance function shall be notified.Subclause 8.3, Information flows related to messages received by the nodekeepModify 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 isthe reverse to that described in the tables for outgoing messages sent by the node in subclause 6.28.2.Subclause 9.1, Table 14/Q.765 - Primitives between ISUP ASE and SACFkeepReplace note of table 14 by:NOTE:Primitive flow from SACF to ISUP ASE - ¬Primitive flow from ISUP ASE to SACF - ®SIST EN 301 069-1:2000

ETSIEN 301 069-1 V1.2.3 (1998-08)6Subclause 10.2.1, Normal Procedures - SendingkeepReplace 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 limitwould be exceeded.Subclause 10.2.4, SegmentationkeepModify 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 zerolength. The first segment message may be an ISUP call control IAM, ACM, CPG, CON, ANM or PRI message (whenavailable) and this procedure ensures that the reassembling node is able to associate the APM information with the callcontrol first ISUP message. A maximum of one cal
...

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija št. 7 – ISDN-uporabniški del (ISUP) - Aplikacijski prenosni mehanizem (APM) - 1. del: Specifikacija protokolaIntegrated 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]33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 069-1 Version 1.2.3SIST EN 301 069-1:2000en01-januar-2000SIST EN 301 069-1:2000SLOVENSKI
STANDARD
EN 301 069-1 V1.2.3 (1998-08)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]SIST EN 301 069-1:2000

ETSIEN 301 069-1 V1.2.3 (1998-08)2ReferenceREN/SPS-01042-1 (9wc90iq0.PDF)KeywordsISDN, SS7, ISUP, NNI, protocolETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail]://www.etsi.frhttp://www.etsi.orgCopyright NotificationNo 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.SIST EN 301 069-1:2000

ETSIEN 301 069-1 V1.2.3 (1998-08)3Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI 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 guaranteecan 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.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document is part 1 of a multi-part EN covering Integrated Services Digital Network (ISDN); SignallingSystem 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 datesDate of adoption of this EN: 17 April 1998Date of latest announcement of this EN (doa): 31 July 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e): 31 January 1999Date of withdrawal of any conflicting National Standard (dow): 31 January 1999Endorsement noticeThe 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 tohighlight detailed modifications where necessary.NOTE 2:ITU-T Recommendation Q.765 had
not yet been adopted by ITU-T prior to Publication ofthe present document. This endorsement is based upon the draft of that Recommendation whichaccompanies the present document, located in an archive file named 9wc90iq0.zip.SIST EN 301 069-1:2000

ETSIEN 301 069-1 V1.2.3 (1998-08)4Clause 2, ReferencesReplace this clause by:Normative referencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)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 samenumber.[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-TRecommendations Q.761 to Q.764 (1997), modified]".[2]ITU-T Recommendation Q.1400 (1993): "Architecture framework for the development ofsignalling and OA&M protocols using OSI concepts".Throughout the text of ITU-T Recommendation Q.765Replace references as shown below.Reference in ITU-T Recommendation Q.765Modified referenceITU-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 TEN 300 356-1 [1] Annex T (temporary), Changes to ITU-T Recommendations Q.761, Q.762, Q.763 andQ.764Not supported, see EN 300 356-1 [1].Appendix I, Example sequence diagrams of APM segmentationAppendix I has the status of an informative annex.SIST EN 301 069-1:2000

ETSIEN 301 069-1 V1.2.3 (1998-08)5Temporary 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 themeeting which addressed the national comments received following PE9748. The complete text of this annex will becontributed to the ITU-T resolution 1 procedure for approval of Q.765. Once this procedure is finished, it is intendedthat 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 anycompatibility problems in the case of mismatch between Q.765 and the present docuement are to become a part of themain body of this EN. The modifications that do not become part of Q.765 and may result in an incompatibility when aQ.765 based service and an EN 301 069-1 based service interwork will be removed from this EN. Each of the proposalsbelow 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, AbbreviationskeepModify in the following way: ACM
Address Complete Message APM-userApplication Transport Mechanism User Application CPG
Call Progress Message IAM
Initial Address Message PRI
Pre-Release Information MessageSubclause 7.2.1, IntroductionkeepAdd 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", ora CPG indicating "alerting", oran ANM or CONwith no APP (for the appropriate context) then if the application association for the call was essential, thecall shall be release and the maintenance function shall be notified.Subclause 8.3, Information flows related to messages received by the nodekeepModify 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 isthe reverse to that described in the tables for outgoing messages sent by the node in subclause 6.28.2.Subclause 9.1, Table 14/Q.765 - Primitives between ISUP ASE and SACFkeepReplace note of table 14 by:NOTE:Primitive flow from SACF to ISUP ASE - ¬Primitive flow from ISUP ASE to SACF - ®SIST EN 301 069-1:2000

ETSIEN 301 069-1 V1.2.3 (1998-08)6Subclause 10.2.1, Normal Procedures - SendingkeepReplace 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 limitwould be exceeded.Subclause 10.2.4, SegmentationkeepModify 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 zerolength. The first segment message may be an ISUP call control IAM, ACM, CPG, CON, ANM or PRI message (whenavailable) and this procedure ensures that the reassembling node is able to associate the APM information with the callcontrol first ISUP message. A maximum of
...