>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.
+
+The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.
+
+IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire.
+
+This document is a member of a TS-family consisting of 3G TS 32.150, 3G TS 32.151, 3G TS 32.152.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 152 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 152 | 8.0.0 | Published | 2009-01-20 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532152v800 |
+| ATIS | ATIS.3GPP.32.152V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.152(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT_3G-32.152(R8-8.0.0) |
+| TTC | TS-3GA-32.152(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32152rel8v800.pdf |
+
+### 10.10.15 TS 32.154 Telecommunication management; Backward and forward compatibility (BFC); Concept and definitions
+
+This document gives recommendations to develop future IRP specifications in a backward compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.
+
+The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.
+
+Clause 4 specifies the Recommendations and clause 5 describes the system context where the Recommendations are applicable.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 154 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 154 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532154v800 |
+| ATIS | ATIS.3GPP.32.154V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.154(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT_3G-32.154(R8-8.0.0) |
+| TTC | TS-3GA-32.154(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32154rel8v800.pdf |
+
+### 10.10.16 TS 32.155 Telecommunication management; Requirements template
+
+The document contains the template to be used for the production of all the requirements of TSs for the 3GPP Telecommunication management.
+
+This template is mainly based on the requirements template (mainly Annex A) in [ITU-T M.3020].
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 155 | 8.2.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532155v820 |
+| ATIS | ATIS.3GPP.32.155V820-2009 | 8.2.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.155(R8-8.2.0) | 8.2.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.155(R8-8.2.0) |
+| TTC | TS-3GA-32.155(Rel8)v8.2.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32155rel8v820.pdf |
+
+#### 10.10.17 TS 32.171 Subscription management (SuM) network resource model (NRM) integration reference point (IRP): Requirements
+
+The document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102, 3G TS 32.140, 3G TS 32.141, the requirements for the present SuM NRM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 171 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 171 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532171v800 |
+| ATIS | ATIS.3GPP.32.171V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.171(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.171(R8-8.0.0) |
+| TTC | TS-3GA-32.171(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32171rel8v800.pdf |
+
+#### 10.10.18 TS 32.172 Telecommunication management; Subscription management (SuM) network resource model (NRM) integration reference point (IRP): Information service (IS)
+
+The interface Itf-N, defined in 3G TS 32.102, is built up by a number of integration reference points (IRPs) and a related name convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in 3G TS 32.101 and 3G TS 32.102.
+
+This document defines the network resources model (NRM) for the SuM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 172 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 172 | 8.0.0 | Published | 2009-02-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532172v800 |
+| ATIS | ATIS.3GPP.32.172V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+
+| | Document No. | Version | Status | Issued date | Location |
+|-----|---------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| TTA | TTAT.3G-32.172(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.172(R8-8.0.0) |
+| TTC | TS-3GA-32.172(Rel8)v8.0.0 | 1 | TTC Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32172rel8v800.pdf |
+
+#### 10.10.19 TS 32.175 Telecommunication management; Subscription management (SuM) network resource model (NRM) integration reference point (IRP): eXtensible markup language (XML) definition
+
+The purpose of this *Subscription Management (SuM) Network Resource Model IRP XML definition* is to define the mapping of the IRP information model (see TS 32.172) to the protocol specific details necessary for implementation of this IRP in an XML environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 175 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 175 | 8.0.0 | Published | 2009-02-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532175v800 |
+| ATIS | ATIS.3GPP.32.175 V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.175(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.175(R8-8.0.0) |
+| TTC | TS-3GA-32.175(Rel8)v8.0.0 | 1 | TTC Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32175rel8v800.pdf |
+
+#### 10.10.20 TS 32.240 Telecommunication management; Charging management; Charging architecture and principles
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in the present document, which thus provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain/subsystem/service (offline charging);
+- the content of real-time charging events per domain/subsystem/service (online charging);
+- the functionality of online and offline charging for those domains/subsystems/services;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The purposes of the present document are:
+
+- to lay down common principles of charging in the network; and
+- to specify a logical common charging architecture that applies to all 3GPP domains, subsystems and services.
+
+A set of domain/subsystem/service-specific TSs covers the bearer (CS, PS, WLAN domains), subsystem (IMS) and service (MMS, LCS, etc.) levels, respectively, in the 3G TS 32.25x, 32.26x and 32.27x number range. These 3G TSs describe the mapping of the common architecture specified in the present document onto the specific domain/subsystem/service and the scenarios and
+
+information for online and offline charging that are specific to the domain/subsystem/service. They are commonly referred to as the "middle tier (charging) TSs".
+
+A set of 3G TSs in the 32.29x range covers common aspects such as CDR parameter and syntax descriptions, online and offline charging applications, and the charging interactions within the network (CDR transfer) as well as between the network and the billing domain (CDR file transfer).
+
+The complete document structure for these 3G TSs is outlined in Figure 10.10.20-1.
+
+
+
+```
+graph TD; 32.240[32.240 Charging Architecture and Principles] --> 32.250[32.250 CS-domain Charging]; 32.240 --> 32.251[32.251 PS-domain Charging]; 32.240 --> 32.252[32.252 WLAN Charging]; 32.240 --> 32.260[32.260 IM Subsystem Charging]; 32.250 --> 32.270[32.270 MMS Charging]; 32.250 --> 32.271[32.271 LCS Charging]; 32.250 --> 32.27x[32.27x tbd.]; 32.251 --> 32.295[32.295 Charging Data Record (CDR) transfer]; 32.251 --> 32.296[32.296 Online Charging System (OCS) applications and interfaces]; 32.251 --> 32.297[32.297 Charging Data Record (CDR) file format and transfer]; 32.251 --> 32.298[32.298 Charging Data Record (CDR) parameter description]; 32.251 --> 32.299[32.299 Diameter Charging Application];
+```
+
+A hierarchical tree diagram showing the structure of charging documents. The root node is '32.240 Charging Architecture and Principles'. It branches into four nodes: '32.250 CS-domain Charging', '32.251 PS-domain Charging', '32.252 WLAN Charging', and '32.260 IM Subsystem Charging'. The '32.250' node branches into '32.270 MMS Charging', '32.271 LCS Charging', and '32.27x tbd.'. The '32.251' node branches into '32.295 Charging Data Record (CDR) transfer', '32.296 Online Charging System (OCS) applications and interfaces', '32.297 Charging Data Record (CDR) file format and transfer', '32.298 Charging Data Record (CDR) parameter description', and '32.299 Diameter Charging Application'.
+
+Q.1741.6(09)\_F10.10.20-1
+
+**Figure 10.10.20-1 – Charging documents structure**
+
+All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 3GPP TR 21.905. Those that are common across charging management in GSM/UMTS domains, services or subsystems are provided in the present document (umbrella TS), and are copied into clause 3 of the other TSs depicted in the figure above, for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|-------------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132
240 | 8.5.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 240 | 8.5.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532240v850 |
+| ATIS | ATIS.3GPP.32.240
V850-2009 | 8.5.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-
32.240(R8-8.5.0) | 8.5.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.240(R8-8.5.0) |
+| TTC | TS-3GA-
32.240(Rel8)v8.5.0 | 1 | TTC Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32240rel8v850.pdf |
+
+### 10.10.21 TS 32.250 Telecommunication management; Charging management; Circuit-switched (CS) domain charging
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3G TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in 3G TS 32.240.
+
+The document specifies the offline charging description for the 3GPP circuit-switched domain, based on the functional descriptions of the 3GPP bearer-, tele- and supplementary services in 3G TS 22.002, 3GPP TS 22.003 and 3G TS 22.004, respectively. This charging description includes the offline charging architecture and scenarios specific to the CS domain, as well as the mapping of the common charging architecture specified in 3G TS 32.240 onto the CS domain. It further specifies the structure and content of the CDRs for offline charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3G TS 32.298.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+
+Note that online charging for the CS domain is solely based on CAMEL (3G TS 23.078 and 3G TS 29.078) and therefore outside the scope of the 32-series charging specifications.
+
+All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3G TSs, are defined in 3G TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document 3G TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 250 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 250 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532250v800 |
+| ATIS | ATIS.3GPP.32.250V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.250(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.250(R8-8.0.0) |
+| TTC | TS-3GA-32.250(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32250rel8v800.pdf |
+
+#### **10.10.22 TS 32.251 Telecommunication management; Charging management; Packet-switched (PS) domain charging**
+
+This document is part of a series of documents specifying charging functionality and charging management in GSM/UMTS networks.
+
+The document specifies the offline and online charging description for the packet-switched (PS) domain (i.e., GPRS), based on the functional Stage 2 description of GPRS in 3G TS 23.060. This charging description includes the offline and online charging architecture and scenarios specific to the PS domain, as well as the mapping of the common 3GPP charging architecture specified in 3G TS 32.240 onto the PS domain. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for the CDRs are specified in 3G TS 32.298.
+- A transaction based mechanism for the transfer of CDRs within the network is specified in 3G TS 32.295.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+- The 3GPP Diameter application that is used for PS domain offline and online charging is specified in 3G TS 32.299.
+
+Note that a CAMEL-based prepaid function and protocol is also specified for the PS domain (3G TS 23.078 and 3G TS 29.078). CAMEL entities and functions are outside the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 251 | 8.5.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 251 | 8.4.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532251v840 |
+| ATIS | ATIS.3GPP.32.251V840-2009 | 8.4.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.251(R8-8.4.0) | 8.4.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT.3G-32.251(R8-8.4.0) |
+| TTC | TS-3GA-32.251(Rel8)v8.4.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32251rel8v840.pdf |
+
+### 10.10.23 TS 32.252 Telecommunication management; Charging management; Wireless local area network (WLAN) charging
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management documents that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+The document specifies the offline and online charging description for the 3GPP interworked wireless LAN (WLAN), based on the functional stage 2 description of 3GPP WLAN interworking in TS 23.234. This charging description includes the offline and online charging architecture and scenarios specific to the 3GPP interworked WLAN, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto the 3GPP interworked WLAN. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297.
+- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 252 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 252 | 8.0.0 | Published | 2009-01-20 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532252v800 |
+| ATIS | ATIS.3GPP.32.252V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.252(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.252(R8-8.0.0) |
+| TTC | TS-3GA-32.252(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32252rel8v800.pdf |
+
+#### **10.10.24 TS 32.260 Telecommunication management; Charging management; IP multimedia subsystem (IMS) charging**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The document specifies the offline and online charging description for the IP multimedia subsystem (IMS), based on the functional descriptions of the IMS in 3G TS 23.228. This charging description includes the offline and online charging architecture and scenarios specific to IMS, as well as the mapping of common 3GPP charging architecture specified in 3G TS 32.240 onto IMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. This document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3G TS 32.298.
+- A transaction-based mechanism for the transfer of CDRs within the network is specified in 3G TS 32.295.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+- The 3GPP Diameter application that is used for IMS offline and online charging is specified in 3G TS 32.299.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 260 | 8.6.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 260 | 8.6.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532260v860 |
+| ATIS | ATIS.3GPP.32.260V860-2009 | 8.6.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.260(R8-8.6.0) | 8.6.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.260(R8-8.6.0) |
+| TTC | TS-3GA-32.260(Rel8)v8.6.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32260rel8v860.pdf |
+
+### **10.10.25 TS 32.270 Telecommunication management; Charging management; Multimedia messaging service (MMS) charging**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The complete document structure for these TSs is defined in 3G TS 32.240.
+
+This document specifies the offline and online charging description for MMS charging, based on the functional Stage 2 descriptions of the MMS in 3G TS 23.140. This charging description includes the offline and online charging architecture and scenarios specific to the MMS, as well as the mapping of the common 3GPP charging architecture specified in 3G TS 32.240 onto MMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3G TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3G TS 32.298.
+- A transaction-based mechanism for the transfer of CDRs within the network is specified in 3G TS 32.295.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3G TS 32.297.
+- The 3GPP Diameter application that is used for MMS online charging is specified in 3G TS 32.299.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 270 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 270 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532270v800 |
+| ATIS | ATIS.3GPP.32.270V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.270(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.270(R8-8.0.0) |
+| TTC | TS-3GA-32.270(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32270rel8v800.pdf |
+
+#### **10.10.26 TS 32.271 Telecommunication management; Charging management; Location services (LCS) charging**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The document specifies the LCS offline and online charging description for the LCS domain, based on the functional Stage 2 description of the LCS in 3G TS 23.071. This charging description includes the offline and online charging architecture and scenarios specific to the LCS, as well as the mapping of the common 3GPP architecture specified in 3G TS 32.240 onto the LCS domain. It further specifies the structure and content of the CDRs for offline charging and the charging events for online charging.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 271 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 271 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532271v800 |
+| ATIS | ATIS.3GPP.32.271V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.271(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.271(R8-8.0.0) |
+| TTC | TS-3GA-32.271(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32271rel8v800.pdf |
+
+#### **10.10.27 TS 32.272 Telecommunication management; Charging management; Push-to-talk over cellular (PoC) charging**
+
+The document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+This document specifies the offline and online charging description for the "Push-to-Talk over Cellular" (PoC) service, based on the functional description of the PoC service in TR 23.979 "3GPP enablers for OMA PoC Services", in OMA-AD-POC "Push to talk over Cellular (PoC) – Architecture", in OMA-CP-POC "OMA PoC Control Plane" and in OMA-UP-POC: "OMA POC User Plane", respectively. This charging description includes the offline and online charging architecture and scenarios specific to PoC, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto the PoC service. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297.
+- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 272 | 8.2.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 272 | 8.2.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532272v820 |
+| ATIS | ATIS.3GPP.32.272V820-2009 | 8.2.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.272(R8-8.2.0) | 8.2.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT.3G-32.272(R8-8.2.0) |
+| TTC | TS-3GA-32.272(Rel8)v8.2.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32272rel8v820.pdf |
+
+## 10.10.28 TS 32.273 Telecommunication management; Charging management; Multimedia broadcast and multicast service (MBMS) charging
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging messages per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+This document specifies the offline and online charging description for the multimedia broadcast and multicast service (MBMS), based on the functional stage 2 description in TS 23.246. This charging description includes the offline and online charging architecture and scenarios specific to MBMS, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto MBMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in TS 32.240.
+- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298.
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in TS 32.297.
+- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in TS 32.299.
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 273 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 273 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532273v800 |
+| ATIS | ATIS.3GPP.32.273V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.273(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT.3G-32.273(R8-8.0.0) |
+| TTC | TS-3GA-32.273(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32273rel8v800.pdf |
+
+### **10.10.29 TS 32.274 Telecommunication management; Charging management; Short message service (SMS) charging**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240, which provides an umbrella for other charging management TSs that specify:
+
+- the content of the CDRs per domain/subsystem/service (offline charging);
+- the content of real-time charging messages per domain/subsystem/service (online charging);
+- the functionality of online and offline charging for those domains/subsystems/services;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in 3GPP TS 32.240.
+
+This document specifies the offline and online charging description for the short message service (SMS), based on the functional description in 3GPP TS 23.040 and on the SMS over IP in 3GPP TS 23.204. The document does not replace the existing offline SMS charging functionality and therefore is in addition to that defined in 3GPP TS 32.250 and 3GPP TS 32.251. This charging description includes the offline and online charging architecture and scenarios specific to SMS, as well as the mapping of the common 3GPP charging architecture specified in 3GPP TS 32.240 onto SMS. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. This document is related to other 3GPP charging TSs as follows:
+
+- The common 3GPP charging architecture is specified in 3GPP TS 32.240;
+- The parameters, abstract syntax and encoding rules for the CDRs are specified in 3GPP TS 32.298;
+- A transaction-based mechanism for the transfer of CDRs within the network is specified in TS 32.295;
+- The file-based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device) is specified in 3GPP TS 32.297;
+- The 3GPP Diameter application that is used for SMS offline and online charging is specified in 3GPP TS 32.299.
+
+Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 274 | 8.4.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532274v840 |
+| ATIS | ATIS.3GPP.32.274V 840-2009 | 8.4.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.274(R8-8.4.0) | 8.4.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.274(R8-8.4.0) |
+| TTC | TS-3GA-32.274(Rel8)v8.4.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32274rel8v840.pdf |
+
+### **10.10.30 TS 32.295 Telecommunication management; Charging management; Charging data record (CDR) transfer**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The document specifies the transaction-based mechanism for the near real-time transfer of CDRs within the network.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 295 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 295 | 8.0.0 | Published | 2009-01-20 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532295v800 |
+| ATIS | ATIS.3GPP.32.295V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.295(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.295(R8-8.0.0) |
+| TTC | TS-3GA-32.295(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32295rel8v800.pdf |
+
+### **10.10.31 TS 32.296 Telecommunication management; Charging management; Online charging system (OCS): Applications and interfaces**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+The document covers all internal aspects of the online charging system (OCS). The document contains the architecture and functions of the OCS logical components and thereby derives the functionality of the OCS interfaces. A detailed specification of interfaces between the logical OCS components is also included. The functionality of the OCS, as described in the present document, applies to all charging domains (bearer, session and service).
+
+The interfaces connecting to the OCS (e.g., Ro, CAP) are out of the scope of the present document.
+
+NOTE – In the current release, the present document is limited to the interface between the charging function and the rating function, namely Re.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 296 | 8.3.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 296 | 8.2.1 | Published | 2009-01-15 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532296v821 |
+| ATIS | ATIS.3GPP.32.296V821-2009 | 8.2.1 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.296(R8-8.2.1) | 8.2.1 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.296(R8-8.2.1) |
+| TTC | TS-3GA-32.296(Rel8)v8.2.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32296rel8v820.pdf |
+
+### **10.10.32 TS 32.297 Telecommunication management; Charging management; Charging data record (CDR) file format and transfer**
+
+This document is part of a series of documents specifying charging functionality and charging management in GSM/UMTS networks.
+
+The document specifies the mechanisms used to transfer the CDRs from the network to the operator's billing domain (e.g., the billing system or a mediation device). This includes the file transfer procedures and the layout of the CDR files, as well as file meta information and the encoding of the CDRs within the files.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 297 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 297 | 8.1.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532297v810 |
+| ATIS | ATIS.3GPP.32.297V810-2009 | 8.1.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.297(R8-8.1.0) | 8.1.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT.3G-32.297(R8-8.1.0) |
+| TTC | TS-3GA-32.297(Rel8)v8.1.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32297rel8v810.pdf |
+
+### **10.10.33 TS 32.298 Telecommunication management; Charging management; Charging data record (CDR) parameter description**
+
+This document is part of a series of documents that specify charging functionality and charging management in GSM and UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in document TS 32.240, which provides an umbrella for other charging management documents that specify:
+
+- the content of the CDRs per domain and subsystem (offline charging);
+- the content of real-time charging events per domain/subsystem (online charging);
+- the functionality of online and offline charging for those domains and subsystems;
+- the interfaces that are used in the charging framework to transfer the charging information (i.e., CDRs or charging events).
+
+The complete document structure for these TSs is defined in TS 32.240.
+
+This document specifies the CDR parameters, the abstract syntax and encoding rules for all the CDR types that are defined in the charging management TSs described above. Therefore, it is only applicable to offline charging. The mechanisms used to transfer the CDRs from the generating node to the operator's billing domain (e.g., the billing system or a mediation device) are specified in TS 32.297. Further details with respect to the operator's billing domain for offline charging are out of scope of 3GPP standardization.
+
+Note that a generic Diameter application for online charging in 3GPP networks is specified in TS 32.299. Furthermore, 3GPP TSs are being created to standardize some technical aspects of the operator's billing domain for online charging, i.e., the online charging system (OCS).
+
+All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, [ETSI TR 121 905]. Those that are common across charging management in UMTS domains or subsystems are provided in the umbrella document
+
+TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
+
+Furthermore, requirements that govern the charging work are specified in TS 22.115.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 298 | 8.4.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 298 | 8.3.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532298v830 |
+| ATIS | ATIS.3GPP.32.298V830-2009 | 8.3.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.298(R8-8.3.0) | 8.3.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.298(R8-8.3.0) |
+| TTC | TS-3GA-32.298(Rel8)v8.3.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32298rel8v830.pdf |
+
+#### 10.10.34 TS 32.299 Telecommunication management; Charging management; Diameter charging applications
+
+The document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks.
+
+This document specifies in detail the Diameter-based offline and online charging applications for 3GPP networks. It includes all charging parameters, scenarios and message flows.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 299 | 8.6.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 299 | 8.5.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532299v850 |
+| ATIS | ATIS.3GPP.32.299V850-2009 | 8.5.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.299(R8-8.5.0) | 8.5.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.299(R8-8.5.0) |
+| TTC | TS-3GA-32.299(Rel8)v8.5.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32299rel8v850.pdf |
+
+#### 10.10.35 TS 32.300 Telecommunication management; Configuration management (CM); Name convention for managed objects
+
+A more detailed background and introduction of the IRP concept is given in TS 32.101 and TS 32.102.
+
+To perform network management tasks, cooperating applications require identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The document recommends one name convention for network resources under management in the IRP context.
+
+To facilitate integration of network management information obtained via multiple IRPs of different technologies such as CMIP and CORBA, identical network resource name semantics shall be conveyed in all IRPs. The document specifies one such name convention.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 300 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532300v800 |
+| ATIS | ATIS.3GPP.32.300V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.300(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.300(R8-8.0.0) |
+| TTC | TS-3GA-32.300(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32300rel8v800.pdf |
+
+### 10.10.36 TS 32.301 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP); Requirements
+
+The purpose of notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This document is the "Requirements" of notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirements that shall be fulfilled on Itf-N.
+
+How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 301 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 301 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532301v800 |
+| ATIS | ATIS.3GPP.32.301V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.301(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.301(R8-8.0.0) |
+| TTC | TS-3GA-32.301(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32301rel8v800.pdf |
+
+### 10.10.37 TS 32.302 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP); Information service (IS)
+
+The purpose of notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This document is the "Information Service" of notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by the management system's client, and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the "notificationHeader".
+
+An IRP Agent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP: Information service 3G TS 32.111-2) and others. This IRP IS defines a mechanism that IRP Manager can use to determine the categories of notifications supported by an IRP Agent. It also defines a mechanism (subscribe and unsubscribe operations) that IRP Manager can use to specify the categories of notifications IRP Agent should emit to IRP Manager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRP Manager can use to check which categories of notifications it has subscribed to. IRP Manager can set and change the filter criteria applicable during the life-cycle of a subscription. IRP Manager can also exercise flow-control on IRP Agent's emission of notifications (suspendSubscription and resumeSubscription operations).
+
+Using different managerReference, an IRP Manager can subscribe several times. It will result in multiple subscriptions. As far as IRP Agent is concerned, notifications are sent to multiple "places".
+
+Using the same managerReference, an IRP Manager can subscribe several times specifying different categories of notifications.
+
+This IRP IS does not specify information that is carried in some but not all the notifications. That kind of information is specified in other IRP ISs involved. For example, perceivedSeverity is a piece of information specific for notifications carrying alarm information. This information is not defined in this document but in Alarm IRP: Information service 3G TS 32.111-2.
+
+How IRP Manager discovers the IRP Agent's address or reference (so that IRP Manager can invoke an operation) is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 302 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 302 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532302v800 |
+| ATIS | ATIS.3GPP.32.302V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.302(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.302(R8-8.0.0) |
+| TTC | TS-3GA-32.302(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32302rel8v800.pdf |
+
+### **10.10.38 TS 32.303 Telecommunication management; Configuration management (CM); notification integration reference point (IRP); Common object request broker architecture (CORBA) solution set (SS)**
+
+The document specifies the common object request broker architecture (CORBA) solution set (SS) for the IRP whose semantics is specified in notification IRP: Information service 3G TS 32.302.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 303 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 303 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532303v800 |
+| ATIS | ATIS.3GPP.32.303V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.303(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.303(R8-8.0.0) |
+| TTC | TS-3GA-32.303(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32303rel8v800.pdf |
+
+### **10.10.39 TS 32.305 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP): eXtensible markup language (XML) definition**
+
+This document specifies the XML Definitions for the notification integration reference point (notification IRP) as it applies to Itf-N, in accordance with notification IRP IS definitions.
+
+This XML definitions specification defines the notification IRP XML notification header format.
+
+This specification is related to TS 32.302.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 305 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 305 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532305v800 |
+| ATIS | ATIS.3GPP.32.305V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.305(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.305(R8-8.0.0) |
+| TTC | TS-3GA-32.305(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32305rel8v800.pdf |
+
+### **10.10.40 TS 32.307 Telecommunication management; Configuration management (CM); Notification integration reference point (IRP): SOAP solution set**
+
+This document specifies the SOAP solution set for the IRP whose semantics is specified in notification IRP: Information service (TS 32.302).
+
+This solution set specification is related to TS 32.302.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 307 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 307 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532307v800 |
+| ATIS | ATIS.3GPP.32.307V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.307(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.307(R8-8.0.0) |
+| TTC | TS-3GA-32.307(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32307rel8v800.pdf |
+
+#### 10.10.41 TS 32.311 Telecommunication management; Generic IRP management; Requirements
+
+The purpose of the document is to define a common service supported by all IRPs. This document is the "Requirements" part. It defines, for the purpose of supporting the common service, the requirements that shall be fulfilled by all IRPs supporting this service.
+
+With this common service supported by all IRPs, an IRPManager shall be able to retrieve the profile of operations and notifications supported by a given IRP that are by an IRPAgent. An IRPManager shall also be able to retrieve the different versions supported by an IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 311 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 311 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532311v800 |
+| ATIS | ATIS.3GPP.32.311V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.311(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.311(R8-8.0.0) |
+| TTC | TS-3GA-32.311(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32311rel8v800.pdf |
+
+#### 10.10.42 TS 32.312 Telecommunication management; Generic IRP management; Information service
+
+The purpose of the document is to define a common service supported by all IRPs. This document is the "Information Service" part. It defines, for the purpose of supporting the common service, the information observable and controlled by the management system's client, and it also specifies the semantics of the interactions used to carry this information.
+
+With this common service supported by all IRPs, an IRPManager can retrieve the profile of operations and notifications supported by a given IRP supported by an IRPAgent. An IRPManager can also retrieve the different versions supported by an IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 312 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 312 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532312v800 |
+| ATIS | ATIS.3GPP.32.312V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.312(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.312(R8-8.0.0) |
+| TTC | TS-3GA-32.312(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32312rel8v800.pdf |
+
+#### **10.10.43 TS 32.313 Telecommunication management; Generic integration reference point (IRP) management; Common object request broker architecture (CORBA) solution set (SS)**
+
+The document specifies the CORBA solution set (SS) for generic integration reference point (IRP) management whose capabilities are specified in "Generic integration reference (IRP) management: Information service (IS)" (3G TS 32.312).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 313 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 313 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532313v800 |
+| ATIS | ATIS.3GPP.32.313V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.313(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.313(R8-8.0.0) |
+| TTC | TS-3GA-32.313(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32313rel8v800.pdf |
+
+#### **10.10.44 TS 32.317 Telecommunication management; Generic integration reference point (IRP) management; SOAP solution set**
+
+The document specifies the SOAP solution set for generic IRP management whose capabilities are specified in Generic IRP management: Information service (TS 32.312).
+
+This solution set specification is related to TS 32.312.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 317 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 317 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532317v800 |
+| ATIS | ATIS.3GPP.32.317V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.317(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.317(R8-8.0.0) |
+| TTC | TS-3GA-32.317(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32317rel8v800.pdf |
+
+#### **10.10.45 TS 32.321 Telecommunication management; Test management integration reference point (IRP); Requirements**
+
+This document describes, in addition to the requirements defined in 3G TS 32.101 and 3G TS 32.102, the requirements for the test management IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 321 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 321 | 8.0.0 | Published | 2009-02-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532321v800 |
+| ATIS | ATIS.3GPP.32.321V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.321(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.321(R8-8.0.0) |
+| TTC | TS-3GA-32.321(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32321rel8v800.pdf |
+
+#### **10.10.46 TS 32.322 Telecommunication management; Test management integration reference point (IRP); Information service**
+
+This document defines the IS part of the test management IRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol-independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. This document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 322 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 322 | 8.0.0 | Published | 2009-01-20 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532322v800 |
+| ATIS | ATIS.3GPP.32.322V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.322(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.322(R8-8.0.0) |
+| TTC | TS-3GA-32.322(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32322rel8v800.pdf |
+
+#### **10.10.47 TS 32.323 Telecommunication management; Test management integration reference point (IRP); CORBA solution set**
+
+This document specifies the CORBA solution set (SS) for the IRP whose semantics is specified in test management IRP: Information service (IS) (3G TS 32.322).
+
+Clauses 1 to 3 provide background information. Clause 4 provides key architectural features supporting the SS. Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
+
+This solution set specification is related to 3G TS 32.322.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 323 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 323 | 8.0.0 | Published | 2009-01-20 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532323v800 |
+| ATIS | ATIS.3GPP.32.323V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.323(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.323(R8-8.0.0) |
+| TTC | TS-3GA-32.323(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32323rel8v800.pdf |
+
+#### **10.10.48 TS 32.325 Telecommunication management; Test management integration reference point (IRP); eXtensible markup language (XML) definitions**
+
+This document specifies the XML definitions for the test management IRP (TMIRP) as it applies to Itf-N, in accordance with TM IRP IS definitions in TS 32.322, as well as notification log IRP XML definitions in TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 325 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 325 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532325v800 |
+| ATIS | ATIS.3GPP.32.325V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.325(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.325(R8-8.0.0) |
+| TTC | TS-3GA-32.325(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32325rel8v800.pdf |
+
+#### 10.10.49 TS 32.331 Telecommunication management; Notification log integration reference point (IRP): Requirements
+
+The document describes the requirements and information model necessary for telecommunications management (TM). The TM principles and TM architecture are specified in 3G TS 32.101 and 3G TS 32.102, respectively.
+
+This document specifies the overall requirements for notification log management over Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 331 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 331 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532331v800 |
+| ATIS | ATIS.3GPP.32.331V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.331(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.331(R8-8.0.0) |
+| TTC | TS-3GA-32.331(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32331rel8v800.pdf |
+
+#### 10.10.50 TS 32.332 Telecommunication management; Notification log integration reference point (IRP): Information service (IS)
+
+The document specifies the information service for the notification log integration reference point (NL IRP) as it applies to Itf-N.
+
+This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 332 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 332 | 8.0.0 | Published | 2009-02-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532332v800 |
+| ATIS | ATIS.3GPP.32.332V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.332(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.332(R8-8.0.0) |
+| TTC | TS-3GA-32.332(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts3232rel8v800.pdf |
+
+#### **10.10.51 TS 32.333 Telecommunication management; Notification log (NL) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+This document specifies the CORBA solution set for the IRP whose semantics is specified in TS 32.332 notification log IRP: Information service.
+
+Clauses 1 to 3 provide background information. Clause 4 provides key architectural features supporting the SS.
+
+Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
+
+This solution set specification is related to TS 32.332.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 333 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 333 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532333v800 |
+| ATIS | ATIS.3GPP.32.333V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.333(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.333(R8-8.0.0) |
+| TTC | TS-3GA-32.333(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32333rel8v800.pdf |
+
+#### **10.10.52 TS 32.335 Telecommunication management; Notification log (NL) integration reference point (IRP): eXtensible markup language (XML) solution definitions**
+
+The document specifies the XML definitions for the notification log IRP as it applies to Itf-N, in accordance with the requirements in TS 32.331 and information service definitions in TS 32.332.
+
+This XML definitions specification defines the XML syntax of the NL IRP XML data file.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 335 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 335 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532335v800 |
+| ATIS | ATIS.3GPP.32.335V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.335(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.335(R8-8.0.0) |
+| TTC | TS-3GA-32.335(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32335rel8v800.pdf |
+
+#### **10.10.53 TS 32.341 Telecommunication management; File transfer (FT) integration reference point (IRP): Requirements**
+
+The document specifies the overall requirements for the file transfer integration reference point (FT IRP) as it applies to the Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 341 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+#### **10.10.54 TS 32.342 Telecommunication management; File transfer (FT) integration reference point (IRP): Information service (IS)**
+
+The document specifies the information service for the file transfer integration reference point (FileTransferIRP) as it applies to the Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 342 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+#### **10.10.55 TS 32.343 Telecommunication management; File transfer (FT) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The document specifies the common object request broker architecture (CORBA) solution set (SS) for the IRP whose semantics is specified in file transfer IRP: Information service TS 32.342.
+
+This solution set specification is related to TS 32.342.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 343 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+#### **10.10.56 TS 32.345 Telecommunication management; File transfer (FT) integration reference point (IRP); eXtensible markup language (XML) definitions**
+
+The document specifies the XML definitions for the file transfer IRP (FTIRP) as it applies to Itf-N, in accordance with FT IRP IS definitions in TS 32.342, as well as notification log IRP XML definitions in TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 345 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+#### **10.10.57 TS 32.351 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Requirements**
+
+The document describes the requirements of the communication surveillance IRP (CSIRP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 351 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 351 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532351v800 |
+| ATIS | ATIS.3GPP.32.351V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.351(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.351(R8-8.0.0) |
+| TTC | TS-3GA-32.351(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32351rel8v800.pdf |
+
+#### **10.10.58 TS 32.352 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Information service (IS)**
+
+The document defines the IS part of the CSIRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol-independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 352 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 352 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532352v800 |
+| ATIS | ATIS.3GPP.32.352V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.352(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.352(R8-8.0.0) |
+| TTC | TS-3GA-32.352(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32352rel8v800.pdf |
+
+**10.10.59 TS 32.353 Telecommunication management; Communication surveillance (CS) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The document specifies the CORBA solution set for the IRP whose semantics is specified in 3G TS 32.352 communication surveillance IRP: Information service.
+
+This solution set specification is related to TS 32.352.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 353 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 353 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532353v800 |
+| ATIS | ATIS.3GPP.32.353V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.353(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.353(R8-8.0.0) |
+| TTC | TS-3GA-32.353(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32353rel8v800.pdf |
+
+**10.10.60 TS 32.361 Telecommunication management; Entry point (EP) integration reference point (IRP): Requirements**
+
+The document describes the requirements of the EPIRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 361 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+### 10.10.61 TS 32.362 Telecommunication management; Entry point (EP) integration reference point (IRP): Information service (IS)
+
+The document defines the IS part of the EPIRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol-independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 362 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 362 | 8.0.0 | Published | 2009-02-17 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532362v800 |
+| ATIS | ATIS.3GPP.32.362V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.362(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.362(R8-8.0.0) |
+| TTC | TS-3GA-32.362(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32362rel8v800.pdf |
+
+### 10.10.62 TS 32.363 Telecommunication management; Entry point (EP) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)
+
+The document specifies the CORBA solution set for the IRP whose semantics is specified in the entry point IRP: Information service (3G TS 32.362).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 363 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 363 | 8.0.0 | Published | 17-Feb-09 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532363v800 |
+| ATIS | ATIS.3GPP.32.363V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.363(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.363(R8-8.0.0) |
+| TTC | TS-3GA-32.363(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32363rel8v800.pdf |
+
+### 10.10.63 TS 32.365 Telecommunication management; Entry point (EP) integration reference point (IRP); eXtensible markup language (XML) definitions
+
+The document specifies the XML definitions for the entry point IRP (EPIRP) as it applies to Itf-N, in accordance with EP IRP IS definitions TS 32.362, as well as notification log IRP XML definitions TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 365 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+### 10.10.64 TS 32.371 Telecommunication management; Security management concept and requirements
+
+The document defines, in addition to the requirements defined in 3G TS 32.101 and 3G TS 32.102, the requirements for security management IRP.
+
+The purpose of this document is to specify the necessary security features, services and functions to protect the network management data, including Requests, Responses, Notifications and Files, exchanged across the Itf-N.
+
+Telecommunication network security can be breached by weaknesses in operational procedures, physical installations, communication links, computational processes and data storage. Of concern here in the present document is the security problems resulting from the weaknesses inherent in the communication technologies (i.e., the 3GPP-defined interface IRPs and their supporting protocol stacks) deployed across the Itf-N.
+
+An appropriate level of security for a telecommunication network is essential. Secured access to the network management applications, and network management data, is essential. The 3GPP-defined interface IRPs (and their supporting protocol stacks), deployed across the Itf-N, are used for such access, and therefore, their security is considered essential.
+
+Many network management security standards exist. However, there is no recommendation on how to apply them in the Itf-N context. Their deployment across the Itf-N is left to operators. The present document and the corresponding solutions identify and recommend security standards in the Itf-N context.
+
+The business case for secured Itf-N is complex as it does not relate to the functions of the interface IRPs (the functions are constant) but rather, it relates to variants such as the cost of recovering from security breaks, the probability of security incidents and the cost of implementing security management, all of which differ depending on specific deployment scenarios.
+
+This document describes the security functions for a 3G network in terms of security domains.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 371 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 371 | 8.0.0 | Published | 2009-01-27 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532371v800 |
+| ATIS | ATIS.3GPP.32.371V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.371(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.371(R8-8.0.0) |
+| TTC | TS-3GA-32.371(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32371rel8v800.pdf |
+
+### **10.10.65 TS 32.372 Telecommunication management; Security services for integration reference point (IRP): Information service (IS)**
+
+The purpose of this document is to specify the necessary security features, services and functions to protect the network management data, including Requests, Responses, Notifications and Files, exchanged across the Itf-N.
+
+The document specifies the security service for IRP information service.
+
+This security service for IRP IS defines the semantics of management information visible across the Itf-N in a protocol- and technology-neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+This information service specification is related to 3GPP TS 32.371.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 372 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 372 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532372v800 |
+| ATIS | ATIS.3GPP.32.372V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.372(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.372(R8-8.0.0) |
+| TTC | TS-3GA-32.372(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32372rel8v800.pdf |
+
+### **10.10.66 TS 32.373 Telecommunication management; Security services for integration reference point (IRP); Common object request broker architecture (CORBA) solution**
+
+This document specifies the CORBA solution for the IRP whose semantics is specified in TS 32.372 security service for IRP information service.
+
+This solution set specification is related to TS 32.372.
+
+Note that within this document, there are several alternate solutions. Specific choices will be made to counter identified security threats, and to consider performance and cost criteria, i.e., an implementation is not expected to have to support every option for every deployment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 373 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 373 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532373v800 |
+| ATIS | ATIS.3GPP.32.373V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.373(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.373(R8-8.0.0) |
+| TTC | TS-3GA-32.373(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32373rel8v800.pdf |
+
+#### **10.10.67 TS 32.375 Telecommunication management; Security services for integration reference point (IRP): File integrity solution**
+
+The document contains the security services for IRP: File integrity solution whose semantics is specified in TS 32.372.
+
+This solution specification is related to TS 32.372.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 375 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 375 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532375v800 |
+| ATIS | ATIS.3GPP.32.375V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.375(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.375(R8-8.0.0) |
+| TTC | TS-3GA-32.375(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32375rel8v800.pdf |
+
+#### **10.10.68 TS 32.381 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP): Requirements**
+
+The purpose of partial suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+This document contains the requirements of partial suspension of Itf-N IRP. It defines, for the purpose of generally suspending the forwarding of notifications, the basic requirements to be fulfilled on Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 381 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 381 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532381v800 |
+| ATIS | ATIS.3GPP.32.381V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.381(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.381(R8-8.0.0) |
+| TTC | TS-3GA-32.381(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32381rel8v800.pdf |
+
+#### **10.10.69 TS 32.382 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP): Information service (IS)**
+
+The purpose of partial suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+This document is the information service of partial suspension of Itf-N IRP. It defines, for the purpose of suspending generally the forwarding of notifications, the information observable and controlled by the management system's client, and it also specifies the semantics of the interactions used to carry this information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 382 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 382 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532382v800 |
+| ATIS | ATIS.3GPP.32.382V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.382(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.382(R8-8.0.0) |
+| TTC | TS-3GA-32.382(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32382rel8v800.pdf |
+
+#### **10.10.70 TS 32.383 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of partial suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+This document is the "CORBA Solution Set" of partial suspension of Itf-N IRP for the IRP whose semantics is specified in partial suspension of Itf-N IRP: Information service (TS 32.382).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 383 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 383 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532383v800 |
+| ATIS | ATIS.3GPP.32.383V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.383(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.383(R8-8.0.0) |
+| TTC | TS-3GA-32.383(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32383rel8v800.pdf |
+
+#### **10.10.71 TS 32.385 Telecommunication management; Partial suspension of Itf-N integration reference point (IRP): eXtensible markup language (XML) file format definition**
+
+The purpose of partial suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
+
+This document is the eXtensible markup language (XML) file format definition of partial suspension of Itf-N IRP for the IRP whose semantics is specified in partial suspension of Itf-N IRP: Information service (TS 32.382).
+
+This XML definitions specification defines the XML syntax of the partial suspension of Itf-N IRP.
+
+This XML definitions specification is related to TS 32.382.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 385 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 385 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532385v800 |
+| ATIS | ATIS.3GPP.32.385V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.385(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.385(R8-8.0.0) |
+| TTC | TS-3GA-32.385(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32385rel8v800.pdf |
+
+#### **10.10.72 TS 32.391 Telecommunication management; Delta synchronization integration reference point (IRP): Requirements**
+
+The purpose of delta synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e., changed, were created or deleted) from a synchronization point onwards.
+
+This document contains the requirements of delta synchronization IRP. It defines, for the purpose of delta synchronization, the basic requirements to be fulfilled on Itf-N.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 391 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 391 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532391v800 |
+| ATIS | ATIS.3GPP.32.391V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.391(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.391(R8-8.0.0) |
+| TTC | TS-3GA-32.391(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32391rel8v800.pdf |
+
+### 10.10.73 TS 32.392 Telecommunication management; Delta synchronization integration reference point (IRP): Information service (IS)
+
+The purpose of delta synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e., changed, were created or deleted) from a synchronization point onwards.
+
+This document is the information service of delta synchronization IRP. It defines, for the purpose of delta synchronization, the information observable and controlled by the management system's client, and it also specifies the semantics of the interactions used to carry this information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 392 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 392 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532392v800 |
+| ATIS | ATIS.3GPP.32.392V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.392(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.392(R8-8.0.0) |
+| TTC | TS-3GA-32.392(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32392rel8v800.pdf |
+
+### 10.10.74 TS 32.393 Telecommunication management; Delta synchronization integration reference point (IRP); Common object request broker architecture (CORBA) solution set (SS)
+
+The purpose of delta synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e., changed, were created or deleted) from a synchronization point onwards.
+
+This document is the "CORBA Solution Set" of delta synchronization IRP for the IRP whose semantics is specified in delta synchronization IRP: Information service (TS 32.392).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 393 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 393 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532393v800 |
+| ATIS | ATIS.3GPP.32.393V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.393(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.393(R8-8.0.0) |
+| TTC | TS-3GA-32.393(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32393rel8v800.pdf |
+
+### 10.10.75 TS 32.395 Telecommunication management; Delta synchronization integration reference point (IRP); eXtensible markup language (XML) file format definition
+
+The purpose of delta synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e., changed, were created or deleted) from a synchronization point onwards.
+
+This document is the eXtensible markup language (XML) file format definition of delta synchronization IRP for the IRP whose semantics is specified in delta synchronization IRP: Information service (TS 32.392).
+
+This XML definitions specification defines the XML syntax of the delta synchronization IRP XML data file.
+
+This XML definitions specification is related to 3GPP TS 32.392.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 395 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 395 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532395v800 |
+| ATIS | ATIS.3GPP.32.395V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.395(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.395(R8-8.0.0) |
+| TTC | TS-3GA-32.395(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32395rel8v800.pdf |
+
+### 10.10.76 TS 32.401 Telecommunication management; Performance management (PM); Concept and requirements
+
+The present document describes the requirements for the management of performance measurements and the collection of performance measurement result data across GSM and UMTS networks. It defines the administration of measurement schedules by the network element manager (EM), the generation of measurement results in the network elements (NEs) and the transfer of these results to one or more operations systems, i.e., EM(s) and/or network manager(s) (NM(s)).
+
+The basic performance management concept that the present document is built upon is described in clause 4. The requirements of how an EM administers the performance measurements and how the results can be collected are defined in detail in clause 5. Measurements available for collection by NEs are described in the following specifications:
+
+- TS 52.402 for GSM systems;
+- TS 32.405, TS 32.406, TS 32.407 and TS 32.408 for UMTS and combined UMTS/GSM systems;
+- TS 32.409 for IMS networks.
+
+Effort has been made to ensure consistency in the definition of measurements between different NEs and generations. The performance measurement result is described in performance measurement file format definition (TS 32.432).
+
+The following is beyond the scope of the present document, and therefore the present document does not describe:
+
+- the formal definition of the interface that the EM uses to administer performance measurements in the NEs;
+- the formal definition of the interface that the EM uses to collect measurement results from the NEs;
+- how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user;
+- the information which may be obtained through the collection and processing of call or event-related records which have been produced by the NEs primarily for the purpose of raising bills and other charges.
+
+The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardization work so as to minimize the reinvention factor. References are given as appropriate.
+
+The objectives of this standardization are:
+
+- to provide the descriptions for a standard set of measurements;
+- to produce a common description of the management technique for measurement administration and result accumulation; and
+- to define a method for the bulk transmission of measurement results across a management interface.
+
+The definition of the standard measurements is intended to result in comparability of measurement result data produced in a multi-vendor wireless network, for those measurement types that can be standardized across all vendors' implementations.
+
+As far as possible, existing standardization in the area of performance management has been reused and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognized.
+
+This document considers all the above aspects of performance management for a GSM and UMTS network and its NEs defined in the core Technical Specifications. However, only those aspects which are specific to a GSM/UMTS system and particular to wireless network operation are included in the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 401 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 401 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532401v800 |
+| ATIS | ATIS.3GPP.32.401V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.401(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.401(R8-8.0.0) |
+| TTC | TS-3GA-32.401(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32401rel8v800.pdf |
+
+### **10.10.77 TS 32.404 Telecommunication management; Performance management (PM); Performance measurements – Definitions and template**
+
+This document describes the measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
+
+Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+TS 32.411; Telecommunication management; performance management (PM) integration reference point (IRP): Requirements
+
+This document specifies the overall requirements for the performance management integration reference point (PMIRP) as it applies to the network elements (NE), element manager (EM) and network manager (NM).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 404 | 8.3.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 404 | 8.3.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532404v830 |
+| ATIS | ATIS.3GPP.32.404V830-2009 | 8.3.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.404(R8-8.3.0) | 8.3.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.404(R8-8.3.0) |
+| TTC | TS-3GA-32.404(Rel8)v8.3.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32404rel8v830.pdf |
+
+### 10.10.78 TS 32.405 Telecommunication management; Performance management (PM); Performance measurements universal terrestrial radio access network (UTRAN)
+
+This document describes the measurements for UMTS and combined UMTS/GSM. TS 32.401 describes performance management concepts and requirements.
+
+The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network. Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents.
+
+Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 405 | 8.5.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 405 | 8.4.0 | Published | 2009-01-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532405v840 |
+| ATIS | ATIS.3GPP.32.405V840-2009 | 8.4.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.405(R8-8.4.0) | 8.4.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.405(R8-8.4.0) |
+| TTC | TS-3GA-32.405(Rel8)v8.4.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32405rel8v840.pdf |
+
+### **10.10.79 TS 32.406 Telecommunication management; Performance management (PM); Performance measurements core network (CN) packet switched (PS) domain**
+
+This document describes the measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+This document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
+
+Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 406 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 406 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532406v800 |
+| ATIS | ATIS.3GPP.32.406V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.406(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.406(R8-8.0.0) |
+| TTC | TS-3GA-32.406(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32406rel8v800.pdf |
+
+### **10.10.80 TS 32.407 Telecommunication management; Performance management (PM); Core network (CN) circuit switched (CS) domain; Performance measurements – UMTS and combined UMTS/GSM**
+
+This document describes the CN CS measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+This document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network. These may be measurement types defined within the present document, measurements defined within other standards bodies, or vendor-specific measurement types.
+
+Only measurement types that are specific to CN CS UMTS or combined UMTS/GSM networks are defined within the present documents, i.e., vendor-specific measurement types used in UMTS and combined UMTS/GSM networks. Some ATM or IP measurements defined here are only used for load carrying. The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 407 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 407 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532407v800 |
+| ATIS | ATIS.3GPP.32.407V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.407(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.407(R8-8.0.0) |
+| TTC | TS-3GA-32.407(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32407rel8v800.pdf |
+
+### 10.10.81 TS 32.408 Telecommunication management; Performance management (PM); Performance measurements teleservice
+
+This document describes the measurements for UMTS and combined UMTS/GSM.
+
+TS 32.401 describes performance management concepts and requirements.
+
+This document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
+
+Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor-specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to the manufacturer's documentation.
+
+Measurements related to "external" technologies (such as ATM or IP), as described by "external" standards bodies (e.g., ITU-T or IETF), shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 408 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 408 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532408v800 |
+| ATIS | ATIS.3GPP.32.408V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.408(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.408(R8-8.0.0) |
+| TTC | TS-3GA-32.408(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32408rel8v800.pdf |
+
+### **10.10.82 TS 32.409 Telecommunication management; Performance management (PM); Performance measurements – IP multimedia subsystem (IMS)**
+
+This document describes the measurements of IMS.
+
+TS 32.401 describes performance management concepts and requirements.
+
+This document is valid for all measurement types provided by an implementation of an IMS network. These may be measurement types defined within the present document, measurements defined within other standards bodies, or vendor-specific measurement types.
+
+Only measurement types that are specific to IMS network are defined within the present documents, i.e., vendor-specific measurement types and measurements related to "external" technologies used in IMS network, such as ATM or IP, are not covered. Instead, these could be applied as described by the other "external" standards bodies (e.g., ITU-T or IETF), or according to the manufacturer's documentation.
+
+The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardized across all vendors' implementations.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 409 | 8.2.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 409 | 8.2.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532409v820 |
+| ATIS | ATIS.3GPP.32.409V820-2009 | 8.2.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.409(R8-8.2.0) | 8.2.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT.3G-32.409(R8-8.2.0) |
+| TTC | TS-3GA-32.409(Rel8)v8.2.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32409rel8v820.pdf |
+
+### **10.10.83 TS 32.411 Telecommunication management; Performance management (PM) integration reference point (IRP): Requirements**
+
+The present document specifies the overall requirements for the performance management integration reference point (PMIRP) as it applies to the network elements (NE), element manager (EM) and network manager (NM).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------|----------------|---------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 411 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+### **10.10.84 TS 32.412 Telecommunication management; Performance management (PM) integration reference point (IRP): Information service (IS)**
+
+This document specifies the information service for the performance management integration reference point (PMIRP) as it applies to the Itf-N.
+
+This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol- and technology-neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 412 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+#### **10.10.85 TS 32.413 Telecommunication management; Performance management (PM) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+This document specifies the common object request broker architecture (CORBA) solution set (SS) for the IRP whose semantics is specified in PM (performance management) IRP: Information service 3G TS 32.412.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 413 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+#### **10.10.86 TS 32.415 Telecommunication management; Performance management (PM) integration reference point (IRP); eXtensible markup language (XML) definitions**
+
+This document specifies the XML definitions for the performance management (PM) integration reference point (IRP) as it applies to Itf-N, in accordance with PM IRP IS definitions in 3GPP TS 32.412, as well as the notification log IRP XML definitions in 3GPP TS 32.335.
+
+This specification is related to 3GPP TS 32.412.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 415 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+#### **10.10.87 TS 32.421 Telecommunication management; Subscriber and equipment trace: Trace concepts and requirements**
+
+This document describes the requirements for the management of trace and the reporting of trace data across UMTS networks as it refers to subscriber tracing (tracing of IMSI or private ID) and MS tracing (tracing of IMEI or IMEISV). It defines the administration of trace session activation/deactivation by the element manager (EM) or the network itself via signalling, the generation of trace results in the network elements (NEs) and the transfer of these results to one or more operations systems, i.e., EM(s) and/or network manager(s) (NM(s)).
+
+The basic subscriber and MS trace concept that the present document is built upon is described in clause 4. The high-level requirements for trace data, trace session activation/deactivation and trace reporting are defined in clause 5. Clause 5 also contains an overview of use cases for trace (the use cases are described in Annex B). Annex A provides a high-level view of trace functional architecture. Trace control and configuration management are described in 3GPP TS 32.422, and trace data definition and management are described in 3GPP TS 32.423.
+
+In this release, this document does not cover any trace capability limitations within a NE (e.g., maximum number of simultaneous traced mobiles for a given NE) or any functionality related to these limitations (e.g., NE aborting a trace session due to resource limitations).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 421 | 8.4.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 421 | 8.4.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532421v840 |
+| ATIS | ATIS.3GPP.32.421V840-2009 | 8.4.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.421(R8-8.4.0) | 8.4.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.421(R8-8.4.0) |
+| TTC | TS-3GA-32.421(Rel8)v8.4.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32421rel8v840.pdf |
+
+#### **10.10.88 TS 32.422 Telecommunication management; Subscriber and equipment trace; Trace control and configuration management**
+
+This document describes the mechanisms used for the control and configuration of the trace functionality at the EMs and NEs. It covers the triggering events for starting/stopping of subscriber/MS activity traced over 3GPP standardized signalling interfaces, the types of trace mechanisms, configuration of a trace, level of detail available in the trace data, the generation of trace results in the network elements (NEs) and the transfer of these results to one or more EM(s) and/or network manager(s) (NM(s)).
+
+The mechanisms for trace activation/deactivation are detailed in clause 4; clause 5 details the various trace control and configuration parameters and the triggering events that can be set in a network. Trace concepts and requirements are covered in 3G TS 32.421, while trace data definition and management is covered in 3G TS 32.423.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 422 | 8.4.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 422 | 8.3.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532422v830 |
+| ATIS | ATIS.3GPP.32.422V830-2009 | 8.3.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.422(R8-8.3.0) | 8.3.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.422(R8-8.3.0) |
+| TTC | TS-3GA-32.422(Rel8)v8.3.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32422rel8v830.pdf |
+
+#### **10.10.89 TS 32.423 Telecommunication management; Subscriber and equipment trace; Trace data definition and management**
+
+The document describes trace data definition and management. It covers trace records content, their format and transfer.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 423 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+#### 10.10.90 TS 32.432 Telecommunication management; Performance measurement: File format definition
+
+The document describes the general semantics of performance measurement result and collection. It defines the report file format, report file conventions and the file transfer procedure. Clause 4 specifies the file format for the bulk transfer of performance measurement results to the NM, while clause 6 discusses the file transfer procedure utilized on that interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 432 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 432 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532432v800 |
+| ATIS | ATIS.3GPP.32.432V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.432(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.432(R8-8.0.0) |
+| TTC | TS-3GA-32.432(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32432rel8v800.pdf |
+
+#### 10.10.91 TS 32.435 Telecommunication management; Performance measurement eXtensible markup language (XML) file format definition
+
+The document describes the XML file format of performance measurement results whose semantics is defined in 3G TS 32.432.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 435 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 435 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532435v800 |
+| ATIS | ATIS.3GPP.32.435V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.435(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.435(R8-8.0.0) |
+| TTC | TS-3GA-32.435(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32435rel8v800.pdf |
+
+### 10.10.92 TS 32.436 Telecommunication management; Performance measurement: Abstract syntax notation one (ASN.1) file format definition
+
+The document defines the ASN.1 file format definition for performance measurement results collection whose semantics is defined in 3G TS 32.432.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 436 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 436 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532436v800 |
+| ATIS | ATIS.3GPP.32.436V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.436(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.436(R8-8.0.0) |
+| TTC | TS-3GA-32.436(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32436rel8v800.pdf |
+
+### 10.10.93 TS 32.441 Telecommunication management; Trace management integration reference point (IRP): Requirements
+
+This document specifies the overall requirements for the trace management integration reference point (TraceIRP) as it applies to Itf-N.
+
+The trace IRP supports the operations that are required for the subscriber and equipment trace, the service level trace and the cell traffic trace functionalities.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 441 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 441 | 8.1.0 | Published | 2009-01-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532441v810 |
+| ATIS | ATIS.3GPP.32.441V810-2009 | 8.1.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.441(R8-8.1.0) | 8.1.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.441(R8-8.1.0) |
+| TTC | TS-3GA-32.441(Rel8)v8.1.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32441rel8v810.pdf |
+
+**10.10.94 TS 32.442 Telecommunication management; Trace management integration reference point (IRP): Information service (IS)**
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 442 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 442 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532442v800 |
+| ATIS | ATIS.3GPP.32.442V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.442(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.442(R8-8.0.0) |
+| TTC | TS-3GA-32.442(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32442rel8v800.pdf |
+
+**10.10.95 TS 32.443 Telecommunication management; Trace management integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+This solution set specification is related to TS 32.442.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 443 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 443 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532443v800 |
+| ATIS | ATIS.3GPP.32.443V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.443(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.443(R8-8.0.0) |
+| TTC | TS-3GA-32.443(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32443rel8v800.pdf |
+
+**10.10.96 TS 32.445 Telecommunication management; Trace management integration reference point (IRP): eXtensible markup language (XML) file format definition**
+
+This document is the eXtensible markup language (XML) file format definition of trace IRP for the IRP whose semantics is specified in trace IRP: Information service (TS 32.442).
+
+This XML definitions specification defines the XML syntax of the trace IRP XML data file for the notifications related to trace IRP. The XML file definitions for a trace data file can be found in Annex A of TS 32.423.
+
+This XML file format definition specification is related to 3GPP TS 32.442.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 445 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+### **10.10.97 TS 32.500 Telecommunication management; Self-organizing networks (SON); Concepts and requirements**
+
+This document describes the requirements and architecture for the self-organizing network (SON) functions within the OAM system. SON includes:
+
+#### **Provision of infrastructure for SON, in the OAM system**
+
+- Enabling SON operations
+- Provide SON capabilities (each of which can either be distributed or centralized) within the OAM infrastructure, including their management
+- Access to SON relevant eNodeB attributes
+- Identification of SON relevant eNodeB and UE measurements
+- Access to and transfer of SON relevant eNodeB and UE measurements
+- Transfer of SON relevant eNodeB alarms
+
+#### **Define necessary interface IRPs**
+
+- the automation of neighbour relation lists in E-UTRAN and between different 3GPP Radio Access Technologies,
+- self-establishment of a new eNodeB in the network,
+- self-configuration and self-healing of eNodeBs,
+- automated coverage and capacity optimization,
+- optimization of parameters due to troubleshooting,
+- continuous optimization due to dynamic changes in the network,
+- automated handover optimization,
+- optimization of QoS related radio parameters.
+
+The SON concept and architecture are described in clause 4.
+
+The high-level requirements for SON are defined in clause 5.
+
+Use cases for SON are described in clause 5.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 500 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532500v800 |
+| ATIS | ATIS.3GPP.32.500V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.500(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT_3G-32.500(R8-8.0.0) |
+| TTC | TS-3GA-32.500(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32500rel8v800.pdf |
+
+### **10.10.98 TS 32.501 Telecommunication management; Self-configuration of network elements; Concepts and integration reference point (IRP) requirements**
+
+This document describes the concepts how self-configuration works and what IRP requirements need to be met to support this functionality. The document also captures if a requirement shall be met via the Itf-N interface or via other protocols. This version of the TS is restricted to self-configuration of eNBs. The requirements in this document are not imposed on HNBs.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 501 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532501v800 |
+| ATIS | ATIS.3GPP.32.501V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.501(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.501(R8-8.0.0) |
+| TTC | TS-3GA-32.501(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32501rel8v800.pdf |
+
+### **10.10.99 TS 32.502 Telecommunication management; Self-configuration of network elements integration reference point (IRP); Information service (IS)**
+
+This document defines the information service (IS) part of the self-configuration IRP (SCIRP). It describes the semantics of the information and the interactions visible across Itf-N in a protocol-independent way. The information is specified by means of information object classes (IOCs) and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
+
+The scope of this version of the TS is restricted to self-configuration of eNBs.
+
+The document also describes how already defined Itf-N functionalities are used in the context of Self-Configuration.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 502 | 8.0.0 | Published | 2009-02-06 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532502v800 |
+| ATIS | ATIS.3GPP.32.502V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.502(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.502(R8-8.0.0) |
+| TTC | TS-3GA-32.502(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32502rel8v800.pdf |
+
+### **10.10.100 TS 32.503 Telecommunication management; Self-configuration of network elements integration reference point (IRP); Common object request broker architecture (CORBA) solution set (SS)**
+
+The document is the "CORBA Solution Set" of Software Management IRP for the IRP whose semantics is specified in Software Management IRP Information Service (3GPP TS 32.502).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 503 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532503v800 |
+| ATIS | ATIS.3GPP.32.503V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.503(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.503(R8-8.0.0) |
+| TTC | TS-3GA-32.503(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32503rel8v800.pdf |
+
+### 10.10.101 TS 32.511 Telecommunication management; Automatic neighbour relation (ANR) management; Concepts and requirements
+
+This document describes the requirements and architecture for the management of neighbour cell relations (NRs) across the Itf-N. The NR management is a key feature of self-organizing network (SON), described in 3GPP TR 32.816.
+
+The NR concept and background information are described in clause 4.
+
+The requirements for management of NR are defined in clause 5.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 511 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532511v800 |
+| ATIS | ATIS.3GPP.32.511V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.511(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.511(R8-8.0.0) |
+| TTC | TS-3GA-32.511(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32511rel8v800.pdf |
+
+### 10.10.102 TS 32.532 Telecommunication management; Software management integration reference point (IRP); Information service (IS)
+
+The document contains the Software Management Interface IRP Information Services descriptions.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 532 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532532v800 |
+| ATIS | ATIS.3GPP.32.532V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.532(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.532(R8-8.0.0) |
+| TTC | TS-3GA-32.532(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32532rel8v800.pdf |
+
+**10.10.103 TS 32.533 Telecommunication management; Software management integration reference point (IRP); Common object request broker architecture (CORBA) solution set (SS)**
+
+The present document is the "CORBA solution set" of software management IRP for the IRP whose semantics is specified in Software Management IRP Information Service (3GPP TS 32.532).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 533 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532533v800 |
+| ATIS | ATIS.3GPP.32.533V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.533(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.533(R8-8.0.0) |
+| TTC | TS-3GA-32.533(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32533rel8v800.pdf |
+
+**10.10.104 TS 32.600 Telecommunication management; Configuration management (CM); Concept and high-level requirements**
+
+The document describes the configuration management (CM) aspects of managing a 3G network. This is described from the management perspective in TS 32.101 and TS 32.102.
+
+This document defines a set of controls to be employed to effect set-up and changes to a 3G network in such a way that operational capability and quality of service (QoS), network integrity and system interworking are ensured. In this way, this document describes the interface definition and behaviour for the management of relevant 3G NEs in the context of the described management environment. The context is described for both the management system (OS) and network element (NE) functionality.
+
+The Itf-N for CM is built up by a number of integration reference points (IRPs) and a related name convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.101 and TS 32.102. For CM, a number of IRPs (and a name convention TS 32.300) are defined, used by this as well as by other specifications for telecom management produced by 3GPP. These IRPs are defined in separate specifications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 600 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 600 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532600v800 |
+| ATIS | ATIS.3GPP.32.600V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.600(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.600(R8-8.0.0) |
+| TTC | TS-3GA-32.600(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32600rel8v800.pdf |
+
+### **10.10.105 TS 32.601 Telecommunication management; Configuration management (CM); Basic CM integration reference point (IRP); Requirements**
+
+The document defines, in addition to the requirements defined in TS 32.101, TS 32.102 and TS 32.600, the requirements for the present IRP: Basic configuration management IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 601 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 601 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532601v800 |
+| ATIS | ATIS.3GPP.32.601V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.601(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.601(R8-8.0.0) |
+| TTC | TS-3GA-32.601(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32601rel8v800.pdf |
+
+### **10.10.106 TS 32.602 Telecommunication management; Configuration management; Basic CM integration reference point (IRP) information service**
+
+The document defines a component of an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate basic configuration management-related information to one or several 'IRPManagers' (typically network managers).
+
+This version of the IRP is mainly intended for "passive management" of high-level network configuration and status information, as required by a network manager.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the introduction clause. An important aspect of such a split is that the network resource models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP information service. The Basic CM IRP: IS defined herein provides one such information service.
+
+The basic CM IRP: IS defined in the document has the following main purpose: to define an interface for retrieval of configuration management information.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 602 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 602 | 8.0.0 | Published | 2009-01-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532602v800 |
+| ATIS | ATIS.3GPP.32.602V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.602(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.602(R8-8.0.0) |
+| TTC | TS-3GA-32.602(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32602rel8v800.pdf |
+
+### 10.10.107 TS 32.603 Telecommunication management; Configuration management; Basic configuration management IRP: CORBA solution set
+
+The purpose of this *Basic Configuration Management (CM) IRP: CORBA Solution Set* is to define the mapping of the basic CM IRP: IS (see TS 32.602) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+This document defines NRM independent data types, methods and notifications.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 603 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 603 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532603v800 |
+| ATIS | ATIS.3GPP.32.603V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.603(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.603(R8-8.0.0) |
+| TTC | TS-3GA-32.603(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32603rel8v800.pdf |
+
+### 10.10.108 TS 32.607 Telecommunication management; Configuration management (CM); Basic CM integration reference point (IRP): SOAP solution set (SS)
+
+The purpose of this basic CM IRP: SOAP solution set is to define the mapping of the basic CM IRP: IS (TS 32.602) to the protocol specific details necessary for the implementation of this IRP in a SOAP/WSDL environment.
+
+This document defines NRM independent data types and methods.
+
+This solution set specification is related to 3G TS 32.602.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 607 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 607 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532607v800 |
+| ATIS | ATIS.3GPP.32.607V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.607(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.607(R8-8.0.0) |
+| TTC | TS-3GA-32.607(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32607rel8v800.pdf |
+
+#### **10.10.109 TS 32.611 Telecommunication management; 3G configuration management (CM); Bulk CM integration reference point (IRP): Requirements**
+
+The document describes the bulk configuration management (CM) requirements for managing a 3G network. This is described from the management perspective in TS 32.101 and TS 32.102.
+
+The Itf-N for CM is built up by a number of integration reference points (IRPs) and a related name convention TS 32.300, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.101 and TS 32.102. For CM, a number of IRPs (and a name convention) are defined, used by this as well as by other specifications for telecom management. These IRPs are defined in separate specifications. This document defines the requirements for the bulk CM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 611 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+#### **10.10.110 TS 32.612 Telecommunication management; 3G configuration management (CM); Bulk CM integration reference point (IRP): Information service**
+
+The document (bulk configuration management IRP: Information service) defines an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate bulk configuration management related information to one or several 'IRPManagers' (typically network managers).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 612 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+#### **10.10.111 TS 32.613 Telecommunication management; 3G configuration management (CM); Bulk CM integration reference point (IRP): CORBA solution set**
+
+The purpose of this *Bulk CM IRP: CORBA Solution Set* is to define the mapping of the IRP information service (see TS 32.612) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+The document does not describe any network resource models (NRMs) – they are described in generic network resources IRP: NRM TS 32.622, UTRAN network resources IRP: NRM TS 32.642.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 613 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+**10.10.112 TS 32.615 Telecommunication management; Configuration management (CM); Bulk CM integration reference point (IRP): eXtensible markup language (XML) file format definition**
+
+The document defines the XML file formats for the configuration data files and session log files of bulk CM IRP IS TS 32.612.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 615 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+**10.10.113 TS 32.621 Telecommunication management; Configuration management (CM); Generic network resources integration reference point (IRP): Requirements**
+
+The document defines, in addition to the requirements defined in TS 32.101, 32.102 and 32.600, the requirements for the present IRP: Generic network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 621 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 621 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532621v800 |
+| ATIS | ATIS.3GPP.32.621V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.621(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT_3G-32.621(R8-8.0.0) |
+| TTC | TS-3GA-32.621(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32621rel8v800.pdf |
+
+**10.10.114 TS 32.622 Telecommunication management; Configuration management (CM); Generic network resources IRP; Network resource model (NRM)**
+
+The document (generic network resources IRP: Network resource model) defines an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate network management-related information to one or several 'IRPManagers' (typically network managers).
+
+The document specifies a generic network resource model (NRM) (also referred to as a management information model – MIM) with definitions of managed object classes.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs. In addition to the subject IRP, it is expected that IRPs will be defined for functional areas like security management, software management, network and service provisioning, etc. An important aspect of such a split is that the network resource models (NRMs) defined in different IRPs are consistent. The generic network resources IRP here provides a base for all resource modelling.
+
+The generic network resources IRP main purpose is to define a generic network resource model that constitutes a base from which other (more specialized) resource models can inherit or have associations with.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 622 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 622 | 8.1.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532622v810 |
+| ATIS | ATIS.3GPP.32.622V810-2009 | 8.1.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.622(R8-8.1.0) | 8.1.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.622(R8-8.1.0) |
+| TTC | TS-3GA-32.622(Rel8)v8.1.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32622rel8v810.pdf |
+
+### 10.10.115 TS 32.623 Telecommunication management; Configuration management (CM); Generic network resources IRP: CORBA solution set
+
+The TS 32.620 series (generic network resources IRP) defines an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate network management-related information to one or several 'IRPManagers' (typically network managers).
+
+This series of documents specifies a generic network resource model (NRM) (also referred to as a management information model – MIM) with definitions of information object classes and managed object classes.
+
+The document specifies the CORBA solution set.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 623 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 623 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532623v800 |
+| ATIS | ATIS.3GPP.32.623V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.623(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.623(R8-8.0.0) |
+| TTC | TS-3GA-32.623(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32623rel8v800.pdf |
+
+**10.10.116 TS 32.625 Telecommunication management; Configuration management (CM); Generic network resources IRP: Bulk CM eXtensible markup language (XML) file format definition**
+
+This document provides the NRM-specific part related to the generic network resources IRP NRM (3G TS 32.622) of the XML file format definition for the bulk configuration management IRP IS (3G TS 32.612).
+
+The main part of this XML file format definition is provided by 3G TS 32.615.
+
+This file format definition specification is related to 3G TS 32.622.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 625 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 625 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532625v800 |
+| ATIS | ATIS.3GPP.32.625V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.625(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.625(R8-8.0.0) |
+| TTC | TS-3GA-32.625(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32625rel8v800.pdf |
+
+**10.10.117 TS 32.631 Telecommunication management; Configuration management (CM); Core network resources IRP: Requirements**
+
+The document defines, in addition to the requirements defined in TS 32.101, 32.102 and 32.600, the requirements for the present IRP: Core network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 631 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 631 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532631v800 |
+| ATIS | ATIS.3GPP.32.631V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.631(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.631(R8-8.0.0) |
+| TTC | TS-3GA-32.631(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32631rel8v800.pdf |
+
+**10.10.118 TS 32.632 Telecommunication management; Configuration management; Core network resources IRP: Network resource model (NRM)**
+
+The document is part of an integration reference point (IRP) named "Core Network Resources IRP", through which an 'IRPAgent' (typically an element manager or network element) can communicate configuration management information to one or several 'IRPManagers' (typically network managers) concerning CN resources. This version of the IRP is mainly intended for
+
+"passive management" of high-level network configuration and status information as required by a network manager. The "Core Network Resources IRP" comprises a set of specifications defining Requirements, a protocol-neutral network resource model (NRM) and corresponding solution set(s).
+
+The document specifies the protocol-neutral core network resources IRP: Network resource model. It reuses relevant parts of the generic NRM in TS 32.622, either by direct reuse or sub-classing, and in addition to that defines CN-specific managed object classes.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause. An important aspect of such a split is that the network resource models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRP Agent implementation can be accessed as one coherent model through one IRP information service.
+
+The document has the following main purpose: to define the applied CN-specific network resource model, based on the generic NRM in TS 32.622.
+
+Finally, in order to access the information defined by this NRM, an IRP information service (IS) is needed, such as the basic CM IRP: IS TS 32.602. However, which information service is applicable is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 632 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/technical.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 632 | 8.1.0 | Published | 2009-01-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532632v810 |
+| ATIS | ATIS.3GPP.32.632V810-2009 | 8.1.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.632(R8-8.1.0) | 8.1.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT_3G-32.632(R8-8.1.0) |
+| TTC | TS-3GA-32.632(Rel8)v8.1.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32632rel8v810.pdf |
+
+#### **10.10.119 TS 32.633 Telecommunication management; Configuration management (CM); Core network resources IRP: CORBA solution set**
+
+The purpose of this *Core Network Resources IRP: CORBA Solution Set* is to define the mapping of the IRP information model (see TS 32.632) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 633 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 633 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532633v800 |
+| ATIS | ATIS.3GPP.32.633V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.633(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.633(R8-8.0.0) |
+| TTC | TS-3GA-32.633(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32633rel8v800.pdf |
+
+**10.10.120 TS 32.635 Telecommunication management; Configuration management (CM); Core network resources IRP: Bulk CM eXtensible markup language (XML) file format definition**
+
+This document provides the NRM-specific part related to the core network resources IRP NRM (3G TS 32.632) of the XML file format definition for the bulk configuration management IRP IS (3G TS 32.612).
+
+The main part of this XML file format definition is provided by 3G TS 32.615.
+
+This file format definition specification is related to 3G TS 32.632.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 635 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 635 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532635v800 |
+| ATIS | ATIS.3GPP.32.635V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.635(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.635(R8-8.0.0) |
+| TTC | TS-3GA-32.635(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32635rel8v800.pdf |
+
+**10.10.121 TS 32.641 Telecommunication management; Configuration management (CM); UTRAN network resources IRP: Requirements**
+
+The document defines, in addition to the requirements defined in TS 32.101, 32.102 and 32.600, the requirements for the present IRP: UTRAN network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 641 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 641 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532641v800 |
+| ATIS | ATIS.3GPP.32.641V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.641(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.641(R8-8.0.0) |
+| TTC | TS-3GA-32.641(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32641rel8v800.pdf |
+
+### 10.10.122 TS 32.642 Telecommunication management; Configuration management (CM); UTRAN network resources IRP: NRM
+
+The document is part of an integration reference point (IRP) named "UTRAN Network Resources IRP", through which an 'IRPAgent' (typically an element manager or network element) can communicate configuration management information to one or several 'IRPManagers' (typically network managers) concerning UTRAN resources. The "UTRAN Network Resources IRP" comprises a set of specifications defining Requirements, a protocol neutral network resource model (NRM) and corresponding solution set(s).
+
+The document specifies the protocol neutral UTRAN network resources IRP: Network resource model. It reuses relevant parts of the generic NRM in TS 32.622, either by direct reuse or subclassing, and in addition to that defines UTRAN specific managed object classes.
+
+The configuration management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the introduction clause. An important aspect of such a split is that the network resource models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP information service.
+
+The document has the following main purpose: to define the applied UTRAN-specific network resource model, based on the generic NRM in TS 32.600.
+
+Finally, in order to access the information defined by this NRM, an IRP information service (IS) is needed, such as the basic CM IRP: IS 32.602 or the bulk CM IRP: IS 32.612. However, which information service is applicable is outside the scope of this document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 642 | 8.2.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 642 | 8.2.0 | Published | 2009-01-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532642v820 |
+| ATIS | ATIS.3GPP.32.642V820-2009 | 8.2.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.642(R8-8.2.0) | 8.2.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.642(R8-8.2.0) |
+| TTC | TS-3GA-32.642(Rel8)v8.2.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32642rel8v820.pdf |
+
+**10.10.123 TS 32.643 Telecommunication management; Configuration management (CM);
+UTRAN network resources IRP: CORBA solution set**
+
+The purpose of this UTRAN network resources IRP: CORBA solution set is to define the mapping of the IRP information model (see TS 32.642) to the protocol-specific details necessary for the implementation of this IRP in a CORBA/IDL environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 643 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 643 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532643v800 |
+| ATIS | ATIS.3GPP.32.643V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.643(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.643(R8-8.0.0) |
+| TTC | TS-3GA-32.643(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32643rel8v800.pdf |
+
+**10.10.124 TS 32.645 Telecommunication management; Configuration management (CM);
+UTRAN network resources IRP: Bulk CM eXtensible markup language (XML)
+file format definition**
+
+This document provides the NRM-specific part related to the UTRAN network resources IRP NRM (3G TS 32.642) of the XML file format definition for the bulk configuration management IRP IS (3G TS 32.612).
+
+The main part of this XML file format definition is provided by 3G TS 32.615.
+
+This file format definition specification is related to 3G TS 32.642.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 645 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 645 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532645v800 |
+| ATIS | ATIS.3GPP.32.645V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.645(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.645(R8-8.0.0) |
+| TTC | TS-3GA-32.645(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32645rel8v800.pdf |
+
+**10.10.125 TS 32.661 Telecommunication management; Configuration management (CM);
+Kernel CM; Requirements**
+
+This document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102, and 3G TS 32.600, the requirements for the present IRP: Kernel configuration management IRP. It is the intent of Kernel configuration management to provide an IRP that contains the configuration
+
+management functionality that is basic and minimal. It is the functionality that is common to and required by both basic CM and bulk CM. While neither the basic CM IRP nor the bulk CM IRP requires the other, each of which requires the Kernel CM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 661 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 661 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532661v800 |
+| ATIS | ATIS.3GPP.32.661V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.661(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.661(R8-8.0.0) |
+| TTC | TS-3GA-32.661(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32661rel8v800.pdf |
+
+#### 10.10.126 TS 32.662 Telecommunication management; Configuration management (CM); Kernel CM; Information service
+
+This document defines integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate configuration management-related information to one or several 'IRPManagers' (typically network managers).
+
+The function of this Kernel CM IRP information service is to define an interface that provides the essential CM services. While it is not expected that the Kernel CM IRP alone will provide adequate CM capability, the Kernel CM IRP is expected to provide the common supporting capability required for other IRPs such as the basic CM IRP or the bulk CM IRP, each of which requires the Kernel CM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 662 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 662 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532662v800 |
+| ATIS | ATIS.3GPP.32.662V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.662(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.662(R8-8.0.0) |
+| TTC | TS-3GA-32.662(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32662rel8v800.pdf |
+
+#### 10.10.127 TS 32.663 Telecommunication management; Configuration management (CM); Kernel CM: CORBA solution set
+
+The purpose of this document is to define the mapping of the Kernel CM IRP: IS (see 3G TS 32.662) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+This solution set specification is related to 3G TS 32.662.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 663 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 663 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532663v800 |
+| ATIS | ATIS.3GPP.32.663V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.663(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.663(R8-8.0.0) |
+| TTC | TS-3GA-32.663(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32663rel8v800.pdf |
+
+**10.10.128 TS 32.665 Telecommunication management; Configuration management (CM); Kernel CM integration reference point (IRP): eXtensible markup language (XML) definitions**
+
+This document specifies the XML definitions for the Kernel CM integration reference point (IRP) as it applies to Itf-N, in accordance with Kernel CM IRP IS definitions in TS 32.662, as well as the notification log IRP XML definitions in TS 32.335.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 665 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 665 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532665v800 |
+| ATIS | ATIS.3GPP.32.665V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.665(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.665(R8-8.0.0) |
+| TTC | TS-3GA-32.665(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32665rel8v800.pdf |
+
+**10.10.129 TS 32.667 Telecommunication management; Configuration management (CM); Kernel CM integration reference point (IRP): SOAP solution set (SS)**
+
+The purpose of the present document is to define the mapping of the Kernel CM IRP: IS (TS 32.662) to the protocol-specific details necessary for the implementation of this IRP in a SOAP/WSDL environment.
+
+This solution set specification is related to TS 32.662.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 667 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 667 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532667v800 |
+| ATIS | ATIS.3GPP.32.667V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.667(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.667(R8-8.0.0) |
+| TTC | TS-3GA-32.667(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32667rel8v800.pdf |
+
+#### **10.10.130 TS 32.671 Telecommunication management; Configuration management (CM); State management integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102 and 3G TS 32.600, the requirements for the present IRP: State management.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 671 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 671 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532671v800 |
+| ATIS | ATIS.3GPP.32.671V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.671(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.671(R8-8.0.0) |
+| TTC | TS-3GA-32.671(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32671rel8v800.pdf |
+
+#### **10.10.131 TS 32.672 Telecommunication management; Configuration management (CM); State management integration reference point (IRP): Information service**
+
+This document defines the information service (IS) part of the state management IRP. It specifies the semantics of the network resource state and status information visible across the Itf-N. It also specifies the interaction required for the management of the state and status information.
+
+The state and status attributes specified in this document shall be used, where applicable, as attributes in the information object class (IOC) definitions of other 3G IRPs. When used by the IOC definition, the semantics of the state and status attributes can be qualified and enhanced, if deemed necessary.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 672 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 672 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532672v800 |
+| ATIS | ATIS.3GPP.32.672V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.672(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.672(R8-8.0.0) |
+| TTC | TS-3GA-32.672(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32672rel8v800.pdf |
+
+### **10.10.132 TS 32.673 Telecommunication management; Configuration management (CM); State management integration reference point (IRP): CORBA solution set**
+
+This document specifies the CORBA solution set (SS) for the IRP whose semantics is specified in state management IRP: Information service (IS) (3G TS 32.672).
+
+Clauses 1 to 3 provide background information. Clause 4 provides key architectural features supporting the SS. Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Annex A contains the IDL specification.
+
+This solution set specification is related to 3G TS 32.672.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 673 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 673 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532673v800 |
+| ATIS | ATIS.3GPP.32.673V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.673(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.673(R8-8.0.0) |
+| TTC | TS-3GA-32.673(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32673rel8v800.pdf |
+
+### **10.10.133 TS 32.675 Telecommunication management; Configuration management (CM); State management integration reference point (IRP): Bulk CM eXtensible markup language (XML) file format definition**
+
+The document specifies the XML file format definition for the bulk configuration management IRP IS for the IRP whose semantics is specified in state management IRP: Information service (IS) (3G TS 32.672).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 675 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 675 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532675v800 |
+| ATIS | ATIS.3GPP.32.675V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.675(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.675(R8-8.0.0) |
+| TTC | TS-3GA-32.675(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32675rel8v800.pdf |
+
+#### **10.10.134 TS 32.690 Telecommunication management; Inventory management (IM): Requirements**
+
+The document defines the requirements for the present IRP: Inventory management IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 690 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 690 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532690v800 |
+| ATIS | ATIS.3GPP.32.690V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.690(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.690(R8-8.0.0) |
+| TTC | TS-3GA-32.690(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32690rel8v800.pdf |
+
+#### **10.10.135 TS 32.691 Telecommunication management; Inventory management network resources integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3G TS 32.101, 3G TS 32.102 and 3G TS 32.600, the requirements for the present IRP: Inventory management network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 691 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 691 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532691v800 |
+| ATIS | ATIS.3GPP.32.691V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.691(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.691(R8-8.0.0) |
+| TTC | TS-3GA-32.691(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32691rel8v800.pdf |
+
+### 10.10.136 TS 32.692 Telecommunication management; Inventory management network resources integration reference point (IRP): Network resource model
+
+This document defines an integration reference point (IRP) through which an 'IRPAgent' (typically an element manager or network element) can communicate network management-related information to one or several 'IRPManagers' (typically network managers).
+
+This document specifies an inventory management network resource model (NRM) (also referred to as a management information model – MIM) with definitions of information object classes.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 692 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 692 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532692v800 |
+| ATIS | ATIS.3GPP.32.692V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.692(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.692(R8-8.0.0) |
+| TTC | TS-3GA-32.692(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32692rel8v800.pdf |
+
+### 10.10.137 TS 32.695 Telecommunication management; Inventory management (IM) network resource model (NRM) integration reference point (IRP): Bulk CM eXtensible markup language (XML) file format definition
+
+The document provides the NRM-specific part related to the inventory management NRM IRP IS 3GPP TS 32.692 of the XML file format definition for the bulk configuration management IRP IS 3GPP TS 32.612.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 695 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 695 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532695v800 |
+| ATIS | ATIS.3GPP.32.695V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.695(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.695(R8-8.0.0) |
+| TTC | TS-3GA-32.695(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32695rel8v800.pdf |
+
+**10.10.138 TS 32.711 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) integration reference point (IRP): Requirements**
+
+The document defines the requirements for the present IRP: Transport network (TN) interface network resource model (NRM) integration reference point.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 711 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 711 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532711v800 |
+| ATIS | ATIS.3GPP.32.711V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.711(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.711(R8-8.0.0) |
+| TTC | TS-3GA-32.711(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32711rel8v800.pdf |
+
+**10.10.139 TS 32.712 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) integration reference point (IRP): Information service (IS)**
+
+This document is part of an integration reference point (IRP) named "Transport Network (TN) interface network resource model (NRM) IRP", through which an "IRPAgent" (typically an element manager or network element) can communicate configuration management information to one or several "IRPManagers" (typically network managers) concerning transport resources. The "Transport Network (TN) Interface Network Resource Model (NRM) IRP" comprises a set of specifications defining Requirements, a protocol-neutral network resource model (NRM) and corresponding solution set(s).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 712 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 712 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532712v800 |
+| ATIS | ATIS.3GPP.32.712V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.712(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.712(R8-8.0.0) |
+| TTC | TS-3GA-32.712(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32712rel8v800.pdf |
+
+**10.10.140 TS 32.713 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of this transport network (TN) interface network resource model IRP: CORBA solution set is to define the mapping of the IRP information model (see 3G TS 32.712) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 713 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 713 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532713v800 |
+| ATIS | ATIS.3GPP.32.713V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.713(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.713(R8-8.0.0) |
+| TTC | TS-3GA-32.713(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32713rel8v800.pdf |
+
+**10.10.141 TS 32.715 Telecommunication management; Configuration management (CM); Transport network (TN) interface network resource model (NRM) integration reference point (IRP): Bulk CM eXtensible markup language (XML) file format definition**
+
+The document provides the NRM-specific part related to 3G TS 32.712 transport network (TN) interface NRM IRP IS of the XML file format definition for the 3G TS 32.612 bulk configuration management IRP IS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 715 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 715 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532715v800 |
+| ATIS | ATIS.3GPP.32.715V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.715(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.715(R8-8.0.0) |
+| TTC | TS-3GA-32.715(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32715rel8v800.pdf |
+
+#### **10.10.142 TS 32.721 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3GPP TS 32.101, 3GPP TS 32.102 and 3GPP TS 32.600, the requirements for the present repeater network resources IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 721 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 721 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532721v800 |
+| ATIS | ATIS.3GPP.32.721V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.721(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.721(R8-8.0.0) |
+| TTC | TS-3GA-32.721(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32721rel8v800.pdf |
+
+#### **10.10.143 TS 32.722 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP): Information service (IS)**
+
+This document is part of an integration reference point (IRP) named "Repeater Network Resources IRP", through which an "IRPAgent" (typically an element manager or network element) can communicate configuration management information to one or several "IRPManagers" (typically network managers) concerning repeater resources. The "Repeater Network Resources IRP" comprises a set of specifications defining Requirements, a protocol neutral network resource model (NRM) and corresponding solution set(s).
+
+The document specifies the protocol neutral repeater network resources IRP: Network resource model. It reuses relevant parts of the generic NRM in TS 32.622 and 32.642, either by direct reuse or sub-classing, and, in addition to that, defines repeater-specific information object classes.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 722 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 722 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532722v800 |
+| ATIS | ATIS.3GPP.32.722V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.722(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.722(R8-8.0.0) |
+| TTC | TS-3GA-32.722(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32722rel8v800.pdf |
+
+**10.10.144 TS 32.723 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of this repeater network resources IRP: CORBA solution set is to define the mapping of the IRP information model (see 3GPP TS 32.722) to the protocol-specific details necessary for the implementation of this IRP in a CORBA/IDL environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 723 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 723 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532723v800 |
+| ATIS | ATIS.3GPP.32.723V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.723(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.723(R8-8.0.0) |
+| TTC | TS-3GA-32.723(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32723rel8v800.pdf |
+
+**10.10.145 TS 32.725 Telecommunication management; Configuration management (CM); Repeater network resources integration reference point (IRP): Bulk CM eXtensible markup language (XML) file format definition**
+
+This document provides the NRM-specific part related to the repeater network resources IRP NRM (3GPP TS 32.722) of the XML file format definition for the bulk configuration management IRP IS (3GPP TS 32.612).
+
+The main part of this XML file format definition is provided by 3GPP TS 32.615.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 725 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 725 | 8.0.0 | Published | 2009-01-30 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532725v800 |
+| ATIS | ATIS.3GPP.32.725V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.725(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.725(R8-8.0.0) |
+| TTC | TS-3GA-32.725(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32725rel8v800.pdf |
+
+#### **10.10.146 TS 32.731 Telecommunication management; IP multimedia subsystem (IMS) network resource model (NRM) integration reference point (IRP): Requirements**
+
+This document defines, in addition to the requirements defined in 3GPP TS 32.101, 3GPP TS 32.102 and 3GPP TS 32.600, the requirements for the IMS network resource model (NRM) IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 731 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 731 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532731v800 |
+| ATIS | ATIS.3GPP.32.731V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.731(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT.3G-32.731(R8-8.0.0) |
+| TTC | TS-3GA-32.731(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32731rel8v800.pdf |
+
+#### **10.10.147 TS 32.732 Telecommunication management; IP multimedia subsystem (IMS) network resource model (NRM) integration reference point (IRP): Information service (IS)**
+
+This document is part of an integration reference point (IRP) named IMS network resource model (NRM) IRP, through which an IRP Agent can communicate configuration management information to one or several IRP Managers concerning IMS resources. The IMS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral information service and one or more solution set(s).
+
+The document specifies the protocol neutral IMS NRM IRP: Information service (IS). It reuses relevant parts of the generic NRM IRP: IS in 3GPP TS 32.622, either by direct reuse or sub-classing, and, in addition to that, defines IMS-specific information object classes.
+
+Finally, in order to access the information defined by this NRM, an interface IRP is needed, such as the basic CM IRP in 3GPP TS 32.602. However, which interface IRP is applicable is outside the scope of the present document.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 732 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 732 | 8.1.0 | Published | 2009-01-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532732v810 |
+| ATIS | ATIS.3GPP.32.732V810-2009 | 8.1.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.732(R8-8.1.0) | 8.1.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.732(R8-8.1.0) |
+| TTC | TS-3GA-32.732(Rel8)v8.1.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32732rel8v810.pdf |
+
+**10.10.148 TS 32.733 Telecommunication management; IP multimedia subsystem (IMS) network resource model (NRM) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of this *IMS NRM IRP: CORBA Solution Set* is to define the mapping of the IRP information service (see TS 32.732) to the protocol-specific details necessary for the implementation of this IRP in a CORBA/IDL environment.
+
+This solution set specification is related to 3GPP TS 32.732.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 733 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 733 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532733v800 |
+| ATIS | ATIS.3GPP.32.733V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.733(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.733(R8-8.0.0) |
+| TTC | TS-3GA-32.733(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32733rel8v800.pdf |
+
+**10.10.149 TS 32.735 Telecommunication management; IP multimedia subsystem (IMS) network resource model (NRM) integration reference point (IRP): eXtensible markup language (XML) file format definition**
+
+The document provides the NRM-specific part related to the IMS NRM IRP (3GPP TS 32.732) of the XML file format definition for the bulk configuration management IRP IS (3GPP TS 32.612).
+
+The main part of this XML file format definition is provided by 3GPP TS 32.615.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 735 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 735 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532735v800 |
+| ATIS | ATIS.3GPP.32.735V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.735(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.735(R8-8.0.0) |
+| TTC | TS-3GA-32.735(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32735rel8v800.pdf |
+
+**10.10.150 TS 32.741 Telecommunication management; Configuration management (CM); Signalling transport network (STN) interface network resource model (NRM) integration reference point (IRP): Requirements**
+
+The document defines the requirements for the signalling transport network (STN) interface NRM IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 741 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 741 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532741v800 |
+| ATIS | ATIS.3GPP.32.741V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.741(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.741(R8-8.0.0) |
+| TTC | TS-3GA-32.741(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32741rel8v800.pdf |
+
+**10.10.151 TS 32.742 Telecommunication management; Configuration management (CM); Signalling transport network (STN) interface network resource model (NRM) integration reference point (IRP): Information service (IS)**
+
+This document is part of an integration reference point (IRP) named "Signalling Transport Network (STN) network resources IRP", through which an "IRPAgent" (typically an element manager or network element) can communicate configuration management information to one or several "IRPManagers" (typically network managers) concerning signalling transport resources. The "Signalling Transport Network (STN) network resources IRP" comprises a set of specifications defining Requirements, a protocol-neutral network resource model (NRM) and corresponding solution set(s).
+
+The document specifies the protocol-neutral STN resources IRP: Network resource model.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 742 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 742 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532742v800 |
+| ATIS | ATIS.3GPP.32.742V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.742(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.742(R8-8.0.0) |
+| TTC | TS-3GA-32.742(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32742rel8v800.pdf |
+
+**10.10.152 TS 32.743 Telecommunication management; Configuration management (CM); Signalling transport network (STN) interface network resource model (NRM) integration reference point (IRP): Common object request broker architecture (CORBA) solution set (SS)**
+
+The purpose of this STN network resources IRP: CORBA solution set is to define the mapping of the IRP information model (see 3G TS 32.742) to the protocol-specific details necessary for implementation of this IRP in a CORBA/IDL environment.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 743 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 743 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532743v800 |
+| ATIS | ATIS.3GPP.32.743V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.743(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.743(R8-8.0.0) |
+| TTC | TS-3GA-32.743(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32743rel8v800.pdf |
+
+**10.10.153 TS 32.745 Telecommunication management; Configuration management (CM); Signalling transport network (STN) interface network resource model (NRM) integration reference point (IRP): Bulk CM eXtensible markup language (XML) file format definition**
+
+This document provides the NRM-specific part related to the STN network resources IRP NRM 3G TS 32.742 of the XML file format definition for the bulk configuration management IRP IS 3G TS 32.612.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-132 745 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 132 745 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0532745v800 |
+| ATIS | ATIS.3GPP.32.745V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.745(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.745(R8-8.0.0) |
+| TTC | TS-3GA-32.745(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32745rel8v800.pdf |
+
+#### **10.10.154 TS 32.751 Telecommunication management; Evolved packet core (EPC) network resource model (NRM) integration reference point (IRP); Requirements**
+
+The document defines, in addition to the requirements defined in 3GPP TS 32.101, TS 32.102 and TS 32.600, the Requirements for the EPC network resource model (NRM) IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 751 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532751v800 |
+| ATIS | ATIS.3GPP.32.751V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.751(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.751(R8-8.0.0) |
+| TTC | TS-3GA-32.751(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32751rel8v800.pdf |
+
+#### **10.10.155 TS 32.761 Telecommunication management; Evolved universal terrestrial radio access network (E-UTRAN) network resource model (NRM) integration reference point (IRP); Requirements**
+
+The document defines, in addition to the requirements defined in 3GPP TS 32.101, TS 32.102 and TS 32.600, the Requirements for the E-UTRAN network resource model (NRM) IRP.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ETSI | TS 132 761 | 8.0.0 | Published | 2009-01-29 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0532761v800 |
+| ATIS | ATIS.3GPP.32.761V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-32.761(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-32.761(R8-8.0.0) |
+| TTC | TS-3GA-32.761(Rel8)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts32761rel8v800.pdf |
+
+## 10.11 33-series, Security aspects
+
+### 10.11.1 TS 33.102 3G security; Security architecture
+
+This specification defines the security architecture, i.e., the security features and the security mechanisms, for the third generation mobile telecommunication system.
+
+A security feature is a service capability that meets one or several security requirements. The complete set of security features addresses the security requirements as they are defined in "3G Security: Threats and Requirements" (TS 21.133) and implement the security objectives and principles described in TS 33.120. A security mechanism is an element that is used to realize a security feature. All security features and security mechanisms taken together form the security architecture.
+
+An example of a security feature is user data confidentiality. A security mechanism that may be used to implement that feature is a stream cipher using a derived cipher key.
+
+This specification defines 3G security procedures performed within 3G capable networks (R99+), i.e., intra-UMTS and UMTS-GSM. As an example, UMTS authentication is applicable to UMTS radio access as well as GSM radio access provided that the serving network node and the MS are UMTS capable. Interoperability with non-UMTS capable networks (R98-) is also covered.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.102 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33102-810.pdf |
+| CCSA | CCSA-TSD-133 102 | 8.2.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 102 | 8.1.0 | Published | 2009-01-09 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333102v810 |
+| ATIS | ATIS.3GPP.33.102V810-2009 | 8.1.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.102(R8-8.1.0) | 8.1.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT_3G-33.102(R8-8.1.0) |
+
+### 10.11.2 TS 33.105 3G security; Cryptographic algorithm requirements
+
+This specification constitutes a requirements specification for the security functions which may be used to provide the network access security features defined in 3G TS 33.102.
+
+The specification covers the intended use of the functions, the technical requirements on the functions and the requirements as regards standardization.
+
+For those functions that require standardization, it also covers the intended use of the algorithm specification, the requirements on test data, and quality assurance requirements on both the algorithm and its documentation.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.105 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33105-800.pdf |
+| CCSA | CCSA-TSD-133 105 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 105 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333105v800 |
+| ATIS | ATIS.3GPP.33.105V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.105(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.105(R8-8.0.0) |
+
+### 10.11.3 TS 33.106 Lawful interception requirements
+
+The document provides basic interception requirements within a third generation mobile communication system (3GMS).
+
+The specification describes the service requirements from a law enforcement point of view only. The aim of this document is to define a 3GMS interception system that supports a number of regional interception regulations, but these regulations are not repeated here as they vary. Regional interception requirements shall rely on this specification to derive such information, as they require.
+
+These interception requirements shall be used to derive specific network requirements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.106 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33106-810.pdf |
+| CCSA | CCSA-TSD-133 106 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 106 | 8.1.0 | Published | 2008-10-28 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333106v810 |
+| ATIS | ATIS.3GPP.33.106V810-2009 | 8.1.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.106(R8-8.1.0) | 8.1.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.106(R8-8.1.0) |
+
+### 10.11.4 TS 33.107 3G security; Lawful interception architecture and functions
+
+The document describes the architecture and functional requirements within a third generation mobile communication system (3GMS).
+
+The specification shows the service requirements from a law enforcement point of view only. The aim of this document is to define a 3GMS interception system that supports a number of regional interception regulations, but these regulations are not repeated here as they vary. Regional interception requirements shall be met in using specific (regional) mediation functions allowing only required information to be transported.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.107 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33107-860.pdf |
+| CCSA | CCSA-TSD-133 107 | 8.7.1 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 107 | 8.6.0 | Published | 2009-01-09 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333107v860 |
+| ATIS | ATIS.3GPP.33.107V860-2009 | 8.6.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.107(R8-8.6.0) | 8.6.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.107(R8-8.6.0) |
+
+#### 10.11.5 TS 33.108 3G security; Handover interface for lawful interception (LI)
+
+This specification addresses the handover interfaces for lawful interception of packet-data services, circuit-switched services, and multimedia services within the UMTS network. The handover interface in this context includes the delivery of intercept related information (HI2) and content of communication (HI3) to the law enforcement monitoring facility.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.108 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33108-850.pdf |
+| CCSA | CCSA-TSD-133 108 | 8.6.1 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 108 | 8.5.0 | Published | 2009-01-09 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333108v850 |
+| ATIS | ATIS.3GPP.33.108V850-2009 | 8.5.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.108(R8-8.5.0) | 8.5.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.108(R8-8.5.0) |
+
+#### 10.11.6 TS 33.110 Key establishment between a universal integrated circuit card (UICC) and a terminal
+
+This document describes the security features and mechanisms to provision a shared key between a UICC and a terminal that may host the UICC or be connected to the device hosting the UICC via a local interface. Candidate applications to use this key establishment mechanism include, but are not restricted to, secure channel between a UICC and a terminal [ETSI TS 102 484].
+
+The scope of this specification includes an architecture overview and the detailed procedure how to establish the shared key between the UICC and the terminal.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.110 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33110-800.pdf |
+| CCSA | CCSA-TSD-133 110 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 110 | 8.0.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333110v800 |
+| ATIS | ATIS.3GPP.33.110V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.110(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.110(R8-8.0.0) |
+
+### 10.11.7 TS 33.141 Presence service; Security
+
+This document is the Stage 2 specification for the security requirements, security architecture, security features and security mechanisms for the presence service, which includes the elements necessary to realize the requirements in 3G TS 22.141 and 3G TS 23.141. As far as SIP-based procedures are concerned, this specification refers to 3G TS 33.203. The main content of this specification is the security for the Ut reference point, which is HTTP based, as applied in presence services.
+
+The document includes information applicable to network operators, service providers and manufacturers.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.141 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33141-810.pdf |
+| CCSA | CCSA-TSD-133 141 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 141 | 8.1.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333141v810 |
+| ATIS | ATIS.3GPP.33.141V810-2009 | 8.1.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.141(R8-8.1.0) | 8.1.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.141(R8-8.1.0) |
+
+### 10.11.8 TS 33.203 3G security; Access security for IP-based services
+
+The scope for this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system.
+
+The IMS in UMTS will support IP multimedia applications such as video, audio and multimedia conferences. Session initiation protocol (SIP [IETF RFC 3261]) has been chosen as the signalling protocol for creating and terminating multimedia sessions. This specification only deals with how the SIP signalling is protected between the subscriber and the IMS, how the subscriber is authenticated and how the subscriber authenticates the IMS.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.203 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33203-850.pdf |
+| CCSA | CCSA-TSD-133 203 | 8.5.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 203 | 8.5.0 | Published | 2009-01-09 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333203v850 |
+| ATIS | ATIS.3GPP.33.203V850-2009 | 8.5.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.203(R8-8.5.0) | 8.5.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.203(R8-8.5.0) |
+
+### 10.11.9 TS 33.204 3G Security; Network domain security (NDS); Transaction capabilities application part (TCAP) user security
+
+This technical specification covers the security mechanisms and procedures necessary to protect all TCAP user messages which are sent between different security domains. The complete set of enhancements and extensions to facilitate security protection for the TCAP protocol is termed TCAPsec and it covers transport security in the TCAP protocol itself and the security management procedures.
+
+This technical specification contains the stage 2 specification for security protection of the TCAP protocol. The actual implementation (stage 3) specification can be found in TS 29.204.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|---------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-133 204 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 204 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333204v800 |
+| ATIS | ATIS.3GPP.33.204V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.204(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.204(R8-8.0.0) |
+| TTC | TS-3GA-33.204(Rel8)v8.0.0 | 1 | TTC Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/ts/ts33204rel8v800.pdf |
+
+### 10.11.10 TS 33.210 3G security; Network domain security (NDS); IP network layer security
+
+This document defines the security architecture for the UMTS network domain IP-based control plane. The scope of the UMTS network domain control plane security is to cover the control signalling on selected interfaces between UMTS network elements.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.210 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33210-820.pdf |
+| CCSA | CCSA-TSD-133 210 | 8.2.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 210 | 8.2.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333210v820 |
+| ATIS | ATIS.3GPP.33.210V820-2009 | 8.2.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.210(R8-8.2.0) | 8.2.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.210(R8-8.2.0) |
+
+### 10.11.11 TS 33.220 Generic authentication architecture (GAA); Generic bootstrapping architecture
+
+This document describes the security features and a mechanism to bootstrap authentication and key agreement for application security from the 3GPP AKA mechanism. Candidate applications to use this bootstrapping mechanism include, but are not restricted to, subscriber certificate distribution 3GPP TS 33.221. Subscriber certificates support services whose provision the mobile operator assists, as well as services that are offered by the mobile operator.
+
+The scope of this specification includes a generic AKA bootstrapping function, an architecture overview and the detailed procedure how to bootstrap the credential.
+
+Clause 4 of this specification describes a mechanism, called GBA\_ME, to bootstrap authentication and key agreement, which does not require any changes to the UICC. Clause 5 of this specification describes a mechanism, called GBA\_U, to bootstrap authentication and key agreement, which does require changes to the UICC, but provides enhanced security by storing certain derived keys on the UICC.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.220 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33220-850.pdf |
+| CCSA | CCSA-TSD-133 220 | 8.6.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 220 | 8.5.0 | Published | 2009-01-09 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333220v850 |
+| ATIS | ATIS.3GPP.33.220V850-2009 | 8.5.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.220(R8-8.5.0) | 8.5.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.220(R8-8.5.0) |
+
+### 10.11.12 TS 33.221 Generic authentication architecture (GAA); Support for subscriber certificates
+
+This document describes subscriber certificate distribution by means of generic bootstrapping architecture (GBA) 3GPP TS 33.220. Subscriber certificates support services whose provision the mobile operator assists, as well as services that are offered by the mobile operator.
+
+The scope of this specification presents signalling procedures for support of issuing certificates to subscribers and the standard format of certificates and digital signatures. It is not intended to duplicate existing standards being developed by other groups on these topics, and will reference these, where appropriate.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.221 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33221-800.pdf |
+| CCSA | CCSA-TSD-133 221 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 221 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333221v800 |
+| ATIS | ATIS.3GPP.33.221V 800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.221(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.221(R8-8.0.0) |
+
+### 10.11.13 TS 33.222 Generic authentication architecture (GAA); Access to network application functions using hypertext transfer protocol over transport layer security (HTTPS)
+
+The document specifies secure access methods to network application functions (NAFs) using HTTP over TLS in the generic authentication architecture (GAA), and provides Stage 2 security requirements, principles and procedures for the access. The present document describes both direct access to an application server (AS) and access to an application server through an authentication proxy (AP).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.222 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33222-800.pdf |
+| CCSA | CCSA-TSD-133 222 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 222 | 8.0.0 | Published | 2009-01-19 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333222v800 |
+| ATIS | ATIS.3GPP.33.222V 800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.222(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.222(R8-8.0.0) |
+
+### 10.11.14 TS 33.223 Generic authentication architecture (GAA); Generic bootstrapping architecture (GBA) push function
+
+The present document specifies a Push Function as a functional add-on for the generic authentication architecture (GAA) described in 3GPP TS 33.220.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.223 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33223-820.pdf |
+| ETSI | TS 133 223 | 8.2.0 | Published | 2009-01-20 | http://pda.etsi.org/pda/home.asp?wkr=DTS/TSGS-0333223v820 |
+| ATIS | ATIS.3GPP.33.223V820-2009 | 8.2.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.223(R8-8.2.0) | 8.2.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.223(R8-8.2.0) |
+
+### 10.11.15 TS 33.234 3G security; Wireless local area network (WLAN) interworking security
+
+This document specifies the security architecture, trust model and security requirements for the interworking of the 3GPP System and WLAN access networks.
+
+Specifications of the appropriate mechanisms for user and network authentication, key management, service authorization, confidentiality and integrity protection of user and signalling data are also provided.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.234 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33234-810.pdf |
+| CCSA | CCSA-TSD-133 234 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/fi les.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 234 | 8.1.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333234v810 |
+| ATIS | ATIS.3GPP.33.234V810-2009 | 8.1.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.234(R8-8.1.0) | 8.1.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.234(R8-8.1.0) |
+
+### 10.11.16 TS 33.246 3G security; Security of multimedia broadcast/multicast service
+
+The Technical Specification covers the security procedures of the multimedia broadcast/multicast service (MBMS) for 3GPP systems (UTRAN and GERAN). MBMS is a 3GPP system network bearer service over which many different applications could be carried. The actual method of protection may vary depending on the type of MBMS application.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.246 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33246-820.pdf |
+| CCSA | CCSA-TSD-133 246 | 8.3.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 246 | 8.2.0 | Published | 2009-01-09 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333246v820 |
+| ATIS | ATIS.3GPP.33.246V820-2009 | 8.2.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.246(R8-8.2.0) | 8.2.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.246(R8-8.2.0) |
+
+### 10.11.17 TS 33.259 Key establishment between a UICC hosting device and a remote device
+
+This document describes the security features and mechanisms to provision a shared key between a UICC hosting device and a remote device connected via a local interface. The shared secret is then intended to be used to secure the interface between the remote device and the UICC hosting device. Candidate applications to use this key establishment mechanism include, but are not restricted to, personal network management (see TS 22.259).
+
+The scope of this specification includes an architecture overview and the detailed procedure on how to establish the shared key between the UICC hosting device and the remote device. This is different from Technical Specification TS 33.110 that describes an architecture overview and the detailed procedure on how to establish the shared key between the UICC itself and the terminal hosting the UICC. The use cases utilizing the mechanisms described in this specification are seen to be different to the use cases where "Key establishment between a UICC and a terminal", IETF RFC 4279, is utilized.
+
+The solution described in this document is built on the existing infrastructure defined in "GBA", TS 33.220.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.259 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33259-820.pdf |
+| CCSA | CCSA-TSD-133 259 | 8.2.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 133 259 | 8.2.0 | Published | 2009-01-26 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333259v820 |
+| ATIS | ATIS.3GPP.33.259V820-2009 | 8.2.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.259(R8-8.2.0) | 8.2.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.259(R8-8.2.0) |
+
+### 10.11.18 TS 33.310 Network domain security (NDS); Authentication framework (AF)
+
+For 3GPP systems, there is a need for truly scalable entity authentication framework (AF) since an increasing number of network elements and interfaces are covered by security mechanisms.
+
+This specification provides a highly scalable entity authentication framework for 3GPP network nodes. This framework is developed in the context of the network domain security work item, which effectively limits the scope to the control plane entities of the core network. Thus, *the Authentication Framework will provide entity authentication for the nodes that are using NDS/IP.*
+
+Feasible trust models (i.e., how CAs are organized) and their effects are provided. Additionally, requirements are presented for the used protocols and certificate profiles, to make it possible for operator IPsec and PKI implementations to interoperate.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|------------------|---------|----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-133 310 | 8.2.1 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+
+### 10.11.19 TS 33.401 3GPP system architecture evolution (SAE); Security architecture
+
+This document specifies the security architecture, i.e., the security features and the security mechanisms for the evolved packet system and the evolved packet core, and the security procedures performed within the evolved packet system (EPS) including the evolved packet core (EPC) and the evolved UTRAN (E-UTRAN).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.401 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33401-821.pdf |
+| ETSI | TS 133 401 | 8.2.1 | Published | 2009-01-09 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333401v821 |
+| ATIS | ATIS.3GPP.33.401V821-2009 | 8.2.1 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.401(R8-8.2.1) | 8.2.1 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.401(R8-8.2.1) |
+
+### 10.11.20 TS 33.402 3GPP System architecture evolution (SAE); Security aspects of non-3GPP accesses
+
+The present document specifies the security architecture, i.e., the security feature groups and the security mechanisms performed during interworking between non-3GPP accesses and the evolved packet system (EPS).
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-33.402 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33402-821.pdf |
+| ETSI | TS 133 402 | 8.2.1 | Published | 2009-01-15 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0333402v821 |
+| ATIS | ATIS.3GPP.33.402V821-2009 | 8.2.1 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.402(R8-8.2.1) | 8.2.1 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.402(R8-8.2.1) |
+
+## 10.11.21 TR 33.905 Recommendations for trusted open platforms
+
+This technical report investigates relevant trust standards and technologies, both existing as well as the ones that are work-in-progress. It develops the recommendations for trusted open platforms for the delivery of new applications and services to open platforms.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-133 905 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TR 133 905 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0333905v800 |
+| ATIS | ATIS.3GPP.33.905V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.905(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.905(R8-8.0.0) |
+| TTC | TR-3GA-33.905(Re18)v8.0.0 | 1 | TTC
Published | 2009-02-25 | http://www.ttc.or.jp/imt2000/tr/tr33905rel8v800.pdf |
+
+## 10.11.22 TR 33.919 3G security; Generic authentication architecture (GAA); System description
+
+This 3GPP Technical Report aims to give an overview of the different mechanisms that mobile applications can rely upon for authentication between the server and the client (i.e., the UE). Additionally, it provides guidelines related to the use of GAA and to the choice of authentication mechanism in a given situation and for a given application.
+
+To this end, the TR puts the different GAA specifications that are related to peer authentication into perspective. It clarifies the logic for having three technical specifications, sketches their content and explains the interrelation between these three TSs and their relation with this TR.
+
+
+
+| | | | | |
+|---------------------------------|----------------------------------|--------------------------|-----------------------------------------------|-------------------------|
+| Interfaces and specifications { | GAA System Description TR 33.919 | | | |
+| | GAA SSC 33.221 | GAA HTTPS TS 33.222 | GAA GBA TS 33.220 | |
+| | | | GAA Ub & Ua TS 24.109 | GAA Zh and Zn TS 29.109 |
+| | Ua | Ub | Zh | Zn |
+| | HTTP Digest RFC 2617 (Note) | HTTP Digest AKA RFC 3310 | IMS Cx Diameter message definitions TS 29.229 | |
+| | HTTP | | Diameter Base Protocol RFC 3588 | |
+| | TCP | | SCTP | |
+| | IP | | | |
+
+Diagram showing the relationships between GAA specifications and the protocols used by GAA interfaces. The diagram is a hierarchical tree structure. At the top is 'GAA System Description TR 33.919'. Below it, 'GAA GBA TS 33.220' branches into 'GAA SSC 33.221' and 'GAA HTTPS TS 33.222'. 'GAA SSC 33.221' branches into 'GAA Ub & Ua TS 24.109' and 'GAA Zh and Zn TS 29.109'. 'GAA HTTPS TS 33.222' branches into 'Ua', 'Ub', 'Zh', and 'Zn'. 'Ua' branches into 'HTTP Digest RFC 2617 (Note)'. 'Ub' branches into 'HTTP Digest AKA RFC 3310'. 'Zh' and 'Zn' both branch into 'IMS Cx Diameter message definitions TS 29.229'. Below these, 'HTTP' branches into 'TCP'. 'Diameter Base Protocol RFC 3588' branches into 'SCTP'. Both 'TCP' and 'SCTP' branch into 'IP'.
+
+Q.1741.6(09)\_F10.11.22-1
+
+NOTE – The GAA supports potentially many protocols on the Ua interface. One example is the HTTP digest.
+
+**Figure 10.11.22-1 – Relationships between GAA specifications and the protocols used by GAA interfaces**
+
+Figure 10.11.22-1 depicts protocols used over GAA interfaces and the relationships between different GAA specifications. New GAA specifications will be added to the figure as they become available. Also, other protocols may be added in the future. In particular, new kinds of Ua interfaces could be added in the future and then other protocols may be added below the Ua interface.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB-TR-T12-33.919 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33919-800.pdf |
+| CCSA | CCSA-TSD-133 919 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TR 133 919 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0333919v800 |
+| ATIS | ATIS.3GPP.33.919V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.919(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.919(R8-8.0.0) |
+
+### 10.11.23 TR 33.978 Security aspects of early IP multimedia subsystem (IMS)
+
+The present document documents an interim security solution for early IMS implementations that are not fully compliant with the IMS security architecture specified in TS 33.203. For security reasons, the provisions in this TR only apply to IMS procedures used over the 3GPP PS domain.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB-TR-T12-33.978 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33978-800.pdf |
+| CCSA | CCSA-TSD-133 978 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TR 133 978 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0333978v800 |
+| ATIS | ATIS.3GPP.33.978V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.978(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.978(R8-8.0.0) |
+
+### 10.11.24 TR 33.980 Liberty alliance and 3GPP security interworking; Interworking of liberty alliance identity federation framework (ID-FF), Identity web services framework (ID-WSF) and generic authentication architecture (GAA)
+
+The present document provides guidelines on the interworking of the generic authentication architecture (GAA) and the liberty alliance architecture. The document studies the details of possible interworking methods between the security assertion markup language v2.0, SAML v2.0 (or alternatively the liberty alliance identity federation framework, ID-FF), the identity web services framework (ID-WSF), the security assertion markup language (SAML) and a component of GAA
+
+called the generic bootstrapping architecture (GBA). This document only applies if liberty alliance and GBA or SAML v2.0 and GBA are used in combination.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB-TR-T12-33.980 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A33980-800.pdf |
+| CCSA | CCSA-TSD-133 980 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TR 133 980 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0333980v800 |
+| ATIS | ATIS.3GPP.33.980V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-33.980(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-33.980(R8-8.0.0) |
+
+## 10.12 35-series, Algorithm specifications
+
+### 10.12.1 TS 35.201 Specification of the 3GPP confidentiality and integrity algorithms; Document 1: *f8* and *f9* specifications
+
+This specification gives a detailed specification of the confidentiality algorithm *f8*, and the integrity algorithm *f9*.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.201 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A35201-800.pdf |
+| CCSA | CCSA-TSD-135 201 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 135 201 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335201v800 |
+| ATIS | ATIS.3GPP.35.201V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-35.201(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-35.201(R8-8.0.0) |
+
+### 10.12.2 TS 35.202 Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification
+
+This specification gives a detailed specification of the Algorithm KASUMI. KASUMI is a block cipher that forms the heart of the confidentiality algorithm *f8*, and the integrity algorithm *f9*.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.202 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A35202-800.pdf |
+| CCSA | CCSA-TSD-135 202 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 135 202 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335202v800 |
+| ATIS | ATIS.3GPP.35.202V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-35.202(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-35.202(R8-8.0.0) |
+
+### 10.12.3 TS 35.205 3G security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f_1, f_1^*, f_2, f_3, f_4, f_5$ and $f_5^*$ ; Document 1: General
+
+This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the Milenage algorithm set: an example set of authentication and key generation functions.
+
+The authentication and key generation functions are not standardized. An example set of these algorithms has been produced with the intent that it shall be offered to the UMTS operators, to utilize instead of developing their own. An ETSI SAGE Task Force has carried out this work.
+
+The requirement specification stated that operator personalization of the example set must be possible and that the basic Kernel must be possible to replace.
+
+The example set is based on the block cipher Rijndael, which at the time was one of the AES candidates, and the specification describes how the seven algorithms used in 3GPP authentication and key generation are scheduled around this basic Kernel. The specification and associated test data for the example algorithm set is documented in three documents:
+
+- A formal specification of both the modes and the example Kernel TS 35.206;
+- A detailed test data document, covering modes and the example Kernel TS 35.207;
+- A "black box" test data document TS 35.208.
+
+This report gives an overview of the overall work by the task force.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-135 205 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 135 205 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335205v800 |
+| ATIS | ATIS.3GPP.35.205V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-35.205(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-35.205(R8-8.0.0) |
+
+#### 10.12.4 TS 35.206 3G security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 2: Algorithm specification
+
+This document contains an example set of algorithms which may be used as the authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ . (It is not mandatory that the particular algorithms specified in this document are used – all seven functions are operator-specifiable rather than being fully standardized.)
+
+The algorithms specified in this document are examples that may be used by an operator who does not wish to design his own.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-135 206 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 135 206 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335206v800 |
+| ATIS | ATIS.3GPP.35.206V 800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-35.206(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-35.206(R8-8.0.0) |
+
+#### 10.12.5 TS 35.215 Specification of the 3GPP confidentiality and integrity algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|----------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.215 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A35215-800.pdf |
+| CCSA | CCSA-TSD-135 215 | 8.1.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 135 215 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335215v800 |
+| ATIS | ATIS.3GPP.35.215V 800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-35.215(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-35.215(R8-8.0.0) |
+
+### 10.12.6 TS 35.216 Specification of the 3GPP confidentiality and integrity algorithms UEA2 & UIA2; Document 2: SNOW 3G specification
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB STD-T63-35.216 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A35216-800.pdf |
+| CCSA | CCSA-TSD-135 216 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TS 135 216 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGS-0335216v800 |
+| ATIS | ATIS.3GPP.35.216V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-35.216(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-35.216(R8-8.0.0) |
+
+### 10.12.7 TR 35.909 3G security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions $f_1$ , $f_1^*$ , $f_2$ , $f_3$ , $f_4$ , $f_5$ and $f_5^*$ ; Document 5: Summary and results of design and evaluation
+
+This report contains a detailed summary of the work performed during the design and evaluation of the 3G authentication functions denoted as the MILENAGE algorithm set.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|---------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CCSA | CCSA-TSD-135 909 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TR 135 909 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0335909v800 |
+| ATIS | ATIS.3GPP.35.909V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-35.909(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDown.jsp?where=14688&pk_num=TTAT_3G-35.909(R8-8.0.0) |
+
+### **10.12.8 TR 35.919 Specification of the 3GPP confidentiality and integrity algorithms UEA2 & UIA2; Document 5: Design and evaluation report**
+
+This document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2.
+
+| | Document No. | Version | Status | Issued date | Location |
+|------|---------------------------|----------------|----------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ARIB | ARIB TR-T12-35.919 | 7.20 | ARIB published | 2009-3-18 | http://www.arib.or.jp/IMT-2000/ARIB-STD/ITU-T_Rev9/Rel8/A35919-800.pdf |
+| CCSA | CCSA-TSD- 135 919 | 8.0.0 | Approved | 2009-4-31 | http://www.ccsa.org.cn/english/tc/files.php?docpath=/ITU-T/Q.1741/Q.1741-6/ |
+| ETSI | TR 135 919 | 8.0.0 | Published | 2009-02-03 | http://pda.etsi.org/pda/home.asp?wkr=RTR/TSGS-0335919v800 |
+| ATIS | ATIS.3GPP.35.919V800-2009 | 8.0.0 | Published | July 2009 | https://www.atis.org/docstore |
+| TTA | TTAT.3G-35.919(R8-8.0.0) | 8.0.0 | Approved | 2009-07-17 | http://www.tta.or.kr/data/ttasDownload.jsp?where=14688&pk_num=TTAT.3G-35.919(R8-8.0.0) |
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+- Series A Organization of the work of ITU-T
+- Series D General tariff principles
+- Series E Overall network operation, telephone service, service operation and human factors
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media, digital systems and networks
+- Series H Audiovisual and multimedia systems
+- Series I Integrated services digital network
+- Series J Cable networks and transmission of television, sound programme and other multimedia signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M Telecommunication management, including TMN and network maintenance
+- Series N Maintenance: international sound programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Terminals and subjective and objective assessment methods
+- Series Q Switching and signalling**
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminals for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks, open system communications and security
+- Series Y Global information infrastructure, Internet protocol aspects and next-generation networks
+- Series Z Languages and general software aspects for telecommunication systems
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/008b6e24fa6aef654a11223efed035dd_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/008b6e24fa6aef654a11223efed035dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bdec1ea1573dd6acd6335d97afaf1170f210e5e4
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/008b6e24fa6aef654a11223efed035dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f553016e9ab71dc6a3493fd703ae506154e40df8c130fcf8557de1c8a219fb47
+size 32312
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/11728b408ca6402f502858c9bc161c4a_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/11728b408ca6402f502858c9bc161c4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03a83c35c0757b043b064670d44a231f29dd24fd
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/11728b408ca6402f502858c9bc161c4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7c6b96f1fc1f1976d0dffbd2fc6837b83e533c49401d03599c76246b3c5ca03
+size 13248
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c
+size 8232
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/391ab9e5616ba6311161af4d7a93422b_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/391ab9e5616ba6311161af4d7a93422b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d5e2b16505b2add62478a2ff696f2fdfbb073a7
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/391ab9e5616ba6311161af4d7a93422b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6da6e39a698c2a4447291e5be4c32024b29be2f2d5d94e6e7c4b8a2fcb2a3b0
+size 12880
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/5f748e9d8e77de7b6a98e6039de7d0fd_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/5f748e9d8e77de7b6a98e6039de7d0fd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..056c182df23ce71d85493792ec29224b4c6f48d1
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/5f748e9d8e77de7b6a98e6039de7d0fd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a926eee6d664a74845326c7ae913442608793d2fd090d257bd6abddb85389886
+size 18317
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/a2c9fe78d22304889baddc26f4329ddf_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/a2c9fe78d22304889baddc26f4329ddf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e27dd5432f0884445677c0da2c1d5f3ae99b407d
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/a2c9fe78d22304889baddc26f4329ddf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92395de79da883f860ee06b089c01cf40aee36b54408aa20141b0b65f6f13afb
+size 11214
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/ae02603e9e4b46477222bf72c1c7c7f6_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/ae02603e9e4b46477222bf72c1c7c7f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..efe05a59e8a92da56fe14fbe20eef9f4382f1908
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/ae02603e9e4b46477222bf72c1c7c7f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9dccd569fc2e891c7780848a9b5ed0af6588c695ec9ed8ffb3864413376c8ff
+size 19888
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/b91e305493a4852dca57a801f54085c8_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/b91e305493a4852dca57a801f54085c8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4fa57e572ff7bfe9972b6cbfaec7cfe4a6980753
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/b91e305493a4852dca57a801f54085c8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7133d9efec5ac3d3bfbe9af73d3ddc8e1b901041704ab28720e4bcf96298691b
+size 13684
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/ca81500b365ed30190cb2d9c38fc1f84_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/ca81500b365ed30190cb2d9c38fc1f84_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6b426d5502383f0636849ef27e874133d28b892
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/ca81500b365ed30190cb2d9c38fc1f84_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:479bd13a477309ef7431b48a63322d7a6e65cbb9addb334bae8ec470168c2b95
+size 22108
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f2645f30c909e448926e66bd94a5c519519d5bf
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd6169e15dd26b2f1724154c4ddbd7f08f01ae83fce79bd73f5acbea2b2d9d05
+size 17285
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/e9a1dfde7b55d69a0a56f5bbe35328d4_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/e9a1dfde7b55d69a0a56f5bbe35328d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8678ae0298b2ae6de04e727358814b872bc9d789
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/e9a1dfde7b55d69a0a56f5bbe35328d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:694949df61346f7da202919cc37045d01bdaad88efd61edcf6e8d8b11cc519cd
+size 27784
diff --git a/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/f2f0092624aaf8ad2bcb99a821409714_img.jpg b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/f2f0092624aaf8ad2bcb99a821409714_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2cf565b4cb77319802871f94642f9f6d2ce426bf
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.2-200107-I_PDF-E/f2f0092624aaf8ad2bcb99a821409714_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2224ddda128fdb6243ff50b6478ec57ec2a912a4a1222343c835256f7119439
+size 12651
diff --git a/marked/Q/T-REC-Q.1902.5-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1902.5-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.5-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c
+size 8232
diff --git a/marked/Q/T-REC-Q.1902.5-200107-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.1902.5-200107-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..46841cd14fcf3f9d720cc7516b9c38089237b9d1
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.5-200107-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:918916f3f8bdf44c33d5ca81b4b933774223e3d7379f768443b09b50860cdef6
+size 66050
diff --git a/marked/Q/T-REC-Q.1902.5-200107-I_PDF-E/raw.md b/marked/Q/T-REC-Q.1902.5-200107-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..abf15438877e216cfcfe450352d7a21edb134812
--- /dev/null
+++ b/marked/Q/T-REC-Q.1902.5-200107-I_PDF-E/raw.md
@@ -0,0 +1,238 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.1902.5**
+
+(07/2001)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Specifications of signalling related to Bearer Independent
+Call Control (BICC)
+
+---
+
+**Bearer Independent Call Control protocol
+(Capability Set 2): Exceptions to the application
+transport mechanism in the context of BICC**
+
+ITU-T Recommendation Q.1902.5
+
+(Formerly CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|---------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **Bearer Independent Call Control protocol (Capability Set 2): Exceptions to the application transport mechanism in the context of BICC**
+
+## **Summary**
+
+This Recommendation describes exceptions to ITU-T Q.765, *Signalling System No. 7 – Application transport mechanism*, in the context of bearer independent call control, see ITU-T Q.1902.1, *Bearer Independent Call Control Protocol (Capability Set 2):Functional description*.
+
+## **Source**
+
+ITU-T Recommendation Q.1902.5 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 2 July 2001.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2002
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+# CONTENTS
+
+| | | Page |
+|---|---------------------------------|-------------|
+| 1 | Scope..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 1 |
+| 4 | Abbreviations..... | 1 |
+| 5 | Conventions ..... | 2 |
+| 6 | Exceptions to ITU-T Q.765 ..... | 2 |
+
+
+
+## **Bearer Independent Call Control protocol (Capability Set 2): Exceptions to the application transport mechanism in the context of BICC**
+
+# **1 Scope**
+
+This Recommendation describes exceptions to ITU-T Q.765, *Signalling System No. 7 – Application transport mechanism* [1], in the context of bearer independent call control, see Recommendation Q.1902.1, *Bearer Independent Call Control protocol (Capability Set 2): Functional description* [2].
+
+# **2 References**
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revisions; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- [1] ITU-T Q.765 (2000), *Signalling System No. 7 – Application transport mechanism*.
+- [2] ITU-T Q.1902.1 (2001), *Bearer Independent Call Control protocol (Capability Set 2): Functional description*.
+- [3] ITU-T Q.1902.3 (2001), *Bearer Independent Call Control protocol (Capability Set 2) and Signalling System No. 7 ISDN User Part: Formats and codes*.
+- [4] ITU-T Q.1902.4 (2001), *Bearer Independent Call Control protocol (Capability Set 2) Basic call procedures*.
+- [5] ITU-T Q.2150.0 (2001), *Generic Signalling Transport Service*.
+- [6] ITU-T Q.2150.1 (2001), *Signalling Transport Converter on MTP3 and MTP3b*.
+- [7] ITU-T Q.2150.2 (2001), *Signalling Transport Converter on SSCOP and SSCOPMCE*.
+- [8] ITU-T Q.2150.3 (2001), *Signalling Transport Converter on SCTP*.
+
+# **3 Definitions**
+
+See ITU-T Q.765 [1] and ITU-T Q.1902.1 [2].
+
+# **4 Abbreviations**
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|------|---------------------------------|
+| AEI | Application Entity Invocation |
+| APM | Application Transport Mechanism |
+| ASE | Application Service Element |
+| BAT | Bearer Association Transport |
+| BICC | Bearer Independent Call Control |
+
+| | |
+|------|-------------------------------------|
+| CSF | Call Service Function |
+| EH | Errors Handling |
+| ISUP | ISDN User Part |
+| MTP | Message Transfer Part |
+| NI | Network Interface |
+| SACF | Single Association Control Function |
+| SAO | Single Association Object |
+| STC | Signalling Transport Converter |
+
+# 5 Conventions
+
+See ITU-T Q.1902.1 [2], clause 5 Conventions.
+
+# 6 Exceptions to ITU-T Q.765
+
+ITU-T Q.765 [1] applies with the following exceptions.
+
+The reference to Signalling System No. 7 in the title is not relevant. Where the text refers to ISUP this shall be interpreted to mean BICC.
+
+The subsequent subclause numbers (after the dash) within this clause correspond to the numbering within ITU-T Q.765 [1].
+
+### 6 – 6.2.2 General model
+
+BICC is an adaptation of the narrow-band ISUP protocol for use in a bearer and message transport independent environment. It thus includes significantly different procedures for basic call control, compared to ISUP. It also includes an APM User for the transport of BICC specific information between peer BICC entities.
+
+The generalized model for the ISUP Application Transport Mechanism Application Process is presented in Figure 2/Q.765 [1].
+
+In this model, the application logic for the APM users are considered to be within the Nodal functions (Application Process).
+
+ISUP basic call Recommendation (ITU-T Q.764) includes specification of ISUP signalling procedures and nodal functions (Application Process functions) in a monolithic way, i.e. the partitioning of functionality between the ISUP ASE and ISUP Nodal functions is not defined. ITU-T Q.765 [1] also does not define the functionality split for ISUP basic call.
+
+The model from Figure 2/Q.765 [1] applied on the BICC basic call is shown in Figure 1.
+
+
+
+Figure 1/Q.1902.5 – BICC specification model diagram. The diagram shows a hierarchical structure of network functions. At the top is 'Nodal functions'. Below it is 'BICC AEI' which contains a 'BICC SAO' block and a 'SACF' block. The 'SACF' block is connected to four 'ASE' blocks: 'BAT ASE', 'EH ASE', 'APM ASE', and 'BICC ASE' via interfaces 'b', 'c', 'd', and 'e' respectively. The 'SACF' block is also connected to an 'NI' block via interface 'f'. The 'NI' block is connected to a 'Signalling Transport Converter' block via interface 'h'. The 'Signalling Transport Converter' block is connected to an external interface 'g'. The entire structure is enclosed in a 'CSF Application Process' box. A reference code 'T11111820-01' is present in the bottom right corner of the diagram.
+
+**Figure 1/Q.1902.5 – BICC specification model**
+
+In this model the BAT ASE is introduced to provide the transport for the BICC data, and the ISUP ASE has been replaced by a BICC ASE. It should be noted that there is still no definition of the split of functionality between the BICC ASE and the Nodal functions. The replacement of the ISUP ASE by the BICC ASE just signifies that the BICC signalling is not the same as ISUP signalling. The BICC procedures, insofar as they are the user of the BAT ASE, should be considered as a part of the Nodal functions (in order to conform with the model expected in ITU-T Q.765 [1]). The BICC procedures thus access the service provided by the BAT ASE by using the BICC\_Data primitive at interface a.
+
+The BICC procedures indicated by the BICC procedures block in Figure 4/Q.1902.1 [2], and described in ITU-T Q.1902.4 [4], correspond to the composite of the BICC Nodal functions, (as a BAT ASE user), and the BICC ASE. No attempt is made to provide distinct descriptions of these two modelling entities.
+
+The interface h is the BICC Signalling Transport Service primitive interface as specified in ITU-T Q.2150.0 [5] while interface g is the specific signalling transport service (see ITU-T Q.2150.X-series of Recommendations, e.g. [6], [7], [8]), and, in case of MTP-3 signalling transport, is the same as described in ITU-T Q.765 [1].
+
+#### **6 – 10.2.1 Normal procedures – Sending**
+
+Clause 10.2.1/Q.765 [1] states that the 272 octet limit of the MTP is the reason that would cause APM segmentation to be invoked. This statement is applicable to BICC if the START-INFO.indication primitive received from the STC, see ITU-T Q.2150.0 [5], indicates that the underlying message transport mechanism can transport only 272 octets. However, if the transport can support greater than 272 octets then APM segmentation is only applicable if the BICC application information exceeds the 255 octet limit imposed by the parameter formatting rules of ITU-T Q.1902.3 [3].
+
+## **6 – 12 Network interface function**
+
+Clause 12/Q.765 [1] applies with the following exceptions:
+
+- 1) When the text refers to MTP it shall be interpreted to mean the actual signalling transport.
+- 2) When the text refers to CIC it shall be interpreted to mean Call Instance Code.
+- 3) When the text refers to ITU-T Q.763, it shall be interpreted to be a reference to ITU-T Q.1902.3 [3].
+- 4) When the text refers to ITU-T Q.764, it shall be interpreted to be a reference to ITU-T Q.1902.4 [4].
+- 5) There is one instance of signalling transport converter per signalling route, and thus the distribution function performed by the NI acts only upon the CIC value. When the signalling transport is MTP the OPC, DPC, SIO and SLS are handled within the MTP3/MTP3b signalling transport converter as described in ITU-T Q.2150.1 [6].
+- 6) Primitive interface g shall be replaced by the primitive interface as described in the Q.2150.x-series of Recommendations (e.g. [6], [7], [8]).
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6f19b794859078008f50eb46e6de60d09074f3b8
--- /dev/null
+++ b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62822c6dbbf2a45c4be6c78124bf8bb627f5dd847834f8cffeda416edbf85c30
+size 27934
diff --git a/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..104a57fbd03964ffd2520508b2be42e03343d20f
--- /dev/null
+++ b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2468dfa77e8d32611a5fe8a2ebb904676994eeb54463226fd865698560c960c
+size 8232
diff --git a/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d26534f632ad61beb499a723a5f7885c20aafaa4
--- /dev/null
+++ b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4ba418142d40c6231e79a5e1817ae52bcc483d36b50fcef2e5ffedd279f1310
+size 70482
diff --git a/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64ac8b6f581810de9f9c83b5bf53fa76e0b2b7b6
--- /dev/null
+++ b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/5e92d9e8e9ce204e405bff2367f88176_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cfefc595c872fbfdda72e745cfa5a88f4396d47b309224ecba001d07a23d4e65
+size 8973
diff --git a/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4a03da611bacda6bd7bc02206d816d5d45965d2b
--- /dev/null
+++ b/marked/Q/T-REC-Q.1912.3-200107-I_PDF-E/853f59c89931a666c07903b31d098277_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c429601b36219dfadb2651daa4fc5915e60a413d1735ad613f0dfb93e3723bc3
+size 9539
diff --git a/marked/Q/T-REC-Q.1980.1-200412-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.1980.1-200412-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..917e22b9ee2f4a3fdf5e8e3d27c117036492770e
--- /dev/null
+++ b/marked/Q/T-REC-Q.1980.1-200412-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c6782ef88554e46d162830165ad7f2bde18ba61bf2e76fe30c6ee74727616e2
+size 5901
diff --git a/marked/Q/T-REC-Q.1980.1-200412-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Q/T-REC-Q.1980.1-200412-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0985dbaf02b489290ad708ed7aff8a2a4a3c286b
--- /dev/null
+++ b/marked/Q/T-REC-Q.1980.1-200412-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4895af2a13104aeac370ad7951c0bb036c54f1b338c540315f0cd3ad095e355b
+size 69334
diff --git a/marked/Q/T-REC-Q.2100-199407-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2100-199407-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cfcb6b924e097141cf0122fcb114252e72f20825
--- /dev/null
+++ b/marked/Q/T-REC-Q.2100-199407-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c942335dbf5e6cb33a969396d1fd1f175c552e46ec341db9e15798be2b90ee12
+size 8229
diff --git a/marked/Q/T-REC-Q.2100-199407-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/Q/T-REC-Q.2100-199407-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bfd6412ed5d1b61644f855d9876b687bfbca8013
--- /dev/null
+++ b/marked/Q/T-REC-Q.2100-199407-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:988b934eb4b653546f373f439dd8878eea5941480f1471b54e92057982a3b31d
+size 51494
diff --git a/marked/Q/T-REC-Q.2144-199510-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c719d0e1ff69868451a19c8385423fb03d27c394
--- /dev/null
+++ b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e60bbb261cbfc631b8c6bc29ead02baecdf5f075d39dcbdee7fd355702635902
+size 79915
diff --git a/marked/Q/T-REC-Q.2144-199510-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..44c665217cd1a54e9c2656d3161e9b51c914db99
--- /dev/null
+++ b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce6795779a34e7fc0bf79ced1433578c4155bc39f0b6a62b16899f461a45cd92
+size 81349
diff --git a/marked/Q/T-REC-Q.2144-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..129e1ece44b43392e4d324b0669e852a13d1f68e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e99309a61148567f49b287c83a59313286493a55906beeef9ae111896560092e
+size 8225
diff --git a/marked/Q/T-REC-Q.2144-199510-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..498a599f8ac3b4724868e6a4d7956e5adb8c96a6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fbe13ae535a7f6069c3be678227233a2f861413d8b09e29aeff4c5702ce5619
+size 36302
diff --git a/marked/Q/T-REC-Q.2144-199510-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1e1e1e79e5f6fbcce4428b9fda83ae6fabcea68
--- /dev/null
+++ b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d998cfb46d6aefde2ed511a31490e79487571016558d305bccada5f9002d8dc
+size 102845
diff --git a/marked/Q/T-REC-Q.2144-199510-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5e351dc65381f4da04769412d6e6516c08d51551
--- /dev/null
+++ b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d87f075b8de732398c1a7e2fac9944a7c1c78e3d07fd7a31608223e09946141a
+size 109349
diff --git a/marked/Q/T-REC-Q.2144-199510-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d04506b448544213e597a51319d9ee006a60de24
--- /dev/null
+++ b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8a5856bd0e0b1c17cb33786a2c9cd5718edb4b4b686b637c151df8375b3ed1b2
+size 90219
diff --git a/marked/Q/T-REC-Q.2144-199510-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c81334e9566685bddd65995c00e111d9a542295
--- /dev/null
+++ b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a513ae3de1f2b26ff82aad404986c257934cb0ea9dc70d1a755ffdadf0f2275e
+size 74548
diff --git a/marked/Q/T-REC-Q.2144-199510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee5da450921f94cb7f8bb6b173046364a7999731
--- /dev/null
+++ b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2aaf04f05518a32e3c13e157f5122a6176a946831dce13d60f16943f23a0d71
+size 265244
diff --git a/marked/Q/T-REC-Q.2144-199510-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..71493cc64e0669ac878cdbe389e9b0c3e5d2db85
--- /dev/null
+++ b/marked/Q/T-REC-Q.2144-199510-I_PDF-E/raw.md
@@ -0,0 +1,1069 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.2144**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(10/95)
+
+**B-ISDN ATM ADAPTATION LAYER**
+
+---
+
+**B-ISDN SIGNALLING ATM ADAPTATION
+LAYER (SAAL) – LAYER MANAGEMENT
+FOR THE SAAL AT THE NETWORK NODE
+INTERFACE (NNI)**
+
+**ITU-T Recommendation Q.2144**
+
+(Previously "CCITT Recommendation")
+
+---
+
+# FOREWORD
+
+The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993).
+
+ITU-T Recommendation Q.2144 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 17th of October 1995.
+
+---
+
+# NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+| | Page |
+|-----------------------------------------------------------------------|-------------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 2.1 Normative references..... | 1 |
+| 2.2 Informative references ..... | 1 |
+| 3 Abbreviations and acronyms..... | 2 |
+| 4 Model for interactions with Layer Management..... | 3 |
+| 5 Interface Between Layer Management and the SAAL at the NNI..... | 3 |
+| 5.1 Interface Between Layer Management and SSCOP ..... | 3 |
+| 5.2 Interface Between Layer Management and the SSCF at the NNI ..... | 5 |
+| 6 State Transition Table of LM for the management of SAAL at NNI..... | 7 |
+| 7 Interface to systems management..... | 12 |
+| 8 Peer-to-peer Layer Management communication ..... | 12 |
+| 9 Procedures of Layer Management..... | 12 |
+| 9.1 Error processing..... | 12 |
+| 9.2 Measurements ..... | 14 |
+| 9.3 Handling of processor outage conditions..... | 16 |
+| 9.4 Management of signalling link proving..... | 16 |
+| Annex A – Real system resources ..... | 17 |
+| Appendix I – Management error indications ..... | 18 |
+| Appendix II – Example of error monitoring of In-Service links ..... | 19 |
+| II.1 Overview ..... | 19 |
+| II.2 Detailed description ..... | 19 |
+| II.3 Rationale for default parameters..... | 22 |
+| II.4 Proving..... | 23 |
+
+# **SUMMARY**
+
+The ATM Adaptation Layer (AAL) is defined to enhance the services provided by the ATM layer to support the functions required by the next higher layer. One particular type of AAL service is the Signalling AAL (SAAL) which comprises AAL functions necessary to support a signalling entity. The structure of the SAAL is defined in Recommendation Q.2100.
+
+The SAAL consists of a Segmentation And Reassembly (SAR) function, and a Convergence Sublayer which is divided into two sublayers: a Common Part Convergence Sublayer (CPCS) and a Service Specific Convergence Sublayer (SSCS). The common part protocol is defined in clause 6/I.363, and is used as the underlying protocol for the service specific part for signalling. The SSCS is functionally divided into two parts. The Service Specific Connection Oriented Protocol (SSCOP), which provides an assured data transfer service and the Service Specific Coordination Function (SSCF). The SSCOP is defined in Recommendation Q.2110 and is suitable for use by various SSCFs. This Recommendation specifies the layer management functions for the SAAL at the Network Node Interface (NNI).
+
+The layer management functions at the NNI perform error monitoring and a coordination function between the systems management function and the SAAL.
+
+This Recommendation describes the NNI layer management functions associated with the management primitives between the SAAL sublayers and the layer management entity.
+
+# **KEYWORDS**
+
+Error monitoring, Layer management, NNI, SAAL
+
+###### B-ISDN SIGNALLING ATM ADAPTATION LAYER (SAAL) – LAYER MANAGEMENT FOR THE SAAL AT THE NETWORK NODE INTERFACE (NNI)
+
+(Geneva, 1995)
+
+# 1 Scope
+
+This Recommendation specifies the Layer Management functions for the Signalling ATM Adaptation Layer (SAAL) at the Network Node Interface (NNI). These include the interfaces to the Service Specific Connection Oriented Protocol (SSCOP, Recommendation Q.2110 [2]), to the Service Specific Coordination Function (SSCF) at the NNI (Recommendation Q.2140 [3]), and to systems management. Layer Management provides, or supports, the following functions for the Service Specific Convergence Sublayer (SSCS) at the NNI:
+
+- error processing;
+- measurements;
+- notification of processor outage status;
+- determination of link quality during proving; and
+- determination of link quality during normal operation.
+
+# 2 References
+
+The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+## 2.1 Normative references
+
+- [1] ITU-T Recommendation I.363 (1993), *B-ISDN ATM Adaptation Layer (AAL) specification*.
+- [2] ITU-T Recommendation Q.2110 (1994), *B-ISDN ATM adaptation layer – Service Specific Connection Oriented Protocol (SSCOP)*.
+- [3] ITU-T Recommendation Q.2140 (1995), *B-ISDN ATM adaptation layer – Service Specific Coordination Function for signalling at the Network Node Interface (SSCF AT NNI)*.
+
+## 2.2 Informative references
+
+- [4] ITU-T Recommendation Q.703 (1993), *Signalling System No. 7 Signalling link*.
+- [5] ITU-T Recommendation Q.704 (1993), *Signalling System No. 7 Signalling network functions and messages*.
+- [6] ITU-T Recommendation Q.750 (1993), *Overview of Signalling System No. 7 management*.
+- [7] ITU-T Recommendation Q.752 (1993), *Monitoring and measurements for Signalling System No. 7 networks*.
+
+# 3 Abbreviations and acronyms
+
+For the purposes of this Recommendation, the following abbreviations are used.
+
+| | |
+|--------|-----------------------------------------------|
+| AA | ATM Adaptation |
+| AAL | ATM Adaptation Layer |
+| ALN | Alignment |
+| ANS | Alignment Not Successful |
+| ATM | Asynchronous Transfer Mode |
+| BER | Bit Error Ratio |
+| BGAK | Begin Acknowledge (SSCOP PDU) |
+| BGN | Begin (SSCOP PDU) |
+| BGREJ | Begin Reject (SSCOP PDU) |
+| B-ISDN | Broadband Integrated Services Digital Network |
+| CC | Congestion Ceased |
+| CD | Congestion Detected |
+| END | End (SSCOP PDU) |
+| ENDAK | End Acknowledge (SSCOP PDU) |
+| ER | Error Recovery (SSCOP PDU) |
+| ERAK | Error Recovery Acknowledge (SSCOP PDU) |
+| INS | IN Service |
+| LM | Layer Management |
+| LPO | Local Processor Outage |
+| LR | Local Release |
+| MAA | Management ATM Adaptation |
+| MAAL | Management ATM Adaptation Layer |
+| MD | Management Data (SSCOP PDU) |
+| MPS | Management Proving State |
+| MTP | Message Transfer Part |
+| MTP-2 | Message Transfer Part Level 2 |
+| MTP-3 | Message Transfer Part Level 3 |
+| MU | Message Unit |
+| NC | NO CREDIT |
+| NNI | Network Node Interface |
+| NRP | Number of Retransmitted SSCOP PDUs |
+| OOS | Out Of Service |
+| OSI | Open Systems Interconnection |
+| PDU | Protocol Data Unit |
+| PDUT | SSCOP PDU Transmitted |
+
+| | |
+|----------|-----------------------------------------------|
+| PE | Protocol Error |
+| PNS | Proving Not Successful |
+| PO | Processor Outage |
+| POLL | Poll (SSCOP PDU) |
+| QOS | Quality of Service |
+| RR | Remote Release |
+| RS | Resynchronization (SSCOP PDU) |
+| RSAK | Resynchronization Acknowledge (SSCOP PDU) |
+| RSREC | Timer_REPEAT-SREC |
+| SAAL | Signalling ATM Adaptation Layer |
+| SAR | Segmentation And Reassembly |
+| SD | Sequenced Data (SSCOP PDU) |
+| SR | SSCOP Release |
+| SREC | SSCOP RECover |
+| SSCF | Service Specific Coordination Function |
+| SSCOP | Service Specific Connection Oriented Protocol |
+| SSCOP-UU | SSCOP User-to-User Information |
+| SSCS | Service Specific Convergence Sublayer |
+| STAT | Solicited STATus (SSCOP PDU) |
+| UD | Unnumbered Data (SSCOP PDU) |
+| UDR | UNITDATA Received |
+| USTAT | Unsolicited STATus (SSCOP PDU) |
+
+# 4 Model for interactions with Layer Management
+
+Figure 1 shows the relationship of Layer Management to other protocols and management entities. In the figure, solid lines connect Layer Management to entities with which it interacts directly. Sections 5, 6 and 7 provide more information on these interfaces.
+
+# 5 Interface Between Layer Management and the SAAL at the NNI
+
+This clause defines the signals between the Layer Management entity for the SAAL at the NNI and between the SSCF at the NNI and the SSCOP. Subclause 5.1 defines the interface to SSCOP. Subclause 5.2 defines the interface to the SSCF at the NNI. For information concerning the interface of AAL Type 5 Common Part to Layer Management, consult 6/L.363 [1].
+
+NOTE – Currently there are no interactions between the AAL Type 5 Common Part and Layer Management specified in Recommendation I.363 [1].
+
+## 5.1 Interface Between Layer Management and SSCOP
+
+Between Layer Management and the SSCOP the signals contained in Table 1 are defined:
+
+
+
+```
+
+graph LR
+ SM[Systems Management] --- LM[Layer Management]
+ LM --- MTP3[MTP-3]
+ LM --- SSCF[SSCF at NNI]
+ LM --- SSCOP[SSCOP]
+ LM --- AAL5[AAL Type 5 Common Part]
+
+```
+
+T1166720-94/d01
+
+Diagram showing the relationships of Layer Management with other entities. Systems Management is connected to Layer Management. Layer Management is connected to MTP-3, SSCF at NNI, SSCOP, and AAL Type 5 Common Part.
+
+FIGURE 1/Q.2144
+**Relationships of Layer Management with other entities**
+
+TABLE 1/Q.2144
+**Signals and Parameters between SSCOP and Layer Management**
+
+| Generic name | Type | | | |
+|--------------|-------------|-------------|-------------|-------------|
+| | Request | Indication | Response | Confirm |
+| MAA-ERROR | Not Defined | Code, Count | Not Defined | Not Defined |
+| MAA-UNITDATA | MU | MU | Not Defined | Not Defined |
+
+The definitions of these signals are found in Recommendation Q.2110 [2]. They are shown here for ease of reference.
+
+- The MAA-ERROR signal is used by SSCOP to report the occurrence of various error events to Layer Management.
+- The MAA-UNITDATA signals are used for the non-assured transfer of information between peer Layer Management entities.
+
+NOTE – Thus far, no procedures using the MAA-UNITDATA signal have been defined for the Layer Management for the SAAL at the NNI.
+
+The parameters in these signals are defined as follows:
+
+- The Message Unit (MU) parameter contains the service data unit that is transferred from Layer Management to SSCOP in the MAA-UNITDATA.request and from SSCOP to Layer Management in the MAA-UNITDATA.indication.
+- The Code parameter indicates the type of error that occurred. A table of errors that can be reported and the corresponding Code values are given in Recommendation Q.2110 [2] and are replicated for convenience in Appendix I.
+- The Count parameter indicates the number of SD PDU retransmissions that occurred.
+
+## 5.2 Interface Between Layer Management and the SSCF at the NNI
+
+Between Layer Management and the NNI SSCF the signals contained in Table 2 are defined in Recommendation Q.2140 [3]. These definitions are repeated below for the convenience of the reader.
+
+TABLE 2/Q.2144
+
+### Signals between SSCF at the NNI and Layer Management
+
+| Signals | Direction |
+|----------------------------------------|------------|
+| MAAL-PROVING.indication | SSCF to LM |
+| MAAL-CLEAR_FORCE_MODES.request | LM to SSCF |
+| MAAL-FORCE_EMERGENCY.request | LM to SSCF |
+| MAAL-FORCE_PROVING.request | LM to SSCF |
+| MAAL-STOP_PROVING.indication | SSCF to LM |
+| MAAL-PROVING_UNSUCCESSFUL.response | LM to SSCF |
+| MAAL-RELEASE.request | LM to SSCF |
+| MAAL-LOCAL_PROCESSOR_OUTAGE.request | LM to SSCF |
+| MAAL-LOCAL_PROCESSOR_RECOVERED.request | LM to SSCF |
+| MAAL-REPORT.indication | SSCF to LM |
+
+These signals are defined as follows:
+
+"MAAL-PROVING.indication"
+
+is used by SSCF to initiate the error monitoring within Layer Management for connection proving.
+
+"MAAL-FORCE\_PROVING.request"
+
+is used to instruct SSCF to implement forced proving.
+
+"MAAL-FORCE\_EMERGENCY.request"
+
+is used to instruct SSCF to omit proving.
+
+"MAAL-CLEAR\_FORCE\_MODES.request"
+
+is used to notify SSCF that Layer Management is indifferent to which proving mode is used.
+
+"MAAL-RELEASE.request"
+
+is used to instruct SSCF to release the connection.
+
+"MAAL-STOP\_PROVING.indication"
+
+is used to indicate that the proving procedure has terminated.
+
+"MAAL-PROVING\_UNSUCCESSFUL.response"
+
+is used to notify SSCF that the proving was not successful.
+
+"MAAL-LOCAL\_PROCESSOR\_OUTAGE.request"
+
+is used to notify SSCF of local processor outage.
+
+"MAAL\_LOCAL\_PROCESSOR-RECOVERED.request"
+
+is used to notify SSCF that the local processor has recovered.
+
+"MAAL-REPORT.indication"
+
+is used to notify Layer Management of events detected by SSCF.
+
+The generic structure for the MAAL-REPORT.indication is:
+
+MAAL-REPORT.indication (“lower boundary conditions,” “upper boundary conditions,” “reasons in case of exceptional situations”)
+
+The “lower boundary conditions” parameter reports whether the SSCOP connection was released by the remote or local SSCF or by SSCOP itself if the event being reported involves release of the SSCOP connection; it can take values RR, LR, SR, or -.
+
+The “upper boundary conditions” parameter reports the interface state at the upper boundary of the SSCF into which a transition was made if the event being reported involves a transition at this boundary; it can take values OOS, INS, ALN, or -.
+
+The “reasons in case of exceptional situations” parameter reports the reason for transitions reported in the lower boundary conditions or upper boundary conditions parameters or the type of event being reported when the boundary conditions parameters are empty; it can take values ANS, SREC, SSCOP-UU, PE, CD, CC, PDUT, UDR, or -.
+
+#### Key
+
+| | |
+|----------|--------------------------------|
+| ALN | Alignment |
+| ANS | Alignment Not Successful |
+| CC | Congestion Ceased |
+| CD | Congestion Detected |
+| INS | IN Service |
+| LR | Local Release |
+| OOS | Out Of Service |
+| PDUT | SSCOP PDU Transmitted |
+| PE | Protocol Error |
+| RR | Remote Release |
+| SR | SSCOP Release |
+| SREC | SSCOP RECover |
+| SSCOP-UU | SSCOP User-to-User Information |
+| UDR | UNITDATA Received |
+| - | empty |
+
+These parameter values of the MAAL-REPORT.indication and other MAAL-signals provide the Layer Management with an unambiguous view of the status of SSCF (see Table 6/Q.2140 [3] for applicability of notifications).
+
+In the state transition diagram Figure 2:
+
+- the signal MAAL-REPORT.indication (-,-,UDR) is possible in any state. This is not shown;
+- any other signal which is not shown as resulting in a transition (from one state to the same state, or from one state to a different state) is not permitted in that state;
+
+- c) it is assumed that the signals passed between LM and an SSCF are coordinated so that collisions do not occur;
+- d) the following abbreviations are used:
+
+MAAL-PROVING\_UNS = MAAL-PROVING\_UNSUCCESSFUL,
+
+MAAL-LOC\_PROC\_OUT = MAAL-LOCAL\_PROCESSOR\_OUTAGE,
+
+MAAL-LOC\_PROC\_REC = MAAL-LOCAL\_PROCESSOR\_RECOVERED.
+
+# 6 State Transition Table of LM for the management of SAAL at NNI
+
+This clause contains the state transition table, Table 3, of the LM for the management of SAAL at NNI in support of an SAAL service which is provided at an AAL connection endpoint. It makes use of sequences of MAA-, and MAAL-signals as defined in 5.1 and 5.2.
+
+The events shown in Table 3 are signals at the boundary between LM and SSCF or SSCOP, LM-internal events, management status information, e.g. Local Management Proving Status. Some of the events identified in Table 3 as illegal and associated with a state are the result of collisions at the boundary between LM and SSCF or SSCOP which, as assumed here, do not occur.
+
+The state of Layer Management is determined by its perception of the state of the SSCF. The following states are defined:
+
+- 1) Out Of Service: In this state no signalling connection exists and SSCF waits for an AAL-START.request from the SSCF user.
+- 2) Alignment: In this state the SSCF has received an AAL-START.request and is either in the process of establishing an SSCOP connection or waiting between connection establishment attempts.
+- 3) Proving: In this state the SSCF has established an SSCOP connection. Layer Management has been notified of the establishment and conducts alignment error rate monitoring.
+- 4) Aligned Ready: In this state the SSCF has completed proving and awaits an indication from its peer that the signalling link can be put into service. Layer Management conducts in-service error rate monitoring.
+- 5) In-Service: In this state, the signalling connection may be used by the SSCF user to transfer messages. Layer Management conducts In-Service error rate monitoring.
+
+The LM has an internal state variable Number of Retransmitted PDUs (NRP) which keeps track of SSCOP retransmission of SD PDUs during proving, based on MAA-ERROR.indication (V,Count). The LM parameter Max\_NRP determines such maximum permissible retransmissions.
+
+The LM has an internal Timer\_NO-CREDIT (NC) which supervises the unavailability of credit, if PDUs are available to be transmitted. The value of this timer is an LM parameter. On expiry of this timer, LM issues an MAAL-RELEASE.request signal which causes the release of the signalling connection.
+
+The LM has an internal Timer\_REPEAT-SREC which is set whenever a report of an SSCOP recovery is received from the SSCF. If the timer is already active when the report of recovery is received, LM issues an MAAL-RELEASE.request signal which causes release of the signalling connection.
+
+Some of the events result in an Error logging. The accumulation of these error reports and comparison with thresholds is beyond the scope of this Recommendation.
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> 4: Aligned Ready
+ 4 --> 1: Out of Service
+ 4 --> 5: In Service
+ 4 --> 2: Alignment
+ 1 --> 2: Alignment
+ 1 --> 3: Proving
+ 2 --> 1: Out of Service
+ 2 --> 3: Proving
+ 2 --> 4: Aligned Ready
+ 3 --> 1: Out of Service
+ 3 --> 4: Aligned Ready
+ 3 --> 5: In Service
+ 5 --> 1: Out of Service
+ 5 --> 2: Alignment
+ 5 --> 3: Proving
+ 5 --> 4: Aligned Ready
+
+```
+
+**State 1: Out of Service**
+
+- Entry: MAAL-REPORT.indication (-,-,CC), or MAAL-REPORT.indication (LR,-,PE), or MAAL-REPORT.indication (RR,-,SSCOP-UU), or MAAL-LOC.PROC\_OUT.request, or MAAL-LOC.PROC\_REC.request, or MAAL-FORCE\_PROVING.request, or MAAL-FORCE\_EMERGENCY.request, or MAAL-CLEAR\_FORCE\_MODES.request, or MAAL-STOP\_PROVING.indication
+- Exit: MAAL-REPORT.indication (LR,OOS,ANS), or MAAL-REPORT.indication (-,OOS,-), or MAAL-REPORT.indication (-,OOS,ANS), or MAAL-RELEASE.request
+
+**State 2: Alignment**
+
+- Entry: MAAL-REPORT.indication (-,ALN,-)
+- Exit: MAAL-REPORT.indication (RR,-,SSCOP-UU), or MAAL-REPORT.indication (SR,-,-), or MAAL-REPORT.indication (LR,-,PE)
+
+**State 3: Proving**
+
+- Entry: MAAL-PROVING.indication
+- Exit: MAAL-LOC.PROC\_OUT.request, or MAAL-LOC.PROC\_REC.request, or MAAL-FORCE\_PROVING.request, or MAAL-FORCE\_EMERGENCY.request, or MAAL-CLEAR\_FORCE\_MODES.request
+
+**State 4: Aligned Ready**
+
+- Entry: MAAL-REPORT.indication (LR,OOS,-), or MAAL-REPORT.indication (LR,OOS,ANS), or MAAL-RELEASE.request, or MAAL-LOC.PROC\_OUT.request
+- Exit: MAAL-REPORT.indication (-,-,SREC) or MAAL-REPORT.indication (-,-,CD), or MAAL-REPORT.indication (-,-,CC), or MAAL-FORCE\_PROVING.request, or MAAL-FORCE\_EMERGENCY.request, or MAAL-CLEAR\_FORCE\_MODES.request
+
+**State 5: In Service**
+
+- Entry: MAAL-REPORT.indication (-,INS,-)
+- Exit: MAAL-REPORT.indication (-,-,PDUT), or MAAL-REPORT.indication (-,-,SREC), or MAAL-REPORT.indication (-,-,CD), or MAAL-REPORT.indication (-,-,CC), or MAAL-FORCE\_PROVING.request, or MAAL-FORCE\_EMERGENCY.request, or MAAL-CLEAR\_FORCE\_MODES.request
+
+State transition diagram showing five states: Out of Service (1), Alignment (2), Proving (3), Aligned Ready (4), and In Service (5). Transitions are triggered by various MAAL signals such as MAAL-REPORT.indication, MAAL-LOC.PROC\_OUT.request, MAAL-FORCE\_PROVING.request, MAAL-FORCE\_EMERGENCY.request, MAAL-CLEAR\_FORCE\_MODES.request, and MAAL-RELEASE.request.
+
+T1166730-94/d02
+
+FIGURE 2/Q.2144
+State transition diagram at the SSCF to LM boundary for sequences of MAAL-signals
+
+TABLE 3/Q.2144 (1 of 4)
+
+## State transition table for the LM at the NNI
+
+| State
Event | Out Of Service
1 | Alignment
2 | Proving
3 | Aligned Ready
4 | In-Service
5 |
+|-------------------------------------------|---------------------|----------------|--------------|-------------------------------|-------------------------------|
+| MAAL-REPORT. indication (-,ALN,-) | 2 | I | I | I | I |
+| MAAL-PROVING. indication | Illegal | NRP:=0
3 | I | I | I |
+| MAAL-STOP_PROVING. indication | 1 | 2 | 4 | I | I |
+| MAAL-REPORT. indication (-,INS,-) | Illegal | I | I | 5 | I |
+| MAAL-REPORT. indication (-,OOS,-) | Illegal | 1 | I | I | I |
+| MAAL-REPORT. indication (-,OOS,ANS) | Illegal | 1 | I | I | I |
+| MAAL-REPORT. indication (LR,OOS,-) | Illegal | I | 1 | Stop timers NC and RSREC
1 | Stop timers NC and RSREC
1 |
+| MAAL-REPORT. indication (LR,OOS,ANS) | Illegal | 1 | 1 | Stop timers NC and RSREC
1 | I |
+| MAAL-REPORT. indication (LR,OOS,PE) | Illegal | I | I | I | Stop timers NC and RSREC
1 |
+| MAAL-REPORT. indication (LR,-,PE) | Illegal | 2 | 2 | Stop timers NC and RSREC
2 | I |
+| MAAL-REPORT. indication (LR,-,CD) | Illegal | I | 2 | I | I |
+| MAAL-REPORT. indication (RR,OOS,SSCOP-UU) | Illegal | I | I | I | Stop timers NC and RSREC
1 |
+| MAAL-REPORT. indication (RR,-,SSCOP-UU) | Illegal | 2 | 2 | Stop timers NC and RSREC
2 | I |
+| MAAL-REPORT. indication (SR,OOS,-) | Illegal | I | I | I | Stop timers NC and RSREC
1 |
+| MAAL-REPORT. indication (SR,-,-) | Illegal | 2 | 2 | Stop timers NC and RSREC
2 | I |
+
+TABLE 3/Q.2144 (2 of 4)
+
+## State transition table for the LM at the NNI
+
+| State
Event | Out Of Service
1 | Alignment
2 | Proving
3 | Aligned Ready
4 | In-Service
5 |
+|------------------------------------|---------------------|--------------------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MAAL-REPORT. indication (-,-,SREC) | Illegal | I | I | If timer RSREC active
THEN
MAAL-RELEASE.
request
MAAL-FORCE_PROVING.
request
stop timer NC
stop timer RSREC (NOTE 1)
1
ELSE
start timer RSREC
4 | If timer RSREC active
THEN
MAAL-RELEASE.
request
MAAL-FORCE_PROVING.
request
stop timer NC
stop timer RSREC (NOTE 1)
1
ELSE
start timer RSREC
5 |
+| MAAL-REPORT. indication (-,-,CD) | Illegal | I | I | 4 | 5 |
+| MAAL-REPORT. indication (-,-,CC) | Illegal | 2 | I | 4 | 5 |
+| MAAL-REPORT. indication (-,-,PDUT) | Illegal | I | I | I | 5 |
+| MAAL-REPORT. indication (-,-,UDR) | Error logging
1 | Error logging
2 | MAAL-PROVING_UNS.response
2 | Error logging
4 | Error logging
5 |
+| MAA-ERROR. indication (A – M) | Error logging
1 | Error logging
2 | MAAL-PROVING_UNS.response
2 | Error logging
4 | Error logging
5 |
+| MAA-ERROR. indication (O) | Error logging
1 | Error logging
2 | I | I | I |
+| MAA-ERROR. indication (P) | Illegal | Illegal | Error logging
3 | Error logging
4 | Error logging
5 |
+| MAA-ERROR. indication (Q – T) | Illegal | Illegal | Error logging
3 | Error logging
4 | Error logging
5 |
+| MAA-ERROR. indication (U) | Error logging
1 | Error logging
2 | MAAL-PROVING_UNS.response
2 | Error logging
4 | Error logging
5 |
+
+TABLE 3/Q.2144 (3 of 4)
+
+## State transition table for the LM at the NNI
+
+| State
Event | Out Of Service
1 | Alignment
2 | Proving
3 | Aligned Ready
4 | In-Service
5 |
+|----------------------------------------------------|-----------------------------------------|-----------------------------------------|----------------------------------------------------------------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------|
+| MAA-ERROR. indication (V,Count) | Illegal | Illegal | NRP:=NRP+count
IF
NRP>Max_NRP
THEN
MAAL-PROVING_ _UNS.response
2
ELSE
3 | Error logging
4 | Error logging
5 |
+| MAA-ERROR. indication (W) | Illegal | Illegal | MAAL-PROVING_ _UNS.response
2 | Start timer NC | Start timer NC |
+| MAA-ERROR. indication (X) | Illegal | Illegal | I | Stop timer NC | Stop timer NC |
+| MAA-UNITDATA. indication {MU} | Management communication Protocol Error | Management communication Protocol Error | Management communication Protocol Error | Management communication Protocol Error | Management communication Protocol Error |
+| Local Management Proving Status NORMAL (Note 2) | MAAL-FORCE_PROVING. request
1 | MAAL-FORCE_PROVING. request
2 | MAAL-FORCE_PROVING. request
3 | MAAL-FORCE_PROVING. request
4 | MAAL-FORCE_PROVING. request
5 |
+| Local Management Proving Status EMERGENCY (Note 2) | MAAL-FORCE_EMERGENCY. request
1 | MAAL-FORCE_EMERGENCY. request
2 | MAAL-FORCE_EMERGENCY. request
3 | MAAL-FORCE_EMERGENCY. request
4 | MAAL-FORCE_EMERGENCY. request
5 |
+| Local Management Proving Status NEUTRAL (Note 2) | MAAL-CLEAR_FORCE_MODES.request
1 | MAAL-CLEAR_FORCE_MODES.request
2 | MAAL-CLEAR_FORCE_MODES.request
3 | MAAL-CLEAR_FORCE_MODES.request
4 | MAAL-CLEAR_FORCE_MODES.request
5 |
+| Expiry timer NC | / | / | / | MAAL-RELEASE. request
stop timer RSREC
1 | MAAL-RELEASE. request
stop timer RSREC
1 |
+| Local Processor Outage (Note 3) | MAAL-LOC_PROC_OUT. request
1 | MAAL-LOC_PROC_OUT. request
2 | MAAL-LOC_PROC_OUT. request
3 | MAAL-LOC_PROC_OUT. request
Stop timers NC and RSREC
1 | MAAL-LOC_PROC_OUT. request
Stop timers NC and RSREC
1 |
+| Local Processor Recovered (Note 3) | MAAL-LOC_PROC_REC. request
1 | MAAL-LOC_PROC_REC. request
2 | MAAL-LOC_PROC_REC. request
3 | I | I |
+
+TABLE 3/Q.2144 (4 of 4)
+
+State transition table for the LM at the NNI
+
+| State | Out Of Service | Alignment | Proving | Aligned Ready | In-Service |
+|-------------------------------------------------------------------|----------------|-----------|---------|------------------------------------------------------------------------|------------------------------------------------------------------------|
+| Event | 1 | 2 | 3 | 4 | 5 |
+| Expiry timer
RSREC | / | / | / | 4 | 5 |
+| Signalling Link below
acceptable performance level
(Note 4) | / | / | / | MAAL-
RELEASE.
request
stop timer NC
stop timer RSREC
1 | MAAL-
RELEASE.
request
stop timer NC
stop timer RSREC
1 |
+
+| Impossible by the definition of the boundary condition
+/ Impossible by the definition of LM internal events
+MAAL-PROVING\_UNS MAAL-PROVING\_UNSUCCESSFUL
+MAAL-LOC\_PROC\_OUT MAAL-LOCAL\_PROCESSOR\_OUTAGE
+MAAL-LOC\_PROC\_REC MAAL-LOCAL\_PROCESSOR\_RECOVERED
+RSREC Timer\_REPEAT-SREC
+NC Timer\_NO-CREDIT
+
+NOTES
+1 The Local Management proving status is set to "NORMAL" by implementation dependent means.
+2 This event is implementation specific.
+3 The detection of local processor outage is implementation dependent.
+4 See 9.1.1.
+
+# 7 Interface to systems management
+
+The interface to systems management is for further study. The real system resources that may be managed by this interface are listed in Annex A.
+
+# 8 Peer-to-peer Layer Management communication
+
+The use of peer-to-peer Layer Management messages is for further study. SSCOP has provided the MAA-UNITDATA signal type for such communication should the need for it arise.
+
+# 9 Procedures of Layer Management
+
+## 9.1 Error processing
+
+The various protocol errors reported by SSCOP to Layer Management are found in Appendix I. The actions taken, beyond those specified in Table 3, upon receipt of these error notifications may be network specific.
+
+### 9.1.1 Error Monitoring for In-Service Links
+
+Layer Management determines when the performance of an In-Service link has deteriorated to the point where the link should be taken out of service. Information contained in MAA-ERROR.indication signals from SSCOP and in MAAL-REPORT.indication signals from the SSCF can be used for this purpose. When a determination is made that performance is unsatisfactory, the MAAL-RELEASE.request signal is issued from Layer Management to the SSCF.
+
+Error monitoring is a mandatory feature on the transmitting side of NNI signalling links, but the need for a standardized algorithm to make this determination is for further study. The ideal error monitoring algorithm would satisfy simultaneously the following criteria:
+
+#### 1) *Burst tolerance*
+
+To avoid unnecessary changeovers, the error monitor should tolerate all error bursts of duration less than 300 ms and should tolerate error bursts of duration 400 ms with probability 0.9.
+
+#### 2) *Limit data to be retrieved*
+
+If cell error ratios approaching 1.0 persist on the link, the error monitor should take the link out of service quickly enough that at the time the error monitor determines that the link is to be taken out of service, the amount of traffic that must be retrieved does not exceed twice the traffic that arrives from the upper layer in TE1.
+
+TE1 is the maximum time between the beginning of an error burst of length 400 ms and the arrival at the transmitter of the STAT triggered by the first POLL sent after the error burst terminates; it is equal to the sum of 400 ms plus the SSCOP Timer\_POLL and the delay between the sending of a POLL and the receipt of the resulting STAT, including the round trip propagation delay and the possible queueing delays for the POLL and STAT, which are limited by the implementation dependent "lower layer busy" mechanism within SSCOP.
+
+#### 3) *Avoidance of excessive delays*
+
+The error monitor should prevent signalling traffic from experiencing excessive delays for an extended period of time. Characterization of "excessive delays" and "extended period of time" is for further study.
+
+#### 4) *Limit of buffer*
+
+The amount of traffic in the buffer at link failure at any cell error ratio should not exceed 1.4 times the amount in the buffer at link failure when the cell error ratio approaches 1.0.
+
+#### 5) *No unnecessary Out-of\_Service Events*
+
+If the effective BER of the signalling link is less than $10^{-7}$ for links of speed up to 4 Mbits/s, the mean time between link failures declared by the error monitor should exceed $10^6$ s.
+
+#### 6) *Effectiveness Under Small Load Conditions*
+
+If the effective BER is $10^{-4}$ or greater and the user load is at least 0.01 erlang, the error monitor should take the link out of service within 600 s with probability 0.9.
+
+#### 7) *Administrative Ease*
+
+It is desirable that the error monitor not require manual adjustments of its parameters to meet the preceding criteria for links of different speeds, lengths and traffic characteristics (e.g. load or message size distributions). At a minimum, an error monitor designed to meet the criteria on a link of a given speed and TE1 should continue to meet the criteria for all link lengths and traffic characteristics yielding a smaller TE1, provided criterion 2 is interpreted as limiting the retrieved traffic to the amount of traffic that arrives in 2 times TE1\*, where TE1\* is the TE1 of the original link.
+
+An example algorithm is given in Appendix II.
+
+##### NOTES
+
+- 1 Simulation studies indicate that the algorithm in Appendix II meets the above criteria for a wide range of link speeds, link loads, and traffic characteristics, although not all possibilities were studied.
+- 2 This algorithm requires information from SSCOP and SSCF at the NNI beyond that provided by the MAA-ERROR and MAAL-REPORT signals defined in the Recommendations Q.2110 [2] and Q.2140 [3], respectively. It is a local matter how this information is provided.
+- 3 The use of other algorithms that meet criteria established by the network operators using the link is not precluded.
+
+### 9.1.2 Detection of Excessive Time with no Credit
+
+SSCOP notifies Layer Management (using the MAA-ERROR.indication signal) when it has message(s) to send to its peer but cannot do so because it has not been given credit to do so. SSCOP also notifies Layer Management (using the MAA-ERROR.indication signal) when it again has credit to send at least one message. Layer Management shall issue an MAAL-RELEASE.request when the length of a period of no credit exceeds a threshold.
+
+NOTE – A similar function is performed in MTP-2 via timer T6, as described in clause 9/Q.703 [4].
+
+### 9.1.3 Detection of Closely Spaced SSCOP Recoveries
+
+SSCF notifies Layer Management (using MAAL-REPORT.indication) when an SSCOP recovery takes place. Layer Management ensures that the link does not remain in service if closely spaced SSCOP recoveries take place. If Layer Management receives an MAAL-REPORT.indication indicating an SSCOP recovery, it checks to see if Timer\_REPEAT-SREC is active. If it is active, Layer Management issues an MAAL-RELEASE.request and sets the local management proving status to NORMAL, ensuring that the link must successfully pass proving before it can be put in service. Whether the timer is active or not, Layer Management then sets it so a subsequent closely spaced recovery can be detected. When Timer\_REPEAT-SREC expires, no action is taken.
+
+## 9.2 Measurements
+
+The Layer Management shall maintain various counters for interrogation by systems management and report specified events autonomously to systems management. The set of measurements that should be supported includes the contents of Table 4.
+
+The usage of the measurements identified in Table 4 has been categorized to correspond to OSI management categories of Recommendation Q.750 [6] and the “administration” category of Recommendation Q.752 [7]. These measurements may be used singly or in conjunction with other measurements by the network administration for management, administration or planning purposes.
+
+The applicable usage categories are defined as follows:
+
+- **Fault (F)** – This category utilizes on occurrence events and measurements to report and detect faults, and monitor the signalling network response to abnormal conditions. Measurements made for this purpose are usually made for use in near real time, but resources performing to “just acceptable” limits might require long measurement intervals.
+- **Network planning and administration (N)** – This category involves measurements that are used on a long-term basis and are generally retained external to the signalling network resources. The activities include planning and dimensioning (engineering) the signalling network resources, including determination of the resource quantities, e.g. number of link sets, and resource configuration, e.g. routing.
+- **Performance (P)** – This category is used for near real time, medium-term and long-term control. The purpose is to sustain network performance, over both the short and long terms.
+- **Near real time measurements (R)** – This classification is applied, in addition to the categories defined above, for those measurements which are for use in near real time. Usually, it is applied to those measurements which are marked as “on occurrence,” or “1st & interval», or “5 minute” duration. These measurements include all alarms that might require immediate attention.
+
+TABLE 4/Q.2144
+
+### **Signalling link faults and performance**
+
+| No. | Description of measurements | Units | Support required | Usage | Duration (Note) |
+|-----|---------------------------------------------------------|-----------|------------------|-----------------|-----------------|
+| 1 | Duration of link in the In-Service state | Secs/SL | M | F, P, N | 30 min |
+| 2 | SL failure – all reasons | Event/SL | M | F, R, P | On occurrence |
+| 3 | SL failure – No_RESPONSE Timer expiration | Event/SL | O | F, R, P | On occurrence |
+| 4 | SL failure – excessive error rate | Event/SL | O | F, R, P | On occurrence |
+| 5 | SL failure – excessive duration of congestion | Event/SL | O | F, R, P | On occurrence |
+| 6 | SL alignment failure | Event/SL | O | F, R
F, P | 5 min
30 min |
+| 7 | Number of MAA-ERROR indications with Error Type SD loss | Events/SL | O | F, R, P
F, P | 5 min
30 min |
+
+F Fault
+M Mandatory
+N Network planning and administration
+O Optional
+P Performance
+R Near real time measurements
+SL Signalling Link
+NOTE – Entities in this column specify the measurement interval applicable for each measurement.
+
+### **9.2.1 Duration of presence in In-Service state**
+
+The SAAL Layer Management can determine when a signalling link goes into the In-Service state based upon the receipt of an MAAL-REPORT.indication signal from the SSCF indicating “Link In Service.” Similarly, it can determine when a link is taken out of service based upon receipt of an MAAL-REPORT.indication from the SSCF indicating “Out of Service”. The difference in time of arrival of these signals represents the duration of that link being in the In-Service state.
+
+### **9.2.2 Signalling Link Failures**
+
+Failure events and the reasons for them can be obtained through MAAL-REPORT.indication signals from the SSCF and through MAA-ERROR.indication signals from SSCOP. In particular, signalling link failures caused by the expiry of the SSCOP Timer\_NO-RESPONSE can be detected by receiving an MAA-ERROR.indication with the Code parameter set to P.
+
+Excessive error rate failures may be determined by the SAAL Layer Management through its error monitoring function for In-Service links. This function is described in 9.1.1.
+
+Excessive duration of congestion can be determined by the SAAL Layer Management through the Layer Management function for detection of excessive time with no credit. This function is described in 9.1.2.
+
+Signalling link alignment failures can be determined by the SAAL Layer Management based upon receipt of MAAL-REPORT.indication signals indicating “Alignment Not Successful”.
+
+The SAAL Layer Management may utilize an internal counter for accumulating the number of MAA-ERROR.indications that it receives for each signalling link from SSCOP.
+
+### 9.2.3 Signalling Link Restoration
+
+The SAAL Layer Management can only determine when the signalling link goes into the In-Service state. This is based upon the receipt of MAAL-REPORT.indication signals from the SSCF indicating "Link In Service." Only MTP-3 can determine when it considers the signalling link to be restored, i.e. after successful completion of signalling link test (see clause 12/Q.704 [5]). Therefore, specification of signalling link restoration measurements are beyond the scope of this Recommendation.
+
+## 9.3 Handling of processor outage conditions
+
+Implementation dependent functions determine when factors at a functional level higher than SAAL (e.g. when received messages cannot be transferred to functional levels higher than SAAL) preclude the use of the link and cause the Layer Management entity to issue the MAAL-LOCAL\_PROCESSOR\_OUTAGE.request signal to the SSCF. When the use of the link is again possible the Layer Management entity issues the MAAL-LOCAL\_PROCESSOR\_RECOVERED.request signal to the SSCF.
+
+The SSCF notifies SAAL Layer Management of a condition of remote processor outage via an MAAL-REPORT.indication signal indicating "Remote Release" and "Processor Outage". This information is useful in trouble sectionalization of difficulties and in network performance measurements. The actions taken upon receipt of these error notifications may be network specific.
+
+## 9.4 Management of signalling link proving
+
+While the SSCF is sending proving messages over the link, the Layer Management entity must make a determination of whether the link performance is satisfactory. It uses the MAAL-ERROR.indication signals it receives from SSCOP and MAAL-REPORT.indication signals it receives from SSCF to make this determination. The number of messages sent during normal proving (parameter n1 in Recommendation Q.2140 [3]) and the maximum permissible retransmissions during a successful proving attempt (Max\_NRP) should be such that the probability of proving the link successfully within eight minutes does not exceed 0.05 when the error ratio is such that the mean time for which the In-Service error monitor will leave the link in service is less than one day.
+
+The SSCF notifies Layer Management of the beginning of proving with the MAAL-PROVING.indication. Layer Management notifies the SSCF that proving is unsuccessful with the MAAL-PROVING\_UNSUCCESSFUL.response. If an MAAL-STOP\_PROVING.indication is received from the SSCF, then procedures related to proving in the Layer Management entity are stopped.
+
+The ability for Layer Management to override the decision of whether to perform normal or emergency proving, usually made by the user of the SSCF, is possible by using the MAAL-FORCE\_PROVING.request to notify the SSCF to use forced proving and by using the MAAL-FORCE\_EMERGENCY.request. Layer Management informs the SSCF to cancel forced normal proving or forced emergency proving through the use of an MAAL-CLEAR\_FORCE\_MODES.request. The algorithm used to decide when to force any mode of proving and when to cancel such force modes may be network specific.
+
+# Annex A
+
+## Real system resources
+
+(This annex forms an integral part of this Recommendation)
+
+Besides the Layer Management states (Out Of Service, Alignment, Proving, Aligned Ready, In-Service) that are described in clause 6 and the measurements that are described in clause 9.2, the following real system resources, i.e. timers and parameters may be managed via the interface between Layer Management and system management.
+
+| Parameter or timer | Default value |
+|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|
+| SSCOP parameters and timers (Note 1) | |
+| k | 4096 octet |
+| j | 4 octet |
+| MaxCC | 4 |
+| MaxPD | 500 |
+| Timer_CC | 200 milliseconds |
+| Timer_KEEP-ALIVE | 100 milliseconds |
+| Timer_NO-RESPONSE | 1.5 seconds |
+| Timer_POLL | 100 milliseconds |
+| Timer_IDLE | 100 milliseconds |
+| MaxSTAT | 67 |
+| SSCF parameter and timers (Note 2) | |
+| Timer T1 | 5 seconds |
+| Timer T2 | 30 seconds |
+| Timer T3 | Such that loading of the signalling link is approximately 50% of its nominal cell rate |
+| n1 | 1 000 |
+| Layer Management parameters and timers | |
+| Max_NRP | 0 |
+| Timer_REPEAT-SREC | 1 hour |
+| Timer_NO-CREDIT | 1.5 seconds |
+| NOTES | |
+| 1 Defined in 7.6/Q.2110 and 7.7/Q.2110 [2] and repeated here for convenience. | |
+| 2 Defined in Recommendation Q.2140 [3] and repeated here for convenience. | |
+
+Furthermore, the internal flags LPO (Local Processor Outage) and MPS (Management Proving State) of the SSCF at the NNI are real system resources. The use of these flags, their sets of values, and their initial values are described in clause 12/Q.2140 [3].
+
+# Appendix I
+
+## Management error indications
+
+(This appendix does not form an integral part of this Recommendation)
+
+A number of events will cause errors to be submitted to the layer management entity. The associated error parameter contains the error code that describes the specific error conditions.
+
+The column entitled “Error Condition” describes specific protocol error events and the basic state of the SSCOP entity at the point when the MAA-ERROR.indication primitive is generated. Should differences be detected between this description of the management error indications and the specification comprised in Annex A/Q.2110 [2], the specification of Recommendation Q.2110 [2] takes precedence.
+
+| Error type | Error code | Error condition |
+|---------------------------------------------|------------|-----------------------------------|
+| Receipt of unsolicited or inappropriate PDU | A | SD PDU |
+| | B | BGN PDU |
+| | C | BGAK PDU |
+| | D | BGREJ PDU |
+| | E | END PDU |
+| | F | ENDAK PDU |
+| | G | POLL PDU |
+| | H | STAT PDU |
+| | I | USTAT PDU |
+| | J | RS |
+| | K | RSAK PDU |
+| | L | ER |
+| | M | ERAK |
+| Unsuccessful retransmission | O | VT(CC) >= MaxCC |
+| | P | Timer_NO-RESPONSE expiry |
+| Other list elements error type | Q | SD or POLL, N(S) error |
+| | R | STAT N(PS) error |
+| | S | STAT N(R) or list elements error |
+| | T | USTAT N(R) or list elements error |
+| | U | PDU length violation |
+| SD loss | V | SD PDUs must be retransmitted |
+| Credit condition | W | Lack of credit |
+| | X | Credit obtained |
+
+# Appendix II
+
+## Example of error monitoring of In-Service links
+
+(This appendix does not form an integral part of this Recommendation)
+
+## II.1 Overview
+
+This error monitor comprises three algorithms.
+
+**High Error Rates:** Algorithm 1 removes the link from service whenever the queue of untransmitted and unacknowledged messages, i.e. the sum of the SSCOP transmission queue and transmission buffer, exceeds the maximum queue that could be caused by an error burst of length 400 ms, given the input traffic and link capacity. This algorithm responds accurately to extreme traffic conditions (e.g. overload) as well as expected traffic conditions.
+
+**Intermediate Error Rates:** Algorithm 2 removes the link from service when retransmissions occur too frequently within the monitoring intervals. This algorithm removes a link from service when errors are sufficient to cause unacceptable delays, but not so severe as to cause sufficient queue build up to trigger the first algorithm.
+
+**Low Error Rates and Low Traffic:** Algorithm 3 removes the link from service when the number of POLLs within a large block, termed a superblock, that fail to be acknowledged with a STAT exceeds a threshold. This algorithm discovers problems on links when they are carrying little or no user traffic.
+
+## II.2 Detailed description
+
+The error monitor periodically (every $\tau$ seconds) makes a determination of whether the link should be taken out of service. The following information is assumed to be available at the end of each monitoring interval:
+
+- 1) NA: The length of the PDUs that arrived from the upper layer during the last $\tau$ seconds (the monitoring interval). This value is obtained from the SSCF via an implementation specific mechanism.
+- 2) MCR: The maximum number of PDU cells that are allowed to pass to the lower layer during the interval [this value is available to the SSCF as part of the requirement that the AAL not overrun the ATM layer (see 6.1.3/Q.2140 [3])].
+- 3) NF: The length of the PDUs freed from the retransmit buffer during the interval. (This value is computed during the SSCOP processing of STATs and USTATs via an implementation specific mechanism.)
+- 4) CRED: An indication that credit was denied at any time during the preceding interval. CRED = 1 if credit was denied, CRED = 0 otherwise. (This information is reported by SSCOP to Layer Management as an error indication.)
+- 5) ROLLBACK: An indication that window has been rolled back in the preceding interval. Rollback occurs whenever the receiver has closed the transmission window so that previously transmitted PDUs will not be accepted by the receiver. ROLLBACK = 1 if rollback has occurred, ROLLBACK = 0 otherwise. (ROLLBACK can be detected during the SSCOP processing of STAT and USTATs via an implementation specific mechanism.)
+- 6) rexit\_flag: A flag that indicates PDUs were put in the retransmission queue in the preceding interval and the retransmissions were not caused by a credit rollback by the remote receiver. [This information can be determined from MAA-ERROR indications (code V) and indications of credit rollback and advancing VT(S)].
+
+- 7) PI-count: A count of the number of POLLS that have been sent since the beginning of the current superblock. (Layer Management could accumulate this count if SSCOP simply gives an indication every time a POLL is sent.)
+- 8) ct\_stats: A count of the number of STATs that have been received since the beginning of the current superblock. (Layer Management could accumulate this count if SSCOP simply gives an indication every time it receives a STAT.)
+
+A flow chart of the algorithm is given in Figure II.1. This flow chart also uses the following variables:
+
+- 9) seqno: VT(S) at the time of the most recent sending of a POLL. This value is obtained from SSCOP via an implementation specific mechanism.
+- 10) prev\_seqno: VT(S) value from the previous polling interval.
+- 11) rollback: A Boolean to indicate credit has been withdrawn by the remote receiver for those already transmitted SD PDUs, and VT(S) has not advanced since the credit rollback.
+- 12) stat\_received: A Boolean to indicate that a STAT has been received since the most recent SSCOP connection establishment or recovery.
+- 13) tot\_penalty: Running total of the penalty factors for the polling intervals within a block.
+- 14) block\_qos: QOS value for the current block.
+- 15) tot\_qos: Overall running QOS value.
+- 16) I\_count: A count of successive error monitoring intervals.
+- 17) NAVECT: A vector that stores the most recent N values of NA, where N is the number of error monitoring intervals required to span the time when data may not be acknowledged because of an error event of duration 400 ms.
+- 18) MCVECT: A vector which stores the most recent N values of MCR.
+- 19) IX: An index used to access the appropriate entry in MCVECT or NAVECT.
+- 20) Q: The total length of PDUs currently in the SSCOP Transmission queue and Transmission buffer.
+- 21) TTH: See definition in third paragraph following.
+- 22) FTH: See definition in third paragraph following.
+- 23) I: An index used to access the appropriate entry in MCVECT or NAVECT during computation of the effects of a credit rollback.
+- 24) Y: A temporary variable used to store the minimum of Q and TTH during computation of the effects of a credit rollback.
+- 25) QT: A temporary variable used to sum entries of NAVECT during computation of the effects of a credit rollback.
+
+Algorithm 1 computes Q, the queue length, by simply maintaining a cumulative sum of NA minus NF. It takes the link out of service if Q exceeds a threshold T, which is the total length of PDUs that could be in the transmit and retransmit buffers due to any error event with Bit Error Ratio (BER) of 1 that has occurred in the recent past for a duration of 400 ms, the value based on Criterion 1 in 9.1.1.
+
+This length T includes PDUs in the buffers just prior to the onset of the error event, the PDUs added to the buffers during the event and the PDUs added to the buffers after the event has abated up to the point where messages are released from the transmit buffer. T is computed by maintaining a history of the NAs (in NAVECT) and MCRs (in MCVECT) over the last N intervals. N is the number of $\tau$ second intervals needed to span the time when messages are not released from the buffers as a result of a 400 ms second error event. IX, an index that is incremented modulo N to address the oldest (N intervals prior) elements of NAVECT and MCVECT, is used to efficiently update T, NAVECT and MCVECT.
+
+T has two components:
+
+- 1) TTH – The amount of data that would be held in the transmit buffer as the result of a 400 ms error event (including the necessary POLL and round trip delay times). This is the sum of the elements of NAVECT after all updates have been completed.
+- 2) FTH – The length of the PDUs in the buffer due to the arrivals (NA) that exceed the VC's capacity (MCR) for N or more intervals back in time. FTH is computed by cumulative summation of the NAVECT[IX] – MCVECT[IX] prior to the updating of NAVECT and MCVECT. FTH is allowed to be a minimum of 0 (no overload need be accounted for).
+
+Algorithm 1 periodically updates Q, TTH and FTH and tests to determine whether T is exceeded.
+
+Algorithm 1 responds appropriately to denial of credit and rollback. In either case, the error monitor assumes that no cells were allowed to be transmitted in the affected intervals. If credit is denied at any time during the preceding interval (CRED = 1) then MCVECT[IX] is set to 0. If the window is rolled back during the preceding interval (ROLLBACK = 1), then elements of MCVECT corresponding to intervals when PDUs currently in the transmit queues arrived are set to 0. In both instances, FTH will increase at the appropriate time to account for the window closings. This may present a slightly pessimistic estimate of the impact of credit denial and rollback. However, it has the side effect of forcing the error monitor to tolerate congestion. In this case, as in overload, the congestion, which is due to the network elements themselves and not VC error phenomena, is expected and should be tolerated.
+
+At the end of each monitoring interval, Algorithm 2 sets a penalty factor for the interval to either 1 or 0 depending on whether any reports of retransmissions have been received from SSCOP during the interval. At the end of every N\_blk interval, a Quality Of Service (QOS) measure for the block is computed as the arithmetic average of the penalty factors and an overall (or running) QOS is computed by using exponential smoothing over consecutive block QOSs. That is, if Q denotes the running QOS and Q\_b denotes the QOS from the current block, Q is updated as follows:
+
+$$Q = (1 - \alpha) * Q + \alpha * Q\_b$$
+
+where $\alpha$ is the exponential smoothing factor in the range (0,1). Whenever the running QOS exceeds a threshold "thres", the link is taken out of service. To prevent the error monitor from taking the link out of service because of retransmissions caused by a rollback in credit by the remote SSCOP receiver, the error monitor ignores all retransmission reports from SSCOP from the time it receives an indication of a credit rollback until after it receives the indication of a sending of a POLL by SSCOP with a VT(S) value that is higher than the VT(S) value when the credit rollback indication was received. Note that excessive time with lack of credit is independently supervised by the Layer Management, so the error monitor does not need to monitor such time also.
+
+In the absence of user PDUs, Algorithms 1 and 2 are ineffective. The only monitoring on such a link is that the no-response timer will cause a link failure for severe errors or complete loss of connectivity. Some signalling links may be used predominantly in alternate routes and have nearly no traffic under normal conditions, but it is best not to find out that the link has an excessive error rate only when the normal routes become unusable and traffic is placed on the alternate route. Therefore, Algorithm 3 uses traffic that is always on the link, the POLLS and STATS. Over a superbblock of N\_sup polling intervals (on the order of 1000) the number of received STATS is accumulated. If the number of received STATS is less than the number of transmitted POLLS by more than a threshold N\_loss, the link is taken out of service. Otherwise accumulation of STATS over another superbblock is begun. To prevent the algorithm from being influenced by the delay in receiving an initial STAT upon SSCOP connection establishment or recovery on a high delay link, the algorithm behaves as if STATS are received in every polling interval until the first STAT is actually received.
+
+Timer\_NO-RESPONSE will fail the link if the first STAT is not received in an acceptable amount of time. Although Algorithm 3 is most conveniently described using the counts $N_{sup}$ and $N_{loss}$ , the values of these counts must change if the SSCOP Timer\_POLL is changed. Therefore, it is best to consider the primary parameters of the algorithm to be the amount of time that corresponds to these counts when Timer\_POLL is at its default value. These time parameters are denoted $T_{sup}$ and $T_{loss}$ . Then the counts are set as follows where $T_{poll}$ is the actual value of Timer\_POLL: $N_{sup} := T_{sup}/T_{poll}$ ; $N_{loss} := T_{loss}/T_{poll}$ .
+
+When SSCOP recovery takes place, all three algorithms are reinitialized. For Algorithm 1, the initial value of NA is set to the number of cells in messages in the transmission queue after the transmission buffer is cleared. This value is obtained from SSCOP in an implementation dependent manner.
+
+All the primary parameters of the algorithms and their recommended default values are listed below:
+
+- $T_{sup}$ : Superblock size in seconds. (Default value: 120 s.)
+- $T_{loss}$ : STAT loss limit in seconds. (Default value: 1.3 s.)
+- $\alpha$ : Exponential smoothing factor. (Default value: 0.1.)
+- thres: Threshold for comparing the running QOS. (Default value: 0.244.)
+- $\tau$ : Error Monitoring Interval. (Default value 0.1 s.)
+- N: Monitoring intervals needed to span the time when messages are not released from buffers as a result of a 400 ms error event. (Default value 9.)
+- $N_{blk}$ : Number of monitoring intervals in a block for Algorithm 2. (Default value 3.)
+
+## II.3 Rationale for default parameters
+
+$N * \tau$ must be chosen to span the time when messages are not positively acknowledged because of a 400 ms error event. The default design is for a link of 100 ms round trip delay and 100 ms Timer\_POLL, and up to 100 ms queueing delay for a POLL and STAT pair. Thus, TE1, i.e. the maximum time until arrival of a STAT calling for the retransmission of the first PDU affected by the error burst, for the default design is 600 ms. After this STAT arrives, the SD PDU can be retransmitted, but the STAT that acknowledges it may not arrive until after another Timer\_POLL plus the round trip delay plus the possible queueing delays. This is a total of 900 ms. To minimize the amount of buffered traffic at changeover a value of N of the order of 10 is desirable. Default values of N = 9 and $\tau$ = 100 ms are chosen. A smaller $\tau$ will reduce retrieved traffic somewhat at the expense of more computation.
+
+Grouping the monitoring intervals into blocks of 3 ( $N_{blk}$ ) improves the burst tolerance of Algorithm 2.
+
+The parameters $\alpha$ and thres are chosen together to give good burst tolerance and to ensure that link is removed from service quickly whenever the error ratio on the link is below the sustainable BER, i.e. the highest BER at which delays are considered acceptable. The default values are chosen so that the second algorithm will tolerate eight consecutive intervals of penalty equal to 1. This means that Algorithm 2 will tolerate nearly all 500 ms bursts and more than 90% of 600 ms bursts. (Thus, the combination of Algorithms 1 and 2 will have a burst tolerance very similar to that of Algorithm 1 acting alone.) Minimizing $\alpha$ and thres subject to this constraint, and the constraint that a 4 Mb/s link (at arbitrary load) remain in service for $10^6$ seconds at BER of $10^{-7}$ gives a design that minimizes link meantime to failure at moderate error rates, better limiting the persistence of unacceptable delays for signalling traffic. This gives the defaults of $\alpha = 0.1$ and thres = 0.244.
+
+The parameter $T_{loss}$ can be chosen to allow for STAT deficiency due to one error burst of length $t_b$ seconds, two random errors, and queueing delays suffered by POLLs or STATs at the edges of a superblock. Thus, a $T_{loss}$ of 1.3 sec is sufficient. $T_{sup}$ is chosen to enforce a given link quality, denoted $\theta$ , under random errors and zero offered load. It suffices to choose $\theta$ as the sustainable BER of a 4 Mbit/sec link at normal engineered load. This gives $\theta$ of approximately $5 * 10^{-6}$ , which, in turn, gives $T_{sup}$ equal approximately 120 sec. (A very precise calculation of $T_{sup}$ is unnecessary.)
+
+## II.4 Proving
+
+When the default values given above are used for the In-Service error monitor and Timer\_POLL is 100 ms, the following default values for proving parameters will satisfy the criterion given in 9.4.
+
+Max\_NRP = 1
+
+$n1/Q.2140 = 4200 + 41*(Y - 64)$ where Y is nominal link speed in kbit/s
+
+T3/Q.2140 = such that n1 cells are generated in one minute
+
+T2/Q.2140 = 120 seconds
+
+The effective BER at which a link will fail to prove in within eight minutes ranges from $4 * 10^{-6}$ for a 64 kbit/s link to $1 * 10^{-7}$ for a 4 Mbit/s link.
+
+
+
+```
+
+graph TD
+ S1[ ] --> Init1["N_sup := T_sup/T_poll
+N_loss := T_loss/T_poll"]
+ Init1 --> Idle1["1
+Idle"]
+ Idle1 --> Start[/Start/]
+ Start --> Init2["NA := 0"]
+ Init2 --> Connector1((1))
+ Connector1 --> Init3["PI_count := 0
+rexit_flag := 0
+rollback := false
+prev_seqno := 0
+tot_penalty := 0
+tot_qos := 0
+l_count := 0
+ct_stats := 0
+stat_received := false
+failure := false
+ROLLBACK := 0
+CRED := 0
+NAVECT(l) := 0, l := 0 to N - 1
+MCVECT(l) := 0, l := 0 to N - 1
+Q := 0
+NF := 0
+IX := 0
+FTH := 0
+TTH := 0"]
+ Init3 --> SetTimer["Set Timer_tau"]
+ SetTimer --> Wait2["2
+Wait"]
+
+```
+
+[Issued upon transition by layer management to Proving state is equivalent to the signal MAAL-PROVING.indication]
+
+[from Figure II.1 (sheet 4 of 6)]
+
+Flowchart for Error monitor state transitions. It starts with an unlabeled state, followed by an initialization block (N\_sup := T\_sup/T\_poll, N\_loss := T\_loss/T\_poll), then an Idle state (1). A transition 'Start' leads to an initialization block (NA := 0). A connector (1) leads to a large initialization block with many variables. This is followed by 'Set Timer\_tau' and a Wait state (2). Annotations explain the 'Start' transition and the connector.
+
+T1172800-95/d03
+
+FIGURE II.1/Q.2144 (sheet 1 of 6)
+**Error monitor**
+
+
+
+```
+
+graph TD
+ Start((2 Wait)) --> Poll[POLL generated with seqno (VT(S)) ]
+ Start --> Credit[credit rollback ]
+ Start --> Retrans[retransmission MAA-ERROR. indication (V) ]
+ Start --> Stat[stat arrived ]
+
+ Poll --> Seqno{seqno > prev_seqno}
+ Seqno -- No --> Wait2((2 Wait))
+ Seqno -- Yes --> RollbackFalse[rollback := false]
+ RollbackFalse --> PrevSeqno[prev_seqno := seqno
+PI_count := PI_count + 1]
+ PrevSeqno --> StatReceived{stat_received}
+ StatReceived -- false --> CtStats1[ct_stats := ct_stats + 1]
+ CtStats1 --> Wait3((2 Wait))
+ StatReceived -- true --> Wait3
+
+ Credit --> RollbackTrue[rollback := true
+ROLLBACK := 1]
+ RollbackTrue --> Wait4((2 Wait))
+
+ Retrans --> RollbackRetrans{rollback}
+ RollbackRetrans -- true --> RexmitFlag[rexmit_flag := 1]
+ RexmitFlag --> Wait5((2 Wait))
+ RollbackRetrans -- false --> Wait5
+
+ Stat --> CtStats2[ct_stats := ct_stats + 1]
+ CtStats2 --> StatReceived2[stat_received := true]
+ StatReceived2 --> Wait5
+
+```
+
+Flowchart for Error monitor (FIGURE II.1/Q.2144 (sheet 2 of 6)). The process starts at a 'Wait' state (2) and branches into four events: 'POLL generated with seqno (VT(S))', 'credit rollback', 'retransmission MAA-ERROR. indication (V)', and 'stat arrived'. Each event leads to specific logic and returns to a 'Wait' state (2).
+
+T1172810-95/d04
+
+FIGURE II.1/Q.2144 (sheet 2 of 6)
+**Error monitor**
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> Wait2: 2
+ state "Wait" as Wait2
+ state "Timer_τ" as Timer_tau
+ state "no credit MAA-ERROR. indication (W)" as no_credit
+ state "messages freed (m cells)" as messages_freed
+ state "messages arrived (n cells)" as messages_arrived
+ state "MONITOR" as MONITOR
+ state "CRED := 1" as CRED
+ state "NF := NF + m" as NF
+ state "NA := NA + n" as NA
+ state "failure" as failure
+ state "Set timer_τ" as Set_timer
+ state "MAAL-RELEASE. request" as MAAL_RELEASE
+ state "To SSCF" as To_SSCF
+ state "Idle" as Idle
+ state "Wait" as Wait
+
+ Wait2 --> Timer_tau
+ Wait2 --> no_credit
+ Wait2 --> messages_freed
+ Wait2 --> messages_arrived
+
+ Timer_tau --> MONITOR
+ no_credit --> CRED
+ messages_freed --> NF
+ messages_arrived --> NA
+
+ MONITOR --> failure
+ CRED --> NF
+ NF --> NA
+ NA --> Wait
+
+ failure --> Set_timer: false
+ failure --> MAAL_RELEASE: true
+ Set_timer --> Wait
+ MAAL_RELEASE --> To_SSCF
+ To_SSCF --> Idle
+ Idle --> [*]
+
+```
+
+Flowchart for Error monitor state transitions. It starts at a 'Wait' state (2) and branches based on inputs from SSCOP and SSCF. Inputs from SSCOP include 'Timer\_τ' leading to 'MONITOR' and 'no credit MAA-ERROR. indication (W)' leading to 'CRED := 1'. Inputs from SSCF include 'messages freed (m cells)' leading to 'NF := NF + m' and 'messages arrived (n cells)' leading to 'NA := NA + n'. A 'failure' decision follows 'MONITOR'. If 'true', it goes to 'MAAL-RELEASE. request' (To SSCF) and then to 'Idle' (1). If 'false', it goes to 'Set timer\_τ' and then back to 'Wait' (2). All state changes lead to a common 'Wait' (2) state. Reference T1172820-95/d05.
+
+FIGURE II.1/Q.2144 (sheet 3 of 6)
+**Error monitor**
+
+
+
+State transition diagram for the Error monitor. The initial state is 'Wait' (labeled 2). Transitions are triggered by events from SSCF, SSCOP, or layer management. From 'Wait', a transition 'SSCOP Recovery MAAL-REPORT.indication (-,-,SREC)' leads to 'Reset Timer\_τ' and back to 'Wait'. A transition 'begin local SCCOP recovery MAA-ERROR.indication (Q,R,S, or T)' leads to 'Reset Timer\_τ' and back to 'Wait'. A transition 'transmission buffer cleared, transmission queue has k cells' leads to 'NA := k' and then to state '1' (labeled to Figure II.1 (sheet 1 of 6)). A transition 'Stop' leads to state '1' (Idle). A bracket indicates that the 'Stop' transition is 'Issued by layer management upon transition to Out of Service or Alignment states (Note)'.
+
+NOTE – This signal is equivalent to any of the following events:
+
+| | |
+|------------------------------------------|----------------------------------------|
+| MAAL-REPORT.indication (LR,OOS,-) | MAAL-REPORT.indication (SR,OOS,-) |
+| MAAL-REPORT.indication (RR,OOS,SSCOP-UU) | MAAL-REPORT.indication (LR,-,PE) |
+| MAAL-REPORT.indication (RR,OOS,ANS) | MAAL-REPORT.indication (RR,-,SSCOP-UU) |
+| MAAL-REPORT.indication (LR,-,CD) | MAAL-LOC_PROC_OUT.request |
+| MAAL-REPORT.indication (SR,-,-) | |
+| MAAL-REPORT.indication (LR,OOS,PE) | |
+
+In addition, an MAAL-RELEASE.request generated outside this error monitor is also equivalent to this signal.
+
+T1172830-95/d06
+
+FIGURE II.1/Q.2144 (sheet 4 of 6)
+**Error monitor**
+
+
+
+```
+
+graph TD
+ MONITOR([MONITOR]) --> Init["FTH := MAX(0, FTH + NAVECT(IX) - MCVect(IX))
+TTH := TTH + NA - NAVECT(IX)
+NAVECT(IX) := NA
+Q := Q + NA - NF
+I_count := I_count + 1"]
+ Init --> CRED{CRED}
+ CRED -- 1 --> M0["MCvect(IX) := 0"]
+ CRED -- 0 --> M1["MCvect(IX) := MCR"]
+ M1 -.-> Note["MCR is computed by an implementation-dependent function"]
+ M0 --> ROLLBACK{ROLLBACK}
+ M1 --> ROLLBACK
+ ROLLBACK -- 1 --> InitI["I := IX
+QT := 0
+Y := MIN(Q, TTH)"]
+ InitI --> QTY{QT : Y}
+ QTY -- < --> UpdateI["MCvect(I) := 0
+QT := QT + NAVECT(I)
+I := (I - 1)%N"]
+ UpdateI --> QTY
+ QTY -- ≥ --> QTF{Q: TTH + FTH}
+ ROLLBACK -- 0 --> QTF
+ QTF -- > --> Failure["failure := true"]
+ QTF -- ≤ --> Reset["IX := (IX + 1)%N
+ROLLBACK := 0
+CRED := 0
+NA := 0
+NF := 0"]
+ Reset --> Connector2((2))
+ Failure --> FailureExit([ ])
+
+```
+
+Flowchart for Error monitor algorithm. The process starts with a MONITOR entry, followed by initialization of FTH, TTH, NAVECT(IX), Q, and I\_count. It then enters a loop checking CRED. If CRED is 1, MCVect(IX) is set to 0. If CRED is 0, MCVect(IX) is set to MCR (computed by an implementation-dependent function). Both paths lead to a ROLLBACK decision. If ROLLBACK is 1, it initializes I, QT, and Y, then enters a loop checking QT:Y. If QT:Y is less than Y, it updates MCVect(I), QT, and I. If QT:Y is greater than or equal to Y, it proceeds to a decision Q: TTH + FTH. If Q: TTH + FTH is greater than 0, failure := true. If Q: TTH + FTH is less than or equal to 0, it updates IX, ROLLBACK, CRED, NA, and NF, then proceeds to connector 2. If ROLLBACK is 0, it proceeds directly to the Q: TTH + FTH decision.
+
+FIGURE II.1/Q.2144 (sheet 5 of 6)
+**Error monitor**
+
+
+
+```
+
+graph TD
+ 2((2)) --> P1[tot_penalty := tot_penalty + rexmit_flag]
+ P1 --> P2[rexmit_flag := 0]
+ P2 --> D1{l_count % N_blk = 0}
+ D1 -- No --> C1(( ))
+ D1 -- Yes --> P3["block_qos := tot_penalty/N_blk
+tot_penalty := 0
+tot_qos := (1 - α) tot_qos + α(block_qos)"]
+ P3 --> D2{tot_qos > thres}
+ D2 -- Yes --> P4[failure := true]
+ D2 -- No --> D3{PI_count < N_sup}
+ P4 --> C2(( ))
+ D3 -- Yes --> C3(( ))
+ D3 -- No --> D4{N_loss < PI_count - ct_stats}
+ D4 -- Yes --> P5[failure := true]
+ D4 -- No --> P6["PI_count := 0
+ct_stats := 0"]
+ P5 --> C4(( ))
+ P6 --> C5(( ))
+
+```
+
+T1172850-95/d08
+
+Flowchart for Error monitor starting at connector 2. It includes steps for penalty calculation, flag resetting, and several decision diamonds for l\_count, tot\_qos, PI\_count, and N\_loss. It ends with failure flags and connectors.
+
+FIGURE II.1/Q.2144 (sheet 6 of 6)
+**Error monitor**
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.24-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.24-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/Q/T-REC-Q.24-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/11f18bf0233d812ad2604f88f3385d60_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0e79a5165bc00f06f0b6f2a44abcfde56fcfe28
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/11f18bf0233d812ad2604f88f3385d60_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d50ef9f6d5e0170a36da301a011c7ad5da09546a9d4f9e374705a9b93afd914
+size 150920
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..699f7dd4ef4bf7b7c10a46f86c66a009797dcd96
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/1c953f32bd34345dfd68fddf8a3736d6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ada2c2e530aca4fef50aa8ada863b1c964eb99ebd118ae3a4ef92cbebe8ac57
+size 95291
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/235e996e83e7d5198cf9d909f5713cdd_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/235e996e83e7d5198cf9d909f5713cdd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..590e0b091a7894d71361b83c1936a32f1c401387
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/235e996e83e7d5198cf9d909f5713cdd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e15bbff57a8783dc4d0273dc0e16a0c751a07246bbd5bd96c50355d36c05302c
+size 132172
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2d1e5e876890c183b8ced8c9004a339f6513cfe5
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46f09d6afa5e23567436760dc142eb7d2aea18accb84ccec9ff49c5b76a64108
+size 11234
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3ebfd619f541d4bc872ede4517be83f3f6abc5dc
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8501f24970f13ca1564f043ccd53ad7c3002e3c823bd85ecf88681e4686b56b9
+size 11956
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939eb6a57fac47a375526475ba6c31bf67e08b30
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359
+size 8245
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93f32d8485bfc89d29c9e9790d27b342499af362
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/301f4a188198a15b1415d54545b07e0d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7f595a281aa8ff3515b161a181fd6294d64d959a699996cedd33a9aa12f7884
+size 143372
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/356eb99ab9489bbd647223390a913903_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/356eb99ab9489bbd647223390a913903_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..47119f046fea3922900bcc71f62accf3eab0027a
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/356eb99ab9489bbd647223390a913903_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c3990eecbf2c8c5fd7fa210a2466b08d4f3475846e78ab47d8c8ec23c6f51041
+size 16457
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8fab0ca4b1c0bdd50ff19b88784a01f976b437ca
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5805ccf9161d086c2547307864ecd7f4c2e4c100f9c717ce5fdb5f5ea7d805cb
+size 85022
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eda51d4dbf4819b5537cce4a98c9741eeb2a421b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53c7b06e94514b14f8f843122e3b4112d8a5ab07a57017fae2c578ec06b82d5e
+size 91837
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..becbecafb757ed6fa475401dcdc8aaa99f313fd0
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8587fdd82d79aae93be6fe2cbbf0e01043a302172ae6672bf9388e86fe840cbf
+size 20808
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/426a0ab9454f31706038a0ac0bc37b9c_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/426a0ab9454f31706038a0ac0bc37b9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2305de46d9899a29631a133e11b453886747119c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/426a0ab9454f31706038a0ac0bc37b9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0de43c4987d732e8bff0cd1be142ab5843db54a63431baf9fc7a7c9796d9add7
+size 52642
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c6ab5819cc9f79fcd4c1ce2cf2c7d8631bfc645
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/487c58c79e44e6cf98b6368b6667b9c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fbaeb60e4e755d1d41bd6d95b4abfef70ad55282dd15c0de359c66ea9a76f251
+size 85004
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0b191650cf86940a265a6a060c2ed4ddcb2b897a
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a99b6b9abed973c0fc15b2cca2873f3cf6f1485118fc369d583a738483640ba4
+size 132871
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/4c63a0e17b54c7e61d512c276932114c_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/4c63a0e17b54c7e61d512c276932114c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1bee0926a6b5c6ab17f5e56375cc94a1e440ecce
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/4c63a0e17b54c7e61d512c276932114c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d242af4f7e85c5e5591270f775dd349018972c6706972a84355ef503f9aa833d
+size 59073
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/54a1e5d91d7f442361767b1f8c81c777_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/54a1e5d91d7f442361767b1f8c81c777_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3b9fd8faa269a1ff7a9d82741e60f557eafa4c2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/54a1e5d91d7f442361767b1f8c81c777_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:19be911e88b06f4da933c92b2bffd8db348dc24d2ad63ba56ebdf7bd969395bc
+size 20586
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/592f13acca3e6d5152dd4489f030d004_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/592f13acca3e6d5152dd4489f030d004_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fbd6af08d989db82f3917965aff5f323a33c93a7
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/592f13acca3e6d5152dd4489f030d004_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff920bd6909be74cdd21110102ecc3b00561db8033c6c9e2d53ea81c95233b79
+size 93700
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97046c44f668de230047165551762af252e1fbdb
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb4a9427f10e693e0d658e53b32a1dd151b7baf12618e3d6c4ca2050e07abfd8
+size 124712
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/5efe6377e22b9ab76a19a70da29976b9_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/5efe6377e22b9ab76a19a70da29976b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f2834e7d8d58c26c225fcbca2f007dfd3462515
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/5efe6377e22b9ab76a19a70da29976b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b8dc23a6ee359082b005b43d998bc046ac7961e9b084af6e050393a6246f4ff
+size 49026
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/69e5f1993021af230d08c08aac97d9df_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e0b1ff2fcfdb6747a8808cd3a13381c70b97b733
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/69e5f1993021af230d08c08aac97d9df_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a147ba9c04973b7cfd9e1132c30a5c863d9b6cd3605f02ad4c452e0fafed3a9
+size 16639
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d0466aa45b97ffb53e96d9d5c764e031757226a
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aad3d03d975dea6500eb81ca47621cc5920c6362c69ff781fc7e110d1600d508
+size 36577
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8e69fb86a92531bed5826eba5e63643f7be97578
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4901d1d1f3bc33b6fb3f97f8a5b5571145d19e44e8b1f90da97d6070060d44c4
+size 103396
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..30dd119f1fa4c21705e66f83da84d928b8b5e124
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a760538d7299397529144e135f3e44b53f06ca58e61d8648e9aa642fec8095fe
+size 57816
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/901343511e3efc3f994eaffe6fc393ca_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/901343511e3efc3f994eaffe6fc393ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..45ff52e97ee20430e23832550a36354321afbb53
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/901343511e3efc3f994eaffe6fc393ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3144e238d1ca3da8f1fe828dca7eadbb354eb6aef9c820784ee17c2c0090a95a
+size 24362
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/90183a52275501da5a0fd5c63d837009_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/90183a52275501da5a0fd5c63d837009_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3b3cc1cf247e0f5d13c8a73b12fed524d1925fca
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/90183a52275501da5a0fd5c63d837009_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab54009ca4b1f4861d25e9abf1f16b42d4a5a368823349ce2d42e161b178d824
+size 93934
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1ad342fdfb10a4c4c45b28af6af5a5d17556b5dc
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63c1ede7b029581f88d6d3bd25b238ff6a09692b1fa18fa15cb29e375a65cf18
+size 151942
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..070062518d14325fc8c995a00ab90776d18748eb
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d64d888ddf895ae972ba6c2130169278961829dd7885980efd48a4d07b5c2713
+size 150955
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/9f51a76cae7309a296cbc6997941eb3f_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/9f51a76cae7309a296cbc6997941eb3f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e54197d95c9fd3bab00ef45d7cb3e9c7e2db903f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/9f51a76cae7309a296cbc6997941eb3f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9c2da398e9c87f321f42b8a5d2729a333b69aaba6dc587115f530c70f58bcc4d
+size 156371
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/abeba89144744fac6a1571aa9f94889e_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/abeba89144744fac6a1571aa9f94889e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8a8b2542e721011cba96515477161d8c72f70e6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/abeba89144744fac6a1571aa9f94889e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:923b184d4f01099eea55561e1d3762e22a7042f0af65a08a0445a4f6431ccb64
+size 107921
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0b191650cf86940a265a6a060c2ed4ddcb2b897a
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/b3d488012fdceacab867cf24c5efef05_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a99b6b9abed973c0fc15b2cca2873f3cf6f1485118fc369d583a738483640ba4
+size 132871
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c4bbfaf82a577dd9f17917c31ead4a85371188b0
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d8a3dbe2d58fb41446306331b3d37026265b69877a620d23c8ecb7589871f9b
+size 92579
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..25fcacc49627a539c968dd44e9562e1385826d88
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c642ca8761815441e53aac67d5b3794cea3d7f3725bb190af52d456809dc7af6
+size 151595
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/c7111699f84f3e2bc4016b7876f10de6_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/c7111699f84f3e2bc4016b7876f10de6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca29fb3e066b09943df9a7c323dd1813c8b657a2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/c7111699f84f3e2bc4016b7876f10de6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a28078630073c1932c9f867a69c55fdebcfc9d1a470351461e63a6fcd445639b
+size 95573
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..02d135779a6e3775ba462a39c4a03ebeb006aeeb
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5486da1d343932ba9afb72febd3969d860c09c63b9aecce5f83795a6a10a162b
+size 83301
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8e69fb86a92531bed5826eba5e63643f7be97578
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4901d1d1f3bc33b6fb3f97f8a5b5571145d19e44e8b1f90da97d6070060d44c4
+size 103396
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..86a9ee91f3ae56124b680c33fd487caef5727554
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:734d399f827ac9c5ebf537f4277f2b8b6b472285f9aca2a9ecef03761277e839
+size 36192
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9dd24ab37c0f0636d8d617804f3556eb8423ac60
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:049f6a925bfcc8a56dbf42026780854b0563dbb842ce65970f0e8fedbcfd8ae3
+size 57956
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f6814e6070451d96ea3b32eb4988a6c3deff7d6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f963abbf203cef46f006712841488c2019e6402ead74e44ea94587700b25feaa
+size 137285
diff --git a/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/ff87509cc2b267501d910a2d9f9054ac_img.jpg b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/ff87509cc2b267501d910a2d9f9054ac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8502a1d5cf491d3ec3c7fed57e6da103a19d220b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2630.3-200310-I_PDF-E/ff87509cc2b267501d910a2d9f9054ac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b94a513ae98f9f12921517480d0135b3bdc065c4fb49e04764a66e1d4dae6885
+size 64783
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/01832e59ebad7ada5e790de6f90cc9b6_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/01832e59ebad7ada5e790de6f90cc9b6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8121b25af19a97566357fb3f749de2e9e0f38346
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/01832e59ebad7ada5e790de6f90cc9b6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d2857b175d0cf865b3f0b3e09e1cf17149c29c64d1f99f1ee01b302b393a2b6
+size 70268
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6980a46a2ea4396f51c136aebef9442bf80fb823
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9047d0984e75f0747d83a5b4d2a4ea6bd790603ababaec054fd3a6795b7f88cb
+size 137492
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/1033dc9fde75540d224c907681b1b7aa_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/1033dc9fde75540d224c907681b1b7aa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24dbe4ba4967581f36527f2f872ab47ccdbb2536
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/1033dc9fde75540d224c907681b1b7aa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66cf5f046e6021ff7ad8a87b9c43069d57fb8d0b161684fdbb4315cb4f064f75
+size 68970
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8a3e36eaa00a936be7efb7c88034957634be8805
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b2de7db83ecb41bbc23c1f618960ef8423146b5e91150b28b88365640764bc4
+size 13851
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..597350198bf183a462cef91611cc21dc746957d4
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30a6e102b1da0d13af03d660db963eef109c7d460e75a8e2594ffa6362039a83
+size 8212
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3becb1fbc7346c5a5e4cb00c61a26a63b093158c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ed67a468c98d038746e0eb7848540322734b965a4ded284a492cbb45501f5a86
+size 111208
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..94591840fe92f320a2c6df1cd238222005ece284
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/3c99312f83459559d9a301148555d7b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b56f383f8921dba83943c4917b915af5438f1147c1dd88ce6fe8123c6b84518
+size 62672
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc02d9d3b9e445a9ffdbbd6a862f3d210e05468f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/50214d232017279410e9c9db8eb75119_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8099c6bac662a2f406f24e94617a70c21498796048467049d8b57d72a6c436e8
+size 8321
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5a431eabd14f13f09d103f0201da232b991d7b36
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aaf3696883d75cb2fcdf0ca1ae98a9e87f44697f4e45fb1a24e271c8dbb4fc95
+size 74067
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a37b041384cd016c8aa2e649c8259bde2ed6305f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d79993c9d44c07d8afb88d3eb5b2feda340c11e63e8620237a99187d922456bd
+size 91951
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/61a7f401eb46fe99a71f27bc37493f04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..af7df4bad34ef12c40635b436940e208c514b1c7
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/61a7f401eb46fe99a71f27bc37493f04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9070a7da7d5c849ee0c4cb1abf47e2ca61c43715480be7b71d9b0c85ad8420bf
+size 58224
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61b5a589b48b07afb2b5a65ee3e40044802f6e6c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4123238a994e50e49fb731a17f17a2b087912929bf6861e753a831c2659926a5
+size 69857
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1ce63dba9b79c3946917f9bf5a2bcc698000868d
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca16e8304f1db7897fa008de192482b4b4b61fabef8083507ae32e6457a6de42
+size 95803
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8120fe3bba1b61e78612a20a312edef3c406b7a
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd115bfb8eaae532ee0e2f3013ae23373070e8793cde70f377d5d0e235dd80d2
+size 57596
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/90aa518591dfa9a78f61c31296f9b158_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/90aa518591dfa9a78f61c31296f9b158_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50f71b1f0ac12888a80ae0dcb0dc349ed29ba29b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/90aa518591dfa9a78f61c31296f9b158_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85b392bcd0369bdd03049a902027ad6145bd0a42c42a6993d51247a7ea8e0ad3
+size 14456
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dbef66676137b411dbb59ac9226b05bdc50ae4cc
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ae824811994a723bb3e44bebce56124aae49283fc53ee3da9569613efb8f892
+size 61795
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b59dd640433bb8e0d5eeacb215b4baf448b5f091
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:390603845bf0b1170c1c26f7356d83f2b3d8f7918ab7500cfc4d3664a687152f
+size 61469
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/cac61a60141d0335b4ae7a081f6b18d4_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/cac61a60141d0335b4ae7a081f6b18d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76dc0e33839cae3992f029800e7670bef82c45bf
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/cac61a60141d0335b4ae7a081f6b18d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5cb0c72f27491fd9f37e7f0f9ae811435d5eb9313a5a302a210a60a249b20bb
+size 60078
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9229f6e28c202c4ca0fc208c2094ba55f3c5ca9e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/cbb2d311b20781a595488445ded48d0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f1bb2a3f455055e700a67a07eb4389d9e4c49304b91c2602caa9cbcd2516bb68
+size 69240
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d67a5af388728915dd1ffdc9735febe45d5c8e2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8d3918bb48eed3824861cda3934bcef6f06cd005d3865ac2c94f7fc50f00ed7
+size 143807
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..94f016efd7f2a4557f3531215b9f80cd9589a733
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f879ab23a81bce27c6cb1553d990134dd5b5e5232f76854615029a61e17ccc2
+size 88910
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d52af5075523ac1bdf6419a76a145f047fb6ee5f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7020a28a2cca40dd07af547cf2aef02ce737cad50f45ffe7f0dcf34346fa3af
+size 126379
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7fb87282fa297b3712edf9587fbe019cc6e553b8
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7876e0f2faeeb07ce1c7d108657e3c37e7e9ed0513ac64d81466173552d4a6bd
+size 83877
diff --git a/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8d4a8070015066ef549fb8fdc60ca55db29539c8
--- /dev/null
+++ b/marked/Q/T-REC-Q.2722.1-199607-I_PDF-E/raw.md
@@ -0,0 +1,2334 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.2722.1**
+
+(07/96)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Broadband ISDN – B-ISDN application protocols for the
+network signalling
+
+---
+
+**B-ISDN User Part – Network Node Interface
+specification for point-to-multipoint
+call/connection control**
+
+ITU-T Recommendation Q.2722.1
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|--------------------------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| General aspects | Q.2000–Q.2099 |
+| ATM adaptation layer | Q.2100–Q.2199 |
+| Signalling network protocols | Q.2200–Q.2599 |
+| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600–Q.2699 |
+| B-ISDN application protocols of the network | Q.2700–Q.2899 |
+| B-ISDN application protocols for access signalling | Q.2900–Q.2999 |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+# **ITU-T RECOMMENDATION Q.2722.1**
+
+# **B-ISDN USER PART – NETWORK NODE INTERFACE SPECIFICATION FOR POINT-TO-MULTIPOINT CALL/CONNECTION CONTROL**
+
+## **Summary**
+
+This Recommendation specifies the extensions to the Broadband ISDN User Part to support point-to-multipoint call control.
+
+## **Source**
+
+ITU-T Recommendation Q.2722.1 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 9th of July 1996.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1997
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+| | | Page |
+|-------|-----------------------------------------------------------------------------------------------------------------------------------------|------|
+| 1 | Overview..... | 1 |
+| 1.1 | Scope..... | 1 |
+| 1.2 | Normative references..... | 1 |
+| 1.3 | Definitions and abbreviations ..... | 2 |
+| 1.3.1 | Definitions ..... | 2 |
+| 1.3.2 | Abbreviations..... | 2 |
+| 1.4 | Capabilities supported by this Recommendation..... | 2 |
+| 2 | Call control, application process functions..... | 3 |
+| 2.1 | Introduction..... | 3 |
+| 2.1.1 | Primitive interface ..... | 3 |
+| 2.1.2 | Assignment procedure of VPCI/VCI and bandwidth for point-to-multipoint network connections ..... | 3 |
+| 2.2 | Successful call/connection set-up ..... | 3 |
+| 2.2.1 | Forward address signalling – en bloc ..... | 4 |
+| 2.2.2 | Forward address signalling – overlap operation ..... | 13 |
+| 2.2.3 | Address_Complete request primitive ..... | 13 |
+| 2.2.4 | Progress (basic call)..... | 14 |
+| 2.2.5 | Answer primitive ..... | 15 |
+| 2.2.6 | Transit network selection (national option)..... | 15 |
+| 2.2.7 | Storage and release of information..... | 16 |
+| 2.2.8 | Simple segmentation (national option)..... | 16 |
+| 2.3 | Unsuccessful call/connection set-up..... | 16 |
+| 2.3.1 | Lack of resources at the incoming side..... | 16 |
+| 2.3.2 | Lack of resources at the outgoing side..... | 16 |
+| 2.3.3 | Actions at an exchange receiving an Incoming_Resources_Rejected primitive..... | 17 |
+| 2.3.4 | Actions at an exchange receiving a release message..... | 17 |
+| 2.3.5 | Address incomplete ..... | 18 |
+| 2.4 | Normal call/connection release..... | 18 |
+| 2.4.1 | General..... | 18 |
+| 2.4.2 | Drop of a leaf party requested by a root party ..... | 19 |
+| 2.4.3 | Drop of a leaf party requested by the party itself..... | 20 |
+| 2.4.4 | Drop of a leaf party initiated by the network..... | 20 |
+| 2.4.5 | En bloc release of call/connection requested by the root party..... | 20 |
+| 2.4.6 | A B-NT2 causing multiple leaf parties to be dropped, initiated at the T B reference point with a single RELEASE message..... | 21 |
+| 2.5 | Suspend, resume (network initiated)..... | 21 |
+
+| | Page | |
+|-------|-------------------------------------------------------------------------------------------------------------------------|----|
+| 2.6 | Propagation delay determination ..... | 21 |
+| 2.7 | Error indication primitive ..... | 22 |
+| 2.8 | Interaction ..... | 24 |
+| 2.8.1 | Interaction of point-to-multipoint features and Capability Set 1
supplementary services..... | 24 |
+| 2.8.2 | Interaction with a leaf party that does not support multipoint procedures .... | 25 |
+| 2.8.3 | Interaction with a leaf party that is not a broadband user..... | 25 |
+| 2.8.4 | Interaction of a CS-2.1 node with a CS-1 node..... | 25 |
+| 2.9 | Primitive contents ..... | 26 |
+| 3 | Maintenance control, application process functions..... | 29 |
+| 3.1 | Reset..... | 30 |
+| 3.1.1 | Actions at reset initiating exchange..... | 31 |
+| 3.1.2 | Actions at reset responding exchange..... | 32 |
+| 3.1.3 | Abnormal reset procedures..... | 32 |
+| 3.2 | Blocking and unblocking of virtual paths..... | 33 |
+| 4 | B-ISDN User Part messages and parameters..... | 33 |
+| 4.1 | Parameter name codes..... | 33 |
+| 4.2 | Parameter format and coding..... | 33 |
+| 4.2.1 | Destination connection link identifier ..... | 33 |
+| 4.2.2 | Origination connection link identifier ..... | 34 |
+| 4.3 | Leaf party type ..... | 34 |
+| 5 | Interworking of DSS 2 and B-ISUP for point-to-multipoint call/connections ..... | 34 |
+| 5.1 | General..... | 34 |
+| 5.1.1 | Architectural overview ..... | 35 |
+| 5.2 | Originating exchange ..... | 38 |
+| 5.2.1 | Sending of IAM ..... | 38 |
+| 5.2.2 | Receipt of ACM..... | 40 |
+| 5.2.3 | Receipt of CPG..... | 41 |
+| 5.2.4 | Receipt of ANM ..... | 41 |
+| 5.2.5 | Receipt of REL ..... | 42 |
+| 5.2.6 | Sending of REL ..... | 43 |
+| 5.3 | Destination exchange..... | 43 |
+| 5.3.1 | Interworking with DSS 2 access supporting coincident S B /T B reference
point procedures ..... | 43 |
+| 5.3.2 | Interworking with DSS 2 access supporting T B reference point procedures. | 45 |
+| 5.4 | Typical scenarios..... | 50 |
+
+###### **Page**
+
+Annex A – Message sequence flows..... 54
+
+Appendix I – Instruction indicator setting..... 59
+
+
+
+## Recommendation Q.2722.1
+
+# **B-ISDN USER PART – NETWORK NODE INTERFACE SPECIFICATION FOR POINT-TO-MULTIPOINT CALL/CONNECTION CONTROL**
+
+(Geneva, 1996)
+
+# **1 Overview**
+
+## **1.1 Scope**
+
+This Recommendation describes the basic B-ISDN User Part signalling procedures for the set-up and clear-down of national and international B-ISDN CS-2.1 point-to-multipoint network connections.
+
+The action to be taken at six exchange types are described:
+
+- originating exchange;
+- intermediate national exchange;
+- outgoing international exchange;
+- intermediate international exchange;
+- incoming international exchange;
+- destination exchange.
+
+Actions common for all exchange types are described only once. Different, or additional actions required for specific types are described in separate subclauses applicable to this type of exchange.
+
+This Recommendation is based on the basic B-ISDN User Part signalling procedures specified in Recommendation Q.2764.
+
+This Recommendation specifies the procedures for establishing, maintaining, and clearing of network point-to-multipoint connections at the B-ISDN network-node interface.
+
+To support new capabilities in B-ISUP beyond Capability Set 2, additional messages, parameters and/or modification of existing parameters will be used.
+
+This Recommendation specifies the following interactions:
+
+- interactions of point-to-multipoint features and Capability Set 1 supplementary services;
+- interaction with a leaf party that does not support multipoint procedures;
+- interaction with a leaf party that is not a broadband user;
+- interaction of a CS-2.1 to CS-1 node and CS-1 to CS-2.1 case.
+
+## **1.2 Normative references**
+
+The following ITU-T Recommendations, and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- ITU-T Recommendation I.610 (1995), *B-ISDN operation and maintenance principles and functions*.
+
+- ITU-T Recommendation Q.2650 (1995), *Interworking between Signalling System No. 7 Broadband ISDN User Part (B-ISUP) and Digital Subscriber Signalling System No. 2 (DSS 2)*.
+- ITU-T Recommendation Q.2721.1 (1996), *B-ISDN User Part – Overview of the B-ISDN network node interface signalling Capability Set 2, step 1*.
+- ITU-T Recommendation Q.2763 (1995), *Signalling System No. 7 B-ISDN User Part (B-ISUP) – Formats and codes*.
+- ITU-T Recommendation Q.2764 (1995), *Signalling System No. 7 B-ISDN User Part (B-ISUP) – Basic call procedures*.
+- ITU-T Recommendation Q.2931 (1995), *Digital Subscriber Signalling System No. 2 – User-Network Interface (UNI) layer 3 specification for basic call/connection control*.
+- ITU-T Recommendation Q.2971 (1995), *Digital Subscriber Signalling System No. 2 – User-network interface layer 3 specification for point-to-multipoint call/connection control*.
+
+## 1.3 Definitions and abbreviations
+
+This Recommendation defines the following terms.
+
+#### 1.3.1 Definitions
+
+**1.3.1.1 root:** The source of the point-to-multipoint connection.
+
+**1.3.1.2 leaf:** One of the destinations of the point-to-multipoint connection.
+
+#### 1.3.2 Abbreviations
+
+This Recommendation uses the following abbreviations.
+
+| | |
+|--------|-----------------------------------------------|
+| ATM | Asynchronous Transfer Mode |
+| B-ISDN | Broadband Integrated Services Digital Network |
+| CLI | Connection Link Identifier |
+
+## 1.4 Capabilities supported by this Recommendation
+
+The following capabilities shall be supported by this Recommendation:
+
+- Establishment of a call/connection containing one point-to-multipoint network connection requested by the root party of the network connection.
+- Addition of one new party, requested by the root party of the network connection.
+- Drop of a leaf party from an existing call/connection, requested by the root party.
+- Drop of a leaf party from an existing call/connection, requested by the party itself.
+- Release of the call/connection, requested by the root party.
+
+The capabilities above shall not be combined with narrow-band emulation services.
+
+Only unidirectional (forward), single connection point-to-multipoint call/connections are supported.
+
+Only *en bloc* address signalling is applicable for point-to-multipoint call/connections.
+
+# 2 Call control, application process functions
+
+## 2.1 Introduction
+
+This Recommendation describes the protocol architecture model that is used as a basis for the description.
+
+#### 2.1.1 Primitive interface
+
+The point-to-multipoint call control functions in the application process use the services provided by the SACF primitive interface. These are listed in Table 2-1.
+
+The primitives on this interface, in many cases, correspond with B-ISUP messages, this is also indicated in Table 2-1.
+
+**Table 2-1/Q.2722.1 – Call control primitives between AP and SACF**
+
+| Primitive name | Types | Corresponding B-ISUP message(s) |
+|-----------------------------|----------------------------------------------|---------------------------------|
+| Set_Up | Request/Indication | Initial Address |
+| Address_Complete | Request/Indication | Address Complete |
+| Incoming_Resources_Accepted | Request/Indication | IAM Acknowledge |
+| Incoming_Resources_Rejected | Request/Indication | IAM Reject |
+| Release | Request/Indication/Response/
Confirmation | Release, Release Complete |
+| Answer | Request/Indication | Answer |
+| Progress | Request/Indication | Call Progress |
+| Segment (National use) | Request/Indication | Segmentation |
+| Error | Indication | - |
+
+Tables 2-2 to 2-10 (see 2.9) list the mandatory and optional contents for these primitives for the set-up and release of basic call/connections.
+
+#### 2.1.2 Assignment procedure of VPCI/VCI and bandwidth for point-to-multipoint network connections
+
+See 2.1.2/Q.2764.
+
+##### 2.1.2.1 Management of VPCI/VCI value and bandwidth of each VPC
+
+See 2.1.2.1/Q.2764.
+
+#### 2.1.2.2 Assignment procedure of VPCI/VCI and bandwidth
+
+See 2.1.2.2/Q.2764.
+
+#### 2.1.2.3 Abnormal conditions
+
+See 2.1.2.3/Q.2764.
+
+### 2.2 Successful call/connection set-up
+
+This clause describes the successful procedures for point-to-multipoint calls where user plane information is multicast unidirectional from one root party to a set of leaf parties. These
+
+procedures are activated on receipt of a call request from the B-ISDN access indicating "point-to-multipoint" in the user plane configuration field of the broadband bearer capability parameter.
+
+#### 2.2.1 Forward address signalling – *en bloc*
+
+Subclause 2.2.1.1 specifies the signalling procedures for the set-up of the first leaf party of the point-to-multipoint call initiated by the root party. Subclause 2.2.1.2 specifies the signalling procedures for the addition of one new leaf party and for the attachment of the party to the point-to-multipoint (type 2) network connection. This can only be requested by the root party.
+
+##### 2.2.1.1 Forward address signalling – *en bloc* – Establishment of a call/connection
+
+##### 2.2.1.1.1 Actions required at the originating exchange
+
+###### a) *Virtual channel selection – Assigning exchange*
+
+When the originating exchange has received the complete information from the root party of the point-to-multipoint connection and has determined that the call/connection is to be routed to another exchange, route and virtual channel selection shall take place.
+
+Appropriate routing information is either stored at the originating exchange or at a remote database.
+
+The selection of the route shall depend on the called party number, broadband bearer capability, ATM cell rate, and the outcome of the assignment procedure, see 2.1.2.2 a)/Q.2764. Additionally, if the maximum end-to-end transit delay parameter is present, this is used together with the propagation delay counter. The selection process may be performed at the exchange, or with the assistance of the remote database. The exchange shall create:
+
+- an instance of the outgoing connection link object;
+- an instance of the B-ISUP AE and issue the Set\_Up request primitive to it.
+
+The origination connection link identifier parameter, set to identify the outgoing connection link object instance, shall be included in the Set\_Up request primitive.
+
+The information used to determine the routing of the call/connection by the originating exchange shall be included in the Set\_Up request primitive to enable the correct routing at intermediate exchanges. The Set\_Up request primitive implicitly confirms that performance parameter objectives have been met. It indicates the reservation of ATM connection elements.
+
+###### b) *Virtual channel selection – Non-assigning exchange*
+
+As for the assigning exchange except that the assignment procedure is according to 2.1.2.2 b)/Q.2764.
+
+###### c) *Address information sending sequence*
+
+The sending sequence of address information on international call/connections shall be the country code followed by the national (significant) number. On national connections, the address information may be the subscriber number or the national (significant) number as required by the Administration concerned.
+
+The end of pulsing (ST) signal shall always be sent by the outgoing exchange.
+
+###### d) *Set\_Up request primitive – issued by the assigning exchange*
+
+The Set\_Up request primitive shall contain all the information required to route the call/connection to the destination exchange, and to connect the call/connection to the leaf party.
+
+The originating exchange shall include in the Set\_Up request primitive the mandatory parameters listed in Table 2-2, and the connection element identifier parameter.
+
+The Set\_Up request primitive can also transport parameters from the access transparently to the destination, these are AAL parameters, broadband bearer capability, broadband low layer information, broadband high layer information and progress indicator.
+
+The OAM traffic descriptor parameter shall not be present since OAM flows are not supported for point-to-multipoint connections (see Recommendation I.610).
+
+If the call request from the access contains a broadband bearer capability indicating "point-to-multipoint" in the user plane connection configuration field and contains an OAM traffic descriptor parameter, it shall be treated as an unexpected parameter and shall be discarded.
+
+If the call request from the access contains a broadband bearer capability indicating "point-to-multipoint" in the user plane connection configuration field and contains an ATM traffic descriptor information element containing any backward cell rate field which specifies a non-zero value, the call/connection shall be rejected with cause #73, "unsupported combination of traffic parameters".
+
+The endpoint reference information element received from the access shall be mapped into the leaf party type parameter. If the endpoint reference information element has the value 0, then the leaf party type parameter shall be set to "First endpoint of type 2 connection", else it shall be set to "Subsequent endpoint of type 2 connection".
+
+NOTE – The endpoint reference information element value can be different from 0, because the first leaf party can belong to the same B-NT2 as the root of the connection.
+
+Since a point-to-multipoint connection is established, the broadband bearer capability parameter shall indicate "point-to-multipoint" in the user plane connection configuration field. The ATM cell rate and broadband bearer capability parameters shall be stored at the requesting serving node or associated database so that identical copies of these parameters can be sent in the subsequent Initial Address messages for the addition of leaf parties.
+
+After issuing the Set\_Up request primitive, a response is awaited, i.e. the Incoming\_Resources\_Accepted indication primitive or Incoming\_Resources\_Rejected indication primitive.
+
+###### e) *Set\_Up request primitive – issued by the non-assigning exchange*
+
+With regard to the issuing of the Set\_Up request primitive by the non-assigning exchange, the same procedures as for the assigning exchange are applicable, with the exception that the connection element identifier shall not be included in the Set\_Up request primitive.
+
+###### f) *Completion of transmission path*
+
+See 2.2.1.1 f)/Q.2764.
+
+##### 2.2.1.1.2 Actions required at an intermediate national exchange
+
+###### 2.2.1.1.2.1 Incoming side of the exchange
+
+###### a) *Assigning exchange*
+
+After having received a Set\_Up indication primitive, an incoming connection link object instance shall be created. An assigning exchange shall perform the assignment procedure for VPCI/VCI and bandwidth as described in Section 2.1.2.2 b)/Q.2764. If this is successful the Incoming\_Resources\_Accepted request primitive shall be issued immediately. The Incoming\_Resources\_Accepted request primitive shall include the mandatory parameters listed in Table 2-4, including the origination connection link identifier and connection element identifier parameters.
+
+###### b) *Non-assigning exchange*
+
+After having received a Set\_Up Indication primitive an incoming connection link object instance shall be created. A non-assigning exchange shall issue the Incoming\_Resources\_Accepted request primitive immediately. The Incoming\_Resources\_Accepted request primitive shall include the mandatory parameters listed in Table 2-4, without the connection element identifier parameter but containing the assigned origination connection link identifier parameter.
+
+###### 2.2.1.1.2.2 Other actions at the exchange
+
+###### a) *Virtual channel selection*
+
+After issuing the Incoming\_Resources\_Accepted request primitive, an intermediate national exchange shall analyse the called party number and the other routing information (see 2.2.1.1.1) to determine the routing of the call/connection. If the intermediate national exchange can route the call/connection, it shall:
+
+- create an instance of the outgoing connection link object;
+- create an instance of the B-ISUP AE and issue a Set\_Up request primitive to it;
+- establish a logical association between the incoming and outgoing AEIs used for this call/connection establishment.
+
+The exchange shall follow the assignment procedure for VPCI/VCI and bandwidth as described in 2.1.2.2.
+
+###### b) *Parameters in the Set\_Up request primitive issued by the assigning exchange*
+
+Signalling information is passed on transparently, except when specified otherwise (i.e. propagation delay).
+
+The exchange shall include in the Set\_Up request primitive the mandatory parameters included in Table 2-2, containing the origination connection link identifier and the connection element identifier parameters.
+
+After issuing the Set\_Up request primitive, a response, i.e. the Incoming\_Resources\_Accepted indication primitive or Incoming\_Resources\_Rejected indication primitive is awaited.
+
+###### c) *Set\_Up request primitive – issued by the non-assigning exchange*
+
+With regard to the issuing of the Set\_Up request primitive by the non-assigning exchange, the same procedures as for the assigning exchange are applicable, with the exception that the connection element identifier shall not be included in the Set\_Up request primitive.
+
+- d) *Completion of transmission path*
+See 2.2.1.1.2.2 d)/Q.2764.
+
+###### **2.2.1.1.3 Actions required at an outgoing international exchange**
+
+###### **2.2.1.1.3.1 Incoming side of the exchange**
+
+See 2.2.1.1.2.1.
+
+###### **2.2.1.1.3.2 Other actions at the exchange**
+
+- a) *Virtual channel selection*
+See 2.2.1.1.2.2 a).
+- b) *Parameters in the Set\_Up request primitive – issued by the assigning exchange*
+See 2.2.1.1.2.2 b), with the following additions:
+The most significant digits in the called party number may be amended or omitted (country code is removed at the last exchange before the incoming international exchange).
+If a location number parameter is received, the nature of address indicator is checked. If the nature of address indicator is set to "international number" then the parameter is passed on unchanged, otherwise the number is modified to the international number format and the nature of address is set to "international number" before being passed.
+The outgoing international gateway exchange shall include the origination ISC point code parameter in the Set\_Up request primitive. This information is used for statistical purposes, e.g. accumulation of the number of incoming call/connections on an originating international switching centre basis.
+- c) *Parameters in the Set\_Up request primitive – issued by the non-assigning exchange*
+See 2.2.1.1.2.2 c) with the addition in item b) above.
+- d) *Completion of transmission path*
+See 2.2.1.1.2.2 d).
+
+##### **2.2.1.1.4 Actions required at an intermediate international exchange**
+
+###### **2.2.1.1.4.1 Incoming side of the exchange**
+
+See 2.2.1.1.2.1.
+
+###### **2.2.1.1.4.2 Other actions at the exchange**
+
+- a) *Virtual channel selection*
+See 2.2.1.1.2.2 a).
+- b) *Parameters in the Set\_Up request primitive – issued by the assigning exchange*
+See 2.2.1.1.2.2 b), with the following addition:
+The most significant digits in the called party number may be amended or omitted (country code is removed at the last exchange before the incoming international exchange).
+- c) *Parameters in the Set\_Up request primitive – issued by the non-assigning exchange*
+See 2.2.1.1.2.2 c), with the addition in item b) above.
+
+- d) *Completion of transmission path*
+See 2.2.1.1.2.2 d).
+
+##### **2.2.1.1.5 Actions required at an incoming international exchange**
+
+###### **2.2.1.1.5.1 Incoming side of the exchange**
+
+See 2.2.1.1.2.1.
+
+###### **2.2.1.1.5.2 Other actions at the exchange**
+
+- a) *Virtual channel selection*
+See 2.2.1.1.2.2 a).
+- b) *Parameters in the Set\_Up request primitive – issued by the assigning exchange*
+See 2.2.1.1.2.2 b) with the following additions:
+The incoming international gateway exchange shall delete the origination ISC point code parameter from the Set\_Up indication primitive and set up a call/connection to the national network. This information is used for statistical purposes, e.g. accumulation of the number of incoming call/connections on an originating international switching centre basis.
+- c) *Parameters in the Set\_Up request primitive – issued by the non-assigning exchange*
+See 2.2.1.1.2.2 c) with the addition in item b) above.
+- d) *Completion of transmission path*
+See 2.2.1.1.2.2 d).
+
+##### **2.2.1.1.6 Actions required at the destination exchange**
+
+After issuing the Incoming\_Resources\_Accepted request primitive (see 2.2.1.1.2.1), the destination exchange shall analyse the called party number to determine to which party the call/connection shall be connected. It shall also check the leaf party's access condition and perform various checks to verify whether the connection is allowed or not. These checks shall include correspondence of compatibility checks, e.g. checks associated with supplementary services.
+
+If the connection is allowed, the destination exchange shall proceed to offer the call/connection to the leaf party.
+
+If the Set\_Up indication primitive contains information from the access carried in the parameters mentioned in 2.2.1.1.1, it is transferred unaltered in the indication sent to the called user, as specified in clause 5.
+
+#### **2.2.1.2 Forward address signalling – *en bloc* – Addition of one new leaf party**
+
+##### **2.2.1.2.1 Actions required at the originating exchange**
+
+- a) *Virtual channel selection – Assigning exchange*
+Route and virtual channel selection shall take place when the originating exchange has received the complete information for the addition of a new leaf party to the existing point-to-multipoint network connection and has determined that the call/connection is to be routed to another exchange. Appropriate routing information is either stored at the originating exchange or at the remote database. The selection of the route shall depend on the called party number, broadband bearer capability, ATM cell rate, and the outcome of the assignment procedure, see 2.1.2.2 a)/Q.2764. The ATM cell rate and broadband bearer
+
+capability parameters shall be retrieved from the stored call information parameters, received when the first party of the point-to-multipoint connection was established. Additionally, if the maximum end-to-end transit delay parameter is present, this parameter is used together with the propagation delay counter.
+
+It shall also be determined whether or not the call/connection is to be routed to another exchange with already selected connection link establishments for that network connection, and if this other exchange is CS-1 (see 2.8.4).
+
+In case 1 where the network connection branches to another exchange without already having a connection link established for this point-to-multipoint connection and in case of interworking with CS-1 (see 2.8.4) the procedures defined in 2.2.1.1.1 a) shall apply.
+
+In case 2 where the network connection is routed to another exchange to which there already is a connection link established for this point-to-multipoint connection, the existing outgoing connection link object instance shall be used. An instance of the B-ISUP AE shall be created and the Set\_Up request primitive shall be issued to it. No VPCI/VCI and bandwidth assignment procedures shall take place. The destination connection link identifier parameter associated with the outgoing connection link object instance shall be included in the Set\_Up request primitive.
+
+In the case where the destination connection link identifier value associated with the outgoing connection link object instance is not yet known, the Incoming\_Resources\_Accepted indication primitive shall be awaited first. Subsequently, procedures used for case 2 shall apply.
+
+###### b) *Virtual channel selection – non-assigning exchange*
+
+As for the assigning exchange except that the assignment procedure, if required, is according to 2.1.2.2 b)/Q.2764.
+
+###### c) *Address information sending sequence*
+
+See 2.2.1.1.1 c).
+
+###### d) *Set\_Up request primitive – issued by the assigning exchange*
+
+In case 1 the Set\_Up request primitive shall contain the mandatory parameters of Table 2-2, the origination connection link identifier and the connection element identifier parameter.
+
+In case 2 the Set\_Up request primitive shall contain the mandatory parameters of Table 2-2, the destination connection link identifier and shall not contain the connection element identifier parameters.
+
+The Set\_Up request primitive shall include the stored values of broadband bearer capability and ATM cell rate parameters as used for the initial Set\_Up request primitive.
+
+The AAL parameter, the broadband low layer information parameter and the broadband high layer information parameters shall only be passed in the Set\_Up request primitive if provided by the access protocol from the calling user. This information shall not be retrieved from stored data.
+
+The Set\_Up request primitive shall include the leaf party type parameter set to "Subsequent endpoint of type 2 connection".
+
+For the treatment of parameters received from the access protocol related to supplementary services, see 2.8.1.
+
+After having issued the Set\_Up request primitive, a response is awaited, i.e. the Incoming\_Resources\_Accepted indication primitive or Incoming\_Resources\_Rejected indication primitive.
+
+###### e) *Set\_Up request primitive – issued by the non-assigning exchange*
+
+With regard to issuing the Set\_Up request primitive by the non-assigning exchange, the same procedures as for the assigning exchange are applicable, with the exception that the connection element identifier shall not be included in the Set\_Up request primitive.
+
+###### f) *Completion of transmission path*
+
+On receipt of the first answer indication primitive, the transmission path towards the related party shall be through-connected in the forward direction.
+
+In case 1 the receipt of further answer indication primitives shall through-connect the related party(ies) accordingly and a cell replication function shall be invoked.
+
+In case 2 no additional action is performed on receipt of further answer indication primitives.
+
+##### **2.2.1.2.2 Actions required at an intermediate national exchange**
+
+###### **2.2.1.2.2.1 Incoming side of the exchange**
+
+If the received Set\_Up indication primitive contains the destination connection link identifier parameter, the associated incoming connection link object instance already exists for the incoming point-to-multipoint connection.
+
+Where an incoming connection link object instance does not exist, the procedures shall continue as in 2.2.1.1.2.1.
+
+Where an incoming connection link object instance already exists (this implies an already existing virtual channel), the following procedures shall apply for both the assigning and non-assigning exchanges:
+
+After receiving a Set\_Up indication primitive, the Incoming\_Resources\_Accepted request primitive shall be issued immediately. The Incoming\_Resources\_Accepted request primitive shall include the mandatory parameters listed in Table 2-4 and shall not contain the connection element identifier parameter.
+
+###### **2.2.1.2.2.2 Other actions at the exchange**
+
+After having issued the Incoming\_Resources\_Accepted request primitive, an intermediate national exchange shall analyse the called party number and the other routing information (see 2.2.1.1.1) to determine the routing of the call/connection.
+
+Where the additional party/connection branches to another exchange not currently the far end for any of the existing outgoing connection links, the procedures shall continue as in 2.2.1.1.2.2 and in case of interworking with CS-1 (see 2.8.4).
+
+Where the additional party/connection is routed to an exchange that is already the far end of an existing outgoing connection link for this point-to-multipoint call/connection, the following procedures shall apply:
+
+- a) The exchange shall:
+ - create an instance of the B-ISUP AE and issue a Set\_Up request primitive to it;
+ - establish a logical association between the incoming and outgoing AEIs used for this call/connection establishment.
+
+The exchange shall not perform the assignment procedure for VPCI/VCI and bandwidth, the connection element identifier (VPCI/VCI) used for the new party shall correspond to the stored outgoing connection link. In case the destination connection link identifier is not yet known at the exchange, the Incoming\_Resources\_Accepted indication primitive, in response to the first Set\_Up request primitive that was associated with the outgoing connection link object instance, shall be awaited first.
+
+###### b) Set\_Up request primitive issued by the assigning exchange
+
+Signalling information is passed transparently, except when specified otherwise (i.e. propagation delay).
+
+The exchange shall include the destination connection link identifier parameter and shall not include the connection element identifier parameter.
+
+After having issued the Set\_Up request primitive, a response awaited, i.e. the Incoming\_Resources\_Accepted indication primitive or Incoming\_Resources\_Rejected indication primitive.
+
+###### c) Set\_Up request primitive issued by the non-assigning exchange
+
+With regard to issuing the Set\_Up request primitive by the non-assigning exchange, the same procedures as for the assigning exchange are applicable.
+
+###### d) Completion of transmission path
+
+For the case 1 completion of the transmission shall follow the procedures defined in 2.2.1.1.2.2 d), furthermore a cell replication function shall be invoked.
+
+##### 2.2.1.2.3 Actions required at an outgoing international exchange
+
+###### 2.2.1.2.3.1 Incoming side of the exchange
+
+See 2.2.1.2.2.1.
+
+###### 2.2.1.2.3.2 Other actions at the exchange
+
+###### a) *Virtual channel selection*
+
+See 2.2.1.2.2.2 a).
+
+###### b) *Parameters in the Set\_Up request primitive – issued by the assigning exchange*
+
+See 2.2.1.2.2.2 b), with the following additions:
+
+The most significant digits in the called party number may be amended or omitted (country code is removed at the last exchange before the incoming international exchange).
+
+If a location number parameter is received, the nature of address indicator is checked. If the nature of address indicator is set to "international number" then the parameter is passed unchanged; Otherwise the number is modified to the international number format and the nature of address is set to "international number" before being passed.
+
+The outgoing international gateway exchange shall include the origination ISC point code parameter in the Set\_Up request primitive. This information is used for statistical purposes, e.g. accumulation of the number of incoming call/connections on an originating international switching centre basis.
+
+###### c) *Parameters in the Set\_Up request primitive – issued by the non-assigning exchange*
+
+See 2.2.1.2.2.2 c) with the addition in item b) above.
+
+- d) *Completion of transmission path*
+See 2.2.1.2.2.2 d).
+
+##### **2.2.1.2.4 Actions required at an intermediate international exchange**
+
+###### **2.2.1.2.4.1 Incoming side of the exchange**
+
+See 2.2.1.2.2.1.
+
+###### **2.2.1.2.4.2 Other actions at the exchange**
+
+- a) *Virtual channel selection*
+See 2.2.1.2.2.2 a).
+- b) *Parameters in the Set\_Up request primitive – issued by the assigning exchange*
+See 2.2.1.2.2.2 b), with the following addition:
+The most significant digits in the called party number may be amended or omitted (country code is removed at the last exchange before the incoming international exchange).
+- c) *Parameters in the Set\_Up request primitive – issued by the non-assigning exchange*
+See 2.2.1.2.2.2 c), with the addition in item b) above.
+- d) *Completion of transmission path*
+See 2.2.1.2.2.2 d).
+
+##### **2.2.1.2.5 Actions required at an incoming international exchange**
+
+###### **2.2.1.2.5.1 Incoming side of the exchange**
+
+See 2.2.1.2.2.1.
+
+###### **2.2.1.2.5.2 Other actions at the exchange**
+
+- a) *Virtual channel selection*
+See 2.2.1.2.2.2 a).
+- b) *Parameters in the Set\_Up request primitive – issued by the assigning exchange*
+See 2.2.1.2.2.2 b) with the following additions:
+The incoming international gateway exchange shall delete the origination ISC point code parameter from the Set\_Up indication primitive and set up a call/connection to the national network. This information is used for statistical purposes, e.g. accumulation of the number of incoming call/connections on an originating international switching centre basis.
+- c) *Parameters in the Set\_Up request primitive – issued by the non-assigning exchange*
+See 2.2.1.2.2.2 c) with the addition in item b) above.
+- d) *Completion of transmission path*
+See 2.2.1.2.2.2 d).
+
+##### **2.2.1.2.6 Actions required at the destination exchange**
+
+See 2.2.1.1.6.
+
+#### **2.2.2 Forward address signalling – overlap operation**
+
+This procedure is not supported. Therefore any received subsequent address indication primitive shall be discarded by the incoming connection link object instance.
+
+#### **2.2.3 Address\_Complete request primitive**
+
+#### **2.2.3.1 Actions required at the destination exchange**
+
+An Address\_Complete request primitive shall be sent from the destination exchange as soon as it has been determined that the complete called party number has been received, and to convey indications on the called party's status. The called line status indicator will be set appropriately.
+
+- a) If an indication that the address is complete or no status indication has been received from the ISDN access prior to the destination exchange determining that the complete called party number has been received, the indicators in the Address\_Complete request primitive will be set as follows:
+ - called party's status: "No indication"
+In this case the indication that the destination user is being alerted is transferred in a progress primitive (see 2.2.4).
+- b) The destination exchange concludes from the receipt of an indication from the ISDN access that the complete called party number has been received. In this case the indicators in the Address\_Complete request primitive will be set as follows:
+ - called party's status: "alerting".
+
+The address complete request primitive can transport transparently information from the access to the origin in the progress indicator parameter. The Address\_Complete request primitive shall include the mandatory parameters listed in Table 2-3.
+
+If an answer indication is received immediately from the called ISDN access, the answer request primitive may be issued without having previously issued an Address\_Complete request primitive.
+
+#### **2.2.3.2 Actions required at an intermediate national exchange**
+
+Upon receipt of an Address\_Complete indication primitive, an intermediate national exchange will issue the corresponding Address\_Complete request primitive to the associated incoming AEI.
+
+If this is a national controlling exchange, the following is applicable in addition:
+
+- If an Address Complete indication primitive is received the await answer timer is started.
+- If the await answer timer expires, the new leaf party shall be dropped according to 2.4.1 and 2.4.4 using cause "No answer from user (user alerted)".
+
+#### **2.2.3.3 Actions required at an outgoing international exchange**
+
+See 2.2.3.2. Additional actions are:
+
+- On receipt of the Address\_Complete indication primitive the await answer timer is started.
+- If the await answer timer expires, the new leaf party shall be dropped according to 2.4.1 and 2.4.4 using cause "No answer from user (user alerted)".
+
+#### **2.2.3.4 Actions required at an intermediate international exchange**
+
+See 2.2.3.2.
+
+#### **2.2.3.5 Actions required at an incoming international exchange**
+
+See 2.2.3.2.
+
+#### **2.2.3.6 Actions required at the originating exchange**
+
+- a) On receipt of an Address\_Complete indication primitive with the called party's status indicator set to "alerting", an alerting indication is passed to the calling party.
+- b) On receipt of the Address\_Complete indication primitive the "Awaiting Answer" timer is started. If timer "Await Answer" expires, the new leaf party shall be dropped according to 2.4.1 and 2.4.4 using cause "No answer from user (user alerted)".
+- c) If the address complete indication primitive contains information from the access carried in the parameters mentioned in 2.2.3.1, it is transferred unaltered in the indication to the calling user.
+
+#### **2.2.3.7 Through connection and the awaiting answer indication at the destination exchange**
+
+The sending of the awaiting answer indication shall not be applicable.
+
+The through connection of the virtual connection at answer, at other exchange types, is covered in 2.2.5.
+
+#### **2.2.3.8 Access delivery indication**
+
+See 2.2.3.8/Q.2764.
+
+#### **2.2.4 Progress (basic call)**
+
+The progress request primitive is sent only after the Address\_Complete indication primitive. The progress request primitive is sent from an exchange in the backward direction to indicate that an event has occurred during call/connection set-up that should be relayed to the calling party.
+
+#### **2.2.4.1 Actions required at the destination exchange**
+
+The progress request primitive is sent from the destination exchange if the Address\_Complete request primitive has been sent and subsequently:
+
+- an indication is received that the leaf party is being alerted. The progress request primitive contains a called party's indicators parameter with the called party's status set to "alerting".
+
+NOTE – A progress indication cannot be received from the leaf party; therefore, the transport of this progress indication in the progress request primitive containing a progress indicator parameter shall not be supported.
+
+The progress request primitive shall include the mandatory parameters listed in Table 2-9.
+
+#### **2.2.4.2 Actions required at an intermediate exchange**
+
+On receipt of a progress indication primitive, an intermediate exchange will issue the corresponding progress request primitive.
+
+#### **2.2.4.3 Actions required at the originating exchange**
+
+On receipt of a progress indication primitive at the originating exchange, no state change occurs, and the appropriate indication is sent to the calling user.
+
+If the progress indication primitive contains information from the access carried in the parameters mentioned in 2.2.4.1, it is transferred unaltered in the indication to the calling user.
+
+#### **2.2.5 Answer primitive**
+
+#### **2.2.5.1 Actions required at the destination exchange**
+
+When the leaf party answers, the destination exchange shall:
+
+- allocate the requested quality of service;
+NOTE – A more detailed description has to be provided, for further study.
+- issue an answer request primitive. The answer request primitive shall include the mandatory parameters listed in Table 2-8.
+
+Through connection: see 2.2.3.7.
+
+The answer request primitive can be issued without having issued a previous Address\_Complete request, e.g. in the case of an automatic answering terminal.
+
+The answer request primitive can transport information from the access to the origin in the following parameters: AAL parameter and broadband low layer information parameter.
+
+#### **2.2.5.2 Actions required at an intermediate national exchange**
+
+Upon receipt of an answer indication primitive, the intermediate national exchange through connects the virtual connection in the forward direction if not already connected and issues the corresponding answer request primitive towards the preceding exchange.
+
+If this is a national controlling exchange, and the answer indication is received subsequent to an address complete indication, timer "Await Answer" is stopped.
+
+#### **2.2.5.3 Actions required at an outgoing international exchange**
+
+See 2.2.5.2. Additionally if the answer indication is received subsequent to an address complete indication, timer "Await Answer" is stopped.
+
+#### **2.2.5.4 Actions required at an intermediate or incoming international exchange**
+
+See 2.2.5.2.
+
+#### **2.2.5.5 Actions required at the originating exchange**
+
+When the originating exchange receives an answer indication primitive indicating the required leaf party establishment has been completed, the "Awaiting Answer" timer is stopped, (if the answer indication is received subsequent to an address complete indication). The virtual connection is connected through in the forward direction, if not already connected, and a connect indication is sent to the calling subscriber.
+
+If the answer indication primitive contains information from the access carried in the parameters mentioned in 2.2.5.1, it is transferred unaltered in the indication to the calling user.
+
+#### **2.2.6 Transit network selection (national option)**
+
+If transit network selection information is included in the set-up or add party information from the calling party or is provided on a subscription basis, this information is carried in the transit network selection parameter. It is used for routing the call/connection, e.g. to a specific B-ISDN.
+
+#### 2.2.7 Storage and release of information
+
+Two cases for the storage of call/connection information shall be foreseen:
+
+- The requesting serving exchange of the connection shall store the broadband bearer capability and ATM cell rate parameters contained in the first Set\_Up primitive sent (originating exchange). This call information shall be stored so that identical copies of these parameters can be sent in the subsequent initial address messages.
+- Each exchange of the connection shall store the information contained in the Set\_Up primitive sent (originating exchange) or received (intermediate or destination exchange) during the call/connection set-up. The information to be stored includes all parameters in the Set\_Up primitive. The Set\_Up primitive information can be released from memory:
+ - a) in the originating or intermediate exchange, when the Address\_Complete or Answer indication primitive has been received;
+ - b) in the destination exchange, when the Address\_Complete or answer request primitive has been sent;
+ - c) in all exchanges, when the call/connection is released earlier and no automatic repeat attempt is to be attempted.
+
+#### 2.2.8 Simple segmentation (national option)
+
+See 2.2.9/Q.2764.
+
+### 2.3 Unsuccessful call/connection set-up
+
+#### 2.3.1 Lack of resources at the incoming side
+
+If at any time the call/connection establishment to the first leaf party or the establishment of a new connection link (leg) for the addition of a new leaf party cannot be completed due to lack of resources at the incoming side (e.g. SIDs, CLIDs, VPCI/VCI or bandwidth), the exchange shall issue an Incoming\_Resources\_Rejected request primitive towards the preceding exchange. The Incoming\_Resources\_Rejected primitive shall contain the mandatory parameters listed in Table 2-5. Cause value "resource unavailable – unspecified" is included, if no SIDs or CLIDs were available, cause value "No VPCI/VCI available" in case no VPCI/VCI is available, and cause value "user cell rate not available" in the case of lack of bandwidth. The incoming signalling association (AEI) and the incoming connection link object instance (provided it does not control any additional B-ISUP AEIs) are deleted.
+
+If at any time the addition of one new leaf party to an already existing connection link cannot be completed due to lack of resources at the incoming side (e.g. SIDs), the exchange shall issue an Incoming\_Resources\_Rejected request primitive towards the preceding exchange. The Incoming\_Resources\_Rejected primitive shall contain the mandatory parameters listed in Table 2-5. Cause value "resource unavailable – unspecified" is included, if no SIDs were available.
+
+#### 2.3.2 Lack of resources at the outgoing side
+
+If at any time the call/connection establishment to the first leaf party or the establishment of a new connection link (leg) cannot be completed due to lack of resources at the outgoing side (e.g. SIDs, CLIDs or bandwidth), or if the maximum end-to-end transit delay is exceeded, the exchange shall immediately start to drop the leaf party and shall issue a release request primitive towards the preceding exchange. The release primitive shall contain the mandatory parameters listed in Table 2-6. Cause value "resource unavailable – unspecified" is included, if no SIDs or CLIDs were available, or if the maximum end-to-end transit delay is exceeded, cause value "no VPCI/VCI
+
+available" in the case of lack of VPCI/VCI, and cause value "user cell rate not available" in the case of lack of bandwidth. Procedures continue as in 2.4.
+
+If at any time the addition of a new leaf party to an already existing connection link cannot be completed due to lack of resources at the outgoing side (e.g. SIDs) or if the maximum end-to-end transit delay is exceeded, the exchange will immediately start to drop the leaf party and issue a release request primitive towards the preceding exchange. The release primitive shall contain the mandatory parameters listed in Table 2-6. Cause value "resource unavailable – unspecified" is included, if no SIDs were available, or if the maximum end-to-end transit delay is exceeded. Procedures continue as in 2.4.
+
+#### **2.3.3 Actions at an exchange receiving an Incoming\_Resources\_Rejected primitive**
+
+If during the call/connection establishment to the first leaf party or the establishment of a new connection link (leg) for the addition of a new leaf party an exchange receives an Incoming\_Resources\_Rejected indication primitive it shall release the VPCI/VCI (if applicable) and the bandwidth, and shall terminate the outgoing signalling association, i.e. the associated outgoing connection link object instance and the corresponding AEI are deleted. When one or more Set\_Up request primitives corresponding to the parties to be added to the point-to-multipoint call/connection are waiting the reception of the peer connection link identifier value, one of these Set\_Up request primitives shall be issued containing the origination connection link identifier referring to this outgoing connection link object instance. The exchange may attempt to re-route the call/connection.
+
+If during the addition of a new leaf party to an already existing connection link an exchange receives an Incoming\_Resources\_Rejected indication primitive the signalling association is terminated, i.e. the associated AEI is deleted. The exchange shall provide the capability to re-route the call/connection.
+
+If all attempts to re-route the call/connection have failed the exchange shall:
+
+- a) at an intermediate exchange issue a release request primitive with the received cause value towards the preceding exchange. Procedures continue as in 2.4;
+- b) at an originating exchange send an indication to the calling user.
+
+#### **2.3.4 Actions at an exchange receiving a release message**
+
+If during the call/connection establishment of a point-to-multipoint network connection, an exchange receives a release indication primitive from the succeeding exchange after the Incoming\_Resources\_Accepted indication and before the Address\_Complete indication the exchange shall release the VPCI/VCI (if applicable) and the bandwidth, and shall issue a release response primitive. The outgoing signalling association is terminated, i.e. the associated outgoing connection link object instance and the corresponding AEI are deleted:
+
+- a) if it is the controlling exchange (i.e. the exchange controlling the call), the exchange may attempt to re-route the call/connection;
+- b) if it is not the controlling exchange or if all attempts to re-route the call/connection have failed:
+ - 1) an intermediate exchange will issue a release request primitive with the received cause value towards the preceding exchange. Procedures continue as in 2.4.3;
+ - 2) an originating exchange will send an indication to the calling user.
+
+If during the addition of one new leaf party and attachment to the point-to-multipoint network connection, an exchange receives a release indication primitive from the succeeding exchange after the Incoming\_Resources\_Accepted indication and before the Address\_Complete indication the exchange shall take the following actions:
+
+- if there are no other AEIs associated with the concerning outgoing connection link object instance the associated VPCI/VCI and the corresponding bandwidth shall be made available for new traffic;
+- issue a release response primitive;
+- the signalling association is terminated, i.e. the associated AEI is deleted;
+- when the last remaining AEI associated with the outgoing connection link object instance is deleted, the corresponding outgoing connection link object instance shall be deleted;
+- when the last remaining outgoing connection link object instance associated with a call/connection instance is deleted, the call/connection shall be deleted;
+ - a) if it is the controlling exchange (i.e. the exchange controlling the call), the exchange may attempt to re-route the call/connection;
+ - b) if it is not the controlling exchange or if all attempts to re-route the call/connection have failed:
+ - 1) an intermediate exchange will issue a release request primitive in order to drop the leaf party with the received cause value towards the preceding exchange. Procedures continue as in 2.4.3;
+ - 2) an originating exchange will send an indication to the calling user.
+
+#### 2.3.5 Address incomplete
+
+The determination that the proper number of digits has not been received can be made at once if the end of pulsing signal is received.
+
+If the end of pulsing has not been received, the release request primitive with cause "address incomplete" will be sent towards the preceding exchange. Procedures continue as in 2.4.
+
+### 2.4 Normal call/connection release
+
+#### 2.4.1 General
+
+The following release procedures are applicable:
+
+- Release of a call/connection requested by the root party: the *en bloc* release procedures as specified in 2.4.5 shall always apply.
+- Drop of a leaf party from an existing call/connection when requested by the root party.
+- Drop of a leaf party from an existing call/connection when requested by the party itself.
+- A B-NT2 causing multiple leaf parties to be dropped, initiated at the TB reference point with a single RELEASE message.
+
+The release procedure is a confirmed operation; whereby the release request/indication initiates release of the call/connection and/or drop of a party and the response/confirmation signifies completion of the release. A set of common procedures are used in the network irrespective of whether they are initiated by the root party, the leaf party or the network.
+
+The following actions will be performed by any exchange receiving a release indication primitive:
+
+- if there are no other AEIs associated with the concerned incoming/outgoing connection link object instance, the associated VPCI/VCI and the corresponding bandwidth shall be made available for new traffic;
+- the appropriate release response primitive is returned;
+- the signalling association is terminated, i.e. the associated AEI is deleted;
+- when the last remaining AEI associated with an incoming or outgoing connection link object instance is deleted, the corresponding incoming or outgoing connection link object instance shall be deleted;
+- when the last remaining incoming or outgoing connection link instances associated with a call/connection instance is deleted, the call/connection instance shall be deleted.
+
+An exchange that has initiated the release procedure by issuing a release request primitive shall perform the following actions on receipt of the release confirmation primitive:
+
+- if there are no other AEIs associated with the concerned incoming/outgoing connection link object instances, the associated VPCI/VCI and the corresponding bandwidth shall be made available for new traffic;
+- the signalling association is terminated, i.e. the associated AEI is deleted;
+- when the last remaining AEI associated with an incoming or outgoing connection link object instance is deleted, the corresponding incoming or outgoing connection link object instance shall be deleted;
+- when the last remaining incoming or outgoing connection link instances associated with a call/connection instance is deleted, the call/connection instance shall be deleted.
+
+The following subclause describe additional required actions.
+
+#### **2.4.2 Drop of a leaf party requested by a root party**
+
+##### **a) *Actions required at the originating exchange***
+
+On receipt of a request from the access protocol to drop a leaf party from the root party, the originating exchange immediately starts the release. A release request primitive is issued towards the succeeding exchange via the outgoing AEI corresponding to the remote leaf party to be dropped. The release request primitive shall not contain the destination connection link identifier parameter.
+
+In case of premature drop by the root party, the exchange shall immediately release the resources towards the root party, but shall delay the release of the connection towards the succeeding exchange until receipt of the Incoming\_Resources\_Accepted primitive.
+
+##### **b) *Actions at an intermediate exchange***
+
+On receipt of the release indication primitive, an intermediate exchange will issue a release request primitive towards the succeeding exchange via the associated outgoing AEI. The release towards the succeeding exchange shall not occur until after the receipt of the Incoming\_Resources\_Accepted primitive.
+
+##### **c) *Actions required at the destination exchange***
+
+If there is no remaining party at the interface, the exchange shall immediately release the resources towards the leaf party.
+
+##### **d) *Collision of release primitives***
+
+In the case when two points in the connection initiate the drop of the same leaf party, a release indication primitive may be received at an exchange from a succeeding or preceding
+
+exchange after the drop is initiated. In this case, the exchange shall return a release response primitive towards the exchange from which the concerned release request primitive was received. The release response primitive shall be issued, when the switch resources have been released.
+
+#### **2.4.3 Drop of a leaf party requested by the party itself**
+
+##### *a) Actions required at the leaf party serving (destination) exchange*
+
+On receipt of a request from the access protocol to drop a leaf party, the leaf party serving exchange immediately starts the release. A release request primitive is issued towards the preceding exchange via the associated incoming AEI, corresponding to the leaf party to be dropped.
+
+##### *b) Actions at an intermediate exchange*
+
+On receipt of the release indication primitive, an intermediate exchange will issue a release request primitive towards the preceding exchange via the associated incoming AEI.
+
+##### *c) Actions required at the originating exchange*
+
+The exchange shall notify the originating party that the leaf party has dropped.
+
+##### *d) Collision of release primitives*
+
+See 2.4.2 d).
+
+#### **2.4.4 Drop of a leaf party initiated by the network**
+
+The procedures in 2.4.2 and 2.4.3 apply, except that they can be initiated at any exchange.
+
+#### **2.4.5 En bloc release of call/connection requested by the root party**
+
+#### **2.4.5.1 Normal operation**
+
+##### *a) Actions required at the originating exchange*
+
+On receipt of a request from the access protocol to release the call/connection by the root party, the exchange shall immediately start the release. For each associated outgoing connection link object instance, a release request primitive is issued towards the succeeding exchange containing the relevant destination connection link identifier parameter to one of the controlled B-ISUP AEIs. The selection of the B-ISUP AEI is implementation dependant. The transmission path shall be disconnected.
+
+When the release confirmation primitive related to an outgoing connection link object is received:
+
+- all the associated B-ISUP AEIs shall be deleted;
+- the associated VPCI/VCI and the corresponding bandwidth shall be made available for new traffic, when the last remaining B-ISUP AEI associated with the outgoing connection link object instance has been deleted;
+- the outgoing connection link object instance shall be deleted.
+
+In case of premature release by the calling party, the exchange shall:
+
+- immediately release the resources towards the root party;
+- immediately release the connection links towards the succeeding exchanges for which one of the incoming resources accepted primitive has been received;
+- delay the release of the connection links towards the succeeding exchange on which no incoming resources accepted primitive has been received until receipt of one of the incoming resources accepted primitives.
+
+In general the Release request primitive shall only be issued via a B-ISUP AEI for which an Incoming Resources Accepted primitive has been received.
+
+##### b) *Actions at an intermediate exchange*
+
+###### i) Incoming side of the exchange
+
+On receipt of the release indication primitive from an incoming B-ISUP AEI containing a destination connection link identifier parameter, an intermediate exchange:
+
+- shall make the associated VPCI/VCI and corresponding bandwidth available for new traffic;
+- shall delete all the other B-ISUP AEIs associated with the incoming connection link object instance;
+- shall return a release response primitive to the preceding exchange, when all the other B-ISUP AEIs associated with the incoming connection link object instance have been deleted;
+- when a release response primitive has been returned, the last remaining B-ISUP AEI and the incoming connection link object instance shall be deleted.
+
+###### ii) Other action at the exchange
+
+See item a) above.
+
+##### c) *Actions required at the destination exchange*
+
+###### i) Incoming side of the exchange
+
+See item b) i) above.
+
+###### ii) Other actions at the exchange
+
+The destination exchange shall immediately release the resources towards the leaf parties.
+
+##### d) *Collision of release primitives*
+
+###### i) Outgoing side of an exchange
+
+After sending the release request primitive with the destination connection link identifier parameter, a release indication primitive may be received. In this case, the exchange shall return a release response primitive towards the B-ISUP AEI from which the concerned release indication primitive was received. The release response primitive shall be issued when the transmission path is disconnected.
+
+###### ii) Incoming side of an exchange
+
+#### **2.4.6 A B-NT2 causing multiple leaf parties to be dropped, initiated at the TB reference point with a single RELEASE message**
+
+When multiple leaf parties are dropped at the destination TB reference point with a single RELEASE message requested by the B-NT2, then individual REL messages shall be sent between exchanges and drop party messages to the originating interface.
+
+## **2.5 Suspend, resume (network initiated)**
+
+This capability shall not be supported.
+
+## **2.6 Propagation delay determination**
+
+The propagation delay determination procedures as defined in 2.6/Q.2764 shall be applied for each leaf party establishment.
+
+## 2.7 Error indication primitive
+
+The error indication primitive can be received as a result of various protocol errors detected by the ASEs.
+
+For the call/connection establishment of a point-to-multipoint network connection requested by the party who is the root of the network connection, the following errors and their corresponding actions are identified:
+
+- a) Timer "Await Address Complete" expiry, detected by CC ASE: if this error occurs the call/connection should be released, in both the forward and backward directions, using cause "Address Incomplete".
+- b) Unexpected message received while awaiting the IAM acknowledge message, detected by BCC ASE: this will initiate an automatic repeat attempt. The existing outgoing signalling association is terminated, i.e. the associated connection link object instance and corresponding AEI are deleted. (Reset initiated by the maintenance application process.)
+- c) Unexpected message received while awaiting the address complete message, detected by CC ASE: this shall initiate an automatic repeat attempt. The existing outgoing signalling association is terminated, i.e. the associated connection link object instance and corresponding AEI are deleted. (Reset initiated by the maintenance application process.)
+- d) Timer "Await IAM Acknowledge" expiry, detected by BCC ASE: if this error occurs the VPCI/VCI and the bandwidth shall be removed from service, and the signalling association is terminated, i.e. the associated connection link object instance and corresponding AEI are deleted. (Reset initiated by the maintenance application process.)
+- e) Unexpected release complete message received after the reception, or sending, of the IAM Acknowledge message, detected by BCC ASE: this will initiate the release of the call/connection, using cause value "protocol error – unspecified".
+
+For the addition of one new leaf party and attachment to the point-to-multipoint network connection, the following errors and their corresponding actions are identified:
+
+- a) Timer "Await Address Complete" expiry, detected by CC ASE: if this error occurs the leaf party shall be dropped by sending a release request primitive, in both the forward and backward directions, using cause "Address Incomplete".
+- b) Unexpected message received while awaiting the IAM Acknowledge message, detected by BCC ASE: this will initiate an automatic repeat attempt and the following actions are performed:
+ - the signalling association is terminated, i.e. the associated AEI is deleted;
+ - when the last remaining AEI associated with the outgoing connection link object instance is deleted, the corresponding outgoing connection link object instance shall be deleted;
+ - a reset is initiated by the maintenance application process.
+- c) Unexpected message received while awaiting the address complete message, detected by CC ASE: this shall initiate an automatic repeat attempt and the following actions shall be performed:
+ - if there are no other AEIs associated with the concerning outgoing connection link object instance, the associated VPCI/VCI and the corresponding bandwidth shall be made available for new traffic;
+ - issue a release request primitive;
+ - the signalling association is terminated, i.e. the associated AEI is deleted;
+
+- when the last remaining AEI associated with the outgoing connection link object instance is deleted, the corresponding outgoing connection link object instance shall be deleted;
+ - when the last remaining outgoing connection link object instance associated with a call/connection instance is deleted, the call/connection shall be deleted;
+ - a reset is initiated by the maintenance application process.
+- d) Timer "Await IAM Acknowledge" expiry, detected by BCC ASE: if this error occurs, the following actions shall be performed:
+- if there are no other AEIs associated with the concerning outgoing connection link object instance, the associated VPCI/VCI and the corresponding bandwidth shall be removed from service by the assigning exchange;
+ - the signalling association is terminated, i.e. the associated AEI is deleted;
+ - when the last remaining AEI associated with the outgoing connection link object instance is deleted, the corresponding outgoing connection link object instance shall be deleted;
+ - when the last remaining outgoing connection link object instance associated with a call/connection instance is deleted, the call/connection shall be deleted;
+ - a reset is initiated by the maintenance application process.
+- e) Unexpected release complete message received after the reception, or sending, of the IAM Acknowledge message, detected by BCC ASE: this shall initiate the drop of the called leaf, using cause value "protocol error – unspecified".
+
+For a drop of a leaf party requested by the root party, the following errors and their corresponding actions are identified:
+
+- Timer "Await release Complete" expiry, detected by BCC ASE: if this error occurs, the following actions are performed:
+ - if there are no other AEIs associated with the concerning outgoing connection link object instance, the associated VPCI/VCI and the corresponding bandwidth shall be removed from service by the assigning exchange;
+ - the signalling association is terminated, i.e. the associated AEI is deleted;
+ - when the last remaining AEI associated with the outgoing connection link object instance is deleted, the corresponding outgoing connection link object instance shall be deleted;
+ - when the last remaining outgoing connection link object instance associated with a call/connection instance is deleted, the call/connection shall be deleted;
+ - a reset is initiated by the maintenance application process.
+
+For a drop of a leaf party requested by the party itself, the following errors and their corresponding actions are identified:
+
+- Timer "Await release Complete" expiry, detected by BCC ASE: if this error occurs the following actions are performed:
+ - if there are no other AEIs associated with the concerning outgoing connection link object instance the associated VPCI/VCI and the corresponding bandwidth shall be removed from service by the assignment exchange;
+ - the signalling association is terminated, i.e. the associated AEI is deleted;
+
+- when the last remaining AEI associated with the outgoing connection link object instance is deleted, the corresponding outgoing connection link object instance shall be deleted;
+- when the last remaining outgoing connection link object instance associated with a call/connection instance is deleted, the call/connection shall be deleted;
+- a reset is initiated by the maintenance application process.
+
+For the release of call/connection by the root party, the following errors and their corresponding actions are identified:
+
+- Timer "Await release Complete" expiry, detected by BCC ASE: if this error occurs the VPCI/VCI and the bandwidth shall be removed from service, and the signalling associations shall be terminated, i.e. the associated connection link object instance and corresponding AEIs are deleted. (Reset initiated by the maintenance application process.)
+
+If an error indication primitive is received indicating any other error has occurred, it is discarded with no action.
+
+### **2.8 Interaction**
+
+#### **2.8.1 Interaction of point-to-multipoint features and Capability Set 1 supplementary services**
+
+##### **2.8.1.1 Direct-dialling-in supplementary service**
+
+The direct-dialling-in supplementary service shall have no impact on the NNI protocol, however the B-ISUP protocol shall carry the called party number in order to support the direct-dialling-in supplementary service.
+
+#### **2.8.1.2 Multiple subscriber number supplementary service**
+
+The multiple subscriber number supplementary service shall have no impact on the NNI protocol, however the B-ISUP protocol shall carry the called party number in order to support the multiple subscriber number supplementary service.
+
+#### **2.8.1.3 Calling line identification presentation and restriction supplementary services**
+
+The procedures specified provide for the inclusion of an calling line identity in the initial address message for each additional party to be added to the existing network connection, therefore no additional procedures are required. The evaluation, screening and restriction requirements of the calling line identity have to be performed independently for each additional party.
+
+#### **2.8.1.4 Connected line identification presentation and restriction supplementary services**
+
+The procedures specified provide for the inclusion of each additional party to be added by the use of the initial address message and the answer message, point-to-point procedures already provide for the inclusion of the connected line identity in the answer message, therefore no additional procedures are required.
+
+##### **2.8.1.5 Subaddressing supplementary service**
+
+The subaddressing supplementary service shall have no impact on the NNI protocol, however the B-ISUP protocol shall carry the called party subaddress in order to support the subaddressing supplementary service.
+
+##### **2.8.1.6 User-to-user supplementary service**
+
+The procedures specified provide for the inclusion of the user-to-user information in the initial address, segmentation, address complete or release messages and the user-to-user indicators in the address complete, segmentation or answer messages for each party to be added or dropped to/from the existing network connection, therefore no additional procedures are required.
+
+#### **2.8.2 Interaction with a leaf party that does not support multipoint procedures**
+
+It is not required that the leaf party of a point-to-multipoint network connection supports the procedures defined in Recommendation Q.2971, however connections shall be supported to leaf parties who support the procedures defined in clause 5/Q.2931.
+
+The NNI protocol shall support such users and shall apply the following procedures when the destination exchange receives an interworking primitive as a result of receiving at the UNI protocol a CALL PROCEEDING, ALERTING or CONNECT message as the first response to the SETUP message and it does not contain an endpoint reference information element:
+
+- The network shall deliver the broadband low layer information element in the answer primitive towards the root serving node provided the network supports the delivery of the broadband low layer information parameter.
+- The network shall deliver the AAL parameter in the answer primitive towards the root serving node.
+
+#### **2.8.3 Interaction with a leaf party that is not a broadband user**
+
+The network shall not support the connection establishment to a user which is not a broadband user. When an exchange has received the complete call information for the establishment of a point-to-multipoint network connection to a remote party or the addition of a remote party to an existing network connection and has determined that the call/connection has to be routed to a non-broadband ISDN user then this establishment shall be released in accordance with the normal call/connection release procedures specified in 2.4.
+
+#### **2.8.4 Interaction of a CS-2.1 node with a CS-1 node**
+
+If a new connection link (leg) is established to a CS-1 node, the CS-1 node shall establish the point-to-multipoint call/connection as if it is a point-to-point call/connection. Therefore the CS-1 exchange is instructed to discard the origination connection link identifier and to pass on the leaf party type.
+
+NOTE – If a broadband bearer capability parameter with the "point-to-multipoint" field in the user plane connection configuration field is received in the CS-1 exchange, the broadband bearer capability parameter is passed unchanged.
+
+Since the CS-1 exchange will not include an origination connection link identifier in the IAA, the application process functions of the CS-2.1 exchange will receive an Incoming\_Resources\_Accepted indication primitive without this parameter. Therefore the CS-2.1 exchange is in a position to know that the succeeding exchange is not capable to support point-to-multipoint functions, e.g. cell replication, creation of an connection link object instance. This knowledge is stored in the application process for the lifetime of the call/connection in order to use it for the handling of subsequent add party requests. The CS-2.1 shall not delete the connection link object instance because it has an associated AEI with it and is controlling the VPCI/VCI resource. For the continuation of the call set-up on the outgoing side of the CS-2.1 exchange, the procedures as specified for the normal CS-2.1 call set-up shall be applied.
+
+For subsequent requests to add new parties branching to the same CS-1 exchange, on the outgoing side of the CS-2.1 exchange the add party procedures for C-2.1 as specified in 2.2.1.2.1 a) case 1 for handling at the origination exchanges and 2.2.1.1.2.2 for intermediate exchanges shall be applied (in
+
+a case where no outgoing connection link object instance exists). For each add party establishment towards an CS-1 exchange a connection link object instance and associated AEI shall be created. Furthermore the replication function shall be invoked.
+
+The release procedures as specified in 2.4 apply also for the interaction with a CS-1 node. The *en bloc* release handled by the CS-2.1 exchange towards the CS-1 exchange is performed by sending individual release requests for each outgoing connection link object instance since no more than one AEI per connection link object instance is present.
+
+For a point-to-multipoint call/connection that is routed from a CS-2.1 exchange to a CS-1 exchange and on to a CS-2.1 exchange, the second CS-2.1 exchange shall receive a set-up request primitive containing a broadband bearer capability indicating point-to-multipoint, but no originating connection link identifier parameter. This shall be handled by the second CS-2.1 exchange as a point-to-point call.
+
+## 2.9 Primitive contents
+
+Tables 2-2 to 2-10 list the mandatory and optional contents for the SACF call control service primitives for the set-up and release of basic call/connections.
+
+Mandatory/Optional (M/O) indications are provided.
+
+For primitives generated by the application process, these tables indicate which parameters must be generated.
+
+For primitives received by the application process: if the primitive does not contain a parameter indicated as mandatory the primitive is discarded and maintenance application process is notified of the error. (Reset initiated by the maintenance application process.) Any other parameter which is not listed and which is not tagged as an unrecognized parameter by the UI ASE shall be discarded, unless explicitly specified otherwise.
+
+**Table 2-2/Q.2722.1 – Parameters for Set\_Up request/indication primitive**
+
+| Set_Up request/indication | |
+|---------------------------------------|---------------------------|
+| Parameter | Mandatory/Optional |
+| Message Compatibility Information | M |
+| AAL Parameters | O |
+| ATM Cell Rate | M |
+| Broadband Bearer Capability | M |
+| Broadband Low Layer Information | O |
+| Broadband High Layer Information | O |
+| Called Party Number | M |
+| Calling Party's Category | M |
+| Connection Element Identifier | O |
+| Location Number | O |
+| Maximum End-to-End Transit Delay | O |
+| National/international Call Indicator | O |
+| Origination ISC Point Code | O (Note 2) |
+| Progress Indicator | O |
+
+**Table 2-2/Q.2722.1 – Parameters for Set\_Up request/indication primitive (concluded)**
+
+| Set_Up request/indication | |
+|----------------------------------------|---------------------------|
+| Parameter | Mandatory/Optional |
+| Propagation Delay Counter | M |
+| Segmentation Indicator | O (national use) |
+| Transit Network Selection | O (national use) |
+| Origination Connection Link Identifier | (Note 3) |
+| Destination Connection Link Identifier | (Note 4) |
+| Leaf Party Type | M |
+| Exchange type (Note 1) | M |
+
+NOTE 1 – The exchange type parameter takes the appropriate value from the list in 1.1. It is passed to the AE so that the protocol can be varied depending on the role that the exchange is performing for this call/connection. Unlike the other parameters it does not relate to a protocol information element. This parameter is only present in the request primitive.
+
+NOTE 2 – This parameter is mandatory when the Set\_Up request is issued at an outgoing international exchange.
+
+NOTE 3 – This parameter is mandatory for the establishment of a new connection link.
+
+NOTE 4 – This parameter is mandatory for the addition of a new leaf to an existing connection.
+
+**Table 2-3/Q.2722.1 – Parameters for Address\_Complete request/indication primitive**
+
+| Address_Complete request/indication | |
+|--------------------------------------------|---------------------------|
+| Parameter | Mandatory/Optional |
+| Message Compatibility Information | M |
+| Access Delivery | O |
+| Called Party's Indicators | M |
+| Cause Indicators | O |
+| Charge Indicator | O |
+| Progress Indicator | O |
+| Segmentation Indicator | O (national use) |
+
+**Table 2-4/Q.2722.1 – Parameters for Incoming\_Resources\_Accepted request/indication primitive**
+
+| Incoming_Resources_Accepted request/indication | |
+|------------------------------------------------------------------------------------|---------------------------|
+| Parameter | Mandatory/Optional |
+| Message Compatibility Information | M |
+| Connection Element Identifier | O |
+| Origination Connection Link Identifier | (Note) |
+| NOTE – This parameter is mandatory for the establishment of a new connection link. | |
+
+**Table 2-5/Q.2722.1 – Parameters for Incoming\_Resources\_Rejected request/indication primitive**
+
+| Incoming_Resources_Rejected request/indication | |
+|-------------------------------------------------------|---------------------------|
+| Parameter | Mandatory/Optional |
+| Message Compatibility Information | M |
+| Automatic Congestion Level | O |
+| Cause Indicators | M |
+
+**Table 2-6/Q.2722.1 – Parameters for release request/indication primitive**
+
+| Release request/indication | |
+|-------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Parameter | Mandatory/Optional |
+| Message Compatibility Information | M |
+| Access Delivery | O |
+| Automatic Congestion Level | O |
+| Cause Indicators | M |
+| Progress Indicator | O |
+| Destination Connection Link Identifier | (Note) |
+| Segmentation Indicator | O (national use) |
+| NOTE – This parameter is mandatory for the en bloc release of call/connection requested by the root party. | |
+
+**Table 2-7/Q.2722.1 – Parameters for release response/confirmation primitive**
+
+| Release response/confirmation | |
+|--------------------------------------|---------------------------|
+| Parameter | Mandatory/Optional |
+| Message Compatibility Information | M |
+| Cause Indicator | O |
+
+**Table 2-8/Q.2722.1 – Parameters for answer request/indication primitive**
+
+| Answer request/indication | |
+|-----------------------------------|---------------------------|
+| Parameter | Mandatory/Optional |
+| Message Compatibility Information | M |
+| Access Delivery | O |
+| AAL Parameters | O |
+| Broadband Low Layer Information | O |
+| Call History Information | O |
+| Charge Indicator | O |
+| Progress Indicator | O |
+| Segmentation Indicator | O (national use) |
+
+**Table 2-9/Q.2722.1 – Parameters for progress request/indication primitive**
+
+| Progress request/indication | |
+|------------------------------------|---------------------------|
+| Parameter | Mandatory/Optional |
+| Message Compatibility Information | M |
+| Access Delivery | O |
+| Called Party's Indicators | O |
+| Cause Indicators | O |
+| Charge Indicator | O |
+| Progress Indicator | O |
+| Segmentation Indicator | O (national use) |
+
+**Table 2-10/Q.2722.1 – Parameters for segment request/indication primitive**
+
+| Segment request/indication | |
+|-----------------------------------|---------------------------|
+| Parameter | Mandatory/Optional |
+| Message Compatibility Information | M |
+| Broadband High Layer Information | O |
+| Broadband Low Layer Information | O |
+| Progress Indicator | O |
+
+## **3 Maintenance control, application process functions**
+
+The procedures as defined in clause 3/Q.2764 apply also to point-to-multipoint, except the reset and blocking functions for which the specification is provided in this clause.
+
+### 3.1 Reset
+
+The reset procedure is used to return signalling identifiers and connection elements (virtual channel links/path connections) to the idle condition. The procedure is invoked under abnormal conditions; when the current status of the signalling identifiers (SIDs) or the connection element identifiers (CEIs) are unknown or ambiguous. For example, a switching system that has suffered memory mutilation will not know the status of signalling identifiers (SIDs) and virtual channel connections, e.g. idle, busy incoming, busy outgoing, etc., the identifiers and virtual channel links/path connections (and any associated bandwidth) between the two adjacent nodes should therefore be reset to the idle condition. The resources are therefore made available for new traffic.
+
+In order to indicate what resource is to be reset, the Reset\_Resource request contains a Resource Identifier parameter. If the resource indicator is set to "remote SID" the resource value will indicate the local SID reference at the sending node (the remote reference at the receiving node). If the resource indicator is set to "local SID" then the resource value will indicate the remote SID reference at the sending node (the local reference at the receiving node). If the resource indicator is set to "CEI VPCI", or "CEI VPCI/VCI" the resource value will indicate the virtual channel link/path connection common to both the sending and receiving nodes.
+
+The reset procedure shall be initiated for:
+
+- a) signalling anomalies detected by the B-ISUP signalling system. The following anomalies are detected by the protocol procedures, reported to the exchange management functions, and thus initiate the reset procedure:
+ - 1) Unexpected message received while awaiting the IAM acknowledge message, (detected by BCC ASE). Action: Reset remote SID.
+ - 2) Unexpected message received while awaiting the address complete message, (detected by CC ASE). Action: Reset local SID.
+ - 3) Timer "Await Release Complete" expiry, (detected by BCC ASE) in case of a drop party operation if there are no other AEIs associated with the corresponding connection link object instance. Action: Reset VPCI/VCI.
+ - 4) Timer "Await Release Complete" expiry, (detected by BCC ASE) in case of an *en bloc* release operation. Action: Reset VPCI/VCI.
+ - 5) Unexpected message received relating to an unallocated SID, (detected by BCC ASE). Action: Reset remote SID.
+ - 6) Timer "Await IAM Acknowledge" expiry, (detected by BCC ASE) in case of the establishment of the call/connection to the first leaf party.
+Action:
+Assigning exchange: Reset VPCI/VCI and remove the VPCI/VCI and bandwidth from service.
+Non-assigning exchange: Reset remote SID.
+ - 7) Timer "Await IAM Acknowledge" expiry, (detected by BCC ASE) in case of an add party operation if there are no other AEIs associated with the corresponding connection link object instance.
+Action:
+Assigning exchange: Reset VPCI/VCI and remove the VPCI/VCI and bandwidth from service.
+Non-assigning exchange: Reset remote SID.
+
+- | | | |
+|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| 8) | Call control application process detects a missing mandatory parameter in a received primitive. | Action: Reset local SID. |
+| 9) | Timer "Await Release Complete" expiry, (detected by BCC ASE) in case of a drop party operation if there are other AEIs associated with the corresponding connection link object instance. | Action: Reset local SID. |
+| 10) | Timer "Await IAM Acknowledge" expiry, (detected by BCC ASE) in case of an add party operation if there are other AEIs associated with the corresponding connection link object instance. | Action: Reset remote SID. |
+- b) maintenance action due to memory mutilation, e.g. losing of the association information between a signalling ID and a connection element identifier; and
+ - c) maintenance action involving start-up and restart of an exchange and/or a signalling system: reset of each affected VPCI.
+
+#### 3.1.1 Actions at reset initiating exchange
+
+To initiate reset a Reset\_Resource request primitive is issued. The primitive shall contain the resource identifier.
+
+On issuing the Reset\_Resource request primitive the exchange shall (if applicable) stop sending ATM cells on the connection.
+
+On issuing the Reset\_Resource request primitive the exchange shall start timer "Repeat Reset".
+
+On receiving the Reset\_Resource confirmation primitive the exchange shall stop timer "Repeat Reset".
+
+On receiving the Reset\_Resource confirmation primitive, the affected exchange shall perform the following actions depending on the type of reset and the number of AEIs associated with the connection link object instance:
+
+- a) Reset SID and if other AEIs are associated with the connection link object instance the referenced SID shall be put in the "idle" state.
+- b) Reset SID and if no other AEI is associated with the connection link object instance, the referenced SID and the connection link identifier associated with the connection link object instance are put in the "idle" state. Additionally the related VCI is placed in the "idle" state and all associated bandwidth on the virtual path is put to the "available" state (i.e. send indication to resource control mechanism) at the assigning exchange.
+- c) Reset CEI: VPCI/VCI: The connection link identifier and all signalling identifiers associated with the connection link object instance for the referenced VPCI/VCI are put in the "idle" state. Additionally the related VCI is placed in the "idle" state and all associated bandwidth on the virtual path is put to the "available" state (i.e. send indication to resource control mechanism) at the assigning exchange.
+- d) Reset CEI: VPCI: All connection link identifiers and all signalling identifiers associated with the connection link object instances related to the referenced VPCI are put in the "idle" state. Additionally all related VCIs are placed in the "idle" state and all associated bandwidth on the virtual path is put to the "available" state (i.e. send indication to resource control mechanism) at the assigning exchange.
+
+The virtual path blocking conditions are affected by reset of CEI: VPCI as follows:
+
+- a) Any local blocking condition related to the reset VPCI is removed when the Reset\_Resource confirmation primitive is received.
+- b) Any remote blocking condition related to the reset VPCI is removed when the Reset\_Resource confirmation primitive is received, unless a Block\_Resource indication has been received, since the sending of the Reset\_Resource, relating to the concerned VPCI; in which case the remote blocking condition is (re-)instated.
+
+The blocking conditions are unaffected by other types of reset.
+
+The exchange shall notify the maintenance system of the outcome of the procedure.
+
+#### **3.1.2 Actions at reset responding exchange**
+
+On receiving a Reset\_Resource indication primitive, the receiving (unaffected) exchange shall:
+
+- a) If it is the incoming or outgoing exchange on a connection in any call/connection state, the exchange shall accept the message as a request to idle resources it controls. It responds by sending a Reset\_Resource response primitive after the indicated resources have been made available for new traffic. The specific actions depend on the type of reset and on the number of AEIs associated with the incoming or outgoing connection link object instance [see 3.1.1 items a) to d)].
+- b) If the received resource (SID, VPCI/VCI, VPCI) is not allocated (idle condition), accept the primitive as a release request and therefore respond by sending a Reset\_Resource response.
+- c) Interconnected virtual path/channel links and/or associated resources at the other side of the exchange shall be released according to 2.4.4 except in the case of call/connections and add party operations that are currently awaiting the Incoming\_Resources\_Accepted indication: in this case an automatic repeat attempt is applicable.
+- d) If the primitive is received after having sent a Reset\_Resource request primitive, respond by a Reset\_Resource response primitive. The associated identifiers and the bandwidth if applicable should be made available for service as specified in item a) above.
+- e) If the Resource indicator is set to "CEI: VPCI" and if the affected virtual path is in a locally blocked state, the Reset\_Resource indication shall be accepted as specified in item a) above. The affected virtual path is returned to the locally blocked state. A Block\_Resource request with a Resource indicator set to "CEI: VPCI" indicating the affected virtual path shall be sent. A Reset\_Resource response shall be issued following the Block\_Resource request primitive.
+- f) If the resource indicator is set to "CEI: VPCI" and if the affected virtual path is in a remotely blocked state, the remotely blocked state shall be removed.
+
+#### **3.1.3 Abnormal reset procedures**
+
+- a) If a Reset\_Resource confirmation is received which is not a correct response to a sent Reset\_Resource request, it is discarded.
+- b) If a Reset\_Resource indication is received requesting reset of a resource (e.g. connection element identifier) that is not controlled by the B-ISDN User Part, it is discarded.
+- c) If an error indication primitive is received indicating that timer "Await Reset Acknowledgement" has expired in the MC ASE, and if timer "Repeat Reset" has not yet expired for the first time, the Reset procedure is repeated as described in 3.1.1.
+
+If timer "Repeat Reset" expires the "Repeat Reset" timer shall be started again, and the reset procedure is repeated as described in 3.1.1. The maintenance system shall be informed on the first expiry of timer "Repeat Reset", and this procedure shall continue until the Reset\_Resource confirmation primitive is received, or until maintenance intervention occurs.
+
+### 3.2 Blocking and unblocking of virtual paths
+
+Blocking and unblocking procedures are as specified in 3.3/Q.2764.
+
+If an add party request for a blocked virtual path is received, this blocked path shall not be further selected and alternative routing may be done using another virtual path.
+
+## 4 B-ISDN User Part messages and parameters
+
+## 4.1 Parameter name codes
+
+The parameter name codes are given in Table 4-1 together with references to the subclause in which they are described.
+
+**Table 4-1/Q.2722.1 – Parameter codes**
+
+| Parameter name | Reference | Code |
+|----------------------------------------|-----------|----------|
+| Leaf Party Type | 4.3 | 01010110 |
+| Destination Connection Link Identifier | 4.2.1 | 01010100 |
+| Origination Connection Link Identifier | 4.2.2 | 01010101 |
+
+## 4.2 Parameter format and coding
+
+#### 4.2.1 Destination connection link identifier
+
+The format of the destination connection link identifier parameter field is shown as in Figure 4-1:
+
+
+
+| | | | | | | | | |
+|---|------------|---|---|---|---|---|---|---|
+| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 1 | Control ID | | | | | | | |
+| 2 | | | | | | | | |
+| 3 | | | | | | | | |
+| 4 | | | | | | | | |
+
+**Figure 4-1/Q.2722.1 – Destination connection link identifier parameter field**
+
+The following codes are used in the subfields of the destination connection link identifier parameter field:
+
+- *Control ID*
+A bit string representing the identification of the connection link association.
+
+#### 4.2.2 Origination connection link identifier
+
+The format of the origination connection link identifier parameter field is shown as in Figure 4-2:
+
+
+
+| | | | | | | | | |
+|---|------------|---|---|---|---|---|---|---|
+| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 1 | | | | | | | | |
+| 2 | Control ID | | | | | | | |
+| 3 | | | | | | | | |
+| 4 | | | | | | | | |
+
+Figure 4-2/Q.2722.1 – Origination connection link identifier parameter field
+
+The following codes are used in the subfields of the origination connection link identifier parameter field:
+
+- *Control ID*
+A bit string representing the identification of the connection link association.
+
+### 4.3 Leaf party type
+
+The format of the leaf party type identifier parameter field is shown as in Figure 4-3:
+
+
+
+| | | | | | | | | |
+|---|------------|---|---|---|---|---|---|---|
+| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+| 1 | Party type | | | | | | | |
+
+Figure 4-3/Q.2722.1 – Leaf party type
+
+The following codes are used in the subfields of the leaf party type identifier parameter field:
+
+- *Party type*
+00000000 First endpoint of type 2 connection
+00000001 Subsequent endpoint of type 2 connection.
+
+## 5 Interworking of DSS 2 and B-ISUP for point-to-multipoint call/connections
+
+### 5.1 General
+
+For the description of the interworking of DSS 2 and B-ISUP for point-to-multipoint calls/connections, the following principles are applied:
+
+- The specification is done by means of mapping tables for the messages and information elements/parameters.
+
+Only the information element/parameter mappings which are additional to Recommendation Q.2650 are described. For information elements/parameters which are specified by Recommendations Q.2971 and Q.2722.1 for use in conjunction with point-to-multipoint and which are already defined in Recommendations Q.2931 and Q.2763/Q.2764, the mapping of Recommendation Q.2650 is applicable.
+
+- Procedure specifications shall be limited to pure interworking. This means that the procedural semantic to trigger a specific mapping is not relevant in the interworking specification since this is specified in the protocol Recommendations.
+
+- Protocol issues which do have only significance within either DSS 2 or B-ISUP, i.e. which do not lead to a direct mapping are not described in this Recommendation since this is covered in the relevant protocol Recommendations.
+- The mapping is driven by message type and purely local conditions (call configuration states) in the exchange where the mapping is done (no direct relevance of states at the distant exchange, only via the B-ISUP).
+- In order to de-couple the pure interworking specification from the global scenario description and to cater for individual access characteristics mappings are described separately for originating and terminating sides.
+- End-to-end scenarios shall be provided as examples and for better understanding; however, they are not exhaustive and also naturally repeat procedural description which is already specified in the protocol Recommendations. In case of any differences the protocol Recommendations take precedence over the interworking scenarios.
+- Interworking for supplementary services is done along the same principles as for the basic call (i.e. describing only additions to Recommendation Q.2650, modification of procedures and interactions for supplementary services are specified in Recommendations Q.2971 and Q.2722.1).
+
+#### 5.1.1 Architectural overview
+
+The following figures illustrate how the various associations and object instances interact within a point-to-multipoint call.
+
+For example a point-to-multipoint call with 6-leaf parties is shown in Figure 5-1:
+
+- Leaf 2 and Leaf 3 are located within a private network.
+- Leaf 4 is located at a coincident SB/TB reference point type of access.
+- Leaf 1 is located at the same access as Leaf 2 and Leaf 3, however, the connection branch encountered blocking.
+- Leaf 5 and Leaf 6 are located at other destination exchanges as Leaves 1-4.
+
+Figure 5-1 also gives the user plane (ATM connection) configuration for this example.
+
+Figures 5-2 and 5-3 show the control plane configurations at the originating and the destination exchange.
+
+A B-ISUP connection link object instance has a one-to-one relation to a connection branch/VC connection link at ATM layer.
+
+
+
+The diagram illustrates a point-to-multipoint call configuration. At the top left, a 'Root' node is connected to an 'Originating Exchange' labeled $T_B$ or $S_B/T_B$ . This exchange is part of a 'Network' (indicated by a dotted box). From the Originating Exchange, a line extends to a junction point. From this junction, one path leads to 'Destination Exchange 1', which is connected to four leaves: 'Leaf 1', 'Leaf 2', 'Leaf 3', and 'Leaf 4' (labeled $S_B/T_B$ ). Another path from the junction leads to 'Destination Exchange 2', which is connected to 'Leaf 5' (labeled $T_B$ or $S_B/T_B$ ). A third path from the junction leads to 'Destination Exchange 3', which is connected to 'Leaf 6' (labeled $T_B$ or $S_B/T_B$ ). The text 'T1176200-95' is located at the bottom right of the diagram.
+
+Diagram of user plane configuration for a point-to-multipoint call. It shows a Root node connected to an Originating Exchange (TB or SB/TB). The Originating Exchange is part of a Network (dotted box) and connects to three Destination Exchanges. Destination Exchange 1 connects to Leaf 1, Leaf 2, Leaf 3, and Leaf 4 (SB/TB). Destination Exchange 2 connects to Leaf 5 (TB or SB/TB). Destination Exchange 3 connects to Leaf 6 (TB or SB/TB).
+
+**Figure 5-1/Q.2722.1 – Example for the user plane configuration (ATM connection) of a point-to-multipoint call**
+
+
+
+The diagram illustrates a point-to-multipoint call within the originating exchange (control plane). It shows the following components and associations:
+
+- Subscriber interface Root Party:** A bracket on the left side of the diagram, encompassing the 'DSS 2 Call instance' and its associated 'Party' objects.
+- DSS 2 Call instance:** A central box containing:
+ - A 'Call reference value' at the top.
+ - Seven 'Endpoint reference value' labels, each connected to a 'Party' box.
+- B-ISUP Connection link object instances:** Two boxes on the right, labeled 'B-ISUP Connection link object instance'.
+ - The top instance contains four 'AEI' (B-ISUP Application Entity Invocation) boxes. Each 'AEI' is connected to a 'Signalling identifier value' via a dashed line. These four 'Signalling identifier values' are grouped by a bracket labeled 'Network node interface 1'.
+ - The bottom instance contains two 'AEI' boxes. Each 'AEI' is connected to a 'Signalling identifier value' via a dashed line. These two 'Signalling identifier values' are grouped by a bracket labeled 'Network node interface 2'.
+- Associations:**
+ - External protocol associations:** Represented by dashed lines. The 'Call reference value' in the 'DSS 2 Call instance' is connected to the 'Connection link identifier' in each of the two 'B-ISUP Connection link object instances'.
+ - Exchange internal associations:** Represented by dotted lines. Each 'Party' box in the 'DSS 2 Call instance' is connected to an 'AEI' box in the top 'B-ISUP Connection link object instance'.
+
+**Legend:**
+
+- AEI B-ISUP Application Entity Invocation
+- External protocol associations
+- ..... Exchange internal associations
+
+T1176210-95
+
+Diagram of a point-to-multipoint call within the originating exchange (control plane).
+
+**Figure 5-2/Q.2722.1 – Representation of a point-to-multipoint call within the originating exchange (control plane)**
+
+
+
+The diagram shows two network node interfaces on the left, labeled 'Network node interface 1' and 'Network node interface 2'. Each interface is associated with a 'B-ISUP Connection link object instance' box. Inside these boxes are 'AEI' (Application Entity Invocation) boxes. 'Network node interface 1' has one AEI box, while 'Network node interface 2' has three AEI boxes. To the right of the B-ISUP boxes are 'DSS 2 Call instance' boxes. Each call instance contains 'Party' boxes. 'Network node interface 1' is connected to two call instances: the first has one Party box, and the second has two Party boxes. 'Network node interface 2' is connected to one call instance which has one Party box. Dotted lines represent 'Exchange internal associations' between the AEI boxes and the Party boxes. Dashed lines represent 'External protocol associations' leading from the Party boxes to labels on the far right: 'Call reference value', 'Endpoint reference value', and 'Subscriber interface (TB) Leaf Party 1-3' for the top call instances, and 'Call reference value', 'Endpoint reference value', and 'Subscriber interface (SB/TB) Leaf Party 4' for the bottom call instance. A legend at the bottom left defines the symbols: AEI for B-ISUP Application Entity Invocation, dashed lines for External protocol associations, and dotted lines for Exchange internal associations. A small code 'T1176220-95' is in the bottom right.
+
+Diagram illustrating a point-to-multipoint call within the destination exchange 1 (control plane).
+
+**Figure 5-3/Q.2722.1 – Representation of a point-to-multipoint call within the destination exchange 1 (control plane)**
+
+### 5.2 Originating exchange
+
+The tables always show the DSS 2 messages (originating user/network) at the left column and the B-ISUP messages (public network) at the right column.
+
+#### 5.2.1 Sending of IAM
+
+The mapping of parameters/information elements to support supplementary services is described in Recommendation Q.2650, subclauses 7.1.1 (DDI), 7.2.1 (MSN), 7.3.1 (CLIP/CLIR), 7.4.1 (COLP/COLR), 7.5.1 (SUB) and 7.6.1 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of ADD PARTY to IAM.
+
+##### 5.2.1.1 Receipt of SETUP
+
+| SETUP (Note 1) | IAM |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|
+| | Origination connection link identifier (Note 2) |
+| Broadband bearer capability:
user plane configuration = "point-to-multipoint" | Broadband bearer capability |
+| | Leaf party type (Note 3) |
+| Endpoint reference (Note 4) | |
+| NOTE 1 – In case the SETUP contains a N-BC information element the set-up request is rejected.
NOTE 2 – A new outgoing B-ISUP connection link object instance and a new outgoing B-ISUP AEI are created.
An exchange internal association has to be created between the DSS 2 call instance and the B-ISUP connection link object instance (Call reference value <-> Connection link identifier value).
NOTE 3 – If the endpoint reference value is zero then the leaf party type is set to "first endpoint of type 2 connection" or else it is set to "subsequent endpoint of type 2 connection".
NOTE 4 – An exchange internal association has to be created between the DSS 2 party/endpoint and the related outgoing B-ISUP Application Entity Invocation (AEI) [Endpoint reference value <-> Signalling identifier value (SID)].
| |
+
+##### 5.2.1.2 Receipt of ADD PARTY
+
+| ADD PARTY | IAM |
+|----------------------------------|------------------------------------------------------------------------------------------------------------------------|
+| | Either (Note 1) origination connection link identifier (Note 2); or
Destination connection link identifier (Note 3) |
+| | ATM cell rate (Note 4) |
+| | Broadband bearer capability (Note 4) |
+| AAL parameters | AAL parameters |
+| Broadband high layer information | Broadband high layer information |
+| Broadband low layer information | Broadband low layer information |
+| Called party number | Called party number |
+| Broadband sending complete | ST (carried in called party number) |
+| | Leaf party type (Note 5) |
+| Endpoint reference (Note 6) | |
+| End-to-end transit delay | Propagation delay counter and maximum end-to-end transit delay (Note 7) |
+
+NOTE 1 – The choice depends on the routing result (see 2.2.1.2). In both cases a new outgoing B-ISUP AEI is created.
+
+NOTE 2 – The originating connection link identifier is included if a new outgoing B-ISUP connection link object instance is created (i.e. a new virtual channel link is created for that party).
+
+An exchange internal association has to be created between the DSS 2 call instance and this B-ISUP connection link object instance (Call reference value <-> Connection link identifier value).
+
+Furthermore, the exchange has to invoke a call replication function in the user plane.
+
+NOTE 3 – The destination connection link identifier is included if an existing outgoing B-ISUP connection link object instance is used (i.e. an existing virtual channel link is shared with previous parties).
+
+NOTE 4 – Those parameters are retrieved from the stored call information (see 2.2.7).
+
+NOTE 5 – The leaf party type parameter is set to "subsequent endpoint of type 2 connection".
+
+NOTE 6 – An exchange internal association has to be created between the DSS 2 party/endpoint and the related outgoing B-ISUP AEI [Endpoint reference value <-> Signalling identifier value (SID)].
+
+NOTE 7 – The cumulative end-to-end transit delay subfield of the end-to-end transit delay information element is mapped to the propagation delay counter. The maximum end-to-end transit delay subfield is mapped to the maximum end-to-end transit delay parameter in the network. At the destination exchange, the propagation delay counter value is mapped back to the cumulative end-to-end transit delay subfield only if a maximum end-to-end transit delay parameter is present.
+
+#### 5.2.2 Receipt of ACM
+
+The mapping of parameters/information elements to support supplementary services is described in 7.6.2/Q.2650 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of ACM to PARTY ALERTING.
+
+##### 5.2.2.1 Sending of ALERTING
+
+This mapping applies if there is only one outgoing B-ISUP AEI associated with the call.
+
+| ALERTING | ACM |
+|-----------------------------------------------------------------------------------------------------------------------------|-----|
+| Endpoint reference (Note) | |
+| NOTE – The endpoint reference has to be set to the value which has been associated with the SID of the outgoing B-ISUP AEI. | |
+
+##### 5.2.2.2 Sending of PARTY ALERTING
+
+This mapping applies if there are more than one outgoing B-ISUP AEIs associated with the call.
+
+| PARTY ALERTING | ACM |
+|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| | Called party's indicators:
called party status = "alerting" |
+| Endpoint reference (Note) | |
+| NOTE – The endpoint reference has to be set to the value which has been associated with the SID of the outgoing B-ISUP AEI. | |
+
+#### 5.2.3 Receipt of CPG
+
+The mapping of parameters/information elements to support supplementary services is described in 7.6.2/Q.2650 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of CPG to PARTY ALERTING.
+
+##### 5.2.3.1 Sending of ALERTING
+
+This mapping applies if there is only one outgoing B-ISUP AEI associated with the call.
+
+| ALERTING | CPG |
+|-----------------------------------------------------------------------------------------------------------------------------|-----|
+| Endpoint reference (Note) | |
+| NOTE – The endpoint reference has to be set to the value which has been associated with the SID of the outgoing B-ISUP AEI. | |
+
+##### 5.2.3.2 Sending of PARTY ALERTING
+
+This mapping applies if there are more than one outgoing B-ISUP AEIs associated with the call.
+
+| PARTY ALERTING | CPG |
+|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|
+| | Called party's indicators:
called party status = "alerting" |
+| Endpoint reference (Note) | |
+| NOTE – The endpoint reference has to be set to the value which has been associated with the SID of the outgoing B-ISUP AEI. | |
+
+#### 5.2.4 Receipt of ANM
+
+The mapping of parameters/information elements to support supplementary services is described in 7.6.2/Q.2650 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of ANM to ADD PARTY ACKNOWLEDGE.
+
+##### 5.2.4.1 Sending of CONNECT
+
+This mapping applies if there is only one outgoing B-ISUP AEI associated with the call.
+
+| CONNECT | ANM |
+|-----------------------------------------------------------------------------------------------------------------------------|------------|
+| Endpoint reference (Note) | |
+| NOTE – The endpoint reference has to be set to the value which has been associated with the SID of the outgoing B-ISUP AEI. | |
+
+##### 5.2.4.2 Sending of ADD PARTY ACKNOWLEDGE
+
+This mapping applies if there are more than one outgoing B-ISUP AEIs associated with the call.
+
+| ADD PARTY ACKNOWLEDGE | ANM |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|
+| AAL parameters | AAL parameters |
+| Broadband low layer information | Broadband low layer information |
+| Endpoint reference (Note 1) | |
+| End-to-end transit delay | Call history information (Note 2) |
+| NOTE 1 – The endpoint reference has to be set to the value which has been associated with the SID of the outgoing B-ISUP AEI. | |
+| NOTE 2 – If applicable, the cumulative end-to-end transit delay from the called party is mapped to the call history information parameter at the destination exchange, and is mapped back to the cumulative end-to-end transit delay at the originating exchange. | |
+
+#### 5.2.5 Receipt of REL
+
+The mapping of parameters/information elements to support supplementary services is described in 7.6.2/Q.2650 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of REL to DROP PARTY and ADD PARTY REJECT.
+
+##### 5.2.5.1 Sending of RELEASE
+
+This mapping applies if there is only one outgoing B-ISUP AEI associated with the call.
+
+| RELEASE | REL |
+|----------------|------------------|
+| Cause | Cause indicators |
+
+##### 5.2.5.2 Sending of DROP PARTY
+
+This mapping applies if there are more than one outgoing B-ISUP AEIs associated with the call and the party concerned is in the Party Alerting Delivered or Active state (PN3, PN7).
+
+| DROP PARTY | REL |
+|-----------------------------------------------------------------------------------------------------------------------------|------------------|
+| Cause | Cause indicators |
+| Endpoint reference (Note) | |
+| NOTE – The endpoint reference has to be set to the value which has been associated with the SID of the outgoing B-ISUP AEI. | |
+
+##### 5.2.5.3 Sending of ADD PARTY REJECT
+
+This mapping applies if there are more than one outgoing B-ISUP AEIs associated with the call and the party concerned is in the add party received state (PN2).
+
+| ADD PARTY REJECT | REL |
+|-----------------------------------------------------------------------------------------------------------------------------|------------------|
+| Cause | Cause indicators |
+| Endpoint reference (Note) | |
+| NOTE – The endpoint reference has to be set to the value which has been associated with the SID of the outgoing B-ISUP AEI. | |
+
+#### 5.2.6 Sending of REL
+
+The mapping of parameters/information elements to support supplementary services is described in 7.6.2/Q.2650 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of DROP PARTY to REL.
+
+##### 5.2.6.1 Receipt of RELEASE
+
+| RELEASE | REL (Note) |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|
+| Cause | Cause indicators |
+| | Destination connection link identifier |
+| NOTE – The B-ISUP message is repeated for all outgoing connection link object instances which are associated with the call (see en bloc release procedure of Recommendation Q.2722.1). | |
+
+If the RELEASE message contains a User-user information element, the information is also copied together with each REL message.
+
+##### 5.2.6.2 Receipt of DROP PARTY
+
+| DROP PARTY | REL |
+|-----------------------------------------------------------------------------------------------------------------------------|------------------|
+| Cause | Cause indicators |
+| Endpoint reference (Note) | |
+| NOTE – The endpoint reference has to be set to the value which has been associated with the SID of the outgoing B-ISUP AEI. | |
+
+### 5.3 Destination exchange
+
+The tables always show the B-ISUP messages (public network) at the left column and the DSS 2 messages (destination user/network) at the right column.
+
+#### 5.3.1 Interworking with DSS 2 access supporting coincident SB/TB reference point procedures
+
+The mapping of parameters/information elements to support supplementary services is described in Recommendation Q.2650, subclauses 7.1.1 (DDI), 7.2.1 (MSN), 7.3.1 (CLIP/CLIR), 7.4.1 (COLP/COLR), 7.5.1 (SUB) and 7.6.1 (UUS1).
+
+##### 5.3.1.1 Receipt of IAM
+
+###### 5.3.1.1.1 Sending of SETUP
+
+| IAM | SETUP |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|
+| Either
Origination connection link identifier (Note 1); or
Destination connection link identifier (Note 2); or
(no identifier included) (Note 3) | |
+| Leaf party type | |
+| | Endpoint reference (Note 4) |
+
+NOTE 1 – In this case a new incoming B-ISUP connection link object instance, a new incoming B-ISUP AEI and at the access a new DSS 2 call instance is created. The following exchange internal associations have to be created:
+
+- Incoming B-ISUP connection link object instance <-> DSS 2 call instance (i.e. Connection link identifier value <-> Call reference value).
+- Incoming B-ISUP AEI <-> DSS 2 party/endpoint (i.e. Signalling identifier value <-> Endpoint reference value).
+
+NOTE 2 – If the destination connection link identifier is included this means that an incoming B-ISUP connection link object instance (and at least one associated DSS 2 call instance) already exists.
+
+Further processing is as follows:
+
+A new DSS 2 call instance is created and the following exchange internal associations have to be created:
+
+- Incoming B-ISUP connection link object instance <-> DSS 2 Call instance (i.e. Connection link identifier value <-> Call reference value).
+- Incoming B-ISUP AEI <-> DSS 2 party/endpoint (i.e. Signalling identifier value <-> Endpoint reference value).
+
+Furthermore, the exchange has to invoke a cell replication function in the user plane.
+
+NOTE 3 – If no connection link identifier is included the interworking proceeds as for Note 1. This may occur due to interworking with transit nodes in the network which do not support the Q.2722.1 procedures.
+
+NOTE 4 – The value of the endpoint reference has to be set to zero if the leaf party type is set to "First endpoint of type 2 connection" otherwise it is locally assigned.
+
+##### 5.3.1.2 Sending of ACM
+
+###### 5.3.1.2.1 Receipt of ALERTING
+
+The mapping as in 5.3.2.2.1 applies.
+
+The inclusion of the endpoint reference is optional in some cases (see Recommendation Q.2971).
+
+##### 5.3.1.3 Sending of CPG
+
+###### 5.3.1.3.1 Receipt of ALERTING
+
+The mapping as in 5.3.2.3.1 applies.
+
+The inclusion of the endpoint reference is optional in some cases (see Recommendation Q.2971).
+
+##### **5.3.1.4 Sending of ANM**
+
+###### **5.3.1.4.1 Receipt of CONNECT**
+
+The mapping as in 5.3.2.4.1 applies.
+
+The inclusion of the endpoint reference is optional in some cases (see Recommendation Q.2971).
+
+##### **5.3.1.5 Sending of REL**
+
+###### **5.3.1.5.1 Receipt of RELEASE**
+
+The mapping as in 5.3.2.5.1 applies.
+
+###### **5.3.1.5.2 Receipt of RELEASE COMPLETE**
+
+The mapping as in 5.3.2.5.2 applies.
+
+##### **5.3.1.6 Receipt of REL**
+
+###### **5.3.1.6.1 Sending of RELEASE**
+
+The mapping as in 5.3.2.5.2 applies.
+
+#### **5.3.2 Interworking with DSS 2 access supporting TB reference point procedures**
+
+##### **5.3.2.1 Receipt of IAM**
+
+The mapping of parameters/information elements to support supplementary services is described in Recommendation Q.2650, subclauses 7.1.1 (DDI), 7.2.1 (MSN), 7.3.1 (CLIP/CLIR), 7.4.1 (COLP/COLR), 7.5.1 (SUB) and 7.6.1 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of IAM to ADD PARTY.
+
+###### **5.3.2.1.1 Sending of SETUP**
+
+See 5.3.1.1.1.
+
+This mapping only applies if the new party is to be added at a subscriber access with no DSS 2 call instance yet associated to the incoming B-ISUP connection link instance.
+
+##### **5.3.2.1.2 Sending of ADD PARTY**
+
+This mapping applies if the new party is to be added at a subscriber access with already a DSS 2 call instance associated to the incoming B-ISUP connection link object instance which already exists.
+
+A new incoming B-ISUP AEI is created.
+
+| IAM | ADD PARTY |
+|------------------------------------------|----------------------------------|
+| Destination connection link identifier | |
+| ATM cell rate | |
+| Broadband bearer capability | |
+| AAL parameters | AAL parameters |
+| Broadband high layer information | Broadband high layer information |
+| Broadband low layer information (Note 1) | Broadband low layer information |
+| Called party number | Called party number |
+
+| IAM | ADD PARTY |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|
+| ST (carried in Called party number) | |
+| Leaf party type (Note 2) | |
+| | Endpoint reference (Note 3) |
+| Propagation delay counter; and
Maximum end-to-end transit delay (Note 4) | End-to-end transit delay |
+| NOTE 1 – The broadband low layer information element may be repeated up to four times. If it is repeated, all instances are mapped into a single broadband low layer information parameter in the network. The repeat indicator information element is mapped to the repeat indicator subfield of the parameter.
NOTE 2 – The leaf party type parameter is set to "Subsequent endpoint of type 2 connection".
NOTE 3 – An exchange internal association has to be created between the DSS 2 party/endpoint and the related outgoing B-ISUP AEI [Endpoint reference value <-> Signalling identifier value (SID)].
The value of the endpoint reference is locally assigned and non-zero.
NOTE 4 – The cumulative end-to-end transit delay subfield of the end-to-end transit delay information element is mapped to the propagation delay counter. The maximum end-to-end transit delay subfield is mapped to the maximum end-to-end transit delay parameter in the network. At the destination exchange, the propagation delay counter value is mapped back to the cumulative end-to-end transit delay subfield only if a maximum end-to-end transit delay parameter is present.
| |
+
+##### 5.3.2.2 Sending of ACM
+
+The conditions in which ALERTING or PARTY ALERTING apply are specified in Recommendation Q.2971.
+
+The mapping of parameters/information elements to support supplementary services is described in 7.6.1/Q.2650 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of PARTY ALERTING to ACM.
+
+###### 5.3.2.2.1 Receipt of ALERTING
+
+| ACM | ALERTING |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| | Endpoint reference (Note) |
+| NOTE – The party (endpoint reference value) has an exchange internal association with the incoming B-ISUP AEI (i.e. indirectly identifies the AEI where the B-ISUP message has to be sent).
| |
+
+###### 5.3.2.2.2 Receipt of PARTY ALERTING
+
+| ACM | PARTY ALERTING |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Called party's indicators:
called party status = "alerting" | |
+| | Endpoint reference (Note) |
+| NOTE – The party (endpoint reference value) has an exchange internal association with the incoming B-ISUP AEI (i.e. indirectly identifies the AEI where the B-ISUP message has to be sent).
| |
+
+#### 5.3.2.3 Sending of CPG
+
+The conditions in which ALERTING, PARTY ALERTING or NOTIFY apply are specified in Recommendation Q.2971.
+
+The mapping of parameters/information elements to support supplementary services is described in 7.6.1/Q.2650 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of PARTY ALERTING to CPG.
+
+###### 5.3.2.3.1 Receipt of ALERTING
+
+| CPG | ALERTING |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| | Endpoint reference (Note) |
+| NOTE – The party (endpoint reference value) has an exchange internal association with the incoming B-ISUP AEI (i.e. indirectly identifies the AEI where the B-ISUP message has to be sent). | |
+
+###### 5.3.2.3.2 Receipt of PARTY ALERTING
+
+| CPG | PARTY ALERTING |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Called party's indicators:
called party status = "alerting" | |
+| | Endpoint reference (Note) |
+| NOTE – The party (endpoint reference value) has an exchange internal association with the incoming B-ISUP AEI (i.e. indirectly identifies the AEI where the B-ISUP message has to be sent). | |
+
+##### 5.3.2.4 Sending of ANM
+
+The conditions in which CONNECT or ADD PARTY ACKNOWLEDGE apply are specified in Recommendation Q.2971.
+
+The mapping of parameters/information elements to support supplementary services is described in 7.6.1/Q.2650 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of ADD PARTY ACKNOWLEDGE to ANM.
+
+###### 5.3.2.4.1 Receipt of CONNECT
+
+| ANM | CONNECT |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| | Endpoint reference (Note) |
+| NOTE – The endpoint reference value has an exchange internal association with the incoming B-ISUP AEI (i.e. indirectly identifies the AEI where the B-ISUP message has to be sent). | |
+
+###### 5.3.2.4.2 Receipt of ADD PARTY ACKNOWLEDGE
+
+| ANM | ADD PARTY ACKNOWLEDGE |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| AAL parameters | AAL parameters |
+| Broadband low layer information | Broadband low layer information |
+| | Endpoint reference (Note 1) |
+| Call history information (Note 2) | End-to-end transit delay |
+| NOTE 1 – The party (endpoint reference value) has an exchange internal association with the incoming B ISUP AEI (i.e. indirectly identifies the AEI where the B-ISUP message has to be sent).
NOTE 2 – If applicable, the cumulative end-to-end transit delay from the called party is mapped to the call history information parameter at the destination exchange, and is mapped back to the cumulative end-to-end transit delay at the originating exchange. | |
+
+##### 5.3.2.5 Sending of REL
+
+The conditions in which RELEASE, RELEASE COMPLETE, DROP PARTY or ADD PARTY REJECT apply are specified in Recommendation Q.2971.
+
+The mapping of parameters/information elements to support supplementary services is described in 7.6.1/Q.2650 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of DROP PARTY and ADD PARTY REJECT to REL.
+
+###### 5.3.2.5.1 Receipt of RELEASE
+
+| REL (Note) | RELEASE |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| Cause indicators | Cause |
+| NOTE – The B-ISUP message is repeated for all incoming B-ISUP AEIs which are associated with the DSS 2 call instance.
A User-user information element contained in the RELEASE message is only mapped if a single leaf party exists/remains at the DSS 2 call instance, i.e. if there is no other party in the Party Alerting Received or Active State (PN4 and PN7). | |
+
+##### 5.3.2.5.2 Receipt of RELEASE COMPLETE
+
+| REL (Note) | RELEASE COMPLETE |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|
+| Cause indicators | Cause |
+| NOTE – The B-ISUP message is repeated for all incoming B-ISUP AEIs which are associated with the DSS 2 call instance.
A User-user information element contained in the RELEASE COMPLETE message is only mapped if a single leaf party exists/remains at the DSS 2 call instance, i.e. if there is no other party in the Party Alerting Received or Active State (PN4 and PN7). | |
+
+###### 5.3.2.5.3 Receipt of DROP PARTY
+
+| REL | DROP PARTY |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Cause indicators | Cause |
+| | Endpoint reference (Note) |
+| NOTE – The B-ISUP REL message is sent via the incoming B-ISUP AEI which is associated with the party (endpoint reference value) which drops off the point-to-multipoint connection. | |
+
+##### 5.3.2.5.4 Receipt of ADD PARTY REJECT
+
+| REL | ADD PARTY REJECT |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Cause indicators | Cause |
+| | Endpoint reference (Note) |
+| NOTE – The B-ISUP REL message is sent via the incoming B-ISUP AEI which is associated with the party (endpoint reference value) which rejects the add party operation. | |
+
+##### 5.3.2.6 Receipt of REL
+
+The mapping of parameters/information elements to support supplementary services is described in 7.6.1/Q.2650 (UUS1).
+
+These mappings apply in addition to the tables below and are valid also for the mapping of REL to DROP PARTY.
+
+###### 5.3.2.6.1 Sending of RELEASE
+
+This mapping applies if the destination connection link identifier is included in the REL message or for the case where only one party exists within an associated call instance at the access.
+
+| REL | RELEASE |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| Cause indicators | Cause |
+| Destination connection link identifier (Note 1); or
(no identifier included) (Note 2) | |
+| NOTE 1 – All parties associated with the incoming B-ISUP connection link object instance will be dropped (i.e. a RELEASE message is sent on each associated access).
NOTE 2 – This applies for the case where only one party exists within an associated call instance at the access. | |
+
+###### 5.3.2.6.2 Sending of DROP PARTY
+
+This mapping applies if the destination connection link identifier is not included in the REL message and more than one party exists within an associated call instance at the access.
+
+| REL | DROP PARTY |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Cause indicators | Cause |
+| | Endpoint reference (Note) |
+| NOTE – The party identified by the endpoint reference value is dropped.
The party (endpoint reference value) has an exchange internal association with the incoming B-ISUP AEI (i.e. indirectly identifies the AEI where the B-ISUP message has to be sent). | |
+
+## 5.4 Typical scenarios
+
+See Figures 5-4 to 5-12.
+
+
+
+This sequence diagram illustrates the interaction for adding a subsequent party at a $T_B$ reference point as an initial leaf party, where no alerting message and no ACM are returned. The participants are a client (B-TE1 + B-NT2 + B-NT1), two Local Exchanges, a server (B-NT1 + B-TE1 where $S_B$ and $T_B$ are coincident), and a $T_B$ reference point (B-NT1 + B-NT2) connected to two B-TE1 units via $S_B$ interfaces. The message flow is as follows:
+
+- The client sends an **Add Party** message to the first Local Exchange.
+- The first Local Exchange sends an **IAM** (Initial Address Message) to the second Local Exchange.
+- An **IAA** (Initial Address Ack) is sent from the second Local Exchange back to the first, marked with an 'X' indicating termination at the exchange.
+- The second Local Exchange sends a **Setup** message to the $T_B$ reference point.
+- A **Call Proc** (Call Processing) message is sent from the $T_B$ reference point back to the second Local Exchange, marked with an 'X'.
+- The $T_B$ reference point sends a **Connect** message to the second Local Exchange.
+- The second Local Exchange sends an **ANM** (Answer Message) to the first Local Exchange.
+- The first Local Exchange sends an **Add Party Ack or Connect** message to the client.
+- The second Local Exchange sends a **Connect Ack** message back to the $T_B$ reference point.
+
+Sequence diagram for adding a subsequent party at a TB reference point as an initial leaf party without alerting.
+
+T1176230-95
+
+**Figure 5-4/Q.2722.1 – Adding a subsequent party at a $T_B$ reference point as an initial leaf party: No alerting message and no ACM are returned**
+
+
+
+This sequence diagram illustrates the interaction for adding a subsequent party at a $T_B$ reference point as an initial leaf party, where an alerting message and ACM are returned. The participants and initial message flow (Add Party, IAM, IAA, Setup, Call Proc) are identical to Figure 5-4. The additional steps are:
+
+- The $T_B$ reference point sends an **Alerting** message to the second Local Exchange.
+- The second Local Exchange sends an **ACM** (Address Complete Message) to the first Local Exchange.
+- The first Local Exchange sends a **Party Alerting** message to the client.
+- Subsequent messages (**Connect**, **ANM**, **Add Party Ack or Connect**, and **Connect Ack**) follow the same sequence as in Figure 5-4.
+
+Sequence diagram for adding a subsequent party at a TB reference point as an initial leaf party with alerting and ACM.
+
+T1176240-95
+
+**Figure 5-5/Q.2722.1 – Adding a subsequent party at a $T_B$ reference point as an initial leaf party: Alerting message and ACM**
+
+
+
+```
+
+sequenceDiagram
+ participant TE1 as B-TE1 + B-NT2 + B-NT1
+ participant LE1 as Local Exchange
+ participant LE2 as Local Exchange
+ participant NT1_TE1 as B-NT1 + B-TE1 (S_B and T_B coincident)
+ participant NT1_NT2 as B-NT1 + B-NT2 (T_B)
+ participant TE1_SB as B-TE1 (S_B)
+
+ TE1->>LE1: Add Party
+ LE1->>LE2: IAM
+ LE2->>NT1_NT2: Setup
+ LE2--XLE1: IAA
+ NT1_NT2--XLE2: Call Proc
+ LE2--XLE1: ACM
+ NT1_NT2->>LE2: Alerting
+ LE2->>LE1: CPG
+ LE1->>TE1: Party Alerting
+ NT1_NT2->>LE2: Connect
+ LE2->>LE1: ANM
+ LE1->>TE1: Add Party Ack or Connect
+ LE2->>NT1_NT2: Connect Ack
+
+```
+
+T1176250-95
+
+Sequence diagram for Figure 5-6/Q.2722.1 showing message flow between network entities for adding a subsequent party.
+
+Figure 5-6/Q.2722.1 – Adding a subsequent party at a $T_B$ reference point as an initial leaf party: Alerting message mapped onto CPG
+
+
+
+```
+
+sequenceDiagram
+ participant TE1 as B-TE1 + B-NT2 + B-NT1
+ participant LE1 as Local Exchange
+ participant LE2 as Local Exchange
+ participant NT1_TE1 as B-NT1 + B-TE1 (S_B and T_B coincident)
+ participant NT1_NT2 as B-NT1 + B-NT2 (T_B)
+
+ TE1->>LE1: Add Party
+ LE1->>LE2: IAM
+ LE2->>NT1_TE1: Setup
+ LE2--XLE1: IAA
+ NT1_TE1--XLE2: Call Proc
+ NT1_TE1->>LE2: Connect
+ LE2->>LE1: ANM
+ LE1->>TE1: Add Party Ack or Connect
+ LE2->>NT1_TE1: Connect Ack
+
+```
+
+T1176260-95
+
+Sequence diagram for Figure 5-7/Q.2722.1 showing message flow for adding a unique leaf at a coincident SB and TB reference point.
+
+Figure 5-7/Q.2722.1 – Adding a unique leaf at a coincident $S_B$ and $T_B$ reference point: No alerting message and no ACM are returned
+
+
+
+This sequence diagram illustrates the interaction for dropping a call when the initiating party is the last one. On the left, a box contains B-TE1, B-NT2, and B-NT1. A 'Release' message goes from this box to the first 'Local Exchange', which responds with 'Release Complete' (marked with an X). The first 'Local Exchange' sends 'REL' and 'RLC' messages to the second 'Local Exchange', which also responds with 'Release Complete' (marked with an X). The second 'Local Exchange' sends a 'Release' message to a box containing B-NT1 and B-TE1, labeled 'SB and TB coincident', which responds with 'Release Complete'. In the center, a box contains B-NT1 and B-NT2, labeled 'TB'. To the right, two boxes each contain B-TE1, with lines labeled 'SB' connecting them to the B-NT1/B-NT2 box. A small text 'T1176270-95' is in the bottom right.
+
+Sequence diagram for Figure 5-8/Q.2722.1 showing a leaf party initiating dropping at a coincident SB and TB reference point, being the last party in the call/connection. The diagram shows message exchanges (Release, REL, RLC, Release Complete) between a B-TE1/B-NT2/B-NT1 entity, two Local Exchanges, and a B-NT1/B-TE1 entity where SB and TB are coincident. Other B-NT1/B-NT2 and B-TE1 entities are also shown.
+
+**Figure 5-8/Q.2722.1 – Leaf party initiating dropping at a coincident $S_B$ and $T_B$ reference point: Last party in the call/connection**
+
+
+
+This sequence diagram illustrates the interaction for dropping a call when the initiating party is not the last one. On the left, a box contains B-TE1, B-NT2, and B-NT1. A 'Drop Party' message goes from this box to the first 'Local Exchange', which responds with 'Drop Party Ack' (marked with an X). The first 'Local Exchange' sends 'REL' and 'RLC' messages to the second 'Local Exchange', which also responds with 'Release Complete' (marked with an X). The second 'Local Exchange' sends a 'Release' message to a box containing B-NT1 and B-TE1, labeled 'SB and TB coincident', which responds with 'Release Complete'. The central and right parts of the diagram are identical to Figure 5-8, showing B-NT1/B-NT2 (TB) and two B-TE1 entities connected via SB lines. A small text 'T1176280-95' is in the bottom right.
+
+Sequence diagram for Figure 5-9/Q.2722.1 showing a leaf party initiating dropping at a coincident SB and TB reference point, not being the last party in the call/connection. The diagram shows message exchanges (Drop Party, REL, RLC, Release Complete) between a B-TE1/B-NT2/B-NT1 entity, two Local Exchanges, and a B-NT1/B-TE1 entity where SB and TB are coincident. Other B-NT1/B-NT2 and B-TE1 entities are also shown.
+
+**Figure 5-9/Q.2722.1 – Leaf party initiating dropping at a coincident $S_B$ and $T_B$ reference point: Not the last party in the call/connection**
+
+
+
+Sequence diagram for Figure 5-10/Q.2722.1. The diagram shows network entities: a combined block (B-TE1 + B-NT2 + B-NT1), three Local Exchanges, a B-NT1 + B-TE1 block (SB and TB coincident), and a B-NT1 + B-NT2 block connected to two B-TE1 units via SB reference points. The message flow is as follows: 1. A 'Drop Party' message is sent from the B-TE1+B-NT2+B-NT1 block to the first Local Exchange. 2. The first Local Exchange sends 'REL' to the third Local Exchange. 3. The third Local Exchange sends 'Release' to the B-NT1+B-NT2 block at the TB reference point. 4. The B-NT1+B-NT2 block returns 'Release Complete' to the third Local Exchange. 5. The third Local Exchange returns 'RLC' to the first Local Exchange. 6. The first Local Exchange returns 'Drop Party Ack' to the initiating block. This sequence is shown twice, separated by vertical dots, indicating multiple parties being dropped. Technical label T1176290-95 is in the corner.
+
+**Figure 5-10/Q.2722.1 – B-NT2 causing multiple leaf parties to be dropped, initiated at a $T_B$ reference point: with a single RELEASE message**
+
+
+
+Sequence diagram for Figure 5-11/Q.2722.1. The diagram shows network entities: a combined block (B-TE1 + B-NT2 + B-NT1), three Local Exchanges, a B-NT1 + B-TE1 block (SB and TB coincident), and a B-NT1 + B-NT2 block connected to two B-TE1 units via SB reference points. The message flow is: 1. The B-NT1 + B-TE1 block (where SB and TB are coincident) sends a 'Release' message to the second Local Exchange. 2. The second Local Exchange returns 'Release Complete'. 3. The second Local Exchange sends 'REL' to the first Local Exchange. 4. The first Local Exchange sends 'Drop Party' to the initiating B-TE1+B-NT2+B-NT1 block. 5. The initiating block returns 'Drop Party Ack'. 6. The first Local Exchange returns 'RLC' to the second Local Exchange. Technical label T1176300-95 is in the corner.
+
+**Figure 5-11/Q.2722.1 – Root party initiating dropping at a coincident $S_B$ and $T_B$ reference point: Not for the last party in the call/connection**
+
+
+
+The diagram illustrates a sequence of messages for call/connection release initiated by a root party. The root party (B-TE1 + B-NT2 + B-NT1) sends a 'Release' message to the first 'Local exchange'. This exchange sends 'REL(DCLI)' to the second 'Local exchange', which in turn sends 'Release' to the third 'Local exchange'. The third exchange sends 'Release' to a party (B-NT1 + B-TE1) where SB and TB are coincident. Another 'Release' message is sent from the third exchange to a party (B-NT1 + B-NT2) where TB is present. This party then sends 'Release' to two other parties (B-TE1) where SB is present. 'Release complete' messages are returned from each party back through the chain of local exchanges to the root party. 'RLC' (Release Link) messages are shown being processed at the local exchanges.
+
+Sequence diagram showing call/connection release initiated by a root party. The diagram illustrates the flow of messages (Release, REL(DCLI), RLC, Release complete) between a root party (B-TE1 + B-NT2 + B-NT1), three local exchanges, and several other parties (B-NT1 + B-TE1, B-NT1 + B-NT2, B-TE1). The root party sends a Release message to the first local exchange, which then propagates it through subsequent exchanges. The diagram also shows the handling of S\_B and T\_B coincident signals and the final Release complete messages returned to the root party.
+
+T1178400-96
+
+NOTE – This is an *en bloc* release.
+
+**Figure 5-12/Q.2722.1 – Root party initiating call/connection release**
+
+# ANNEX A
+
+## Message sequence flows
+
+## Abbreviations
+
+| | |
+|------------|--------------------------------|
+| A, B, C, D | Address of party A, B, C, D |
+| CdPN | Called Party Number |
+| CEI | Connection Element ID |
+| CLn | Connection Link ID value |
+| DCLI | Destination Connection Link ID |
+| DSI | Destination Signalling ID |
+| LEX | Local Exchange |
+| MPt | Multipoint |
+| OCLI | Origination Connection Link ID |
+| OSI | Origination Signalling ID |
+| Pt | Point |
+
+Sn Signalling ID value
+ TEX Transit Exchange
+ VCI Virtual Channel ID value
+ VPCI Virtual Path Connection ID value
+
+
+
+The diagram illustrates the setup of a unidirectional point-to-multipoint call across four nodes: LEX 0 (A), TEX 1, LEX 2 (B), and LEX 3 (C, D). The connections are as follows: LEX 0 is connected to TEX 1 via 'One virtual channel'; TEX 1 is connected to LEX 2 via 'One virtual channel'; TEX 1 is also connected to LEX 3 via 'One virtual channel'. The sequence of messages is as follows:
+
+- 1st party:**
+ - LEX 0 sends an **IAM** (OSI=S01, OCLI=CL01, CdPN=B, CEI=VPCI:VCI) to TEX 1.
+ - TEX 1 sends an **IAA** (DSI=S01, OSI=S11, OCLI=CL11) back to LEX 0.
+ - TEX 1 sends an **IAM** (OSI=S14, OCLI=M12, CdPN=B, CEI=VPCI:VCI) to LEX 2.
+ - LEX 2 sends an **IAA** (DSI=S14, OSI=S21, OCLI=M21) back to TEX 1.
+- 2nd and following parties:**
+ - TEX 1 sends an **IAM** (OSI=S02, DCLI=CL11, CdPN=C) to LEX 3.
+ - LEX 3 sends an **IAA** (DSI=S02, OSI=S12) back to TEX 1.
+ - TEX 1 sends an **IAM** (OSI=S03, DCLI=CL11, CdPN=D) to LEX 3.
+ - LEX 3 sends an **IAA** (DSI=S03, OSI=S13) back to TEX 1.
+ - TEX 1 sends an **IAM** (OSI=S15, OCLI=CL12, CdPN=C, CEI=VPCI:VCI) to LEX 3.
+ - LEX 3 sends an **IAA** (DSI=S15, OSI=S31, OCLI=CL31) back to TEX 1.
+ - TEX 1 sends an **IAM** (OSI=S16, DCLI=CL31, CdPN=D) to LEX 3.
+ - LEX 3 sends an **IAA** (DSI=S16, OSI=S32) back to TEX 1.
+
+T1178410-96
+
+Sequence diagram showing the setup of a unidirectional point-to-multipoint call. It involves four nodes: LEX 0 (A), TEX 1, LEX 2 (B), and LEX 3 (C, D). The diagram shows the flow of IAM and IAA messages between these nodes to establish multiple virtual channels.
+
+Figure A.1/Q.2722.1 (sheet 1 of 2) – Set-up of a unidirectional point-to-multipoint call
+
+
+
+```
+
+sequenceDiagram
+ participant A as A (LEX 0)
+ participant TEX as TEX (1)
+ participant B as B (LEX 2)
+ participant C as C (LEX 3)
+ participant D as D
+
+ B->>TEX: ANM (DSI=S14)
+ TEX->>A: ANM (DSI=S01)
+ C->>TEX: ANM (DSI=S15)
+ TEX->>A: ANM (DSI=S02)
+ D->>TEX: ANM (DSI=S16)
+ TEX->>A: ANM (DSI=S03)
+
+```
+
+T1176330-95
+
+Sequence diagram showing the set-up of a unidirectional point-to-multipoint call. It involves nodes A (LEX 0), TEX (1), B (LEX 2), C (LEX 3), and D. ANM messages are exchanged between these nodes.
+
+**Figure A.1/Q.2722.1 (sheet 2 of 2) – Set-up of a unidirectional point-to-multipoint call**
+
+
+
+```
+
+sequenceDiagram
+ participant A as A (LEX 0)
+ participant TEX as TEX (1)
+ participant B as B (LEX 2)
+ participant C as C (LEX 3)
+ participant D as D
+
+ A->>TEX: REL (DSI=S11)
+ TEX->>B: REL (DSI=S21)
+ B->>TEX: RLC (DSI=S14)
+ TEX->>A: RLC (DSI=S01)
+
+ TEX->>C: REL (DSI=S15)
+ C->>TEX: RLC (DSI=S31)
+ A->>TEX: REL (DSI=S02)
+ TEX->>A: RLC (DSI=S12)
+
+ TEX->>D: REL (DSI=S16)
+ D->>TEX: RLC (DSI=S32)
+ A->>TEX: REL (DSI=S03)
+ TEX->>A: RLC (DSI=S13)
+
+ Note left of A: VC released and Connection Link object instance-deleted
+ Note right of D: VC released and Connection Link object instance-deleted
+
+```
+
+T1176340-95
+
+Sequence diagram showing the drop of a leaf party. It involves nodes A (LEX 0), TEX (1), B (LEX 2), C (LEX 3), and D. REL and RLC messages are exchanged. Status boxes indicate VC and Connection Link object deletion.
+
+**Figure A.2/Q.2722.1 – Drop of a leaf party**
+
+
+
+The diagram illustrates the signaling process for a unidirectional point-to-multipoint call.
+ **Nodes:** A (LEX 0), 1 (CS-1 TEX), 2 (LEX 2), 3 (LEX 3), B, C, D.
+ **Connections:**
+
+- A (LEX 0) is connected to 1 (CS-1 TEX) via 3 Virtual Channels.
+- 1 (CS-1 TEX) is connected to 2 (LEX 2) and 3 (LEX 3) via 2 Virtual Channels.
+- 2 (LEX 2) is connected to node B.
+- 3 (LEX 3) is connected to nodes C and D.
+
+**Signaling Sequence:**
+
+- Channel 1:** A → 1: IAM (OSI=S01, OCLI=CL01, CdPN=B, CEI=VPCI:VCI); 1 → A: IAA (DSI=S01, OSI=S11); 1 → 2: IAM (OSI=S14, CdPN=B, CEI=VPCI:VCI); 2 → 1: IAA (DSI=S14, OSI=S21); 2 → 3: IAM (OSI=S14, CdPN=B, CEI=VPCI:VCI); 3 → 2: IAA (DSI=S14, OSI=S21); 3 → C: IAM (OSI=S14, CdPN=B, CEI=VPCI:VCI); C → 3: IAA (DSI=S14, OSI=S31).
+- Channel 2:** A → 1: IAM (OSI=S02, OCLI=02, CdPN=C, CEI=VPCI:VCI); 1 → A: IAA (DSI=S02, OSI=S12); 1 → 2: IAM (OSI=S15, CdPN=C, CEI=VPCI:VCI); 2 → 1: IAA (DSI=S15, OSI=S21); 2 → 3: IAM (OSI=S15, CdPN=C, CEI=VPCI:VCI); 3 → 2: IAA (DSI=S15, OSI=S21); 3 → D: IAM (OSI=S15, CdPN=C, CEI=VPCI:VCI); D → 3: IAA (DSI=S15, OSI=S32).
+- Channel 3:** A → 1: IAM (OSI=S03, OCLI=03, CdPN=D, CEI=VPCI:VCI); 1 → A: IAA (DSI=S03, OSI=S13); 1 → 2: IAM (OSI=S16, CdPN=D, CEI=VPCI:VCI); 2 → 1: IAA (DSI=S16, OSI=S21); 2 → 3: IAM (OSI=S16, CdPN=D, CEI=VPCI:VCI); 3 → 2: IAA (DSI=S16, OSI=S21); 3 → C: IAM (OSI=S16, CdPN=D, CEI=VPCI:VCI); C → 3: IAA (DSI=S16, OSI=S32).
+
+Sequence diagram showing the setup of a unidirectional point-to-multipoint call. Node A (LEX 0) sends IAM and IAA messages to Node 1 (CS-1 TEX) over 3 virtual channels. Node 1 then forwards these to Node 2 (LEX 2) and Node 3 (LEX 3) over 2 virtual channels. Node 3 then distributes them to nodes B, C, and D.
+
+T1176350-95
+
+Figure A.3/Q.2722.1 (sheet 1 of 2) – Set-up of a unidirectional point-to-multipoint call – CS-1 TEX
+
+
+
+This diagram shows the final part of the call setup.
+ **Nodes:** A (LEX 0), 1 (TEX), 2 (LEX 2), 3 (LEX 3), B, C, D.
+ **Signaling Sequence:**
+
+- 1 (TEX) → A (LEX 0): ANM (DSI=S01)
+- 1 (TEX) → A (LEX 0): ANM (DSI=S02)
+- 1 (TEX) → A (LEX 0): ANM (DSI=S03)
+- 1 (TEX) → 2 (LEX 2): ANM (DSI=S14)
+- 1 (TEX) → 2 (LEX 2): ANM (DSI=S15)
+- 1 (TEX) → 2 (LEX 2): ANM (DSI=S16)
+- 2 (LEX 2) → 3 (LEX 3): ANM (DSI=S14)
+- 2 (LEX 2) → 3 (LEX 3): ANM (DSI=S15)
+- 2 (LEX 2) → 3 (LEX 3): ANM (DSI=S16)
+- 3 (LEX 3) → C: ANM (DSI=S14)
+- 3 (LEX 3) → D: ANM (DSI=S15)
+- 3 (LEX 3) → C: ANM (DSI=S16)
+
+Sequence diagram showing the continuation of the call setup. Node 1 (TEX) sends ANM messages to Node A (LEX 0) and Node 3 (LEX 3). Node 3 then forwards these to nodes B, C, and D.
+
+T1176360-95
+
+Figure A.3/Q.2722.1 (sheet 2 of 2) – Set-up of a unidirectional point-to-multipoint call – CS-1 TEX
+
+
+
+Multiparty
+control
+function
+deleted
+
+T1178420-96
+
+Sequence diagram for Figure A.4/Q.2722.1 showing the release of a unidirectional point-to-multipoint call. The diagram features vertical lifelines for LEX 0 (A), TEX 1, LEX 2 (B), and LEX 3 (C/D). Horizontal arrows represent messages: REL (DSI=S11) from LEX 0 to TEX 1, RLC (DSI=S01) from TEX 1 to LEX 0; REL (DSI=S21) from TEX 1 to LEX 2, RLC (DSI=S14) from LEX 2 to TEX 1; REL (DSI=S15) from TEX 1 to LEX 3 (C), RLC (DSI=S31) from LEX 3 (C) to TEX 1; REL (DSI=S16) from TEX 1 to LEX 3 (D), RLC (DSI=S32) from LEX 3 (D) to TEX 1; REL (DSI=S02) from TEX 1 to LEX 0, RLC (DSI=S12) from LEX 0 to TEX 1; REL (DSI=S03) from TEX 1 to LEX 0, RLC (DSI=S13) from LEX 0 to TEX 1. A box at the bottom of LEX 0's line says 'Multiparty control function deleted'.
+
+**Figure A.4/Q.2722.1 – Release of a unidirectional point-to-multipoint call – CS-1 TEX**
+
+
+
+VC released
+B-ISUP AEIs
+and outgoing
+connection
+link object
+instance-
+deleted
+
+VC released
+B-ISUP AEIs
+and incoming
+connection
+link object
+instance-
+deleted
+
+T1178430-96
+
+Sequence diagram for Figure A.5/Q.2722.1 showing the en bloc release of a multipoint call. Vertical lifelines for LEX 0 (A), TEX 1, LEX 2 (B), and LEX 3 (C/D). Messages: REL (DSI=S11, DCLI=CL11) from LEX 0 to TEX 1; REL (DSI=S21, DCLI=CL21) from TEX 1 to LEX 2; REL (DSI=S31, DCLI=CL31) from TEX 1 to LEX 3 (C). After these, two state boxes appear. Then RLC (DSI=S01) from TEX 1 to LEX 0; RLC (DSI=S14) from LEX 2 to TEX 1; RLC (DSI=S15) from LEX 3 (C) to TEX 1.
+
+**Figure A.5/Q.2722.1 – En bloc release of a multipoint call**
+
+# APPENDIX I
+
+## Instruction indicator setting
+
+The following instruction indicators may be set for the destination connection link identifier parameter:
+
+| Instruction indicator | Value | Meaning |
+|------------------------------------|-------|----------------------------------|
+| Pass on not possible | 0 | Discard parameter |
+| Discard parameter | 1 | Discard Parameter |
+| Discard message | 0 | Do not discard message (pass on) |
+| Send notification | 0 | Do not send notification |
+| Release Call | 0 | Do not release call |
+| Transit at intermediate exchange | 1 | End node interpretation |
+| Broadband/narrow-band interworking | 10 | Release call |
+
+The following instruction indicators may be set for the origination connection link identifier parameter:
+
+| Instruction indicator | Value | Meaning |
+|------------------------------------|-------|----------------------------------|
+| Pass on not possible | 1 | Discard parameter |
+| Discard parameter | 1 | Discard Parameter |
+| Discard message | 0 | Do not discard message (pass on) |
+| Send notification | 0 | Do not send notification |
+| Release Call | 0 | Do not release call |
+| Transit at intermediate exchange | 1 | End node interpretation |
+| Broadband/narrow-band interworking | 10 | Release call |
+
+The following instruction indicators may be set for the leaf party type parameter:
+
+| Instruction indicator | Value | Meaning |
+|------------------------------------|-------|------------------------------------|
+| Pass on not possible | 1 | Discard parameter |
+| Discard parameter | 0 | Do not discard parameter (pass on) |
+| Discard message | 0 | Do not discard message (pass on) |
+| Send notification | 0 | Do not send notification |
+| Release Call | 0 | Do not release call |
+| Transit at intermediate exchange | 1 | End node interpretation |
+| Broadband/narrow-band interworking | 10 | Release call |
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Telephone network and ISDN
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media
+- Series H Transmission of non-telephone signals
+- Series I Integrated services digital network
+- Series J Transmission of sound-programme and television signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound-programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality
+- Series Q Switching and signalling**
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminal equipments and protocols for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communication
+- Series Z Programming languages
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2726.4-200006-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2726.4-200006-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008
--- /dev/null
+++ b/marked/Q/T-REC-Q.2726.4-200006-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00
+size 8239
diff --git a/marked/Q/T-REC-Q.2726.4-200006-I_PDF-E/af242f25c3ad34b01ebf5fcb23430021_img.jpg b/marked/Q/T-REC-Q.2726.4-200006-I_PDF-E/af242f25c3ad34b01ebf5fcb23430021_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3289953eea1a97295f4e818667944bc646d44fb4
--- /dev/null
+++ b/marked/Q/T-REC-Q.2726.4-200006-I_PDF-E/af242f25c3ad34b01ebf5fcb23430021_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96f9d6fe1a12eff7ad14c3ea084398cbeed741959bb7d48e6363af452518b7b2
+size 30372
diff --git a/marked/Q/T-REC-Q.2730-199912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..afa31795459187de7d2e16c3d602c1bfd6106994
--- /dev/null
+++ b/marked/Q/T-REC-Q.2730-199912-I_PDF-E/raw.md
@@ -0,0 +1,1203 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking through it, and the letters 'ITU' superimposed on the globe.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.2730**
+
+(12/99)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Broadband ISDN – B-ISDN application protocols for the
+network signalling
+
+---
+
+**Signalling system No. 7 B-ISDN user part
+(B-ISUP) – Supplementary services**
+
+ITU-T Recommendation Q.2730
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+# **SWITCHING AND SIGNALLING**
+
+| | |
+|--------------------------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| General aspects | Q.2000–Q.2099 |
+| Signalling ATM adaptation layer (SAAL) | Q.2100–Q.2199 |
+| Signalling network protocols | Q.2200–Q.2299 |
+| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600–Q.2699 |
+| B-ISDN application protocols for the network signalling | Q.2700–Q.2899 |
+| B-ISDN application protocols for access signalling | Q.2900–Q.2999 |
+
+For further details, please refer to ITU-T List of Recommendations.
+
+# **SIGNALLING SYSTEM No. 7 B-ISDN USER PART (B-ISUP) – SUPPLEMENTARY SERVICES**
+
+## **Summary**
+
+This Recommendation describes the supplementary services supported in the broadband ISDN applicable to B-ISUP (with the exception of CUG, which is contained in Recommendation Q.2735.1).
+
+###### **Source**
+
+ITU-T Recommendation Q.2730 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 3 December 1999.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2000
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|-------|------------------------------------------------------------------------------------------------------------|----|
+| 1 | Scope..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Exceptions and clarifications for ISDN supplementary services in the Q.730 series of Recommendations ..... | 3 |
+| | Annex A – CLIP for non-native E.164 addresses ..... | 9 |
+| A.1 | Definition ..... | 9 |
+| A.2 | Description..... | 9 |
+| A.2.1 | General Description ..... | 9 |
+| A.2.2 | Specific terminology..... | 9 |
+| A.2.3 | Qualification on the applicability to telecommunication services..... | 10 |
+| A.3 | Operational requirements..... | 10 |
+| A.4 | Coding requirements..... | 10 |
+| A.5 | Signalling requirements ..... | 10 |
+| A.5.1 | Actions at the originating local exchange..... | 10 |
+| A.5.2 | Actions at the outgoing international gateway exchange ..... | 10 |
+| A.5.3 | Actions at the destination local exchange..... | 10 |
+| A.6 | Interaction with other supplementary services..... | 10 |
+| A.6.1 | Calling Line Identification Restriction (CLIR)..... | 11 |
+| A.7 | Interactions with other networks..... | 11 |
+| A.8 | Signalling flows ..... | 11 |
+| A.9 | Parameter values (timers) ..... | 11 |
+| A.10 | Dynamic description ..... | 11 |
+| | Annex B – CLIR for non-native E.164 addresses ..... | 19 |
+| B.1 | Definition ..... | 19 |
+| B.1.1 | General description..... | 19 |
+| B.1.2 | Specific terminology..... | 19 |
+| B.1.3 | Qualification on the applicability to telecommunication services..... | 19 |
+| B.2 | Description..... | 19 |
+| B.3 | Operational requirements..... | 19 |
+| B.4 | Coding requirements..... | 19 |
+| B.5 | Signalling requirements ..... | 19 |
+| B.5.1 | Actions at the originating local exchange..... | 19 |
+| B.5.2 | Actions at the outgoing international gateway exchange ..... | 20 |
+
+| | Page |
+|-----------------------------------------------------------------------------|-------------|
+| B.6 Interaction with other supplementary services..... | 20 |
+| B.6.1 Calling Line Identification Restriction (CLIR)..... | 20 |
+| B.7 Interactions with other networks..... | 20 |
+| B.8 Signalling flows ..... | 20 |
+| B.9 Parameter values (timers) ..... | 20 |
+| B.10 Dynamic description ..... | 20 |
+| Annex C – COLP for non-native E.164 addresses..... | 20 |
+| C.1 Definition ..... | 20 |
+| C.2 Description..... | 20 |
+| C.2.1 General Description..... | 20 |
+| C.2.2 Specific terminology..... | 20 |
+| C.2.3 Qualification on the applicability to telecommunication services..... | 21 |
+| C.3 Operational requirements..... | 21 |
+| C.4 Coding requirements..... | 21 |
+| C.5 Signalling requirements ..... | 21 |
+| C.5.1 Actions at the originating local exchange..... | 21 |
+| C.5.2 Actions at the incoming international gateway exchange..... | 21 |
+| C.5.3 Actions at the destination local exchange..... | 21 |
+| C.6 Interaction with other supplementary services..... | 21 |
+| C.7 Interactions with other networks..... | 22 |
+| C.8 Signalling flows ..... | 22 |
+| C.9 Parameter values (timers) ..... | 22 |
+| C.10 Dynamic description ..... | 22 |
+| Annex D – COLR for non-native E.164 addresses ..... | 30 |
+| D.1 Definition ..... | 30 |
+| D.2 Description..... | 30 |
+| D.2.1 General Description..... | 30 |
+| D.2.2 Specific terminology..... | 30 |
+| D.2.3 Qualification on the applicability to telecommunication services..... | 30 |
+| D.3 Operational requirements..... | 30 |
+| D.4 Coding requirements..... | 30 |
+| D.5 Signalling requirements ..... | 30 |
+| D.5.1 Actions at the incoming international gateway exchange..... | 30 |
+| D.5.2 Actions at the destination local exchange..... | 31 |
+| D.6 Interaction with other supplementary services..... | 31 |
+
+| | | |
+|--------------|-----------------------------------------|----|
+| D.7 | Interactions with other networks..... | 31 |
+| D.8 | Signalling flows ..... | 31 |
+| D.9 | Parameter values (timers) ..... | 31 |
+| D.10 | Dynamic description ..... | 31 |
+| Appendix I – | Setting of instruction indicators ..... | 32 |
+
+
+
+# **SIGNALLING SYSTEM No. 7 B-ISDN USER PART (B-ISUP) – SUPPLEMENTARY SERVICES**
+
+*(revised in 1999)*
+
+## **1 Scope**
+
+This Recommendation specifies the exceptions to the 1997 Q.730 series of Recommendations for supplementary services to be supported in the broadband network. The information contained in this Recommendation should be read in conjunction with the 1997 Q.730 series of Recommendations.
+
+The following services are supported by the first version of the B-ISUP:
+
+- User-to-User Signalling (Recommendation Q.737).
+- Calling Line Identification Presentation/Restriction (clause 3/Q.731 and clause 4/Q.731).
+- Direct-Dialling-In (clause 1/Q.731).
+- Connected Line Identification Presentation/Restriction (clause 5/Q.731 and clause 6/Q.731).
+- Sub-addressing (clause 8/Q.731).
+- Multiple Subscriber Number (clause 2/Q.731).
+- Closed User Group (clause 1/Q.735).
+
+Direct-Dialling-In and Multiple Subscriber Number are supported but without relevance to B-ISUP.
+
+## **2 References**
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- [1] ITU-T Recommendation Q.2761 (1999), *Functional description of the B-ISDN user part (B-ISUP) of signalling system No. 7.*
+- [2] ITU-T Recommendation Q.2762 (1999), *General functions of messages and signals of the B-ISDN user part (B-ISUP) of signalling system No. 7.*
+- [3] ITU-T Recommendation Q.2763 (1999), *Signalling system No. 7 B-ISDN user part (B-ISUP) – Formats and codes.*
+- [4] ITU-T Recommendation Q.2764 (1999), *Signalling system No. 7 B-ISDN user part (B-ISUP) – Basic call procedures.*
+- [5] ITU-T Recommendation Q.2735.1 (1997), *Stage 3 description for community of interest supplementary services for B-ISDN using SS No. 7: Closed user group (CUG).*
+- [6] ITU-T Recommendation Q.761 (1997), *Signalling system No. 7 – ISDN user part functional description.*
+- [7] ITU-T Recommendation Q.762 (1997), *Signalling system No. 7 – ISDN user part general functions of messages and signals.*
+
+- [8] ITU-T Recommendation Q.763 (1997), *Signalling system No. 7 – ISDN user part formats and codes.*
+- [9] ITU-T Recommendation Q.764 (1997), *Signalling system No. 7 – ISDN user part signalling procedures.*
+- [10] ITU-T Recommendation Q.730 (1997), *ISDN user part supplementary services.*
+- [11] ITU-T Recommendation Q.731.1 (1996), *Stage 3 description for number identification supplementary services using signalling system No. 7: Direct-dialling-in (DDI).*
+- [12] ITU-T Recommendation Q.731.3 (1993), *Stage 3 description for number identification supplementary services using signalling system No. 7: Calling line identification presentation (CLIP).*
+- [13] ITU-T Recommendation Q.731.4 (1993), *Stage 3 description for number identification supplementary services using signalling system No. 7: Calling line identification restriction (CLIR).*
+- [14] ITU-T Recommendation Q.731.5 (1993), *Stage 3 description for number identification supplementary services using signalling system No. 7: Connected line identification presentation (COLP).*
+- [15] ITU-T Recommendation Q.731.6 (1993), *Stage 3 description for number identification supplementary services using signalling system No. 7: Connected line identification restriction (COLR).*
+- [16] ITU-T Recommendation Q.731.7 (1997), *Stage 3 description for number identification supplementary services using signalling system No. 7: Malicious call identification (MCID).*
+- [17] CCITT Recommendation Q.731.8 (1992), *Stage 3 description for number identification supplementary services using signalling system No. 7: Sub-addressing (SUB).*
+- [18] ITU-T Recommendation Q.732.2 (1996), *Stage 3 description for call offering supplementary services using signalling system No. 7: Call diversion services: call forwarding busy, call forwarding no reply, call forwarding unconditional, call deflection.*
+- [19] ITU-T Recommendation Q.732.7 (1996), *Stage 3 description for call offering supplementary services using signalling system No. 7: Explicit call transfer.*
+- [20] CCITT Recommendation Q.733.1 (1992), *Stage 3 description for call completion supplementary services using signalling system No. 7: Call waiting (CW).*
+- [21] ITU-T Recommendation Q.733.2 (1993), *Stage 3 description for call completion supplementary services using signalling system No. 7: Call hold (HOLD).*
+- [22] ITU-T Recommendation Q.733.3 (1997), *Stage 3 description for call completion supplementary services using signalling system No. 7: Completion of calls to busy subscriber (CCBS).*
+- [23] ITU-T Recommendation Q.733.4 (1993), *Stage 3 description for call completion supplementary services using signalling system No. 7: Terminal portability (TP).*
+- [24] ITU-T Recommendation Q.734.1 (1993), *Stage 3 description for multiparty supplementary services using signalling system No. 7: Conference calling.*
+- [25] ITU-T Recommendation Q.734.2 (1996), *Stage 3 description for multiparty supplementary services using signalling system No. 7: Three-party service.*
+- [26] ITU-T Recommendation Q.735.1 (1993), *Stage 3 description for community of interest supplementary services using signalling system No. 7, Closed user group (CUG).*
+
+- [27] ITU-T Recommendation Q.735.3 (1993), *Stage 3 description for community of interest supplementary services using signalling system No. 7: Multi-level precedence and preemption.*
+- [28] ITU-T Recommendation Q.735.6 (1996), *Stage 3 description for community of interest supplementary services using signalling system No. 7: Global virtual network service (GVNS).*
+- [29] ITU-T Recommendation Q.736.1 (1995), *Stage 3 description for charging supplementary services using signalling system No. 7: International telecommunication charge card (ITCC).*
+- [30] ITU-T Recommendation Q.736.3 (1995), *Stage 3 description for charging supplementary services using signalling system No. 7: Reverse charging (REV).*
+- [31] ITU-T Recommendation Q.737.1 (1997), *Stage 3 description for additional information transfer supplementary services using signalling system No. 7: User-to-user signalling (UUS).*
+- [32] ITU-T Recommendation Q.2951.3 (1995), *Stage 3 description for number identification supplementary services using B-ISDN digital subscriber signalling system No. 2 (DSS2) – Basic call: Calling line identification presentation (CLIP).*
+- [33] ITU-T Recommendation Q.2951.4 (1995), *Stage 3 description for number identification supplementary services using B-ISDN digital subscriber signalling system No. 2 (DSS2) – Basic call: Calling line identification restriction (CLIR).*
+- [34] ITU-T Recommendation Q.2951.5 (1995), *Stage 3 description for number identification supplementary services using B-ISDN digital subscriber signalling system No. 2 (DSS2) – Basic call: Connected line identification presentation (COLP).*
+- [35] ITU-T Recommendation Q.2951.6 (1995), *Stage 3 description for number identification supplementary services using B-ISDN digital subscriber signalling system No. 2 (DSS2) – Basic call: Connected line identification restriction (COLR).*
+- [36] ITU-T Recommendation Q.2951.9 (1999), *Stage 3 description for number identification supplementary services using B-ISDN digital subscriber signalling system No. 2 (DSS2) – Basic call: Support of ATM end system addressing format by number identification supplementary services.*
+- [37] ITU-T Recommendation E.191 (1996), *B-ISDN numbering and addressing.*
+
+## 3 Exceptions and clarifications for ISDN supplementary services in the Q.730 series of Recommendations
+
+The following tables contain three columns as follows:
+
+- The first column marked "Q.73x references" identifies the relevant Q.73x Recommendation and references.
+- The second column marked "Title" identifies the relevant title.
+- The third column marked "Remarks" identifies the deviations from Q.73x as appropriate for the broadband signalling references.
+
+All subclauses are the same as in the Q.730 series of Recommendations unless indicated otherwise in Tables 1 to 8 below.
+
+The remark "Not applicable" in the tables means that a procedure described in Recommendation Q.73x is not available in the broadband signalling references.
+
+**Table 1/Q.2730**
+
+| Q.730
references | Title | Remarks |
+|-----------------------------|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | General | References to TC and SCCP are not applicable. |
+| 1.2 | Network-specific facilities (national option) | Not applicable. |
+| 1.2.1 | Sending unsolicited information (national use) | Not applicable. |
+| 1.3 | Generic procedures | Not applicable. |
+| 1.4 | End-to-end signalling | Not applicable. |
+| 1.6 | List of supplementary services | The following services are not applicable:
– 7/Q.731 Malicious Call Identification (MCID)
– 1/Q.732 Call Transfer (CT)
– 2/Q.732 Call Forwarding Busy (CFB)
– 3/Q.732 Call Forwarding No Reply (CFNR)
– 4/Q.732 Call Forwarding Unconditional (CFU)
– 5/Q.732 Call Deflection (CD)
– 6/Q.732 Line Hunting (LH)
– 7/Q.732 Explicit Call Transfer (ECT)
– 8/Q.732 Single Step Call Transfer (SCT)
– 1/Q.733 Call Waiting (CW)
– 2/Q.733 Call Hold (HOLD)
– 3/Q.733 Completion of Calls to Busy Subscriber (CCBS)
– 4/Q.733 Terminal Portability (TP)
– 1/Q.734 Conference Calling (CONF)
– 2/Q.734 Three-Party Service (3PTY)
– 3/Q.735 Multi-Level Precedence and Preemption (MLPP)
– 6/Q.735 Global Virtual Network Service (GVNS)
– 1/Q.736 International Telecommunication Charge Card (ITCC)
– 2/Q.736 Advice of Charge (AOC)
– 3/Q.736 Reverse Charging (REV) |
+| Appendix I | Contents of the interface elements between the ISDN user part and the SCCP | Not applicable. |
+
+**Table 2/Q.2730**
+
+| Q.731 references | Title | Remarks |
+|-------------------------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 3.2.1 | General description | Additional description for non-native E.164 addresses is described in Annex A of this Recommendation. |
+| 3.2.2 | Specific terminology | Additional terminology for non-native E.164 addresses is described in Annex A of this Recommendation. |
+| 3.4 | Coding requirements | i) The Access transport parameter is not used, the calling party subaddress information is transported in the calling party subaddress parameter.
ii) The Generic number parameter is not used, the additional calling party number is transported in the additional calling party number parameter.
iii) The number qualifier indicator is not used.
iv) Additional coding requirements for non-native E.164 addresses are described in Annex A of this Recommendation. |
+| 3.5 | Signalling requirements | Same remarks as for 3.4. Additional signalling requirements for non-native E.164 addresses are described in Annex A of this Recommendation. |
+| Table 3-1 | Calling party number, codepoints | The content of the table is superseded by Figure 1 in Annex A of this Recommendation. |
+| 3.6.6 | Calling Line Identification Restriction (CLIR) | Replace "Generic number parameter" with "additional calling party number parameter". For non-native E.164 addresses, see Annex A of this Recommendation. |
+| 3.6.10 | Call Diversion services (CDIV) | Not applicable. |
+| 3.7 | Interactions with other networks | Replace "Generic number parameter" with "additional calling party number parameter". Additional procedures for non-E.164 addresses are described in Annex A of this Recommendation. |
+| 3.10 | Dynamic description | The dynamic description is specified in Figures 1 and 2 in Annex A of this Recommendation. |
+| 4.5.2.1.1 | Normal operation | Replace "Generic number parameter" with "additional calling party number parameter". Additional procedures for non-E.164 addresses are described in Annex B of this Recommendation. |
+| 4.5.2.3.2 | Exceptional procedures | Replace "Generic number parameter" with "additional calling party number parameter". Additional procedures for non-E.164 addresses are described in Annex B of this Recommendation. |
+| 4.6.5 | Calling Line Identification Presentation (CLIP) | Replace "Generic number parameter" with "additional calling party number parameter". Additional procedures for non-E.164 addresses are described in Annex B of this Recommendation. |
+
+**Table 2/Q.2730 (continued)**
+
+| Q.731
references | Title | Remarks |
+|---------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 5.1 | Definition | Replace "connected party's ISDN number" with "connected number". |
+| 5.2.1 | General description | Replace "Generic number parameter" with "additional connected number parameter". Additional description for non-native E.164 addresses is described in Annex C of this Recommendation. |
+| 5.4 | Coding requirements | i) The Access transport parameter is not used, the connected party subaddress information is transported in the connected party subaddress parameter.
ii) The Generic number parameter is not used, the additional connected number is transported in the additional connected number parameter.
iii) The number qualifier indicator is not used.
iv) Additional coding requirements for non-native E.164 addresses are described in Annex C of this Recommendation. |
+| 5.5 | Signalling requirements | Same remarks as for 5.4. Additional signalling requirements for non-native E.164 addresses are described in Annex C of this Recommendation.
Replace "optional forward call indicator" with "Connected line identity request parameter". |
+| 5.7 | Interactions with other networks | Replace "Generic number parameter" with "additional connected number parameter". Additional procedures for non-E.164 addresses are described in Annex C of this Recommendation. |
+| 5.8 | Signalling flows | Replace "Generic number" with "additional connected number". For non-native E.164 addresses the connected number is to be substituted by AESA (ATM End System Address) for connected party and the additional connected number is to be substituted by AESA for additional connected party . |
+| 5.10 | Dynamic description | The dynamic description is specified in through in Annex A of this Recommendation |
+| 6.2.1 | General description | Replace "connected user's ISDN number" with "connected user's number". |
+| 6.5.2.4.1 | Normal operation | Replace "Generic number parameter" with "additional connected number parameter". Additional procedures for non-E.164 addresses are described in Annex D of this Recommendation. |
+| 6.5.2.5.1 | Normal operation | Replace "Generic number parameter" with "additional connected number parameter". Additional procedures for non-E.164 addresses are described in Annex D of this Recommendation. |
+
+**Table 2/Q.2730 (end)**
+
+| Q.731 references | Title | Remarks |
+|-------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 7 | Malicious Call Identification (MCID) | Not applicable. |
+| 8.2.1 | General description | Replace the words "access transport" with "called party sub-address". |
+| 8.4 | Coding requirements | Replace the first sentence by, "The sub-address information is carried in the called party sub-address parameter."
In the second sentence, replace the words "sub-address information element" with "called party sub-address parameter". |
+| 8.5.2.1.1 | Normal operation | Replace the words "access transport" with "called party sub-address". |
+| 8.5.2.2.1 | Normal operation | Replace the words "access transport" with "called party sub-address". |
+| 8.5.2.3.1 | Normal operation | Replace the words "access transport" with "called party sub-address". |
+| 8.5.2.4.1 | Normal operation | Replace the words "access transport" with "called party sub-address". |
+
+**Table 3/Q.2730**
+
+| Q.732 references | Title | Remarks |
+|-------------------------|-------------------------|-----------------|
+| 2-5 | Call diversion services | Not applicable. |
+| 7 | Explicit call transfer | Not applicable. |
+
+**Table 4/Q.2730**
+
+| Q.733 references | Title | Remarks |
+|-------------------------|-----------------------------------------------|-----------------|
+| 1 | Call Waiting (CW) | Not applicable. |
+| 2 | Call Hold (HOLD) | Not applicable. |
+| 3 | Completion of Calls to Busy Subscriber (CCBS) | Not applicable. |
+| 4 | Terminal Portability (TP) | Not applicable. |
+| 4.6.13.3 | User-to-User Signalling, service 3 (UUS3) | Not applicable. |
+
+**Table 5/Q.2730**
+
+| Q.734 references | Title | Remarks |
+|-------------------------|--------------------|-----------------|
+| 1 | Conference calling | Not applicable. |
+| 2 | Three Party | Not applicable. |
+
+**Table 6/Q.2730**
+
+| Q.735 references | Title | Remarks |
+|-------------------------|---------------------------------------------|-----------------|
+| 1 | Closed User Group (CUG) | See [5]. |
+| 3 | Multilevel Precedence and Preemption (MLPP) | Not applicable. |
+| 6 | Global Virtual Network Service (GVNS) | Not applicable. |
+
+**Table 7/Q.2730**
+
+| Q.736 references | Title | Remarks |
+|-------------------------|----------------------------------------------------|-----------------|
+| 1 | International Telecommunication Charge Card (ITCC) | Not applicable. |
+| 3 | Reverse Charging (REV) | Not applicable. |
+
+**Table 8/Q.2730**
+
+| Q.737 references | Title | Remarks |
+|-------------------------|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1.1.2.2 | Specific terminology | User-to-user Indicators indicating request/acceptance/rejection are not applicable. |
+| 1.1.4 | Coding requirements | The second paragraph is not applicable. |
+| 1.1.5.2.1.1.2 | Explicit service request | Not applicable. |
+| 1.1.5.2.1.1.3 | Transfer of user-to-user information | Replace the first paragraph with the following: "User-to-user information may be contained in any of the messages that may be transferred in the call set-up and call release phases, provided the request for implicit service 1 has not been discarded." |
+| 1.1.5.2.1.2 | Exceptional procedures | In the first sentence, replace the words "and rejection indicators" with "indication". |
+| 1.1.5.2.2.2 | Exceptional procedures | In the second sentence, delete the words "Rejection of an explicit service request or". |
+| 1.1.5.2.5.2.2 | Rejection of explicit service request | Not applicable. |
+
+**Table 8/Q.2730 (concluded)**
+
+| Q.737 references | Title | Remarks |
+|-------------------------|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1.1.5.2.5.2.3 | Discard of user-to-user information | In the first paragraph, second sentence, replace the words "with Q.767 ISUP" with "between Recommendation Q.767 and ISUP'92 or later". The second paragraph is not applicable. |
+| 1.1.6.10 | Call diversion services | Not applicable. |
+| 1.1.6.13 | User-to-User Signalling (UUS) | Not applicable. |
+| 1.1.6.16 | Call Hold (HOLD) | Not applicable. |
+| 1.1.7 | Interactions with other networks | In the first sentence, delete the words "or explicit". In Table 1-1 delete the columns entitled "Non-essential request" and "Essential request". Notes 2 and 3 are not applicable. |
+| 1.1.8 | Signalling flows | In the first paragraph, delete the second sentence. In Notes 1 and 2 delete the words "user-to-user indicators parameter and/or". In the table of abbreviations, the following abbreviations are not applicable: "ni", "rne", "re", "p", "np" and "UUI ind". |
+| 1.2 | User-to-User Signalling service 2 | Not applicable. |
+| 1.3 | User-to-User Signalling service 3 | Not applicable. |
+
+## ANNEX A
+
+## **CLIP for non-native E.164 addresses**
+
+### **A.1 Definition**
+
+See clause 3/Q.731 with the modifications listed in Table 2.
+
+### **A.2 Description**
+
+#### **A.2.1 General Description**
+
+See clause 3/Q.731 with the modifications listed in Table 2, and the following additions:
+
+The stage 3 DSS2 description is given in Recommendations Q.2951.3 [32] and Q.2951.9 [36]. This stage 3 description of the CLIP supplementary service uses the Broadband ISDN user part protocol as defined in Recommendations Q.2761-Q.2764.
+
+#### **A.2.2 Specific terminology**
+
+See clause 3/Q.731 with the modifications listed in Table 2, and the following additions and modifications:
+
+**A.2.2.1 ATM end system address:** The ATM end system address is an address that uniquely identifies an ATM endpoint (see Recommendation E.191 [37]).
+
+**A.2.2.2 native E.164 number:** See "ISDN number".
+
+**A.2.2.3 sub-address:** See Recommendation E.191 [37].
+
+**A.2.2.4 served user:** It is the user of a particular ISDN number or AESA who has subscribed to the presentation of the calling line identification information in association with incoming calls. The served user is also known as the called user.
+
+**A.2.2.5 default number:** A national significant ISDN number or an AESA registered within the public ISDN following prior arrangement between the calling user and the public ISDN.
+
+#### **A.2.3 Qualification on the applicability to telecommunication services**
+
+See clause 3/Q.731 with the modifications listed in Table 2.
+
+### **A.3 Operational requirements**
+
+See clause 3/Q.731 with the modifications listed in Table 2.
+
+### **A.4 Coding requirements**
+
+See clause 3/Q.731 with the modifications listed in Table 2, and the following additions:
+
+#### i) *Coding requirements if a special arrangement does not apply*
+
+Recommendation Q.2763 gives the coding for the *AESA for calling party* parameter which is required to support this service.
+
+The purpose of the *AESA for calling party* parameter is to identify the origin of a call when the calling line identity is an AESA. This number may be provided by the network or by the calling user and verified by the network.
+
+#### ii) *Coding requirements if a special arrangement applies*
+
+Recommendation Q.2763 gives the coding for the *AESA for additional calling party* parameter which is required to support this service.
+
+The purpose of the *AESA for additional calling party* parameter is to transport an AESA calling party number provided by the calling user with a special arrangement.
+
+### **A.5 Signalling requirements**
+
+See clause 3/Q.731 with the modifications listed in Table 2, and the following additions:
+
+#### **A.5.1 Actions at the originating local exchange**
+
+The actions at the originating local exchange are specified by the SDL provided in Figure A.1, which also contains the pure native E.164 case as a special case.
+
+#### **A.5.2 Actions at the outgoing international gateway exchange**
+
+The procedures of Recommendation Q.731 with respect to the handling of the *address presentation restricted indicator* shall be applied analogous to the *AESA for calling party* and *AESA for additional calling party* parameters.
+
+#### **A.5.3 Actions at the destination local exchange**
+
+The actions at the destination local exchange are specified by the SDL provided in Figure A.2, which also contains the pure native E.164 case as a special case.
+
+### **A.6 Interaction with other supplementary services**
+
+See clause 3/Q.731 with the modifications listed in Table 2, and the following additions:
+
+#### **A.6.1 Calling Line Identification Restriction (CLIR)**
+
+Depending on bilateral agreement, the originating network may restrict the information conveyed in the *AESA for additional calling party* and/or *AESA for calling party* parameter(s) from being sent to the destination network when the CLIR supplementary service is applicable.
+
+### **A.7 Interactions with other networks**
+
+ATM end system addresses are not received from or sent to ISUP networks. A broadband/narrowband interworking exchange shall discard the *AESA for calling party* and/or *AESA for additional calling party* parameter.
+
+### **A.8 Signalling flows**
+
+See clause 3/Q.731 with the modifications listed in Table 2.
+
+### **A.9 Parameter values (timers)**
+
+See clause 3/Q.731 with the modifications listed in Table 2.
+
+### **A.10 Dynamic description**
+
+The dynamic description is specified in Figures A.1 and A.2.
+
+
+
+```
+
+graph TD
+ OLEX([CLIP supplementary service OLEX]) --> SetUpInd[Set-Up Ind.]
+ OLEX --> CgPN{CgPN IE provided by the calling user?}
+ CgPN -- Yes --> Y1((Y1))
+ CgPN -- No --> A((A))
+ A --> TypeDefault{Type of default number according to subscription?}
+ TypeDefault -- native E.164 --> Gen1[generate Calling party number with { default number, SI := "network provided", NPI := "ISDN (Telephony)" }]
+ TypeDefault -- AESA (E.164) --> Gen2[generate AESA for calling party with { default number, SI := "network provided", NPI := "AESA" }]
+ TypeDefault -- AESA (other) --> Gen3[generate AESA for calling party with { default number, SI := "network provided", NPI := "AESA" }]
+ Gen2 --> Gen4[generate calling party number with { E.164 number in the IDI part of default number, SI := "network provided", NPI := "ISDN (Telephony)" }]
+ Gen1 --> B((B))
+ Gen4 --> B
+ Gen3 --> B
+ B --> CLIR[CLIR supplementary service]
+ CLIR --> End((X))
+ T11108600-00((T11108600-00))
+
+```
+
+The flowchart illustrates the CLIP procedures at the originating local exchange (OLEX). It begins with the OLEX providing a Set-Up Indication. A decision is made regarding the CgPN IE provided by the calling user. If 'Yes', the process ends at Y1. If 'No', the process proceeds to a connector A. From A, the process moves to a decision on the type of default number according to subscription. Three options are available: native E.164, AESA (E.164), and AESA (other). For native E.164, the calling party number is generated with default number, SI := "network provided", and NPI := "ISDN (Telephony)". For AESA (E.164), the AESA for the calling party is generated with default number, SI := "network provided", and NPI := "AESA". For AESA (other), the AESA for the calling party is generated with default number, SI := "network provided", and NPI := "AESA". The AESA (E.164) path further generates the calling party number with the E.164 number in the IDI part of the default number, SI := "network provided", and NPI := "ISDN (Telephony)". All three generated numbers lead to connector B. From B, the process moves to the CLIR supplementary service, which then leads to the end of the procedure. A reference code T11108600-00 is shown near connector B.
+
+Flowchart of CLIP procedures at the originating local exchange (OLEX).
+
+OLEX Originating Local Exchange
+ CgPN Calling Party Number
+ IE Information Element
+ SI Screening Indicator
+ NPI Numbering Plan Indicator
+ IDI Initial Domain Identifier
+
+**Figure A.1/Q.2730 – CLIP procedures at the originating local exchange**
+
+
+
+```
+
+graph TD
+ Y1((Y1)) --> D1{Special arrangement?}
+ D1 -- Yes --> Y2((Y2))
+ D1 -- No --> D2{Screening result (acc. to number format received)?}
+ D2 -- passed --> P((P))
+ D2 -- incorrect number --> T1[/National option: send incorrect number/]
+ T1 -- No --> A((A))
+ T1 -- Yes --> D3{Format of CgPN received?}
+ D3 -- native E.164 --> B1[generate Additional calling party number with { user provided number, SI := "user provided, verified and failed", NPI := "ISDN (Telephony)" }]
+ D3 -- AESA (E.164) --> B2[generate AESA for additional calling party with { user provided number, SI := "user provided, verified and failed", NPI := "AESA" }]
+ D3 -- AESA (other) --> B3[generate AESA for additional calling party with { user provided number, SI := "user provided, verified and failed", NPI := "AESA" }]
+ B2 --> B4[generate Additional calling party number with { E.164 number in the IDI part of user provided number, SI := "user provided, verified and failed", NPI := "ISDN (Telephony)" }]
+ B1 --> A
+ B4 --> A
+ B3 --> A
+ T11108610-00[T11108610-00]
+
+```
+
+Flowchart of CLIP procedures at the originating local exchange. It starts at Y1, checks for special arrangements, then screening results. If incorrect number, it checks national options. If yes, it checks the format of CgPN received (native E.164, AESA (E.164), or AESA (other)) and generates the appropriate Additional Calling Party Number (ACPN) with specific SI and NPI values. All paths lead to connector A.
+
+Figure A.1/Q.2730 – CLIP procedures at the originating local exchange (continued)
+
+
+
+```
+
+graph TD
+ P((P)) --> D{Format of CgPN received?}
+ D -- native E.164 --> B1[generate Calling party number with { user provided number, SI := "user provided, verified and passed", NPI := "ISDN (Telephony)" }]
+ D -- AESA (E.164) --> B2[generate AESA for calling party with { user provided number, SI := "user provided, verified and passed", NPI := "AESA" }]
+ D -- AESA (other) --> B3[generate AESA for calling party with { user provided number, SI := "user provided, verified and passed", NPI := "AESA" }]
+ B1 --> B
+ B2 --> B4[generate Calling party number with { E.164 number in the IDI, SI := "user provided, verified and passed", NPI := "ISDN (Telephony)" }]
+ B3 --> B
+ B4 --> B
+ T11108620-00[T11108620-00]
+
+```
+
+The flowchart illustrates the CLIP procedures at the originating local exchange. It begins at point **P** and leads to a decision diamond: **Format of CgPN received?**. From this decision, three paths emerge based on the format of the CgPN received:
+
+- native E.164**: This path leads to a process box: **generate Calling party number with { user provided number, SI := "user provided, verified and passed", NPI := "ISDN (Telephony)" }**. This path then leads directly to the end point **B**.
+- AESA (E.164)**: This path leads to a process box: **generate AESA for calling party with { user provided number, SI := "user provided, verified and passed", NPI := "AESA" }**. This path then leads to another process box: **generate Calling party number with { E.164 number in the IDI, SI := "user provided, verified and passed", NPI := "ISDN (Telephony)" }**, which finally leads to the end point **B**.
+- AESA (other)**: This path leads to a process box: **generate AESA for calling party with { user provided number, SI := "user provided, verified and passed", NPI := "AESA" }**. This path then leads directly to the end point **B**.
+
+A reference code **T11108620-00** is located near the bottom right of the flowchart.
+
+Flowchart of CLIP procedures at the originating local exchange. It starts at point P, checks the format of CgPN received (native E.164, AESA (E.164), or AESA (other)), generates the appropriate calling party information, and ends at point B.
+
+**Figure A.1/Q.2730 – CLIP procedures at the originating local exchange (continued)**
+
+
+
+```
+
+graph TD
+ Y2((Y2)) --> Decision{Format of CgPN received?}
+ Decision -- native E.164 --> Box1[generate Additional calling party number with { user provided number, SI := "user provided, not verified", NPI := "ISDN (Telephony)" }]
+ Decision -- AESA (E.164) --> Box2[generate AESA for additional calling party with { user provided number, SI := "user provided, not verified", NPI := "AESA" }]
+ Decision -- AESA (other) --> Box3[generate AESA for additional calling party with { user provided number, SI := "user provided, not verified", NPI := "AESA" }]
+ Box1 --> Box4[generate Additional calling party number with { E.164 number in the IDI part of user provided number, SI := "user provided, not verified", NPI := "ISDN (Telephony)" }]
+ Box2 --> Box4
+ Box3 --> Box4
+ Box4 --> A((A))
+ T11108630-00[T11108630-00]
+
+```
+
+Flowchart showing CLIP procedures at the originating local exchange. It starts with 'Y2' leading to a decision 'Format of CgPN received?'. Three branches follow: 'native E.164', 'AESA (E.164)', and 'AESA (other)'. Each branch leads to a box with instructions to generate a calling party number with specific SI and NPI values. All three branches converge to a central box with instructions to generate an E.164 number in the IDI part. All three branches then converge to a final circle 'A'. A label 'T11108630-00' is present near the bottom right.
+
+**Figure A.1/Q.2730 – CLIP procedures at the originating local exchange (concluded)**
+
+
+
+```
+
+graph TD
+ Start([CLIP supplementary service DLEX]) --> SI[Set-Up Indication]
+ Start --> PF{Presentation format?}
+ PF -- native E.164 --> P1((P1))
+ PF --> APN{Additional calling party number present?}
+ APN -- Yes --> P1a[Prepare CgPN IE to include Additional calling party number as received]
+ APN -- No --> CPN{Calling party number present?}
+ CPN -- Yes --> P1b[Prepare CgPN IE to include Calling Party number as received]
+ CPN -- No --> None[Include no CgPN IE]
+ P1a --> TNO{Two number delivery option?}
+ TNO -- Yes --> CPN2{Calling party number present?}
+ TNO -- No --> One[Include one CgPN IE]
+ CPN2 -- Yes --> P2[Prepare 2nd CgPN IE to include Calling party number as received]
+ CPN2 -- No --> One
+ P2 --> Two[Include two CgPN IEs]
+ P1b --> One
+ Two --> R((R))
+ One --> R
+ None --> R
+
+```
+
+DLEX Destination Local Exchange
+ CgPN Calling Party Number
+ IE Information Element
+ SI Screening Indicator
+ NPI Numbering Plan Indicator
+
+T11108640-00
+
+Flowchart of CLIP procedures at the destination local exchange. It starts with 'CLIP supplementary service DLEX' and 'Set-Up Indication'. It branches based on 'Presentation format?' (native E.164 leads to P1), 'Additional calling party number present?' (Yes leads to 'Prepare CgPN IE to include Additional calling party number as received'; No leads to 'Calling party number present?'), and 'Two number delivery option?' (Yes leads to 'Prepare 2nd CgPN IE to include Calling party number as received'; No leads to 'Include one CgPN IE'). Final options are 'Include two CgPN IEs', 'Include one CgPN IE', or 'Include no CgPN IE', all leading to connector 'R'.
+
+**Figure A.2/Q.2730 – CLIP procedures at the destination local exchange**
+
+
+
+```
+
+graph TD
+ P1((P1)) --> P2((P2))
+ P2 --> AESA[AESA]
+ AESA --> D1{ASEA for additional calling party present?}
+ D1 -- No --> D2{Additional calling party number present?}
+ D1 -- Yes --> B1[Prepare CgPN IE to include AESA for additional calling party as received]
+ D2 -- No --> D3{AESA for calling party present?}
+ D2 -- Yes --> B2[Prepare CgPN IE to include native E.164 address embedded into AESA(E.164) format]
+ D3 -- No --> D4{Calling party number present?}
+ D3 -- Yes --> B3[Prepare CgPN IE to include AESA for calling party as received]
+ D4 -- No --> B4[Include no CgPN IE]
+ D4 -- Yes --> B5[Prepare CgPN IE to include native E.164 address embedded into AESA(E.164) format]
+ B1 --> D5{Two number delivery option?}
+ B2 --> D5
+ B3 --> D5
+ B5 --> D5
+ D5 -- No --> B3
+ D5 -- Yes --> D6{AESA for calling party present?}
+ D6 -- No --> D7{Calling party number present?}
+ D6 -- Yes --> B6[Prepare 2nd CgPn IE include AESA for calling party as received]
+ D7 -- No --> B3
+ D7 -- Yes --> B7[Prepare 2nd CgPn IE to include native E.164 address embedded into AESA(E.164) format]
+ B6 --> B8[Include two CgPN IEs]
+ B7 --> B9[Include two CgPN IEs]
+ B3 --> B10[Include one CgPN IE]
+ B5 --> B11[Include one CgPN IE]
+ B4 --> B12[Include no CgPN IE]
+ B8 --> R((R))
+ B9 --> R
+ B10 --> R
+ B11 --> R
+ B12 --> R
+ T11108650-00[T11108650-00]
+
+```
+
+Flowchart for CLIP procedures at the destination local exchange. It starts with connector P1 leading to P2, then AESA. The process involves a series of decision diamonds: 'ASEA for additional calling party present?', 'Additional calling party number present?', 'AESA for calling party present?', 'Calling party number present?', 'Two number delivery option?', and 'AESA for calling party present?'. Depending on these decisions, it leads to preparation steps for CgPN IE (including AESA or native E.164 address) or final steps: 'Include two CgPN IEs', 'Include one CgPN IE', or 'Include no CgPN IE', all leading to connector R. A reference code T11108650-00 is present.
+
+Figure A.2/Q.2730 – CLIP procedures at the destination local exchange (continued)
+
+
+
+```
+
+graph TD
+ P2((P2)) -- both --> D1{ASEA for additional calling party present?}
+ D1 -- Yes --> P1[Prepare CgPN IE to include AESA for additional calling party as received]
+ D1 -- No --> D2{Additional calling party number present?}
+ D2 -- Yes --> P2_1[Prepare CgPN IE to include Additional calling party number as received]
+ D2 -- No --> D3{AESA for calling party present?}
+ D3 -- Yes --> P3[Prepare CgPN IE to include AESA for calling party as received]
+ D3 -- No --> D4{Calling party number present?}
+ D4 -- Yes --> P4[Prepare CgPN IE to include Calling party number as received]
+ D4 -- No --> P5[Include no CgPN IE]
+ P1 --> D5{Two number delivery option?}
+ P2_1 --> D5
+ P3 --> P4
+ P4 --> P4
+ D5 -- Yes --> D6{AESA for calling party present?}
+ D5 -- No --> P4
+ D6 -- Yes --> P6[Prepare 2nd CgPN IE to include AESA for calling party as received]
+ D6 -- No --> D7{Calling party number present?}
+ D7 -- Yes --> P7[Prepare 2nd CgPN IE to include calling party number as received]
+ D7 -- No --> P4
+ P6 --> P8[Include two CgPN IEs]
+ P7 --> P9[Include two CgPN IEs]
+ P3 --> P10[Include one CgPN IE]
+ P4 --> P11[Include one CgPN IE]
+ P5 --> P12[Include no CgPN IE]
+ P8 --> R((R))
+ P9 --> R
+ P10 --> R
+ P11 --> R
+ P12 --> R
+ T11108660-00[T11108660-00]
+
+```
+
+Flowchart for CLIP procedures at the destination local exchange. It starts at node P2 and proceeds through a series of decision diamonds and process boxes to reach node R. The decisions involve checking for ASEA/AESA for additional calling parties and the calling party, and the presence of calling party numbers. The final output is either two CgPN IEs, one CgPN IE, or no CgPN IE.
+
+**Figure A.2/Q.2730 – CLIP procedures at the destination local exchange (concluded)**
+
+## ANNEX B
+
+### CLIR for non-native E.164 addresses
+
+### B.1 Definition
+
+#### B.1.1 General description
+
+See clause 4/Q.731 with the modifications listed in Table 2, and the following additions:
+
+The stage 3 DSS2 description is given in Recommendations Q.2951.4 [33] and Q.2951.9 [36]. This stage 3 description of the CLIR supplementary service uses the Broadband ISDN user part protocol as defined in Recommendations Q.2761-Q.2764.
+
+#### B.1.2 Specific terminology
+
+See clause 4/Q.731 with the modifications listed in Table 2, and the following additions and modifications:
+
+**B.1.2.1 ATM end system address:** The ATM end system address is an address that uniquely identifies an ATM endpoint (see Recommendation E.191 [37]).
+
+**B.1.2.2 native E.164 number:** See "ISDN number".
+
+**B.1.2.3 sub-address:** See Recommendation E.191 [37].
+
+**B.1.2.4 served user:** It is the user of a particular ISDN number or AESA who has subscribed to the restriction of the calling line identification information (on a permanent or on a per-call basis) in association with outgoing calls. The served user is also known as the calling user.
+
+**B.1.2.5 default number:** A national significant ISDN number or an AESA registered within the public ISDN following prior arrangement between the calling user and the public ISDN.
+
+#### B.1.3 Qualification on the applicability to telecommunication services
+
+See clause 4/Q.731 with the modifications listed in Table 2.
+
+### B.2 Description
+
+See clause 4/Q.731 with the modifications listed in Table 2.
+
+### B.3 Operational requirements
+
+See clause 4/Q.731 with the modifications listed in Table 2.
+
+### B.4 Coding requirements
+
+See A.4.
+
+### B.5 Signalling requirements
+
+See clause 4/Q.731 with the modifications listed in Table 2, and the following additions:
+
+#### B.5.1 Actions at the originating local exchange
+
+The originating local exchange shall set the address presentation restricted indicator of *the AESA for calling party* parameter and of the *AESA for additional calling party* parameter (if applicable) to the value as requested by the access signalling system of the calling user.
+
+#### **B.5.2 Actions at the outgoing international gateway exchange**
+
+Depending on bilateral agreement, the originating network may restrict the information conveyed in the *AESA for additional calling party* and/or *AESA for calling party* parameter(s) from being sent to the destination network when the CLIR supplementary service is applicable.
+
+### **B.6 Interaction with other supplementary services**
+
+See clause 4/Q.731 with the modifications listed in Table 2, and the following additions:
+
+#### **B.6.1 Calling Line Identification Restriction (CLIR)**
+
+Depending on bilateral agreement, the originating network may restrict the information conveyed in the *AESA for additional calling party* and/or *AESA for calling party* parameter from being sent to the destination network when the CLIR supplementary service is applicable.
+
+### **B.7 Interactions with other networks**
+
+See clause 4/Q.731 with the modifications listed in Table 2.
+
+### **B.8 Signalling flows**
+
+See clause 4/Q.731 with the modifications listed in Table 2.
+
+### **B.9 Parameter values (timers)**
+
+See clause 4/Q.731 with the modifications listed in Table 2.
+
+### **B.10 Dynamic description**
+
+See A.10.
+
+## **ANNEX C**
+
+## **COLP for non-native E.164 addresses**
+
+### **C.1 Definition**
+
+See clause 5/Q.731 with the modifications listed in Table 2.
+
+### **C.2 Description**
+
+#### **C.2.1 General Description**
+
+See clause 5/Q.731 with the modifications listed in Table 2, and the following additions:
+
+The stage 3 DSS2 description is given in Recommendations Q.2951.5 [34] and Q.2951.9 [36]. This stage 3 description of the COLP supplementary service uses the Broadband ISDN user part protocol as defined in Recommendations Q.2761-Q.2764.
+
+#### **C.2.2 Specific terminology**
+
+See clause 5/Q.731 with the modifications listed in Table 2, and the following additions and modifications:
+
+**C.2.2.1 ATM end system address:** The ATM end system address is an address that uniquely identifies an ATM endpoint (see Recommendation E.191 [37]).
+
+**C.2.2.2 native E.164 number:** See "ISDN number".
+
+**C.2.2.3 sub-address:** See Recommendation E.191 [37].
+
+**C.2.2.4 served user:** It is the user of a particular ISDN number or AESA who has subscribed to the presentation of the connected line identification information in association with outgoing calls. The served user is also known as the calling user.
+
+**C.2.2.5 default number:** A national significant ISDN number or an AESA registered within the public ISDN following prior arrangement between the connected user and the public ISDN.
+
+#### **C.2.3 Qualification on the applicability to telecommunication services**
+
+See clause 5/Q.731 with the modifications listed in Table 2.
+
+### **C.3 Operational requirements**
+
+See clause 5/Q.731 with the modifications listed in Table 2.
+
+### **C.4 Coding requirements**
+
+See clause 5/Q.731 with the modifications listed in Table 2, and the following additions:
+
+iii) *Coding requirements if a special arrangement does not apply*
+
+Subclause 7.12/Q.2763 gives the coding for the *AESA for connected party* parameter which is required to support this service.
+
+The purpose of the *AESA for connected party* parameter is to transport the identity of the connected user when the connected line identity is an AESA. This number may be provided by the network or by the connected user and verified by the network.
+
+iv) *Coding requirements if a special arrangement applies*
+
+Subclause 7.9/Q.2763 gives the coding for the *AESA for additional connected party* parameter which is required to support this service.
+
+The purpose of the *AESA for additional connected party* parameter is to transport an AESA connected party number provided by the connected user with a special arrangement.
+
+### **C.5 Signalling requirements**
+
+See clause 5/Q.731 with the modifications listed in Table 2, and the following additions:
+
+#### **C.5.1 Actions at the originating local exchange**
+
+The actions at the originating local exchange are specified by the SDL provided in Figure C.2, which also contains the pure native E.164 case as a special case.
+
+#### **C.5.2 Actions at the incoming international gateway exchange**
+
+The procedures of Recommendation Q.731 with respect to the handling of the *address presentation restricted indicator* shall be applied analogous to the *AESA for connected party* and *AESA for additional connected party* parameters.
+
+#### **C.5.3 Actions at the destination local exchange**
+
+The actions at the destination local exchange are specified by the SDL provided in Figure C.1, which also contains the pure native E.164 case as a special case.
+
+### **C.6 Interaction with other supplementary services**
+
+See clause 5/Q.731 with the modifications listed in Table 2.
+
+### **C.7 Interactions with other networks**
+
+ATM end system addresses are not received from or sent to ISUP networks. A broadband/narrowband interworking exchange shall discard the *AESA for connected party* and/or *AESA for additional connected party* parameter.
+
+### **C.8 Signalling flows**
+
+See clause 3/Q.731 with the modifications listed in Table 2.
+
+### **C.9 Parameter values (timers)**
+
+See clause 3/Q.731 with the modifications listed in Table 2.
+
+### **C.10 Dynamic description**
+
+The dynamic description is specified in Figures C.1 and C.2.
+
+
+
+```
+
+graph TD
+ Start([COLP supplementary service DLEX]) -- "Answer request" --> D1{Was COL requested for this call?}
+ D1 -- No --> End(( ))
+ D1 -- Yes --> D2{COL available?}
+ D2 -- No --> G1[generate Connected number with { SI := "network provided", PRI := "address not available" }]
+ D2 -- Yes --> D3{CoPN IE provided by the connected user?}
+ D3 -- Yes --> Y1((Y1))
+ D3 -- No --> A((A))
+ A --> D4{Type of default number according to subscription?}
+ D4 -- native E.164 --> G2[generate Connected number with { default number, SI := "network provided", NPI := "ISDN (Telephony)" }]
+ D4 -- AESA (E.164) --> G3[generate AESA for connected party with { default number, SI := "network provided", NPI := "AESA" }]
+ D4 -- AESA (other) --> G4[generate AESA for connected party with { default number, SI := "network provided", NPI := "AESA" }]
+ G3 --> G5[generate Connected number with { E.164 number in the IDI part of default number, SI := "network provided", NPI := "ISDN (Telephony)" }]
+ G2 --> B((B))
+ G5 --> B
+ G4 --> T11108670-00[T11108670-00]
+ T11108670-00 --> B
+ B --> G6[COLR supplementary service]
+ G6 --> End
+
+```
+
+The flowchart illustrates the COLP procedures at the destination local exchange (DLEX). It begins with an oval labeled "COLP supplementary service DLEX" with an incoming dashed line labeled "Answer request". The process then enters a decision diamond "Was COL requested for this call?". If "No", it ends at a circle with an X. If "Yes", it proceeds to "COL available?". If "No", it generates a connected number with SI := "network provided" and PRI := "address not available". If "Yes", it checks "CoPN IE provided by the connected user?". If "Yes", it ends at circle Y1. If "No", it proceeds to circle A. From circle A, it checks "Type of default number according to subscription?". This leads to three branches: "native E.164" (generates connected number with default number, SI := "network provided", NPI := "ISDN (Telephony)"), "AESA (E.164)" (generates AESA for connected party with default number, SI := "network provided", NPI := "AESA"), and "AESA (other)" (generates AESA for connected party with default number, SI := "network provided", NPI := "AESA"). The "AESA (E.164)" branch further generates a connected number with E.164 number in the IDI part of default number, SI := "network provided", NPI := "ISDN (Telephony)". All three branches lead to circle B. The "AESA (other)" branch also has a label "T11108670-00". From circle B, it proceeds to a double-bordered rectangle "COLR supplementary service", which then ends at the circle with an X.
+
+DLEX Destination Local Exchange
+ CoPN Connected Number
+ IE Information Element
+ SI Screening Indicator
+ NPI Numbering Plan Indicator
+ IDI Initial Domain Identifier
+
+Flowchart of COLP procedures at the destination local exchange (DLEX).
+
+Figure C.1/Q.2730 – COLP procedures at the destination local exchange
+
+
+
+```
+
+graph TD
+ Y1((Y1)) --> D1{Special arrangement?}
+ D1 -- Yes --> Y2((Y2))
+ D1 -- No --> D2{Screening result (acc. to number format received)?}
+ D2 -- passed --> P((P))
+ D2 -- incorrect number --> D3{National option send incorrect number}
+ D3 -- No --> A((A))
+ D3 -- Yes --> D4{Format of CoPN received?}
+ D4 -- native E.164 --> B1[generate Additional connected party number with { user provided number, SI := "user provided, verified and failed", NPI := "ISDN (Telephony)" }]
+ D4 -- AESA (E.164) --> B2[generate AESA for additional connected party with { user provided number, SI := "user provided, verified and failed", NPI := "AESA" }]
+ D4 -- AESA (other) --> B3[generate AESA for additional connected party with { user provided number, SI := "user provided, verified and failed", NPI := "AESA" }]
+ B2 --> B4[generate Additional connected party number with { E.164 number in the IDI part of user provided number, SI := "user provided, verified and failed", NPI := "ISDN (Telephony)" }]
+ B1 --> A
+ B4 --> A
+ B3 --> A
+ T11108680-00
+
+```
+
+Flowchart of COLP procedures at the destination local exchange. It starts at Y1, checks for special arrangement (Y2 if Yes), then screening result (P if passed, incorrect number if No). For incorrect number, it checks if national option is sent. If No, it goes to A. If Yes, it checks the format of CoPN received (native E.164, AESA (E.164), or AESA (other)). Each format leads to a specific 'generate' block for additional connected party number, all of which eventually lead to A. A label T11108680-00 is present near the bottom right.
+
+Figure C.1/Q.2730 – COLP procedures at the destination local exchange (continued)
+
+
+
+```
+
+graph TD
+ P((P)) --> D{Format of CoPN received?}
+ D -- native E.164 --> B1[generate Connected number with { user provided number, SI := "user provided, verified and passed", NPI := "ISDN (Telephony)" }]
+ D -- AESA (E.164) --> B2[generate AESA for connected party with { user provided number, SI := "user provided, verified and passed", NPI := "AESA" }]
+ D -- AESA (other) --> B3[generate AESA for connected party with { user provided number, SI := "user provided, verified and passed", NPI := "AESA" }]
+ B1 --> B4[generate Connected number with { E.164 number in the IDI part of user provided number, SI := "user provided, verified and passed", NPI := "ISDN (Telephony)" }]
+ B2 --> B4
+ B3 --> B4
+ B4 --> B((B))
+ T11108690-00
+
+```
+
+Flowchart of COLP procedures at the destination local exchange. It starts with a connector 'P' leading to a decision diamond 'Format of CoPN received?'. Three branches emerge: 'native E.164', 'AESA (E.164)', and 'AESA (other)'. The 'native E.164' branch leads to a box 'generate Connected number with { user provided number, SI := "user provided, verified and passed", NPI := "ISDN (Telephony)" }'. The 'AESA (E.164)' branch leads to a box 'generate AESA for connected party with { user provided number, SI := "user provided, verified and passed", NPI := "AESA" }'. The 'AESA (other)' branch leads to a box 'generate AESA for connected party with { user provided number, SI := "user provided, verified and passed", NPI := "AESA" }'. All three branches converge to a central box 'generate Connected number with { E.164 number in the IDI part of user provided number, SI := "user provided, verified and passed", NPI := "ISDN (Telephony)" }'. From this central box, an arrow points down to a connector 'B'. A label 'T11108690-00' is near the bottom right of the flow.
+
+Figure C.1/Q.2730 – COLP procedures at the destination local exchange (continued)
+
+
+
+```
+
+graph TD
+ Y2((Y2)) --> Decision{Format of CoPN received?}
+ Decision -- native E.164 --> Box1[generate Additional connected number with { user provided number, SI := "user provided, not verified", NPI := "ISDN (Telephony)"}]
+ Decision -- AESA (E.164) --> Box2[generate AESA for additional connected party with { user provided number, SI := "user provided, not verified", NPI := "AESA"}]
+ Decision -- AESA (other) --> Box3[generate AESA for additional connected party with { user provided number, SI := "user provided, not verified", NPI := "AESA"}]
+ Box1 --> Box4[generate Additional connected number with { E.164 number in the IDI part of user provided number, SI := "user provided, not verified", NPI := "ISDN (Telephony)"}]
+ Box2 --> Box4
+ Box3 --> Box4
+ Box4 --> A((A))
+ T11108700-00[T11108700-00]
+
+```
+
+Flowchart of COLP procedures at the destination local exchange. It starts with 'Y2' leading to a decision 'Format of CoPN received?'. Three branches follow: 'native E.164', 'AESA (E.164)', and 'AESA (other)'. The first branch leads to a box 'generate Additional connected number with { user provided number, SI := "user provided, not verified", NPI := "ISDN (Telephony)"}'. The second and third branches lead to boxes 'generate AESA for additional connected party with { user provided number, SI := "user provided, not verified", NPI := "AESA"}' and 'generate AESA for additional connected party with { user provided number, SI := "user provided, not verified", NPI := "AESA"}' respectively. All three boxes lead to a common box 'generate Additional connected number with { E.164 number in the IDI part of user provided number, SI := "user provided, not verified", NPI := "ISDN (Telephony)"}'. This box leads to 'A'. A label 'T11108700-00' is near the bottom right.
+
+Figure C.1/Q.2730 – COLP procedures at the destination local exchange (*concluded*)
+
+
+
+```
+
+graph TD
+ A([COLP supplementary service OLEX]) -- "Answer ind." --> B{Presentation format according to subscription?}
+ B -- "native E.164" --> P1((P1))
+ B --> C{Additional connected number present?}
+ C -- Yes --> D[Prepare CoPN IE to include Additional connected number as received]
+ C -- No --> E{Connected number present?}
+ E -- Yes --> F[Prepare CoPN IE to include Connected number as received]
+ E -- No --> G[Include no CoPN IE]
+ D --> H[Include one CoPN IE]
+ F --> H
+ H --> R((R))
+ G --> R
+ R -- "T11108710-00" --> I((X))
+
+```
+
+Flowchart of COLP procedures at the originating local exchange. The process starts with 'COLP supplementary service OLEX' (Answer ind.). It then checks 'Presentation format according to subscription?'. If 'native E.164', it goes to connector 'P1'. Next, it checks 'Additional connected number present?'. If 'Yes', it prepares 'CoPN IE to include Additional connected number as received'. If 'No', it checks 'Connected number present?'. If 'Yes', it prepares 'CoPN IE to include Connected number as received'. Both preparation steps lead to 'Include one CoPN IE'. If 'Connected number present?' is 'No', it leads to 'Include no CoPN IE'. Both 'Include one CoPN IE' and 'Include no CoPN IE' lead to connector 'R' (labeled T11108710-00), which then leads to the final connector symbol.
+
+OLEX Originating Local Exchange
+ CoPN Connected Party Number
+ IE Information Element
+ SI Screening Indicator
+ NPI Numbering Plan Indicator
+ IDI Initial Domain Identifier
+
+**Figure C.2/Q.2730 – COLP procedures at the originating local exchange**
+
+
+
+```
+
+graph TD
+ P1((P1)) --> AESA[AESA]
+ AESA --> P2((P2))
+ AESA --> D1{ASEA for additional connected party present?}
+ D1 -- Yes --> P1a[Prepare CoPN IE to include AESA for additional connected party as received]
+ D1 -- No --> D2{Additional connected number present?}
+ D2 -- Yes --> P2a[Prepare CoPN IE to include native E.164 address embedded info AESA (E.164) format]
+ D2 -- No --> D3{AESA for connected party present?}
+ D3 -- Yes --> P3a[Prepare CoPN IE to include AESA for connected party as received]
+ D3 -- No --> D4{Connected number present?}
+ D4 -- Yes --> P4a[Prepare CoPN IE to include native E.164 address embedded info AESA (E.164) format]
+ D4 -- No --> P5a[Include no CoPN IE]
+ P1a --> P1b[Include one CoPN IE]
+ P2a --> P2b[Include one CoPN IE]
+ P3a --> P3b[Include one CoPN IE]
+ P4a --> P5a
+ P1b --> R((R))
+ P2b --> R
+ P3b --> R
+ P5a --> R
+ T11108720-00[T11108720-00]
+
+```
+
+Flowchart of COLP procedures at the originating local exchange. It starts with P1 leading to AESA, which then leads to P2. The main decision path starts with 'ASEA for additional connected party present?'. If Yes, it leads to 'Prepare CoPN IE to include AESA for additional connected party as received', which then leads to 'Include one CoPN IE'. If No, it asks 'Additional connected number present?'. If Yes, it leads to 'Prepare CoPN IE to include native E.164 address embedded info AESA (E.164) format', which then leads to 'Include one CoPN IE'. If No, it asks 'AESA for connected party present?'. If Yes, it leads to 'Prepare CoPN IE to include AESA for connected party as received', which then leads to 'Include one CoPN IE'. If No, it asks 'Connected number present?'. If Yes, it leads to 'Prepare CoPN IE to include native E.164 address embedded info AESA (E.164) format', which then leads to 'Include no CoPN IE'. If No, it also leads to 'Include no CoPN IE'. All three 'Include' options lead to a common path ending at R. The text T11108720-00 is at the bottom right.
+
+Figure C.2/Q.2730 – COLP procedures at the originating local exchange (continued)
+
+
+
+```
+
+graph TD
+ P2((P2)) -- both --> D1{ASEA for additional connected party present?}
+ D1 -- Yes --> P1[Prepare CoPN IE to include AESA for additional connected party as received]
+ D1 -- No --> D2{Additional connected number present?}
+ D2 -- Yes --> P2[Prepare CoPN IE to include Additional connected number as received]
+ D2 -- No --> D3{AESA for connected party present?}
+ D3 -- Yes --> P3[Prepare CoPN IE to include AESA for connected party as received]
+ D3 -- No --> D4{Connected number present?}
+ D4 -- Yes --> P4[Prepare CoPN IE to include Connected number as received]
+ D4 -- No --> P5[Include no CoPN IE]
+ P1 --> P6[Include one CoPN IE]
+ P2 --> P6
+ P3 --> P7[Include one CoPN IE]
+ P4 --> P7
+ P5 --> P8[Include no CoPN IE]
+ P6 --> R((R))
+ P7 --> R
+ P8 --> R
+ T11108730-00
+
+```
+
+Flowchart for COLP procedures at the originating local exchange. It starts at connector P2, proceeds through a series of decision diamonds: 'ASEA for additional connected party present?', 'Additional connected number present?', 'AESA for connected party present?', and 'Connected number present?'. Depending on the 'Yes' or 'No' answers, it leads to preparation steps for CoPN IE (including AESA, additional connected number, or connected number) or directly to 'Include one CoPN IE' or 'Include no CoPN IE'. All paths converge to connector R. The identifier T11108730-00 is present near the bottom right.
+
+Figure C.2/Q.2730 – COLP procedures at the originating local exchange (*concluded*)
+
+## ANNEX D
+
+## COLR for non-native E.164 addresses
+
+### D.1 Definition
+
+See clause 6/Q.731 with the modifications listed in Table 2.
+
+### D.2 Description
+
+#### D.2.1 General Description
+
+See clause 6/Q.731 with the modifications listed in Table 2, and the following additions:
+
+The stage 3 DSS2 description is given in Recommendations Q.2951.6 [35] and Q.2951.9 [36]. This stage 3 description of the COLR supplementary service uses the Broadband ISDN user part protocol as defined in Recommendations Q.2761-Q.2764.
+
+#### D.2.2 Specific terminology
+
+See clause 6/Q.731 with the modifications listed in Table 2, and the following additions and modifications:
+
+**D.2.2.1 ATM end system address:** The ATM end system address is an address that uniquely identifies an ATM endpoint (see Recommendation E.191 [37]).
+
+**D.2.2.2 native E.164 number:** See "ISDN number".
+
+**D.2.2.3 sub-address:** See Recommendation E.191 [37].
+
+**D.2.2.4 served user:** It is the user of a particular ISDN number or AESA who has subscribed to the restriction of the connected line identification information (on a permanent or on a per-call basis) in association with incoming calls. The served user is also known as the connected user.
+
+**D.2.2.5 default number:** A national significant ISDN number or an AESA registered within the public ISDN following prior arrangement between the connected user and the public ISDN.
+
+#### D.2.3 Qualification on the applicability to telecommunication services
+
+See clause 6/Q.731 with the modifications listed in Table 2.
+
+### D.3 Operational requirements
+
+See clause 6/Q.731 with the modifications listed in Table 2.
+
+### D.4 Coding requirements
+
+See C.4.
+
+### D.5 Signalling requirements
+
+See clause 6/Q.731 with the modifications listed in Table 2, and the following additions:
+
+#### D.5.1 Actions at the incoming international gateway exchange
+
+Depending on bilateral agreement, the originating network may restrict the information conveyed in the *AESA for additional connected party* and/or *AESA for connected party* parameter(s) from being sent to the originating network when the COLR supplementary service is applicable.
+
+#### **D.5.2 Actions at the destination local exchange**
+
+The destination local exchange shall set the address presentation restricted indicator of *the AESA for connected party* parameter and of the *AESA for additional connected party* parameter (if applicable) to the value as requested by the access signalling system of the connected user.
+
+### **D.6 Interaction with other supplementary services**
+
+See clause 6/Q.731 with the modifications listed in Table 2.
+
+### **D.7 Interactions with other networks**
+
+See clause 6/Q.731 with the modifications listed in Table 2.
+
+### **D.8 Signalling flows**
+
+See clause 6/Q.731 with the modifications listed in Table 2.
+
+### **D.9 Parameter values (timers)**
+
+See clause 6/Q.731 with the modifications listed in Table 2.
+
+### **D.10 Dynamic description**
+
+See C.10.
+
+# APPENDIX I
+
+## Setting of instruction indicators
+
+The setting of the instruction indicators is as follows:
+
+| Parameter | Pass on not possible indicator | Discard parameter indicator | Discard message indicator | Send notification indicator | Release call indicator | Transit at intermediate exchange indicator | Broadband/narrow-band interworking indicator |
+|-------------------------------------|--------------------------------|-----------------------------|---------------------------|-----------------------------|------------------------|--------------------------------------------|----------------------------------------------|
+| AESA for calling party | Discard | Do not discard | Do not discard message | Do not send notification | Do not release call | Transit node interpretation | Discard |
+| Additional calling party number | Discard | Do not discard | Do not discard message | Do not send notification | Do not release call | Transit node interpretation | Pass on |
+| Additional connected number | Discard | Do not discard | Do not discard message | Do not send notification | Do not release call | Transit node interpretation | Pass on |
+| AESA for additional calling party | Discard | Do not discard | Do not discard message | Do not send notification | Do not release call | Transit node interpretation | Discard |
+| AESA for additional connected party | Discard | Do not discard | Do not discard message | Do not send notification | Do not release call | Transit node interpretation | Discard |
+| AESA for connected party | Discard | Do not discard | Do not discard message | Do not send notification | Do not release call | Transit node interpretation | Discard |
+| Calling party number | Discard | Do not discard | Do not discard message | Do not send notification | Do not release call | Transit node interpretation | Pass on |
+| Connected number | Discard | Do not discard | Do not discard message | Do not send notification | Do not release call | Transit node interpretation | Pass on |
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression: definitions, symbols, classification
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Overall network operation, telephone service, service operation and human factors
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media, digital systems and networks
+- Series H Audiovisual and multimedia systems
+- Series I Integrated services digital network
+- Series J Transmission of television, sound programme and other multimedia signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality, telephone installations, local line networks
+- Series Q Switching and signalling**
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminals for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communications
+- Series Y Global information infrastructure and Internet protocol aspects
+- Series Z Languages and general software aspects for telecommunication systems
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ae902633df494448a72c1a5e0759a69001b4199
--- /dev/null
+++ b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/0236eff05bcb8f3a343ea7933aaa306b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d75e5c340f4b3785e19fcca9bb460882861b4facc73cdc1ea6f187caafddf1de
+size 28064
diff --git a/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d84886c7965d7e4dbdbfc5562e72f33c119c9ecf
--- /dev/null
+++ b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff34b1c23128111a15e6e335050c83320b894a92e59c34f28d035157ae49bc94
+size 60483
diff --git a/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..548413745b4d98c653d31c63962591b02de03f92
--- /dev/null
+++ b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:17406d74d7ebb46734a24b04abc40f7b6896f5c51ae5b230a11d81d12377be37
+size 8372
diff --git a/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7691e98962b0f46754394d5d6bf2997f59ac1b4a
--- /dev/null
+++ b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32a4aa1861e60f4bb27b3d418d91282d8a441a004b66a41e04ffd6295b979af8
+size 27286
diff --git a/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c5081fd903d3e7dcf788b28e39302e784be7083b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2767.1-200006-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4fe51e26f06458b6b14ca8f563e4c77099d46221720e4a56221878bb3f7b8765
+size 26333
diff --git a/marked/Q/T-REC-Q.2931-199502-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..32af43f4d9ae22f19579e53402cbb4fc0320dc86
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931-199502-I_PDF-E/raw.md
@@ -0,0 +1,9435 @@
+
+
+
+
+ITU logo: A globe with the letters ITU and a lightning bolt.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.2931**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(02/95)
+
+# **B-ISDN APPLICATION PROTOCOLS FOR ACCESS SIGNALLING** ---
+
+**BROADBAND INTEGRATED SERVICES
+DIGITAL NETWORK (B-ISDN) – DIGITAL
+SUBSCRIBER SIGNALLING SYSTEM No. 2
+(DSS 2) – USER-NETWORK INTERFACE (UNI)
+LAYER 3 SPECIFICATION FOR BASIC
+CALL/CONNECTION CONTROL**
+
+**ITU-T Recommendation Q.2931**
+
+(Previously "CCITT Recommendation")
+
+---
+
+# FOREWORD
+
+The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993).
+
+ITU-T Recommendation Q.2931 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 7th of February 1995.
+
+---
+
+## NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+*Page*
+
+| | | |
+|-----|------------------------------------------------------------------------------------------------------------------------------------------------------|-----|
+| 1 | Scope..... | 1 |
+| 1.1 | Definitions, abbreviations and references..... | 1 |
+| 1.2 | Application to interface structure ..... | 1 |
+| 1.3 | Capabilities supported by this Recommendation..... | 1 |
+| 2 | Overview of call/connection control ..... | 5 |
+| 2.1 | B-ISDN call/connection states..... | 5 |
+| 2.2 | Additional B-ISDN call/connection states relating to interworking requirements ..... | 6 |
+| 2.3 | B-ISDN call/connection states for global call reference..... | 6 |
+| 3 | Message functional definitions and content ..... | 7 |
+| 3.1 | Messages for B-ISDN call and connection control..... | 8 |
+| 3.2 | Additional or modified messages related for the support of 64 kbit/s based ISDN circuit-mode services ..... | 16 |
+| 3.3 | Messages used with the global call reference ..... | 25 |
+| 4 | General message format and information elements coding..... | 27 |
+| 4.1 | Overview ..... | 27 |
+| 4.2 | Protocol discriminator..... | 28 |
+| 4.3 | Call reference..... | 28 |
+| 4.4 | Message type, and message length ..... | 32 |
+| 4.5 | Variable length information elements for B-ISDN environment..... | 34 |
+| 4.6 | Information elements for the support of 64 kbit/s based ISDN circuit-mode services ..... | 79 |
+| 5 | B-ISDN call/connection control procedures ..... | 81 |
+| 5.1 | Call/connection establishment at the originating interface ..... | 82 |
+| 5.2 | Call/connection establishment at the destination interface – Point-to-point access configuration call offering..... | 86 |
+| 5.3 | Call/connection establishment at the destination – Point-to-multipoint access arrangement call offering..... | 90 |
+| 5.4 | Call/connection clearing ..... | 90 |
+| 5.5 | Restart procedure ..... | 91 |
+| 5.6 | Handling of error conditions..... | 94 |
+| 5.7 | Error procedures with explicit action indication..... | 99 |
+| 5.8 | Handling of messages with insufficient information ..... | 100 |
+| 5.9 | Notification procedures ..... | 101 |
+| 6 | Procedures for the support of 64 kbit/s based circuit-mode ISDN services in B-ISDN and access signalling interworking between N-ISDN and B-ISDN..... | 101 |
+| 6.1 | Introduction ..... | 101 |
+| 6.2 | Information elements for N-ISDN services in B-ISDN..... | 102 |
+| 6.3 | Interworking N-ISDN → B-ISDN..... | 104 |
+| 6.4 | Interworking B-ISDN → N-ISDN..... | 105 |
+| 6.5 | Overlap sending and receiving ..... | 106 |
+| 6.6 | Notification of interworking..... | 108 |
+| 6.7 | Additional features with regard to the provision of N-ISDN services..... | 109 |
+| 7 | List of timers ..... | 110 |
+| 7.1 | Timers in the network side..... | 110 |
+| 7.2 | Timers in the user side..... | 110 |
+
+| | Page |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| 8 Primitives ..... | 115 |
+| 8.1 Introduction ..... | 115 |
+| 8.2 Description of the primitives ..... | 115 |
+| Annex A – Network side and user side SDL diagrams ..... | 118 |
+| A.1 Network side SDL diagrams..... | 118 |
+| A.2 User side SDL diagramas ..... | 163 |
+| Annex B – Compatibility checking ..... | 207 |
+| B.1 Introduction ..... | 207 |
+| B.2 Calling side compatibility checking..... | 207 |
+| B.3 Called side compatibility and address checking ..... | 207 |
+| Annex C – Broadband low layer information negotiation..... | 208 |
+| C.1 General..... | 208 |
+| C.2 Low layer compatibility notification to the called user ..... | 209 |
+| C.3 B-LLI negotiation between users..... | 209 |
+| C.4 Alternate requested values ..... | 209 |
+| Annex D – Transit network selection ..... | 210 |
+| D.1 Selection not supported..... | 210 |
+| D.2 Selection supported..... | 210 |
+| Annex E – Mapping functions to support 64 kbit/s based circuit-mode ISDN services in B-ISDN and interworking between N-ISDN and B-ISDN (DSS 1/DSS 2) ..... | 211 |
+| E.1 Introduction ..... | 211 |
+| E.2 Mapping functions for the direction DSS 2 → DSS 1 ..... | 211 |
+| E.3 Mapping functions for the direction DSS 1 → DSS 2 ..... | 214 |
+| E.4 Codepoint values of information elements to support 64 kbit/s based circuit-mode ISDN services in B-ISDN..... | 216 |
+| Annex F – ATM adaptation layer parameters indication and negotiation..... | 218 |
+| F.1 General..... | 218 |
+| F.2 ATM adaptation layer parameter indication in the SETUP message..... | 219 |
+| F.3 Maximum CPCS-SDU size negotiation..... | 219 |
+| F.4 MID range negotiation..... | 220 |
+| F.5 Use of forward and backward maximum CPCS-SDU size by the AAL entity in the user plane .... | 220 |
+| Annex G ..... | 220 |
+| Annex H – Extensions for symmetric call operation ..... | 221 |
+| Annex I – Handling of the OAM traffic descriptor ..... | 221 |
+| I.1 Use of the OAM traffic descriptor information element..... | 221 |
+| I.2 Handling of the OAM traffic descriptor information element in the SETUP message ..... | 221 |
+| I.3 Procedure at the destination user-network interface ..... | 222 |
+| Annex J – Definitions, Abbreviations and References ..... | 222 |
+| J.1 Definitions ..... | 222 |
+| J.2 Abbreviations..... | 226 |
+| J.3 References..... | 227 |
+| Annex K – Handling of the End-to-end transit delay information element..... | 229 |
+| K.1 General..... | 229 |
+| K.2 Handling of the End-to-end transit delay information element in the SETUP message at the originating UNI..... | 230 |
+| K.3 Handling of the End-to-end transit delay information element in the SETUP message at the destination UNI..... | 230 |
+
+| | Page |
+|-------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|
+| K.4 | Handling of the End-to-end transit delay information element by the called user ..... 230 |
+| K.5 | Handling of the End-to-end transit delay information element in the CONNECT message at the destination UNI..... 231 |
+| K.6 | Handling of the End-to-end transit delay information element in the CONNECT message at the originating UNI..... 231 |
+| Annex L – Examples for Message Structure and Information Element Format..... | 231 |
+| L.1 | Introduction ..... 231 |
+| L.2 | Structure using of an information subfield identifiers ..... 231 |
+| L.3 | The ordering of information elements ..... 233 |
+| Appendix I – Guidelines for the use of Instruction indicators ..... | 234 |
+| Appendix II – Information items for connection establishment in B-ISDN..... | 236 |
+| II.1 | Scope ..... 236 |
+| II.2 | Information items specified by the calling terminal ..... 236 |
+| Appendix III – Status monitoring procedures for Semi-Permanent Virtual Channel Connections..... | 238 |
+| III.1 | Messages used for SPC status..... 239 |
+| III.2 | General information elements..... 240 |
+| III.3 | Other information elements ..... 242 |
+| III.4 | Procedures across the UNI..... 243 |
+| III.5 | Error conditions ..... 247 |
+| III.6 | System timers..... 247 |
+| III.7 | System parameters ..... 247 |
+
+# **SUMMARY**
+
+This Recommendation specifies the procedures for the establishing, maintaining and clearing of network connections at the B-ISDN user network interface. The procedures are defined in terms of messages exchanged.
+
+This Recommendation is intended to specify the essential features, procedures and messages required for call/connection control. However, there are some details of procedure which have not yet been specified, and which will be subject to further study.
+
+## **BROADBAND INTEGRATED SERVICES DIGITAL NETWORK (B-ISDN) – DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 2 (DSS 2) – USER-NETWORK INTERFACE (UNI) LAYER 3 SPECIFICATION FOR BASIC CALL/CONNECTION CONTROL**
+
+*(Geneva, 1995)*
+
+# **1 Scope**
+
+This Recommendation specifies the procedures for the establishing, maintaining, and clearing of network connections at the B-ISDN user-network interface. The procedures are defined in terms of messages exchanged.
+
+This Recommendation is intended to specify the essential features, procedures and messages required for call/connection control.
+
+This Recommendation specifies the layer 3 call/connection states, messages, information elements, timers and procedures used for the control of B-ISDN point-to-point on-demand calls on virtual channels within the overall scope of Release 1 of B-ISDN as specified in Recommendation Q.2010.
+
+The procedures specified by this Recommendation are applied at the interface between a B-ISDN terminal equipment and a B-ISDN public network (reference point SB and TB coincident) as well as at the interface between a B-ISDN customer network and a B-ISDN public network (i.e. at the TB reference point).
+
+Other Recommendations may use additional messages, additional operations (using Facility information element), additional information elements and/or modification of existing information elements to support additional capabilities in DSS 2.
+
+## **1.1 Definitions, abbreviations and references**
+
+These are provided in Annex J.
+
+## **1.2 Application to interface structure**
+
+The layer 3 procedures apply to the interface structures defined in Recommendation I.413. They use the functions and services provided by layer 2. The layer 3 procedures request the services of layer 2 and receive information from layer 2 using the primitives defined in Recommendation Q.2130. These primitives are used to illustrate the communication between the protocol layers and are not intended to specify or constrain implementations.
+
+## **1.3 Capabilities supported by this Recommendation**
+
+The basic capabilities supported by the Release 1 Signalling specified in this Recommendation are listed below:
+
+- 1) Demand (switched virtual) channel connections.
+- 2) Point-to-point switched channel connections.
+- 3) Connections with symmetric or asymmetric bandwidth requirements.
+- 4) Single-connection (point-to-point) calls.
+- 5) Basic signalling functions via protocol messages, information elements and procedures.
+- 6) Class X, Class A and Class C ATM transport services.
+- 7) Request and indication of signalling parameters.
+
+- 8) VCI negotiation.
+- 9) Out-of-band signalling for all signalling messages.
+- 10) Error recovery.
+- 11) Public UNI addressing formats for unique identification of ATM endpoints.
+- 12) End-to-end compatibility parameter identification.
+- 13) Signalling interworking with N-ISDN and provision of N-ISDN services.
+- 14) Forward compatibility.
+
+The following subclauses describe each capability in more detail.
+
+### 1.3.1 Support of demand (switched) channel connections
+
+The purpose of this specification is to support on-demand (switched) channel connections. These connections are established in real-time using signalling procedures. Demand connections can remain active for an arbitrary amount of time but would not automatically be re-established after a network failure.
+
+In contrast, permanent connections are those that are set up and torn down via provisioning. Permanent connections generally remain established for long periods of time and should automatically be re-established in the event of network failure.
+
+### 1.3.2 Support of point-to-point connections
+
+A point-to-point connection is a collection of associated ATM virtual channel (VC) or virtual path (VP) links that connect two endpoints. The Release 1 Signalling specified in this Recommendation supports point-to-point virtual channel (VC) connections.
+
+### 1.3.3 Support of connections with symmetric or asymmetric bandwidth
+
+The Release 1 Signalling specified in this Recommendation supports point-to-point, bidirectional connections that have bandwidth specified independently in the forward and backward directions. The forward direction is from the calling party to the called party, while the backward direction is from the called party to the calling party.
+
+### 1.3.4 Support of a single connection per call
+
+The Release 1 Signalling specified in this Recommendation will support one and only one connection per call.
+
+### 1.3.5 Protocol support for basic signalling functions
+
+The signalling protocol supports the following basic functions at the UNI interface:
+
+- *Call/Connection Set-up*
+
+This is the aspect of the protocol which supports the establishment of a call/connection between different parties. It includes Call/Connection Request and Call/Connection Answer.
+
+- *Call/Connection Request*
+
+This protocol function allows an originating party to request the establishment of a call/connection to a certain destination. In this request, the originating party may provide information related to the call/connection.
+
+- *Call/Connection Answer*
+
+This protocol function allows the destination party to respond to an incoming call/connection request. The destination party may include information related to the call/connection (rejecting the call/connection request is considered part of the Call/Connection Clearing function).
+
+- *Call/Connection Clearing*
+
+This protocol function allows any party involved in a call/connection to initiate its removal from an already established call/connection. This function also allows a destination party to reject its inclusion in a call/connection.
+
+- *Reason for Clearing*
+
+This protocol function allows the clearing party to indicate the cause for initiating its removal from a call/connection.
+
+- *Out-of-Band Signalling*
+
+This function specifies that call/connection control information uses a channel different from the channels used for exchanging data information between the end-parties (i.e. a specific VPCI/VCI value will be used for the call/connection control signalling channel).
+
+### 1.3.6 Support of Class A, Class C and Class X (see Recommendation I.211)
+
+Class A service is a connection-oriented, constant bit rate ATM transport service. Class A service has end-to-end timing requirements. Class A service may require stringent cell loss, cell delay and cell delay variation performance. The user chooses the desired bandwidth and the appropriate QOS in the SETUP message to establish a Class A connection.
+
+Class C service is a connection-oriented variable bit rate (see Note) ATM transport service. Class C service has no end-to-end timing requirements. The user chooses the desired bandwidth and QOS with appropriate information elements in a SETUP message to establish a Class C connection.
+
+NOTE – For Bearer Class C, the network may allocate resources, as if Bearer Class A was requested.
+
+Class X service is a connection-oriented ATM transport service where the AAL, traffic type (VBR or CBR) and timing requirements are user defined (i.e. transparent to the network). The user chooses only the desired bandwidth and QOS with appropriate information elements in a SETUP message to establish a Class X connection.
+
+#### 1.3.7 Support of signalling parameter request and indication
+
+The Release 1 Signalling specified in this supports for the negotiation of some signalling parameters (e.g. B-LLI, AAL parameters).
+
+### 1.3.8 VPCI/VCI support
+
+The Release 1 Signalling specified in this Recommendation supports the VPCI as the way of identifying the virtual path across the UNI, with a restriction that there is a one-to-one mapping between VPCI and VPI.
+
+The following list describes the Release 1 Signalling capabilities with respect to VPCI and VCIs. The Release 1 Signalling specified in this Recommendation:
+
+- 1) provides for the identification of virtual path connections (using VPCIs) and virtual channel connections within virtual paths (using VCIs);
+- 2) includes negotiation of VCIs.
+
+### 1.3.9 Out-of-band signalling
+
+VCI = 5 is reserved in every VPCI for the point-to-point signalling in Release 1. Meta-signalling is not supported in Release 1. (See Recommendation I.311 for the establishment of the association of signalling entities in absence of meta-signalling.) The broadcast signalling virtual channels are not supported.
+
+### 1.3.10 Support of error recovery
+
+The error recovery capabilities of the Release 1 Signalling specified in this Recommendation include:
+
+- 1) Detailed error handling procedures, including means for one signalling entity to inform its peer when it has encountered a non-fatal error (i.e. insufficiently severe to force call clearing); examples of non-fatal errors are message format errors, message content errors and procedural errors (e.g. messages or message contents received in a state in which they are not expected).
+
+- 2) Procedures for recovery from signalling AAL reset and failure (and, by extension, from Physical layer outages and glitches).
+- 3) Mechanisms for signalling entities to exchange state information for calls and interfaces, and to recover gracefully if there is a disagreement; these procedures must operate both in error conditions as a side-effect of 1) and on request by either signalling entity (i.e. status enquiry).
+- 4) Capability to force calls, VCCs, and interfaces to an idle state, either due to manual intervention or as a result of server errors.
+- 5) Cause and diagnostic information for fault resolution provided with call clearing (see 5.1.3), non-fatal errors, and recovery from errors affecting the whole interface.
+- 6) Mechanisms (e.g. timers and associated procedures) to recover from loss of individual messages.
+
+#### **1.3.11 Support of public UNI ATM addressing**
+
+The Release 1 Signalling specified in this Recommendation supports a number of ATM address formats to be used across the Public UNI to unambiguously identify the endpoints in an ATM connection.
+
+### **1.3.12 Support of end-to-end compatibility parameter identification**
+
+On a per-connection basis, the following end-to-end compatibility parameters can be specified:
+
+- 1) The AAL type (e.g. Types 1, 3/4, or 5).
+- 2) The method of protocol multiplexing (e.g. LLC vs. VC) and AAL parameter.
+- 3) For VC-based multiplexing, the protocol which is encapsulated (e.g. any of the list of known routed protocols or bridged protocols).
+- 4) Protocols above the network layer.
+
+### **1.3.13 Signalling interworking with N-ISDN and provision of N-ISDN services**
+
+The Release 1 Signalling supports interworking with N-ISDN. At the same time, signalling is specified to support N-ISDN services in a B-ISDN environment.
+
+The following are the underlying assumptions:
+
+- 1) B-ISDN should be able to provide N-ISDN services.
+- 2) The originator/originating network does not know whether a call requesting a N-ISDN service will terminate on a N-ISDN or a B-ISDN network. (Only the requested service is known, e.g. 64 kbit/s unrestricted digital information, not the protocols supported by intervening networks.)
+- 3) Signalling interworking should be as simple as possible. Complex protocol conversions should be avoided.
+
+Consequently N-ISDN services in a B-ISDN environment obey the following rules:
+
+- 1) Information items that have end-to-end significance should be indicated using the narrow-band versions and not the broadband versions. Examples: N-HLC, N-LLC (and not B-HLI, B-LLI).
+- 2) Information items that have global significance about the requested service should be indicated using both the narrow-band and the broadband version. Example: N-BC and B-BC.
+
+Clause 6 and Annex E contain the N-ISDN service provision and interworking procedures.
+
+### **1.3.14 Forward compatibility**
+
+To support forward compatibility in the signalling protocol, a mechanism based on instruction indicators is specified in this Recommendation. This mechanism applies to both messages and information elements.
+
+## 2 Overview of call/connection control
+
+In this Recommendation, the terms “incoming” and “outgoing” are used to describe the Broadband ISDN call as viewed by the user side of the interface.
+
+This clause defines B-ISDN call/connection control states that individual calls may have. These definitions do not apply to the state of the interface itself, any attached equipment, or the Signalling virtual channel. Because several B-ISDN calls/connections may exist simultaneously at a user-network interface, and each call/connection may be in a different state, the state of the interface itself cannot be unambiguously defined.
+
+## 2.1 B-ISDN call/connection states
+
+This subclause defines the call/connection control states for B-ISDN calls.
+
+### 2.1.1 Call/connection states at the user side of the interface
+
+The states which may exist on the user side of the user-network interface are defined in this subclause.
+
+**2.1.1.1 null (U0):** No call exists.
+
+**2.1.1.2 call initiated (U1):** This state exists for an outgoing call when the user requests call establishment from the network.
+
+**2.1.1.3 outgoing call proceeding (U3):** This state exists for an outgoing call when the user has received acknowledgement that the network has received all call information necessary to effect call establishment.
+
+**2.1.1.4 call delivered (U4):** This state exists for an outgoing call when the calling user has received an indication that remote user alerting has been initiated.
+
+**2.1.1.5 call present (U6):** This state exists for an incoming call when the user has received a call establishment request but has not yet responded.
+
+**2.1.1.6 call received (U7):** This state exists for an incoming call when the user has indicated alerting but has not yet answered.
+
+**2.1.1.7 connect request (U8):** This state exists for an incoming call when the user has answered the call and is waiting to be awarded the call.
+
+**2.1.1.8 incoming call proceeding (U9):** This state exists for an incoming call when the user has sent acknowledgement that the user has received all call information necessary to effect call establishment.
+
+**2.1.1.9 active (U10):** This state exists for an incoming call when the user has received an acknowledgement from the network that the user has been awarded the call. This state exists for an outgoing call when the user has received an indication that the remote user has answered the call.
+
+**2.1.1.10 release request (U11):** This state exists when the user has requested the network to clear the end-to-end connection (if any) and is waiting for a response.
+
+**2.1.1.11 release indication (U12):** This state exists when the user has received an invitation to disconnect because the network has disconnected the end-to-end connection (if any).
+
+### 2.1.2 Call/connection states at the network side of the interface
+
+The states that may exist on the network side of the user-network interface are defined in this subclause.
+
+**2.1.2.1 null (N0):** No call exists.
+
+**2.1.2.2 call initiated (N1):** This state exists for an outgoing call when the network has received a call establishment request but has not yet responded.
+
+**2.1.2.3 outgoing call proceeding (N3):** This state exists for an outgoing call when the network has sent acknowledgement that the network has received all call information necessary to effect call establishment.
+
+**2.1.2.4 call delivered (N4):** This state exists for an outgoing call when the network has indicated that remote user alerting has been initiated.
+
+**2.1.2.5 call present (N6):** This state exists for an incoming call when the network has sent a call establishment request but not yet received a satisfactory response.
+
+**2.1.2.6 call received (N7):** This state exists for an incoming call when the network has received an indication that the user is alerting but has not yet received an answer.
+
+**2.1.2.7 connect request (N8):** This state exists for an incoming call when the network has received an answer but the network has not yet awarded the call.
+
+**2.1.2.8 incoming call proceeding (N9):** This state exists for an incoming call when the network has received acknowledgement that the user has received all call information necessary to effect call establishment.
+
+**2.1.2.9 active (N10):** This state exists for an incoming call when the network has awarded the call to the called user. This state exists for an outgoing call when the network has indicated that the remote user has answered the call.
+
+**2.1.2.10 release request (N11):** This state exists when the network has received a request from the user to clear the end-to-end connection (if any).
+
+**2.1.2.11 release indication (N12):** This state exists when the network has disconnected the end-to-end connection (if any) and has sent an invitation to disconnect the user-network connection.
+
+## **2.2 Additional B-ISDN call/connection states relating to interworking requirements**
+
+This subclause defines the additional call/connection control states for B-ISDN calls relating to interworking requirements.
+
+### **2.2.1 Call/connection states at the user side of the interface**
+
+The states which may exist on the user side of the user-network interface are defined in this subclause.
+
+**2.2.1.1 overlap sending (U2):** This state exists for an outgoing call when the user has received acknowledgement of the call establishment request which permits the user to send additional call information to the network in overlap mode.
+
+**2.2.1.2 overlap receiving (U25):** This state exists for an incoming call when the user has acknowledged the call establishment request from the network and is prepared to receive additional call information (if any) in overlap mode.
+
+### **2.2.2 Call/connection states at the network side of the interface**
+
+The states that may exist on the network side of the user-network interface are defined in this subclause.
+
+**2.2.2.1 overlap sending (N2):** This state exists for an outgoing call when the network has acknowledged the call establishment request and is prepared to receive additional call information (if any) in overlap mode.
+
+**2.2.2.2 overlap receiving (N25):** This state exists for an incoming call when the network has received acknowledgement request which permits the network to send additional call information (if any) in the overlap mode.
+
+## **2.3 B-ISDN call/connection states for global call reference**
+
+This subclause defines the states that the protocol may adopt using the global call reference. The procedures for use of the global call reference for the RESTART message are contained in 5.5.
+
+There is only one global call reference value per signalling virtual channel.
+
+### 2.3.1 Call/connection states at the user side of the interface
+
+The states which may exist on the user side of the user network interface are defined in this subclause.
+
+**2.3.1.1 null (Rest 0):** No transaction exists.
+
+**2.3.1.2 restart request (Rest 1):** This state exists for a restart transaction when the user has sent a restart request but has not yet received an acknowledgement response from the network.
+
+**2.3.1.3 restart (Rest 2):** This state exists when a request for a restart has been received from the network and responses have not yet been received from all locally active call references.
+
+### 2.3.2 Call/connection states at the network side of the interface
+
+The states which may exist on the network side of the user-network interface are defined in this subclause.
+
+**2.3.2.1 null (Rest 0):** No transaction exists.
+
+**2.3.2.2 restart request (Rest 1):** This state exists for a restart transaction when the network has sent a restart request but has not yet received an acknowledgement response from the user.
+
+**2.3.2.3 restart (Rest 2):** This state exists when a request for a restart has been received from the user and a response has not yet been received from all locally active call references.
+
+## 3 Message functional definitions and content
+
+This clause provides an overview of the message structure, which highlights the functional definition and information content (i.e. semantics) of each message. Each definition includes:
+
+- 1) A brief description of the message direction and use, including whether the message has:
+ - a) local significance, i.e. relevant only in the originating or terminating access;
+ - b) access significance, i.e. relevant in the originating and terminating access, but not in the network;
+ - c) dual significance, i.e. relevant in either the originating or terminating access and in the network; or,
+ - d) global significance, i.e. relevant in the originating and terminating access and in the network.
+- 2) A table listing the codeset 0 information elements. For each information element, the table indicates:
+ - a) the reference of this Recommendation describing the information element;
+ - b) the direction in which it may be sent; i.e. user to network ("u → n"), network to user ("n → u"), or both;
+
+NOTE 1 – The user-network terminology in this clause refers to the interface structures between B-ISDN terminal equipment and B-ISDN public network (TE – LCRF), and between B-ISDN customer network and B-ISDN public network (CN – LCRF); the terms TE, CN and LCRF being used as defined in Recommendation I.327.
+
+- c) whether inclusion is mandatory ("M") or optional ("O"), with a reference to Notes explaining the circumstances under which the information element shall be included; and
+ - d) the length of the information element (or permissible range of lengths), in octets, where "\*" denotes an undefined maximum length, which may be network or service dependent.
+- 3) Further explanatory Notes, as necessary.
+
+NOTE 2 – All messages may contain information elements from codesets 4, 5, 6 and 7 and corresponding Broadband locking shift and Broadband non-locking shift information elements which comply with the coding rules specified in 4.5.2 to 4.5.4. None of these information elements, however, are listed in clause 3.
+
+NOTE 3 – The notification indicator information element may be repeated in a message. The maximum length and the number of repetitions allowed is a network option.
+
+## 3.1 Messages for B-ISDN call and connection control
+
+Table 3-1 summarizes the messages for B-ISDN call or connection control.
+
+TABLE 3-1/Q.2931
+**Messages for B-ISDN call and connection control**
+
+| Message | Reference |
+|------------------------------|-----------|
+| Call establishment messages: | |
+| ALERTING | 3.1.1 |
+| CALL PROCEEDING | 3.1.2 |
+| CONNECT | 3.1.3 |
+| CONNECT ACKNOWLEDGE | 3.1.4 |
+| SETUP | 3.1.7 |
+| Call clearing messages: | |
+| RELEASE | 3.1.5 |
+| RELEASE COMPLETE | 3.1.6 |
+| Miscellaneous messages: | |
+| NOTIFY | 3.1.10 |
+| STATUS | 3.1.8 |
+| STATUS ENQUIRY | 3.1.9 |
+
+### 3.1.1 Alerting
+
+This message is sent by the called user to the network and by the network to the calling user to indicate that the called user alerting has been initiated. See Table 3-2.
+
+TABLE 3-2/Q.2931
+**ALERTING message content**
+
+| Message type: ALERTING
Significance: Global
Direction: Both | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Connection identifier | 4.5 | Both | O (Note 1) | 4-9 |
+| Notification indicator | 4.5 | Both | O (Note 2) | 4-* |
+| NOTES
1 When Annex H is implemented, mandatory in the network-to-user direction if this message is the first message in response to a SETUP message. Mandatory in the user-to-network direction if this message is the first message in response to a SETUP message, unless the user accepts the connection identifier indicated in the SETUP message.
2 This indicator may be present whenever notification is delivered. | | | | |
+
+### 3.1.2 Call proceeding
+
+This message is sent by the called user to the network or by the network to the calling user to indicate that the requested call establishment has been initiated and no more call establishment information will be accepted. See Table 3-3.
+
+TABLE 3-3/Q.2931
+
+#### CALL PROCEEDING message content
+
+| Message type: CALL PROCEEDING
Significance: Local
Direction: Both | | | | |
+|-------------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Connection identifier | 4.5 | Both | O (Note 1) | 4-9 |
+| Notification indicator | 4.5 | Both | O (Note 2) | 4-* |
+
+NOTES
+
+1 Mandatory in the network-to-user direction. When Annex H is implemented, mandatory in the network-to-user direction if this message is the first message in response to a SETUP message. Mandatory in the user-to-network direction if this message is the first message in response to a SETUP message, unless the user accepts the connection identifier indicated in the SETUP message.
+
+2 This indicator may be present whenever notification is delivered.
+
+### 3.1.3 Connect
+
+This message is sent by the called user to the network and by the network to the calling user to indicate call acceptance by the called user. See Table 3-4.
+
+TABLE 3-4/Q.2931
+**CONNECT message content**
+
+| Message type: CONNECT
Significance: Global
Direction: Both | | | | |
+|------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| AAL parameters | 4.5 | Both | O (Note 1) | 4-21 |
+| Broadband low layer information | 4.5 | Both | O (Note 2) | 4-17 |
+| Connection identifier | 4.5 | Both | O (Note 3) | 4-9 |
+| End-to-end transit delay | 4.5 | Both | O (Note 4) | 4-10 |
+| Notification indicator | 4.5 | Both | O (Note 5) | 4-* |
+| OAM traffic descriptor | 4.5 | Both | O (Note 6) | 4-6 |
+
+NOTES
+
+- 1 Included in the user-to-network direction when the called user wants to pass ATM adaptation layer parameters information to the calling user, and the ATM adaptation layer parameters information element was present in the SETUP message. Included in the network-to-user direction if the called user included an ATM adaptation layer parameters information element in the CONNECT message. See Annex F.
+- 2 Included in the user-to-network when the answering user wants to return low layer information to the calling user. Included in the network-to-user direction if the user awarded the call included a broadband low layer information information element in the CONNECT message. Optionally included for broadband low layer information negotiation, but some networks may not transport this information element to the calling user (see Annex C).
+- 3 When Annex H is implemented, mandatory in the network-to-user direction if this message is the first message in response to a SETUP message. Mandatory in the user-to-network direction if this message is the first message in response to a SETUP message, unless the user accepts the connection identifier indicated in the SETUP message.
+- 4 Included in the user-to-network direction when the responding user received the end-to-end transit delay information element in the SETUP message. Included in the network-to-user direction if the responding user included the end-to-end transit delay information element in the CONNECT message.
+- 5 This indicator may be present whenever notification is delivered.
+- 6 Included in the user-to-network direction when the responding user received the OAM traffic descriptor information element in the SETUP message. Included in the network-to-user direction if the responding user included the OAM traffic descriptor information element in the CONNECT message.
+
+### 3.1.4 Connect acknowledge
+
+This message is sent by the network to the called user to indicate the user has been awarded the call. It is also sent by the calling user to the network to allow symmetrical call control procedures. See Table 3-5.
+
+TABLE 3-5/Q.2931
+
+#### CONNECT ACKNOWLEDGE message content
+
+| Message type: CONNECT ACKNOWLEDGE
Significance: Local
Direction: Both | | | | |
+|-----------------------------------------------------------------------------|-----------|-----------|----------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Notification indicator | 4.5 | Both | O (Note) | 4-* |
+
+NOTE – This indicator may be present whenever notification is delivered.
+
+### 3.1.5 Release
+
+This message is sent by the user to request the network to clear the end-to-end connection (if any) or is sent by the network to indicate that the end-to-end connection is cleared and that the receiving equipment release the connection identifier and prepare to release its call reference value after sending RELEASE COMPLETE. See Table 3-6.
+
+TABLE 3-6/Q.2931
+
+#### RELEASE message content
+
+| Message type: RELEASE
Significance: Global
Direction: Both | | | | |
+|------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Cause | 4.5 | Both | M (Note 1) | 6-34 |
+| Notification indicator | 4.5 | Both | O (Note 2) | 4-* |
+
+NOTES
+
+- 1 This information element may appear twice in the message.
+- 2 This indicator may be present whenever notification is delivered.
+
+### 3.1.6 Release complete
+
+This message is sent by the user or the network to indicate that the equipment sending the message has released its call reference value and, if appropriate, the connection identifier. The connection identifier, if released, is available for re-use. The receiving equipment shall release its call reference value. See Table 3-7.
+
+TABLE 3-7/Q.2931
+
+#### RELEASE COMPLETE message content
+
+| Message type: RELEASE COMPLETE
Significance: Local (Note 1)
Direction: Both | | | | |
+|-----------------------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Cause | 4.5 | Both | O (Note 2) | 4-34 |
+
+NOTES
+
+- 1 This message has local significance; however, it may carry information of global significance when used as the first call clearing message.
+- 2 Mandatory in the first call clearing message, including when the RELEASE COMPLETE message is sent as a result of an error handling condition. This information element may appear twice in the message.
+
+### 3.1.7 Set-up
+
+This message is sent by the calling user to the network and by the network to the called user to initiate B-ISDN call and connection establishment. See Table 3-8.
+
+TABLE 3-8/Q.2931
+**SETUP message content**
+
+| Message type: SETUP
Significance: Global
Direction: Both | | | | |
+|----------------------------------------------------------------|-----------|-----------|-------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| AAL parameters | 4.5 | Both | O (Note 1) | 4-21 |
+| ATM traffic descriptor | 4.5 | Both | M | 12-20 |
+| Broadband bearer capability | 4.5 | Both | M | 6-7 |
+| Broadband high layer information | 4.5 | Both | O (Note 2) | 4-13 |
+| Broadband repeat indicator | 4.5 | Both | O (Note 3) | 4-5 |
+| Broadband low layer information | 4.5 | Both | O (Note 4) | 4-17 |
+| Called party number | 4.5 | Both | O (Note 5) | 4-* |
+| Called party sub-address | 4.5 | Both | O (Note 6) | 4-25 |
+| Calling party number | 4.5 | Both | O (Note 7) | 4-* |
+| Calling party sub-address | 4.5 | Both | O (Note 8) | 4-25 |
+| Connection identifier | 4.5 | Both | O (Note 9) | 4-9 |
+| End-to-end transit delay | 4.5 | Both | O (Note 10) | 4-10 |
+| Notification indicator | 4.5 | Both | O (Note 11) | 4-* |
+| OAM traffic descriptor | 4.5 | Both | O (Note 12) | 4-6 |
+| QOS parameter | 4.5 | Both | M | 6 |
+| Broadband sending complete | 4.5 | Both | O (Note 13) | 4-5 |
+| Transit network selection | 4.5 | u → n | O (Note 14) | 4-* |
+
+**NOTES**
+
+- 1 Included in the user-to-network direction when the calling user wants to pass AAL information to the called user. Included in the network-to-user direction if the calling user included an AAL parameter information element in the SETUP message. See Annex F.
+- 2 Included in the user-to-network direction when the calling user wants to pass broadband high layer information to the called user. Included in the network-to-user direction if the calling user included a broadband high layer information information element in the SETUP message.
+- 3 Included when two or more broadband low layer information information elements are included for low layer information negotiation. The broadband repeat indicator information element is included immediately before the first broadband low layer information information element.
+- 4 Included in the user-to-network direction when the calling user wants to pass broadband low layer compatibility information to the called user. Included in the network-to-user direction if the calling user included a broadband low layer information information element in the SETUP message. Two or three information elements may be included in descending order of priority, i.e. highest priority first, if the broadband low layer information negotiation procedures are used. See Annex C.
+- 5 The called party number information element is included by the user to convey called party number information to the network. The called party number information element is included by the network when called party number information is conveyed to the user.
+- 6 Included in the user-to-network direction when the calling user wants to indicate the called party sub-address. Included in the network-to-user direction if the calling user included a called party sub-address information element in the SETUP message.
+- 7 May be included by the calling user or the network to identify the calling user.
+
+##### NOTES (continued)
+
+- 8 Included in the user-to-network direction when the calling user wants to indicate the calling party sub-address. Included in the network-to-user direction if the calling user included a calling party sub-address information element in the SETUP message.
+- 9 Included in the user-to-network direction when a user wants to indicate a virtual channel. Included in the network-to-user direction when the network wants to indicate a virtual channel. If not included, its absence is interpreted as any virtual channel is acceptable. This information element may only be absent when using the non-associated signalling procedure.
+- 10 Included in the user-to-network direction when the calling user wants to specify end-to-end transit delay requirements for this call and/or the cumulative transit delay expected for the transmission of user data from the calling user to the network boundary. When included, an end-to-end transit delay information element will be delivered to the called user. Included in the network-to-user direction if end-to-end transit delay information is to be delivered to the called user. See Annex K.
+- 11 This indicator may be present whenever notification is delivered.
+- 12 Included by the calling user to indicate additional information related to the OAM F5 end-to-end information flow. The absence of the OAM traffic descriptor information element does not in itself mean that no OAM flow will be used within this call.
+- 13 It is mandatory for the user to include the broadband sending complete information element when *en bloc* sending procedures are used; its interpretation by the network is optional. It is mandatory for the network to include the broadband sending complete information element when *en bloc* receiving procedures are used. If the broadband sending complete information element is not included, missing mandatory information element error procedures need not be applied.
+- 14 Included by the calling user to select a particular transit network (see Annex D). This information element may appear four times in the message.
+
+### 3.1.8 Status
+
+This message is sent by the user or the network in response to a STATUS ENQUIRY message or at any time to report certain error conditions as listed in clause 5. See Table 3-9.
+
+NOTE – If this message is sent with the global call reference, the “global interface state” (see Table 4-11) is indicated by the call state information element.
+
+TABLE 3-9/Q.2931
+
+#### **STATUS message content**
+
+| Message type: STATUS
Significance: Local
Direction: Both | | | | |
+|----------------------------------------------------------------|-----------|-----------|----------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M (Note) | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Call state | 4.5 | Both | M | 5 |
+| Cause | 4.5 | Both | M | 6-34 |
+
+NOTE – This message may be sent with the global call reference defined in 4.3.
+
+### 3.1.9 Status enquiry
+
+This message is sent by the user or the network at any time to solicit a STATUS message from the peer layer 3 entity. Sending a STATUS message in response to a STATUS ENQUIRY message is mandatory. See Table 3-10.
+
+TABLE 3-10/Q.2931
+
+#### STATUS ENQUIRY message content
+
+| Message type: STATUS ENQUIRY
Significance: Local
Direction: Both | | | | |
+|------------------------------------------------------------------------|-----------|-----------|------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+
+### 3.1.10 Notify
+
+This message is sent by the user or the network to indicate information pertaining to a call/connection. See Table 3-11.
+
+TABLE 3-11/Q.2931
+
+#### NOTIFY message content
+
+| Message type: NOTIFY
Significance: Access
Direction: Both | | | | |
+|-----------------------------------------------------------------|-----------|-----------|------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Notification indicator | 4.5 | Both | M | 5-* |
+
+## 3.2 Additional or modified messages related for the support of 64 kbit/s based ISDN circuit-mode services
+
+Table 3-12 summarizes the messages for B-ISDN call or connection control for the support of 64 kbit/s based ISDN circuit-mode services.
+
+TABLE 3-12/Q.2931
+**Messages related to interworking requirements**
+
+| Message | Reference |
+|------------------------------|-----------|
+| Call establishment messages: | |
+| ALERTING | 3.2.1 |
+| CALL PROCEEDING | 3.2.2 |
+| CONNECT | 3.2.3 |
+| CONNECT ACKNOWLEDGE | 3.1.4 |
+| PROGRESS | 3.2.5 |
+| SETUP | 3.2.7 |
+| SETUP ACKNOWLEDGE | 3.2.8 |
+| Call clearing messages: | |
+| RELEASE | 3.2.6 |
+| RELEASE COMPLETE | 3.1.6 |
+| Miscellaneous messages: | |
+| NOTIFY | 3.1.10 |
+| INFORMATION | 3.2.4 |
+| STATUS | 3.1.8 |
+| STATUS ENQUIRY | 3.1.9 |
+
+### 3.2.1 Alerting
+
+This message is sent by the called user to the network and by the network to the calling user to indicate that called user alerting has been initiated. See Table 3-13.
+
+TABLE 3-13/Q.2931
+**ALERTING message content**
+
+| Message type: ALERTING
Significance: Global
Direction: Both | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Connection identifier | 4.5 | u → n | O (Note 1) | 4-9 |
+| Narrow-band bearer capability | 4.6 | Both | O (Note 2) | 4-14 |
+| Narrow-band high layer compatibility | 4.6 | Both | O (Note 3) | 4-7 |
+| Notification indicator | 4.5 | Both | O (Note 4) | 4-* |
+| Progress indicator | 4.6 | Both | O (Note 5) | 4-6 |
+| NOTES
1 Mandatory in the user-to-network direction if this message is the first message in response to a SETUP message, unless the user accepts the connection identifier indicated in the SETUP message.
2 The narrow-band bearer capability information element is included when procedures for bearer capability selection are used as defined in 5.11/Q.931. When present, progress description No. 5, "interworking has occurred and has resulted in a telecommunication service change" shall also be present.
3 The narrow-band high layer compatibility information element is included when the procedures of 5.12/Q.931 for high layer compatibility selection apply. When present, progress description No. 5, "interworking has occurred and has resulted in a telecommunication service change" shall also be present.
4 This indicator may be present whenever notification is delivered.
5 Included in the event of interworking. Included in the network-to-user direction in connection with the provision of in-band information/patterns. Included in the user-to-network direction in connection with the provision of in-band information/patterns if Annex K/Q.931 is implemented or in accordance with the procedures of 5.11.3/Q.931 and 5.12.3/Q.931. This information element may appear twice in the message. | | | | |
+
+### 3.2.2 Call proceeding
+
+This message is sent by the called user to the network or by network to the calling user to indicate that the requested call establishment has been initiated and no more call establishment information will be accepted. See Table 3-14.
+
+TABLE 3-14/Q.2931
+
+#### CALL PROCEEDING message content
+
+| Message type: CALL PROCEEDING
Significance: Local
Direction: Both | | | | |
+|-------------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Connection identifier | 4.5 | Both | O (Note 1) | 4-9 |
+| Narrow-band bearer capability | 4.6 | Both | O (Note 2) | 4-14 |
+| Narrow-band high layer compatibility | 4.6 | Both | O (Note 3) | 4-7 |
+| Notification indicator | 4.5 | Both | O (Note 4) | 4-* |
+| Progress indicator | 4.6 | Both | O (Note 5) | 4-6 |
+
+NOTES
+
+- 1 Mandatory in the network-to-user direction if this message is the first message in response to a SETUP message. It is mandatory in the user-to-network direction if this message is the first message in response to a SETUP message, unless the user accepts the connection identifier indicated in the SETUP message.
+- 2 The narrow-band bearer capability information element is included when procedures for bearer capability selection are used as defined in 5.11/Q.931. When present, progress description No. 5, "interworking has occurred and has resulted in a telecommunication service change" shall also be present.
+- 3 The narrow-band high layer compatibility information element is included when the procedures of 5.12/Q.931 for high layer compatibility selection apply. When present, progress description No. 5, "interworking has occurred and has resulted in a telecommunication service change" shall also be present.
+- 4 This indicator may be present whenever notification is delivered.
+- 5 Included in the event of interworking. Included in the network-to-user direction in connection with the provision of in-band information/patterns. Included in the user-to-network direction in connection with the provision of in-band information/patterns if Annex K/Q.931 is implemented or in accordance with the procedures of 5.11.3/Q.931 and 5.12.3/Q.931. This information element may appear twice in the message.
+
+### 3.2.3 Connect
+
+This message is sent by the called user to the network and by the network to the calling user to indicate call acceptance by the called user. See Table 3-15.
+
+TABLE 3-15/Q.2931
+**CONNECT message content**
+
+| Message type: CONNECT
Significance: Global
Direction: Both | | | | |
+|------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| AAL parameters | 4.5 | Both | O (Note 1) | 4-21 |
+| Connection identifier | 4.5 | u → n | O (Note 2) | 4-9 |
+| End-to-end transit delay | 4.5 | Both | O (Note 3) | 4-13 |
+| Narrow-band bearer capability | 4.6 | Both | O (Note 4) | 4-14 |
+| Narrow-band high layer compatibility | 4.6 | Both | O (Note 5) | 4-7 |
+| Narrow-band low layer compatibility | 4.6 | Both | O (Note 6) | 4-20 |
+| Notification indicator | 4.5 | Both | O (Note 7) | 4-* |
+| OAM traffic descriptor | 4.5 | Both | O (Note 8) | 4-6 |
+| Progress indicator | 4.6 | Both | O (Note 9) | 4-8 |
+
+NOTES
+
+- 1 Included in the user-to-network direction when the called user wants to pass ATM adaptation layer parameters information to the calling user, and the ATM adaptation layer parameters information element was present in the SETUP message. Included in the network-to-user direction if the called user included an ATM adaptation layer parameters information element in the CONNECT message. See Annex F.
+- 2 Mandatory in the user-to-network if this message is the first message in response to a SETUP message, unless the user accepts the connection identifier indicated in the SETUP message.
+- 3 Included in the user-to-network direction when the responding user received the end-to-end transit delay information element in the SETUP message. Included in the network-to-user direction if the responding user included the end-to-end transit delay information element in the CONNECT message, as described in the procedures for bearer capability selection defined in 5.11/Q.931.
+- 4 The narrow-band bearer capability information element can be included when procedures for bearer capability selection are used as defined in 5.11/Q.931.
+- 5 The narrow-band high layer compatibility information element is included when the procedures of 5.12/Q.931 for high layer compatibility selection apply.
+- 6 Included in the user-to-network direction when the answering user wants to return narrow-band low layer compatibility information to the calling user. Included in the network-to-user direction if the user awarded the call included a narrow-band low layer compatibility information element in the CONNECT message. Optionally included for low layer compatibility negotiation to the calling user (see Annex M/Q.931 – *Blue Book*).
+- 7 This indicator may be present whenever notification is delivered.
+- 8 Included in the user-to-network direction when the responding user received the OAM traffic descriptor information element in the SETUP message. Included in the network-to-user direction if the responding user included the OAM traffic descriptor information element in the CONNECT message.
+- 9 Included in the event of interworking or in connection with the provision of in-band information/patterns. This information element may appear twice in the message.
+
+### 3.2.4 Information
+
+This message is sent by the user or the network to provide additional information. It may be used to provide information for call establishment (e.g. overlap sending) or miscellaneous call-related information. See Table 3-16.
+
+TABLE 3-16/Q.2931
+
+#### INFORMATION message content
+
+| Message type: INFORMATION
Significance: Local (Note 1)
Direction: Both | | | | |
+|------------------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Broadband sending complete | 4.5 | Both | O (Note 2) | 4-5 |
+| Called party number | 4.5 | Both | O (Note 3) | 4-* |
+
+NOTES
+
+- 1 This message has local significance, but may also carry information of global significance.
+- 2 Included if the user optionally indicates completion of overlap sending to the network, or if the network optionally indicates completion of overlap receiving to the user.
+- 3 The called party number information element is included by the user to convey called party number information to the network during overlap sending. The called party number information element is included by the network to convey called party number information to the user during overlap receiving.
+
+### 3.2.5 Progress
+
+This message is sent by the user or the network to indicate the progress of a call in the event of interworking. See Table 3-17.
+
+TABLE 3-17/Q.2931
+**PROGRESS message content**
+
+| Message type: PROGRESS
Significance: Global
Direction: Both | | | | |
+|-------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Narrow-band bearer capability | 4.6 | Both | O (Note 1) | 4-14 |
+| Narrow-band high layer compatibility | 4.6 | Both | O (Note 2) | 4-7 |
+| Notification indicator | 4.5 | Both | O (Note 3) | 4-* |
+| Progress indicator | 4.6 | Both | M (Note 4) | 6 |
+
+NOTES
+
+- 1 The narrow-band bearer capability information element is included when the procedures for bearer capability selection are used as defined in 5.11/Q.931. The narrow-band bearer capability information element indicates the bearer service now being used for the call/connection.
+- 2 The narrow-band high layer compatibility information element is included when the optional procedures of 5.12/Q.931 for high layer compatibility selection apply. The narrow-band high layer compatibility information element indicates the high layer compatibility now being used for the call.
+- 3 This indicator may be present whenever notification is delivered.
+- 4 This information element may appear twice in the message.
+
+### 3.2.6 Release
+
+This message is sent by the user or the network to indicate that the equipment sending the message has disconnected the B-ISDN connection and intends to release the connection identifier (if any) and the call reference, and that the receiving equipment should release the connection identifier and prepare to release the call reference after sending RELEASE COMPLETE. See Table 3-18.
+
+TABLE 3-18/Q.2931
+
+#### RELEASE message content
+
+| Message type: RELEASE
Significance: Global
Direction: Both | | | | |
+|------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Cause | 4.5 | Both | M (Note 1) | 6-34 |
+| Notification indicator | 4.5 | Both | O (Note 2) | 4-* |
+| Progress indicator | 4.6 | Both | O (Note 3) | 4-6 |
+
+NOTES
+
+- 1 This information element may appear twice in the message.
+- 2 This indicator may be present whenever notification is delivered.
+- 3 Included by the network if in-band tones are provided. However, the user may include the progress indicator and provide in-band tones. In such cases, the network will ignore this information element and will not convey the in-band tones. This information element may appear twice in the message.
+
+### 3.2.7 Set-up
+
+This message is sent by the calling user to the network and by the network to the called user to initiate a call in B-ISDN for a 64 kbit/s based circuit-mode ISDN service. See Table 3-19.
+
+TABLE 3-19/Q.2931
+**SETUP message content**
+
+| Message type: SETUP
Significance: Global
Direction: Both | | | | |
+|----------------------------------------------------------------|-----------|-----------|-------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| AAL parameters | 4.5 | Both | O (Note 1) | 4-21 |
+| ATM traffic descriptor | 4.5 | Both | M | 12-20 |
+| Broadband bearer capability | 4.5 | Both | M | 6-7 |
+| Called party number | 4.5 | Both | O (Note 2) | 4-* |
+| Called party sub-address | 4.5 | Both | O (Note 3) | 4-25 |
+| Calling party number | 4.5 | Both | O (Note 4) | 4-* |
+| Calling party sub-address | 4.5 | Both | O (Note 5) | 4-25 |
+| Connection identifier | 4.5 | Both | O (Note 6) | 4-9 |
+| End-to-end transit delay | 4.5 | Both | O (Note 7) | 4-10 |
+| Broadband repeat indicator | 4.5 | Both | O (Note 8) | 4-5 |
+| Narrow-band bearer capability | 4.6 | Both | O (Note 9) | 4-14 |
+| Narrow-band high layer compatibility | 4.6 | Both | O (Note 10) | 4-7 |
+| Broadband repeat indicator | 4.5 | Both | O (Note 11) | 4-5 |
+| Narrow-band low layer compatibility | 4.6 | Both | O (Note 12) | 4-20 |
+| Notification indicator | 4.5 | Both | O (Note 13) | 4-* |
+| OAM traffic descriptor | 4.5 | Both | O (Note 14) | 4-6 |
+| Progress indicator | 4.6 | Both | O (Note 15) | 4-6 |
+| QOS parameter | 4.5 | Both | M | 6 |
+| Broadband sending complete | 4.5 | Both | O (Note 16) | 4-5 |
+| Transit network selection | 4.5 | u → n | O (Note 17) | 4-* |
+
+NOTES
+
+- 1 Included in the user-to-network direction when the calling user wants to pass AAL information to the called user. Included in the network-to-user direction if the calling user included an AAL parameter information element in the SETUP message. See Annex F.
+- 2 The called party number information element is included by the user to convey called party number information to the network. The called party number information element is included by the network when called party number information is conveyed to the user.
+- 3 Included in the user-to-network direction when the calling user wants to indicate the called party sub-address. Included in the network-to-user direction if the calling user included a called party sub-address information element in the SETUP message.
+- 4 May be included by the calling user or the network to identify the calling user.
+- 5 Included in the user-to-network direction when the calling user wants to indicate the calling party sub-address. Included in the network-to-user direction if the calling user included a calling party sub-address information element in the SETUP message.
+- 6 Included in the user-to-network direction when a user wants to indicate a virtual channel. Included in the network-to-user direction when the network wants to indicate a virtual channel. If not included, its absence is interpreted as any virtual channel is acceptable. This information element may only be absent when using the non-associated signalling procedure.
+
+#### NOTES (continued)
+
+7 Included in the user-to-network direction when the calling user wants to specify end-to-end transit delay requirements for this call and/or the cumulative transit delay expected for the transmission of user data from the calling user to the network boundary. When included, an end-to-end transit delay information element will be delivered to the called user. Included in the network-to-user direction if end-to-end transit delay information is to be delivered to the called user (see Annex K).
+
+8 The Broadband repeat indicator information element is included immediately before the first narrow-band bearer capability information element when the narrow-band bearer capability negotiation procedure is used (see Annex L/Q.931).
+
+9 Mandatory for N-ISDN services (see clause 6). May be repeated if the narrow-band bearer capability negotiation procedure is used (see Annex L/Q.931). For narrow-band bearer capability negotiation, three narrow-band bearer capability information elements may be included in descending order of priority, i.e. highest priority first. Although support of multiple narrow-band bearer capability information elements may not be supported on all networks, on networks that do support it, and through suitable subscription arrangements, three narrow-band bearer capability information elements may be included (see 5.11/Q.931). When they are not preceded by a broadband repeat indicator information element, they are included in ascending order of priority.
+
+10 Included in the user-to-network direction when the calling user wants to pass high layer compatibility information to the called user. Included in the network-to-user direction if the calling user included a narrow-band high layer compatibility information element in the SETUP message. Although support of multiple narrow-band high layer compatibility information elements may not be supported on all networks, on networks that do support it, and through suitable subscription arrangements, two narrow-band high layer compatibility information elements may be included (see 5.12/Q.931). They are not preceded by a broadband repeat indicator information element, they are included in ascending order of priority.
+
+11 The broadband repeat indicator is included when two or more narrow-band low layer compatibility information element are included for low layer compatibility negotiation.
+
+12 Included in the user-to-network direction when the calling user wants to pass narrow-band low layer compatibility information to the called user. Included in the network-to-user direction if the calling user included a narrow-band low layer compatibility information element in the SETUP message. Two, three or four information elements may be included in descending order of priority, i.e. highest priority first, if the low layer compatibility negotiation procedures are used (see Annex J/Q.931).
+
+13 This indicator may be present whenever notification is delivered.
+
+14 Included by the calling user to indicate additional information related to the OAM F5 end-to-end information flow. The absence of the OAM traffic descriptor information element does not in itself mean that no OAM flow will be used within this call. This assumes there is an end-to-end B-ISDN connection.
+
+15 Included in the event of interworking or in connection with the provision of in-band information/patterns. This information element may appear twice in the message.
+
+16 It is mandatory for the user to include the broadband sending complete information element when *en bloc* sending procedures are used; its interpretation by the network is optional. It is mandatory for the network to include the broadband sending complete information element when *en bloc* receiving procedures are used. If the broadband sending complete information element is not included, missing mandatory information element error procedures need not be applied.
+
+17 Included by the calling user to select a particular transit network (see Annex D). This information may appear up to four times in the message.
+
+### 3.2.8 Set-up acknowledge
+
+This message is sent by the network to the calling user, or by the called user to the network, to indicate that call establishment has been initiated, but additional information may be required. See Table 3-20.
+
+TABLE 3-20/Q.2931
+
+#### **SETUP ACKNOWLEDGE message content**
+
+| Message type: SETUP ACKNOWLEDGE
Significance: Local
Direction: Both | | | | |
+|---------------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Connection identifier | 4.5 | Both | O (Note 1) | 4-9 |
+| Notification indicator | 4.5 | Both | O (Note 2) | 4-* |
+| Progress indicator | 4.6 | Both | O (Note 3) | 4-6 |
+
+NOTES
+
+- 1 Mandatory in the network-to-user direction if this message is the first message in response to a SETUP message. It is mandatory in the user-to-network direction if this message is the first message in response to a SETUP message, unless the user accepts the connection identifier indicated in the SETUP message.
+- 2 This indicator may be present whenever notification is delivered.
+- 3 Included in the event of interworking or in connection with the provision of in-band information/patterns. This information element may appear twice in the message.
+
+## 3.3 Messages used with the global call reference
+
+The global call reference is used in the message shown in Table 3-21.
+
+TABLE 3-21/Q.2931
+
+### **Messages used with the global call reference**
+
+| Message | Reference |
+|---------------------|-----------|
+| Messages: | |
+| RESTART | 3.3.1 |
+| RESTART ACKNOWLEDGE | 3.3.2 |
+
+NOTE – In addition, the STATUS message shall use the global call reference if it is sent in response to the receipt of a message with the global call reference.
+
+### 3.3.1 Restart
+
+This message is sent by the user or the network to request the recipient to restart (i.e. return to an idle condition) the indicated virtual channel, all virtual channels in the indicated virtual path connection, or all virtual channels controlled by the signalling virtual channel. See Table 3-22.
+
+TABLE 3-22/Q.2931
+
+#### RESTART message content
+
+| Message type: RESTART
Significance: Local
Direction: Both | | | | |
+|-----------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M (Note 1) | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Connection identifier | 4.5 | Both | O (Note 2) | 4-9 |
+| Restart indicator | 4.5 | Both | M | 5 |
+
+NOTES
+
+- 1 This message is sent with the global call reference defined in 4.3.
+- 2 Included when necessary to indicate the particular virtual channel(s) to be restarted.
+
+### 3.3.2 Restart acknowledge
+
+This message is sent to acknowledge the receipt of a RESTART message and to indicate that the requested restart is complete. See Table 3-23.
+
+TABLE 3-23/Q.2931
+
+#### RESTART ACKNOWLEDGE message content
+
+| Message type: RESTART ACKNOWLEDGE
Significance: Local
Direction: Both | | | | |
+|-----------------------------------------------------------------------------|-----------|-----------|------------|--------|
+| Information element | Reference | Direction | Type | Length |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference | 4.3 | Both | M (Note 1) | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Connection identifier | 4.5 | Both | O (Note 2) | 4-9 |
+| Restart indicator | 4.5 | Both | M | 5 |
+
+NOTES
+
+- 1 This message is sent with the global call reference defined in 4.3.
+- 2 Included when necessary to indicate the particular virtual channel(s) which have been restarted.
+
+## 4 General message format and information elements coding
+
+The figures and text in this clause describe message contents.
+
+## 4.1 Overview
+
+Within this protocol, every message shall consist of the following parts:
+
+- a) protocol discriminator;
+- b) call reference;
+- c) message type (including message compatibility instruction indicator);
+- d) message length;
+- e) variable length information elements, as required.
+
+Information elements a), b), c) and d) are common to all the messages and shall always be present, while information elements e) are specific to each message type.
+
+This organization is illustrated in the example shown in Figure 4-1. The first four information elements (protocol discriminator, call reference, message type, and message length) shall appear in the order specified in Figure 4-1.
+
+
+
+| Bits | | | | | | | | Octets |
+|--------------------------------------------------|----------------------|---|---|-------------------------------------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Protocol discriminator | | | | | | | | 1 |
+| 0 | 0 | 0 | 0 | Length of call reference value
0 0 1 1 | | | | 2 |
+| Flag | Call reference value | | | | | | | 3 |
+| Call reference value (continued) | | | | | | | | 4 |
+| | | | | | | | | 5 |
+| | | | | | | | | 6 |
+| Message type | | | | | | | | 7 |
+| | | | | | | | | 8 |
+| Message length | | | | | | | | 9 |
+| Variable length information elements as required | | | | | | | | etc. |
+
+T1162550-94/d001
+
+FIGURE 4-1/Q.2931
+General message organization example
+
+A particular message may contain more information than a particular (user or network) equipment needs or can understand. All equipment should be able to ignore any extra information, present in a message, which is not required for the proper operation of that equipment. For example, a user may ignore the calling party number if that number is of no interest to the user when a SETUP MESSAGE is received.
+
+Unless specified otherwise, a particular information element shall not be present more than once in a given message.
+
+The term “default” implies that the value defined shall be used in the absence of any assignment, or the negotiation of alternative values.
+
+When a field, such as the call reference value, extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest-numbered bit of the highest-numbered octet of the field.
+
+## 4.2 Protocol discriminator
+
+The purpose of the protocol discriminator is to distinguish messages for user-network call control from other messages (to be defined) within this Recommendation. It also distinguishes messages of this Recommendation from those OSI network layer protocol units which are coded according to other ITU-T Recommendations and other standards. See Figure 4-2.
+
+The protocol discriminator is the first part of every message. The protocol discriminator is coded according to Table 4-1. The specification of the protocol discriminator does not imply that the protocol may share the signalling virtual channel with other layer 3 protocols (except when encapsulated in Q.2931 messages).
+
+## 4.3 Call reference
+
+The purpose of the call reference is to identify the call at the local user-network interface to which the particular message applies. The call reference does not have end-to-end significance across B-ISDNs.
+
+The call reference is the second part of every message. The call reference is coded as shown in Figure 4-3. The length of the call reference value is indicated in octet 1, bits 1-4. The length of the call reference information element is 4 octets.
+
+The call reference information element includes the call reference value and the call reference flag. The call reference value 0 (all bits = 0) is reserved for the global call reference, see Figure 4-4; the call reference value with all bits set to 1 is reserved for the dummy call reference, see Figure 4-5.
+
+Call reference values are assigned by the originating side of the interface for a call. These values are unique to the originating side only assigned at the beginning of a call and remains fixed for the lifetime of a call. After a call ends, the associated call reference value may be reassigned to a later call. Two identical call reference values on the same signalling virtual channel may be used when each value pertains to a call originated at opposite ends of the signalling virtual channel link.
+
+To avoid race conditions in certain error scenarios, it is suggested that implementors avoid immediate re-use of the call reference values after they are released.
+
+The call reference flag can take the values “0” or “1”. The call reference flag is used to identify which end of the signalling virtual channel originated a call reference. The originating side always sets the call reference flag to “0”. The destination side always sets the call reference flag to a “1”.
+
+Hence, the call reference flag identifies who allocated the call reference value, and the only purpose of the call reference flag is to resolve simultaneous attempts to allocate the same call reference value. The call reference flag also applies to functions which use the global call reference (e.g. restart procedures).
+
+
+
+| | | | | | | | | |
+|------------------------------------------------------|---|---|---|---|---|---|---|-------|
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet |
+| Q.2931 user-network call/connection control messages | | | | | | | | |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 |
+| protocol discriminator | | | | | | | | |
+
+T1162560-94/d002
+
+FIGURE 4-2/Q.2931
+
+#### **Protocol discriminator**
+
+TABLE 4-1/Q.2931
+
+#### **Protocol discriminator**
+
+| | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-----------------------------------------------------------------------------------------------------|
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | } assigned in clause 4/Q.931;
not available for use in the message protocol discriminator |
+| through | | | | | | | | |
+| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | Q.931/(I.451) user-network call control messages |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | Q.2931 user-network call/connection control messages |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | } reserved for other network layer or layer 3 protocols, including
Recommendation X.25
(Note) |
+| through | | | | | | | | |
+| 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | |
+| 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | } national use |
+| through | | | | | | | | |
+| 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | |
+| 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | } reserved for other network layer or layer 3 protocols, including
Recommendation X.25
(Note) |
+| through | | | | | | | | |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | |
+| All other values are reserved. | | | | | | | | |
+| NOTE – These values are reserved to discriminate these protocol discriminators from the first octet of a X.25 packet including general format identifier. | | | | | | | | |
+
+The numerical value of the global call reference is zero. The equipment receiving a message containing the global call reference shall interpret the message as pertaining to all call references associated with the appropriate signalling virtual channel; see Figure 4-4.
+
+For the global call reference, the flag is used as specified above. This means that in a RESTART message, it is set to 0; in case of a RESTART ACKNOWLEDGE or STATUS message with the global call reference sent in response to a RESTART message, it is set to 1.
+
+The dummy call reference is coded with all bits of the call reference value set to 1; see Figure 4-5. In the future, the dummy call reference may be used for certain supplementary services. For the dummy call reference, the flag is also used as specified above.
+
+The procedures in this Recommendation do not use the dummy call reference. Equipment conforming to this Recommendation shall discard messages received with the dummy call reference.
+
+
+
+Bits
+
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets |
+|---------|----------------------|---|---|--------------------------------------------|---|---|---|--------|
+| 0 0 0 0 | | | | Length of call reference value (in octets) | | | | 1 |
+| Flag | Call reference value | | | | | | | 2 |
+| | | | | | | | | 3 |
+| | | | | | | | | 4 |
+
+Call reference flag (octet 2)
+
+Bit
+
+8
+
+0 the message is sent from the side that originated the call reference.
+
+1 the message is sent to the side that originated the call reference.
+
+T1162570-94/d003
+
+FIGURE 4-3/Q.2931
+**Call reference information element**
+
+| Bits | | | | | | | | Octets |
+|----------------------|---|---|---|--------------------------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| | | | | Length of call reference value | | | | 1 |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | |
+| 0/1
Flag | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 |
+| Call reference value | | | | | | | | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 |
+
+T1162580-94/d004
+
+FIGURE 4-4/Q.2931
+**Encoding for global call reference**
+
+| Bits | | | | | | | | Octets |
+|----------------------|---|---|---|--------------------------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| | | | | Length of call reference value | | | | 1 |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | |
+| 0/1
Flag | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 |
+| Call reference value | | | | | | | | |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 3 |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 4 |
+
+T1162590-94/d005
+
+FIGURE 4-5/Q.2931
+**Encoding of the dummy call reference**
+
+## 4.4 Message type, and message length
+
+### 4.4.1 Message type (including message compatibility instruction indicator)
+
+The purpose of the message type is to identify the function of the message being sent.
+
+The message type is the third part of every message. The message type is coded as shown in Figure 4-6 and Table 4-2.
+
+The value “0000 0000” is used for escape to national specific messages (see Table 4-2).
+
+The value “1111 1111” is reserved for an extension mechanism when all other message type values are exhausted (see Table 4-2).
+
+The message compatibility instruction indicator allows the sender of a message to indicate explicitly the way the peer entity shall handle unrecognized messages. The format and coding of the message compatibility instruction indicator is shown in Figure 4-6 and Table 4-2.
+
+The message compatibility instruction indicator is only of local significance. Unless specified otherwise, it is a network option to which value the instruction indicator is set for messages sent from the network to the user.
+
+### 4.4.2 Message length
+
+The purpose of the message length is to identify the length of the contents of a message. It is the binary coding of the number of octets of the message contents, i.e. excluding the octets used for “protocol discriminator”, “call reference”, “message type”, and for the message length indication itself.
+
+The message length indication has a fixed length of 2 octets. The coding of the message length follows the coding rules for integer values outlined in 4.5.1.
+
+The message length is the fourth part of every message. The message length is coded as shown in Figure 4-7. If the message contains no further octets, the message length is coded as all zeros.
+
+
+
+| Bits | | | | | | | | |
+|--------------|-------|---|------|-------|-------|-----------------------|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets |
+| Message type | | | | | | | | 1 |
+| 1 | 0 | 0 | Flag | 0 | 0 | Msg. action indicator | | 2 |
+| Ext. | Spare | | | Spare | Spare | | | |
+
+Diagram of Message type octet structure showing bits 8-1 and their corresponding octet numbers 1 and 2.
+
+T1162600-94/d006
+
+FIGURE 4-6/Q.2931
+
+#### Message type
+
+TABLE 4-2/Q.2931 (part 1 of 2)
+
+#### **Message types (including message compatibility instruction indicator)**
+
+| – Message type (octet 1) | | | | | | | | |
+|--------------------------|---|---|---|---|---|---|---|------------------------------------------------------------------------------------------------|
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | escape to nationally specific message type (see Note 1) |
+| 0 | 0 | 0 | – | – | – | – | – | Call establishment message: |
+| | | | 0 | 0 | 0 | 0 | 1 | – ALERTING |
+| | | | 0 | 0 | 0 | 1 | 0 | – CALL PROCEEDING |
+| | | | 0 | 0 | 1 | 1 | 1 | – CONNECT |
+| | | | 0 | 1 | 1 | 1 | 1 | – CONNECT ACKNOWLEDGE |
+| | | | 0 | 0 | 0 | 1 | 1 | – PROGRESS |
+| | | | 0 | 0 | 1 | 0 | 1 | – SETUP |
+| | | | 0 | 1 | 1 | 0 | 1 | – SETUP ACKNOWLEDGE |
+| 0 | 1 | 0 | – | – | – | – | – | Call clearing messages: |
+| | | | 0 | 1 | 1 | 0 | 1 | – RELEASE |
+| | | | 1 | 1 | 0 | 1 | 0 | – RELEASE COMPLETE |
+| | | | 0 | 0 | 1 | 1 | 0 | – RESTART |
+| | | | 0 | 1 | 1 | 1 | 0 | – RESTART ACKNOWLEDGE |
+| 0 | 1 | 1 | – | – | – | – | – | Miscellaneous messages: |
+| | | | 1 | 1 | 0 | 1 | 1 | – INFORMATION |
+| | | | 0 | 1 | 1 | 1 | 0 | – NOTIFY |
+| | | | 1 | 1 | 1 | 0 | 1 | – STATUS |
+| | | | 1 | 0 | 1 | 0 | 1 | – STATUS ENQUIRY |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | reserved for extension mechanism when all other message type values are exhausted (see Note 2) |
+
+NOTE 1 – When used, the message type (excluding the message compatibility instruction indicator) is defined in octet 10 of the message, and the contents follows in the subsequent octets, both according to the national specification.
+
+NOTE 2 – In this case, the message type (excluding the message compatibility instruction indicator) is defined in octet 10 of the message, and the contents follows in the subsequent octets.
+
+TABLE 4-2/Q.2931 (part 2 of 2)
+
+| | | |
+|----------------------------------------------------|---|---------------------------------------------------------------------------------------|
+| – Flag (octet 2) | | |
+| Bits | | |
+| 5 | | |
+| 0 | | message instruction field not significant (= regular error handling procedures apply) |
+| 1 | | follow explicit instructions (these supersede the regular error handling procedures) |
+| – Message action indicator (octet 2) | | |
+| Bits | | |
+| 2 | 1 | |
+| 0 | 0 | clear call |
+| 0 | 1 | discard and ignore (Note 3) |
+| 1 | 0 | discard and report status |
+| 1 | 1 | reserved |
+| NOTE 3 – For the meaning of “ignore”, see Annex J. | | |
+
+
+
+Diagram of Message length field structure. It shows a rectangular box representing the message length field, divided into two octets. Above the box, the word 'Bits' is centered, and below it, the numbers 8, 7, 6, 5, 4, 3, 2, 1 are listed. To the right of the box, the word 'Octets' is centered, and below it, the numbers 1 and 2 are listed. The text 'Message length' is centered inside the box. Below the box, the text 'T1162610-94/d007' is present.
+
+FIGURE 4-7/Q.2931
+
+#### **Message length**
+
+## 4.5 Variable length information elements for B-ISDN environment
+
+### 4.5.1 Coding rules
+
+The coding of variable length information elements follows the coding rules described below. These rules are formulated to allow each equipment which processes a message to find information elements important to it, and yet remain ignorant of information elements not important to that equipment.
+
+For the information elements listed below, the coding of the information element identifier bits is summarized in Table 4-3 and Figure 4-8.
+
+The value “1111 1111” for the information element identifier is reserved for an extension mechanism, when all other information element identifier values are exhausted (see Figure 4-9). This mechanism allows to identify 65 536 additional information elements.
+
+TABLE 4-3/Q.2931 (part 1 of 2)
+
+#### **General information element format – Information element identifiers**
+
+| Bits | | | | | | | | |
+|------|---|---|---|---|---|---|---|------------------------------------------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | Called party number |
+| 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | Called party sub-address |
+| 0 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | Transit network selection |
+| 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | Restart indicator |
+| 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | Narrow-band low layer compatibility |
+| 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | Narrow-band high layer compatibility |
+| 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | Broadband locking shift |
+| 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | Broadband non-locking shift |
+| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | Broadband sending complete |
+| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | Broadband repeat indicator |
+| 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | Calling party number |
+| 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | Calling party sub-address |
+| 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | ATM adaptation layer parameters |
+| 0 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | ATM traffic descriptor |
+| 0 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | Connection identifier |
+| 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | OAM traffic descriptor |
+| 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | Quality of Service parameter |
+| 0 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | Broadband bearer capability |
+| 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | Broadband Low Layer Information (B-LLI) |
+| 0 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | Broadband High Layer Information (B-HLI) |
+| 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | End-to-end transit delay |
+| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | Notification indicator |
+| 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | Call state |
+| 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | Progress indicator |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Narrow-band bearer capability |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | Cause |
+
+TABLE 4-3/Q.2931 (part 2 of 2)
+
+##### **General information element format – Compatibility instruction indicator octet**
+
+| | | | |
+|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------|
+| – Coding standard (octet 2) | | | |
+| Bits | | | |
+| 7 | 6 | | |
+| 0 | 0 | | ITU-T standardized coding as described below |
+| 0 | 1 | | ISO/IEC standard (Note 1) |
+| 1 | 0 | | national standard (Note 1) |
+| 1 | 1 | | standard defined for the network (either public or private) present on the network side of the interface (Note 1) |
+| – Flag (octet 2) | | | |
+| Bit | | | |
+| 5 | | | |
+| 0 | | | IE instruction field not significant (= regular error handling procedures apply) |
+| 1 | | | Follow explicit instructions (these supersede the regular error handling procedures) |
+| – Reserved (octet 2) | | | |
+| Bit | | | |
+| 4 | | | this bit is reserved for a possible use to indicate a “pass along request”. It is currently coded as “0” (= no “pass along request” indicated) |
+| – IE action indicator (octet 2) | | | |
+| Bits | | | |
+| 3 | 2 | 1 | |
+| 0 | 0 | 0 | clear call |
+| 0 | 0 | 1 | discard information element and proceed |
+| 0 | 1 | 0 | discard information element, proceed, and report status |
+| 1 | 0 | 1 | discard message, and ignore (Note 2) |
+| 1 | 1 | 0 | discard message, and report status |
+| All other values are reserved. | | | |
+| NOTES | | | |
+| 1 | These other coding standards should be used only when the information element contents cannot be represented with the ITU-T standardized coding. | | |
+| 2 | For the meaning of “ignore”, see Annex J. | | |
+
+
+
+| Bits | | | | | | | | Octets |
+|-------------------------------------------|-----------------|---|----------------------|------|----------------|---|---|--------------------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Information element identifier | | | | | | | | 1 |
+| 1 ext. | Coding standard | | IE instruction field | | | | | 2 (Note 1) |
+| | | | Flag | Res. | IE action ind. | | | |
+| Length of contents of information element | | | | | | | | 3 |
+| Contents of information element | | | | | | | | 4 |
+| | | | | | | | | 5 (Note 2)
etc. |
+
+Diagram of General information element format showing octets 1-5. Octet 1 is 'Information element identifier'. Octet 2 contains '1 ext.', 'Coding standard', and 'IE instruction field' (subdivided into 'Flag', 'Res.', and 'IE action ind.'). Octet 3 is 'Length of contents of information element'. Octet 4 is 'Contents of information element'. Octet 5 is 'etc.'.
+
+T1162620-94/d08
+
+##### NOTES
+
+- 1 The IE instruction field (Bits 5-1 of octet 2) is only interpreted in case of unexpected information elements, unrecognized information element identifier or information elements with unrecognized contents. For some information elements of this Recommendation, the allocation of values to the IE instruction field may be restricted to a limited number of value combinations (see description of individual information elements below).
+- 2 Annex L shows an example structure for an information element using subfield identifiers.
+
+FIGURE 4-8/Q.2931
+General information element format
+
+
+
+| Bits | | | | | | | | Octets |
+|----------------------------------------|-----------------|---|----------------------|------|----------------|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Escape for extension | | | | | | | | |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
+| 1 ext. | Coding standard | | IE instruction field | | | | | 2 |
+| | | | Flag | Res. | IE action ind. | | | |
+| Length of information element contents | | | | | | | | 3 |
+| Information element identifier | | | | | | | | 4 |
+| Contents of information element | | | | | | | | 5 |
+| | | | | | | | | 6 |
+| | | | | | | | | 7 etc. |
+
+Diagram of Information element format using escape for extension showing octets 1-7. Octet 1 is 'Escape for extension' (all bits 1). Octet 2 contains '1 ext.', 'Coding standard', and 'IE instruction field' (subdivided into 'Flag', 'Res.', and 'IE action ind.'). Octet 3 is 'Length of information element contents'. Octet 4 is 'Information element identifier'. Octet 5 is 'Contents of information element'. Octet 6 is 'etc.'.
+
+T1162630-94/d009
+
+FIGURE 4-9/Q.2931
+Information element format using escape for extension
+
+The specific variable length information elements within a message may appear in any order except for the following cases:
+
+- a) If information elements are repeated without using the broadband repeat indicator information element, the following rule applies:
+ - The second occurrence of a repeated information element must immediately follow the first occurrence of the repeated information element. The third occurrence of the repeated information element must immediately follow the second occurrence of the repeated information element, etc.
+
+This rule does not apply to the broadband locking shift information element and the broadband non-locking shift information element.
+
+- b) When information elements are repeated and the broadband repeat indicator information element is used, the following rules apply:
+ - The broadband repeat indicator information element must immediately precede the first occurrence of the repeated information element.
+ - The first occurrence of the repeated information element (immediately following the broadband repeat indicator information element) is interpreted as the highest priority. The second, third, fourth, etc., occurrences of the repeated information element are interpreted in descending order of priority.
+ - The second occurrence of the repeated information element must immediately follow the first occurrence of the repeated information element. The third occurrence of the repeated information element must immediately follow the second occurrence of the repeated information element, etc.
+
+With regard to these rules, a broadband non-locking shift information element with the succeeding information element are regarded together as one “occurrence” in the sense of the text above.
+
+The use of the broadband repeat indicator information element in conjunction with an information element that occurs only once in a message shall not in itself constitute an error, i.e. the broadband repeat indicator information element shall then be ignored.
+
+- c) If a broadband locking shift information element is used, it applies only to all information elements following. The ordering of these information elements is as specified by the new codeset indicated in the broadband locking shift.
+- d) If a broadband non-locking shift information element is used, it shall immediately precede the information element it refers to.
+
+Annex L shows an example message structuring following these rules.
+
+Where the description of information elements in this Recommendation contains spare bits, these bits are indicated as being set to “0”. On reception, no action is taken on spare bits, even if they are not set to “0”.
+
+The second octet of the information element identifier contains the information element compatibility instruction indicator. The coding of the information element compatibility instruction indicator is shown in Table 4-3.
+
+The information element compatibility instruction indicator is only of local significance. Unless specified otherwise, it is a network option to which value the instruction indicator is set for information elements contained in messages sent from the network to the user.
+
+The third and fourth octet of an information element indicates the length of that information element. The length of an information element does not include the length of the information element identifier field, the information element compatibility instruction indicator field or the length of the length field itself. It is the binary coding of the number of octets of the contents. The information element length indication has a fixed length of 2 octets. The coding of the information element length follows the coding rules for integer values outlined in this subclause.
+
+An information element may be present, but empty. For example, a SETUP message may contain a Called party number information element, the contents of which is of zero length. This should be interpreted by the receiver as equivalent to that information element being absent. Similarly, an absent information element should be interpreted by the receiver as equivalent to that information element being empty.
+
+An “Empty information element” is an information element satisfying the following conditions: has a (valid) Information Element Identifier, and has information element length set to 0.
+
+The following rules apply for the coding of information elements:
+
+- a) Variable length information elements consist of octets or groups of octets. These octets or octet groups are numbered to facilitate referencing. The first digit in the octet number identifies one octet or a group of octets.
+- b) Each octet group is a self-contained entity. The internal structure of an octet group may be defined in alternative ways.
+- c) An octet group is formed by using some extension mechanism. The preferred extension mechanism is to extend an octet (N) through the next octet(s) (Na, Nb, etc.) by using bit 8 in each octet as an extension bit. The bit value “0” indicates that the octet continues through the next octet. The bit value “1” indicates that this octet is the last octet. If one octet (Nb) is present, also the preceding octets (N and Na) must be present.
+
+In the format descriptions appearing in 4.5.5, etc., bit 8 is marked as:
+
+- “0/1 ext.”, if another octet of this octet group may follow.
+- “1 ext.”, if this is the last octet in the extension domain.
+- “0 ext.”, if another octet of this octet group always follows.
+
+Additional octets may be defined later (“1 ext.” changed to “0/1 ext.”) and equipments shall be prepared to receive such additional octets although the equipment need not be able to interpret or act upon the content of these octets.
+
+- d) In addition to the extension mechanism defined above, an octet (N) may be extended through the next octet(s) (N.1, N.2, etc.) by indications in bits 8-1 (of octet N).
+- e) The mechanisms in c) and d) may be combined. Mechanism c) shall take priority in the ordering, such that all octets Na, Nb, etc. shall occur before octets N.1, N.2, etc. This rule shall apply even where the extension to octets N.1, N.2, etc. is indicated in one of octet Na, Nb, etc.; similar conventions apply even when mechanism d) is being repeated, i.e. octet N.1 shall occur before octets N.1.1, N.1.2, etc.
+- f) Optional octets are marked with asterisks (\*).
+- g) If information elements are structured using subfield identifiers, these subfield identifiers are position independent, i.e. they need not appear in a certain order within the information element.
+
+NOTE 1 – It is not possible to use mechanism c) repeatedly, i.e. it is not possible to construct an octet 4aa as this would become octet 4b.
+
+NOTE 2 – Protocol designers should exercise care in using multiple extension mechanisms to insure that a unique interpretation of the resultant coding is possible.
+
+NOTE 3 – For all information elements, there is a field that defines the coding standard. When the coding standard defines a national standard, it is recommended that the national standard be structured similar to the information element defined in this Recommendation.
+
+The following rules apply for the coding of integers in this Recommendation. These rules apply if not indicated otherwise explicitly.
+
+- a) Where integer values are coded using more than 1 octet, octets with lower octet numbers contain the more significant bits. In particular, the octet with the lowest octet number contains the most significant bits, and the octet with the highest octet number contains the least significant bits.
+- b) Within one octet or within a field forming part of an octet, the following applies:
+ - the bits with higher bit numbers contain the more significant bits;
+ - in particular, the bit with the highest bit number of the integer coding denotes the most significant bit;
+ - and the bit with the lowest bit number of the integer coding denotes the least significant bit;
+ - the bit representation is “right-aligned”, i.e. aligned to the lowest bit numbers; therefore, if leading “zeros” are present, they have to appear on the “left-hand” side of the octet or field (i.e. on the side of the higher bit numbers).
+
+- c) Where integer values are represented by a fixed number of octets, the bit representation is aligned to the higher octet numbers, i.e. if leading “zeros” are present, they appear within the octets with the lowest octet numbers.
+- d) Where integer values are represented by a variable number of octets (e.g. by using bit 8 as an extension mechanism), the integer value shall be coded with a minimum number of octets, i.e. no leading all-zero octets are present.
+
+NOTE 4 – The escape mechanism is applicable to codesets 0 to 7 (see 4.5.2). When the escape for extension is used, the information element identifier is contained in octets 5 and 6, and the contents of the information element follows in the subsequent octets as shown in Figure 4-9.
+
+### 4.5.2 Extensions of codesets
+
+There are a number of possible information element identifier values using the formatting rules described in 4.5.1.
+
+It is possible to expand this structure to eight codesets. One common value of an information element identifier is employed in each codeset to facilitate shifting from one codeset to another. The contents of this shift information element identifies the codeset to be used for the next information element or elements. The codeset in use at any given time is referred to as the “active codeset”. By convention, codeset 0 is the initially active codeset.
+
+Two codeset shifting procedures are supported: locking shift and non-locking shift.
+
+Codesets 1 to 3 are reserved for future ITU-use.
+
+Codeset 4 is reserved for use by ISO/IEC standards.
+
+Codeset 5 is reserved for information elements for national use.
+
+Codeset 6 is reserved for information elements specific to the local network (either public or private).
+
+Codeset 7 is reserved for user-specific information elements.
+
+The coding rules specified in 4.5.1 shall apply for information elements belonging to any active codeset.
+
+Transitions from one active codeset to another (i.e. by means of the locking shift procedure) may only be made to a codeset with a higher numerical value than the codeset being left.
+
+An information element belonging to codesets 4, 5, 6, or 7, may appear together with information elements belonging to codeset 0 (being the active codeset) by using the non-locking shift procedure (see 4.5.4).
+
+A user or network equipment shall have the capability to recognize a shift information element and to determine the length of the following information element, although the equipment need not be able to interpret and act upon the contents of the information element. This enables the equipment to determine the start of a subsequent information element.
+
+Codeset 7 information elements shall be handled according to the procedures for unrecognized information elements (see 5.6.8.1) by the first exchange in the local network, unless allowed by a future service definition, bilateral agreement, or provision is made to support this across the local network for a specific user.
+
+Codeset 6 is reserved for information elements specific to the local network (either public or private). As such they do not have significance across the boundaries between local networks, or across a national, or international boundary. Therefore, codeset 6 information elements shall be handled according to the procedures for unrecognized information elements (see 5.6.8.1) beyond the local network boundary, unless allowed by bilateral agreement.
+
+Codeset 5 is reserved for information elements reserved for national use. As such they do not have significance across an international boundary. Therefore, codeset 5 information elements shall be handled according to the procedures for unrecognized information elements (see 5.6.8.1) at the first exchange beyond the international boundary, unless there are bilateral agreements to the contrary.
+
+Codeset 4 is reserved for information elements specified in ISO/IEC standards.
+
+Codesets 1 to 3 are reserved for future ITU-use.
+
+#### 4.5.3 Broadband locking shift procedure
+
+The broadband locking shift procedure employs an information element to indicate the new active codeset. The specified codeset remains active until another broadband locking shift information element is encountered which specifies the use of another codeset. For example, codeset 0 is active at the start of message contents analysis. If a broadband locking shift to codeset 5 is encountered, the next information elements will be interpreted according to the information element identifiers assigned in codeset 5, until another shift information element is encountered.
+
+This procedure is used only to shift to a higher order codeset than the one being left.
+
+The broadband locking shift is valid only within that message which contains the broadband locking shift information element. At the start of every message contents analysis, the active codeset is codeset 0.
+
+The broadband locking shift information element uses the information element format and coding shown in Figure 4-10 and Table 4-4.
+
+
+
+| Bits | | | | | | | | Octets |
+|-------------------------------------------|-----------------|---|----------------------|------|----------------------------|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Broadband-locking shift | | | | | | | | 1 |
+| 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | | IE instruction field | | | | | |
+| | | | Flag | Res. | IE action ind. | | | 3 |
+| Length of broadband locking shift content | | | | | | | | |
+| | | | | | | | | 4 |
+| 1 ext. | Spare | | | | New codeset identification | | | 5 |
+| | 0 | 0 | 0 | 0 | | | | |
+
+T1162640-94/d010
+
+FIGURE 4-10/Q.2931
+**Broadband locking shift information element**
+
+TABLE 4-4/Q.2931
+**Broadband locking shift information element**
+
+| - New codeset identification (octet 5) | | | |
+|----------------------------------------|---|---|------------------------------------------------------------------------------------------|
+| Bits | | | |
+| 3 | 2 | 1 | |
+| 0 | 0 | 0 | not applicable |
+| 0 | 0 | 1 | reserved |
+| to | | | |
+| 0 | 1 | 1 | |
+| 1 | 0 | 0 | codeset 4: information elements for ISO/IEC use |
+| 1 | 0 | 1 | codeset 5: information elements for national use |
+| 1 | 1 | 0 | codeset 6: information elements specific to the local network (either public or private) |
+| 1 | 1 | 1 | codeset 7: user-specific information elements |
+
+### 4.5.4 Broadband non-locking shift procedure
+
+The broadband non-locking shift procedure provides a temporary shift to the specified lower or higher codeset. The broadband non-locking shift procedure uses a broadband non-locking shift information element to indicate the codeset to be used to interpret the next single information element. After the interpretation of the next single information element, the active codeset is again used for interpreting any following information elements. For example, codeset 0 is active at the beginning of message contents analysis. If a broadband non-locking shift to codeset 6 is encountered, only the next information element is interpreted according to the information element identifiers assigned in codeset 6. After this information element is interpreted, codeset 0 will again be used to interpret the following information elements. A broadband non-locking shift information element indicating the current codeset shall not be regarded as an error.
+
+A broadband locking shift information element shall not follow directly on a broadband-non-locking shift information element. If this combination is received, it shall be interpreted as though a broadband locking shift information element only had been received.
+
+The broadband non-locking shift information element uses the information element format and coding shown in Figure 4-11 and Table 4-5.
+
+
+
+| Bits | | | | | | | | Octets |
+|------------------------------------------------|-----------------|---|----------------------|---|----------------------------------|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Broadband-non-locking shift | | | | | | | | 1 |
+| 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | |
+| Information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | | IE instruction field | | | | | |
+| Length of Broadband-non-locking shift contents | | | | | | | | 3 |
+| | | | | | | | | 4 |
+| 1 ext. | Spare | | | | Temporary codeset identification | | | 5 |
+| | 0 | 0 | 0 | 0 | | | | |
+
+T1162650-94/d011
+
+FIGURE 4-11/Q.2931
+Broadband-non-locking shift information element
+
+TABLE 4-5/Q.2931
+Broadband non-locking shift information element
+
+| | | | |
+|------|---|---|------------------------------------------------------------------------------------------|
+| Bits | | | Temporary codeset identification (octet 5) |
+| 3 | 2 | 1 | |
+| 0 | 0 | 0 | codeset 0 (initially active): Q.2931 information elements |
+| 0 | 0 | 1 | reserved |
+| to | | | |
+| 0 | 1 | 1 | |
+| 1 | 0 | 0 | codeset 4: information elements for ISO/IEC use |
+| 1 | 0 | 1 | codeset 5: information elements for national use |
+| 1 | 1 | 0 | codeset 6: information elements specific to the local network (either public or private) |
+| 1 | 1 | 1 | codeset 7: user-specific information elements |
+
+#### 4.5.5 ATM adaptation layer parameters
+
+The purpose of the ATM adaptation layer (AAL) parameters information element is to indicate the requested AAL parameter values (end-to-end significance) for the ATM adaptation layer elements of procedures to be used for the call. It contains the parameters selectable by the user for all AAL sublayers.
+
+The contents of this information element is transparent for the network, except for the case of interworking.
+
+The maximum length of this information element is 21 octets.
+
+The AAL parameters information element is coded as shown in Figure 4-12 and Table 4-6.
+
+
+
+| Bits | | | | | | | | Octets |
+|----------------------------------|-----------------|---|----------------------|------|----------------|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| AAL parameters | | | | | | | | 1 |
+| 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | |
+| Information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | | IE instruction field | | | | | |
+| | | | Flag | Res. | IE action ind. | | | 3 |
+| Length of AAL parameter contents | | | | | | | | |
+| | | | | | | | | 4 |
+| AAL type | | | | | | | | 5 |
+
+Further contents depending on AAL type
+(see below)
+
+T1162660-94/d012
+
+FIGURE 4-12/Q.2931 (part 1 of 5)
+**AAL parameters information element**
+
+(further contents for AAL type 1)
+
+| Bits | | | | | | | | Octets |
+|---------------------------------------------------|---|---|---|---|---|---|---|-------------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Subtype identifier | | | | | | | | 6 |
+| 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | |
+| Subtype | | | | | | | | 6.1 |
+| CBR rate identifier | | | | | | | | 7 |
+| 1 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | |
+| CBR rate | | | | | | | | 7.1 |
+| Multiplier identifier | | | | | | | | 8* (Note) |
+| 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | |
+| Multiplier | | | | | | | | 8.1* (Note) |
+| | | | | | | | | 8.2* (Note) |
+| Source clock frequency recovery method identifier | | | | | | | | 9* |
+| 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | |
+| Source clock frequency recovery method | | | | | | | | 9.1* |
+| Error correction method identifier | | | | | | | | 10* |
+| 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | |
+| Error correction method | | | | | | | | 10.1* |
+| Structured data transfer block size identifier | | | | | | | | 11* |
+| 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | |
+| Structured data transfer block size | | | | | | | | 11.1* |
+| | | | | | | | | 11.2* |
+| Partially filled cells method identifier | | | | | | | | 12* |
+| 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | |
+| Partially filled cells method | | | | | | | | 12.1* |
+
+T1162670-94/d013
+
+NOTE – These octets are only present if octet 7.1 indicates “ $n \times 64$ kbit/s or $n \times 8$ kbit/s”.
+
+FIGURE 4-12/Q.2931 (part 2 of 5)
+**AAL parameters information element**
+
+(further contents for AAL type 3/4).
+
+| Bits | | | | | | | | Octets |
+|-------------------------------------------|---|---|---|---|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Forward maximum CPCS-SDU size identifier | | | | | | | | |
+| 1 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 6* |
+| Forward maximum CPCS-SDU size | | | | | | | | 6.1* |
+| | | | | | | | | 6.2* |
+| Backward maximum CPCS-SDU size identifier | | | | | | | | |
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 7* |
+| Backward maximum CPCS-SDU size | | | | | | | | 7.1* |
+| | | | | | | | | 7.2* |
+| MID range identifier | | | | | | | | |
+| 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 8* |
+| MID range (lowest MID value) | | | | | | | | 8.1* |
+| | | | | | | | | 8.2* |
+| | | | | | | | | 8.3* |
+| MID range (highest MID value) | | | | | | | | 8.4* |
+| | | | | | | | | |
+| SSCS-type identifier | | | | | | | | |
+| 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 9* |
+| SSCS-type | | | | | | | | 9.1* |
+
+T1162680-94/d014
+
+NOTE – The indication of values for octet groups 6-8 for use in the CONNECT message is specified in Annex F.
+
+FIGURE 4-12/Q.2931 (part 3 of 5)
+**AAL parameters information element**
+
+(further contents for AAL type 5)
+
+| Bits | | | | | | | | Octets |
+|-------------------------------------------|---|---|---|---|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Forward maximum CPCS-SDU size identifier | | | | | | | | 6* |
+| 1 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | |
+| Forward maximum CPCS-SDU size | | | | | | | | 6.1* |
+| | | | | | | | | 6.2* |
+| Backward maximum CPCS-SDU size identifier | | | | | | | | 7* |
+| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | |
+| Backward maximum CPCS-SDU size | | | | | | | | 7.1* |
+| | | | | | | | | 7.2* |
+| SSCS-type identifier | | | | | | | | 8* |
+| 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | |
+| SSCS-type | | | | | | | | 8.1* |
+
+T1162690-94/d015
+
+NOTE – The indication of values for octet groups 6-7 for use in the CONNECT message is specified in Annex F.
+
+FIGURE 4-12/Q.2931 (part 4 of 5)
+**AAL parameters information element**
+
+(further contents for User-defined AAL)
+
+| Bits | | | | | | | | Octets |
+|------------------------------|---|---|---|---|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| User defined AAL information | | | | | | | | 5.1* |
+| User defined AAL information | | | | | | | | 5.2* |
+| User defined AAL information | | | | | | | | 5.3* |
+| User defined AAL information | | | | | | | | 5.4* |
+
+T1162700-94/d016
+
+FIGURE 4-12/Q.2931 (part 5 of 5)
+**AAL parameters information element**
+
+TABLE 4-6/Q.2931 (sheet 1 of 3)
+
+#### **AAL parameters information element**
+
+| | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|----------------------------------------------------------------------------------------------------------------------|
+| – AAL type (octet 5) | | | | | | | | |
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | AAL for voice (Note 1, Note 2) |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | AAL type 1 |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | AAL type 2 (Note 2) |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | AAL type 3/4 |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | AAL type 5 |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | user defined AAL |
+| All other values are reserved. | | | | | | | | |
+| NOTE 1 – The default AAL for voice is the AAL specified in Recommendation I.363 for voice-band signal transport based on 64 kbit/s (see Recs. G.711/G.722). | | | | | | | | |
+| NOTE 2 – For AAL type 2 and AAL for voice, no further parameters are specified beyond the ones given in part 1 of 5 of Figure 4-12. | | | | | | | | |
+| – Subtype (octet 6.1 for AAL type 1) | | | | | | | | |
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | voice-band signal transport based on 64 kbit/s (see Recs. G.711/G.722) (for further study, see Recommendation I.363) |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | circuit transport (see 2.5.1.1/I.363) |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | high-quality audio signal transport (for further study, see Recommendation I.363) |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | video signal transport (for further study, see Recommendation I.363) |
+| All other values are reserved. | | | | | | | | |
+| – CBR rate (octet 7.1 for AAL type 1) | | | | | | | | |
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 64 kbit/s |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 544 kbit/s |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 6 312 kbit/s |
+| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 32 064 kbit/s |
+| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 44 736 kbit/s |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 97 728 kbit/s |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 2 048 kbit/s |
+| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 8 448 kbit/s |
+| 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 34 368 kbit/s |
+| 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 139 264 kbit/s |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | $n \times 64$ kbit/s |
+| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | $n \times 8$ kbit/s |
+| All other values are reserved. | | | | | | | | |
+
+TABLE 4-6/Q.2931 (sheet 2 of 3)
+
+#### **AAL parameters information element**
+
+– Multiplier (octets 8.1 and 8.2 for AAL type 1 and $n \times 64$ kbit/s or $n \times 8$ kbit/s indication in octet 7.1)
+
+Integer representation of multiplier values between 2 and $2^{16} - 1$ for $n \times 64$ kbit/s.
+
+Integer representation of multiplier values between 1 and 7 for $n \times 8$ kbit/s.
+
+– Source clock frequency recovery method (octet 9.1 for AAL type 1)
+
+Bits
+
+| | | | | | | | | |
+|---|---|---|---|---|---|---|---|------------------------------------------------------------------------------------------------------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null (synchronous circuit transport) |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Synchronous Residual Time Stamp (SRTS) method (asynchronous circuit transport) (see 2.5.2.2.1/I.363) |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | adaptive clock method (see 2.5.2.2.1/I.363) |
+
+All other values are reserved.
+
+– Error correction method (octet 10.1 for AAL type 1)
+
+Bits
+
+| | | | | | | | | |
+|---|---|---|---|---|---|---|---|----------------------------------------------------------------------------------------------------------------------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null (no error correction is provided) |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | a forward error correction method for loss sensitive signal transport (see Recommendation I.363) |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | a forward error correction method for delay sensitive signal transport (for further study, see Recommendation I.363) |
+
+All other values are reserved.
+
+– Structured data transfer block size (octet 11.1 and 11.2 for AAL type 1)
+
+16 bit integer representation of values between 1 and 65 535, i.e. $2^{16} - 1$ . This parameter represents the block size of SDT CBR service.
+
+NOTE 3 – When provisioning ATM connections that support AAL type 1 SDT service, the SDT protocol may distinguish between SDT block sizes with a value of “1” and SDT block sizes ranging from 2 to $2^{16} - 1$ . The special case using a block size of “1” is under study; see Recommendation I.363.
+
+– Partially filled cells method (octet 12.1 for AAL type 1)
+
+Bits
+
+| | | | | | | | | | |
+|---|---|---|----|---|---|---|---|---|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | } | Integer representation of the number of leading octets of SAR-PDU payload in use (values between 1 and 47) (for further study, see Recommendation I.363) |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | | |
+| | | | to | | | | | | |
+| 0 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | | |
+
+– Forward maximum CPCS-SDU size (octets 6.1 and 6.2 for AAL type 3/4 and 5)
+
+16 bit integer representation of the values between 0 and 65 535, i.e. $2^{16} - 1$ . This parameter refers to the forward direction (calling user to called user, see Annex J).
+
+– Backward maximum CPCS-SDU size (octets 7.1 and 7.2 for AAL type 3/4 and 5)
+
+16 bit integer representation of the values between 0 and 65 535, i.e. $2^{16} - 1$ . This parameter refers to the backward direction (called user to calling user, see Annex J).
+
+– MID range (octets 8.1, 8.2, 8.3 and 8.4 for AAL type 3/4)
+
+Integer representation of the lowest MID value (octets 8.1 and 8.2) and of the highest MID value (octets 8.3 and 8.4) of the MID range, only values between 0 and 1023.
+
+TABLE 4-6/Q.2931 (sheet 3 of 3)
+
+#### **AAL parameters information element**
+
+| | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|--------------------------------------------------|
+| – SSCS type (octet 9.1 for AAL type 3/4; octet 8.1 for AAL type 5) | | | | | | | | |
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | null |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | data SSCS based on SSCOP (assured operation) |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | data SSCS based on SSCOP (non-assured operation) |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | frame relay SSCS |
+| All other values are reserved. | | | | | | | | |
+| – User defined AAL information (octets 5.1 to 5.4 for user defined AAL) | | | | | | | | |
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| The contents of this field are user-specified. | | | | | | | | |
+| NOTE 4 – In case of the absence of AAL parameter subfields, the following default values will apply: | | | | | | | | |
+| - – Subtype: no default (mandatory for AAL type 1).
- – CBR Rate: no default (mandatory for AAL type 1).
- – Multiplier: no default (mandatory for CBR Rate kbit/s and kbit/s).
- – Clock Frequency Recovery: default = null.
- – Error Correction: default = null.
- – SDT Block Size: default = no SDT is used.
- – Partially Filled Cells: default = 47 octets.
- – Forward max. CPCS-SDU size: default = 65 535 octets.
- – Backward max. CPCS-SDU size: default = 65 535 octets.
- – MID range: default = 0-0 (no multiplexing via MID field).
- – SSCS-Type: default = null.
| | | | | | | | |
+
+#### **4.5.6 ATM traffic descriptor**
+
+The purpose of the ATM traffic descriptor information element is to specify the set of traffic parameters which, together, specify a traffic control capability.
+
+In Release 1, the ATM peak cell rate (see Recommendation I.371) values are indicated by the ATM traffic descriptor. The ATM peak cell rate values (indicated in the ATM traffic descriptor information element) specify the sum of both the user plane information rate and all end-to-end user originated OAM F5 flow.
+
+If the user intends to use end-to-end OAM F5 flow messages, the peak cell rate for the reverse direction of a unidirectional connection should not be indicated with the value “0”.
+
+The peak cell rate is described using subfield identifiers followed by a pure 3 octet integer representation of the cells per second.
+
+The ATM traffic descriptor information element is coded as shown in Figure 4-13 and Table 4-7. The maximum length of this information element is 20 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|--------------------------------------------------|-----------------|----------------------|------|---|---|---|----------------|------------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| ATM traffic descriptor | | | | | | | | 1 |
+| 0 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | |
+| Information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | | | | IE action ind. | 3 |
+| Length of ATM traffic descriptor contents | | | | | | | | 4 |
+| Forward peak cell rate identifier (CLP = 0) | | | | | | | | 5 (Note 1) |
+| 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 5.1 |
+| Forward peak cell rate (for CLP = 0) | | | | | | | | 5.2 |
+| | | | | | | | | 5.3 |
+| Backward peak cell rate identifier (CLP = 0) | | | | | | | | 6 (Note 1) |
+| 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 6.1 |
+| Backward peak cell rate (for CLP = 0) | | | | | | | | 6.2 |
+| | | | | | | | | 6.3 |
+| Forward peak cell rate identifier (CLP = 0 + 1) | | | | | | | | (Note 2) |
+| 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 7 |
+| Forward peak cell rate (for CLP = 0 + 1) | | | | | | | | 7.1 |
+| | | | | | | | | 7.2 |
+| | | | | | | | | 7.3 |
+| Backward peak cell rate identifier (CLP = 0 + 1) | | | | | | | | 8 (Note 2) |
+| 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 8.1 |
+| Backward peak cell rate (for CLP = 0 + 1) | | | | | | | | 8.2 |
+| | | | | | | | | 8.3 |
+
+T1162710-94/d017
+
+##### NOTES
+
+- 1 If peak cell rate for CLP = 0 is present, the network resource allocation shall assume that the difference between the indicated peak cell rate for CLP = 0 + and the peak cell rate for CLP = 0 may be used for CLP = 1.
+- 2 If only Peak cell rate for CLP = 0 + 1 is specified, the network resource allocation shall assume that the entire peak cell rate can be used for CLP = 0.
+
+FIGURE 4-13/Q.2931
+**ATM traffic descriptor information element**
+
+TABLE 4-2/Q.2931
+
+#### **ATM traffic descriptor information element**
+
+– Forward/backward peak cell rate (octets i.1-i.3, where i may have the values 5, 6, 7, or 8)
+
+A code expressing in pure 3 octet integer representation the number of cells per second, with bit 8 of the first octet being the most significant bit, and bit 1 of the third octet being the least significant bit.
+
+The “forward” direction is defined as that from the calling user to the called user.
+
+The “backward” direction is the reverse, i.e. from the called user to the calling user (see Annex J).
+
+#### **4.5.7 Broadband bearer capability**
+
+The purpose of the broadband bearer capability information element is to indicate a requested broadband connection-oriented bearer service (see Recommendation F.811) to be provided by the network. It contains only information that may be used by the network. The use of the broadband bearer capability information element in relation to compatibility checking is described in Annex B.
+
+No default broadband bearer capability may be assumed by the absence of this information element.
+
+The broadband bearer capability information element will be examined by both the network and the customer equipment.
+
+The broadband bearer capability information element is coded as shown in Figure 4-14 and Table 4-8. The maximum length of this information element is 7 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|----------------------------------------------------------------------------------|----------------------------|----------------|--------------------------------------------------|---|---------------------|---|---|------------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Broadband bearer capability
0 1 0 1 1 1 1 0
information element identifier | | | | | | | | 1 |
+| 1 ext. | Coding standard | | IE instruction field
Flag Res. IE action ind. | | | | | 2 |
+| Length of the broadband bearer capability contents | | | | | | | | 3 |
+| 0/1 ext. | 0 0
Spare | Bearer class | | | | | | 4 |
+| 1 ext. | 0 0
Spare | Traffic type | | | Timing requirements | | | 5a* (Note) |
+| 1 ext. | Susceptibility to clipping | 0 0 0
Spare | User-plane connection configuration | | | | | 6 |
+
+T1162720-94/d018
+
+NOTE – This octet may only be present if Bearer Class “X” is indicated in octet 5.
+
+FIGURE 4-14/Q.2931
+
+#### **Broadband bearer capacity information element**
+
+TABLE 4-8/Q.2931
+
+#### **Broadband bearer capability information element**
+
+– Bearer class (octet 5)
+
+Bits
+
+5 4 3 2 1
+
+0 0 0 0 1 BCOB-A
+
+0 0 0 1 1 BCOB-C (Note 1)
+
+1 0 0 0 0 BCOB-X
+
+All other values are reserved.
+
+– Traffic type (octet 5a)
+
+Bits
+
+5 4 3
+
+0 0 0 no indication
+
+0 0 1 constant bit rate
+
+0 1 0 variable bit rate
+
+All other values are reserved.
+
+– Timing requirements (octet 5a)
+
+Bits
+
+2 1
+
+0 0 no indication
+
+0 1 end-to-end timing required
+
+1 0 end-to-end timing not required
+
+1 1 reserved
+
+– Susceptibility to clipping (octet 6)
+
+Bits
+
+7 6
+
+0 0 not susceptible to clipping
+
+0 1 susceptible to clipping
+
+All other values are reserved.
+
+– User-plane connection configuration (octet 6)
+
+Bits
+
+2 1
+
+0 0 point-to-point
+
+0 1 point-to-multipoint (Note 2)
+
+All other values are reserved.
+
+##### **NOTES**
+
+1 If bearer class BCOB-C is indicated, the network may allocate resources, as if bearer class BCOB-A was requested, and allocate resources on the basis of the peak cell rate only.
+
+2 Procedures for point-to-multipoint connections are not provided in Release 1. However, the support of this codepoint may allow a user to participate via a point-to-point connection segment in a point-to-multipoint connection (e.g. when a user, implementing Release 1 procedures, receives a SETUP message with the user-plane connection configuration coding set to “point-to-multipoint”, it shall treat it as if the coding were “point-to-point”. This will allow the user to be a “leaf” of a point-to-multipoint connection).
+
+#### 4.5.8 Broadband High Layer Information
+
+The purpose of the broadband high layer information information element is to provide a means which should be used for compatibility checking by an addressed entity (e.g. a remote user, an interworking unit or a high layer function network node addressed by the calling user). The broadband high layer information information element is transferred transparently by a B-ISDN between the call originating entity (e.g. the calling user) and the addressed entity.
+
+The broadband high layer information information element is coded as shown in Figure 4-15 and in Table 4-9. The maximum length of this information element is 13 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|---------------------------------------------------------|-----------------------------|----------------------|------|----------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Broadband high layer information | | | | | | | | 1 |
+| 0 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of the broadband high layer information contents | | | | | | | | |
+| | | | | | | | | 4 |
+| 1 ext. | High layer information type | | | | | | | 5 |
+| High layer information | | | | | | | | 6-13* |
+
+T1162730-94/d019
+
+FIGURE 4-15/Q.2931
+**Broadband high layer information**
+
+TABLE 4-9/Q.2931
+
+#### **Broadband high layer information**
+
+| | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|--------------------------------------------------------------------|
+| – High layer information type (octet 5) | | | | | | | |
+| Bits | | | | | | | |
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | ISO/IEC (Note 1) |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | user-specific (Note 2) |
+| 0 | 0 | 0 | 0 | 0 | 1 | 1 | vendor-specific application identifier (Note 3) |
+| 0 | 0 | 0 | 0 | 1 | 0 | 0 | reference to ITU-T SG 1 B-ISDN teleservice recommendation (Note 4) |
+| Other values reserved. | | | | | | | |
+| NOTES | | | | | | | |
+| 1 This codepoint is reserved for use as specified in ISO/IEC standards. | | | | | | | |
+| 2 The exact coding of octets 6-13, when this higher layer information type is used, is user-defined. The use of this codepoint requires bilateral agreement between the two end users. | | | | | | | |
+| 3 When this high layer information type is used, octets 6-12 are coded as follows: octets 6-8 contain a globally-administered Organizationally Unique Identifier (OUI) (as specified in IEEE 802-1990; section 5.1); octet 0 of the OUI is mapped to octet 6 of the broadband high layer information, and so on; the LSB of the OUI is mapped to bit 8 of the B-HLI, the MSB of the OUI is mapped to bit 1 of the B-HLI; bit 7 of octet 6 is always set to “0”; octets 9-12 contain an application identifier which is administered by the vendor identified by the OUI. | | | | | | | |
+| Octet 13 is not used for this high layer information type. | | | | | | | |
+| 4 Codepoints for these Recommendations will be indicated in octet 6. The specific codepoints will be added at the time when ITU-T SG 1 has completed the corresponding Recommendations. | | | | | | | |
+| – High layer information (octets 6-13) | | | | | | | |
+| The content of these octets depends on the high layer information type. | | | | | | | |
+
+#### **4.5.9 Broadband Low Layer Information**
+
+The purpose of the broadband low layer information information element is to provide a means which should be used for compatibility checking by an addressed entity (e.g. a remote user or an interworking unit or a high layer function network node addressed by the calling user). The broadband low layer information information element is transferred transparently by a B-ISDN between the call originating entity (e.g. the calling user) and the addressed entity.
+
+For broadband low layer information negotiation (see Annex C), the broadband low layer information information element is also passed transparently from the addressed entity to the originating entity.
+
+The broadband low layer information information element is coded as shown in Figure 4-16 and in Table 4-10. The maximum length of this information element is 17 octets.
+
+| Bits | | | | | | | | Octets | | | | |
+|--------------------------------------------------------|---------------------------------------------|-------------|----------------------|-----------------------------------|---|-----------|---|-----------------|--|--|--|--|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | |
+| Broadband low layer information | | | | | | | | | | | | |
+| 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | | | | |
+| information element identifier | | | | | | | | | | | | |
+| 1 ext. | Coding standard | | IE instruction field | | | | | 2 | | | | |
+| | | Flag | Res. | IE action ind. | | | | | | | | |
+| Length of the broadband low layer information contents | | | | | | | | 3 | | | | |
+| | | | | | | | | 4 | | | | |
+| 1 ext. | 0 1 | Layer 1 id. | | User information layer 1 protocol | | | | 5* | | | | |
+| 0/1 ext. | 1 0 | Layer 2 id. | | User information layer 2 protocol | | | | 6* | | | | |
+| 0/1 ext. | Mode | | 0 | 0 | 0 | Q.933 use | | 6a*
(Note 1) | | | | |
+| 1 ext. | Window size (k) | | | | | | | 6b*
(Note 1) | | | | |
+| 1 ext. | User specified layer 2 protocol information | | | | | | | 6a*
(Note 2) | | | | |
+| 0/1 ext. | 1 1 | Layer 3 id. | | User information layer 3 protocol | | | | 7* | | | | |
+| 0/1 ext. | Mode | | 0 | 0 | 0 | 0 | 0 | 7a*
(Note 3) | | | | |
+| 0/1 ext. | 0 | 0 | 0 | Default packet size | | | | 7b*
(Note 3) | | | | |
+| 1 ext. | Packet window size | | | | | | | 7c*
(Note 3) | | | | |
+| 1 ext. | User-specified layer 3 protocol information | | | | | | | 7a*
(Note 4) | | | | |
+
+T1162740-94/d20
+
+FIGURE 4-16/Q.2931 (part 1 of 2)
+**Broadband low layer information**
+
+| | |
+|--------------------------------------------|------------------|
+| Additional layer 3
protocol information | 7.1*
(Note 5) |
+| (cont.) | 7.2*
(Note 5) |
+| (cont.) | 7.3*
(Note 5) |
+| (cont.) | 7.4*
(Note 5) |
+| (cont.) | 7.5*
(Note 5) |
+| (cont.) | 7.6*
(Note 5) |
+| (cont.) | 7.7*
(Note 5) |
+| (cont.) | 7.8*
(Note 5) |
+
+T1162750-94/d021
+
+##### NOTES
+
+- 1 This octet may be present only if octet 6 indicates certain HDLC acknowledged-mode elements of procedure as indicated in Table 4-10.
+- 2 This octet may be present only if octet 6 indicates user-specified layer 2 protocol.
+- 3 This octet may be present only if octet 7 indicates a layer 3 protocol based on Recommendation X.25, ISO/IEC 8208 or X.223/ISO/IEC 8878 as indicated in Table 4-10.
+- 4 This octet may be present only if octet 7 indicates user specified layer 3 protocol.
+- 5 These octets may be present only if octet 7 indicates ISO/IEC TR 9577.
+
+FIGURE 4-16/Q.2931 (part 2 of 2)
+**Broadband low layer information**
+
+TABLE 4-10/Q.2931 (sheet 1 of 3)
+
+#### **Broadband low layer information element**
+
+– User information layer 1 protocol (octet 5)
+
+All values are reserved.
+
+– User information layer 2 protocol (octet 6)
+
+Bits
+
+| 5 | 4 | 3 | 2 | 1 | |
+|---|---|---|---|---|-----------------------------------------------------------------|
+| 0 | 0 | 0 | 0 | 1 | Basic mode ISO 1745 |
+| 0 | 0 | 0 | 1 | 0 | ITU-T Recommendation Q.921 (Rec. I.441) |
+| 0 | 0 | 1 | 1 | 0 | ITU-T Recommendation X.25, link layer (Note 1, Note 4) |
+| 0 | 0 | 1 | 1 | 1 | ITU-T Recommendation X.25 multilink (Note 4) |
+| 0 | 1 | 0 | 0 | 0 | extended LAPB; for half-duplex operation (Rec. T.71) |
+| 0 | 1 | 0 | 0 | 1 | HDLC ARM (ISO/IEC 4335) (Note 4) |
+| 0 | 1 | 0 | 1 | 0 | HDLC NRM (ISO/IEC 4335) (Note 4) |
+| 0 | 1 | 0 | 1 | 1 | HDLC ABM (ISO/IEC 4335) (Note 4) |
+| 0 | 1 | 1 | 0 | 0 | LAN logical link control (ISO/IEC 8802-2) |
+| 0 | 1 | 1 | 0 | 1 | ITU-T Recommendation X.75. Single Link Procedure (SLP) (Note 4) |
+| 0 | 1 | 1 | 1 | 0 | ITU-T Recommendation Q.922 (Note 4) |
+| 1 | 0 | 0 | 0 | 0 | user-specified (Note 2) |
+| 1 | 0 | 0 | 0 | 1 | ISO/IEC 7776 DTE-DTE operation (Note 3, Note 4) |
+
+All other values are reserved.
+
+NOTE 1 – This Recommendation is compatible with ISO/IEC 7776 DTE-DCE operation.
+
+NOTE 2 – When this coding is included, octet 6a will include user coding for the user-specified layer 2 protocol.
+
+NOTE 3 – This standard is compatible with Recommendation X.75 modified by the application rules defined in Recommendation T.90.
+
+NOTE 4 – When this coding is included, octets 6a and 6b with ITU-T encoding may be included.
+
+– Octet 6a for ITU-T codings
+
+– Mode of operation (octet 6a)
+
+Bits
+
+| 7 | 6 | |
+|---|---|----------------------------|
+| 0 | 1 | normal mode of operation |
+| 1 | 0 | extended mode of operation |
+
+All other values are reserved.
+
+– Q.933 use (octet 6a)
+
+Bits
+
+| 2 | 1 | |
+|---|---|---------------------------------------------------------------------|
+| 0 | 0 | for use when the coding defined in Recommendation Q.933 is not used |
+
+All other values are reserved.
+
+– Octet 6a for user protocol
+
+– User-specified layer 2 protocol information (octet 6a)
+
+The use and coding of octet 6a is according to user defined requirements.
+
+TABLE 4-10/Q.2931 (sheet 2 of 3)
+
+#### **Broadband low layer information element**
+
+– Window size (k) (octet 6b)
+
+Bits 7 to 1 are coded as a binary coding of k parameter value in the range from 1 to 127.
+
+– User information layer 3 protocol (octet 7)
+
+Bits
+
+| 5 | 4 | 3 | 2 | 1 | |
+|---|---|---|---|---|------------------------------------------------------------------------------------------------------|
+| 0 | 0 | 1 | 1 | 0 | ITU-T Recommendation X.25, packet layer (Note 6) |
+| 0 | 0 | 1 | 1 | 1 | ISO/IEC 8208 (X.25 packet level protocol for data terminal equipment) (Note 6) |
+| 0 | 1 | 0 | 0 | 0 | Rec. X.223 ISO/IEC 8878 (use of ISO/IEC 8208 and ITU-T Rec. X.25 to provide the OSI-CONS) (Note 6) |
+| 0 | 1 | 0 | 0 | 1 | Rec. X.233 ISO/IEC 8473 (OSI connectionless mode protocol) |
+| 0 | 1 | 0 | 1 | 0 | ITU-T Recommendation T.70 [40] minimum network layer |
+| 0 | 1 | 0 | 1 | 1 | ISO/IEC TR 9577 (Note 7) |
+| 1 | 0 | 0 | 0 | 0 | user-specified (Note 5) |
+
+All other values are reserved.
+
+NOTE 5 – When this coding is included, octet 7a will include user coding for the user-specified layer 3 protocol.
+
+NOTE 6 – When this coding is included, octets 7a, 7b and 7c with ITU-T encoding may be included.
+
+NOTE 7 – If extension octets (7.1-7.8) are included, they will identify the layer 3 protocol identification according to ISO/IEC TR 9577 (e.g. see Annexes C and D of ISO/IEC TR 9577); otherwise, the Network Layer Protocol Identification (NLPID) carried on a connection, as defined in ISO/IEC TR 9577, is supported.
+
+– Octet 7a for ITU-T codings
+
+– Mode of operation (octet 7a)
+
+Bits
+
+| 7 | 6 | |
+|---|---|------------------------------------|
+| 0 | 1 | normal packet-sequence numbering |
+| 1 | 0 | extended packet-sequence numbering |
+
+All other values are reserved.
+
+– Octet 7a for user protocol
+
+– User-specified layer 3 protocol information (octet 7a)
+
+The use and coding of octet 7a is according to user defined requirements.
+
+TABLE 4-10/Q.2931 (sheet 3 of 3)
+
+#### **Broadband low layer information element**
+
+| | | | | |
+|-----------------------------------------------------------------------------------------------------------------|---|---|---|---------------------------------|
+| – Default packet size (octet 7b) | | | | |
+| Bits | | | | |
+| 4 | 3 | 2 | 1 | |
+| 0 | 1 | 0 | 0 | default packet size 16 octets |
+| 0 | 1 | 0 | 1 | default packet size 32 octets |
+| 0 | 1 | 1 | 0 | default packet size 64 octets |
+| 0 | 1 | 1 | 1 | default packet size 128 octets |
+| 1 | 0 | 0 | 0 | default packet size 256 octets |
+| 1 | 0 | 0 | 1 | default packet size 512 octets |
+| 1 | 0 | 1 | 0 | default packet size 1024 octets |
+| 1 | 0 | 1 | 1 | default packet size 2048 octets |
+| 1 | 1 | 0 | 0 | default packet size 4096 octets |
+| All other values are reserved. | | | | |
+| – Packet window size (octet 7c) | | | | |
+| Bits 7 to 1 are coded as a binary coding of packet window size value in the range from 1 to 127. | | | | |
+| – Additional layer 3 protocol information (octets 7.1-7.8) for ISO/IEC TR 9577: as specified in ISO/IEC TR 9577 | | | | |
+
+#### **4.5.10 Call state**
+
+The purpose of the call state information element is to describe the current status of a call/connection (see 2.1), or of a call/connection with regard to interworking (see 2.2) or of a call/connection with regard to the global call reference (see 2.3).
+
+The call state information element is coded as shown in Figure 4-17 and Table 4-11.
+
+The maximum length of this information element is 5 octets when ITU-T standard coding is used.
+
+
+
+| | | | | | | | | | | | | |
+|--|--------------------------------|-----------------|------------------------------------------------|----------------------|------|----------------|---|------|--------|--|--|--|
+| | | | | | | | | Bits | | | | |
+| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets | | | |
+| | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | | | |
+| | information element identifier | | | | | | | | | | | |
+| | 1 ext. | Coding standard | | IE instruction field | | | | | 2 | | | |
+| | | | | Flag | Res. | IE action ind. | | | | | | |
+| | Length of Call state contents | | | | | | | | 3 | | | |
+| | | | | | | | | | 4 | | | |
+| | 0 | 0 | Call state value/ global interface state value | | | | | | 5 | | | |
+| | Spare | | | | | | | | | | | |
+
+T1162760-94/d022
+
+FIGURE 4-17/Q.2931
+**Call state information element**
+
+TABLE 4-11/Q.2931
+
+#### **Call state information element**
+
+| – Call state value (octet 5) | | | | | | | |
+|------------------------------------------|---|---|---|---|---|-------------------------------|-------------------------------|
+| Bits | | | | | | | |
+| 6 | 5 | 4 | 3 | 2 | 1 | User state | Network state |
+| 0 | 0 | 0 | 0 | 0 | 0 | U0 – Null | N0 – Null |
+| 0 | 0 | 0 | 0 | 0 | 1 | U1 – Call Initiated | N1 – Call Initiated |
+| 0 | 0 | 0 | 0 | 1 | 0 | U2 – Overlap Sending | N2 – Overlap Sending |
+| 0 | 0 | 0 | 0 | 1 | 1 | U3 – Outgoing Call Proceeding | N3 – Outgoing Call Proceeding |
+| 0 | 0 | 0 | 1 | 0 | 0 | U4 – Call Delivered | N4 – Call Delivered |
+| 0 | 0 | 0 | 1 | 1 | 0 | U6 – Call Present | N6 – Call Present |
+| 0 | 0 | 0 | 1 | 1 | 1 | U7 – Call Received | N7 – Call Received |
+| 0 | 0 | 1 | 0 | 0 | 0 | U8 – Connect Request | N8 – Connect Request |
+| 0 | 0 | 1 | 0 | 0 | 1 | U9 – Incoming Call Proceeding | N9 – Incoming Call Proceeding |
+| 0 | 0 | 1 | 0 | 1 | 0 | U10 – Active | N10 – Active |
+| 0 | 0 | 1 | 0 | 1 | 1 | U11 – Release Request | N11 – Release Request |
+| 0 | 0 | 1 | 1 | 0 | 0 | U12 – Release Indication | N12 – Release Indication |
+| 0 | 1 | 1 | 0 | 0 | 1 | U25 – Overlap Receiving | N25 – Overlap Receiving |
+| – Global interface state value (octet 5) | | | | | | | |
+| Bits | | | | | | | |
+| 6 | 5 | 4 | 3 | 2 | 1 | State | |
+| 0 | 0 | 0 | 0 | 0 | 0 | REST 0 – Null | |
+| 1 | 1 | 1 | 1 | 0 | 1 | REST 1 – Restart Request | |
+| 1 | 1 | 1 | 1 | 1 | 0 | REST 2 – Restart | |
+| All other values are reserved. | | | | | | | |
+
+#### **4.5.11 Called party number**
+
+The purpose of the called party number information element is to identify the called party of a call.
+
+The called party number information element is coded as shown in Figure 4-18 and Table 4-12.
+
+The maximum length of this information element is network dependent.
+
+
+
+Bits
+
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets |
+|----------------------------------------|----------------------------------------|----------------------|------------------------------------------|----------------|---|---|---|-----------------|
+| Called party number | | | | | | | | 1 |
+| 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of called party number contents | | | | | | | | |
+| | | | | | | | | 4 |
+| 1 ext. | Type of number | | Addressing/numbering plan identification | | | | | 5 |
+| 0 | Address/number digits (IA5 characters) | | | | | | | 6 etc. (Note 1) |
+| NSAP address octets | | | | | | | | 6 etc. (Note 2) |
+
+T1162770-94/d023
+
+##### NOTES
+
+1 The number digits appear in multiple octet 6's in the same order in which they would be entered, that is, the number digit which would be entered first is located in the first octet 6. Digits are coded in IA5 characters. Bit 8 is set to 0.
+
+2 If the use of NSAP addressing is indicated in the addressing/numbering plan identification, the address is coded as described in Rec. X.213 | ISO/IEC 8348.
+
+FIGURE 4-18/Q.2931
+**Called party number information element**
+
+TABLE 4-12/Q.2931
+
+#### **Called party number information element**
+
+– Type of number (octet 5)
+
+Bits
+
+| 7 | 6 | 5 | |
+|---|---|---|-----------------------------------------------|
+| 0 | 0 | 0 | unknown (Note 2) |
+| 0 | 0 | 1 | international number (Note 1, Note 3, Note 6) |
+| 0 | 1 | 0 | national number (Note 1, Note 3, Note 6) |
+| 0 | 1 | 1 | network specific number (Note 4, Note 6) |
+| 1 | 0 | 0 | subscriber number (Note 1, Note 3, Note 6) |
+| 1 | 1 | 0 | abbreviated number (Note 5) |
+| 1 | 1 | 1 | reserved for extension |
+
+All other values are reserved.
+
+NOTE 1 – For the definition of international, national and subscriber number, see Recommendation I.330.
+
+NOTE 2 – The type of number “unknown” is used when NSAP addressing is indicated in the addressing/numbering plan identification or when the user or the network indicates the type of number using the number digits field. In the latter case, the number digits field is organized according to the network dialling plan; e.g. prefix digits might be present; in addition, escape digits may also be present.
+
+NOTE 3 – Prefix digits shall not be included.
+
+NOTE 4 – The type of number “network specific number” is used to indicate administration/service number specific to the serving network, e.g. used to access an operator.
+
+NOTE 5 – The support of this code is network dependent. The number provided in this information element presents a shorthand representation of the complete number in the specified numbering plan as supported by the network.
+
+NOTE 6 – The use of these codepoints applies only when the ISDN numbering plan (Rec. E.164) is being used, either by explicit indication or because it is the default numbering plan of the network indicated by the numbering plan identification equal to “unknown”.
+
+– Addressing/numbering plan identification (octet 5) (Note 11)
+
+Bits
+
+| 4 | 3 | 2 | 1 | |
+|---|---|---|---|-------------------------------------------------|
+| 0 | 0 | 0 | 0 | unknown (Note 7) |
+| 0 | 0 | 0 | 1 | ISDN numbering plan (Recommendation E.164) |
+| 0 | 0 | 1 | 0 | NSAP addressing (ISO/IEC 8348) (Note 8, Note 9) |
+| 1 | 0 | 0 | 1 | private numbering plan (Note 8, Note 10) |
+| 1 | 1 | 1 | 1 | reserved for extension |
+
+All other values are reserved.
+
+NOTE 7 – The numbering plan identification “unknown” indicates the default numbering plan of the network. In the absence of bilateral agreement, or alternative specification in other Recommendations, the default numbering plan of the network shall be “ISDN numbering plan (Recommendation E.164)”.
+
+NOTE 8 – The use of this codepoint is a network option and requires bilateral agreement/arrangements between the network operator and the user, subject to both network and user supporting the identified numbering plan.
+
+NOTE 9 – If this codepoint is used, the type of number is coded as “unknown”.
+
+NOTE 10 – If this codepoint is used, the type of number used is outside the scope of this Recommendation.
+
+NOTE 11 – All networks and users shall support the ISDN numbering plan. For the use of other numbering plans, see the Notes on the relevant numbering plan identification value.
+
+– Address/number digits (octets 6, etc.), used unless an alternative is specified
+
+This field is coded with IA5 characters, according to the formats specified in the appropriate numbering/dialling plan.
+
+– NSAP address octets (octets 6, etc. for NSAP addressing)
+
+If the use of NSAP addressing is indicated in the addressing/numbering plan identification, the address is coded as described in ISO/IEC 8348.
+
+#### 4.5.12 Called party sub-address
+
+The purpose of the called party sub-address information element is to identify the sub-address of the called party of a call. For the definition of subaddress, see Recommendation I.330.
+
+The called party sub-address is coded as shown in Figure 4-19 and Table 4-13.
+
+The maximum length of this information element is 25 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|---------------------------------------------|---------------------|----------------------|--------------------|----------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Called party sub-address | | | | | | | | 1 |
+| 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of called party sub-address contents | | | | | | | | |
+| | | | | | | | | 4 |
+| 1 ext. | Type of sub-address | | Odd/even indicator | 0 | 0 | 0 | | 5 |
+| | | | | Spare | | | | |
+| Sub-address information | | | | | | | | 6 etc. |
+
+T1162780-94/d024
+
+FIGURE 4-19/Q.2931
+Called party sub-address information element
+
+TABLE 4-13/Q.2931
+
+#### **Called party sub-address information element**
+
+| | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---|--------------------------------------|--|---|---|---|----------------------------------|---|---|---|--------------------------------------|---|---|---|----------------|---|--|---|--------------------------------|---|-------------------------------|
+| – Type of sub-address (octet 5)
Bits
| 7 | 6 | 5 | |
| 0 | 0 | 0 | NSAP (Rec. X.213 ISO/IEC 8348) |
| 0 | 0 | 1 | user-specified ATM endsystem address |
| 0 | 1 | 0 | user-specified |
All other values are reserved.
– Odd/even indicator (octet 5) (Note 1)
Bit
| 4 | |
| 0 | Even number of address signals |
| 1 | Odd number of address signals |
– Sub-address information (octet 6, etc.)
The NSAP Rec. X.213 ISO/IEC 8348 address, shall be formatted as specified by octet 6 which contains the Authority and Format Identifier (AFI). The encoding is made according to the “preferred binary encoding” as defined in Rec. X.213 ISO/IEC 8348 except when used for terminal selection (Note 3).
For the definition of this type of sub-address, see Recommendation I.334.
For the “user-specified ATM endsystem address”, this field is encoded according to the user specification, subject to a maximum length of 20 octets (Note 4).
For user-specified sub-address, this field is encoded according to the user specification, subject to a maximum length of 20 octets. When interworking with X.25 networks BCD coding should be applied.
| 7 | 6 | 5 | | 0 | 0 | 0 | NSAP (Rec. X.213 ISO/IEC 8348) | 0 | 0 | 1 | user-specified ATM endsystem address | 0 | 1 | 0 | user-specified | 4 | | 0 | Even number of address signals | 1 | Odd number of address signals |
+| 7 | 6 | 5 | | | | | | | | | | | | | | | | | | | | |
+| 0 | 0 | 0 | NSAP (Rec. X.213 ISO/IEC 8348) | | | | | | | | | | | | | | | | | | | |
+| 0 | 0 | 1 | user-specified ATM endsystem address | | | | | | | | | | | | | | | | | | | |
+| 0 | 1 | 0 | user-specified | | | | | | | | | | | | | | | | | | | |
+| 4 | | | | | | | | | | | | | | | | | | | | | | |
+| 0 | Even number of address signals | | | | | | | | | | | | | | | | | | | | | |
+| 1 | Odd number of address signals | | | | | | | | | | | | | | | | | | | | | |
+| NOTES
- 1 The odd/even indicator is used when the type of sub-address is “user-specified” and the coding is BCD.
- 2 It is recommended that users apply the NSAP sub-address type since this sub-address type allows the use of decimal, binary and IA5 characters in a standardized manner.
- 3 It is recommended that users apply the Local IDI format (the AFI field is coded 50 in BCD) when the sub-address is used for terminal selection. In this case, the IA5 character syntax using only digits 0 to 9 shall be used for the DSP. Each character is the coded in one octet according to Rec. T.50 ISO/IEC 646, with zero parity in the most significant position.
- 4 The “user-specified ATM endsystem address” can be used between two ATM terminal equipments when the NSAP codepoint is not appropriate.
| | | | | | | | | | | | | | | | | | | | | | |
+
+#### **4.5.13 Calling party number**
+
+The purpose of the calling party number information element is to identify the origin of a call.
+
+The calling party number information element is coded as shown in Figure 4-20, and Table 4-14. The maximum length of this information element is network dependent.
+
+
+
+| Bits | | | | | | | | Octets |
+|-----------------------------------------|------------------------|----------------------|------------------------------------------|----------------|---------------------|---|---|------------------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Calling party number | | | | | | | | 1 |
+| 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding Standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of calling party number contents | | | | | | | | |
+| | | | | | | | | 4 |
+| 0/1 ext. | Type of number | | Addressing/numbering plan identification | | | | | |
+| 1 ext. | Presentation indicator | 0 | 0 | 0 | Screening indicator | | | 5a* |
+| 0 | Address/number digits | | | | | | | 6* etc. (Note 1) |
+| NSAP address octets | | | | | | | | 6* etc. (Note 2) |
+
+T1162790-94/d025
+
+##### NOTES
+
+1 The number digits appear in multiple octet 6's in the same order in which they would be entered, that is, the number digit which would be entered first is located in the first octet 6. Digits are coded in IA5 characters. Bit 8 is set to 0.
+
+2 If the use of NSAP addressing is indicated in the addressing/numbering plan identification, the address is coded as described in Rec. X.213 | ISO/IEC 8348.
+
+FIGURE 4-20/Q.2931
+**Calling party number information element**
+
+TABLE 4-14/Q.2931 (sheet 1 of 2)
+
+#### **Calling party number information element**
+
+– Type of number (octet 5)
+
+Bits
+
+| 7 | 6 | 5 | |
+|---|---|---|-----------------------------------------------|
+| 0 | 0 | 0 | unknown (Note 2) |
+| 0 | 0 | 1 | international number (Note 1, Note 3, Note 6) |
+| 0 | 1 | 0 | national number (Note 1, Note 3, Note 6) |
+| 0 | 1 | 1 | network specific number (Note 4, Note 6) |
+| 1 | 0 | 0 | subscriber number (Note 1, Note 3, Note 6) |
+| 1 | 1 | 0 | abbreviated number (Note 5) |
+| 1 | 1 | 1 | reserved for extension |
+
+All other values are reserved.
+
+NOTE 1 – For the definition of international, national and subscriber number, see Recommendation I.330.
+
+NOTE 2 – The type of number “unknown” is used when NSAP addressing is indicated in the addressing/numbering plan identification or when the user or the network indicates the type of number using the number digits field. In the latter case, the number digits field is organized according to the network dialling plan; e.g. prefix digits might be present; in addition, escape digits may also be present.
+
+NOTE 3 – Prefix digits shall not be included.
+
+NOTE 4 – The type of number “network specific number” is used to indicate administration/service number specific to the serving network, e.g. used to access an operator.
+
+NOTE 5 – The support of this code is network dependent. The number provided in this information element presents a shorthand representation of the complete number in the specified numbering plan as supported by the network.
+
+NOTE 6 – The use of these codepoints applies only when the ISDN numbering plan (Recommendation E.164) is being used, either by explicit indication or because it is the default numbering plan of the network indicated by the numbering plan identification equal to “unknown”.
+
+– Addressing/numbering plan identification (octet 5) (Note 11)
+
+Bits
+
+| 4 | 3 | 2 | 1 | |
+|---|---|---|---|-------------------------------------------------|
+| 0 | 0 | 0 | 0 | unknown (Note 7) |
+| 0 | 0 | 0 | 1 | ISDN numbering plan (Recommendation E.164) |
+| 0 | 0 | 1 | 0 | NSAP addressing (ISO/IEC 8348) (Note 8, Note 9) |
+| 1 | 0 | 0 | 1 | private numbering plan (Note 8, Note 10) |
+| 1 | 1 | 1 | 1 | reserved for extension |
+
+All other values are reserved.
+
+NOTE 7 – The numbering plan identification “unknown” indicates the default numbering plan of the network. In the absence of bilateral agreement, or alternative specification in other Recommendations, the default numbering plan of the network shall be “ISDN numbering plan (Recommendation E.164)”.
+
+NOTE 8 – The use of this codepoint requires bilateral agreement between the network and the user, supporting the identified numbering plan.
+
+NOTE 9 – If this codepoint is used, the type of number is coded as “unknown”.
+
+NOTE 10 – If this codepoint is used, the type of number used is outside the scope of this Recommendation.
+
+NOTE 11 – All networks and users shall support the ISDN numbering plan. For the use of other numbering plans, see the Notes on the relevant numbering plan identification value.
+
+TABLE 4-14/Q.2931 (sheet 2 of 2)
+
+#### **Calling party number information element**
+
+– Presentation indicator (octet 5a)
+
+Bits
+
+7 6
+
+0 0 presentation allowed
+
+0 1 presentation restricted
+
+1 0 number not available
+
+1 1 reserved
+
+NOTE 12 – At the originating user-network interface, the presentation indicator is used for indicating the intention of the calling user for the presentation of the calling party number to the called user. This may also be requested on a subscription basis. If octet 5a is omitted, and the network does not support subscription information for the calling party number information restrictions, the value “00 – presentation allowed” is assumed.
+
+– Screening indicator (octet 5a)
+
+Bits
+
+2 1
+
+0 0 user-provided, not screened
+
+0 1 user-provided, verified and passed
+
+1 0 user-provided, verified and failed
+
+1 1 network provided
+
+NOTE 13 – If octet 5a is omitted, “00 – User provided, not screened” is assumed.
+
+– Address/number digits (octets 6, etc.), used unless an alternative is specified
+
+This field is coded with IA5 characters, according to the formats specified in the appropriate numbering/dialling plan.
+
+– NSAP address octets (octets 6, etc. for NSAP addressing)
+
+If the use of NSAP addressing is indicated in the addressing/numbering plan identification, the address is coded as described in Rec. X.213 | ISO/IEC 8348 (for details, see also the description of sub-address information in Table 4-15).
+
+#### **4.5.14 Calling party sub-address**
+
+The purpose of the calling party sub-address is to identify a sub-address associated with the origin of a call. For the definition of sub-address, see Recommendation I.330.
+
+The calling party sub-address information element is coded as shown in Figure 4-21 and Table 4-15.
+
+The maximum length of this information element is 25 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|-------------------------------------------|---------------------|---|----------------------|-------|----------------|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Calling party sub-address | | | | | | | | 1 |
+| 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | | IE instruction field | | | | | |
+| | | | Flag | Res. | IE action ind. | | | |
+| Length of Calling party sub-address cont. | | | | | | | | 3 |
+| | | | | | | | | 4 |
+| 1 ext. | Type of sub-address | | Odd/even indicator | 0 | 0 | 0 | | 5 |
+| | | | | Spare | | | | |
+| Sub-address information | | | | | | | | 6 etc. |
+
+T1162800-94/d026
+
+FIGURE 4-21/Q.2931
+**Calling party sub-address information element**
+
+TABLE 4-15/Q.2931
+**Calling party sub-address information element**
+
+| – Type of sub-address (octet 5)
Bits
| 7 | 6 | 5 | |
| 0 | 0 | 0 | NSAP (Rec. X.213 ISO/IEC 8348) |
| 0 | 0 | 1 | user-specified ATM endsystem address |
| 0 | 1 | 0 | user-specified |
All other values are reserved.
– Odd/even indicator (octet 5)
Bit
| 4 | |
| 0 | Even number of address signals (Note 1) |
| 1 | Odd number of address signals (Note 1) |
– Sub-address information (octet 6, etc.)
The NSAP Rec. X.213 ISO/IEC 8348 address, shall be formatted as specified by octet 6 which contains the Authority and Format Identifier (AFI). The encoding is made according to the “preferred binary encoding” as defined in Rec. X.213 ISO/IEC 8348 except when used for terminal selection (Note 3). For the definition of this type of sub-address, see Recommendation I.334.
For the “user-specified ATM endsystem address”, this field is encoded according to the user specification, subject to a maximum length of 20 octets (Note 4).
For user specified sub-address, this field is encoded according to the user specification, subject to a maximum length of 20 octets. When interworking with X.25 networks, BCD coding should be applied.
| 7 | 6 | 5 | | 0 | 0 | 0 | NSAP (Rec. X.213 ISO/IEC 8348) | 0 | 0 | 1 | user-specified ATM endsystem address | 0 | 1 | 0 | user-specified | 4 | | 0 | Even number of address signals (Note 1) | 1 | Odd number of address signals (Note 1) |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|---|--------------------------------------|--|---|---|---|----------------------------------|---|---|---|--------------------------------------|---|---|---|----------------|---|--|---|-----------------------------------------|---|----------------------------------------|
+| 7 | 6 | 5 | | | | | | | | | | | | | | | | | | | | |
+| 0 | 0 | 0 | NSAP (Rec. X.213 ISO/IEC 8348) | | | | | | | | | | | | | | | | | | | |
+| 0 | 0 | 1 | user-specified ATM endsystem address | | | | | | | | | | | | | | | | | | | |
+| 0 | 1 | 0 | user-specified | | | | | | | | | | | | | | | | | | | |
+| 4 | | | | | | | | | | | | | | | | | | | | | | |
+| 0 | Even number of address signals (Note 1) | | | | | | | | | | | | | | | | | | | | | |
+| 1 | Odd number of address signals (Note 1) | | | | | | | | | | | | | | | | | | | | | |
+
+**NOTES**
+
+- The odd/even indicator is used when the type of sub-address is “user-specified” and the coding is BCD.
+- It is recommended that users apply the NSAP sub-address type since this sub-address type allows the use of decimal, binary and IA5 characters in a standardized manner.
+- It is recommended that users apply the Local IDI format (the AFI field is coded 50 in BCD) when the sub-address is used for terminal selection. In this case, the IA5 character syntax using only digits 0 to 9 shall be used for the DSP. Each character is the coded in one octet according to Rec. T.50 | ISO/IEC 646, with zero parity in the most significant position.
+- The “user-specified ATM endsystem address” can be used between two ATM terminal equipments when the NSAP codepoint is not appropriate.
+
+#### 4.5.15 Cause
+
+The contents and use of the cause information element is defined in Recommendation Q.2610.
+
+#### 4.5.16 Connection identifier
+
+The connection identifier information element identifies the local ATM connection resources on the interface. This information element is optionally present in the SETUP message, and optionally in the first response to the SETUP message.
+
+The connection identifier information element is coded as shown in Figure 4-22 and Table 4-16. The length of this information element is 9 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|-----------------------------------------------------------------------------------|-----------------|---|----------------------|------|---------------------|---|---|-------------------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Connection identifier
0 1 0 1 1 0 1 0
information element identifier | | | | | | | | 1 |
+| 1 ext. | Coding standard | | IE instruction field | | | | | 2 |
+| | | | Flag | Res. | IE action ind. | | | |
+| Length of connection identifier contents | | | | | | | | 3 |
+| | | | | | | | | 4 |
+| 1 ext. | Spare
0 0 | | VP-assoc. signalling | | Preferred/exclusive | | | 5 |
+| | | | | | | | | 6 (Note 3) |
+| VPCI | | | | | | | | 7 |
+| | | | | | | | | 8 (Note 1, and 2) |
+| VCI | | | | | | | | 9 |
+
+T1162810-94/d027
+
+##### NOTES
+
+- 1 If the preferred/exclusive field indicates "any VCI", the VCI field shall be ignored.
+- 2 In case of the restart class "001" (see Table 4-20 and 3.3), the VCI field shall be ignored.
+- 3 When VP-associated signalling is indicated in octet 5, the VPCI field shall be ignored.
+
+FIGURE 4-22/Q.2931
+**Connection identifier information element**
+
+TABLE 4-16/Q.2931
+
+#### **Connection identifier information element**
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|---|----------------------------------------------------------------------------|
+| – VP-associated signalling (VP-associated signalling) (octet 5) | | | |
+| Bits | | | |
+| 5 | 4 | | |
+| 0 | 0 | | VP-associated signalling (same VPI for user information as for signalling) |
+| 0 | 1 | | explicit indication of VPCI |
+| All other values reserved. | | | |
+| – Pref./Ex. (preferred/exclusive), (octet 5) | | | |
+| Bits | | | |
+| 3 | 2 | 1 | |
+| 0 | 0 | 0 | exclusive VPCI; exclusive VCI |
+| 0 | 0 | 1 | exclusive VPCI; any VCI |
+| All other values are reserved. | | | |
+| – Virtual Path Connection Identifier (octets 6 and 7) | | | |
+| The values 0 through 65 535 are a code representing the identifier of the virtual path connection (Note 1) | | | |
+| – Virtual Channel Identifier (octets 8 and 9) (Note 2) | | | |
+| 0 through 31 | | | not used for on-demand user plane connections |
+| 32 through 65 535 | | | identifier of the virtual channel (Note 3) |
+| NOTES | | | |
+| 1 | For the use of VPCIs see 5.1.2.2. The range of VPI values available will be determined at subscription time. | | |
+| 2 | The value of the VCI field is the same as the value used in the VCI field of the corresponding ATM cell headers. | | |
+| 3 | Some values in the range may not be available for use for user-plane connections. | | |
+
+#### **4.5.17 End-to-end transit delay**
+
+The purpose of the end-to-end transit delay information element is to indicate the nominal maximum end-to-end transit delay acceptable on a per-call basis, and to indicate the cumulative transit delay to be expected for a virtual channel connection.
+
+Transit delay is the end-to-end one-way transit delay of user data transferred during the data transfer phase on the user plane, between the calling user and the called user. It includes:
+
+- the total processing time in the end user systems (e.g. processing time, AAL handling delay, ATM cell assembly delay, and possibly any additional processing delay); and
+- the network transfer delay (e.g. propagation delay, ATM layer transfer delay, possibly any additional processing delay in the network).
+
+The cumulative transit delay value indicated by the calling user in the SETUP message (if present) includes the cumulative transit delay from the calling user to the network boundary.
+
+The cumulative transit delay value indicated by the network in the SETUP message sent to the called user is the sum of the value which was indicated at the originating UNI and the expected transfer delay accumulated within the network. It does not include further transfer delay on the way from the network boundary to the called user.
+
+The cumulative transit delay value which is transferred over both UNIs in the CONNECT message is the expected total end-to-end transit delay value for user data transfer over the related virtual channel connection as provided for a given call.
+
+The maximum end-to-end transit delay value may be indicated by the calling user to specify end-to-end transit delay requirements for this call. This field is included by the network in the SETUP message to indicate that the calling user has specified end-to-end transit delay requirements for this call.
+
+The procedures which are applicable are described in Annex K.
+
+The maximum end-to-end transit delay is not included in the CONNECT message.
+
+The end-to-end transit delay is coded as shown in Figure 4-23 and Table 4-17.
+
+The maximum length of this information element is 10 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|---------------------------------------------|-----------------|----------------------|------|----------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| End-to-end transit delay | | | | | | | | 1 |
+| 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of end-to-end transit delay contents | | | | | | | | |
+| | | | | | | | | 4 |
+| Cumulative transit delay identifier | | | | | | | | 5 |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | |
+| | | | | | | | | 5.1 |
+| Cumulative transit delay value | | | | | | | | 5.2 |
+| | | | | | | | | 6* |
+| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | |
+| | | | | | | | | 6.1* |
+| Maximum end-to-end transit delay value | | | | | | | | 6.2* |
+
+T1162820-94/d028
+
+FIGURE 4-23/Q.2931
+**End-to-end transit delay information element**
+
+TABLE 4-17/Q.2931
+**End-to-end transit delay information element**
+
+– Cumulative transit delay value (octets 5.1 and 5.2)
+
+The cumulative transit delay value is binary encoded in milliseconds. The coding rules for integer values described in 4.5.1 apply.
+
+The cumulative transit delay value occupies 16 bits total.
+
+– Maximum end-to-end transit delay value (octets 6.1 and 6.2)
+
+The maximum end-to-end transit delay value is binary encoded in milliseconds. The coding rules for integer values described in 4.5.1 apply.
+
+The maximum end-to-end transit delay value occupies 16 bits total.
+
+The value “1111 1111 1111 1111”, however, is not to be interpreted as a maximum end-to-end transfer delay value. This codepoint indicates: “any end-to-end transit delay value acceptable; deliver cumulative end-to-end transit delay value to the called user”.
+
+#### 4.5.18 Quality of Service parameter
+
+In addition to end-to-end transit delay information element, the Quality of Service parameter information element is specified. The purpose of the Quality of Service parameter information element is to indicate a certain Quality of Service (QOS) class.
+
+The Quality of Service parameter information element will not be supported by B-ISUP Release 1, i.e. some networks will not transfer the Quality of Service parameter information element. These networks will generate the default value (unspecified QOS class) for the Quality of Service parameter information element for the transfer to the called user at the terminating interface.
+
+The Quality of Service parameter information element is coded as shown in Figure 4-24 and Table 4-18. The length of this information element is 6 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|----------------------------------|-----------------|---|----------------------|------|----------------|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Quality of Service parameter | | | | | | | | 1 |
+| 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | | IE instruction field | | | | | |
+| | | | Flag | Res. | IE action ind. | | | 3 |
+| Length of QOS parameter contents | | | | | | | | |
+| | | | | | | | | 4 |
+| QOS class forward | | | | | | | | 5 |
+| QOS class backward | | | | | | | | 6 |
+
+T1162830-94/d029
+
+FIGURE 4-24/Q.2931
+Quality of Service parameter information element
+
+TABLE 4-18/Q.2931
+Quality of service parameter information element
+
+| | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|---------------------------------------------------------------|
+| - QOS class forward (octet 5) | | | | | | | | |
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | unspecified QOS class (Note 1) |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | reserved for future indications of parameterized QOS (Note 2) |
+| All other values are reserved. | | | | | | | | |
+| - QOS class backward (octet 6) | | | | | | | | |
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | unspecified QOS class (Note 1) |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | reserved for future indications of parameterized QOS (Note 2) |
+| All other values are reserved. | | | | | | | | |
+| NOTES | | | | | | | | |
+| 1 If this class is indicated, the network does not guarantee any specific Quality of Service. | | | | | | | | |
+| 2 This codepoint is reserved for use when individual QOS parameters are defined. The individual parameters would then be contained in octets 7 and higher. | | | | | | | | |
+
+#### 4.5.19 Broadband repeat indicator
+
+The purpose of the broadband repeat indicator information element is to indicate how repeated information elements shall be interpreted, when included in a message. The broadband repeat indicator information element is included before the first occurrence of the information element which will be repeated in a message. The broadband repeat indicator information element is coded as shown in Figure 4-25 and Table 4-19. The length of this information element is 5 octets.
+
+NOTE – Use of the broadband repeat indicator information element in conjunction with an information element that occurs only once in a message shall not in itself constitute an error.
+
+
+
+| Bits | | | | | | | | Octets |
+|-----------------------------------------------|-----------------|---|----------------------|-----------------------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Broadband repeat indicator | | | | | | | | 1 |
+| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | | IE instruction field | | | | | |
+| Length of broadband repeat indicator contents | | | | | | | | 3 |
+| | | | | | | | | 4 |
+| 1 ext. | 0 | 0 | 0 | Broadband repeat indication | | | | 5 |
+| Spare | | | | | | | | |
+
+T1162840-94/d030
+
+FIGURE 4-25/Q.2931
+
+#### Broadband repeat indicator information element
+
+TABLE 4-19/Q.2931
+
+#### Broadband repeat indicator information element
+
+| | | | | |
+|-----------------------------------------|---|---|---|-------------------------------------------------------------------------------|
+| – Broadband repeat indication (octet 5) | | | | |
+| Bits | | | | |
+| 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | reserved for use by Recommendation Q.2763 (B-ISUP) |
+| 0 | 0 | 0 | 1 | reserved for use by Recommendation Q.2763 (B-ISUP) |
+| 0 | 0 | 1 | 0 | prioritized list for selecting one possibility (descending order of priority) |
+| All other values are reserved. | | | | |
+
+#### 4.5.20 Restart indicator
+
+The purpose of the restart indicator information element is to identify the class of the facility to be restarted.
+
+The restart indicator information element is coded as shown in Figure 4-26 and Table 4-20. The length of this information element is 5 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|--------------------------------------|-----------------|----------------------|------|----------------|-------|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Restart indicator | | | | | | | | 1 |
+| 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of restart indicator contents | | | | | | | | |
+| | | | | | | | | 4 |
+| 1 ext. | 0 | 0 | 0 | 0 | Class | | | 5 |
+| Spare | | | | | | | | |
+
+T1162850-94/d31
+
+FIGURE 4-26/Q.2931
+**Restart indicator information element**
+
+TABLE 4-20/Q.2931
+**Restart indicator information element**
+
+| | | | |
+|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| – Class (octet 5) | | | |
+| Bits | | | |
+| 3 | 2 | 1 | |
+| 0 | 0 | 0 | indicated virtual channel (Note 1) |
+| 0 | 0 | 1 | all virtual channels in the indicated VPC which are controlled via the signalling virtual channel on which the RESTART message is sent (Note 2) |
+| 0 | 1 | 0 | all virtual channels controlled by the layer 3 entity which sends the RESTART message (Note 3) |
+| All other values are reserved. | | | |
+| NOTES | | | |
+| 1 | The connection identifier information element shall be included and indicates the virtual channel to be restarted. | | |
+| 2 | The connection identifier information element shall be included and indicates the Virtual Path Connection in which all virtual channels are to be restarted. The virtual channel identification field in the connection identifier information element is ignored. | | |
+| 3 | The connection identifier information element is not included. All virtual channels controlled by the point-to-point signalling channel are to be restarted. | | |
+
+#### 4.5.21 Broadband sending complete
+
+The purpose of the broadband sending complete information element is to optionally indicate completion of called party number, see clauses 5 and 6.
+
+This information element is mandatory if operating in *en bloc* mode; however, if missing, regular error handling procedures for “mandatory information element missing” need not be applied.
+
+The broadband sending complete information element is coded as shown in Figure 4-27. The length of this information element is 5 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|--------------------------------|---------------------------------------|----------------------|------|----------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Broadband sending complete | | | | | | | | 1 |
+| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of Broadband sending | | | | | | | | |
+| complete contents | | | | | | | | 4 |
+| 1 ext. | Broadband sending complete indication | | | | | | | 5 |
+| 0 | 1 | 0 | 0 | 0 | 0 | 1 | | |
+
+T1162860-94/d032
+
+FIGURE 4-27/Q.2931
+**Broadband sending complete information element**
+
+### 4.5.22 Transit network selection
+
+The purpose of the transit network selection information element is to identify one requested transit network. The transit network selection information element may be repeated in a message to select a sequence of transit networks through which a call must pass. See Annex D.
+
+The transit network selection information element is coded as shown in Figure 4-28 and Table 4-21. The maximum length of this information element is network dependent.
+
+
+
+| Bits | | | | | | | | Octets |
+|----------------------------------------------|--------------------------------|----------------------|-----------------------------|----------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Transit network selection | | | | | | | | 1 |
+| 0 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of transit network selection contents | | | | | | | | |
+| | | | | | | | | 4 |
+| 1 ext. | Type of network identification | | Network identification plan | | | | | 5 |
+| 0 | | | | | | | | |
+| Network identification (IA5 characters) | | | | | | | | 6 etc. |
+
+T1162870-94/d033
+
+FIGURE 4-28/Q.2931
+**Transit network selection information element**
+
+TABLE 4-21/Q.2931
+
+#### **Transit network selection information element**
+
+– Type of network identification (octet 5)
+
+Bits
+
+| | | | |
+|---|---|---|------------------------------------------|
+| 7 | 6 | 5 | |
+| 0 | 0 | 0 | user-specified |
+| 0 | 1 | 0 | national network identification (Note 1) |
+| 0 | 1 | 1 | international network identification |
+
+All other values are reserved.
+
+NOTE 1 – In the case that type of network identification is coded as 010, national network identification, “national identification plan” is coded according to national specification.
+
+– Network identification plan (octet 5)
+
+Bits
+
+| | | | | |
+|---|---|---|---|---------------------------------------------------------|
+| 4 | 3 | 2 | 1 | |
+| 0 | 0 | 0 | 0 | unknown |
+| 0 | 0 | 0 | 1 | carrier identification code (Note 2) |
+| 0 | 0 | 1 | 1 | data network identification code (Recommendation X.121) |
+
+All other values are reserved.
+
+NOTE 2 – Carrier identification codes may be an appropriate method of identifying the network serving the remote user.
+
+– Network identification (octet 6)
+
+These IA5 characters are organized according to the network identification plan specified in octet 5.
+
+### **4.5.23 Notification indicator**
+
+The purpose of the notification indicator information element is to indicate information pertaining to a call. The notification indicator information element is coded as shown in Figure 4-29.
+
+The maximum length of this information element is application dependent consistent with the maximum length of the message.
+
+
+
+| | | | | | | | | |
+|------------------------------------------------------------------------|-----------------|----------------------|------|----------------|---|---|---|--------|
+| Bits | | | | | | | | |
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets |
+| Notification indicator | | | | | | | | 1 |
+| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | |
+| information element identifier | | | | | | | | |
+| 1 ext. | Coding standard | IE instruction field | | | | | | 2 |
+| | | Flag | Res. | IE action ind. | | | | |
+| Length of notification indicator contents | | | | | | | | 3 |
+| | | | | | | | | 4 |
+| Further contents as defined in other ITU-T Recommendations, e.g. Q.932 | | | | | | | | 5 |
+
+T1162880-94/d034
+
+FIGURE 4-29/Q.2931
+
+#### **Notification indicator information element**
+
+### 4.5.24 OAM traffic descriptor
+
+The purpose of the OAM traffic descriptor information element is to provide information relating to the end-to-end OAM F5 information flow for performance management and user-originated fault management associated with the user connection involved in the call.
+
+The handling of the OAM traffic descriptor information element is specified in Annex I.
+
+The length of this information element is 6 octets. The format of this information element is shown in Figure 4-30 and in Table 4-22.
+
+
+
+| Bits | | | | | | | | Octets |
+|-----------------------------------------------------------------------------|-------------------------------------|----------------------|---------|-------------------------------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| OAM traffic descriptor
0 1 0 1 1 0 1 1
information element identifier | | | | | | | | 1 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | 2 |
+| | | Flag | Res. | IE action ind. | | | | |
+| Length of OAM traffic descriptor contents | | | | | | | | 3 |
+| | | | | | | | | 4 |
+| 1 ext. | Shaping indicator | Cmpl. ind. | 0 Spare | User-network fault mngr. ind. | | | | 5 |
+| 1 ext. | Fwd. e.-to-e. OAM F5 flow indicator | | 0 Spare | Bwd. e.-to-e. OAM F5 flow indicator | | | | 6 |
+
+T1165730-94/d035
+
+FIGURE 4-30/Q.2931
+**OAM traffic descriptor**
+
+TABLE 4-22/Q.2931
+
+#### **OAM traffic descriptor information element**
+
+– Shaping indicator (octet 5)
+
+Bits
+
+7 6
+
+0 0 no user specified requirement on shaping by the network, if shaping is applied by the network
+
+0 1 aggregate shaping of user and OAM cells is not allowed, if shaping is applied by the network
+
+All other values are reserved.
+
+– Cmpl. ind. (Compliance Indicator) (octet 5)
+
+Bit
+
+5
+
+0 the use of end-to-end OAM F5 flow is optional
+
+1 the use of end-to-end OAM F5 flow is mandatory
+
+– User-network fault management indicator (octet 5)
+
+Bits
+
+3 2 1
+
+0 0 0 no user-originated fault management indications (Note 1)
+
+0 0 1 use of user-originated fault management indications with a cell rate of 1 cell/s (Note 1)
+
+All other values are reserved.
+
+– Fwd. e-to-e. (Forward end-to-end) OAM F5 flow indicator (octet 6) (Note 1, Note 2)
+
+Bits
+
+7 6 5
+
+0 0 0 0% of the forward cell rate (CLP = 0 + 1) specified by the ATM traffic descriptor information element (forward direction)
+
+0 0 1 0.1% of the forward cell rate (CLP = 0 + 1) specified by the ATM traffic descriptor information element (forward direction)
+
+1 0 0 1% of the forward cell rate (CLP = 0 + 1) specified by the ATM traffic descriptor information element (forward direction)
+
+All other values are reserved.
+
+– Bwd. e-to-e. (Backward end-to-end) OAM F5 flow indicator (octet 6) (Note 1, Note 2)
+
+Bits
+
+3 2 1
+
+0 0 0 0% of the backward cell rate (CLP = 0 + 1) specified by the ATM traffic descriptor information element (backward direction)
+
+0 0 1 0.1% of the backward cell rate (CLP = 0 + 1) specified by the ATM traffic descriptor information element (backward direction)
+
+1 0 0 1% of the backward cell rate (CLP = 0 + 1) specified by the ATM traffic descriptor information element (backward direction)
+
+All other values are reserved.
+
+##### **NOTES**
+
+1 Fault management indications originating in the network (e.g. alarm indications) will always be transferred to the user, independent of the codepoint used in the user-network fault management indicator field.
+
+2 The cell rate allocated in both the forward and the backward direction is the sum of the following:
+
+- the cell rate indicated in the user-network fault management indicator;
+- the percentage of the forward cell rate indicated by the forward end-to-end OAM F5 flow indicator;
+- the percentage of the backward cell rate indicated by the backward end-to-end OAM F5 flow indicator.
+
+## 4.6 Information elements for the support of 64 kbit/s based ISDN circuit-mode services
+
+### 4.6.1 Coding rules
+
+The information elements described in 4.6 use the general information element format as described in Figure 4-8. The coding of these information elements follows the coding rules of this Recommendation and those of Recommendation Q.931.
+
+### 4.6.2 Narrow-band bearer capability
+
+The purpose of the narrow-band bearer capability information element is to indicate a requested circuit-mode N-ISDN bearer service to be provided by the network. It contains only information that may be used by the network (see Annex I/Q.931). The use of the narrow-band bearer capability information element in relation to compatibility checking is described in Annex B/Q.931.
+
+The narrow-band bearer capability is transferred transparently through the B-ISDN.
+
+The narrow-band bearer capability information element is coded as shown in Figure 4-31.
+
+No default narrow-band bearer capability may be assumed by the absence of this information element.
+
+
+
+| Bits | | | | | | | | Octets |
+|---------------------------------------------------------------------------|-----------------|----------------------|------|----------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Narrowband bearer capability | | | | | | | | 1 |
+| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of narrowband bearer capability contents | | | | | | | | |
+| | | | | | | | | 4 |
+| Further contents as described in Figure 4-11/Q.931 and in Table 4-6/Q.931 | | | | | | | | |
+
+T1162900-94/d036
+
+FIGURE 4-31/Q.2931
+Narrowband bearer capability information element
+
+### 4.6.3 Narrow-band high layer compatibility
+
+The purpose of the narrow-band high layer compatibility information element is to provide a means which should be used by the remote user for compatibility checking. See Annex B/Q.931.
+
+The narrow-band high layer compatibility information element is coded as shown in Figure 4-32.
+
+The maximum length of this information element is 7 octets.
+
+NOTE – The narrow-band high layer compatibility information element is transported transparently by a B-ISDN between a call originating entity, e.g. a calling user and the addressed entity; a remote user or a high layer function network node addressed by the call originating entity. However, if explicitly requested by the user (at subscription time), a network which provides some capabilities to realize teleservices may interpret this information to provide a particular service.
+
+
+
+| Bits | | | | | | | | Octets |
+|---------------------------------------------------------------|-----------------|----------------------|------|----------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Narrowband high layer compatibility | | | | | | | | 1 |
+| 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of narrowband high layer compatibility contents | | | | | | | | |
+| | | | | | | | | 4 |
+| Further contents as in Figure 4-23/Q.931 and Table 4-15/Q.931 | | | | | | | | |
+
+T1162910-94/d037
+
+FIGURE 4-32/Q.2931
+**Narrowband high layer compatibility information element**
+
+### 4.6.4 Narrow-band low layer compatibility
+
+The purpose of the narrow-band low layer compatibility information element is to provide a means which should be used for compatibility checking by an addressed entity (e.g. a remote user or an interworking unit or a high layer function network node addressed by the calling user). The low layer compatibility information element is transferred transparently by a B-ISDN between the call originating entity (e.g. the calling user) and the addressed entity.
+
+For narrow-band low layer compatibility negotiation (see Annex J/Q.931), the narrow-band low layer compatibility information element is also passed transparently from the addressed entity to the originating entity.
+
+The narrow-band low layer compatibility information element is coded as shown in Figure 4-33. The maximum length of this information element is 20 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|----------------------------------------------------------------|-----------------|----------------------|------|----------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Narrowband low layer compatibility | | | | | | | | 1 |
+| 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | |
+| information element identifier | | | | | | | | 2 |
+| 1 ext. | Coding standard | IE instruction field | | | | | | |
+| | | Flag | Res. | IE action ind. | | | | 3 |
+| Length of the Narrowband low layer compatibility cont. | | | | | | | | |
+| | | | | | | | | 4 |
+| Further contents as in Figure 4-25/Q.931 and Table 4-16/Q.931. | | | | | | | | |
+
+T1162920-94/d038
+
+FIGURE 4-33/Q.2931
+**Narrowband low layer compatibility information element**
+
+### 4.6.5 Progress indicator
+
+The purpose of the progress indicator information element is to describe an event which has occurred during the life of a call. The information element may occur twice in a message.
+
+The progress indicator information element is coded as shown in Figure 4-34. The maximum length of this information element is 6 octets.
+
+
+
+| Bits | | | | | | | | Octets |
+|------------------------------------------------------------------|--------------------|----------------------|------|----------------|---|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Progress indicator
information element identifier | | | | | | | | 1 |
+| 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | |
+| 1
ext. | Coding
standard | IE instruction field | | | | | | 2 |
+| | | Flag | Res. | IE action ind. | | | | |
+| Length of progress indicator contents | | | | | | | | 3 |
+| Further contents as in Figure 4-29/Q.931 and
Table 4-20/Q.931 | | | | | | | | 4 |
+
+T1162930-94/d039
+
+FIGURE 4-34/Q.2931
+**Progress indicator information element**
+
+# 5 B-ISDN call/connection control procedures
+
+This clause describes the general procedures for call/connection control in B-ISDN. Clause 6 specifies the particular features required to provide 64 kbit/s based circuit-mode ISDN services in B-ISDN and to support access signalling interworking between B-ISDN and N-ISDN.
+
+These procedures apply only to the point-to-point access configuration. For point-to-point access configurations, VCI = 5 is used as the signalling channel.
+
+This Recommendation's procedures are used to establish B-ISDN connections over a signalling virtual channel that has already been established. Subsequent connections controlled by the same signalling virtual channel are distinguished through different call reference values.
+
+For call/connection to be established, it must satisfy the following general criteria determined by the network and end systems:
+
+- basic service support;
+- VC availability;
+- physical and virtual network resource availability to provide Quality of Service requested;
+- end system resource availability to provide Quality of Service requested;
+- end-to-end compatibility.
+
+NOTE – Annex H contains extensions to the call/connection establishment procedures described in this clause for symmetrical operations.
+
+**PAS DE TABLE DE MATIÈRES (PAS DE HEADING 1) DANS CE FICHIER**
+
+The call states referred to in this clause cover the states perceived by the network, states perceived by the user and states which are common to both user and network. Unless specifically qualified, all states described in the following text should be understood as common.
+
+Detailed Specification and Description Language (SDL) diagrams for the procedures specified in this clause are contained in Annex A. When there is an ambiguity in the narrative text, the SDL diagrams should be used to resolve the conflict. Where the text and the SDL are in disagreement, the text should be used as the prime source.
+
+## 5.1 Call/connection establishment at the originating interface
+
+Before these procedures are invoked, an assured mode Signalling AAL connection must be established between the user and the network. All layer 3 messages shall be sent to the Signalling AAL using a AAL-DATA-request primitive. The data link services described in Recommendation Q.2130 are assumed.
+
+Establishment of Signalling AAL connections is initiated by transferring an AAL\_ESTABLISH-request primitive to the Signalling AAL.
+
+On receipt of an AAL\_ESTABLISH-confirm or AAL\_ESTABLISH-indication primitive from the SAAL, access signalling procedures may begin. The AAL\_ESTABLISH-indication primitive will be received in the case of SAAL establishment request by the peer entity, and AAL\_ESTABLISH-confirm in response to a local request to establish an SAAL connection.
+
+### 5.1.1 Call/connection request
+
+The calling party initiates call establishment by transferring a SETUP message on the assigned signalling virtual channel across the interface and starts timer T303. Following the transmission of the SETUP message, the call is considered by the calling party to be in the Call Initiated state. The message shall always contain a call reference, selected according to the procedures given in 4.3. In selecting a call reference, the dummy call reference value shall not be used. The ATM traffic descriptor, Broadband bearer capability, and QOS parameter information elements are mandatory in the SETUP message.
+
+Furthermore, the SETUP message may also contain all or part of the call information (i.e. address) necessary for call establishment depending on whether *en bloc* or overlap procedures (see clause 6) are being used respectively.
+
+If *en bloc* sending is used, the SETUP message shall contain all the information required by the network to process the call. In particular, the called party address information, if present, is contained in the Called party number information element possibly supplemented by the Called party sub-address information element. The Broadband sending complete information shall be included by the B-TEs.
+
+If no response to the SETUP message is received by the user before the first expiry of timer T303, the SETUP message shall be retransmitted and timer T303 restarted. If the user has not received any response to the SETUP message after the final expiry of timer T303, the user shall clear the call internally.
+
+### 5.1.2 Connection identifier (VPCI/VCI) allocation/selection – Origination
+
+Two cases exist:
+
+#### i) *associated signalling*
+
+The layer 3 signalling entity exclusively controls the VCs in the VPC which carries its signalling VC.
+
+#### ii) *non-associated signalling*
+
+The layer 3 signalling entity controls the VCs in the VPC which carries its signalling VC and may control VCs in other VPCs.
+
+The network and user shall support the non-associated signalling procedures and may as an option support the associated signalling procedures. The associated signalling procedures are used only by bilateral agreement between the user and the network.
+
+When the network receives a connection identifier information element with the VP-associated signalling field (see Table 4-16) coded with a value not supported by the network, the call shall be rejected with cause No. 36, "VPCI/VCI assignment failure".
+
+#### 5.1.2.1 Associated signalling
+
+For associated signalling, the user requests a VC in the VPC carrying the signalling VC. The VPC carrying the signalling VC is implicitly indicated.
+
+In the Connection identifier information element, the VP-associated signalling field is coded as "VP-associated signalling" and one of the following values is indicated in the preferred/exclusive field:
+
+- a) "exclusive VPCI; any VCI"; or
+- b) "exclusive VPCI; exclusive VCI".
+
+In case a), the network selects any available VCI within the VPC carrying the signalling VC.
+
+In case b), if the indicated VCI within the VPC carrying the signalling VC is available, the network selects it for the call.
+
+The selected VCI value is indicated in the Connection identifier information element in the first message returned by the network in response to the SETUP message (e.g. CALL PROCEEDING message). The VP-associated signalling field is coded as "VP-associated signalling". The preferred/exclusive field is coded as "exclusive VPCI; exclusive VCI".
+
+In case a), if no VCI is available, a RELEASE COMPLETE message with cause No. 45, "no VPCI/VCI available", is sent by the network.
+
+In case b), if the indicated VCI is not available, a RELEASE COMPLETE message with the cause No. 35, "requested VPCI/VCI not available", is sent by the network.
+
+#### 5.1.2.2 Non-associated signalling
+
+In the user's request for a VC in the SETUP message, the user shall indicate one of the following:
+
+- a) "exclusive VPCI; any VCI";
+- b) "exclusive VPCI; exclusive VCI"; or
+- c) no indication is included (i.e. the Connection identifier information element is not included in the SETUP message).
+
+In cases a) and b), the VP-associated signalling field is coded as "explicit indication of VPCI" in the Connection identifier information element.
+
+In cases a) and b), if the indicated VPCI is available, the network selects it for the call. In case a), the network selects any available VCI in the VPCI. In case b), if the indicated VCI is available within the VPCI, the network selects it for the call.
+
+In case c), the network selects any available VPCI and VCI.
+
+The selected VPCI/VCI value is indicated in the Connection identifier information element in the first message returned by the network in response to the SETUP message (e.g. CALL PROCEEDING message). The VP-associated signalling field is coded as "explicit indication of VPCI". The preferred/exclusive field is coded as "exclusive VPCI; exclusive VCI".
+
+In cases a) and b), if the specified VPCI is not available, a RELEASE COMPLETE message with cause No. 35, "requested VPCI/VCI not available", is sent by the network.
+
+In case a), if no VCI is available, a RELEASE COMPLETE message with cause No. 45, "no VPCI/VCI available", is sent by the network.
+
+In case b), if the VCI in the indicated VPCI is not available, a RELEASE COMPLETE message with cause No. 35, "requested VPCI/VCI not available", is sent by the network.
+
+In case c), if the network is not able to allocate a VCI in any VPCI, a RELEASE COMPLETE message with cause No. 45, "no VPCI/VCI available", is sent by the network.
+
+In case a), if the VPCI values in the first response message is not the VPCI value indicated by the user, a RELEASE message with cause No. 36, "VPCI/VCI assignment failure", shall be sent to the network.
+
+In case b), if the VPCI and VCI values in the first response message are not the VPCI and VCI values indicated by the user, a RELEASE message with cause No. 36, "VPCI/VCI assignment failure", shall be sent to the network.
+
+#### 5.1.2.3 Use of VPCI
+
+The Connection identifier information element is used in signalling messages to identify the corresponding user information flow. The Connection identifier information element contains the Virtual Path Connection Identifier (VPCI) and the Virtual Channel Identifier (VCI). The VPCI is used instead of the Virtual Path Identifier (VPI) since virtual path cross connects may be used in the access and multiple interfaces could be controlled by the signalling virtual channel.
+
+Both the user and the network must understand the relationship between the VPCI used in the signalling protocol and the actual VPI used for the user information flow. VPCIs only have significance with regard to a given signalling virtual channel.
+
+If the signalling virtual channel only controls a single interface at the user side, the VPI and the VPCI have the same numerical value at the user side. Figure 5-1 below illustrates this.
+
+
+
+The diagram shows a 'User' block on the left connected to a 'VP cross connect' block (represented by an 'X'). From the User, three lines emerge labeled 'VPI = 0', 'VPI = 1', and 'VPI = 2'. These lines enter the VP cross connect block. From the cross connect block, three lines emerge labeled 'VPI = 20', 'VPI = 21', and 'VPI = 22'. These lines connect to two 'Network' blocks on the right. Below the cross connect block, a mapping is shown: '0 <-> 20', '1 <-> 21', and '2 <-> 22'.
+
+On the User side, a table shows:
+
+| VPCI | VPI |
+|------|-----|
+| 0 | 0 |
+| 1 | 1 |
+| 2 | 2 |
+
+On the Network side, two tables show:
+
+| VPCI | VPI |
+|------|-----|
+| 0 | 20 |
+| 1 | 21 |
+
+
+
+| VPCI | VPI |
+|------|-----|
+| 2 | 22 |
+
+T1162940-94/d040
+
+Diagram illustrating the mapping of VPCI to VPI through a VP cross connect for a single interface. On the user side, VPCI 0, 1, and 2 are mapped to VPI 0, 1, and 2 respectively. These are then cross-connected to network-side VPI values: VPI 0 maps to VPI 20, VPI 1 maps to VPI 21, and VPI 2 maps to VPI 22. The network-side mapping tables show VPCI 0 as VPI 20, VPCI 1 as VPI 21, and VPCI 2 as VPI 22.
+
+FIGURE 5-1/Q.2931
+Single interface controlled by SVC
+
+If the signalling channel controls multiple interfaces at the user side, the VPCI corresponds to both the interface and a VPI on the interface. See Figure 5-2.
+
+#### 5.1.2.4 VCI range
+
+The range of valid VCI values is indicated below:
+
+- 0 through 31 not used for on-demand user plane connections;
+- 32 through 65 535 identifier of the virtual channel (Note).
+
+NOTE – Some values in the range may not be available for use (e.g. some values may be used for permanent connections). The range of values available for use are determined at the subscription time.
+
+
+
+The diagram illustrates the mapping of Virtual Path Identifiers (VPI) and Virtual Path Component Identifiers (VPCI) across a VP cross connect. The User side has two interfaces, IFid = 0 and IFid = 1. The Network side uses VPI values 20, 21, 22, and 23. The mapping is as follows:
+
+- IFid = 0, VPI = 0 <-> VPI = 20
+- IFid = 0, VPI = 1 <-> VPI = 21
+- IFid = 1, VPI = 0 <-> VPI = 22
+- IFid = 1, VPI = 1 <-> VPI = 23
+
+Tables provided in the diagram:
+
+| VPCI | IFid | VPI |
+|------|------|-----|
+| 00 | 0 | 0 |
+| 01 | 0 | 1 |
+| 10 | 1 | 0 |
+| 11 | 1 | 1 |
+
+| VPCI | VPI |
+|------|-----|
+| 00 | 20 |
+| 01 | 21 |
+| 10 | 22 |
+| 11 | 23 |
+
+T1 162950-94/d041
+
+Diagram illustrating multiple interfaces controlled by SVC. It shows a User connected to a VP cross connect, which is then connected to a Network. The User has two interfaces: IFid = 0 and IFid = 1. The VP cross connect maps these to different VPI values in the Network. Tables show the mapping of VPCI, IFid, and VPI.
+
+FIGURE 5-2/Q.2931
+Multiple interfaces controlled by SVC
+
+#### 5.1.3 QOS and traffic parameters selection procedures
+
+The user shall indicate the QOS class in the Quality of Service parameter information element.
+
+If the network is able to provide the requested QOS class, the network shall progress the call to the called user. If the network is not able to provide the requested QOS class, the network shall reject the call, returning a RELEASE COMPLETE message with cause No. 49, "Quality of Service unavailable".
+
+The user shall indicate the requested peak cell rate in the ATM user cell rate information element.
+
+If the network is able to provide the requested peak cell rate, the network shall progress the call to the called user. If the network is not able to provide the requested peak cell rate, the network shall reject the call, returning a RELEASE COMPLETE message with cause No. 37, "user cell rate unavailable".
+
+### 5.1.4 Invalid call/connection control information
+
+If upon receiving the SETUP message, the network determines that the call information received from the user is invalid (e.g. invalid number), then the network shall initiate call clearing in accordance with 5.4 with a cause such as the following:
+
+- No. 1 "unassigned (unallocated) number";
+- No. 3 "no route to destination";
+- No. 22 "number changed"; or
+- No. 28 "invalid number format (address incomplete)".
+
+### 5.1.5 Call/connection proceeding
+
+If the network can determine that access to the requested service is authorized and available, the network shall send a CALL PROCEEDING message to the user to acknowledge the SETUP message and to indicate that the call is being processed and enter the Outgoing Call Proceeding state. When the user receives the CALL PROCEEDING message, the user shall stop timer T303, start timer T310, and enter the Outgoing Call Proceeding state.
+
+If the network determines that a requested service is not authorized or is not available, the network shall initiate call clearing in accordance with 5.4 with one of the following causes:
+
+- No. 57 "bearer capability not authorized";
+- No. 58 "bearer capability not presently available";
+- No. 63 "service or option not available, unspecified"; or
+- No. 65 "bearer service not implemented".
+
+If the user has received a CALL PROCEEDING message, but does not receive an ALERTING, CONNECT, or RELEASE message prior to the expiration of timer T310, then the user shall initiate clearing procedures towards the network with cause No. 102, "recovery on timer expiry".
+
+### 5.1.6 Call/connection confirmation indication
+
+Upon receiving an indication that user alerting has been initiated at the called address, the network shall send an ALERTING message across the user-network interface of the calling address and enter the Call Delivered state. When the user receives the ALERTING message, the user may begin an internally-generated alerting indication; shall stop timer T310 and shall enter the Call Delivered state.
+
+### 5.1.7 Call/connection acceptance
+
+Upon receiving an indication that the call has been accepted, the network shall send a CONNECT message across the user-network interface to the calling user and enter the Active state.
+
+This message indicates to the calling user that a connection has been established through the network and stops a possible local indication of alerting.
+
+On receipt of the CONNECT message, the calling user shall stop timer T310 (if running); stop any user-generated alerting indication; attach to the user plane virtual channel if not already done; send a CONNECT ACKNOWLEDGE message; and enter the Active state.
+
+At this point, an end-to-end connection is established.
+
+The network shall not take any action on receipt of a CONNECT ACKNOWLEDGE message when it perceives the call to be in the Active state.
+
+### 5.1.8 Call/connection rejection
+
+Upon receiving an indication that the network or the called user is unable to accept the call, the network shall initiate clearing at the originating user-network interface as described in 5.4, using the cause provided by the terminating network or the called user.
+
+### 5.1.9 Transit network selection
+
+When a Transit network selection information element is present, the call shall be processed according to Annex D. Some networks may not support transit network selection.
+
+## 5.2 Call/connection establishment at the destination interface – Point-to-point access configuration call offering
+
+Before these procedures are invoked, an assured mode Signalling AAL connection must be established between the user and the network. All layer 3 messages shall be sent to the Signalling AAL using an AAL-DATA-request primitive.
+
+### 5.2.1 Incoming call/connection request
+
+The network will indicate the arrival of a call at the user-network interface by transferring a SETUP message across the interface. The message shall always contain a call reference, selected according to the procedures given in 4.3. The network shall start timer T303 and enter the Call Present state. This message is sent by the network only if resources for the call are available; otherwise, the call is cleared towards the calling user with cause No. 47, "resources unavailable, unspecified".
+
+If *en bloc* receiving is used, the SETUP message shall contain all the information required by the called user to process the call. In this case, the SETUP message may contain the Broadband sending complete information element.
+
+Upon receipt of a SETUP message, the user shall enter the Call Present state.
+
+If the SETUP message includes the Broadband sending complete information element, *en bloc* receiving procedure shall be followed. Therefore, those users who support overlap receiving procedure shall recognize the Broadband sending complete information element.
+
+If timer T303 expires for the first time (i.e. no response is received by the network to the first SETUP message transmitted), the network shall retransmit the SETUP message and restart timer T303. If timer T303 expires for the second time (i.e. a response is also not received by the network to the second SETUP message transmitted), the network shall follow the procedures of 5.2.5.4.
+
+### 5.2.2 Address and compatibility check
+
+#### 5.2.2.1 Address check
+
+If an address check is not possible because address information is not included, the user shall perform compatibility checking.
+
+The user shall evaluate called party addressing information received in the SETUP message and proceed as described in B.3.1.
+
+#### 5.2.2.2 Compatibility check
+
+##### 5.2.2.2.1 General principles
+
+The user shall perform the compatibility check based on the compatibility information received in the SETUP message. In B-ISDN, there are two categories of compatibility information:
+
+- Broadband category 1 compatibility information is provided for both the network and the user to determine the attributes of the ATM connection. The broadband category 1 compatibility information is:
+ - broadband bearer capability information;
+ - end-to-end transit delay information;
+ - ATM traffic descriptor;
+ - Quality of Service parameter; and
+ - OAM traffic descriptor.
+
+Broadband category 1 compatibility information is always checked by the called user; if the compatibility check fails, the user is incompatible.
+
+- Broadband category 2 compatibility information is provided for the called user. The broadband category 2 compatibility information is:
+ - ATM adaptation layer parameter information (describing the user plane AAL);
+ - optional broadband low layer information; and
+ - optional broadband high layer information.
+
+Broadband category 2 compatibility information is always checked by the called user; if the compatibility check fails, the user is incompatible.
+
+NOTE – In this subclause, the term “called user” is the endpoint entity which is explicitly addressed. This may be an addressed interworking unit (IWU).
+
+##### 5.2.2.2.2 Point-to-point call/connection offering
+
+A user receiving a SETUP message shall perform compatibility checking before responding to that SETUP message. Any reference to “user” in 5.2.3 through 5.2.7 implicitly refers to a compatible user equipment. Annex B defines compatibility checking to be performed by users upon receiving a SETUP message.
+
+An incompatible user shall respond with a RELEASE COMPLETE message with cause No. 88, “incompatible destination”, and enter the Null state. The network shall process this RELEASE COMPLETE message in accordance with 5.2.5.3.
+
+### 5.2.3 Connection identifier (VPCI/VCI) allocation/selection – Destination
+
+Two cases exist:
+
+- 1) *associated signalling*
+
+The layer 3 signalling entity exclusively controls the VCs in the VPC which carries its signalling VC.
+
+- 2) *non-associated signalling*
+
+The layer 3 signalling entity controls the VCs in the VPC which carries its signalling VC and may control VCs in other VPCs.
+
+The user shall support the non-associated signalling procedures and may as an option support the associated signalling procedures. A subscription option is necessary if the network supports both non-associated and associated signalling.
+
+When the network receives a Connection identifier information element with the VP-associated signalling field (see Table 4-16) coded with a value not supported by the network, the call shall be rejected with cause No. 36, "VPCI/VCI assignment failure".
+
+#### 5.2.3.1 Associated signalling
+
+For associated signalling, the network indicates a VC in the VPC carrying the signalling VC. The VPC carrying the signalling VC is implicitly indicated.
+
+In the Connection identifier information element, the VP-associated signalling field is coded as "VP-associated signalling" in the Connection identifier information element and one of the following values is indicated in the preferred/exclusive field:
+
+- a) "exclusive VPCI; any VCI"; or
+- b) "exclusive VPCI; exclusive VCI".
+
+In case a), the user selects any available VCI within the VPC carrying the signalling VC. The selected VCI value is indicated in the Connection identifier information element in the first message returned by the user in response to the SETUP message (e.g. CALL PROCEEDING message). The VP-associated signalling field is coded as "VP-associated signalling". The preferred/exclusive field is coded as "exclusive VPCI; exclusive VCI".
+
+In case b), if the indicated VCI within the VPC carrying the signalling VC is available, the user selects it for the call. If the Connection identifier information element is not present in the first response message, the connection identifier in the SETUP message shall be assumed.
+
+In case a), if no VCI is available, a RELEASE COMPLETE message with cause No. 45, "no VPCI/VCI available", is sent by the user.
+
+In case b), if the indicated VCI is not available, a RELEASE COMPLETE message with the cause No. 35, "requested VPCI/VCI not available", is sent by the user.
+
+#### 5.2.3.2 Non-associated signalling
+
+For non-associated signalling, the network shall indicate one of the following in the SETUP message:
+
+- a) "exclusive VPCI; any VCI";
+- b) "exclusive VPCI; exclusive VCI"; or
+- c) no indication is included (i.e. the Connection identifier information element is not included in the SETUP message).
+
+In cases a) and b), if the indicated VPCI is available, the user selects it for the call. In case a), the user selects any available VCI in the VPCI. In case b), if the indicated VCI is available within the VPCI, the user selects it for the call. In case c), the user selects any available VPCI and VCI.
+
+In cases a) and c), the selected VPCI/VCI value is indicated in the Connection identifier information element in the first message returned by the user in response to the SETUP message (e.g. CALL PROCEEDING message). The VP-associated signalling field is coded as "explicit indication of VPCI". The preferred/exclusive field is coded as "exclusive VPCI; exclusive VCI".
+
+In case b), if the Connection identifier information element is not present in the first response message, the connection identifier in the SETUP message shall be assumed.
+
+In cases a) and b), if the specified VPCI is not available, a RELEASE COMPLETE message with cause No. 35, "requested VPCI/VCI not available", is sent by the user.
+
+In case a), if no VCI is available, a RELEASE COMPLETE message with cause No. 45, "no VPCI/VCI available", is sent by the user.
+
+In case b), if the VCI in the indicated VPCI is not available, a RELEASE COMPLETE message with cause No. 35, "requested VPCI/VCI not available", is sent by the user.
+
+In case c), if the user is not able to allocate a VCI in any VPCI, a RELEASE COMPLETE message with cause No. 45, "no VPCI/VCI available", is sent by the user.
+
+In case a), if the VPCI value in the first response message is not the VPCI value indicated by the network, a RELEASE message with cause No. 36, "VPCI/VCI assignment failure", shall be sent to the user.
+
+In case b), if the VPCI and VCI values in the first response message are not the VPCI and VCI values indicated by the network, a RELEASE message with cause No. 36, "VPCI/VCI assignment failure", shall be sent to the user.
+
+### 5.2.4 QOS and traffic parameter selection procedures
+
+The network shall indicate the QOS class in the Quality of Service parameter information element.
+
+If the user is not able to provide the requested QOS class, the user shall reject the call, returning a RELEASE COMPLETE message with cause No. 49, "Quality of Service unavailable".
+
+The cumulative end-to-end transit delay is indicated in the end-to-end transit delay information element. If the user is not able to accept the indicated end-to-end transit delay, the user shall reject the call, returning a RELEASE COMPLETE message with cause No. 49, "Quality of Service unavailable".
+
+The network shall indicate the peak cell rate in the ATM traffic descriptor information element.
+
+If the user is not able to provide the indicated peak cell rate, the user shall reject the call, returning a RELEASE COMPLETE message with cause No. 47, "resources unavailable, unspecified".
+
+### 5.2.5 Call/connection confirmation
+
+#### 5.2.5.1 Response to *en bloc* SETUP or completion of overlap receiving
+
+When the user determines that sufficient call set-up information has been received and compatibility requirements (see Annex B) have been satisfied, the user responds with either a CALL PROCEEDING, ALERTING, or CONNECT message (see Note), and enters the Incoming Call Proceeding, Call Received, or Connect Request state, respectively.
+
+NOTE – The CALL PROCEEDING message may be sent by the user that cannot respond to a SETUP message with an ALERTING, CONNECT, or RELEASE COMPLETE message before expiry of timer T303.
+
+An incompatible user shall respond by sending a RELEASE COMPLETE message with a cause value as specified in Annex B, and enter the Null state. The network processes this RELEASE COMPLETE message in accordance with 5.2.5.3.
+
+A busy user that satisfies the compatibility requirements indicated in the SETUP message shall normally respond with a RELEASE COMPLETE message with a cause No. 17, "user busy". The network processes this RELEASE COMPLETE message in accordance with 5.2.5.3.
+
+If the user wishes to refuse the call, a RELEASE COMPLETE message shall be sent with cause No. 21, "call rejected", and the user returns to the Null state. The network processes this RELEASE COMPLETE message in accordance with 5.2.5.3.
+
+#### 5.2.5.2 Receipt of CALL PROCEEDING and ALERTING
+
+Upon receipt of the CALL PROCEEDING message from a user, the network shall stop timer T303; start timer T310; and enter the Incoming Call Proceeding state.
+
+Upon receipt of the ALERTING message from a user, the network shall stop timers T303 or T310 (if running); start timer T301 (unless another internal alerting supervision timer function exists; e.g. incorporated in-call control); enter the Call Received state; and send a corresponding ALERTING message to the calling user.
+
+#### 5.2.5.3 Called user clearing during incoming call establishment
+
+If a RELEASE COMPLETE or RELEASE message is received before a CONNECT message has been received, the network shall stop timer T303, timer T310 or timer T301 (if running); continue to clear the call to the called user as described in 5.4.3; and clear the call to the calling user with the cause received in the RELEASE COMPLETE or RELEASE message.
+
+#### 5.2.5.4 Call failure
+
+If the network does not receive any response to the retransmitted SETUP message prior to the expiration of timer T303, then the network shall enter the Null state and initiate clearing procedures towards the calling user with cause No. 18, "no user responding".
+
+If the network has received a CALL PROCEEDING message, but does not receive an ALERTING, CONNECT, or RELEASE message prior to the expiration of timer T310, then the network shall initiate clearing procedures towards the calling user with cause No. 18, "no user responding", and initiate clearing procedures towards the called user with cause No. 102, "recovery on timer expiry".
+
+If the network has received an ALERTING message, but does not receive a CONNECT or RELEASE message prior to the expiration of timer T301 (or a corresponding internal alerting supervision timing function), then the network shall initiate clearing procedures towards the calling user with cause No. 19, "no answer from user (user alerted)", and initiate clearing procedures towards the called user with cause No. 102, "recovery on timer expiry".
+
+### **5.2.6 Call/connection acceptance**
+
+A user indicates acceptance of an incoming call by sending a CONNECT message to the network. Upon sending the CONNECT message, the user shall start timer T313 and enter the Connect Request state. If an ALERTING message had previously been sent to the network, the CONNECT message may contain only the call reference.
+
+If a call can be accepted, and no user alerting is required, a CONNECT message may be sent without a previous ALERTING message.
+
+### **5.2.7 Active indication**
+
+On receipt of the CONNECT message, the network shall stop (if running) timers T301, T303 and T310; enter the Connect Request state; send a CONNECT ACKNOWLEDGE message to the user; initiate procedures to send a CONNECT message towards the calling user; and enter the Active state.
+
+The CONNECT ACKNOWLEDGE message indicates completion of the connection establishment procedures. There is no guarantee of an end-to-end connection until a CONNECT message is received at the calling user. Upon receipt of the CONNECT ACKNOWLEDGE message, the called user shall stop timer T313; attach to the user plane virtual channel; and enter the Active state.
+
+When timer T313 expires prior to receipt of a CONNECT ACKNOWLEDGE message, the called user shall initiate clearing with cause No. 102, "recovery on timer expiry", in accordance with 5.4.3.
+
+## **5.3 Call/connection establishment at the destination – Point-to-multipoint access arrangement call offering**
+
+This capability is outside the scope of this Recommendation.
+
+## **5.4 Call/connection clearing**
+
+### **5.4.1 Terminology**
+
+The following terms are used in this Recommendation in the description of clearing procedures:
+
+- a VC channel is connected when the VC is part of a B-ISDN virtual connection established according to this Recommendation;
+- a VC is disconnected when the VC is no longer part of a B-ISDN virtual connection, but is not yet available for use in a new virtual connection;
+- a VC is released when the VC is not part of a B-ISDN virtual connection and is available for use in a new virtual connection. Similarly, a call reference that is released is available for re-use.
+
+### **5.4.2 Exception conditions**
+
+Under normal conditions, call clearing is usually initiated when the user or the network sends a RELEASE message and follows the procedures defined in 5.4.3 and 5.4.4 respectively. The only exception to the above rule is in response to a SETUP message, the user or network can reject a call/connection (e.g. because of the unavailability of a suitable virtual channel) by responding with a RELEASE COMPLETE message provided no other response has previously been sent; releasing the call reference; and entering the Null state.
+
+### 5.4.3 Clearing initiated by the user
+
+Apart from the exceptions identified in 5.4.2 and 5.6, the user shall initiate clearing by sending a RELEASE message; starting timer T308; disconnecting the virtual channel; and entering the Release Request state.
+
+The network shall enter the Release Request state upon receipt of a RELEASE message. This message then prompts the network to disconnect the virtual channel, and to initiate procedures for clearing the network connection to the remote user. Once the virtual channel used for the call has been disconnected, the network shall send a RELEASE COMPLETE message to the user; release both the call reference and virtual channel (i.e. connection identifier); and enter the Null state.
+
+NOTE – The RELEASE COMPLETE message has only local significance and does not imply an acknowledgement of clearing from the remote user.
+
+On receipt of the RELEASE COMPLETE message, the user shall stop timer T308; release the virtual channel; release the call reference; and return to the Null state.
+
+If timer T308 expires for the first time, the user shall retransmit a RELEASE message to the network with the cause number originally contained in the first RELEASE message; restart timer T308 and remain in the Release Request state. In addition, the user may indicate a second Cause information element with cause No. 102, “recovery on timer expiry”. If no RELEASE COMPLETE message is received from the network before timer T308 expires a second time, the user shall place the virtual channel in a maintenance condition; release the call reference; and return to the Null state. Equipment shall perform implementation dependent recovery, such as initiating restart procedures.
+
+When user initiates normal call/connection clearing, cause No. 16, “normal clearing” is used in the first clearing message.
+
+### 5.4.4 Clearing initiated by the network
+
+Apart from the exception conditions identified in 5.4.2 and 5.6, the network shall initiate clearing by sending a RELEASE message; starting T308; disconnecting the virtual channel; and entering the Release Indication state.
+
+The user shall enter the Release Indication state upon receipt of a RELEASE message. Once the virtual channel used for the call has been disconnected, the user shall send a RELEASE COMPLETE message to the network; release both its call reference and the virtual channel; and return to the Null state.
+
+On receipt of the RELEASE COMPLETE message, the network shall stop timer T308; release both the virtual channel and call reference; and return to the Null state.
+
+If timer T308 expires for the first time, the network shall retransmit the RELEASE message to the user with the cause number originally contained in the first RELEASE message; start timer T308; and remain in the Release Indication state. In addition, the network may indicate a second Cause information element with cause No. 102, “recovery on timer expiry”. If no RELEASE COMPLETE message is received from the user before timer T308 expires a second time, the network shall place the virtual channel in a maintenance condition; release the call reference; and return to the Null state. Equipment shall perform implementation dependent recovery, such as initiating restart procedures.
+
+### 5.4.5 Clear collision
+
+Clear collision can occur when both sides simultaneously transfer RELEASE messages related to the same call reference value. If the user receives a RELEASE message while in the Release Request state, the user shall stop timer T308; release the call reference and virtual channel; and enter the Null state (without sending or receiving a RELEASE COMPLETE message). If the network receives a RELEASE message while in the RELEASE Indication state, the network shall stop timer T308, release the call reference and virtual channel; and enter the Null state (without sending or receiving a RELEASE COMPLETE message).
+
+## 5.5 Restart procedure
+
+When a point-to-point configuration exists, then the user and the network shall implement these procedures.
+
+The restart procedure is used to return a virtual channel, all virtual channels in a virtual path, or all virtual channels controlled by the signalling virtual channel to the idle condition. The procedure is usually invoked when the other side of the interface does not respond to other call control messages or a failure has occurred (e.g. following the expiry of
+
+timer T308 due to the absence of response to a clearing message). It may also be initiated as a result of local failure, maintenance action or mis-operation.
+
+NOTE – The call reference flag of the global call reference applies to restart procedures. In the case when both sides of the interface initiate simultaneous restart requests, they shall be handled independently. In the case when the same user plane virtual channel(s) are specified, they shall not be considered free for re-use until all the relevant restart procedures are completed. In the RESTART message, the call reference flag of the global call reference is set to “0”, in the RESTART ACKNOWLEDGE message sent in response to a RESTART message, the call reference flag of the global call reference is set to “1”.
+
+The STATUS message shall use the global call reference, if it is sent in response to the receipt of a message with the global call reference. The call reference flag in this STATUS message shall be coded to “0” if the call reference flag in the received message was set to “1” and shall be coded to “1” if the call reference flag in the received message was set to “0”.
+
+### 5.5.1 Sending RESTART
+
+#### 5.5.1.1 Normal procedure
+
+A RESTART message is sent by the network or user equipment in order to return virtual channels to the idle condition. The Restart indicator information element shall be present in the RESTART message to indicate whether an “indicated virtual channel”, “all user plane virtual channels in the indicated VPC controlled via signalling virtual channel in which the RESTART message is sent”, or “all virtual channels controlled by the layer 3 entity” are to be restarted. If the Restart indicator information element is coded as “indicated virtual channel” or “all user plane virtual channels in the indicated VPC controlled via signalling virtual channel in which the RESTART message is sent”, then the Connection identifier information element shall be present to indicate which virtual channel or virtual path is to be returned to the idle condition. If the Restart indicator information element is coded as “all virtual channels controlled by layer 3 entity which sends the RESTART message”, then the Connection identifier information element shall not be included.
+
+Upon transmitting the RESTART message, the sender enters the Restart Request state, starts timer T316, and waits for a RESTART ACKNOWLEDGE message. Also, no further RESTART messages shall be sent until a RESTART ACKNOWLEDGE is received or timer T316 expires. Receipt of a RESTART ACKNOWLEDGE message stops timer T316 and indicates that the virtual channel(s) and associated resources [e.g. call reference value(s)] can be freed for re-use. The Null state shall be entered after the virtual channel and call reference value are released.
+
+The RESTART and RESTART ACKNOWLEDGE message shall contain the global call reference value (all zeros) to which the Restart Request state is associated. These messages are transferred using the AAL-DATA-request primitive.
+
+Calls associated with restart user plane virtual channels shall be cleared towards the remote parties using cause No. 41, “temporary failure”.
+
+#### 5.5.1.2 Exceptional procedures
+
+If a RESTART ACKNOWLEDGE message, is not received prior to the expiry of timer T316, one or more subsequent RESTART messages may be sent until a RESTART ACKNOWLEDGE message is returned. While timer T316 is running, the virtual channel(s) being restarted shall not be used to support new calls requested using the call set-up procedures. The number of consecutive unsuccessful restart attempts has a default limit of two. When this limit is reached, the originator of RESTART message shall make no further restart attempts and shall enter the Null state (REST 0). An indication will be provided to the appropriate maintenance entity. The virtual channel(s) is considered to be in an out-of-service condition until maintenance action has been taken.
+
+If a RESTART ACKNOWLEDGE message is received indicating a different set of virtual channels from the set indicated in the RESTART message, the RESTART ACKNOWLEDGE message shall be discarded.
+
+### 5.5.2 Receipt of RESTART
+
+#### 5.5.2.1 Normal procedures
+
+Upon receiving a RESTART message, the recipient shall enter the Restart state associated to the global call reference and start timer T317; it shall then initiate the appropriate internal actions to return the specified virtual channels to the idle condition and release all call references associated with the specified virtual channels. Upon completion of internal clearing, timer T317 shall be stopped and a RESTART ACKNOWLEDGE message transmitted to the originator, and the Null state (REST 0) entered. The RESTART ACKNOWLEDGE message shall indicate a Restart indicator information element containing the same information as received in the related RESTART message. In addition, the RESTART ACKNOWLEDGE message shall contain a Connection identifier information element containing the same information as received in the related RESTART message, if this is included.
+
+Calls associated with restart user plane virtual channels shall be cleared towards the remote parties using cause No. 41, "temporary failure".
+
+Even if all the specified virtual channels are in the idle condition or already in the process of restart to the idle condition, receiving entity shall transmit a RESTART ACKNOWLEDGE message to the originator upon receiving a RESTART message.
+
+If the Restart indicator information element is coded as "all virtual channels controlled by the layer 3 entity which sends the RESTART message", then all calls on all interfaces associated with the signalling virtual channel shall be cleared.
+
+If semi-permanent connections established by management procedures are implicitly specified (by specifying "all virtual channels that are controlled by the layer 3 entity which sends the RESTART message" or "all user plane virtual channels in the indicated VPC controlled via the signalling virtual channel in which the RESTART message is sent"), no action shall be taken on these virtual channels, but a RESTART ACKNOWLEDGE message shall be returned containing the appropriate indications (i.e. "all virtual channels controlled by the layer 3 entity which sends the RESTART message" or "all user plane virtual channels in the indicated VPC controlled via the signalling virtual channel in which the RESTART message is sent").
+
+If semi-permanent connections established by management procedures or reserved VPCI/VCIs (e.g. the point-to-point signalling virtual channel) are explicitly specified (by including a Connection identifier information element in the RESTART message), no action shall be taken on these virtual channels and a STATUS message may as an option be returned with cause No. 82, "identified channel does not exist", optionally indicating in the diagnostic field the virtual channel or virtual path that could not be handled.
+
+The following entities are released as a result of the Restart procedures:
+
+- virtual channels established by this Recommendation's procedures;
+- all resources associated with the released virtual channel (e.g. call reference value).
+
+The following entities are not released as a result of the Restart procedures:
+
+- permanent connections established by a network;
+- management system reserved virtual channels (e.g. point-to-point signalling virtual channel).
+
+#### 5.5.2.2 Exceptional procedures
+
+If timer T317 expires prior to completion of internal clearing, an indication shall be sent to the maintenance entity (i.e. a primitive shall be transmitted to the system management entity) and the Null state (REST 0) shall be entered.
+
+If the Restart indicator information element is coded as "all virtual channels controlled by the layer 3 entity which sends the RESTART message" and a Connection identifier information element is included, the Connection identifier information element is treated as described in 5.6.8.3.
+
+If the Restart indicator information element is coded as "indicated virtual channel" and the Connection identifier information element is not included, then the procedures in 5.6.7.1 shall be followed.
+
+If the Restart indicator information element is coded as "indicated virtual channel" or "all user plane virtual channels in the indicated VPC controlled via the signalling virtual channel in which the RESTART message is sent" and the Connection identifier information element contains an unrecognizable VPCI, then the procedures in 5.6.7.2 shall be followed.
+
+If the RESTART message is received in the Restart state, then the procedures in 5.6.4 shall be followed.
+
+## **5.6 Handling of error conditions**
+
+All messages which use the protocol discriminator Q.2931 user-network call control message must pass the checks described in 5.6.1 through 5.6.8.
+
+Detailed error handling procedures are implementation dependent and may vary from network to network. However, capabilities facilitating the orderly treatment of error conditions are provided for in this subclause and shall be provided in each implementation.
+
+Subclauses 5.6.1 through 5.6.8 are listed in order of precedence.
+
+### **5.6.1 Protocol discrimination error**
+
+When a message is received with a protocol discriminator coded other than Q.2931 user-network call control message, that message shall be ignored. "Ignore" means to do nothing, as if the message had never been received.
+
+### **5.6.2 Message too short**
+
+When a message is received that is too short to contain a complete Message length information element, that message shall be ignored.
+
+### **5.6.3 Call reference error**
+
+#### **5.6.3.1 Invalid call reference format**
+
+If the Call reference information element octet 1, bits 5 through 8 do not equal 0000, then the message shall be ignored.
+
+If the Call reference information element octet 1, bits 1 through 4 indicate a length other than 3 octets (see 4.3), then the message shall be ignored.
+
+#### **5.6.3.2 Call reference procedural errors**
+
+- a) Whenever any message except SETUP, RELEASE COMPLETE, STATUS ENQUIRY, or STATUS, is received specifying a call reference which is not recognized as relating to an active call or to a call in progress, the receiver shall initiate clearing by sending a RELEASE COMPLETE message with cause No. 81, "invalid call reference value", specifying the call reference in the received message and shall remain in the Null state.
+- b) When a RELEASE COMPLETE message is received specifying a call reference which is not recognized as relating to an active call or to a call in progress, no action should be taken.
+- c) When a SETUP message is received specifying a call reference which is not recognized as relating to an active call or to a call in progress, and with a call reference flag incorrectly set to "1", this message shall be ignored.
+- d) When a SETUP message is received specifying a call reference which is recognized as relating to an active call or to a call in progress, this SETUP message shall be ignored.
+- e) When any message except RESTART, RESTART ACKNOWLEDGE, or STATUS is received using the global call reference, no action should be taken on this message and a STATUS message using the global call reference with a call state indicating the current state associated with the global call reference and cause No. 81, "invalid call reference", shall be returned.
+- f) When a STATUS message is received specifying a call reference which is not recognized as relating to an active call or to a call in progress, the procedures of 5.6.12 shall apply.
+- g) When a STATUS ENQUIRY message is received specifying a call reference which is not recognized as relating to an active call or to a call in progress, the procedures of 5.6.11 shall apply.
+- h) When a RESTART message is received specifying the global call reference with a call reference flag incorrectly set to "1" or a RESTART ACKNOWLEDGE message is received specifying the global call reference with a call reference flag incorrectly set to "0", no action should be taken on this message and a STATUS message with a call state indicating the current state associated with the global call reference and cause No. 81, "invalid call reference", shall be returned.
+
+### **5.6.4 Message type or message sequence errors**
+
+The error procedures in this subclause apply only if the flag in the message compatibility instruction indicator is set to "message instruction field not significant". If it is set to "follow explicit instructions", the procedures in 5.7 take precedence.
+
+Whenever an unexpected message, except RELEASE, RELEASE COMPLETE, or an unrecognizable message is received in any state other than the Null state, no state change shall occur and a STATUS message shall be returned with one of the following causes:
+
+- a) No. 97 message type non-existent or not implemented; or
+- b) No. 101 message not compatible with call state.
+
+However, two exceptions to this procedure exist. The first exception is when the network or the user receives an unexpected RELEASE message in response to a SETUP message. In this case no STATUS or STATUS ENQUIRY message is sent. Whenever the network receives an unexpected RELEASE message, the network shall release the virtual channel; clear the network connection and the call to the remote user with the cause in the RELEASE message sent by the user or, if not included, cause No. 31, "normal, unspecified"; return a RELEASE COMPLETE message to the user; release the call reference; stop all timers; and enter the Null state. Whenever the user receives an unexpected RELEASE message, the user shall release the virtual channel; return a RELEASE COMPLETE message to the network; release the call reference; stop all timers; and enter the Null state.
+
+The second exception is when the network or the user receives an unexpected RELEASE COMPLETE message. Whenever the network receives an unexpected RELEASE COMPLETE message, the network shall disconnect and release the virtual channel; clear the network connection and the call to the remote user with the cause indicated by the user or, if not included, cause No. 111, "protocol error, unspecified"; release the call reference; stop all timers; and enter the Null state. Whenever the user receives an unexpected RELEASE COMPLETE message, the user shall disconnect and release the virtual channel; release the call reference; stop all timers; and enter the Null state.
+
+### **5.6.5 Message length error**
+
+If the message length indicated in the Message length information element is inconsistent with the length of the message actually received, the message shall be handled normally as far as possible and, if necessary, the error handling procedures of 5.6.6 shall be followed.
+
+### **5.6.6 General information element errors**
+
+The general information element error procedures may also apply to information elements in codesets other than 0. In that case, the diagnostics in the Cause information element may indicate information elements other than those in codeset 0 by applying the locking or non-locking shift procedures as described in 4.5.
+
+#### **5.6.6.1 Information element sequence**
+
+Variable length information elements may appear in any order within a message except for cases described in 4.5.1. If more than one information element of the same type is included in a message, and the repeated information elements do not immediately follow the preceding occurrence of this information element type (see 4.5.1), the receiving entity shall ignore subsequent information element of this type.
+
+#### **5.6.6.2 Duplicated information elements**
+
+If an information element is repeated in a message in which repetition of the information element is not permitted, only the contents of the information element appearing first shall be handled and where all subsequent repetitions of the information element shall be ignored. When repetition of information elements is permitted, and when the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored.
+
+#### **5.6.6.3 Coding standard error**
+
+If the user or the network receives an information element with the coding standard field indicating a coding standard that is not supported by the receiver, this information element shall be treated as an information element with a content error. Depending on the information element, the procedures as described in 5.6.7.2 or 5.6.8.2 shall be followed.
+
+### **5.6.7 Mandatory information element error**
+
+#### **5.6.7.1 Mandatory information element missing**
+
+When a message other than SETUP, RELEASE, or RELEASE COMPLETE is received which has one or more mandatory information elements missing, no action shall be taken on the message and no state change should occur. A STATUS message is then returned with cause No. 96, "mandatory information element is missing".
+
+When a SETUP message is received which has one or more mandatory information elements missing, a RELEASE COMPLETE message with cause No. 96, "mandatory information element is missing", shall be returned.
+
+When a RELEASE message is received with the Cause information element missing, the actions taken shall be the same as if a RELEASE message with cause No. 31, "normal, unspecified", was received (see 5.4), with the exception that the RELEASE COMPLETE message sent on the local interface contains cause No. 96, "mandatory information element is missing".
+
+When a RELEASE COMPLETE message is received with a Cause information element missing, it will be assumed that a RELEASE COMPLETE message was received with cause No. 31, "normal, unspecified".
+
+#### **5.6.7.2 Mandatory information element content error**
+
+The error procedures in this subclause apply only if the flag (bit 5) in the instruction field is set to "IE instruction field not significant". If it is set to "follow explicit instruction", the procedures in 5.7 take precedence.
+
+When a message other than SETUP, RELEASE, or RELEASE COMPLETE is received which has one or more mandatory information elements with invalid content, no action shall be taken on the message and no state change shall occur. A STATUS message is then returned with cause No. 100, "invalid information element contents".
+
+When a SETUP message is received which has one or more mandatory information elements with invalid content, a RELEASE COMPLETE message with cause No. 100, "invalid information element contents", shall be returned.
+
+When a RELEASE message is received with invalid content of the Cause information element, the actions taken shall be the same as if a RELEASE message with cause No. 31, "normal, unspecified", was received (see 5.4), with the exception that the RELEASE COMPLETE message sent on the local interface contains cause No. 100, "invalid information element contents".
+
+When a RELEASE COMPLETE message is received with invalid content of the Cause information element, it will be assumed that a RELEASE COMPLETE message was received with cause No. 31, "normal, unspecified".
+
+Information elements with a length exceeding the maximum length (given in clause 3) will be treated as information element with content error.
+
+NOTE – As an option of user equipment (e.g. B-NT2), cause values, location codes, and diagnostics which are not understood by the B-NT2 may be passed on to another entity (e.g. user or B-NT2) instead of treating the cause value as if it were cause No. 31, "normal, unspecified", and sending cause No. 100, "invalid information element contents", with the RELEASE COMPLETE message. This option is intended to aid user equipment to be compatible to future additions of cause values, location codes and diagnostics to the Recommendation.
+
+#### **5.6.8 Non-mandatory information element errors**
+
+The error procedures in this subclause apply only if the flag (bit 5) in the instruction field is set to "IE instruction field not significant". If it is set to "follow explicit instruction", the procedures in 5.7 take precedence.
+
+The following subclauses identify actions on information elements not recognized as mandatory.
+
+#### **5.6.8.1 Unrecognized information element**
+
+When a message is received that has one or more unrecognized information elements, then the receiving entity shall proceed as follows.
+
+Action shall be taken on the message and those information elements which are recognized and have valid content. When the received message is other than RELEASE or RELEASE COMPLETE, a STATUS message may be returned containing one Cause information element. The STATUS message indicates the call state of the receiver after taking action on the message. The Cause information element shall contain cause No. 99, "information element non-existent or
+
+not implemented", and the diagnostic field, if present, shall contain the information element identifier for each information element which was unrecognized. Subsequent actions are determined by the sender of the unrecognized information elements.
+
+If a clearing message contains one or more unrecognized information elements, the error is reported to the local user in the following manner:
+
+- a) when a RELEASE message is received which has one or more unrecognized information elements, a RELEASE COMPLETE message with cause No. 99, "information element non-existent or not implemented", shall be returned. The Cause information element diagnostic field, if present, shall contain the information element identifier for each information element which was unrecognized;
+- b) when a RELEASE COMPLETE message is received which has one or more unrecognized information elements, no action shall be taken on the unrecognized information.
+
+NOTE – The diagnostic(s) of cause No. 99 facilitates the decision in selecting an appropriate recovery procedure at the reception of a STATUS message. Therefore, it is recommended to provide cause No. 99 with diagnostic(s) if a layer 3 entity expects the peer to take an appropriate action at the receipt of a STATUS message, although inclusion of diagnostic(s) is optional.
+
+#### **5.6.8.2 Non-mandatory information element content error**
+
+When a message is received which has one or more non-mandatory information elements with invalid content, action shall be taken on the message and those information elements which are recognized and have valid content. A STATUS message may be returned containing one Cause information element. The STATUS message indicates the call state of the receiver after taking action on the message. The Cause information element shall contain cause No. 100, "invalid information element contents", and the diagnostic field, if present, shall contain the information element identifier for each information element which has invalid contents.
+
+Information elements with a length exceeding the maximum length (given in clause 3) will be treated as an information element with content error. But for access information elements (see Annex J), cause No. 43, "access information discarded" is used instead of cause No. 100, "invalid information element contents".
+
+#### **5.6.8.3 Unexpected recognized information element**
+
+When a message is received with a recognized information element that is not defined to be contained in that message, the receiving entity shall (except as noted below) treat the information element as an unrecognized information element and follow the procedures defined in 5.6.8.1.
+
+NOTE – Some implementations may choose to process unexpected recognized information elements when the procedure for processing the information element is independent of the message in which it is received.
+
+### **5.6.9 Signalling AAL connection reset**
+
+Whenever a Q.2931 entity is informed of a spontaneous Signalling AAL reset by means of the AAL-ESTABLISH-indication primitive, the following procedures apply:
+
+- a) for calls in the clearing phase (states N11, N12, U11 and U12), no action shall be taken;
+- b) for calls in the establishment phase (states N1, N3, N4, N6, N7, N8, N9, U1, U3, U4, U6, U7, U8 and U9) shall be maintained. Optionally, the status enquiry procedure may be invoked;
+- c) calls in the Active state shall be maintained, and the entity shall invoke the status enquiry procedures described in 5.6.11.
+
+### **5.6.10 Signalling AAL connection release**
+
+Whenever a Q.2931 entity is notified by its Signalling AAL connection release by means of the AAL-RELEASE-indication primitive, the following procedure shall apply:
+
+- a) any calls not in the Active state shall be cleared locally;
+- b) if there is at least one call in the Active state controlled by the released Signalling AAL connection, then timer T309 shall be started. If timer T309 is already running, it shall not be restarted.
+
+The Q.2931 entity shall request Signalling AAL re-establishment by sending an AAL-ESTABLISH-request primitive.
+
+When informed of Signalling AAL re-establishment by means of the AAL-ESTABLISH-confirm primitive, the following procedure shall apply:
+
+- stop timer T309; and
+- perform the status enquiry procedure according to 5.6.11 to verify the call state of the peer entity per each call/connection.
+
+If timer T309 expires prior to Signalling AAL re-establishment, the network shall clear the network connection and call to the remote user with cause No. 27, “destination out of order”; disconnect and release the bearer virtual channel; release the call reference; and enter the Null state.
+
+If timer T309 expires prior to Signalling AAL re-establishment, the user shall disconnect and release the virtual channel; release the call reference; and enter the Null state. The user may clear the attached internal connection (if any) with cause No. 27, “destination out of order”.
+
+### 5.6.11 Status enquiry procedure
+
+To check the correctness of a call state at a peer entity, a STATUS ENQUIRY message may be sent requesting the call state. This may, in particular, apply to procedural error conditions described in 5.6.9 and 5.6.10.
+
+In addition, whenever indication is received from the Signalling AAL that a disruption has occurred at the data link layer, a STATUS ENQUIRY message shall be sent to check the correctness of the call state at the peer entity.
+
+Upon sending the STATUS ENQUIRY message, timer T322 shall be started in anticipation of receiving a STATUS message. While timer T322 is running, only one outstanding request for call state information shall exist. Therefore, if timer T322 is already running, it shall not be restarted. If a clearing message is received before timer T322 expires, timer T322 shall be stopped and call clearing shall continue.
+
+Upon receipt of a STATUS ENQUIRY message, the receiver shall respond with a STATUS message, reporting the current call state (the current state of an active call or a call in progress, or the Null state if the call reference does not relate to an active call or to a call in progress) and cause No. 30, “response to STATUS ENQUIRY” (see 5.6.4). Receipt of the STATUS ENQUIRY message does not result in a state change.
+
+The sending or receipt of the STATUS message in such a situation will not directly affect the call state of either the sender or receiver. The side having received the STATUS message shall inspect the Cause information element. If a STATUS message is received that contains cause No. 30, “response to STATUS ENQUIRY”, timer T322 shall be stopped and the appropriate action taken, based on the information in that STATUS message, relative to the current state of the receiver.
+
+If timer T322 expires, and no STATUS message was received, the STATUS ENQUIRY message may be retransmitted one or more times until a response is received. The number of times the STATUS ENQUIRY message is retransmitted is an implementation dependent value. If following the maximum number of retransmissions of the STATUS ENQUIRY message, no STATUS message is received before expiry of T322 for the last time, the call shall be cleared to the local interface with cause No. 41, “temporary failure”. If appropriate, the network shall also clear the network connection, using cause No. 41, “temporary failure”.
+
+### 5.6.12 Receiving a STATUS message
+
+On receipt of a STATUS message reporting an incompatible state, the receiving entity shall:
+
+- a) clear the call by sending the appropriate clearing message with cause No. 101, “message not compatible with call state”; or
+- b) take other actions which attempt to recover from a mismatch and which are an implementation option.
+
+Except for the following rules, the determination of which states are incompatible is left as an implementation decision:
+
+- a) If a STATUS message indicating any call state except the Null state is received in the Null state, then the receiving entity shall send a RELEASE COMPLETE message with cause No. 101, “message not compatible with call state”; and remain in the Null state.
+
+- b) If a STATUS message indicating any call state except the Null state is received in the Release Request or Release Indication state, no action shall be taken.
+- c) If a STATUS message indicating the Null state is received in any state except the Null state, the receiver shall release all resources and move into the Null state.
+
+When in the Null state, the receiver of a STATUS message indicating the Null state shall take no action other than to discard the message and shall remain in the Null state.
+
+A STATUS message may be received indicating a compatible call state but containing one of the following causes:
+
+- No. 96 mandatory information element is missing;
+- No. 97 message type non-existing or not implemented;
+- No. 99 information element non-existent or not implemented;
+- No. 100 invalid information element contents; or
+- No. 101 message not compatible with call state.
+
+In this case, the actions to be taken are an implementation option. If other procedures are not defined, the receiver shall clear the call with the appropriate procedure defined in 5.4, using the cause specified in the received STATUS message.
+
+On receipt of a STATUS message specifying the global call reference and reporting an incompatible state in the Restart Request or Restart state, the receiving Q.2931 entity shall inform layer management and take no further action on this message.
+
+When in the Null state, then on receipt of a STATUS message with the global call reference no action shall be taken.
+
+NOTE – Further actions as a result of higher layer activity (e.g. system or layer management) are implementation dependent (including the retransmission of RESTART).
+
+Except for the above case, the error handling procedures when receiving a STATUS message specifying the global call reference are an implementation option.
+
+## 5.7 Error procedures with explicit action indication
+
+The procedures of this subclause shall only be used if the flag of the message compatibility instruction indicator or information element instruction field is set to “follow explicit instructions”.
+
+### 5.7.1 Unexpected or unrecognized message type
+
+If an unexpected or unrecognized message type is received in any state other than the Null state, the following procedures are applicable.
+
+If the action indicator bits of the instruction field of a Message type information element are set to “clear call” in any state other than the Release Request and Release Indication state, the call shall be cleared in accordance with procedures of 5.4.3 or 5.4.4, except that a Cause information element indicating cause No. 97, “message type non-existent or not implemented”, or cause No. 101, “message not compatible with call state”, shall be sent. When in the Release Request or in the Release Indication state, the receiver shall take no action and remain in the same state.
+
+If the action indicator bits of the instruction field of a Message type information element are set to “discard and ignore”, the message shall be ignored.
+
+If the action indicator bits of the instruction field of a Message type information element are set to “discard, and report status”, no action shall be taken on the message but a STATUS message shall be sent with a Cause information element indicating cause No. 97, “message type non-existent or not implemented” or cause No. 101, “message not compatible with call state”.
+
+If the message action indicator bits are set to an undefined (reserved) value, the receiver shall handle the message as if the message action indicator bits had been set to “discard and report status”.
+
+### 5.7.2 Information element errors
+
+When a message other than a RELEASE or RELEASE COMPLETE message is received which has one or more unexpected information elements, unrecognized information elements or information elements with unrecognized contents, the receiving entity shall examine the information element action indicator, and follow the procedures described in a), b), c), d) or e) below as appropriate.
+
+When a RELEASE message is received with one or more information elements in error, a RELEASE COMPLETE message with cause No. 99, "information element non-existent or not implemented" or with cause No. 100, "invalid information element contents", shall be returned.
+
+When a RELEASE COMPLETE message is received with one or more information elements in error, no action shall be taken on the information elements in error. The message shall be processed as if received without the information elements in error.
+
+If more than one information element is received in error, only one response shall be given. The response shall be according to the handling of the action indicator field according to the following order of priority: "clear call" (highest priority), "discard message and report status", "discard message, and ignore", "discard information element, proceed, and report status", "discard information element and proceed".
+
+- a) Action indicator field = clear call
+
+If the action indicator field is equal to "clear call", the call shall be cleared according to the procedures defined in 5.4 except that the Cause information element shall contain cause No. 99, "information element non-existent or not implemented" or cause No. 100, "invalid information element contents".
+
+- b) If the action indicator field = discard message and report status
+
+The message shall be ignored and a STATUS message shall be sent with a cause No. 99 "information element non-existent or not implemented" or cause No. 100 "invalid information element contents".
+
+- c) If the action indicator field = "discard message"
+
+The message shall be ignored.
+
+- d) Action indicator field = discard information element, proceed and report status
+
+If the message contains sufficient information to proceed, the following shall apply:
+
+if the action indicator field specifies "discard information element, proceed and report status", the information element shall be discarded, the handling of the message shall proceed and a STATUS message shall be returned indicating the call state of the receiver after taking action on the message and containing cause No. 99, "information element non-existent or not implemented" or cause No. 100, "invalid information element contents".
+
+- e) Action indicator field = discard information element and proceed
+
+If the action indicator field is equal to "discard information element and proceed", the information element shall be ignored and the message shall be processed as if the information element was not received. No STATUS message shall be sent.
+
+- f) Action indicator field = undefined (reserved) value
+
+The receiver shall handle the information element as if the action indicator field had been set to "discard information element, proceed, and report status".
+
+## 5.8 Handling of messages with insufficient information
+
+If insufficient information for the protocol entity to act upon a message is available, the procedures of 5.6.7.1 shall apply if the flag of the message compatibility instruction indicator is set to "message instruction field not significant" or the procedures of 5.7.1 shall apply if the flag of the message compatibility instruction indicator is set to "follow explicit instruction" with the difference that when a Cause information element is to be returned, it shall include cause No. 96 "mandatory information element is missing".
+
+## 5.9 Notification procedures
+
+The delivery of bearer-related notifications shall use an active call reference of the call/connection the notification is associated with. In this context, a call reference shall be active from the initiation of call establishment (i.e. the SETUP message) to the initiation of call clearing (i.e. the RELEASE message).
+
+If the delivery of the notification coincides with call/connection establishment or clearing procedures, the notification information can be carried in the associated call control messages. In all other cases, the notification information shall be delivered in a NOTIFY message. In addition, a NOTIFY message may be sent or received by the user or by the network only after the first response to a SETUP message has been sent or received and before clearing of the call reference is initiated.
+
+If a notification is received by the network, the network shall optionally ensure that the contents of the notification are a valid coding; and forward the notification to the other user involved in the call.
+
+No call state change shall occur at either side of the interface following the sending or receipt of a NOTIFY message.
+
+# 6 Procedures for the support of 64 kbit/s based circuit-mode ISDN services in B-ISDN and access signalling interworking between N-ISDN and B-ISDN
+
+This clause specifies the particular features required to provide 64 kbit/s based circuit-mode ISDN services in B-ISDN and to support access signalling interworking between B-ISDN and N-ISDN. For the 64 kbit/s based circuit-mode ISDN services also the term “N-ISDN services” is used. This term includes the circuit-mode services described in the I.200-Series of Recommendations and supported by the DSS 1 signalling protocol. For these services interworking with N-ISDN is possible.
+
+The description of service provision and interworking in this clause assumes the communication scenario B as defined in Annex A/1.580 [58].
+
+## 6.1 Introduction
+
+The procedures defined in this Recommendation are based on the principle that no difference is made between the provision of N-ISDN services in a pure B-ISDN environment and the provision of these services in the case of interworking with the N-ISDN.
+
+In order to allow signalling interworking between B-ISDN and N-ISDN, separate service related information elements are defined for N-ISDN services and for B-ISDN services.
+
+For the provision of N-ISDN services, basically the DSS 1 information elements Bearer capability, High layer compatibility and Low layer compatibility are defined in B-ISDN. In DSS 2 these information elements are designated as Narrow-band Bearer Capability (N-BC), Narrow-band Low Layer Compatibility (N-LLC) and Narrow-band High Layer Compatibility (N-HLC). For their application in B-ISDN, the DSS 1 information elements are modified according to the DSS 2 coding rules, i.e. octet 2 contains the information element instruction field with the Flag bit set to “0” (see also 6.3.2) and octets 3 and 4 indicate the length of contents. These information elements are specified in 4.6.
+
+NOTE – The benefit of taking the DSS 1 service related information elements nearly unchanged in DSS 2 is that it significantly simplifies interworking between B-ISDN and N-ISDN (see 6.3 and 6.4). Another important benefit is that by dividing the service related attributes into N-ISDN and B-ISDN related parts, a decoupling of the DSS 2 specific information elements from the evolution of the DSS 1 based information elements is achieved.
+
+The reason for taking the DSS 1 information elements even for the provision of N-ISDN services in a pure B-ISDN environment is that a B-ISDN user cannot know in advance whether the destination of a call will be a B-ISDN (DSS 2) or a N-ISDN (DSS 1) user.
+
+Table 6-1 shows the information elements required for the provision of N-ISDN services in B-ISDN.
+
+TABLE 6-1/Q.2931
+
+### **Information elements in B-ISDN to provide N-ISDN services**
+
+| | Information elements used to describe network relevant bearer attributes | Information elements used to describe lower layer attributes (transparent for B-ISDN) | Information elements used to describe high layer attributes |
+|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|
+| N-ISDN related information elements (see 4.6) | Narrow-band Bearer Capability (N-BC) | Narrow-band Low Layer Compatibility (N-LLC) | Narrow-band High Layer Compatibility (N-HLC) |
+| B-ISDN related information elements (see 4.5) | - – Broadband Bearer Capability (B-BC)
- – ATM traffic descriptor
- – QOS parameter
- – End-to-end transit delay (optional)
- – OAM traffic descriptor (optional)
| - – ATM adaptation layer parameters (AAL parameters)
| – |
+
+Subclause 6.2 describes which N-ISDN service-related information elements are included in this Recommendation. Subclauses 6.3 and 6.4 specify the interworking functions between B-ISDN and N-ISDN. These subclauses specify the interworking between the DSS 2 and the DSS 1 protocol. Interworking functions within the public network (i.e. between N-ISUP and B-ISUP) are outside the scope of this Recommendation.
+
+## 6.2 Information elements for N-ISDN services in B-ISDN
+
+### 6.2.1 General aspects
+
+When N-ISDN services are requested in a B-ISDN environment, in principle the information elements of this Recommendation (e.g. "Called party number", see 4.5) are used in the same manner as for B-ISDN specific services. However, for the service-related attributes listed in Table 6-1, specific information elements (see upper line of Table 6-1) are re-used for compatibility checking as described in Annex B and for the provision of the N-ISDN services as described below.
+
+The following subclauses (see 6.2.2 to 6.2.4) only describe the use of the service-related information elements in the SETUP message. However, in the case of service negotiation they may also be included in the first response message returned to the call initiating entity.
+
+### 6.2.2 Bearer-service related information
+
+The B-BC information element is always included in the SETUP message. This information element is mandatory for all services. It is interpreted by the B-ISDN. For N-ISDN services, the N-BC information element is also mandatory in the SETUP message. Unlike the B-BC information element, however, the N-BC information element is only interpreted when tones/announcements according to 6.7.1 have to be provided.
+
+The N-BC information element is included in the SETUP message even if no interworking takes place, since the user is not able to know in advance whether the receiver of the SETUP message will be a B-ISDN (DSS 2) or a N-ISDN (DSS 1) user.
+
+The ATM traffic descriptor information element is always included in the SETUP message.
+
+For N-ISDN services, a value for the ATM user cell rate is selected such, that the bit rate of the N-ISDN service (64 kbit/s or $n \times 64$ kbit/s) can be transported as the cell payload of the ATM cells, i.e. excluding the overhead of the ATM cell and the AAL header.
+
+The Quality of Service parameter information element is always included in the SETUP message indicating the unspecified QOS class.
+
+The end-to-end transit delay information element may be included in the SETUP message and coded according to 4.5.17.
+
+The OAM traffic descriptor information element may be included in the SETUP message and coded according to 4.5.24.
+
+### 6.2.3 Low layer related information
+
+If required for the description of a particular N-ISDN service, the N-LLC information element is included in the SETUP message.
+
+The B-LLI information element is only used for B-ISDN specific services.
+
+The N-LLC and the B-LLI information elements shall be used according to the following rules:
+
+- 1) The N-LLC information element is used to describe end-to-end attributes of N-ISDN circuit-mode services supported in B-ISDN. This information element shall not be used for B-ISDN specific services. In particular, this information element is used by:
+ - a B-ISDN terminal emulating a N-ISDN service; and
+ - between a TA (connecting a N-ISDN-TE to B-ISDN) and a B-ISDN network.
+- 2) For B-ISDN specific services, the B-LLI information element is used as described in the main part of this Recommendation.
+- 3) Either the N-LLC or the B-LLI information element can be used in a call, not both.
+- 4) If B-ISDN specific user equipment are connected to B-ISDN which do not support emulation of N-ISDN services, only the B-LLI information element is to be used (not the N-LLC information element).
+
+The use of the N-LLC and B-LLI information elements is illustrated in Figure 6-1.
+
+The N-LLC information element is transported transparently through the B-ISDN.
+
+The destination user shall ignore the conflicting information in the N-LLC information element if it detects a contradiction between the N-BC information element and N-LLC information element.
+
+NOTE – It is expected that some B-ISDNs will support only A-law and some others only $\mu$ -law coding; with conversion provided by the $\mu$ -law network (see Recommendation G.711 [3]) for the provision of emulated N-ISDN services. If the encoding scheme is specified in both the N-BC information element and the N-LLC information element, interworking between two B-ISDNs might require a change of the user information layer 1 protocol in the N-BC information element (e.g. from A-law to $\mu$ -law), while the encoding scheme specified in the N-LLC information element would presumably be forwarded unchanged to the destination. Since, to determine compatibility, the destination terminal examines both the N-BC information element and the N-LLC information element, it would receive conflicting information regarding the encoding scheme used.
+
+For the provision of N-ISDN services, the inclusion of the AAL parameters information element in the SETUP message is required, specifying either AAL type 1 or the AAL for voice.
+
+### 6.2.4 High layer related information
+
+If required for the description of a particular N-ISDN service, the N-HLC information element is included in the SETUP message. The N-HLC information element is transported transparently through the B-ISDN. No specific B-ISDN information element describing high layer attributes is required.
+
+
+
+Diagram illustrating the use of N-LLC and B-LLI information elements in an ISDN network. A central 'B-ISDN network' box is connected to various terminals. At the top, two 'B-ISDN TE (B-ISDN specific service)' units connect via 'B-LLI'. Below them, two 'B-ISDN TE (N-ISDN service)' units connect via 'N-LLC in DSS 2'. At the bottom, four 'N-TE' units are shown. Two connect via 'N-NT2' and 'IWF' using 'LLC in DSS 1' and 'N-LLC in DSS 2'. The other two connect via 'TA\*' using 'LLC in DSS 1' and 'N-LLC in DSS 2'.
+
+T1165740-94/d042
+
+\* The LLC information is transferred transparently across the Terminal Adapter (TA) or Interworking Function (IWF), except for the changes required by the different coding rules.
+
+FIGURE 6-1/Q.2931
+**Illustration of the use of the N-LLC and B-LLI information elements in this Recommendation**
+
+### 6.2.5 Handling of inconsistent combination of service parameters
+
+If the network receives a SETUP message with an inconsistent combination of broadband (i.e. B-HLI and B-LLI information elements) and narrow-band service parameters (i.e. N-BC, N-HLC and N-LLC information elements), the network may clear the call with cause No. 79, "service or option not implemented, unspecified".
+
+## 6.3 Interworking N-ISDN → B-ISDN
+
+### 6.3.1 Introduction
+
+This subclause describes the functions performed by a Terminal Adapter (TA) or an Interworking Function (IWF) in the case of a call originated in the N-ISDN and routed to the B-ISDN according to scenario B/Recommendation I.580 [58]. For the detailed mapping of code points, see Annex E.
+
+### 6.3.2 Bearer-service related information
+
+The DSS 1-BC information element is mapped to the N-BC information element by the TA or the IWF by simply inserting the second octet containing the IE instruction field and changing the length indication from one to two octets. The Flag bit in the second octet is set to "0", i.e. the normal error handling procedures as defined in 5.6 apply.
+
+In addition to the N-BC information element, the B-BC information element is created by the TA or IWF, indicating BCOB-A and the value susceptible to clipping in the susceptibility to clipping field.
+
+The ATM traffic descriptor and the QOS parameter information elements are also generated by the TA or IWF, evaluating the information of the DSS 1-BC information element.
+
+The end-to-end transit delay information element and the OAM traffic descriptor information element are not created by the TA or IWF.
+
+For further details, see Annex E.
+
+### **6.3.3 Low layer compatibility information**
+
+The DSS 1-LLC information element (if included) is mapped to the N-LLC information element by the TA or IWF without change of contents. Simply, the new octet 2 is inserted in the same way as described in 6.3.2 for the N-BC information element and the length indication is adapted.
+
+The AAL parameters information element is generated by the TA or IWF, indicating either AAL-type 1 or the AAL for voice. For further details, see Annex E.
+
+### **6.3.4 High layer compatibility information**
+
+The DSS 1-HLC information element (if included) is mapped to the N-HLC information element by the TA or IWF without change of contents. Simply, the new octet 2 is inserted in the same way as described in 6.3.2 for the N-BC information element and the length indication is adapted.
+
+### **6.3.5 Cause information**
+
+The DSS 1 Cause information element is mapped to the DSS 2 Cause information element by the TA or IWF by simply inserting the second octet containing the IE instruction field and changing the length indication from one to two octets.
+
+The Flag bit in the second octet is set to "0", i.e. the normal error handling procedures as defined in 5.6 apply.
+
+## **6.4 Interworking B-ISDN → N-ISDN**
+
+This subclause describes the functions to be performed by a Terminal Adapter (TA) or an Interworking Function (IWF) in the case of a call originated in the B-ISDN and routed to the N-ISDN according to scenario B/Recommendation I.580 [58].
+
+### **6.4.1 Introduction**
+
+If a B-TE initiates a call to a N-TE, only N-ISDN service related information elements will be processed by the IWF or TA. If a B-ISDN specific service is selected by the B-TE and routed towards the N-ISDN, then the call shall be rejected by the IWF or TA with cause No. 63, "service or option not available, unspecified".
+
+### **6.4.2 Bearer-service related information**
+
+The B-BC, the ATM traffic descriptor, the QOS parameter, the end-to-end transit delay and the OAM traffic descriptor information elements are discarded by the IWF or TA.
+
+The N-BC information element is mapped to the DSS 1-BC information element by the IWF or TA, by simply removing its second octet and adjusting the length indication, without causing other changes to the contents.
+
+If no N-BC information element is included in the SETUP message, then a B-ISDN service shall be assumed and the call shall be rejected by the IWF or TA, with cause No. 63, "service or option not available, unspecified".
+
+### **6.4.3 Low layer compatibility information**
+
+The AAL parameter information element is discarded by the IWF or TA.
+
+The N-LLC information element (if included) is mapped to the DSS 1-LLC information element by the IWF or TA by simply removing its second octet and adjusting the length indication without causing other changes to the contents.
+
+If a B-LLI information element is detected by the IWF or TA, and service interworking for the indicated service is not provided, then the call shall be rejected by the IWF or TA, with cause No. 63, "service or option not available, unspecified".
+
+### 6.4.4 High layer compatibility information
+
+The N-HLC information element (if included) is mapped to the DSS 1-HLC information element by the IWF or TA by simply removing its second octet and adjusting the length indication without causing other changes to the contents.
+
+If a B-HLI information element is detected by the IWF or TA, then the call shall be rejected with cause No. 63, "service or option not available, unspecified".
+
+### 6.4.5 Cause information
+
+For the mapping of the DSS 2 Cause information element to the DSS 1 Cause information element, the following rules shall apply:
+
+- a) Any broadband specific cause value where there is no equivalent value in the DSS 1 protocol is mapped to the unspecified value of the same class, e.g. the DSS 2 cause values:
+- | | |
+|----------------------------------------------------|------------------------------------------------------------------------------------------|
+| – 35 Requested VPCI/VCI not available | } Are mapped to the DSS 1 cause value 47: Resource unavailable, unspecified |
+| – 36 VPCI/VCI assignment failure | |
+| – 37 User cell rate not available and | |
+| – 45 No VPCI/VCI available | |
+| – 73 Unsupported combination of traffic parameters | } Are mapped to the DSS 1 cause value 79: Service or option not implemented, unspecified |
+| – 93 AAL parameters cannot be supported | |
+- b) Any cause value and diagnostic used in both DSS 2 and DSS 1 protocol is not changed by the TA or IWF.
+- c) If any cause value used in the DSS 2 protocol is received by the TA or IWF for which a diagnostic field may be present (e.g. cause value 82) while the same cause value of the DSS 1 protocol does not allow for a diagnostic field, then the TA or IWF shall discard the diagnostic field and leave the cause value unchanged.
+- d) In addition to the actions described in items a) to c), the DSS 2 Cause information element is changed in the same manner as the other DSS 2 information elements, i.e. the second octet is discarded and the length indication is adjusted.
+
+## 6.5 Overlap sending and receiving
+
+### 6.5.1 Objectives
+
+B-ISDN terminal equipment (B-TE) shall use *en bloc* sending in B-ISDN. This implies, from the B-TE perspective, the mandatory inclusion of the Broadband sending complete information element in the SETUP message.
+
+Since overlap receiving is an allowed procedure in N-ISDN, this procedure is also supported in B-ISDN for incoming calls originating in the N-ISDN.
+
+In order to allow also terminal equipment designed for the N-ISDN to be connected to the B-ISDN via a terminal adapter or via a customer's network, the DSS 2 protocol supports also overlap sending.
+
+The procedures of DSS 2 for overlap sending and receiving are specified in 6.5.2 and 6.5.3.
+
+### 6.5.2 Overlap sending
+
+If overlap sending is used, the SETUP message contains either:
+
+- a) no called number information; or
+- b) incomplete called number information; or
+- c) called number information which the network cannot determine to be complete.
+
+On receipt of such a SETUP message, the network starts timer T302 (the value of this timer is specified in 7.1), sends a SETUP ACKNOWLEDGE message to the user, and enters the Overlap Sending state.
+
+When the SETUP ACKNOWLEDGE message is received, the user enters the Overlap Sending state and optionally starts timer T304 (the value of this timer is specified in 7.2).
+
+After receiving the SETUP ACKNOWLEDGE message, the user sends the remainder of the call information (if any) in one or more INFORMATION messages.
+
+The called party number information shall be provided by the user in the Called party number information element.
+
+If, for symmetry purposes, the user employs timer T304, the user restarts T304 when each INFORMATION message is sent.
+
+The call information in the message that completes the information sending may contain a “sending complete” indication (i.e. the Broadband sending complete information element). The network restarts timer T302 on the receipt of every INFORMATION message not containing a sending complete indication.
+
+### 6.5.3 Overlap receiving
+
+When a user determines that a received message contains either:
+
+- a) no called number information; or
+- b) incomplete called number information; or
+- c) called number information which the user cannot determine to be complete;
+
+and when the user:
+
+- is compatible with the other call characteristics (see Annex B); and
+- implements overlap receiving;
+
+the user shall start timer T302; send a SETUP ACKNOWLEDGE message to the network; and enter the Overlap Receiving state.
+
+When the SETUP ACKNOWLEDGE message is received, the network shall stop timer T303; start timer T304; enter the Overlap Receiving state; and send the remainder of the call information (if any) in one or more INFORMATION messages, starting timer T304 when each INFORMATION message is sent.
+
+The called party number information is provided in the Called party number information element.
+
+The called address information may contain a sending complete indication (i.e. the Broadband sending complete information element).
+
+NOTE 1– It is recommended that the network inserts the Broadband sending complete information element in the INFORMATION message which is delivered to the called user if the network can determine that this message contains the last digit(s) of the called party number.
+
+The user shall start timer T302 on receipt of every INFORMATION message not containing a sending complete indication.
+
+Following the receipt of a sending complete indication, or the determination that sufficient call information has been received, the user shall stop timer T302 (if implemented) and send a CALL PROCEEDING message to the network. Alternatively, depending on internal events, the user may send an ALERTING or CONNECT message to the network.
+
+NOTE 2 – The CALL PROCEEDING message in this case will cause the originating exchange to send a CALL PROCEEDING message to the originating user, if not already sent.
+
+At the expiration of timer T302, the user shall either:
+
+- a) send a CALL PROCEEDING, ALERTING or CONNECT message as appropriate if sufficient information has been received; or
+- b) initiate clearing in accordance with 5.4 with cause No. 28, "invalid number format (incomplete number)" if it determines that the call information is definitely incomplete.
+
+At the expiration of timer T304, the network initiates call clearing in accordance with 5.4 with cause No. 28, "invalid number format (incomplete number)" sent to the calling user, and cause No. 102, recovery on timer expiry, sent to the called user.
+
+If, following the receipt of a SETUP message or during overlap receiving, the user determines that the received call information is invalid (e.g. invalid called party number), it shall initiate call clearing in accordance with 5.4 with a cause such as one of the following:
+
+- No. 1 unassigned (unallocated) number;
+- No. 3 no route to destination;
+- No. 22 no route to destination;
+- No. 28 invalid number format (incomplete number).
+
+Upon receipt of the complete call information, the user may further perform compatibility checking functions, as outlined in Annex B.
+
+## 6.6 Notification of interworking
+
+Interworking of B-ISDN with N-ISDN requires the support of the progress indicator values specified in Recommendation Q.931 [33] by the B-ISDN.
+
+The following principles shall apply:
+
+- 1) Interworking with a non-ISDN may occur in the case where an emulated N-ISDN service is requested and interworking with N-ISDN has occurred. In this case, all progress indicator values applying for N-ISDN interworking with non-ISDN shall be relayed to B-ISDN, transported transparently through the B-ISDN and then be indicated to the calling user.
+- 2) In the case of a call leaving or entering the B-ISDN at the IWF or TA, the IWF/TA shall not generate a DSS 1- or DSS 2-Progress indicator information element.
+
+The DSS 1-Progress indicator information element shall be mapped to the DSS 2-Progress indicator information element by adding or removing octet 2, dependent on the direction of the call and adjusting the coding of the length indication.
+
+### 6.6.1 Notification of interworking at the originating interface
+
+If the Progress indicator information element is included in a call control message, the procedures as described in 5.1 apply. If the Progress indicator information element is included in the PROGRESS message, no state change will occur but the network shall stop any supervisory timers except network timers T302 and T322 if the progress description is No. 1, No. 2 or, optionally, No. 4. In both cases, if indicated by the Progress indicator information element, the user shall connect to (if not connected already) and then monitor the user virtual channel for further in-band information.
+
+### 6.6.2 Notification of interworking at the terminating interface
+
+If the Progress indicator information element is included in a call control message, the procedures as described in 5.2 apply. If the Progress indicator information element is included in the PROGRESS message, no state change will occur but the network shall stop any supervisory timers except network timers T301, T304, T312 and T322 if the progress description is No. 1, No. 2 or, optionally, No. 4.
+
+## 6.7 Additional features with regard to the provision of N-ISDN services
+
+### 6.7.1 Tones and announcements
+
+#### 6.7.1.1 General principle
+
+For the provision of tones and announcements, the following principles shall apply:
+
+- Tones and announcements are provided by the network only if the N-BC information element is present and indicates speech, 3.1 kHz audio or Unrestricted digital information with tones and announcements.
+- Tones and announcements are coded according to Recommendation G.711 [3] (i.e. these are basically 3.1 kHz audio signals).
+- Tones and announcements are conveyed through the B-ISDN using the connection-oriented bearer service, Class A.
+- Tones and announcements generated in a non-B-ISDN are converted into ATM cells (using the AAL for voice) at the IWF.
+- Tones and announcements generated in the B-ISDN are converted into the 64 kbit/s stream at the IWF.
+
+The traffic and protocol parameters for the provision of tones and announcements with ATM cells shall have the same code point values as those for speech or 3.1 kHz audio services defined in E.4.
+
+Figure 6-2 illustrates a possible scenario for the provision of the ringback tone. The provision of other tones is not shown.
+
+
+
+The diagram shows a call flow across three domains: B-ISDN, IWF (Interworking Function), and Non-B-ISDN. On the left, in the B-ISDN domain, a 'Call originator' sends a 'Tone (Note)' which is represented by a series of four square-wave-like pulses. These pulses travel towards the IWF. The IWF is shown as a central vertical rectangle. On the right, in the Non-B-ISDN domain, there is another 'Call originator' connected to two telephone icons. A 'Tone' signal, represented by a continuous sine-like wave, is generated in the Non-B-ISDN domain and travels towards the IWF. The IWF converts the tone from the Non-B-ISDN domain into the B-ISDN format (the four pulses) and sends it back to the first call originator. The diagram is labeled with 'B-ISDN', 'IWF', and 'Non-B-ISDN' at the top. A reference code 'T1165750-94/d043' is in the bottom right corner.
+
+Diagram illustrating the provision of the ringback tone across B-ISDN, IWF, and Non-B-ISDN domains.
+
+NOTE – This tone shall be provided by the terminating exchange but may be provided by a non-B-ISDN functional entity of that exchange.
+
+FIGURE 6-2/Q.2931
+
+Possible scenario for the provision of the ringback tone
+
+#### 6.7.1.2 Provision of tones at call establishment
+
+On receipt of a SETUP message with no called number information, the network will return dial tone, if required by the tone option. In this case, it may include progress indicator No. 8 in-band information or appropriate pattern now available in the SETUP ACKNOWLEDGE message.
+
+The user need not attach to the virtual channel until receiving a CALL PROCEEDING / SETUP ACKNOWLEDGE / PROGRESS / ALERTING message with the progress indicator No. 8 in-band information or appropriate pattern now available or progress indicator No. 1 call is not end-to-end ISDN; further call progress information may be available in-band. Prior to this time, the network cannot assume that the user has attached to the virtual channel. After this time, the user shall be connected to the virtual channel, provided the equipment does not generate the tone locally. Upon receipt of the CONNECT message, the user shall attach to the virtual channel (if it has not already done so).
+
+#### 6.7.1.3 Clearing when tones and announcements are provided
+
+When in-band tones/announcements are provided, the RELEASE message sent by the network shall contain progress indicator No. 8 in-band information or appropriate pattern now available. The network shall initiate clearing by sending the RELEASE message; starting timer T306; and entering the Release Indication state.
+
+On receipt of the RELEASE message with progress indicator No. 8, the user may connect (if not already connected) to the virtual channel to receive the in-band tone/announcement; and enter the Release Indication state. Alternatively, to continue clearing without connecting to the in-band tone/announcement, the user shall release the virtual channel and the call reference; send a RELEASE COMPLETE message; and return to the Null state.
+
+If the user connects to the in-band tone/announcement, the user may subsequently continue clearing (before receipt of a RELEASE COMPLETE message from the network) by: releasing the user virtual channel and the call reference; sending a RELEASE COMPLETE message and returning to the Null state.
+
+On receipt of the RELEASE COMPLETE message, the network shall stop timer T306; release both the user virtual channel and the call reference; and return to the Null state.
+
+If timer T306 expires, the network shall continue clearing by releasing the user virtual channel and the call reference; sending a RELEASE COMPLETE message with the cause number originally contained in the RELEASE message; and returning to the Null state. In addition to the original clearing cause, the RELEASE COMPLETE message may contain a second Cause information element with cause No. 102, "recovery on timer expiry"; this cause may optionally contain a diagnostic field identifying the timer that expired.
+
+### 6.7.2 Fall-back procedure
+
+The B-ISDN does not provide any particular function or procedure to explicitly support the procedures for bearer capability and high layer compatibility selection as defined in 5.10/Q.931 to 5.12/Q.931 [33]. It provides the transparent transfer of the N-BC and N-HLC information elements required for the support of this N-ISDN capability, e.g. in a N-BC CONNECT message.
+
+# 7 List of timers
+
+The description of timers in the following tables is considered a brief summary. The precise details are found in clauses 5 and 6 which contain the definitive description.
+
+## 7.1 Timers in the network side
+
+The timers specified in clause 5 and summarized in Table 7-1 are maintained in the network side of the interface.
+
+The timers specified in clause 6 and summarized in Table 7-2 are maintained in the network side of the interface.
+
+## 7.2 Timers in the user side
+
+The timers specified in clause 5 and summarized in Table 7-3 are maintained in the user side of the interface.
+
+The timers specified in clause 6 and summarized in Table 7-4 are maintained in the user side of the interface.
+
+TABLE 7-1/Q.2931
+
+### **Timers in the network side defined in clause 5**
+
+| Timer | Default value | Call state | Cause for start | Cause for normal stop | Action at the first expiry | Action at the second expiry | Implementation |
+|-------|------------------|--------------------------|---------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|---------------------------------------------------|
+| T301 | Minimum 3 min. | Call received | ALERT received | CONN received | Clear call | Not applicable | Mandatory (Note 1) |
+| T303 | 4 sec. | Call present | SETUP sent | ALERT, CONN, REL COMP or CALL PROC received | Resend SETUP; restart T303 | Clear network connection; enter Null state | Mandatory |
+| T308 | 30 sec. | Release indication | REL sent | REL COMP or REL received | Resend REL; restart T308 | Place bearer virtual channel in maintenance condition. Release call reference and enter Null state (Note 2) | Mandatory |
+| T309 | 10 sec. | Any stable state | SAAL disconnection. Calls in stable states are not lost | SAAL reconnected | Clear network connection; release connection and call reference | Not applicable | Mandatory |
+| T310 | 10 sec. (Note 3) | Incoming call proceeding | CALL PROC received | ALERT, CONN or REL received | Clear call in accordance with 5.4 | Not applicable | Mandatory |
+| T316 | 2 min. | Restart request | RESTART sent | RESTART ACK received | RESTART may be sent several times | RESTART may be sent several times | Mandatory for point-to-point access configuration |
+| T317 | (Note 4) | Restart | RESTART received | Internal clearing of call references | Maintenance notification | Not applicable | Mandatory for point-to-point access configuration |
+| T322 | 4 sec. | Any call state | STAT ENQ sent | STAT, REL or REL COMP received | STAT ENQ may be resent several times | STAT ENQ may be resent several times | Mandatory |
+
+#### **NOTES**
+
+1 The network may already have applied an internal alerting supervision timing function; e.g. incorporated within call control. If such a function is known to be operating on the call, then timer T301 is not used.
+
+2 The restart procedures in 5.5 may be used.
+
+3 The default value of this timer has been aligned with the default value specified in Recommendation Q.931 for the equivalent timer. If these values are different, then Recommendation Q.931 shall take precedence.
+
+4 The value of timer T317 is implementation dependent but a value that is less than the likely values of T316 in peer implementations shall be chosen.
+
+TABLE 7-2/Q.2931
+
+### **Timers in the network side defined in clause 6**
+
+| Timer | Default value | Call state | Cause for start | Cause for normal stop | Action at the first expiry | Action at the second expiry | Implementation |
+|-------|------------------------|--------------------|-----------------------------------------------|--------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------|--------------------------------------------------------------------------|
+| T302 | 10-15 sec.
(Note 1) | Overlap sending | SETUP ACK sent.
Restart when INFO received | With sending complete indication, or network alert or connect request received | Clear if call information determined to be definitely incomplete; else send CALL PROC | Not applicable | Mandatory only if 6.5 is implemented |
+| T303 | 4 sec. | Call present | SETUP sent | ALERT, CONN, CALL PROC, SETUP ACK or REL COMP received | Resend SETUP; restart T303 | Clear network connection; enter Null state | Mandatory |
+| T304 | 20 sec.
(Note 1) | Overlap receiving | SETUP ACK received.
Restart when INFO sent | INFO sent or CALL PROC, ALERT or CONN received | Clear the call | Not applicable | Mandatory only if 6.5 is implemented |
+| T306 | 30 sec.
(Note 2) | Release indication | REL with progress indicator No. 8 sent | REL COMP received | Stop the tone/announcement.
Send REL COMP | Not applicable | Mandatory when in-band tones/announcements are provided.
See clause 6 |
+
+NOTES
+
+1 The default value of this timer has been aligned with the default value specified in Recommendation Q.931 for the equivalent timer. If these values are different, then Recommendation Q.931 shall take precedence.
+
+2 The value of timer T306 may depend on the length of the announcement.
+
+TABLE 7-3/Q.2931
+
+### **Timers in the user side defined in clause 5**
+
+| Timer | Default value | Call state | Cause for start | Cause for normal stop | Action at the first expiry | Action at the second expiry | Implementation |
+|-------|----------------------|--------------------------|---------------------------------------------------------|---------------------------------------------|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|---------------------------------------------------|
+| T301 | Minimum 3 min. | Call delivered | ALERT received | CONN received | Clear call | Not applicable | Mandatory if Annex H is supported |
+| T303 | 4 sec. | Call initiated | SETUP sent | ALERT, CONN, CALL PROC or REL COMP received | SETUP resent; restart T303 | Clear internal connection; enter Null state | Mandatory |
+| T308 | 30 sec. | Release request | REL sent | REL COMP or REL received | REL resent; restart T308 | Place bearer virtual channel in maintenance condition. Release call reference and enter Null state (Note 1) | Mandatory |
+| T309 | 10 sec. | Any stable state | SAAL disconnection. Calls in stable states are not lost | SAAL reconnected | Clear internal connection; release connection and call reference | Not applicable | Mandatory |
+| T310 | 30-120 sec. (Note 2) | Outgoing call proceeding | CALL PROC received | ALERT, CONN or REL received | REL sent | Not applicable | Mandatory |
+| T313 | 4 sec. | Connect request | CONN sent | CONN ACK received | REL sent | Not applicable | Mandatory |
+| T316 | 2 min. | Restart request | RESTART sent | RESTART ACK received | RESTART may be sent several times | RESTART may be sent several times | Mandatory for point-to-point access configuration |
+| T317 | (Note 3) | Restart | RESTART received | Internal clearing of call references | Maintenance notification | Not applicable | Mandatory for point-to-point access configuration |
+| T322 | 4 sec. | Any call state | STAT ENQ sent | STAT, REL or REL COMP received | STAT ENQ may be resent several times | STAT ENQ may be resent several times | Mandatory |
+
+NOTES
+
+- 1 The restart procedures of 5.5 may be used.
+- 2 The default value of this timer has been aligned with the default value specified in Recommendation Q.931 for the equivalent timer. If these values are different, then Recommendation Q.931 shall take precedence.
+- 3 The value of timer T317 is implementation dependent but a value that is less than the likely values of T316 in peer implementations shall be chosen.
+
+TABLE 7-4/Q.2931
+
+### **Timers in the user side defined in clause 6**
+
+| Timer | Default value | Call state | Cause for start | Cause for normal stop | Action at the first expiry | Action at the second expiry | Implementation |
+|-------|----------------------|-------------------|-----------------------------------------------|--------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------------------|-----------------------------------|
+| T302 | 10-15 sec.
(Note) | Overlap receiving | SETUP ACK sent.
Restart when INFO received | With sending complete indication, or network alert or connect request received | Clear if call information determined to be definitely incomplete; else send CALL PROC | Not applicable | Mandatory only if 6.5 implemented |
+| T304 | 30 sec.
(Note) | Overlap sending | SETUP ACK received.
Restart when INFO sent | CALL PROC, ALERT or CONN received | Clear the call | Not applicable | Optional |
+
+NOTE – The default value of this timer has been aligned with the default value specified in Recommendation Q.931 for the equivalent timer. If these values are different, then Recommendation Q.931 shall take precedence.
+
+# 8 Primitives
+
+## 8.1 Introduction
+
+This subclause describes only the interaction between a Q.2931 entity and the SAAL. There are also interactions between Q.2931 and its layer management and between Q.2931 and the user of Q.2931. These interactions are not described here.
+
+A Q.2931 entity requests and accepts services from the SAAL via service primitives. The primitives represent in an abstract way, the logical exchange of information and control between a Q.2931 entity and the SAAL. They do not specify nor constrain implementation; this means that they are only a suggestion of how layers within an equipment should interact; they are not tested for conformance.
+
+In general, the following four types of primitives are used (see also Figure 8-1):
+
+- a) Request;
+- b) Indication;
+- c) Response; and
+- d) Confirm.
+
+The *request* primitive type is used when a higher layer is requesting a service from the next lower layer.
+
+The *indication* primitive type is used by a layer providing a service to notify the next higher layer of any specific activity which is service related. The indication primitive may be the result of an activity of the lower layer related to the primitive type request at the peer entity.
+
+The *response* primitive type is used by a layer to acknowledge receipt, from a lower layer, of the primitive type indication.
+
+The *confirm* primitive type is used by the layer providing the requested service to confirm that the activity has been completed.
+
+
+
+The diagram shows two side-by-side representations of a protocol stack. Each stack has a 'Layer 3' box at the top and a 'Layer 2' box at the bottom. Between them is an oval labeled 'SAP' with a dot inside. On the left stack, a downward arrow from Layer 3 to Layer 2 is labeled 'Request', and an upward arrow from Layer 2 to Layer 3 is labeled 'Confirm'. On the right stack, an upward arrow from Layer 2 to Layer 3 is labeled 'Indication', and a downward arrow from Layer 3 to Layer 2 is labeled 'Response'. Dashed lines connect the Layer 2 boxes of both stacks. The text 'T1162980-94/d044' is at the bottom right.
+
+Diagram illustrating the primitive action sequence between Layer 3 and Layer 2 entities across two systems. On the left, a 'Request' primitive is sent from Layer 3 to Layer 2 via a Service Access Point (SAP). A 'Confirm' primitive is sent from Layer 2 back to Layer 3 via the SAP. On the right, an 'Indication' primitive is sent from Layer 2 to Layer 3 via the SAP. A 'Response' primitive is sent from Layer 3 back to Layer 2 via the SAP. Dashed lines connect the Layer 2 entities of both systems, indicating a peer relationship. The SAP is represented by an oval with a dot, and arrows point to it from the label 'SAP'. The diagram is labeled 'T1162980-94/d044' at the bottom right.
+
+FIGURE 8-1/Q.2931
+Primitive action sequence
+
+## 8.2 Description of the primitives
+
+The primitives exchanged between Q.2931 and the SAAL to support Q.2931 services are shown in Table 8-1.
+
+TABLE 8-1/Q.2931
+
+### **Primitives between Q.2931 and SAAL**
+
+| Generic name | Type | | | | Parameters |
+|---------------|---------------|---------------|-------|---------------|-----------------|
+| | Req. | Ind. | Resp. | Conf. | |
+| AAL-ESTABLISH | (Note 1)
X | (Note 1)
X | | (Note 1)
X | Q.2931 messages |
+| AAL-RELEASE | (Note 1)
X | (Note 1)
X | | (Note 2)
X | Q.2931 messages |
+| AAL-DATA | (Note 3)
X | (Note 3)
X | | | Q.2931 messages |
+| AAL-UNIT_DATA | (Note 4)
X | (Note 4)
X | | | Q.2931 messages |
+
+X Indicates that primitive is implemented.
+
+NOTES
+
+- This primitive may contain a Q.2931 message as a Parameter Data. This parameter shall not be used by a sending entity complying with this Recommendation, but its use by future extensions of this signalling protocol is not excluded. A receiving entity need not process a Q.2931 message received in this primitive; when it chooses to do so, as an implementation option, the processing of the received message is implementation dependent.
+- This primitive does not have a parameter.
+- This primitive has a parameter data containing a Q.2931 message.
+- This primitive has a parameter data containing a Q.2931 message. The use of this primitive to include a Q.2931 call/connection control message is not defined within this Recommendation, however its use by future extensions of this signalling protocol is not precluded. A receiving entity need not process a Q.2931 message received in this primitive; when it chooses to do so, as an implementation option, the processing of the received message is implementation dependent.
+
+### **8.2.1 AAL-ESTABLISH-request**
+
+Issued by a Q.2931 entity to the SAAL to request it to establish an assured Signalling AAL connection between a user and the network. The assured Signalling AAL connection must be established before an AAL-DATA-request can be issued.
+
+### **8.2.2 AAL-ESTABLISH-indication**
+
+Issued by the SAAL to a Q.2931 entity to inform it that it has established an assured Signalling AAL connection between a user and the network. This primitive may be due to an AAL-ESTABLISH-request having been issued by a peer Q.2931 entity or due to a re-establishment with a possible loss of data. If the Q.2931 entity receiving this primitive is not in the NULL state, it should do a status enquiry.
+
+### **8.2.3 AAL-ESTABLISH-confirm**
+
+Issued by the SAAL to a Q.2931 entity to inform it that it has established an assured Signalling AAL connection between a user and the network. The establishment of this Signalling AAL connection had been previously requested by the Q.2931 entity with an AAL-ESTABLISH-request.
+
+### **8.2.4 AAL-RELEASE-request**
+
+Issued by a Q.2931 entity to the SAAL to request it to release an assured Signalling AAL connection. If a previous AAL-ESTABLISH-indication returned an identifier for this Signalling AAL connection, then it must be passed as a parameter with this primitive.
+
+### **8.2.5 AAL-RELEASE-indication**
+
+Issued by the SAAL to a Q.2931 entity to inform it that it has released an assured Signalling AAL connection. If a previous AAL-ESTABLISH-indication returned an identifier for this Signalling AAL connection, then it must be passed as a parameter with this primitive. This primitive may be due to an AAL-RELEASE-request having been issued by a peer Q.2931 entity or due to an error.
+
+### **8.2.6 AAL-RELEASE-confirm**
+
+Issued by the SAAL to a Q.2931 entity to inform it that it has released an assured Signalling AAL connection between a user and the network. The release of this Signalling AAL connection had been previously requested by the Q.2931 entity with an AAL-RELEASE-request.
+
+### **8.2.7 AAL-DATA-request**
+
+Issued by a Q.2931 entity to the SAAL to request it to send a message across an established assured Signalling AAL connection.
+
+### **8.2.8 AAL-DATA-indication**
+
+Issued by the SAAL to a Q.2931 entity to deliver it a message that was sent by a peer Q.2931 entity using an AAL-DATA-request primitive.
+
+### **8.2.9 AAL-UNIT\_DATA-request**
+
+Issued by a Q.2931 entity to the SAAL to request it to send a message to one or more peer Q.2931 entities. It is sent using unacknowledged, unassured data transfer.
+
+### **8.2.10 AAL-UNIT\_DATA-indication**
+
+Issued by the SAAL to a Q.2931 entity to deliver it a message that was sent by a peer Q.2931 entity using an AAL-UNIT\_DATA-request primitive.
+
+# Annex A
+
+## Network side and user side SDL diagrams
+
+(This annex forms an integral part of this Recommendation)
+
+This annex provides System Diagrams and SDL process description for User and Network side entities implementing the processes using the procedures defined in clauses 5 and 6. Figure A.1 gives a list of the symbols used in the SDL processes definition.
+
+## A.1 Network side SDL diagrams
+
+The Network Side SDL diagrams are structured as follows:
+
+| Reference | Length (Network Side) |
+|----------------------------------------------------------------------|-----------------------|
+| System diagram ..... | 1 page |
+| Block diagram ..... | 1 page |
+| Co-ord-N process ..... | 10 pages |
+| Reset-Start-N process ..... | 2 pages |
+| Reset-Response-N process ..... | 2 pages |
+| Q.2931-N process:..... | 31 pages, comprises: |
+| Procedures for B-ISDN calls
(See clause 5) ..... | pp. 1-18 |
+| Extensions for symmetric call operation
(See Annex H) ..... | p. 19 |
+| Additional procedures related to interworking
(See clause 6)..... | pp. 20-31 |
+
+### SYSTEM Q.2931 – Network Side
+
+
+
+Q.2931 SDL
+
+SYSTEM DIAGRAM – NETWORK SIDE
+
+A rectangular box with a dog-eared top-right corner. Inside, the text 'Q.2931 SDL' is at the top left, and 'SYSTEM DIAGRAM – NETWORK SIDE' is centered.
+
+![A block diagram showing a central process block labeled 'Q.2931-N'. It has four signal lines connected to it. From the top, an arrow labeled '[SigList-1] FromApplication' points into the block. An arrow labeled '[SigList-2] ToApplication' points out from the top of the block to the left. From the bottom, an arrow labeled '[SigList-3] FromSAAL' points into the block. An arrow labeled '[SigList-4] ToSAAL' points out from the bottom of the block to the left.](5661815043254c37a4e3e4833f51e727_img.jpg)
+
+```
+
+ graph TD
+ FromApp("[SigList-1] FromApplication") --> QN[Q.2931-N]
+ QN --> ToApp("[SigList-2] ToApplication")
+ FromSAAL("[SigList-3] FromSAAL") --> QN
+ QN --> ToSAAL("[SigList-4] ToSAAL")
+
+```
+
+A block diagram showing a central process block labeled 'Q.2931-N'. It has four signal lines connected to it. From the top, an arrow labeled '[SigList-1] FromApplication' points into the block. An arrow labeled '[SigList-2] ToApplication' points out from the top of the block to the left. From the bottom, an arrow labeled '[SigList-3] FromSAAL' points into the block. An arrow labeled '[SigList-4] ToSAAL' points out from the bottom of the block to the left.
+
+
+
+SigList-1: From-AP
+
+SigList-2: To-AP
+
+SigList-3: From-SAAL
+
+SigList-4: To-SAAL
+
+/\*The signal lists are expanded
+in the Co-ord N process
+diagram\*/
+
+A rectangular box with a dog-eared top-right corner containing signal list definitions and a comment.
+
+T1162990-94/d045
+
+
+
+SDL key
+=====
+
+| | | | |
+|--|--------------------------------------------------------------|--|-----------------------------------------------------------------|
+| | Start | | Process termination |
+| | Implementation specific process | | Task |
+| | Create | | Decision |
+| | Signal (either within layer or through SAP) or PDU received | | Implementation option |
+| | Signal (either within layer or through SAP) or PDU generated | | Save a signal (until completion of a transition to a new state) |
+| | State | | Text symbol |
+| | Any state | | Comment |
+| | Return to same state | | Note |
+
+Start symbol: a horizontal oval Process termination symbol: a circle with an X and a dot Implementation specific process symbol: a rectangle with double vertical lines on the left and right sides Task symbol: a simple rectangle Create symbol: a rectangle with double horizontal lines at the top and bottom Decision symbol: a diamond shape Signal received symbol: a chevron shape pointing right Implementation option symbol: a triangle pointing up Signal generated symbol: a chevron shape pointing left Save a signal symbol: a parallelogram State symbol: a horizontal oval with vertical lines at the ends Text symbol: a rectangle with a folded top-right corner Any state symbol: a horizontal oval with a star (\*) inside Comment symbol: a dashed line with a bracket Return to same state symbol: a horizontal oval with a dash (-) inside Note symbol: a rectangle with a folded bottom-left corner
+
+T1165770-94/d046
+
+FIGURE A.1/Q.2931
+Key to symbols used in SDL representation of procedures
+
+#### BLOCK Q.2931 Network Side
+
+
+
+The diagram illustrates the network side of a Q.2931 block. At the center is a block labeled **Co-ord-N (1, 1)**. To its left, the **Call Control** and **Adaptation Layer** are shown. The **Call Control** has a **From-AP** input and a **To-AP** output. The **Adaptation Layer** has a **From-SAAL** input and a **To-SAAL** output. Both are connected to the central **Co-ord-N (1, 1)** block. To the right of the central block are three other blocks: **Q.2931-N (O, N)**, **Reset-Start-N (1, 1)**, and **Reset-Response-N (1, 1)**. The **Q.2931-N (O, N)** block has a **CDtoQN** input and a **QNtoCD** output from the central block. A dotted line also connects the central block to the **Q.2931-N (O, N)** block. The **Reset-Start-N (1, 1)** block has a **CDtoRS** input and an **RStoCD** output from the central block. The **Reset-Response-N (1, 1)** block has a **CDtoRR** input and an **RRtoCD** output from the central block.
+
+Diagram of BLOCK Q.2931 Network Side showing a central Co-ord-N (1, 1) block connected to Call Control, Adaptation Layer, Q.2931-N (O, N), Reset-Start-N (1, 1), and Reset-Response-N (1, 1) blocks with various data flow arrows.
+
+Reset processes always present to allow return to REST 0 state –
+
+T1163000-94/d047
+
+
+
+A diagram consisting of a large rectangular box with a dog-eared top-right corner containing the text "Q.2931 SDL - Network Side". Below it, a smaller rectangle is centered, partially overlapping the bottom edge of the larger box, creating a shadow-like effect.
+
+SDL Process symbol for Q.2931 SDL - Network Side
+
+##### Acronyms
+
+#### Processes
+
+| | | |
+|-----------------|---|------------------------------------------------------------------------------------------------------------|
+| Co-ord-N | = | Coordination function for all Q.2931 processes (ASEs) and performs "common" functions on the network side. |
+| Q.2931-N | = | Process that performs the Call/Bearer specific signalling functions. |
+| Reset-Start-N | = | Process that starts the RESTART procedure on the network side. |
+| Reset-Respond-N | = | Process that responds to a RESTART message on the network side. |
+
+##### Other Entities
+
+| | | |
+|------|---|---------------------------------------|
+| AP | = | Signalling Application Process |
+| SAAL | = | Signalling ATM Adaption Layer Process |
+
+##### Others
+
+| | | |
+|-------|---|--------------------------------------------------------------------------------------------------|
+| § x.x | = | Reference to relevant Section x.x of Q.2931 |
+| Cause | = | Cause field contents in Cause IE |
+| CS | = | Call State value in Call State IE |
+| # | = | Indicates all IEs in a primitive or message except those explicitly identified (e.g. (Cause, #)) |
+| CD | = | Coordination Process |
+| CLR | = | Release Call |
+| I | = | Ignore |
+| IE | = | Information Element |
+| OK | = | Okay (proceed) |
+| QN | = | Q.2931-N |
+| RAI | = | Report And Ignore |
+| RAP | = | Report And Proceed |
+| RR | = | Reset-Respond-N |
+| RS | = | Reset-Start-N |
+| SC | = | Sending Complete |
+
+The List of IEs possible for each message and the contents of the IEs are defined in clauses 3 and 4
+
+T1163010-94/d048
+
+##### Signal lists
+
+##### Signal for B-ISDN Calls
+
+##### Primitives to/from SAAL
+
+##### From-SAAL
+
+AAL-DATA-ind. – Includes Message from point-to-point signalling virtual channel connection
+
+AAL-ESTABLISH-ind., AAL-ESTABLISH-conf.
+AAL-RELEASE-ind., AAL-RELEASE-conf.
+
+##### To-SAAL
+
+AAL-DATA-req. – Message sent to specific point-to-point signalling virtual channel connection
+
+AAL-ESTABLISH-req. – SAAL link establishment
+AAL-RELEASE-req. – SAAL link reset or release
+
+##### Primitives to/from Application Process
+
+##### From AP
+
+Setup-req.
+Proceeding-req.
+Alerting-req.
+Setup-resp.
+Setup-complete-req.
+Release-req.
+Release-resp.
+Reset-req.
+Reset-resp.
+Reset-error-response
+Notify-req.
+Link Establish-req.
+Link Release-req.
+
+##### To AP
+
+Setup-ind.
+Proceeding-ind.
+Alerting-ind.
+Setup-conf.
+
+Release-ind.
+Release-conf.
+Reset-ind.
+Reset-conf.
+Reset-error-ind.
+Notify-ind.
+Link Establish-conf.
+Link Release-conf.
+
+#### Signal lists
+
+##### Additional signals related to interworking
+
+##### Primitives to/from Application Process
+
+##### From AP
+
+More-info-req.
+Info-req.
+Progress-req.
+
+##### To AP
+
+More-info-ind.
+Info-ind.
+Progress-ind.
+
+#### Signal lists
+
+##### Additional signals related to interworking
+
+##### Primitives to/from Application Process
+
+##### From AP
+
+##### To AP
+
+*These primitives are listed in the relevant broadband supplementary service Recommendations (Q.295x. – Series)*
+
+T1163020-94/d049
+
+##### Primitives to/from Q.2931-N
+
+##### Signal lists
+
+| CDtoQN | QNtoCD |
+|---------------------------|------------------------|
+| Setup-req. | Setup-ind. |
+| Proceeding-req. | Proceeding-ind. |
+| Alerting-req. | Alerting-ind. |
+| Setup-resp. | Setup-conf. |
+| Setup-complete-req. | |
+| Release-req. | Release-ind. |
+| Release-resp. | Release-conf. |
+| | Status-ind. |
+| Notifiy-req. | Notify-ind. |
+| Link Establish confirm | Link Establish request |
+| Link Establish indication | |
+| Link Release indication | |
+| Link Establish error | |
+
+##### Primitives to/from Reset-Start-N
+
+##### Signal lists
+
+| CDtoRS | CDtoRS |
+|---------------|------------------|
+| Reset-req. | Reset-error-ind. |
+| | Reset-conf. |
+
+##### Primitives to/from Reset-Respond-N
+
+##### Signal lists
+
+| CDtoRR | RRtoCD |
+|-------------------|------------------|
+| Reset-resp. | Reset-ind. |
+| Reset-error-resp. | Reset-error-ind. |
+
+##### Additional Primitives to/from Q.2931-N related to interworking
+
+##### Signal lists
+
+| CDtoQN | QNtoCD |
+|----------------|----------------|
+| More-info-req. | More-info-ind. |
+| Infor-req. | Info-ind. |
+| Progress-req. | Progress-ind. |
+
+##### Additional Primitives to/from Q.2931-N related to supplementary services
+
+##### Signal lists
+
+| CDtoQN | QNtoCD |
+|-------------------------------------------------------------------------------------------------------------------------------|---------------|
+| These primitives are listed in the relevant
broadband supplementary service
Recommendations (Q.295x. – Series) | |
+
+##### Messages to/from Q.2931-N for B-ISDN calls
+
+##### Signal lists
+
+| CDtoQN | QNtoCD |
+|------------------|------------------|
+| SETUP | SETUP |
+| CALL-PROCEEDING | CALL-PROCEEDING |
+| ALERTING | ALERTING |
+| CONNECT | CONNECT |
+| CONNECT-ACK | CONNECT-ACK |
+| RELEASE | RELEASE |
+| RELEASE-COMPLETE | RELEASE-COMPLETE |
+| STATUS | STATUS |
+| STATUS-ENQUIRY | STATUS-ENQUIRY |
+| NOTIFY | NOTIFY |
+
+##### Messages to/from Reset-Start-N
+
+##### Signal lists
+
+| CDtoRS | RStoCD |
+|---------------|---------------|
+| RESTART-ACK | RESTART |
+| | STATUS |
+
+##### Messages to/from Reset-Respond-N
+
+##### Signal lists
+
+| CDtoRR | RRtoCD |
+|---------------|---------------|
+| RESTART | RESTART-ACK |
+| | STATUS |
+
+##### Additional Messages to/from Q.2931-N related to interworking
+
+##### Signal lists
+
+| CDtoQN | QNtoCD |
+|-------------------|-------------------|
+| SETUP-ACKNOWLEDGE | SETUP-ACKNOWLEDGE |
+| INFORMATION | INFORMATION |
+| PROGRESS | PROGRESS |
+
+##### Additional Messages to/from Q.2931-N related to Supplementary Services
+
+##### Signal lists
+
+| CDtoQN | QNtoCD |
+|-------------------------------------------------------------------------------------------------------------------------------|---------------|
+| These primitives are listed in the relevant
broadband supplementary service
Recommendations (Q.295x. – Series) | |
+
+T1163030-94/d050
+
+
+
+The diagram illustrates the state transitions for the Co-ord-N process. It begins with a state 'CNO - AAL Connection Released' (oval). Transitions from this state include:
+
+
+- 'Check-Msg (#)' and 'Build-Msg (#)' leading to 'Implementation specific procedure declarations' (dashed box).
+- 'Link Establish request' (from AP or Q.2931-U) leading to 'AAL-ESTABLISH request' (To SAAL).
+- 'Timeout T309' leading to 'Link Establish error' (To Q.2931-N (all)) and 'CNO - AAL Connection Released'.
+- An unlabeled transition leading to an exit node 'X'.
+
+ From 'Implementation specific procedure declarations', transitions lead to:
+
+
+- 'Setup-req. (\*From AP\*/)' leading to 'Q.2931-N' and then 'Setup-req. (\*To Q.2931N\*/)'.
+- 'Reset-req. (\*From AP\*/)' leading to 'Reset-req. (#) (\*To Reset-Start-N\*/)'.
+
+ Both 'Setup-req. (\*To Q.2931N\*/)' and 'Reset-req. (#) (\*To Reset-Start-N\*/)' lead to the 'Link Establish request' state.
+ From 'AAL-ESTABLISH request', the transition leads to 'ACTIVE T309' (decision diamond):
+
+
+- If 'Yes', it leads to 'CN1 - AAL Awaiting Establish' (oval).
+- If 'No', it leads to 'SET(Now + t309, timer T309)' (rectangle), which then leads to 'CN1 - AAL Awaiting Establish'.
+
+ From 'CN1 - AAL Awaiting Establish', transitions include:
+
+
+- 'Message (#) (\*From Q.2931-N, Reset-Start-N or Reset-Respond-N\*)' leading to 'Link Establish error' (To Q.2931-U (all)) and 'CNO - AAL Connection Released'.
+- 'Timeout T309' leading to 'Link Establish error' (To Q.2931-U (all)) and 'CNO - AAL Connection Released'.
+- 'AAL-ESTABLISH Confirm' leading to 'RESET T309' (rectangle), 'Link Establish confirm' (To Q.2931-N(all) and AP)), and 'CN3 - AAL Connection Established' (oval).
+- 'AAL-RELEASE indication' (From SAAL) leading to 'Link-Release indication' (To Q.2931-N (all)) and 'CNO - AAL Connection Released'.
+
+ There is also a separate path starting with an exit node 'X' leading to 'AAL Establish indication' (parallelogram), which leads to 'Link Establish indication' (parallelogram), which leads to 'CN3 - AAL Connection Established' (oval).
+
+State transition diagram for PROCESS Co-ord-N. The diagram shows various states (ovals), transitions (arrows), and input/output actions (parallelograms). States include 'CNO - AAL Connection Released', 'CN3 - AAL Connection Established', and 'CN1 - AAL Awaiting Establish'. Transitions are triggered by messages like 'Check-Msg (#)', 'Build-Msg (#)', 'Setup-req. (\*From AP\*/)', 'Reset-req. (\*From AP\*/)', 'Link Establish request', 'Timeout T309', 'AAL-ESTABLISH request', 'Message (#) (\*From Q.2931-N, Reset-Start-N or Reset-Respond-N\*)', 'AAL-ESTABLISH Confirm', and 'AAL-RELEASE indication'. Some transitions lead to external entities like 'Q.2931-N', 'Q.2931-U', 'SAAL', or 'X' (exit).
+
+T1163040-94/d051
+
+
+
+The diagram shows the state transitions for process Co-ord-N, focusing on AAL connection establishment and release.
+
+- Initial State:** CN3 – AAL Connection Established
+- Path 1 (Release initiated by AP):**
+ - Input from AP: Link Release request
+ - Output to SAAL: AAL-RELEASE request
+ - Next State: CN2 – AAL Awaiting Release
+ - Input: AAL-RELEASE confirm
+ - Output: Link Release confirm
+ - Final State: CN0 – AAL Connection Released
+- Path 2 (Release indication from SAAL):**
+ - Input from SAAL: AAL-RELEASE indication
+ - Output: Link Release indication
+ - Final State: CN0 – AAL Connection Released
+- Path 3 (Establishment indication from SAAL):**
+ - Input from SAAL: AAL-ESTABLISH indication
+ - Output: Link Establish indication
+ - Final State: CN3 – AAL Connection Established
+- Path 4 (Establishment confirm from SAAL):**
+ - Input from SAAL: AAL-ESTABLISH confirm
+ - Output to Q.2931-N (all): Link Establish confirm
+ - Final State: CN3 – AAL Connection Established
+- Path 5 (Establishment request from AP):**
+ - Input from AP: Link Establish request
+ - Output to AP: Link Establish confirm
+ - Final State: CN3 – AAL Connection Established
+
+T1175590-95/d052
+
+SDL state transition diagram for AAL connection coordination.
+
+
+
+```
+
+graph TD
+ Start([CN3 - AAL Connection Established
+See 5.1, 5.2, 5.1.1, 5.2.1]) --> P1[/"Primitive" /From AP*/]
+ Start --> P2[/AAL-DATA-ind. (#) /From SAAL*/]
+ Start --> P3[/"Primitive" /From Q.2931-N, Reset-Start-N or Reset-Respond-N*/]
+ Start --> P4[/Message (#) /From Q.2931-N, Reset-Start-N or Reset-Respond-N*/]
+
+ P1 --> W((W))
+ W --> AP[To application primitive handling procedures]
+
+ P2 --> CM[Check-Msg (#)]
+ CM --> S1[See 5.6.1, 5.6.2, 5.6.3]
+ CM --> Q2931{Q.2931 Protocol Discriminator}
+
+ Q2931 -- No --> CN3_Established_1([CN3 - AAL Connection Established])
+ Q2931 -- Yes --> ML{Message Length < 9 octets}
+
+ ML -- Yes --> CN3_Established_1
+ ML -- No --> VCRF{Valid Call Reference format}
+
+ VCRF -- No --> CN3_Established_1
+ VCRF -- Yes --> CRD{Call Reference = Dummy}
+
+ CRD -- Yes --> CN3_Established_1
+ CRD -- No --> CRG{Call Reference = Global}
+
+ CRG -- Yes --> X((X))
+ X --> GCRP[To Global Call Reference Procedures]
+
+ CRG -- No --> CR{Call Reference recognized}
+ CR -- No --> Z((Z))
+ Z --> NP[To "No Protocol" Procedures]
+
+ CR -- Yes --> Y((Y))
+ Y --> PRP[To Protocol Related Procedures]
+
+ P3 --> P3_TO[/"Primitive" /To AP*/]
+ P3_TO --> CN3_Established_2([CN3 - AAL Connection Established])
+
+ P4 --> BM[Build-Msg (#)]
+ BM --> ADREQ[/"AAL-DATA.req. (#) /To SAAL*/]
+ ADREQ --> CN3_Established_3([CN3 - AAL Connection Established])
+
+ Note1[Does not include check of Call Reference flag] -.-> CR
+
+```
+
+Flowchart for PROCESS Co-ord-N. It starts with 'CN3 - AAL Connection Established' (See 5.1, 5.2, 5.1.1, 5.2.1). It branches into four paths: 1) 'Primitive' from AP to application primitive handling procedures. 2) AAL-DATA-ind. from SAAL to Check-Msg (#) (See 5.6.1, 5.6.2, 5.6.3) to Q.2931 Protocol Discriminator. 3) Primitive from Q.2931-N (Reset-Start-N or Reset-Respond-N) to Primitive to AP to CN3 - AAL Connection Established. 4) Message from Q.2931-N (Reset-Start-N or Reset-Respond-N) to Build-Msg (#) to AAL-DATA.req. to SAAL to CN3 - AAL Connection Established. The Q.2931 Protocol Discriminator path continues with checks for Message Length < 9 octets, Valid Call Reference format, Call Reference = Dummy, Call Reference = Global, and Call Reference recognized, leading to CN3 - AAL Connection Established, Global Call Reference Procedures (X), 'No Protocol' Procedures (Z), or Protocol Related Procedures (Y).
+
+T1165790-94/d053
+
+
+
+```
+
+graph TD
+ Start((X)) --> GCRP[Global Call Reference
+Procedures]
+ GCRP --> MT{Message Type}
+ MT --> MT_Ref[See 5.5, 5.6.3.2 e),
+5.6.12]
+
+ MT --> RESTART[RESTART (#)]
+ MT --> OTHER[OTHER (#)]
+ MT --> RESTART_ACK[RESTART-ACKNOWLEDGE (#)]
+ MT --> STATUS[STATUS (#)]
+
+ RESTART --> CRF1{CRF}
+ CRF1 -- 1 --> Join(( ))
+ CRF1 -- 0 --> RESTART_RESP[RESTART (#)
+/* To Reset-
+Respond-N*/]
+ RESTART_RESP --> CN3_1([CN3 - AAL
+Connection
+Established])
+
+ OTHER --> OTHER_ACTION[Cause := 81; CS: = 0]
+ OTHER_ACTION --> BUILD_MSG[Build-Msg(STATUS,
+Cause, CS, #)]
+ BUILD_MSG --> AAL_REQ[/AAL-DATA-req. (#)
+/*To SAAL*/]
+ AAL_REQ --> CN3_2([CN3 - AAL
+Connection
+Established])
+
+ RESTART_ACK --> CRF2{CRF}
+ CRF2 -- 0 --> Join
+ CRF2 -- 1 --> RESTART_ACK_RESP[RESTART
+ACKNOWLEDGE (#)
+/*To Reset-Start-N*/]
+ RESTART_ACK_RESP --> CN3_3([CN3 - AAL
+Connection
+Established])
+
+ STATUS --> CRF3{CRF}
+ CRF3 -- 0 --> STATUS_RESP1[/STATUS (#)
+/* To Reset-
+Respond-N*//]
+ CRF3 -- 1 --> STATUS_RESP2[/STATUS (#) /* To
+Reset-Start-N*//]
+ STATUS_RESP1 --> CN3_4([CN3 - AAL
+Connection
+Established])
+ STATUS_RESP2 --> CN3_4
+
+ Join --> OTHER_ACTION
+
+```
+
+T1165800-94/d054
+
+Flowchart for PROCESS Co-ord-N starting with Global Call Reference Procedures, leading to Message Type decision, then branches for RESTART, OTHER, RESTART-ACKNOWLEDGE, and STATUS messages with associated CRF flag checks and subsequent actions like CN3 - AAL Connection Established or AAL-DATA.req.
+
+CRF = Call Reference Flag
+
+
+
+```
+graph TD; Z((Z)) --> MT{Message Type}; Z -.-> NP["\"No Protocol\" Procedures"]; MT -.-> Ref["See 5.6.3.2 a), b), c), f), g), 5.6.11"]; MT --> SETUP[SETUP (#)]; MT --> RELEASE[RELEASE-COMPLETE (#)]; MT --> OTHER[OTHER (#)]; MT --> STATUS[STATUS (#)]; MT --> STATUS_ENQ[STATUS-ENQUIRY (#)]; SETUP --> CRF{Call Reference flag = 0}; CRF -- No --> RELEASE; CRF -- Yes --> Q2931N[Q.2931-N]; Q2931N --> SETUP_REQ[SETUP (#) /*To Q.2931-N*/]; SETUP_REQ --> CN3_EST1([CN3 – AAL Connection Established]); RELEASE --> CN3_EST2([CN3 – AAL Connection Established]); OTHER --> C81[Cause := 81]; C81 --> BUILD_MSG[Build-Msg (RELEASE-COMPLETE, Cause, #)]; BUILD_MSG --> DATA_REQ[AAL-DATA-req. (#) /*To SAAL*/]; DATA_REQ --> CN3_EST3([CN3 – AAL Connection Established]); STATUS --> CS0{CS=0}; CS0 -- Yes --> C30[Cause := 30; CS := 0]; CS0 -- No --> C101[Cause := 101]; C30 --> BUILD_STATUS[Build-Msg(STATUS, CS, Cause, #)]; C101 --> BUILD_STATUS; BUILD_STATUS --> DATA_REQ2[AAL-DATA-req. (#) /*To SAAL*/]; DATA_REQ2 --> CN3_EST4([CN3 – AAL Connection Established]); STATUS_ENQ --> C30; BUILD_STATUS --> CN3_EST4; T1165810-94/d055
+```
+
+Flowchart for PROCESS Co-ord-N starting with connector Z, leading to Message Type decision, then branching into SETUP, RELEASE-COMPLETE, OTHER, STATUS, and STATUS-ENQUIRY paths with various processing steps and connectors.
+
+
+
+```
+
+graph TD
+ Y((Y)) -- "Protocol Procedures" --> MT{Message Type}
+ MT -- "SETUP (#)" --> S[SETUP with active call reference is ignored]
+ S --> CN3((CN3 - AAL Connection Established))
+ MT -- "OTHER" --> M{{Message (#)
+/*To Q.2931-N*/}}
+ M --> CN3
+ T1165820-94/d056
+
+```
+
+Flowchart for PROCESS Co-ord-N; page 9 of (10). It starts with connector 'Y' (Protocol Procedures) leading to 'Message Type' decision. 'SETUP (#)' leads to 'SETUP with active call reference is ignored' and then to 'CN3 - AAL Connection Established'. 'OTHER' leads to 'Message (#) /\*To Q.2931-N\*/' and then to 'CN3 - AAL Connection Established'. Reference T1165820-94/d056.
+
+
+
+```
+
+graph TD
+ W((W)) -- "Application primitive handling procedures" --> PT{Primitive Type}
+ PT -- "See 5.5.1, 5.1.1" --> PT
+ PT -- "All other primitives" --> P{{"Primitive" /*To Q.2931-N*/}}
+ P --> CN3_1((CN3 - AAL Connection Established))
+ PT -- "Setup-req." --> SR[Q.2931-N]
+ SR --> SQ{{Setup-req. /*To Q.2931-N*/}}
+ SQ --> CN3_2((CN3 - AAL Connection Established))
+ PT -- "Reset-req." --> RR{{Reset-req. (#)
+/*To Reset-Start-N*/}}
+ RR --> CN3_3((CN3 - AAL Connection Established))
+ PT -- "Reset-error.resp." --> RE{{Reset-req. (#)
+/*To Reset-req. N*/}}
+ RE --> CN3_3
+ T1165830-94/d057
+
+```
+
+Flowchart for PROCESS Co-ord-N; page 10 of (10). It starts with connector 'W' (Application primitive handling procedures) leading to 'Primitive Type' decision (See 5.5.1, 5.1.1). 'All other primitives' leads to '"Primitive" /\*To Q.2931-N\*/' and then to 'CN3 - AAL Connection Established'. 'Setup-req.' leads to 'Q.2931-N' and then to 'Setup-req. /\*To Q.2931-N\*/' and then to 'CN3 - AAL Connection Established'. 'Reset-req.' leads to 'Reset-req. (#) /\*To Reset-Start-N\*/' and then to 'CN3 - AAL Connection Established'. 'Reset-error.resp.' leads to 'Reset-req. (#) /\*To Reset-req. N\*/' and then to 'CN3 - AAL Connection Established'. Reference T1165830-94/d057.
+
+
+
+```
+graph TD; Entry([See 5.5.1]) --> RestN0Null1([Rest-N0 - Null]); RestN0Null1 --> ResetReq[/Reset.req.
+(Restart indicator,
+Connection identifier)/]; ResetReq -.-> Note1[Connection identifier=null is valid]; ResetReq --> ConnectIDs["ConnectIDs :=
+Connection identifier,
+Timeouts := 0"]; ConnectIDs --> RESTART[/RESTART
+(Restart Indicator,
+Connection identifier)/]; RESTART --> SET["SET(Now + t316,
+timer T316)"]; SET --> RestN1Request1([Rest-N1 - Restart Request]); RestN1Request1 --> TimeoutT316[/Timeout T316/]; TimeoutT316 --> TimeoutsInc["Timeouts :=
+Timeouts + 1"]; TimeoutsInc --> TimeoutsRSN{Timeouts=RSN}; Note2[RSN = Number of
+RESTART's sent.
+Implementation
+dependent value;
+Default=2] -.-> TimeoutsRSN; TimeoutsRSN -- No --> RESTART; TimeoutsRSN -- Yes --> Reason["Reason :=
+NoResponse"]; Reason --> ResetErrorInd[/Reset-error-ind.
+(Reason)/]; Note3[VC/VP in Connection identifier
+should be placed in an out-of-
+service maintenance condition] -.-> ResetErrorInd; ResetErrorInd --> RestN0Null2([Rest-N0 - Null]); VerifyMsg[Verify-Msg] -.-> Note4[See 5.6, 5.7, 5.8];
+```
+
+Flowchart for PROCESS Reset-Start-N. It starts with an entry point (See 5.5.1) leading to 'Rest-N0 - Null'. From there, it goes to 'Reset.req. (Restart indicator, Connection identifier)' with a note 'Connection identifier=null is valid'. Then 'ConnectIDs := Connection identifier, Timeouts := 0'. Next is 'RESTART (Restart Indicator, Connection identifier)' followed by 'SET(Now + t316, timer T316)' and 'Rest-N1 - Restart Request'. A 'Verify-Msg' (See 5.6, 5.7, 5.8) is shown separately. The 'Rest-N1 - Restart Request' leads to 'Timeout T316', then 'Timeouts := Timeouts + 1'. A decision 'Timeouts=RSN' follows, with a note 'RSN = Number of RESTART's sent. Implementation dependent value; Default=2'. If 'No', it loops back to 'RESTART'. If 'Yes', it goes to 'Reason := NoResponse', then 'Reset-error-ind. (Reason)' with a note 'VC/VP in Connection identifier should be placed in an out-of-service maintenance condition', and finally 'Rest-N0 - Null'.
+
+T1165840-94/d058
+
+
+
+```
+
+graph TD
+ Start([Rest-N1 - Restart Request]) -.-> Note1[See 5.6.12, 5.5.1]
+ Start --> STATUS_1[/STATUS
+(Cause, CS)/]
+ Start --> RESTART_1[/RESTART-
+ACKNOWLEDGE
+(Restart indication,
+Connection
+identifier)/]
+ STATUS_1 --> VerifyMsg_1[[Verify-Msg]]
+ RESTART_1 --> VerifyMsg_2[[Verify-Msg]]
+ VerifyMsg_1 --> Result_1{Result}
+ VerifyMsg_2 --> Result_2{Result}
+ Result_1 -- RAP --> STATUS_Cause_1[/STATUS
+Cause, CS/]
+ Result_1 -- OK --> RestN0_1([Rest-N0])
+ Result_1 -- CLR --> RestN0_2([Rest-N0])
+ Result_1 -- RAI --> STATUS_Cause_2[/STATUS
+Cause, CS/]
+ STATUS_Cause_1 --> CSCompatible{CS Compatible}
+ STATUS_Cause_2 --> CSCompatible
+ CSCompatible -- No --> Reason[Reason := Peer-
+IncompatibleState]
+ Reason --> ResetError[/Reset-error-ind.
+(Reason)/]
+ ResetError --> RestN1_1([Rest-N1 - Restart
+Request])
+ CSCompatible -- Yes --> ImplProc[[Implementation
+dependent
+procedure]]
+ ImplProc --> RESTART_ACK[RESTART
+ACKNOWLEDGE with
+mis-matched connection
+identification ignored -]
+ RESTART_ACK --> RestN1_2([Rest-N1 - Restart
+Request])
+ Result_2 -- RAP --> STATUS_Cause_3[/STATUS
+Cause, CS/]
+ Result_2 -- OK --> RestN0_3([Rest-N0 - Null])
+ Result_2 -- CLR --> RestN0_4([Rest-N0 - Null])
+ Result_2 -- RAI --> STATUS_Cause_3_2[/STATUS
+(Cause, CS
+= Reset-N1)/]
+ STATUS_Cause_3_2 --> RestN1_3([Rest-N1 - Restart
+Request])
+ STATUS_Cause_3 --> ConnectIDs{Connection
+identifier =
+ConnectIDs}
+ ConnectIDs -- No --> RestN1_4([Rest-N1 - Restart
+Request])
+ ConnectIDs -- Yes --> RESET_T316[RESET T316]
+ RESET_T316 --> ResetConf[/Reset conf.
+(Restart indicator,
+Connection
+identifier)/]
+ ResetConf --> RestN0_5([Rest-N0 - Null])
+ Note2[Connection
+identifier = null is valid] -.-> ConnectIDs
+ T1165850_94_d059[T1165850-94/d059]
+
+```
+
+Flowchart for PROCESS Reset-Start-N. It starts with 'Rest-N1 - Restart Request' (See 5.6.12, 5.5.1). It branches into two main paths: 'STATUS (Cause, CS)' and 'RESTART-ACKNOWLEDGE (Restart indication, Connection identifier)'. Both paths lead to 'Verify-Msg' and then to a 'Result' decision. The 'STATUS' path has four outcomes: RAP, OK, CLR, and RAI. RAP leads to 'STATUS Cause, CS' which then leads to 'CS Compatible'. OK leads to 'Rest-N0'. CLR leads to 'Rest-N0'. RAI leads to 'STATUS Cause, CS' which then leads to 'CS Compatible'. 'CS Compatible' has two outcomes: No and Yes. No leads to 'Reason := Peer-IncompatibleState', then 'Reset-error-ind. (Reason)', then 'Rest-N1 - Restart Request'. Yes leads to 'Implementation dependent procedure', then 'RESTART ACKNOWLEDGE with mis-matched connection identification ignored -', then 'Rest-N1 - Restart Request'. The 'RESTART-ACKNOWLEDGE' path has four outcomes: RAP, OK, CLR, and RAI. RAP leads to 'STATUS Cause, CS' which then leads to 'Connection identifier = ConnectIDs'. OK leads to 'Rest-N0 - Null'. CLR leads to 'Rest-N0 - Null'. RAI leads to 'STATUS (Cause, CS = Reset-N1)', then 'Rest-N1 - Restart Request'. 'Connection identifier = ConnectIDs' has two outcomes: No and Yes. No leads to 'Rest-N1 - Restart Request'. Yes leads to 'RESET T316', then 'Reset conf. (Restart indicator, Connection identifier)', then 'Rest-N0 - Null'. A note indicates 'Connection identifier = null is valid'. A reference 'T1165850-94/d059' is at the bottom right.
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> Rest-N0 : See 5.5.2
+ Rest-N0 --> RESTART_N0 : RESTART (Restart indication, Connection identifier)
+ RESTART_N0 --> Verify-Msg_N0 : Connection identifier = null is valid
+ Verify-Msg_N0 --> Result_N0 : Result
+ Result_N0 --> STATUS_N2 : RAP
+ Result_N0 --> OK_N0 : OK
+ Result_N0 --> STATUS_N0 : CLR
+ Result_N0 --> STATUS_N0 : RAI
+ STATUS_N2 --> Reset-ind_N2 : STATUS (Cause, CS = Rest-N2)
+ STATUS_N0 --> Rest-N0 : STATUS (Cause, CS = Rest-N0)
+ Reset-ind_N2 --> SET_N2 : Reset-ind. (Restart indicator, Connection identifier)
+ SET_N2 --> Rest-N2 : SET (Now + t317, timer T317)
+ Note right of SET_N2 : Timer value implementation dependent
+ Rest-N2 --> [*] : Return to "null" state (Rest-N0) instead of process end (all places in this process)
+ Note right of Rest-N2 : Handling second reception of RESTART
+ Rest-N2 --> RESTART_N2 : RESTART (Restart indicator, Connection identifier)
+ RESTART_N2 --> Cause_N2 : Cause := 101, CS := Rest-N2
+ Cause_N2 --> STATUS_N2 : STATUS (Cause, CS) Rest-N2
+ Rest-N2 --> Reset-error-resp : Reset-error-resp. (Cause := 82)
+ Reset-error-resp --> Is-Supported : Is Status Option supported?
+ Is-Supported --> STATUS_N2 : Yes
+ Is-Supported --> STATUS_N2 : No
+ Note right of Verify-Msg_N2 : See 5.6, 5.7, 5.8
+
+```
+
+The diagram illustrates the state transitions for the PROCESS Reset-Response-N. It begins at an initial state leading to Rest-N0 (Null). From Rest-N0, a RESTART message with a null connection identifier is processed, leading to a Verify-Msg state. The Result state then branches based on RAP, OK, CLR, and RAI inputs. RAP leads to STATUS (Cause, CS = Rest-N2), which then leads to Reset-ind. (Restart indicator, Connection identifier). OK leads to a state where a timer is set (Now + t317, timer T317). CLR and RAI both lead to STATUS (Cause, CS = Rest-N0), which then leads back to Rest-N0. The Reset-ind. state leads to SET (Now + t317, timer T317), which then leads to Rest-N2 (Restart). A note indicates that the timer value implementation is dependent. From Rest-N2, a transition leads to the end state, with a note that this returns to the "null" state (Rest-N0) instead of process end for all places in this process. Another note indicates that this state handles the second reception of RESTART. From Rest-N2, a RESTART message with a restart indicator and connection identifier is processed, leading to a state where Cause := 101, CS := Rest-N2. This leads to STATUS (Cause, CS) Rest-N2, which then leads back to Rest-N2. A Reset-error-resp. message (Cause := 82) is also processed from Rest-N2, leading to a decision state: Is Status Option supported?. If Yes, it leads to STATUS (Cause, CS = Rest-N2), which then leads back to Rest-N2. If No, it also leads to STATUS (Cause, CS) Rest-N2, which then leads back to Rest-N2. A note indicates that the Verify-Msg state for Rest-N2 is defined in sections 5.6, 5.7, and 5.8.
+
+State transition diagram for PROCESS Reset-Response-N. It shows transitions between states Rest-N0 (Null) and Rest-N2 (Restart) based on RESTART and Reset-error-resp. messages, with various guards and actions like Verify-Msg, STATUS, and SET timer T317.
+
+T1165860-94/d060
+
+
+
+```
+
+graph TD
+ Start([Reset-N2 - Restart]) -- "See 5.6.12, 5.5.2" --> Start
+ Start --> STATUS_CS[STATUS (Cause, CS)]
+ Start --> Reset_resp[Reset-resp. Restart indicator Connection identifier]
+ Start --> Timeout_T317[Timeout T317]
+
+ STATUS_CS --> Verify_Msg[Verify-Msg]
+ Verify_Msg --> Result{Result}
+
+ Reset_resp --> RESET_T317[RESET T317]
+ RESET_T317 --> RESTART_ACK[RESTART-ACKNOWLEDGE (Restart indicator, Connection identifier)]
+ RESTART_ACK --> Rest_N0_Null1([Rest-N0 - Null])
+
+ Timeout_T317 --> Reason_No[Reason := No reset-conf.]
+ Reason_No --> Reset_error_ind1[Reset-error-ind. (Reason)]
+ Reset_error_ind1 --> Rest_N0_Null2([Rest-N0 - Null])
+
+ Result --> RAP
+ RAP --> STATUS_CS_N2_1[STATUS (Cause CS) N2]
+ STATUS_CS_N2_1 --> OK
+ STATUS_CS_N2_1 --> CLR
+ STATUS_CS_N2_1 --> RAI
+ STATUS_CS_N2_1 --> I
+
+ OK --> STATUS_CS_N2_2[STATUS (Cause CS) N2]
+ CLR --> STATUS_CS_N2_2
+ RAI --> STATUS_CS_N2_2
+ STATUS_CS_N2_2 --> CS_Compatible{CS Compatible}
+ I --> CS_Compatible
+
+ CS_Compatible -- No --> Reason_Peer[Reason := Peer-Incompatible State]
+ Reason_Peer --> Reset_error_ind2[Reset-error ind. (Reason)]
+ Reset_error_ind2 --> Reset_N2_Restart([Reset-N2 - Restart])
+
+ CS_Compatible -- Yes --> Impl_Proc[Implementation dependent procedure]
+ Impl_Proc --> CS_Compatible
+
+ RESTART_ACK -.-> CI_Null[Connection identifier = null is valid]
+ Rest_N0_Null2 -.-> CI_Null
+
+```
+
+Flowchart for PROCESS Reset-Response-N. It starts with 'Reset-N2 - Restart' (See 5.6.12, 5.5.2) leading to three parallel paths: 1) STATUS (Cause, CS) -> Verify-Msg -> Result. 2) Reset-resp. Restart indicator Connection identifier -> RESET T317 -> RESTART-ACKNOWLEDGE -> Rest-N0 - Null. 3) Timeout T317 -> Reason := No reset-conf. -> Reset-error-ind. (Reason) -> Rest-N0 - Null. The Result from path 1 leads to a table with columns RAP, OK, CLR, RAI, I. RAP leads to STATUS (Cause CS) N2. OK, CLR, and RAI lead to STATUS (Cause CS) N2. I leads to CS Compatible. If CS Compatible is No, Reason := Peer-Incompatible State -> Reset-error ind. (Reason) -> Reset-N2 - Restart. If CS Compatible is Yes, Implementation dependent procedure -> CS Compatible. A dashed line from RESTART-ACKNOWLEDGE and Rest-N0 - Null indicates 'Connection identifier = null is valid'.
+
+T1175550-95/d061
+
+
+
+The flowchart illustrates the procedures for B-ISDN calls. It begins with a box labeled "Procedures for B-ISDN Calls". Below this, a "Verify-Msg" block (represented by a double-bordered rectangle) is shown with a dashed line pointing to a note "See 5.6, 5.7, 5.8". This leads to an oval state labeled "N0 - Null", which has a dashed line pointing to a note "See 5.1.1, 5.2.1".
+
+From the "N0 - Null" state, the flowchart branches into two main paths:
+
+- Left Path (SETUP (#)):** This path starts with a chevron block "SETUP (#)", followed by a double-bordered rectangle "Verify-Msg", and then a diamond decision block "Result". From the "Result" block, four outcomes are possible:
+ - RAP:** Leads to a chevron block "STATUS (Cause, CS = N1)", which then leads to a chevron block "Setup-ind. (#)", which finally leads to an oval state "N1 - Call Initiated".
+ - OK:** Leads directly to the "Setup-ind. (#)" block.
+ - CLR:** Leads to a chevron block "RELEASE COMPLETE (Cause, #)", which ends at a small 'X' symbol.
+ - RAI:** Leads to a chevron block "STATUS, (Cause, CS = N0)", which then leads to an oval state "N0 - Null".
+- Right Path (Setup-req. (#)):** This path starts with a chevron block "Setup-req. (#)", followed by a chevron block "SETUP (#)", then a rectangle "SET (Now + t303, timer T303); Timeout := 0", and finally an oval state "N6 - Call Present". Below this state is the text "T1165870-94/d062".
+
+Flowchart for B-ISDN Calls starting with a Verify-Msg and N0 - Null state, branching into SETUP and Setup-req paths with various result outcomes like RAP, OK, CLR, and RAI.
+
+
+
+```
+graph TD; N1([N1 - Call Initiated]) --> R[Release-resp. (cause)]; N1 --> P[Proceeding-req. (#)]; R --> RC[RELEASE-COMPLETE (Cause)]; RC --> X((X)); P --> CP[CALL-PROCEEDING (#)]; CP --> N3([N3 - Outgoing Call Proceeding]);
+```
+
+See 5.1.2.1, 5.1.3, 5.1.4, 5.1.5, 5.4.2
+
+T1165880-94/d063
+
+Flowchart for N1 - Call Initiated process
+
+
+
+```
+graph TD; N3([N3 - Outgoing Call Proceeding]) --> S[Setup-resp. (#)]; N3 --> A[Alerting-req. (#)]; S --> C[CONNECT (#)]; C --> N10([N10 - Active]); A --> AL[ALERTING (#)]; AL --> N4([N4 - Call Delivered]);
+```
+
+See 5.1.6, 5.1.7
+
+T1163170-94/d064
+
+Flowchart for N3 - Outgoing Call Proceeding process
+
+
+
+```
+
+graph TD
+ N4([N4 - Call Delivered])
+ SR{{Setup-resp. (#)}}
+ C{{CONNECT (#)}}
+ N10([N10 - Active])
+
+ N4 --> SR
+ SR --> C
+ C --> N10
+
+ N4 -.- Note[See 5.1.7]
+
+```
+
+The diagram illustrates a process flow with four main components arranged vertically. At the top is a state symbol (oval with flat sides) labeled "N4 - Call Delivered". To its right, a dashed line connects to a bracketed note "See 5.1.7". Below this state is an input symbol (chevron pointing right) labeled "Setup-resp. (#)". Below that is an output symbol (chevron pointing right) labeled "CONNECT (#)". At the bottom is another state symbol (oval with flat sides) labeled "N10 - Active". Solid vertical lines with downward-pointing arrows connect each component to the next in the sequence. Below the final state symbol is the text "T1163180-94/d065".
+
+Flowchart showing a process flow: N4 - Call Delivered (with a note 'See 5.1.7'), Setup-resp. (#), CONNECT (#), and N10 - Active. The diagram is labeled T1163180-94/d065.
+
+
+
+```
+graph TD; N6((N6 - Call Present)) --> C[CONNECT (#)]; N6 --> A[ALERTING (#)]; C --> VM1[Verify-Msg]; VM1 --> R1{Result}; R1 -- RAP --> S1[STATUS (Cause, CS = N8)]; R1 -- OK --> RT1[RESET T303]; R1 -- CLR --> D1((D)); R1 -- RAI --> S2[STATUS (Cause, CS = N6)]; R1 -- I --> S2; S1 --> RT1; S2 --> SC[Setup-conf. (#)]; SC --> N8((N8 - Connect Request)); A --> VM2[Verify-Msg]; VM2 --> R2{Result}; R2 -- RAP --> S3[STATUS (Cause, CS = N7)]; R2 -- OK --> RT2[RESET T303]; R2 -- CLR --> D2((D)); R2 -- RAI --> S4[STATUS (Cause, CS = N6)]; R2 -- I --> S4; S3 --> RT2; S4 --> AI[Alerting-ind. (#)]; AI --> SET[SET (Now + t301, timer T301)]; SET --> N7((N7 - Call Received)); N6 -.-> Ref["See 5.2.1, 5.2.5.2
+5.2.6, 5.2.7"]; T1163190-94/d066
+```
+
+Flowchart for N6 - Call Present process. It branches into CONNECT (#) and ALERTING (#) paths. The CONNECT path leads to N8 - Connect Request. The ALERTING path leads to N7 - Call Received. Both paths include message verification, result handling (RAP, OK, CLR, RAI, I), and status updates.
+
+
+
+```
+graph TD; N6((N6 - Call Present)) --> CALL[CALL-PROCEEDING (#)]; N6 --> T303[Timeout T303]; CALL --> VM[Verify-Msg]; VM --> R{Result}; R -- RAP --> STATUS_N9[STATUS (Cause, CS = N9)]; R -- OK --> RESET[RESET T303]; R -- CLR --> D((D)); R -- RAI --> STATUS_N6[STATUS (Cause, CS = N6)]; R -- I --> STATUS_N6; STATUS_N9 --> PROCEEDING[Proceeding-ind. (#)]; RESET --> PROCEEDING; STATUS_N6 --> N6_CALL_PRESENT((N6 - Call Present)); PROCEEDING --> SET_T310[SET (Now + t310, timer T310)]; SET_T310 --> N9_INCOMING((N9 - Incoming Call Proceeding)); T303 --> T1{Timeout = 1}; T1 -- Yes --> RELEASE[Release-conf. (Cause := 18)]; T1 -- No --> SETUP[SETUP (#)]; SETUP --> SET_T303[SET (Now + t310, timer T303; timeout = 1)]; SET_T303 --> N6_CALL_PRESENT; RELEASE -.-> X[ ]; X -.-> NOTE[The Application process should implement a delay before releasing the Call Reference]; NOTE -.-> ID[T1175560-95/d067];
+```
+
+Flowchart for N6 - Call Present process. It branches into CALL-PROCEEDING (#) and Timeout T303. CALL-PROCEEDING leads to Verify-Msg, then Result. Result branches into RAP (STATUS Cause, CS = N9), OK (RESET T303), CLR (D), RAI (STATUS Cause, CS = N6), and I. RAP, OK, and RAI lead to Proceeding-ind. (#), then SET (Now + t310, timer T310), then N9 - Incoming Call Proceeding. Timeout T303 leads to Timeout = 1. If Yes, Release-conf. (Cause := 18). If No, SETUP (#), then SET (Now + t303, timer T303; timeout = 1), then N6 - Call Present. A note indicates the Application process should implement a delay before releasing the Call Reference.
+
+
+
+```
+graph TD; N7((N7 - Call Received)) --- Ref[See 5.2.5.4, 5.2.7]; N7 --> T301{Timeout T301}; N7 --> CONNECT{CONNECT (#)}; T301 --> Cause19[Cause := 19]; Cause19 --> D1((D)); CONNECT --> Verify[Verify-Msg]; Verify --> Result{Result}; Result -- RAP --> STATUSN8{STATUS (Cause, CS = N8)}; Result -- OK --> RESET[RESET T301]; Result -- CLR --> D2((D)); Result -- RAI --> STATUSN7{STATUS (Cause, CS = N7)}; Result -- I --> N7; STATUSN8 --> RESET; STATUSN7 --> RESET; RESET --> SetupConf{Setup-conf. (#)}; SetupConf --> N8((N8 - Connect Request)); N7 --- ID[T1163210-94/d068];
+```
+
+Flowchart for N7 - Call Received process. It starts with 'N7 - Call Received' (oval), which branches into 'Timeout T301' (parallelogram) and 'CONNECT (#)' (parallelogram). 'Timeout T301' leads to 'Cause := 19' (rectangle) and then to connector 'D' (circle). 'CONNECT (#)' leads to 'Verify-Msg' (rectangle) and then to 'Result' (diamond). 'Result' has five branches: 'RAP' leads to 'STATUS (Cause, CS = N8)' (parallelogram); 'OK' leads to 'RESET T301' (rectangle); 'CLR' leads to connector 'D' (circle); 'RAI' leads to 'STATUS (Cause, CS = N7)' (parallelogram); 'I' leads to the entry point of 'N7 - Call Received'. Both 'STATUS (Cause, CS = N8)' and 'STATUS (Cause, CS = N7)' lead to 'RESET T301'. 'RESET T301' leads to 'Setup-conf. (#)' (parallelogram), which leads to 'N8 - Connect Request' (oval).
+
+
+
+```
+graph TD;
+ N8([N8 - Connect Request]) --- Note[See 5.2.7];
+ N8 --> SC[Setup-complete-req. (#)];
+ SC --> CA{CONNECT-ACKNOWLEDGE (#)};
+ CA --> N10([N10 - Active]);
+```
+
+The diagram illustrates a sequence of four steps in a process flow. It begins with a state labeled 'N8 - Connect Request' (represented by a stadium shape), which is connected by a dashed line to a bracketed note 'See 5.2.7'. This is followed by an internal process block 'Setup-complete-req. (#)' (represented by a rectangle with a concave left side), then an outgoing message block 'CONNECT-ACKNOWLEDGE (#)' (represented by a rectangle with a pointed right side), and finally a state labeled 'N10 - Active' (represented by a stadium shape). The steps are connected by vertical arrows pointing downwards. Below the diagram is the identifier 'T1163220-94/d069'.
+
+Flowchart showing the sequence of messages for PROCESS Q.2931-N: N8 - Connect Request, Setup-complete-req. (#), CONNECT-ACKNOWLEDGE (#), and N10 - Active. A note 'See 5.2.7' is associated with the first step.
+
+T1163220-94/d069
+
+
+
+```
+
+graph TD
+ N9((N9 - Incoming Call Proceeding)) --> Note[See 5.2.5.4, 5.2.7, 5.2.5.2]
+ N9 --> ALERTING[ALERTING (#)]
+ N9 --> CONNECT[CONNECT (#)]
+ N9 --> Timeout[Timeout T310]
+
+ ALERTING --> V1[Verify-Msg]
+ V1 --> R1{Result}
+
+ CONNECT --> V2[Verify-Msg]
+ V2 --> R2{Result}
+
+ Timeout --> C1[Cause := 18]
+ C1 --> D1((D))
+
+ R1 -- RAP --> S1[STATUS (Cause, CS = N7)]
+ R1 -- OK --> RT1[RESET T310]
+ R1 -- CLR --> D2((D))
+ R1 -- RAI --> S2[STATUS (Cause, CS = N9)]
+ R1 -- I --> N9_1((N9 - Incoming Call Proceeding))
+
+ S1 --> RT1
+ S2 --> N9_1
+
+ RT1 --> AI[Alerting-ind. (#)]
+ AI --> SET[SET (Now + t301, timer T301)]
+ SET --> N7((N7 - Call Received))
+
+ R2 -- RAP --> S3[STATUS (Cause, CS = N8)]
+ R2 -- OK --> RT2[RESET T310]
+ R2 -- CLR --> D3((D))
+ R2 -- RAI --> S4[STATUS (Cause, CS = N9)]
+ R2 -- I --> N9_2((N9 - Incoming Call Proceeding))
+
+ S3 --> RT2
+ S4 --> N9_2
+
+ RT2 --> SC[Setup-conf. (#)]
+ SC --> N8((N8 - Connect Request))
+
+ Note2[T1163230-94/d070]
+
+```
+
+Flowchart for N9 - Incoming Call Proceeding process. It branches into ALERTING (#), CONNECT (#), and Timeout T310. The ALERTING path leads to Verify-Msg, then a Result decision. The CONNECT path also leads to Verify-Msg and a Result decision. The Timeout T310 path leads to Cause := 18 and then to connector D. Both Result decisions have RAP, OK, CLR, RAI, and I options. The RAP options lead to STATUS messages (N7 or N8). The OK options lead to RESET T310 and then to Alerting-ind. (#) or Setup-conf. (#). The CLR options lead to connector D. The RAI options lead to STATUS messages (N9). The I options lead to N9 - Incoming Call Proceeding. The Alerting-ind. (#) path leads to SET (Now + t301, timer T301) and then to N7 - Call Received. The Setup-conf. (#) path leads to N8 - Connect Request. The STATUS (Cause, CS = N9) messages lead to N9 - Incoming Call Proceeding. A note 'See 5.2.5.4, 5.2.7, 5.2.5.2' is present near the top. A reference 'T1163230-94/d070' is present near the bottom right.
+
+
+
+This flowchart illustrates the 'N-10 - Active' process. It begins with an oval labeled 'N-10 - Active', which is linked by a dashed line to a note 'See 5.1.7'. The flow proceeds to a chevron-shaped connector labeled 'CONNECT ACKNOWLEDGE (#)'. Below this is a rectangular process block labeled 'Verify-Msg'. A diamond-shaped decision block labeled 'Result' follows. From the 'Result' diamond, five paths emerge: 'RAP' and 'RAI' lead to a chevron-shaped connector labeled 'STATUS (Cause, CS = N10)'; 'OK' and 'I' lead directly to an oval labeled 'N10 - Active'; and 'CLR' leads to a circle labeled 'D'. The 'STATUS (Cause, CS = N10)' connector leads to the 'N10 - Active' oval.
+
+Flowchart for N-10 - Active process
+
+
+
+This flowchart illustrates the '\*' (except N0) process. It begins with an oval labeled '\* (except N0)', which is linked by a dashed line to a note 'See 5.9'. The flow splits into two parallel paths. The left path consists of a chevron-shaped connector labeled 'Notify.req. (#)', followed by a chevron-shaped connector labeled 'NOTIFY (#)', and finally an oval labeled '-'. The right path consists of a chevron-shaped connector labeled 'NOTIFY (#)', followed by a rectangular process block labeled 'Verify-Msg', and then a diamond-shaped decision block labeled 'Result'. From the 'Result' diamond, five paths emerge: 'RAP' leads to a chevron-shaped connector labeled 'STATUS (Cause, CS)'; 'OK' leads to a chevron-shaped connector labeled 'Notify.ind. (#)'; 'CLR' leads to a circle labeled 'D'; 'RAI' leads to a chevron-shaped connector labeled 'STATUS (Cause, CS)'; and 'I' leads to an oval labeled '-'. Both 'STATUS (Cause, CS)' connectors lead to the same oval labeled '-'. The 'Notify.ind. (#)' connector also leads to this oval.
+
+Flowchart for \* (except N0) process
+
+T1163240-94/d071
+
+
+
+```
+graph TD; N10_Active1([N10 - Active]) -- "See 5.6.9 b, 5.6.10" --- N10_Active1; N10_Active1 --> LRI[Link Release indication]; N10_Active1 --> LEError[Link Establish error]; N10_Active1 --> LEIndication[Link Establish indication]; N10_Active1 --> LEConfirm[Link Establish confirm]; LRI --> LERequest[Link Establish request]; LERequest --> N10_Active2([N10 - Active]); LEError --> ReleaseConf["Release-conf. (Cause := 27)"]; ReleaseConf --> End((X)); LEIndication --> SE((SE)); LEConfirm --> SE; CoOrdN[From Co-ord-N] -.-> LRI;
+```
+
+State transition diagram for N10 - Active process. It shows four main paths: 1) Link Release indication (from Co-ord-N) leads to Link Establish request, which returns to N10 - Active. 2) Link Establish error leads to Release-conf. (Cause := 27), which ends. 3) Link Establish indication leads to SE. 4) Link Establish confirm leads to SE. A note 'See 5.6.9 b, 5.6.10' is associated with the initial N10 - Active state.
+
+T1165890-94/d072
+
+PROCESS Q.2931-N;
+
+page 12 of (31)
+
+
+
+```
+
+graph TD
+ subgraph Path1 [ ]
+ P1_1[RELEASE COMPLETE
+(Cause, #)] --> P1_2[Verify-Msg]
+ P1_2 --> P1_3{Result}
+ P1_3 --> P1_4[RESET ALL TIMERS]
+ P1_4 --> P1_5[Release-conf.
+(Cause, #)]
+ P1_5 --> P1_6(( ))
+ end
+ subgraph Path2 [ ]
+ P2_1[RELEASE
+(Cause, #)] --> P2_2[Verify-Msg]
+ P2_2 --> P2_3{Result}
+ P2_3 --> P2_4[RESET ALL TIMES]
+ P2_4 --> P2_5[Release-ind.
+(Cause, #)]
+ P2_5 --> P2_6((N11 - Release
+Request))
+ end
+ subgraph Path3 [ ]
+ P3_1[Release.req.
+(Cause)] --> P3_2[CauseR := Cause
+/*Cause saved*/]
+ P3_2 --> P3_3[RESET ALL TIMERS]
+ P3_3 --> P3_4[RELEASE
+(Cause)]
+ P3_4 --> P3_5[SET (Now + t308,
+timer T308)]
+ P3_5 --> P3_6((N12 - Release
+Indication))
+ end
+ P1_1 -.-> C1["*
+(except N0, N12)"]
+ C1 -.-> R1["See 5.6.4, 5.4.3"]
+ P2_1 -.-> C2["*
+(except N0, N11, N12)"]
+ C2 -.-> R2["See 5.4.3, 5.4.4"]
+ P1_2 -.-> C3[Message length
+not checked]
+ P2_2 -.-> C3
+ P2_5 -.-> R3["After receiving this
+primitive, the
+Application process
+shall release the
+user virtual channel"]
+ P3_5 -.-> R3
+ P3_2 -.-> C4["new 'cause remote' variable
+for cause values sent to
+remote user (e.g. called
+user when overlap receiving
+timeout occurs)"]
+ D((D)) --> P3_2
+ P1_3 --> P1_3_I[I]
+ P1_3 --> P1_3_RAP[RAP]
+ P1_3 --> P1_3_OK[OK]
+ P1_3 --> P1_3_CLR[CLR]
+ P1_3 --> P1_3_RAI[RAI]
+ P2_3 --> P2_3_RAP[RAP]
+ P2_3 --> P2_3_OK[OK]
+ P2_3 --> P2_3_CLR[CLR]
+ P2_3 --> P2_3_RAI[RAI]
+ P2_3 --> P2_3_I[I]
+ P1_5 -.-> R4["After receiving this
+primitive, the
+Application process
+shall release the
+user virtual channel"]
+ error_handling[error handling exception]
+ P1_3 -.-> error_handling
+ error_handling -.-> P2_3
+
+```
+
+Flowchart for PROCESS Q.2931-N showing three main paths for RELEASE primitives. Path 1 (left) starts with RELEASE COMPLETE (Cause, #), followed by Verify-Msg, Result, and RESET ALL TIMERS, leading to Release-conf. Path 2 (middle) starts with RELEASE (Cause, #), followed by Verify-Msg, Result, RESET ALL TIMES, Release-ind., and N11 - Release Request. Path 3 (right) starts with Release.req. (Cause), followed by CauseR := Cause, RESET ALL TIMERS, RELEASE (Cause), SET (Now + t308, timer T308), and N12 - Release Indication. A callout 'new 'cause remote' variable for cause values sent to remote user (e.g. called user when overlap receiving timeout occurs)' points to the CauseR := Cause block. Another callout 'After receiving this primitive, the Application process shall release the user virtual channel' points to the Release-ind. blocks in paths 2 and 3. A dashed line labeled 'Message length not checked' connects the Verify-Msg blocks in paths 1 and 2. A connector 'D' is shown between paths 2 and 3.
+
+T1163260-94/d073
+
+
+
+```
+graph TD; A([N11 RELEASE REQUEST]) -- "See 5.4.3, 5.6.12 b)" --> B[/Release resp. (#)/]; A --> C[/STATUS (Cause, CS)/]; B --> D[/RELEASE COMPLETE (#)/]; D --> E(( )); C --> F[Verify message]; F --> G{Result}; G -- RAP --> H[/STATUS (Cause, CS)/]; G -- OK --> I([N0 - Null]); G -- CLR --> J(( )); G -- RAI --> K[/STATUS (Cause, CS)/]; H --> J; I --> J; K --> J; J --> L{CS = 0}; L -- Yes --> M([N11 Release Request]); L -- No --> N(( )); M --- O[T1165900-94/d074];
+```
+
+Flowchart for N11 RELEASE REQUEST process. It starts with an N11 RELEASE REQUEST, leading to Release resp. (#) and STATUS (Cause, CS). Release resp. (#) leads to RELEASE COMPLETE (#) which ends. STATUS (Cause, CS) leads to Verify message, which leads to a Result decision. The Result decision has four paths: RAP, OK, CLR, and RAI. RAP and RAI lead to STATUS (Cause, CS) blocks. OK leads to N0 - Null. CLR leads to a junction. All four paths lead to a CS = 0 decision. If CS = 0 is Yes, it leads to N11 Release Request. If CS = 0 is No, it ends. A note 'See 5.4.3, 5.6.12 b)' is associated with the initial request.
+
+148 Recommendation Q.2931 (02/95)
+
+PROCESS Q.2931-N;
+
+page 14 of (31)
+
+
+
+```
+
+ graph TD
+ N12[N12 - Release Indication] -- See 5.4.4, 5.4.5 --> RELEASE_COMP{RELEASE-COMPLETE #}
+ N12 -- See 5.4.4, 5.4.5 --> RELEASE_IN{RELEASE #}
+ N12 -- See 5.4.4, 5.4.5 --> T308{Timeout T308}
+
+ RELEASE_COMP --> VerifyMsg[Verify-Msg]
+ RELEASE_IN -- Clear collision --> VerifyMsg
+
+ VerifyMsg --> Result{Result}
+ Result -- RAP --> RESET_T308[RESET T308]
+ Result -- OK --> RESET_T308
+ Result -- CLR --> RESET_T308
+ Result -- RAI --> RESET_T308
+ Result -- I --> RESET_T308
+
+ RESET_T308 --> RelConf[Release-conf. Cause, #]
+ RelConf -- After receiving this primitive, the Application process shall release the user virtual channel --> End1((X))
+
+ T308 --> Timeout1{Timeout = 1}
+ Timeout1 -- No --> Cause1[Cause1 := CauseR]
+ Timeout1 -- Yes --> RelReason[Release reason := failure]
+
+ Cause1 --> CauseOpt{Cause option}
+ CauseOpt --> RELEASE_C1[RELEASE Cause1, #]
+ CauseOpt --> Cause2[Cause2 := 102]
+
+ Cause2 --> RELEASE_C1C2[RELEASE Cause1, Cause2, #]
+
+ RelReason --> RelConfReason[Release conf. Release reason]
+ RelConfReason --> End2((X))
+ End2 -- The Application process shall place the user virtual channel in a maintenance condition --> End2
+
+ RELEASE_C1 --> SetTimer[SET Now + t308, timer T308; Timeout := 1]
+ RELEASE_C1C2 --> SetTimer
+ SetTimer --> N12_Ind[N12 - Release Indication]
+
+```
+
+T1165910-94/d075
+
+After receiving this primitive, the Application process shall release the user virtual channel
+
+The Application process shall place the user virtual channel in a maintenance condition
+
+SDL Diagram for PROCESS Q.2931-N showing release indication handling.
+
+
+
+```
+graph TD
+ Start([N12 - Release Indication]) --> Input1[/STATUS
(Cause, CS)/]
+ Input1 --> Task1[Verify message]
+ Task1 --> Dec1{Result}
+
+ Dec1 -- RAP --> Input2[/STATUS
(Cause, CS)/]
+ Dec1 -- OK --> Dec2{CS = 0}
+ Dec1 -- CLR --> State2([N0 - Null])
+ Dec1 -- RAI --> Input3[/STATUS
(Cause, CS)/]
+ Dec1 -- I --> Join1
+
+ Input2 --> Join1
+ State2 --> Join1
+ Input3 --> Join1
+ Join1(( )) --> Dec2
+
+ Dec2 -- Yes --> Output1[/Release-conf.
(Cause)/]
+ Dec2 -- No --> State3([N12 - Release
Indication])
+ Output1 --> End((X))
+```
+
+The flowchart illustrates the process for Q.2931-N. It begins with a state oval labeled "N12 - Release Indication", which has a dashed line and bracket pointing to the text "See 5.6.12". Below this is an input chevron labeled "STATUS (Cause, CS)". This is followed by a task rectangle labeled "Verify message". A decision diamond labeled "Result" follows. From "Result", five paths emerge: "RAP", "OK", "CLR", "RAI", and "I". The "RAP" path leads to an input chevron labeled "STATUS (Cause, CS)". The "OK" path leads directly to a decision diamond labeled "CS = 0". The "CLR" path leads to a state oval labeled "N0 - Null". The "RAI" path leads to an input chevron labeled "STATUS (Cause, CS)". The "I" path bypasses these and joins the others. All paths except "OK" (which goes directly) converge before entering the "CS = 0" diamond. From "CS = 0", a "Yes" path leads to an output chevron labeled "Release-conf. (Cause)", which then leads to an end symbol (X). A "No" path leads to a state oval labeled "N12 - Release Indication". Below this final oval is the reference code "T1165920-94/d076".
+
+SDL flowchart for PROCESS Q.2931-N showing state transitions and message handling.
+
+
+
+```
+
+graph TD
+ subgraph LeftFlow [ ]
+ L1[except N0
+See 5.6.11] --> L2[STATUS-ENQUIRY]
+ L2 --> L3[Verify message]
+ L3 --> L4{Result}
+ L4 -- RAP --> L5[CS := 'current state',
+Cause := 30]
+ L4 -- OK --> L5
+ L4 -- CLR --> L5
+ L4 -- RAI --> L6[STATUS
+(Cause, CS)]
+ L6 --> L7[-]
+ end
+
+ subgraph RightFlow [ ]
+ R1[except N0, N11,
+N12
+See 5.6.12] --> R2[STATUS
+(Cause, CS)]
+ R2 --> R3[Verify message]
+ R3 --> R4{Result}
+ R4 -- RAP --> R5[STATUS
+(Cause, CS)]
+ R4 -- OK --> R6[N0 - Null]
+ R4 -- CLR --> R6
+ R4 -- RAI --> R7[STATUS
+(Cause, CS)]
+ R5 --> R6
+ R6 --> R8[X]
+ R7 --> R9{CS = 0}
+ R9 -- Yes --> R10[Release-conf.
+(cause)]
+ R10 --> R8
+ R9 -- No --> R11{Cause = 30}
+ R11 -- Yes --> R12[RESET T322]
+ R12 --> R13[Verify State]
+ R13 --> R14{Compatible State}
+ R14 -- Yes --> R15[-]
+ R14 -- No --> R16{Recovery option}
+ R16 -- No --> R17[Status-ind.
+(Cause := 101)]
+ R17 --> R18((D))
+ R16 -- Yes --> R19[Recovery procedure]
+ R19 --- R20[Implementation specific]
+ R19 --> R8
+ end
+
+ L5 --> L6
+ L6 --> L7
+ L7 --> I((I))
+ I --> RAI
+ RAI --> R4
+
+```
+
+Flowchart for PROCESS Q.2931-N, page 16 of (31). The diagram shows two main process flows. The left flow starts with a connector 'except N0' (See 5.6.11), followed by STATUS-ENQUIRY, Verify message, and a Result decision. The Result leads to RAP, OK, CLR, or RAI paths. RAP, OK, and CLR lead to CS := 'current state', Cause := 30, then STATUS (Cause, CS), and finally a connector '-'. The RAI path leads to a connector 'I'. The right flow starts with a connector 'except N0, N11, N12' (See 5.6.12), followed by STATUS (Cause, CS), Verify message, and a Result decision. The Result leads to RAP, OK, CLR, or RAI paths. RAP, OK, and CLR lead to STATUS (Cause, CS), then N0 - Null, and finally a connector 'X'. The RAI path leads to STATUS (Cause, CS), then a CS = 0 decision. If Yes, it leads to Release-conf. (cause) and then a connector 'X'. If No, it leads to a Cause = 30 decision. If Yes, it leads to RESET T322, then Verify State, then a Compatible State decision. If Yes, it leads to a connector '-'. If No, it leads to a Recovery option decision. If No, it leads to Status-ind. (Cause := 101) and then a connector 'D'. If Yes, it leads to Recovery procedure, which is Implementation specific, and then a connector 'X'.
+
+T1175570-95/d077
+
+
+
+```
+
+ graph TD
+ Start([* except N0]) --> T322_Exp[Timeout T322]
+ Start --> SE_Circle((SE))
+ SE_Circle --> Timeout_0[Timeout := 0]
+ T322_Exp --> Timeout_Inc[Timeout := Timeout + 1]
+ Timeout_Inc --> Timeout_NT{Timeout = NT}
+ Timeout_NT -- Yes --> D1((D))
+ Timeout_NT -- No --> ACTIVE_T322{ACTIVE T322}
+ ACTIVE_T322 -- Yes --> D2(( ))
+ ACTIVE_T322 -- No --> STATUS_ENQ[STATUS ENQUIRY (#)]
+ STATUS_ENQ --> SET_T322[SET (Now + t322, timer T322)]
+ SET_T322 --> D2
+ D2 --> Unrecognized[unrecognized message]
+ Unrecognized --> Verify_Msg1[Verify-Msg]
+ Verify_Msg1 --> Result1{Result}
+ Result1 --> Inst_Flag_0[Inst. Ind. flag = 0]
+ Inst_Flag_0 -- RAI --> STATUS_Cause1[STATUS Cause # 97/101]
+ STATUS_Cause1 --> D3(( ))
+ Result1 -- Reserved_Inst_Ind[Reserved Inst. Ind.] --> I
+ I --> State_Release{State = Release request or Release indication?}
+ State_Release -- Yes --> STATUS_Cause1
+ State_Release -- No --> D4((D))
+ Start --> Any_Msg[/* any other message*/]
+ Any_Msg --> Verify_Msg2[Verify-Msg]
+ Verify_Msg2 --> Result2{Result}
+ Result2 --> Inst_Ind_Flag_0[Inst. ind. flag = 0]
+ Inst_Ind_Flag_0 -- RAI --> STATUS_Cause2[STATUS Cause # 97/101]
+ STATUS_Cause2 --> D5(( ))
+ Result2 -- Reserved_Inst_Ind_2[Reserved Inst. Ind.] --> I_2
+ I_2 --> State_Release2{State = Release request or Release indication?}
+ State_Release2 -- Yes --> STATUS_Cause2
+ State_Release2 -- No --> D6((D))
+ Note1[NT = number of STATUS ENQUIRY transmissions; Implementation dependent value ≥ 1] -.-> Timeout_NT
+ Note2[See 5.6.4, 5.6.11] -.-> Start
+ Note3[Any recognized message other than those specifically shown in Q.2931N process] -.-> Any_Msg
+ Note4[Notification can be sent on any state other than the null state] -.-> D5
+
+```
+
+The flowchart illustrates the state transition logic for PROCESS Q.2931-N. It begins with an initial state (\*) except N0, which leads to a Timeout T322 state or a Start Event (SE). In the Timeout T322 state, the timeout is incremented. If it reaches NT (number of STATUS ENQUIRY transmissions), the process reaches a destination (D). Otherwise, it checks if ACTIVE T322 is true. If yes, it reaches another destination. If no, it sends a STATUS ENQUIRY (#) and sets the timer to Now + t322. If an unrecognized message is received, it calls Verify-Msg. If the result indicates 'Inst. Ind. flag = 0' and 'RAI' is set, it sends 'STATUS Cause # 97/101' and reaches a destination. If 'Reserved Inst. Ind.' is set, it checks if the state is a 'Release request or Release indication'. If yes, it sends 'STATUS Cause # 97/101'; if no, it reaches a destination. For any other recognized message, the process calls Verify-Msg again. If the result indicates 'Inst. ind. flag = 0' and 'RAI' is set, it sends 'STATUS Cause # 97/101' and reaches a destination. If 'Reserved Inst. Ind.' is set, it checks if the state is a 'Release request or Release indication'. If yes, it sends 'STATUS Cause # 97/101'; if no, it reaches a destination. Annotations include: 'NT = number of STATUS ENQUIRY transmissions; Implementation dependent value ≥ 1', 'See 5.6.4, 5.6.11', 'Any recognized message other than those specifically shown in Q.2931N process', and 'Notification can be sent on any state other than the null state'. The diagram is identified by T1175580-95/d078.
+
+Flowchart for PROCESS Q.2931-N showing state transitions and message handling logic.
+
+
+
+```
+
+graph TD
+ subgraph Path1
+ N11N12([N11, N12]) -- "See 5.6.9 a), b)" --> LE1[Link Establish indication]
+ LE1 --> D1([ - ])
+ end
+ subgraph Path2
+ N1N3N4N6N7N8N9([N1, N3, N4, N6, N7, N8, N9]) --> LE2[Link Establish indication]
+ LE2 --> SEQ{Status enquiry option supported?}
+ SEQ -- No --> D2([ - ])
+ SEQ -- Yes --> SE((SE))
+ end
+ subgraph Path3
+ Asterisk([ * (except N10) ]) -- "See 5.6.10" --> LR[Link Release indication]
+ LR --> RC["Release-conf. (Cause := # 27)"]
+ RC --> X[X]
+ end
+
+```
+
+Flowchart for Process Q.2931-N, page 18. It shows three vertical paths. Path 1: N11, N12 -> Link Establish indication -> - (with a note 'See 5.6.9 a), b)'). Path 2: N1, N3, N4, N6, N7, N8, N9 -> Link Establish indication -> Status enquiry option supported? (No leads to -, Yes leads to SE). Path 3: \* (except N10) -> Link Release indication -> Release-conf. (Cause := # 27) -> X (with a note 'See 5.6.10').
+
+T1165950-94/d079
+
+
+
+```
+
+graph TD
+ E[Extensions for symmetric call operation] --> N1([N1 - Call Initiated])
+ N1 -- "See 5.1.2.1, 5.1.3, 5.1.4, 5.1.5, 5.4.2, Annex H" --> N1
+ N1 --> SR[Setup-resp. (#)]
+ N1 --> AR[Alerting-req. (#)]
+ SR --> C[CONNECT (#)]
+ C --> N10([N10 - Active])
+ AR --> AL[ALERTING (#)]
+ AL --> N4([N4 - Call Delivered])
+
+```
+
+Flowchart for Process Q.2931-N, page 19. It starts with 'Extensions for symmetric call operation' -> N1 - Call Initiated (with a note 'See 5.1.2.1, 5.1.3, 5.1.4, 5.1.5, 5.4.2, Annex H'). From N1, it branches into two paths: Path 1: Setup-resp. (#) -> CONNECT (#) -> N10 - Active. Path 2: Alerting-req. (#) -> ALERTING (#) -> N4 - Call Delivered.
+
+T1163330-94/d080
+
+
+
+```
+graph TD; A[Additional procedures related to interworking] --> B((N1 - Call Initiated)); B -.-> C[See 6.5.2]; B --> D[/More-info.req. (#)/]; D --> E[/SETUP ACKNOWLEDGE (#)/]; E --> F[SET (Now + t302, timer T302)]; F --> G((N2 - Overlap Sending)); G --- H[T1163340-94/d081];
+```
+
+Additional procedures related to interworking
+
+N1 - Call Initiated
+
+See 6.5.2
+
+More-info.req. (#)
+
+SETUP ACKNOWLEDGE (#)
+
+SET (Now + t302, timer T302)
+
+N2 - Overlap Sending
+
+T1163340-94/d081
+
+Flowchart of PROCESS Q.2931-N showing steps: Additional procedures related to interworking, N1 - Call Initiated, More-info.req. (#), SETUP ACKNOWLEDGE (#), SET (Now + t302, timer T302), N2 - Overlap Sending. Includes a note 'See 6.5.2' for N1 and a reference 'T1163340-94/d081' at the bottom.
+
+
+
+```
+
+graph TD
+ Start([N2 - Overlap Sending]) --> INFO[INFORMATION (#)]
+ Start --> PR[Proceeding-req. (#)]
+ Start --> T302[Timeout T302]
+ INFO --> VM[Verify-Msg]
+ VM --> Result{Result}
+ Result -- RAP --> STATUS1[STATUS (Cause, CS =N2)]
+ Result -- OK --> INFOIND[Info-ind. (#)]
+ Result -- CLR --> D1((D))
+ Result -- RAI --> STATUS2[STATUS (Cause, CS =N2)]
+ Result -- I --> STATUS2
+ STATUS2 --> N2OS1([N2 - Overlap Sending])
+ INFOIND --> SCIE{SC IE present}
+ SCIE -- Yes --> N2OS2([N2 - Overlap Sending])
+ SCIE -- No --> SET[SET (Now + t302, timer T302)]
+ SET --> N2OS2
+ PR --> RESET[RESET T302]
+ RESET --> IsComplete{Is information definitely complete?}
+ T302 --> IsComplete
+ IsComplete -- Yes --> CALLPROC[CALL-PROCEEDING (#)]
+ CALLPROC --> N2OS3([N3 - Outgoing Call Proceeding])
+ IsComplete -- No --> Cause[Cause := 28
+Cause-remote := 102]
+ Cause --> D2((D))
+ D2 --- Note[T1175600-95/d082]
+ Note --- SCNote[SC means Sending Complete]
+ Note --- SeeNote[See 6.5.2]
+
+```
+
+Flowchart for PROCESS Q.2931-N, starting with N2 - Overlap Sending. It branches into INFORMATION (#), Proceeding-req. (#), and Timeout T302. The INFORMATION path leads to Verify-Msg and then a Result decision (RAP, OK, CLR, RAI, I). The Proceeding-req. path leads to RESET T302 and then a decision 'Is information definitely complete?'. The Timeout T302 path leads to the same 'Is information definitely complete?' decision. Various states like STATUS (Cause, CS =N2), Info-ind. (#), CALL-PROCEEDING (#), and N2 - Overlap Sending are shown.
+
+
+
+Additional procedures related to interworking
+
+N2 - Overlap Sending --- See 6.5.2, 6.6
+
+Progress.req. (#)
+
+Setup.resp. (#)
+
+Alerting.req. (#)
+
+RESET T302
+
+RESET T302
+
+RESET T302
+
+PROGRESS (#)
+
+CONNECT (#)
+
+ALERTING (#)
+
+N2 - Overlap Sending
+
+N10 - Active
+
+N4 - Call Delivered
+
+T1163360-94/d083
+
+Flowchart for PROCESS Q.2931-N; page 22 of (31). It shows three parallel paths starting from 'N2 - Overlap Sending'. Path 1: Progress.req. (#) -> RESET T302 -> PROGRESS (#) -> N2 - Overlap Sending. Path 2: Setup.resp. (#) -> RESET T302 -> CONNECT (#) -> N10 - Active. Path 3: Alerting.req. (#) -> RESET T302 -> ALERTING (#) -> N4 - Call Delivered. A note 'Additional procedures related to interworking' is at the top. A reference 'See 6.5.2, 6.6' is next to the start node. The diagram code is T1163360-94/d083.
+
+
+
+Additional procedures related to interworking
+
+N3 - Outgoing Call Proceeding --- See 6.6
+
+Progress.req. (#)
+
+PROGRESS (#)
+
+N3 - Outgoing Call Proceeding
+
+T1163370-94/d084
+
+Flowchart for PROCESS Q.2931-N; page 23 of (31). It shows a single path starting from 'N3 - Outgoing Call Proceeding'. Path: Progress.req. (#) -> PROGRESS (#) -> N3 - Outgoing Call Proceeding. A note 'Additional procedures related to interworking' is at the top. A reference 'See 6.6' is next to the start node. The diagram code is T1163370-94/d084.
+
+
+
+Additional procedures related to interworking
+
+N4 - Call Delivered
+
+See 6.6
+
+Progress-req. (#)
+
+PROGRESS (#)
+
+N4 - Call Delivered
+
+T1163380-94/d085
+
+```
+graph TD; A([N4 - Call Delivered]) --> B[/Progress-req. (#)/]; B --> C[/PROGRESS (#)/]; C --> D([N4 - Call Delivered]);
+```
+
+Flowchart showing a sequence of steps: N4 - Call Delivered, Progress-req. (#), PROGRESS (#), N4 - Call Delivered. Includes a callout 'See 6.6' and a reference code T1163380-94/d085.
+
+
+
+```
+graph TD
+ Start[Additional procedures related to interworking] --> N6_1((N6 - Call Present))
+ N6_1 -.- Note1[See 6.5.3]
+ N6_1 --> SetupAck[/SETUP-ACKNOWLEDGE (#)/]
+ N6_1 --> MoreInfoReq[/More-info-req. (#)/]
+ SetupAck --> VerifyMsg[Verify-Msg]
+ MoreInfoReq --> VerifyMsg
+ VerifyMsg --> Result{Result}
+ Result -- RAP --> StatusN25[/STATUS (Cause, CS =N25)/]
+ Result -- OK --> ResetT303[RESET T303]
+ Result -- CLR --> ConnF((F))
+ Result -- RAI --> StatusN6[/STATUS (Cause, CS =N6)/]
+ Result -- I --> N6_2((N6 - Call Present))
+ StatusN25 --> SetT304[SET (Now + t304, timer T304)]
+ ResetT303 --> SetT304
+ StatusN6 --> SetT304
+ SetT304 --> MoreInfoInd[/More-info-ind. (#)/]
+ MoreInfoInd --> N25((N25 - Overlap Receiving))
+ style Start fill:none,stroke:none
+ subgraph Legend
+ T1163390[T1163390-94/d086]
+ end
+```
+
+Flowchart for PROCESS Q.2931-N showing call handling logic for additional interworking procedures. It starts with a state 'N6 - Call Present' (referenced to section 6.5.3). From this state, two messages can be received: 'SETUP-ACKNOWLEDGE (#)' or 'More-info-req. (#)'. Both lead to a 'Verify-Msg' process followed by a 'Result' decision. The decision has five outcomes: 'RAP' leads to a 'STATUS (Cause, CS =N25)' message; 'OK' leads to 'RESET T303'; 'CLR' leads to connector 'F'; 'RAI' leads to a 'STATUS (Cause, CS =N6)' message; and 'I' leads back to the 'N6 - Call Present' state. The 'RAP', 'OK', and 'RAI' paths eventually converge to 'SET (Now + t304, timer T304)', followed by a 'More-info-ind. (#)' message, ending in the state 'N25 - Overlap Receiving'.
+
+Additional procedures related to interworking
+
+
+
+```
+graph TD; Start([N9 - Incoming Call Proceeding]) -.-> Ref66[See 6.6]; Start --> Progress[/PROGRESS (#)/]; Progress --> Verify[Verify-Msg]; Verify --> Result{Result}; Result -- RAP --> Status1[/STATUS (Cause, CS =N9)/]; Result -- OK --> Reset[RESET T310]; Result -- CLR --> F((F)); Result -- RAI --> Status2[/STATUS (Cause, CS =N9)/]; Result -- I --> Start; Status1 --> ProgressInd[/Progress-ind. (#)/]; Status2 --> ProgressInd; ProgressInd --> End([N9 - Incoming Call Proceeding]); Reset --> ProgressInd; T116340094d087[T1163400-94/d087];
+```
+
+Flowchart for N9 - Incoming Call Proceeding. It starts with a state 'N9 - Incoming Call Proceeding' (referencing section 6.6), followed by 'PROGRESS (#)', 'Verify-Msg', and a 'Result' decision. The 'Result' has five branches: RAP, OK, CLR, RAI, and I. RAP leads to 'STATUS (Cause, CS =N9)'. OK leads to 'RESET T310'. CLR leads to a failure state 'F'. RAI leads to 'STATUS (Cause, CS =N9)'. I loops back to the start. Both 'STATUS' blocks lead to 'Progress-ind. (#)', which then leads to the final 'N9 - Incoming Call Proceeding' state. Reference T1163400-94/d087 is noted.
+
+
+
+Additional procedures related to interworking
+
+```
+graph TD; Start([N25 - Overlap Receiving]) --> IntoReq[/Into-req (#)/]; Start --> Timeout[/Timeout T304/]; Start --> Progress[/PROGRESS (#)/]; Note[See 6.5.3, 6.6] -.-> Start; IntoReq --> Info[/INFORMATION (#)/]; Info --> Set[SET (Now + t304, timer T304)]; Set --> Start; Timeout --> Cause["Cause := 102, Cause-remote := 28"]; Cause --> F1((F)); Progress --> Verify[Verify-Msg]; Verify --> Result{Result}; Result -- RAP --> Status1[/STATUS (Cause, CS =N25)/]; Status1 --> Start; Result -- OK --> Reset[RESET T304]; Reset --> ProgressInd[/Progress-ind. (interworking, #)/]; ProgressInd --> Start; Result -- CLR --> F2((F)); Result -- RAI --> Status2[/STATUS (Cause, CS =N25)/]; Status2 --> Start; Result -- I --> Result; T116341094d088[T1163410-94/d088]
+```
+
+Flowchart for N25 - Overlap Receiving process. It starts with a connector 'N25 - Overlap Receiving' leading to three parallel paths: 'Into-req (#)', 'Timeout T304', and 'PROGRESS (#)'. The 'Into-req (#)' path leads to 'INFORMATION (#)', then 'SET (Now + t304, timer T304)', and back to 'N25 - Overlap Receiving'. The 'Timeout T304' path leads to 'Cause := 102, Cause-remote := 28', then to connector 'F'. The 'PROGRESS (#)' path leads to 'Verify-Msg', then to a 'Result' decision diamond. The 'Result' diamond has five branches: 'RAP' leads to 'STATUS (Cause, CS =N25)'; 'OK' leads to 'RESET T304'; 'CLR' leads to connector 'F'; 'RAI' leads to 'STATUS (Cause, CS =N25)'; 'I' loops back to the 'Result' diamond. Both 'STATUS' blocks lead to 'N25 - Overlap Receiving'. 'RESET T304' leads to 'Progress-ind. (interworking, #)', which leads to 'N25 - Overlap Receiving'. A note 'See 6.5.3, 6.6' is next to the initial connector. A reference 'T1163410-94/d088' is at the bottom right.
+
+
+
+Additional procedures related to interworking
+
+```
+
+graph TD
+ Start([N25 - Overlap Receiving]) -- See 6.5.3 --- Dummy[ ]
+ style Dummy display:none
+
+ Start --> CP[CALL-PROCEEDING #]
+ Start --> AL[ALERTING #]
+
+ CP --> VM1[Verify-Msg]
+ VM1 --> R1{Result}
+ R1 -- RAP --> S1[STATUS Cause, CS =N9]
+ R1 -- OK --> RT1[RESET T304]
+ R1 -- CLR --> F1((F))
+ R1 -- RAI --> S2[STATUS Cause, CS =N25]
+ R1 -- I --> S2
+
+ S1 --> RT1
+ RT1 --> PI[Proceeding-ind. #]
+ PI --> SET1[SET Now + t310, timer T310]
+ SET1 --> N9([N9 - Incoming Call Request])
+
+ AL --> VM2[Verify-Msg]
+ VM2 --> R2{Result}
+ R2 -- RAP --> S3[STATUS Cause, CS =N7]
+ R2 -- OK --> RT2[RESET T304]
+ R2 -- CLR --> F2((F))
+ R2 -- RAI --> S4[STATUS Cause, CS =N25]
+ R2 -- I --> S4
+
+ S3 --> RT2
+ RT2 --> AI[Alerting-ind. #]
+ AI --> SET2[SET Now + t310, timer T310]
+ SET2 --> N7([N7 - Call Received])
+
+ S2 --> N25_Back([N25 - Overlap Receiving])
+ S4 --> N25_Back
+
+```
+
+T1163420-94/089
+
+
+
+```
+graph TD; A[Additional procedures related to interworking] --> B((N25 - Overlap Receiving)); B -.-> B_note[See 6.5.3]; B --> C[/CONNECT (#)/]; C --> D[Verify-Msg]; D --> E{Result}; E -- RAP --> F[STATUS (Cause, CS =N8)]; E -- OK --> G[RESET T304]; E -- CLR --> H((F)); E -- RAI --> I[STATUS (Cause, CS =N25)]; E -- I --> J((N25 - Overlap Receiving)); F --> G; G --> K[/Setup-conf. (3)/]; I --> J; J --> L((N8 - Connect Request)); K --> L; M[T1163430-94/d090];
+```
+
+Flowchart for N25 - Overlap Receiving process. It starts with 'Additional procedures related to interworking', followed by 'N25 - Overlap Receiving' (with a note 'See 6.5.3'), 'CONNECT (#)', 'Verify-Msg', and a 'Result' decision. The 'Result' decision has five paths: RAP, OK, CLR, RAI, and I. RAP leads to 'STATUS (Cause, CS =N8)' which then leads to 'RESET T304'. OK leads directly to 'RESET T304'. CLR leads to a circle 'F'. RAI leads to 'STATUS (Cause, CS =N25)'. I leads to 'N25 - Overlap Receiving'. Both 'RESET T304' and 'STATUS (Cause, CS =N25)' lead to 'Setup-conf. (3)'. 'Setup-conf. (3)' leads to 'N8 - Connect Request'. 'N25 - Overlap Receiving' also leads to 'N8 - Connect Request'. A reference 'T1163430-94/d090' is at the bottom right.
+
+
+
+Additional procedures related to interworking
+
+\*
+
+(except N0, N1, N11, N12)
+
+See 6.7.1.3
+
+Replace the transition with this one
+
+F
+
+Release-ind.
+(Cause remote)
+
+Release-req.
+(Cause)
+
+CauseR := Cause
+/\*Cause saved\*/
+
+RESET ALL TIMERS
+
+RELEASE (Progress
+Ind #8 "In-band info",
+Cause)
+
+SET (Now + t306,
+timer T306)
+
+See 6.7.1.3
+
+N12 - Release
+Indication
+
+T1175610-95/d091
+
+SDL flowchart for PROCESS Q.2931-N showing the procedure for 'Release initiated by the network with tones & announcements'. The flow starts with a state '\*' (except N0, N1, N11, N12) leading to a 'Release-req. (Cause)' input. This is followed by a task 'CauseR := Cause' with a comment '/\*Cause saved\*/', then 'RESET ALL TIMERS', then a 'RELEASE' output with parameters 'Progress Ind #8 In-band info, Cause', then a 'SET' task for timer T306, and finally entering state 'N12 - Release Indication'. An alternative entry point 'F' leads to 'Release-ind. (Cause remote)' which joins the main flow before 'RESET ALL TIMERS'.
+
+Release initiated by the network with tones & announcements
+
+
+
+Additional procedures related to interworking
+
+Release with tones & announcements
+
+```
+
+graph TD
+ Start((N12 - Release Indication)) -- See 6.7.1.3 --- Note1[ ]
+ Start --> RC[RELEASE-COMPLETE #]
+ Start --> R[RELEASE]
+ Start --> T306[Timeout T306]
+
+ RC --> VM[Verify-Msg]
+ R --> VM
+ VM --> Res{Result}
+
+ Res --> RAP[RAP]
+ Res --> OK[OK]
+ Res --> CLR[CLR]
+ Res --> RAI[RAI]
+ Res --> I[I]
+
+ RAP --> RT306[RESET T306]
+ OK --> RT306
+ CLR --> RT306
+ RAI --> RT306
+ I --> RT306
+
+ RT306 -- See 6.7.1.3 --- Note2[ ]
+ RT306 --> RConf1[Release-conf. Cause, #]
+ RConf1 -- "After receiving this primitive, the Application process shall release the user virtual channel" --- Note3[ ]
+ RConf1 --> End1((X))
+
+ T306 --> C1[Cause 1 := Cause R]
+ C1 --> CO{Cause option}
+ CO --> C2[Cause 2 := 102]
+ C2 --> RC2[RELEASE COMPLETE Cause 1, Cause 2, #]
+ CO --> RC1[RELEASE COMPLETE Cause 1, #]
+
+ RC1 --> RConf2[Release-conf. Cause, #]
+ RC2 --> RConf2
+ RConf2 -- "After receiving this primitive, the Application process shall release the user virtual channel" --- Note4[ ]
+ RConf2 --> End2((X))
+
+```
+
+Flowchart for PROCESS Q.2931-N; showing release procedures. It starts with 'N12 - Release Indication' leading to 'RELEASE-COMPLETE (#)', 'RELEASE', and 'Timeout T306'. 'RELEASE-COMPLETE (#)' leads to 'Verify-Msg' then 'Result' (RAP, OK, CLR, RAI, I). 'Timeout T306' leads to 'Cause 1 := Cause R' then 'Cause option' (Cause 2 := 102). Both paths lead to 'Release-conf. (Cause, #)' with a note about releasing the user virtual channel.
+
+T1165980-94/d092
+
+## A.2 User side SDL diagrams
+
+The User Side SDL diagrams are structured as follows:
+
+| Reference | Length (User Side) |
+|-----------------------------------------------------------------------|----------------------|
+| System diagram ..... | 1 page |
+| Block diagram ..... | 1 page |
+| Co-ord-U process ..... | 10 pages |
+| Reset-Start-U process ..... | 2 pages |
+| Reset-Response-U process ..... | 2 pages |
+| Q.2931-U process: ..... | 31 pages, comprises: |
+| Procedures for B-ISDN calls
(See clause 5) ..... | pp. 1-17 |
+| Extensions for symmetric call operation
(See Annex H) ..... | pp. 18-20 |
+| Additional procedures related to interworking
(See clause 6) ..... | pp. 21-31 |
+
+### SYSTEM Q.2931 – User Side
+
+
+
+A diagram titled 'SYSTEM DIAGRAM – USER SIDE' with a sub-label 'Q.2941 SDL'. It shows a large rectangular box with a smaller, empty rectangular box nested inside its bottom-left corner.
+
+![A block diagram of the Q.2931 system. A central box is labeled 'Q.2931'. Four signal paths are shown: '[SigList-1] FromApplication' enters from the top left, '[SigList-2] ToApplication' exits to the top left, '[SigList-3] FromSAAL' enters from the bottom left, and '[SigList-4] ToSAAL' exits to the bottom left.](7fbdef79403f482e82031e3591c98bc2_img.jpg)
+
+A block diagram of the Q.2931 system. A central box is labeled 'Q.2931'. Four signal paths are shown: '[SigList-1] FromApplication' enters from the top left, '[SigList-2] ToApplication' exits to the top left, '[SigList-3] FromSAAL' enters from the bottom left, and '[SigList-4] ToSAAL' exits to the bottom left.
+
+SigList-1: From-AP
+SigList-2: To-AP
+SigList-3: From-SAAL
+SigList-4: To-SAAL
+
+/\*The signal lists are expanded in the Co-ord-U process diagram\*/
+
+T1165990-94/D093
+
+#### BLOCK Q.2931 – User Side
+
+
+
+The diagram illustrates the internal structure and interfaces of the Q.2931 User Side block. At the center is a block labeled **Co-ord-U (1,1)**. To its left, the **Call Control** interface shows 'From-AP' entering and 'To-AP' exiting the block. Below it, the **Adaptation Layer** interface shows 'From-SAAL' entering and 'To-SAAL' exiting. To the right, three sub-processes are shown in hexagonal blocks:
+
+
+- Q.2931 (0,N)**: Connected via 'CDtoQU' (entering) and 'QutoCD' (exiting) signals. A dotted line also connects the central block to this process.
+- Reset-Start-U (1,1)**: Connected via 'CDtoRS' (entering) and 'RStoCD' (exiting) signals.
+- Reset-Response-U (1,1)**: Connected via 'CDtoRR' (entering) and 'RRtoCD' (exiting) signals.
+
+Diagram of BLOCK Q.2931 – User Side showing the Co-ord-U (1,1) block and its connections to Call Control, Adaptation Layer, Q.2931 (0,N), Reset-Start-U (1,1), and Reset-Response-U (1,1).
+
+Reset processes always present to allow return to REST 0 state –
+
+T1163470-94/d094
+
+#### Q.2931 SDL – User Side
+
+##### Acronyms
+
+#### Processes
+
+| | | |
+|-----------------|---|---------------------------------------------------------------------------------------------------------|
+| Co-ord-U | = | Coordination function for all Q.2931 processes (ASEs) and performs "common" functions on the user side. |
+| Q.2931-U | = | Process that performs the Call/Bearer specific signalling functions. |
+| Reset-Start-U | = | Process that starts the RESTART procedure on the user side. |
+| Reset-Respond-U | = | Process that responds to a RESTART message on the user side. |
+
+##### Others Entities
+
+| | | |
+|------|---|-----------------------------------------|
+| AP | = | Signalling Application Process |
+| SAAL | = | Signalling ATM Adaptation Layer Process |
+
+##### Others
+
+| | | |
+|---------|---|--------------------------------------------------------------------------------------------------|
+| See x.x | = | Reference to relevant Section x.x of Q.2931 |
+| Cause | = | Cause field contents in Cause IE |
+| CS | = | Call State value in Call State IE |
+| # | = | Indicates all IEs in a primitive or message except those explicitly identified (e.g. (Cause. #)) |
+| CLR | = | Release Call |
+| CP | = | Coordination Process |
+| I | = | Ignore |
+| IE | = | Information Element |
+| QU | = | Q.2931-U |
+| RAI | = | Report and Ignore |
+| RAP | = | Report and Proceed |
+| RR | = | Reset-Respond-U |
+| RS | = | Reset-Start-U |
+| OK | = | Okay (proceed) |
+| SC | = | Sending Complete |
+
+The List of IEs possible for each message and the contents of the IEs are defined in clauses 3 and 4.
+
+T1166000-94/d095
+
+Signal lists
+
+Signals for B-ISDN Calls
+
+Primitives to/from SAAL
+
+From-SAAL
+
+AAL-Data.ind. – Includes Message from point-to-point signalling virtual channel connection
+ AAL-ESTABLISH-ind. AAL-ESTABLISH-conf.
+ AAL-RELEASE-ind. AAL-RELEASE-conf.
+
+To-SAAL
+
+AAL-Data.req. – Message sent to specific point-to-point signalling virtual channel connection
+ AAL-ESTABLISH.req. – SAAL link establishment
+ AAL-RELEASE.req. – SAAL link reset or release
+
+Primitives to/from Application Process
+
+From-AP
+
+Setup.req.
+ Proceeding.req.
+ Alerting.req.
+ Setup.resp.
+ Release.req.
+ Release.resp.
+ Reset.req.
+ Reset.resp.
+ Reset-error-response
+ Notify.req.
+ Link Establish-request
+ Link Release-request
+
+To-AP
+
+Setup.ind.
+ Proceeding.ind.
+ Alerting.ind.
+ Setup.conf.
+ Setup-complete.ind.
+ Release.ind.
+ Release.conf.
+ Reset.ind.
+ Reset.conf.
+ Reset-error-indication
+ Status.ind.
+ Notify.ind.
+ Link Establish-conf.
+ Link Release-conf.
+
+Signal lists
+
+Additional signals related to interworking
+
+Primitives to/from Application Process
+
+From-AP
+
+More-info.req.
+ Info.req.
+ Progress.req.
+
+To-AP
+
+More-info.ind.
+ Info.ind.
+ Progress.ind.
+
+Signal lists
+
+Additional signals related to Supplementary Services
+
+Primitives to/from Application Process
+
+From-AP
+
+*These primitives are listed in the relevant broadband supplementary service Recommendations (Q.295 x-Series).*
+
+To-AP
+
+##### Primitives to/from Q.2931-U
+
+##### Signal lists
+
+##### CDtoQU
+
+##### QUtoCD
+
+| | |
+|---------------------------|------------------------|
+| Setup-req. | Setup-ind. |
+| Proceeding-req. | Proceeding-ind. |
+| Alerting-req. | Alerting-ind. |
+| Setup-resp. | Setup-conf. |
+| | Setup-complete-ind. |
+| Release-req. | Release-ind. |
+| Release-resp. | Release-conf. |
+| | Status-ind. |
+| Notify-req. | Notify-ind. |
+| Link Establish confirm | Link Establish request |
+| Link Establish indication | |
+| Link Release indication | |
+| Link Establish error | |
+
+##### Primitives to/from Reset-Start-U
+
+##### Signal lists
+
+##### CDtoRS
+
+##### RStoCD
+
+| | |
+|------------|------------------|
+| Reset-req. | Reset-error-ind. |
+| | Reset-conf. |
+
+##### Primitives to/from Reset-Respond-U
+
+##### Signal lists
+
+##### CDtoRR
+
+##### RRtoCD
+
+| | |
+|-------------------|------------------|
+| Reset resp. | Reset-ind. |
+| Reset-error-resp. | Reset-error-ind. |
+
+##### Additional Primitives to/from Q.2931-U related to interworking
+
+##### Signal lists
+
+##### CDtoQU
+
+##### QUtoCD
+
+| | |
+|----------------|----------------|
+| More-info-req. | More-info-ind. |
+| | Timeout-ind. |
+| Info-req. | Info-ind. |
+| Progress-req. | Progress-ind. |
+
+##### Additional Primitives to/from Q.295x related to supplementary services
+
+##### Signal lists
+
+##### CDtoQU
+
+##### QUtoCD
+
+*These primitives are listed in the relevant broadband supplementary service Recommendations (Q.295 x-Series).*
+
+##### Messages to/from Q.2931-U for B-ISDN calls
+
+##### Signal lists
+
+##### CDtoQU
+
+##### QUtoCD
+
+| | |
+|------------------|------------------|
+| SETUP | SETUP |
+| CALL-PROCEEDING | CALL-PROCEEDING |
+| ALERTING | ALERTING |
+| CONNECT | CONNECT |
+| CONNECT-ACK | CONNECT-ACK |
+| RELEASE | RELEASE |
+| RELEASE-COMPLETE | RELEASE-COMPLETE |
+| STATUS | STATUS |
+| STATUS-ENQUIRY | STATUS-ENQUIRY |
+| NOTIFY | NOTIFY |
+
+##### Messages to/from Reset-Start-U
+
+##### Signal lists
+
+##### CDtoRS
+
+##### RStoCD
+
+| | |
+|-------------|---------|
+| RESTART-ACK | RESTART |
+| | STATUS |
+
+##### Messages to/from Reset-Respond-U
+
+##### Signal lists
+
+##### CDtoRR
+
+##### RRtoCD
+
+| | |
+|---------|-------------|
+| RESTART | RESTART-ACK |
+| | STATUS |
+
+##### Additional Messages to/from Q.2931-U related to interworking
+
+##### Signal lists
+
+##### CDtoQU
+
+##### QUtoCD
+
+| | |
+|-------------------|-------------------|
+| SETUP-ACKNOWLEDGE | SETUP-ACKNOWLEDGE |
+| INFORMATION | INFORMATION |
+| PROGRESS | PROGRESS |
+
+##### Additional Messages to/from Q.295x related to Supplementary Services
+
+##### Signal lists
+
+##### CDtoQU
+
+##### QUtoCD
+
+*These primitives are listed in the relevant broadband supplementary service Recommendations (Q.295 x-Series).*
+
+T1163500-94/d097
+
+
+
+```
+
+graph TD
+ subgraph Procedures
+ CheckMsg["Check-Msg (#)"]
+ BuildMsg["Build-MSG (#)"]
+ ImplSpec["Implementation specific procedure declarations"]
+ CheckMsg --- ImplSpec
+ BuildMsg --- ImplSpec
+ end
+
+ CU0["CU0 - AAL Connection Released"]
+ AAL_Est_Box["AAL Establishment handling at the Q.2931-SAAL layer boundary (see Q.2130)"]
+
+ CU0 --- Ref1["See 5.1, 5.6.9, 5.6.10"]
+
+ CU0 --> SetupReqAP["Setup-req. /*From AP*/"]
+ CU0 --> ResetReqAP["Reset-req. /*From AP*/"]
+ CU0 --> LinkEstReq["Link Establish request"]
+ CU0 --> TimeoutT309_1["Timeout T309"]
+ CU0 --> ConnX1((X))
+
+ SetupReqAP --> Q2931U_1["Q.2931-U"]
+ Q2931U_1 --> SetupReqTo["Setup-req/*To Q.2931-U*/"]
+
+ ResetReqAP --> ResetReqTo["Reset-req. (#) /*To Reset-Start-U*/"]
+
+ LinkEstReq --> AAL_Est_Req["AAL ESTABLISH request"]
+ AAL_Est_Req --> ToSAAL["To SAAL"]
+ AAL_Est_Req --> ActiveT309{ACTIVE T309}
+
+ ActiveT309 -- Yes --> CU1
+ ActiveT309 -- No --> SetTimer["SET (Now +t309, Timer T309)"]
+ SetTimer --> CU1
+
+ TimeoutT309_1 --> LinkEstErr1["Link Establish error"]
+ LinkEstErr1 --> CU0
+ LinkEstErr1 -.-> ToQ2931U_All1["To Q.2931-U (all)"]
+
+ ConnX1 --> ConnX2((X))
+ ConnX2 --> AALEstInd["AAL Establish indication"]
+ AALEstInd --> LinkEstInd["Link Establish indication"]
+ LinkEstInd --> CU3["CU3 - AAL Connection Established"]
+
+ CU1["CU1 - AAL Awaiting Establish"]
+
+ CU1 --> MsgHash["Message (#) /*From Q.2931-U Reset-Start-U or Reset-Respond-U*/"]
+ CU1 --> TimeoutT309_2["Timeout T309"]
+ CU1 --> AALEstConf["AAL-ESTABLISH confirm"]
+ CU1 --> AALRelInd["AAL-RELEASE indication"]
+
+ MsgHash --> LinkEstErr2["Link Establish error"]
+ TimeoutT309_2 --> LinkEstErr2
+ LinkEstErr2 --> CU0
+ LinkEstErr2 -.-> ToQ2931U_All2["To Q.2931-U (all)"]
+
+ AALEstConf --> ResetT309["RESET T309"]
+ ResetT309 --> LinkEstConf["Link Establish confirm"]
+ LinkEstConf --> CU3
+ LinkEstConf -.-> ToQ2931U_AP["To Q.2931-U (all) and AP"]
+
+ AALRelInd --> LinkRelInd["Link Release indication"]
+ LinkRelInd --> CU0
+ LinkRelInd -.-> ToQ2931U_All3["To Q.2931-U (all)"]
+
+```
+
+The diagram describes the coordination process for AAL establishment. It begins at state **CU0 - AAL Connection Released**. Various inputs like *Setup-req*, *Reset-req*, or *Link Establish request* trigger transitions. A *Link Establish request* leads to an **AAL ESTABLISH request** sent to the SAAL. If timer T309 is not active, it is set, and the process enters state **CU1 - AAL Awaiting Establish**. From CU1, receiving an **AAL-ESTABLISH confirm** resets T309 and moves the process to **CU3 - AAL Connection Established**. Errors or timeouts during establishment return the process to state CU0.
+
+SDL state transition diagram for AAL Establishment handling.
+
+T1163510-94/d098
+
+
+
+The diagram illustrates the state transitions for the Co-ord-U process. It features three main states represented by ovals: 'CU3 - AAL Connection Established' (top), 'CU2 - AAL Awaiting Release' (middle left), and 'CU0 - AAL Connection Released' (bottom left). Transitions are shown as rectangles with chevron-like shapes on their sides. Dashed lines represent requests from the AP, while solid lines represent indications and confirmations. The diagram is organized into three horizontal tracks: 'From AP' (top), 'To SAAL' (middle), and 'To Q.2931-U (all)' (bottom right). The top track shows a sequence of messages: 'Link Release request' (From AP), 'AAL-RELEASE indication', 'AAL-ESTABLISH indication', and 'AAL-ESTABLISH confirm' (To SAAL). The middle track shows 'AAL-RELEASE request' (To SAAL), 'Link Release indication', 'Link ESTABLISH indication', and 'Link ESTABLISH confirm' (To Q.2931-U). The bottom track shows 'AAL - RELEASE confirm', 'Link Release confirm' (leading to CU0 - AAL Connection Released), 'Link Establish request' (From AP), 'Link Establish confirm' (To AP), and 'CU3 - AAL Connection Established'.
+
+State transition diagram for PROCESS Co-ord-U showing AAL connection states and transitions between AP, SAAL, and Q.2931-U entities.
+
+T1166010-94/d099
+
+
+
+```
+
+graph TD
+ Start([CU3 - AAL Connection Established]) --> P1[/"Primitive" /From AP*/]
+ Start --> P2[/"AAL-DATA-ind. (#) /From SAAL*/]
+ Start --> P3[/"Primitive" /From Q.2931-U, Reset-Start-U or Reset-Respond-U*/]
+ Start --> P4[/"Message (#) /From Q.2931-U, Reset-Start-U or Reset-Respond-U*/]
+
+ P1 --> W((W))
+ W --- W_text[To application primitive handling procedures]
+
+ P2 --> CM[Check-Msg (#)]
+ CM --- CM_text[See 5.6.1, 5.6.2, 5.6.3]
+ CM --> Q2931{Q.2931 Protocol Discriminator}
+ Q2931 -- No --> CU3_Established_1([CU3 - AAL Connection Established])
+ Q2931 -- Yes --> ML{Message Length <9 octets}
+ ML -- Yes --> CU3_Established_1
+ ML -- No --> VCRF{Valid Call Reference format}
+ VCRF -- No --> CU3_Established_1
+ VCRF -- Yes --> CRD{Call Reference = Dummy}
+ CRD -- Yes --> CU3_Established_1
+ CRD -- No --> CRG{Call Reference = Global}
+ CRG -- Yes --> X((X))
+ X --- X_text[To Global Call Reference Procedures]
+ CRG -- No --> CR{Call Reference recognized}
+ CR --- CR_text[Does not include check of Call Reference Flag]
+ CR -- No --> Z((Z))
+ Z --- Z_text[To "No Protocol" Procedures]
+ CR -- Yes --> Y((Y))
+ Y --- Y_text[To Protocol Related Procedures]
+
+ P3 --> P3_T[/"Primitive" /To AP*/]
+ P3_T --> CU3_Established_2([CU3 - AAL Connection Established])
+
+ P4 --> BM[Build-M (#)]
+ BM --> P4_T[/"AAL-DATA-req (#) /To SAAL*/]
+ P4_T --> CU3_Established_3([CU3 - AAL Connection Established])
+
+ Note1[See 5.1, 5.2, 5.1.1, 5.2.1] -.-> Start
+
+```
+
+Flowchart for PROCESS Co-ord-U. It starts with 'CU3 - AAL Connection Established' and branches into four main paths based on input type: 'Primitive' from AP, 'AAL-DATA-ind' from SAAL, 'Primitive' from Q.2931-U, and 'Message' from Q.2931-U. The 'AAL-DATA-ind' path includes a series of decision diamonds for protocol discriminator, message length, call reference format, dummy status, global status, and recognition, leading to various procedure calls (W, X, Y, Z).
+
+T1166020-94/d100
+
+
+
+```
+
+graph TD
+ Start((X)) --> GT[Global Call Reference Procedures]
+ GT --> MT{Message Type}
+ MT --> MT_Ref[See 5.5, 5.6.3.2 e), 5.6.12]
+ MT --> OTHER[OTHER (#)]
+ MT --> RESTART[RESTART (#)]
+ MT --> RESTART_ACK[RESTART-ACKNOWLEDGE (#)]
+ MT --> STATUS[STATUS (#)]
+
+ OTHER --> C81[Cause: = 81, CS: = 0]
+ C81 --> BuildMsg[Build-Msg (STATUS Cause, CS, #)]
+ BuildMsg --> AALData[AAL-DATA.req. (#) /To SAAL*/]
+ AALData --> CU3_1(CU3 - AAL Connection Established)
+
+ RESTART --> CRF0{Call Reference Flag = 0}
+ CRF0 -- No --> OTHER
+ CRF0 -- Yes --> RESTART_MSG[RESTART (#) /To Reset-Respond-U*/]
+ RESTART_MSG --> CU3_2(CU3 - AAL Connection Established)
+
+ RESTART_ACK --> CRF0Q{Call Reference Flag = 0?}
+ CRF0Q -- No --> RESTART_ACK_MSG[RESTART ACKNOWLEDGE (#) /To Reset-Start-U*/]
+ RESTART_ACK_MSG --> CU3_3(CU3 - AAL Connection Established)
+
+ STATUS --> CRF0S{Call Reference Flag = 0?}
+ CRF0S -- Yes --> STATUS_RESP[STATUS (#) /To Reset-Respond-U*/]
+ CRF0S -- No --> STATUS_START[STATUS (#) /To Reset-Start-U*/]
+ STATUS_RESP --> CU3_4(CU3 - AAL Connection Established)
+ STATUS_START --> CU3_4
+
+```
+
+Flowchart for Process Co-ord-U showing message handling logic for OTHER, RESTART, RESTART-ACKNOWLEDGE, and STATUS messages, including decision points for Call Reference Flag and resulting actions like AAL-DATA.req or CU3 - AAL Connection Established.
+
+T1175620-95/d101
+
+
+
+```
+graph TD; Z((Z)) --> MT{Message Type}; Z -.-> NP["No Protocol Procedures"]; MT -.-> MT_REF["See 5.6.3.2 a), b), c), f), g), 5.6.11"]; MT --> S[SETUP (#)]; MT --> RC[RELEASE-COMPLETE (#)]; MT --> O[OTHER (#)]; MT --> ST[STATUS (#)]; MT --> SE[STATUS-ENQUIRY (#)]; S --> CRF{Call Reference flag = 0}; CRF -- No --> RC; CRF -- Yes --> Q2931U[Q.2931-U]; Q2931U --> S_TO_Q2931U[SETUP (#) /*To Q.2931-U*/]; S_TO_Q2931U --> CU3_SE1([CU3 - AAL Connection Established]); RC --> CU3_SE2([CU3 - AAL Connection Established]); O --> C81[Cause := 81]; C81 --> BM_RC["Build-Msg (RELEASE-COMPLETE. Cause #)"]; BM_RC --> ADR_O["AAL-DATA.req. (#) /*To SAAL*/"]; ADR_O --> CU3_SE3([CU3 - AAL Connection Established]); ST --> CS0{CS = 0}; CS0 -- Yes --> SE; CS0 -- No --> C101[Cause := 101]; C101 --> BM_RC; SE --> C30["Cause := 30; CS := 0"]; C30 --> BM_SE["Build-Msg (STATUS CS, Cause #)"]; BM_SE --> ADR_SE["AAL-DATA.req. (#) /*To SAAL*/"]; ADR_SE --> CU3_SE4([CU3 - AAL Connection Established]);
+```
+
+Flowchart for Message Type handling in PROCESS Co-ord-U. It branches into SETUP (#), RELEASE-COMPLETE (#), OTHER (#), STATUS (#), and STATUS-ENQUIRY (#). Each branch has specific logic for handling the message, such as setting cause codes (81, 101, 30) or building specific messages (Q.2931-U, RELEASE-COMPLETE, STATUS).
+
+T1166040-94/d102
+
+
+
+```
+
+graph TD
+ Y((Y)) -- "Protocol Procedures" --- MT{Message Type}
+ MT -- "SETUP (#)" --> M[Message (#)
+/*To Q.2931-U*/]
+ MT -- "Other" --> M
+ M --> CU3([CU3 - AAL
+Connection
+Established])
+ Note1[SETUP
+with active
+call reference
+is ignored] -.- SETUP_PATH[SETUP (#)]
+
+```
+
+Flowchart for PROCESS Co-ord-U; page 9 of (10).
+
+T1166050-94/d103
+
+
+
+```
+
+graph TD
+ W((W)) -- "Application
+primitive handling
+procedures" --- PT{Primitive Type}
+ PT -.- Note2[See 5.1.1, 5.5.1]
+ PT --- AOP[All other primitives]
+ PT --- SRQ[Setup-req.]
+ PT --- RRS[Reset-resp.]
+ PT --- RRQ[Reset-req.]
+ PT --- RER[Reset-error-resp.]
+
+ AOP --> P1["Primitive" /*To
+Q.2931-U*/]
+ P1 --> CU3_1([CU3 - AAL
+Connection
+Established])
+
+ SRQ --> Q[Q.2931-U]
+ Q --> SR2[Setup-req.
+/*To Q.2931-U*/]
+ SR2 --> CU3_2([CU3 - AAL
+Connection
+Established])
+
+ RRS --> RR1[Reset-resp. (#)
+/*To Reset-
+response-U*/]
+ RRQ --> RR2[Reset-req. (#)
+/*To Reset-
+Start-U*/]
+ RER --> RR3[Reset-resp. (#)
+/*To Reset-
+response-U*/]
+
+ RR1 --> CU3_3([CU3 - AAL
+Connection
+Established])
+ RR2 --> CU3_3
+ RR3 --> CU3_3
+
+```
+
+Flowchart for PROCESS Co-ord-U; page 10 of (10).
+
+T1166060-94/d104
+
+
+
+```
+
+graph TD
+ Entry(( )) -.->|See 5.5.1| RestU0Null1([Rest-U0 - Null])
+ RestU0Null1 --> ResetReq{Reset.req
+(Restart indicator,
+Connection identifier)}
+ ResetReq -.->|Connection identifier = null is valid| ConnectIDs[ConnectIDs :=
+Connection identifier,
+Timeouts := 0]
+ ConnectIDs --> RESTART[/RESTART (Restart Indicator, Connection identifier)/]
+ RESTART --> SET[SET (Now + t316,
+timer T316)]
+ SET --> RestU1Request1([Rest-U1 - Restart Request])
+ RestU1Request1 --> RestU1Request2([Rest-U1 - Restart Request])
+ RestU1Request2 --> TimeoutT316[/Timeout T316/]
+ TimeoutT316 --> TimeoutsInc[Timeouts :=
+Timeouts + 1]
+ TimeoutsInc --> TimeoutsRSN{Timeouts = RSN}
+ TimeoutsRSN -- Yes --> Reason[Reason :=
+NoResponse]
+ Reason --> ResetErrorInd[/Reset-error.ind.
+(Reason)/]
+ ResetErrorInd -.->|VC/VP in Connection identifier should be placed in an out-of-service maintenance condition| RestU0Null2([Rest-U0 - Null])
+ TimeoutsRSN -- No --> RESTART
+ TimeoutsRSN -.->|RSN = Number of RESTART's sent. Implementation dependent value: Default = 2| RestU0Null2
+ VerifyMsg[Verify-Msg] -.->|See 5.6, 5.7, 5.8| RestU0Null2
+
+```
+
+Flowchart for PROCESS Reset-Start-U. The process starts with an entry point (See 5.5.1) leading to 'Rest-U0 - Null'. It then checks 'Reset.req' with 'Connection identifier = null is valid'. If valid, it initializes 'ConnectIDs' and sends a 'RESTART' message, starting timer 'T316' and leading to 'Rest-U1 - Restart Request'. If not valid, it sends 'Rest-U1 - Restart Request', waits for 'Timeout T316', increments 'Timeouts', and checks if 'Timeouts = RSN'. If 'Yes', it sets 'Reason := NoResponse', sends 'Reset-error.ind.', and returns to 'Rest-U0 - Null'. If 'No', it loops back to the 'RESTART' message step. External references include 'Verify-Msg' (See 5.6, 5.7, 5.8), 'RSN' (Default = 2), and 'VC/VP' placement in out-of-service conditions.
+
+T1166070-94/d105
+
+
+
+```
+
+graph TD
+ Start([Rest-U1 - Restart Request]) --> Note1[See 5.6.12, 5.5.1]
+ Start --> StatusL[Status (Cause CS)]
+ Start --> AckR[RESTART-ACKNOWLEDGE (Restart indicator, Connection identifier)]
+ StatusL --> VerifyL[Verify message]
+ AckR --> VerifyR[Verify-Msg]
+ VerifyL --> ResultL{Result}
+ VerifyR --> ResultR{Result}
+ ResultL --> RAPL[RAP]
+ ResultL --> OKL[OK]
+ ResultL --> CLRL[CLR]
+ ResultL --> RAIL[RAI]
+ ResultL --> IL[I]
+ ResultR --> RAPR[RAP]
+ ResultR --> OKR[OK]
+ ResultR --> CLRR[CLR]
+ ResultR --> RAIR[RAI]
+ ResultR --> IR[I]
+ RAPL --> StatusCSL[Status (Cause, CS)]
+ StatusCSL --> CSCompat{CS Compatible}
+ OKL --> RestU0NullL([Rest-U0 - Null])
+ CLRL --> RestU0NullL
+ RAIL --> StatusCSRL[Status (Cause, CS)]
+ IL --> StatusCSRL
+ StatusCSRL --> CSCompat
+ RAPR --> STATUSCS[STATUS (Cause, CS)]
+ STATUSCS --> ConnID{Connection identifier ConnectIDS}
+ Note2[Connection identifier = null is valid] -.-> ConnID
+ OKR --> ConnID
+ CLRR --> RestU0NullR([Rest-U0 - Null])
+ RAIR --> STATUSCSRestU1[STATUS (Cause, CS) Rest-U1]
+ IR --> STATUSCSRestU1
+ STATUSCSRestU1 --> RestU1RestartR([Rest-U1 - Restart Request])
+ CSCompat -- No --> Reason[Reason := Peer-incompatible State]
+ Reason --> ResetError[Reset-error-ind. (Reason)]
+ ResetError --> RestU1RestartL([Rest-U1 - Restart Request])
+ CSCompat -- Yes --> ImplProc[Implementation dependent procedure]
+ ImplProc --> RestartAck[RESTART ACKNOWLEDGE with mis-matched connection identification ignored]
+ RestartAck --> RestU1RestartL
+ ConnID -- No --> RestU1RestartR
+ ConnID -- Yes --> ResetT316[RESET T316]
+ ResetT316 --> ResetConf[Reset conf. (Restart indicator, Connection identifier)]
+ ResetConf --> RestU0NullR
+
+```
+
+Flowchart for PROCESS Reset-Start-U. It starts with 'Rest-U1 - Restart Request' leading to two parallel paths. The left path uses 'Status (Cause CS)' and 'Verify message' to check 'Result'. The right path uses 'RESTART-ACKNOWLEDGE' and 'Verify-Msg' to check 'Result'. Both paths lead to decision diamonds for RAP, OK, CLR, RAI, and I. The left path's OK leads to 'Rest-U0 - Null', while RAP, CLR, RAI, and I lead to 'Status (Cause, CS)' which then leads to 'CS Compatible'. The right path's OK leads to 'Connection identifier ConnectIDS', while RAP, CLR, RAI, and I lead to 'STATUS (Cause, CS) Rest-U1' which leads to 'Rest-U1 - Restart Request'. 'CS Compatible' leads to 'Reason := Peer-incompatible State' (No) or 'Implementation dependent procedure' (Yes), both leading to 'Rest-U1 - Restart Request'. 'Connection identifier ConnectIDS' leads to 'RESET T316' (Yes) or 'Rest-U1 - Restart Request' (No). 'RESET T316' leads to 'Reset conf.' which leads to 'Rest-U0 - Null'. A note 'See 5.6.12, 5.5.1' is near the start, and 'Connection identifier = null is valid' is near the 'Connection identifier ConnectIDS' decision.
+
+T1166080-94/d106
+
+PROCESS Reset-Response-U;
+ page 1 of (2)
+
+
+```
+
+ graph TD
+ Start1([ ]) --> StateU0([Rest-U0 - Null])
+ StateU0 --> InputRestart1[/RESTART
+Restart indicator,
+Connection
+identifier/]
+ InputRestart1 --> TaskVerify1[[Verify-Msg]]
+ TaskVerify1 --> DecisionResult{Result}
+
+ DecisionResult -- RAP --> OutputStatus1>STATUS
+Cause, CS
+Rest-U2<]
+ DecisionResult -- OK --> InputResetInd[/Reset ind.
+Restart indicator,
+Connection
+identifier/]
+ DecisionResult -- I --> InputResetInd
+ DecisionResult -- CLR --> InputResetInd
+ DecisionResult -- RAI --> OutputStatus2>STATUS
+Cause, CS
+= Rest-U0<]
+
+ OutputStatus2 --> StateU0
+ InputResetInd --> TaskSet[SET
+Now + t317,
+timer T317]
+ TaskSet --> StateU2([Rest-U2 - Restart])
+
+ Start2[[Verify-Msg]] --> Note1[See 5.6, 5.7, 5.8]
+
+ StateU2_2([Rest-U2 - Restart]) --> InputResetErr[/Reset-error-resp.
+Cause := 82/]
+ StateU2_2 --> InputRestart2[/RESTART
+Restart indicator,
+Connection
+identified/]
+
+ InputResetErr --> DecisionStatus{STATUS
+Option
+supported}
+ DecisionStatus -- No --> Join1
+ DecisionStatus -- Yes --> OutputStatus3>STATUS
+Cause, Rest-U2<]
+ OutputStatus3 --> Join1(( ))
+
+ InputRestart2 --> TaskCause[Cause := 101; CS :=
+Rest-U2]
+ TaskCause --> Join1
+ Join1 --> StateU2_2
+
+```
+
+SDL diagram for PROCESS Reset-Response-U
+
+See 5.5.2
+
+ Connection
+identifier =
+null is valid
+
+ timer value
+implementation
+dependent
+
+Handling second
+reception of
+RESTART
+
+Verify-Msg
+
+This procedure verifies messages
+based on the Current State and Q.2931,
+clauses 4 and 5 rules. It removes unaccep-
+table IEs and returns the result in the
+Result and Cause variables
+
+Result abbreviations:
+
+| | | |
+|-----|---|--------------------|
+| RAI | - | Report and Ignore |
+| RAP | - | Report and Proceed |
+| I | - | Ignore |
+| CLR | - | Release Call |
+| OK | - | OK (proceed) |
+
+T1175630-95/d107
+
+ 178 **Recommendation Q.2931 (02/95)**
+
+PROCESS Reset-Response-U;
+
+page 2 of (2)
+
+
+
+```
+
+graph TD
+ Start([Rest-U2 - Restart]) --> Branch1{ }
+ Branch1 --> StatusIn[/STATUS (Cause CS)/]
+ Branch1 --> ResetResp[/Reset-resp.
(Restart indicator,
Connection
identifier)/]
+ Branch1 --> Timeout[/Timeout T317/]
+
+ StatusIn --> Verify[Verify message]
+ Verify --> Result{Result}
+
+ Result -- RAP --> StatusOut[/STATUS
(Cause, CS)/]
+ Result -- OK --> Join1(( ))
+ Result -- CLR --> Null1([Rest-U0-Null])
+ Result -- RAI --> StatusOut2[/STATUS
(Cause, CS)/]
+ Result -- I --> Join1
+
+ ResetResp --> ResetT317[RESET T317]
+ ResetT317 --> RestartAck[/RESTART-ACKNOWLEDGE
(Restart indicator,
Connection
identifier)/]
+ RestartAck --> Null2([Rest-U0 - Null])
+
+ Timeout --> ReasonNoReset[Reason := No-reset-conf.]
+ ReasonNoReset --> ResetErrorIn[/Reset-error-in.
(Reason)/]
+ ResetErrorIn --> Null3([Rest-U0 - Null])
+
+ StatusOut --> Join1
+ StatusOut2 --> Join1
+ Join1 --> CSComp{CS Compatible}
+
+ CSComp -- No --> ReasonPeer[Reason := Peer-
Incompatible State]
+ ReasonPeer --> ResetErrorIn2[/Reset-error-in.
(Reason)/]
+ ResetErrorIn2 --> RestartState([Rest-U2 - Restart])
+
+ CSComp -- Yes --> ImpDep[Implementation
dependent
procedure]
+
+```
+
+See 5.6.12, 5.5.2
+
+Connection identifier = null is valid
+
+T1166100-94/d108
+
+Flowchart for PROCESS Reset-Response-U; showing state transitions from Rest-U2 - Restart based on STATUS, Reset-resp, or Timeout T317 messages.
+
+**Recommendation Q.2931 (02/95)** 179
+
+
+
+```
+
+graph TD
+ Start([Procedures for B-ISDN Calls])
+ VerifyMsgProc[[Verify-Msg]] --- Ref1[See 5.6, 5.7, 5.8]
+ U0((U0 - Null)) --- Ref2[See 5.1.1, 5.2.1]
+
+ U0 --> SetupIn{{SETUP (#)}}
+ U0 --> SetupReq{{Setup-req (#)}}
+
+ SetupIn --> VerifyMsg[[Verify-Msg]]
+ VerifyMsg --> Result{Result}
+
+ Result -- RAP --> StatusU6{{STATUS
(Cause, CS = U6)}}
+ Result -- OK --> SetupInd{{Setup-ind. (#)}}
+ Result -- CLR --> RelComp{{RELEASE
COMPLETE
(Cause. #)}}
+ Result -- RAI --> StatusU0{{STATUS
(Cause, CS = U0)}}
+ Result -- I --> U0_2((U0 - Null))
+
+ StatusU6 --> SetupInd
+ SetupInd --> U6((U6 - Call Present))
+ RelComp --> EndX((X))
+ StatusU0 --> U0_3((U0 - Null))
+
+ SetupReq --> SetupOut{{SETUP (#)}}
+ SetupOut --> SetTimer[SET (Now+ t303,
timer T303);
Timeout := 0]
+ SetTimer --> U1((U1 - Call Initiated))
+
+```
+
+T1166110-94/d109
+
+SDL Flowchart for B-ISDN Call Procedures
+
+
+
+```
+graph TD; U1((U1 - Call Initiated)) --> Note1[See 5.1.1, 5.1.5]; U1 --> CP{CALL-PROCEEDING (#)}; U1 --> T303{Timeout T303}; CP --> VM[Verify-Msg]; VM --> R{Result}; R -- RAP --> S3[STATUS (Cause, CS = U3)]; R -- OK --> RESET[RESET T303]; R -- CLR --> D((D)); R -- RAI --> S1[STATUS (Cause, CS = U1)]; R -- I --> U1; S3 --> RESET; S1 --> U1; RESET --> PI{Proceeding-ind. (#)}; PI --> SET310[SET (Now + t310, timer T310);]; SET310 --> U3((U3 - Outgoing Call Proceeding)); T303 --> T1{Timeout = 1}; T1 -- Yes --> RC[Release-conf.]; T1 -- No --> SETUP{SETUP (#)}; SETUP --> SET303[SET (Now + t303, timer T303); Timeout := 1]; SET303 --> U1; Note2[The Application process should implement a delay before releasing the Call Reference] -.-> RC; T1163630-94/d110 -.-> RC;
+```
+
+Flowchart for Process Q.2931-U, starting with 'U1 - Call Initiated'. It branches into 'CALL-PROCEEDING (#)' and 'Timeout T303'. The 'CALL-PROCEEDING' path leads to 'Verify-Msg', then 'Result', which branches into RAP, OK, CLR, RAI, and I. The 'Timeout T303' path leads to 'Timeout = 1' decision, then 'SETUP (#)', 'SET (Now + t303, timer T303); Timeout := 1', and finally 'U1 - Call Initiated'.
+
+
+
+```
+graph TD; U3((U3 - Outgoing Call Proceeding)) --> L[See 5.1.6, 5.1.7]; U3 --> A[ALERTING (#)]; U3 --> C[CONNECT (#)]; U3 --> T[Timeout T310]; A --> VM1[Verify-Msg]; VM1 --> R1{Result}; R1 --> RAP1[RAP]; R1 --> OK1[OK]; R1 --> CLR1[CLR]; R1 --> RAI1[RAI]; R1 --> I1[I]; RAP1 --> STATUS_U4[STATUS (Cause, CS = U4)]; STATUS_U4 --> RESET_T310_1[RESET T310]; RESET_T310_1 --> Alerting_ind[Alerting-ind. (#)]; Alerting_ind --> U4((U4 - Call Delivered)); CLR1 --> D1((D)); RAI1 --> STATUS_U3_1[STATUS (Cause, CS = U3)]; STATUS_U3_1 --> U3_1((U3 - Outgoing Call Proceeding)); I1 --> STATUS_U3_1; C --> VM2[Verify-Msg]; VM2 --> R2{Result}; R2 --> RAP2[RAP]; R2 --> OK2[OK]; R2 --> CLR2[CLR]; R2 --> RAI2[RAI]; R2 --> I2[I]; RAP2 --> STATUS_U10[STATUS (Cause, CS = U10)]; STATUS_U10 --> RESET_T310_2[RESET T310]; RESET_T310_2 --> Setup_conf[Setup-conf. (#)]; Setup_conf --> CONNECT_ACK[CONNECT ACKNOWLEDGE (#)]; CONNECT_ACK --> U10((U10 - Active)); CLR2 --> D2((D)); RAI2 --> STATUS_U3_2[STATUS (Cause, CS = U3)]; STATUS_U3_2 --> U3_2((U3 - Outgoing Call Proceeding)); I2 --> STATUS_U3_2; T --> Cause_102[Cause := 102]; Cause_102 --> D3((D));
+```
+
+State transition diagram for U3 - Outgoing Call Proceeding. It branches into ALERTING (#), CONNECT (#), and Timeout T310. The ALERTING path leads to Verify-Msg, then Result, then branches based on RAP, OK, CLR, RAI, and I. The CONNECT path leads to Verify-Msg, then Result, then branches based on RAP, OK, CLR, RAI, and I. The Timeout T310 path leads to Cause := 102, then D. The diagram includes states like U4 - Call Delivered, U3 - Outgoing Call Proceeding, and U10 - Active.
+
+T1163640-94/d111
+
+
+
+```
+graph TD; U4_1([U4 - Call Delivered]) --> CONNECT1[/CONNECT (#)/]; CONNECT1 --> VERIFY[Verify-Msg]; VERIFY --> RESULT{Result}; RESULT -- RAP --> STATUS_U10[/STATUS (Cause, CS = U10)/]; STATUS_U10 --> U4_2([U4 - Call Delivered]); RESULT -- OK --> SETUP_CONF[/Setup-conf. (#)/]; SETUP_CONF --> CONNECT_ACK[/CONNECT ACKNOWLEDGE (#)/]; CONNECT_ACK --> U10([U10 - Active]); RESULT -- CLR --> D((D)); RESULT -- RAI --> STATUS_U4[/STATUS (Cause, CS = U4)/]; STATUS_U4 --> U4_2; RESULT -- I --> RESULT; U4_1 -.-> Note1[See 5.1.7]; Note2[T1163650-94/d112];
+```
+
+Flowchart for PROCESS Q.2931-U; showing call delivery logic. It starts with 'U4 - Call Delivered' (See 5.1.7), followed by 'CONNECT (#)', 'Verify-Msg', and a 'Result' decision. The 'Result' decision has five paths: RAP leads to 'STATUS (Cause, CS = U10)'; OK leads to 'Setup-conf. (#)'; CLR leads to connector 'D'; RAI leads to 'STATUS (Cause, CS = U4)'; I loops back to the 'Result' decision. Both 'STATUS' blocks lead to 'U4 - Call Delivered'. 'Setup-conf. (#)' leads to 'CONNECT ACKNOWLEDGE (#)', which leads to 'U10 - Active'. A note 'T1163650-94/d112' is present near the bottom right.
+
+
+
+This flowchart illustrates the state transitions for the U6 - Call Present state. The initial state is U6 - Call Present, which is associated with sections 5.2.2.1, 5.2.2.2, 5.2.4, 5.2.5.1, and 5.4.2. From this state, four possible transitions are shown: Release-resp. (cause), Proceeding-req. (#), Setup-resp. (#), and Alerting-req. (#). The Release-resp. (cause) transition leads to the RELEASE-COMPLETE (Cause) state, which then leads to an exit. The Proceeding-req. (#) transition leads to the CALL-PROCEEDING (#) state, which then leads to the U9 - Incoming Call Proceeding state. The Setup-resp. (#) transition leads to the CONNECT (#) state, which then leads to the SET (NOW + t313, timer T313) state, which then leads to the U8 - Connect Request state. The Alerting-req. (#) transition leads to the ALERTING (#) state, which then leads to the U7 - Call Received state.
+
+```
+graph TD; U6((U6 - Call Present)) -->|See 5.2.2.1, 5.2.2.2, 5.2.4, 5.2.5.1, 5.4.2| T1[ ]; T1 -->|Release-resp. (cause)| RC[RELEASE-COMPLETE (Cause)]; RC --> X[ ]; T1 -->|Proceeding-req. (#)| CP[CALL-PROCEEDING (#)]; CP --> U9((U9 - Incoming Call Proceeding)); T1 -->|Setup-resp. (#)| C[CONNECT (#)]; C --> SET[SET (NOW + t313, timer T313)]; SET --> U8((U8 - Connect Request)); T1 -->|Alerting-req. (#)| AL[ALERTING (#)]; AL --> U7((U7 - Call Received));
+```
+
+Flowchart for U6 - Call Present state transitions.
+
+T1163660-94/d113
+
+
+
+This flowchart illustrates the state transitions for the U7 - Call Received state. The initial state is U7 - Call Received, which is associated with section 5.2.6. From this state, a single transition is shown: Setup-resp. (#). This transition leads to the CONNECT (#) state, which then leads to the SET (Now + t313, timer T313) state, which then leads to the U8 - Connect Request state.
+
+```
+graph TD; U7((U7 - Call Received)) -->|See 5.2.6| T1[ ]; T1 -->|Setup-resp. (#)| C[CONNECT (#)]; C --> SET[SET (Now + t313, timer T313)]; SET --> U8((U8 - Connect Request));
+```
+
+Flowchart for U7 - Call Received state transitions.
+
+T1163670-94/d114
+
+
+
+```
+graph TD; U8[("U8 - Connect Request")] --> T313[/Timeout T313/]; U8 --> ACK[/CONNECT-ACKNOWLEDGE (#)/]; T313 --> C102[Cause := 102]; C102 --> D1((D)); ACK --> VM[Verify-Msg]; VM --> R{Result}; R -- RAP --> S10[STATUS (Cause, CS = U10)]; S10 --> RT[RESET T313]; R -- OK --> RT; R -- CLR --> D2((D)); R -- RAI --> S8[STATUS (Cause, CS = U8)]; S8 --> U8R[("U8 - Connect Request")]; RT --> SCI[/Setup-complete-ind. (#)/]; SCI --> U10[("U10 - Active")];
+```
+
+The Application process should attach the user to the virtual channel
+
+T1163680-94/d115
+
+Flowchart for PROCESS Q.2931-U showing the connection process. It starts with 'U8 - Connect Request' leading to 'Timeout T313' and 'CONNECT-ACKNOWLEDGE (#)'. 'Timeout T313' leads to 'Cause := 102' and then to connector 'D'. 'CONNECT-ACKNOWLEDGE (#)' leads to 'Verify-Msg' and then to 'Result'. 'Result' has four paths: 'RAP' leads to 'STATUS (Cause, CS = U10)' and then to 'RESET T313'; 'OK' leads to 'RESET T313'; 'CLR' leads to connector 'D'; 'RAI' leads to 'STATUS (Cause, CS = U8)' and then to 'U8 - Connect Request'. 'RESET T313' leads to 'Setup-complete-ind. (#)' and then to 'U10 - Active'. A note indicates 'The Application process should attach the user to the virtual channel' for 'Setup-complete-ind. (#)'. A reference 'T1163680-94/d115' is at the bottom right.
+
+
+
+U9 - Incoming Call Proceeding
+
+See 5.2.5.1, 5.2.6, 5.2.5.2
+
+Setup-resp. (#)
+
+Alerting-req. (#)
+
+CONNECT (#)
+
+ALERTING (#)
+
+SET(Now + t313, timer T313)
+
+U7 - Call Received
+
+T1163690-94/d116
+
+U8 - Connect Request
+
+```
+stateDiagram-v2
+ [*] --> U9
+ U9 --> Setup_resp[Setup-resp. (#)]
+ U9 --> Alerting_req[Alerting-req. (#)]
+ Setup_resp --> CONNECT[CONNECT (#)]
+ CONNECT --> SET_timer[SET(Now + t313, timer T313)]
+ SET_timer --> U8[U8 - Connect Request]
+ Alerting_req --> ALERTING[ALERTING (#)]
+ ALERTING --> U7[U7 - Call Received]
+```
+
+State transition diagram for U9 - Incoming Call Proceeding
+
+
+
+U10 - Active
+
+See 5.6.9c, 5.6.10
+
+Link Release indication
+
+Link Establish error
+
+Link Establish indication
+
+Link Establish confirm
+
+Link Establish request
+
+Release-conf. (Cause := 27)
+
+SE
+
+T1163700-94/d117
+
+U10 - Active
+
+```
+stateDiagram-v2
+ [*] --> U10
+ U10 --> Link_Release[Link Release indication]
+ U10 --> Link_Error[Link Establish error]
+ U10 --> Link_Ind[Link Establish indication]
+ U10 --> Link_Confirm[Link Establish confirm]
+ Link_Release --> Link_Request[Link Establish request]
+ Link_Request --> U10
+ Link_Error --> Release_Conf[Release-conf. (Cause := 27)]
+ Release_Conf --> [*]
+ Link_Ind --> Link_Confirm
+ Link_Confirm --> SE((SE))
+ SE --> [*]
+```
+
+State transition diagram for U10 - Active
+
+
+
+```
+graph TD; Start["*(except U0)"] --- Note["See 5.9"]; Start --> Req["Notify.req (#)"]; Req --> NotifyReq["NOTIFY (#)"]; NotifyReq --> End1[(- - -)]; Start --> Notify["NOTIFY (#)"]; Notify --> Verify["Verify-Msg"]; Verify --> Result{Result}; Result -- RAP --> StatusRAP["STATUS (Cause, CS)"]; StatusRAP --> NotifyInd["Notify-ind. (#)"]; NotifyInd --> End2[(- - -)]; Result -- OK --> NotifyInd; Result -- CLR --> D((D)); Result -- RAI --> StatusRAI["STATUS (Cause, CS)"]; StatusRAI --> End3[(- - -)]; Result -- I --> End3;
+```
+
+Flowchart for PROCESS Q.2931-U; starting with a loop condition '\*' (except U0) leading to 'Notify.req (#)' and 'NOTIFY (#)' paths. The 'NOTIFY (#)' path includes 'Verify-Msg' and a 'Result' decision with branches RAP, OK, CLR, RAI, and I leading to various status and notification outputs.
+
+T1163710-94/d11 18
+
+PROCESS Q.2931-U;
+
+page 11 of (31)
+
+
+
+The diagram illustrates three flowcharts for PROCESS Q.2931-U, each representing a different release procedure.
+
+**Flowchart 1: RELEASE-COMPLETE (Cause, #)**
+
+- Starts with a connector symbol: \* (except U0, U11, U12) -- See 5.6.4, 5.4.3.
+- Primitive: RELEASE-COMPLETE (Cause, #).
+- Process: Verify-Msg.
+- Decision: Result.
+- Output options: I, RAP, OK, CLR, RAI.
+- Process: RESET ALL TIMERS.
+- Primitive: Release-conf. (Cause, #).
+- Note: After receiving this primitive, the Application process shall release the user virtual channel.
+- End: X.
+
+**Flowchart 2: RELEASE (Cause, #)**
+
+- Starts with a connector symbol: \* (except U0, U11, U12) -- See 5.4.3, 5.4.4.
+- Primitive: RELEASE (Cause, #).
+- Process: Verify-Msg.
+- Decision: Result.
+- Output options: RAP, OK, CLR, RAI, I.
+- Process: RESET ALL TIMERS.
+- Primitive: Release-ind. (Cause, #).
+- Note: After receiving this primitive, the Application process shall release the user virtual channel.
+- End: U12 - Release Indication.
+
+**Flowchart 3: Release.req. (Cause)**
+
+- Starts with a connector symbol: \* (except U0, U11, U12) -- See 5.4.3, 5.4.4.
+- Primitive: Release.req. (Cause).
+- Process: Cause R := Cause /\*Cause saved\*/.
+- Process: RESET ALL TIMERS.
+- Primitive: RELEASE (Cause).
+- Process: SET(Now + t308, timer T308); Timeout := 0.
+- End: U11 - Release Request.
+
+A connector symbol 'D' is shown between the second and third flowcharts, with an arrow pointing to a primitive: Release-ind. (Cause).
+
+Flowcharts for PROCESS Q.2931-U showing three release procedures: RELEASE-COMPLETE, RELEASE, and Release.req.
+
+T1163720-94/d119
+
+
+
+```
+
+graph TD
+ U11_Req1([U11 - Release Request]) --> RC[RELEASE-COMPLETE (#)]
+ U11_Req1 --> R[RELEASE (#)]
+ U11_Req1 --> T[Timeout T308]
+ R -.-> CC[Clear collision]
+ RC --> VM[Verify-Msg]
+ VM --> Res{Result}
+ Res -- RAP --> RAP_L[ ]
+ Res -- OK --> OK_L[ ]
+ Res -- CLR --> CLR_L[ ]
+ Res -- RAI --> RAI_L[ ]
+ Res -- I --> I_L[ ]
+ OK_L --> RT[RESET T308]
+ RT --> RCnf[Release-conf. (Cause, #)]
+ RCnf -.-> AP[After receiving this primitive, the Application process shall release the user virtual channel]
+ RCnf --> End1(( ))
+ T --> T1{Timeout = 1}
+ T1 -- Yes --> RF[Release reason = failure]
+ RF --> RCnf2[Release Conf. Release reason]
+ RCnf2 --> End2(( ))
+ T1 -- No --> C1[Cause1 := CauseR]
+ C1 --> CO{Cause option}
+ CO --> C[Cause := 102]
+ C --> R2[RELEASE (Cause 1, Cause 2, #)]
+ R2 --> SET[SET (Now + t308, timer T308) Timeout := 1]
+ SET --> U11_Req2([U11 - Release Request])
+ CO --> R1[RELEASE (Cause1, #)]
+ R1 --> SET
+ RF -.-> AP2[The Application process shall place the user virtual channel in a maintenance condition]
+ RCnf2 -.-> AP2
+
+```
+
+Flowchart for PROCESS Q.2931-U showing the release process flow. It starts with 'U11 - Release Request' leading to 'RELEASE-COMPLETE (#)', 'RELEASE (#)' (with 'Clear collision' note), and 'Timeout T308'. 'RELEASE-COMPLETE (#)' leads to 'Verify-Msg' then 'Result' (RAP, OK, CLR, RAI, I). 'OK' leads to 'RESET T308' then 'Release-conf. (Cause, #)'. 'Timeout T308' leads to 'Timeout = 1' decision. 'Yes' leads to 'Release reason = failure' then 'Release Conf. Release reason'. 'No' leads to 'Cause1 := CauseR' then 'Cause option' (Cause := 102) then 'RELEASE (Cause 1, Cause 2, #)' then 'SET (Now + t308, timer T308) Timeout := 1' then 'U11 - Release Request'. 'Cause option' also leads to 'RELEASE (Cause1, #)'.
+
+T1166120-94/d120
+
+
+
+```
+graph TD; U11_1([U11 - Release Request]) --> STATUS_1[/STATUS (Cause, CS)/]; STATUS_1 --> VM[Verify message]; VM --> Result{Result}; Result -- RAP --> STATUS_2[/STATUS (Cause, CS)/]; Result -- OK --> U0_1([U0 - Null]); Result -- CLR --> STATUS_3[/STATUS (Cause, CS)/]; Result -- RAI --> STATUS_4[/STATUS (Cause, CS)/]; STATUS_2 --> CS_0{CS = 0}; U0_1 --> CS_0; STATUS_3 --> CS_0; STATUS_4 --> CS_0; CS_0 -- Yes --> RC[Release conf. (Cause)]; RC --> X((X)); X --- T1175640_95_d121[T1175640-95/d121]; CS_0 -- No --> U11_2([U11 - Release Request]);
+```
+
+Flowchart for PROCESS Q.2931-U. The process starts with 'U11 - Release Request' (input symbol), which has a note 'See 5.6.12'. It then flows to 'STATUS (Cause, CS)' (output symbol), then to 'Verify message' (process symbol), and then to 'Result' (decision symbol). From 'Result', there are four paths: RAP, OK, CLR, and RAI. The RAP path leads to 'STATUS (Cause, CS)' (output symbol). The OK path leads to 'U0 - Null' (input symbol). The CLR path leads to 'STATUS (Cause, CS)' (output symbol). The RAI path leads to 'STATUS (Cause, CS)' (output symbol). All four paths converge to a decision 'CS = 0'. If 'Yes', it leads to 'Release conf. (Cause)' (output symbol), which ends at a connector symbol 'X' and the text 'T1175640-95/d121'. If 'No', it leads to 'U11 - Release Request' (input symbol).
+
+
+
+```
+
+graph TD
+ U12_1([U12 - Release Indication])
+ Note[See 5.4.4, 5.6.12 b)]
+ RelResp[/Release-resp. (#)/]
+ Status1[/STATUS (Cause, CS)/]
+ RelComp[/RELEASE COMPLETE (#)/]
+ Verify[Verify message]
+ Result{Result}
+ Status2[/STATUS (Cause, CS)/]
+ U0([U0 - Null])
+ Status3[/STATUS (Cause, CS)/]
+ CS0{CS = 0}
+ U12_2([U12 - Release Indication])
+ End1((X))
+ End2((X))
+
+ U12_1 --- Note
+ U12_1 --> RelResp
+ U12_1 --> Status1
+ RelResp --> RelComp
+ RelComp --> End1
+ Status1 --> Verify
+ Verify --> Result
+ Result -- RAP --> Status2
+ Result -- OK --> CS0
+ Result -- CLR --> U0
+ Result -- RAI --> Status3
+ Status2 --> CS0
+ U0 --> CS0
+ Status3 --> CS0
+ CS0 -- Yes --> End2
+ CS0 -- No --> U12_2
+
+```
+
+The flowchart illustrates the process for Q.2931-U. It begins with the state 'U12 - Release Indication', which is accompanied by a note 'See 5.4.4, 5.6.12 b)'. From this state, two parallel paths are shown: one receiving 'Release-resp. (#)' leading to the output 'RELEASE COMPLETE (#)' and termination; the other receiving 'STATUS (Cause, CS)'. The latter leads to a 'Verify message' task followed by a 'Result' decision. The 'Result' decision has four branches: 'RAP' leading to a 'STATUS (Cause, CS)' output; 'OK' leading directly to the next decision; 'CLR' leading to state 'U0 - Null'; and 'RAI' leading to another 'STATUS (Cause, CS)' output. All these branches converge at the 'CS = 0' decision. If the result is 'Yes', the process terminates. If 'No', the process returns to the state 'U12 - Release Indication'.
+
+Flowchart for PROCESS Q.2931-U; showing steps from U12 - Release Indication to RELEASE COMPLETE (#), STATUS (Cause, CS), Verify message, Result, RAP, OK, CLR, U0 - Null, RAI, CS = 0, and final U12 - Release Indication.
+
+T1175650-95/d122
+
+
+
+```
+
+graph TD
+ subgraph LeftPath [ ]
+ L1[except U0] --> L2[STATUS-ENQUIRY]
+ L2 --> L3[Verify message]
+ L3 --> L4{Result}
+ end
+ subgraph RightPath [ ]
+ R1[except U0, U11, U12] --> R2[STATUS (Cause, CS)]
+ R2 --> R3[Verify message]
+ R3 --> R4{Result}
+ end
+ L4 --> Common[ ]
+ R4 --> Common
+ subgraph Common [ ]
+ direction TB
+ C1{RAP OK CLR RAI I} --> C2[ ]
+ end
+ C2 --> OK[OK]
+ C2 --> RAP[RAP]
+ C2 --> CLR[CLR]
+ C2 --> RAI[RAI]
+ C2 --> I[I]
+ RAP --> RAP_OUT[STATUS (Cause, CS)]
+ OK --> U0[ ]
+ CLR --> U0
+ RAI --> RAI_OUT[STATUS (Cause, CS)]
+ I --> CS0[ ]
+ RAI_OUT --> CS0
+ CS0 --> CS0_Q{CS = 0}
+ CS0_Q -- Yes --> ReleaseConf[ ]
+ CS0_Q -- No --> Cause30[ ]
+ Cause30 -- Yes --> ResetT322[ ]
+ Cause30 -- No --> CS0_Q
+ ResetT322 --> ReleaseConf
+ ReleaseConf --> ReleaseConf_X[ ]
+ ReleaseConf_X --> CompatibleState[ ]
+ CompatibleState -- No --> RecoveryOption[ ]
+ CompatibleState -- Yes --> CompatibleState_Dash[ ]
+ RecoveryOption -- Yes --> RecoveryProcedure[ ]
+ RecoveryOption -- No --> StatusInd[ ]
+ RecoveryProcedure --> D((D))
+ StatusInd --> D
+ style LeftPath fill:none,stroke:none
+ style RightPath fill:none,stroke:none
+ style Common fill:none,stroke:none
+ style U0 fill:none,stroke:none
+ style CS0 fill:none,stroke:none
+ style ReleaseConf fill:none,stroke:none
+ style CompatibleState fill:none,stroke:none
+ style CompatibleState_Dash fill:none,stroke:none
+ style ReleaseConf_X fill:none,stroke:none
+
+```
+
+Flowchart for PROCESS Q.2931-U; showing two main paths. The left path starts with an exception block 'except U0' leading to STATUS-ENQUIRY, then Verify message, then Result. The right path starts with an exception block 'except U0, U11, U12' leading to STATUS (Cause, CS), then Verify message, then Result. Both paths lead to a common decision point with options RAP, OK, CLR, RAI, I. The OK path leads to U0 - Null. The RAI path leads to STATUS (Cause, CS), then CS = 0. If CS = 0 is No, it leads to Cause = 30. If Cause = 30 is Yes, it leads to RESET T322. Both RESET T322 and CS = 0 Yes lead to Release-conf. (Cause). If CS = 0 is Yes, it leads to Compatible State. If Compatible State is No, it leads to Recovery option. If Recovery option is Yes, it leads to Recovery procedure. If Recovery option is No, it leads to Status-ind. (Cause := 101). Both Recovery procedure and Status-ind. lead to connector D.
+
+T1175660-95/d123
+
+
+
+The diagram is a state transition flowchart for PROCESS Q.2931-U. It begins with an initial state marked with an asterisk (\*) and the note "(except U0)". A dashed line from this state points to a note "See 5.6.4, 5.6.11".
+
+From the initial state, three main paths emerge:
+
+- Timeout T322 Path:** Leads to a state where "Timeout := Timeout + 1". This leads to a decision diamond "Timeout = NT".
+ - If "Yes", it leads to a state "Release-conf. (Cause = 41)". A note indicates "NT = number of STATUS ENQUIRY transmissions: implementation dependent value $\geq 1$ ".
+ - If "No", it leads to a decision diamond "ACTIVE T322".
+ - If "Yes", it loops back to the initial state.
+ - If "No", it leads to a state "STATUS ENQUIRY (#)", which then leads to "SET (Now + t322, timer T322)", which then leads to a state represented by a circle with a dash.
+- Start Event (SE) Path:** Leads to a state "Timeout := 0", which then leads to the "ACTIVE T322" decision diamond.
+- Any recognized message Path:** Leads to a state labeled with an asterisk (\*) and the note "/\*any other message\*/". A note indicates "Any recognized message other than those specifically shown in the Q.2931-U process". This leads to a "Verify message" decision diamond.
+ - From "Verify message", it branches based on flags: "Inst. Ind. Flag = 0", "RAI", and "Reserved Inst. Ind.". This leads to a state "STATUS (Cause 97/101)", which then leads to a state represented by a circle with a dash.
+ - It also branches based on "I" and "CLR" flags to a decision diamond "State = Release request or Release indication?".
+ - If "Yes", it loops back to the initial state.
+ - If "No", it leads to a connector "D".
+
+Below the first path, there is a section for unrecognized messages:
+
+- Leads to a state labeled with an asterisk (\*) and the note "/\*unrecognized message\*/". A note indicates "Any unrecognized message". This leads to a "Verify message" decision diamond.
+- From "Verify message", it branches based on flags: "Inst. Ind. Flag = 0", "RAI", and "Reserved Inst. Ind.". This leads to a state "STATUS (Cause 97/101)", which then leads to a state represented by a circle with a dash.
+- It also branches based on "I" and "CLR" flags to a decision diamond "State = Release request or Release indication?".
+ - If "Yes", it loops back to the initial state.
+ - If "No", it leads to a connector "D".
+
+A reference code "T1175670-95/d124" is located near the bottom right connector "D".
+
+State transition diagram for PROCESS Q.2931-U. The diagram shows various states and transitions based on timers (T322), messages (STATUS ENQUIRY, STATUS, any other message, unrecognized message), and flags (Inst. Ind. Flag, RAI, Reserved Inst. Ind., I, CLR). It includes decision diamonds for 'Timeout = NT', 'ACTIVE T322', 'Verify message', and 'State = Release request or Release indication?'. Transitions include actions like 'Timeout := Timeout + 1', 'Timeout := 0', 'Release-conf. (Cause = 41)', 'STATUS ENQUIRY (#)', 'SET (Now + t322, timer T322)', and 'STATUS (Cause 97/101)'. Annotations explain symbols like '\*' (except U0), 'SE' (Start Event), and 'NT' (number of STATUS ENQUIRY transmissions).
+
+
+
+Flowchart for PROCESS Q.2931-U;:
+
+- Top block: U1, U3, U4, U6, U7, U8, U9, U11, U12 (linked to See 5.6.9 a), b)
+- Second block: Link Establish indication
+- Third block: -
+
+Flowchart for PROCESS Q.2931-U; showing a sequence of steps: a list of U1, U3, U4, U6, U7, U8, U9, U11, U12 (linked to See 5.6.9 a), b), followed by Link Establish indication, and ending with a dash.
+
+
+
+Flowchart for PROCESS Q.2931-U;:
+
+- Top block: \* (except U10) (linked to See 5.6.10)
+- Second block: Link Establish indication
+- Third block: Release-conf. (Cause := 127)
+- End: Crossed-out arrow
+
+Flowchart for PROCESS Q.2931-U; showing a sequence of steps: an asterisk (except U10) (linked to See 5.6.10), followed by Link Establish indication, then Release-conf. (Cause := 127), and ending with a crossed-out arrow.
+
+T1166170-94/d125
+
+
+
+The diagram illustrates two call flow paths for symmetric call operations, starting from a common state 'U1 - Call Initiated' which is linked to 'Annex H'.
+
+**Path 1: CONNECT (#)**
+
+- Starts with 'CONNECT (#)' message.
+- Followed by 'Verify-Msg'.
+- A 'Result' decision diamond follows.
+- From 'Result', four outcomes are possible:
+ - RAP**: Leads to 'Status (Cause, CS = U10)'.
+ - OK**: Leads to 'RESET T303'.
+ - CLR**: Leads to a discard symbol 'D'.
+ - RAI**: Leads to 'Status (Cause, CS = U1)'.
+- Both 'Status (Cause, CS = U10)' and 'Status (Cause, CS = U1)' lead to 'Setup-conf. (#)'.
+- 'Setup-conf. (#)' leads to 'CONNECT ACKNOWLEDGE'.
+- 'CONNECT ACKNOWLEDGE' leads to the final state 'U10 - Active'.
+
+**Path 2: ALERTING (#)**
+
+- Starts with 'ALERTING (#)' message.
+- Followed by 'Verify-Msg'.
+- A 'Result' decision diamond follows.
+- From 'Result', four outcomes are possible:
+ - RAP**: Leads to 'Status (Cause, CS = U4)'.
+ - OK**: Leads to 'RESET T303'.
+ - CLR**: Leads to a discard symbol 'D'.
+ - RAI**: Leads to 'Status (Cause, CS = U1)'.
+- Both 'Status (Cause, CS = U4)' and 'Status (Cause, CS = U1)' lead to 'Alerting-ind. (#)'.
+- 'Alerting-ind. (#)' leads to 'SET (Now + t301, timer T301)'.
+- 'SET (Now + t301, timer T301)' leads to the final state 'U4 - Call Delivered'.
+
+A reference code 'T1163790-94/d126' is located near the bottom right of the diagram.
+
+Flowchart titled 'Extensions for symmetric call operation' showing two call flow paths: CONNECT (#) and ALERTING (#).
+
+## Extensions for symmetric call operation
+
+
+
+**U2 - Overlap Sending Process:**
+
+- State: U2 - Overlap Sending (See 6.5.2, Interworking only, Annex H)
+- Action: ALERTING (#)
+- Action: Verify-Msg
+- Decision: Result
+ - RAP: Status (Cause, CS = U4) → RESET T304
+ - OK: RESET T304
+ - CLR: D (Connector)
+ - RAI: Status (Cause, CS = U2) → U2 - Overlap Sending
+ - I: Allerting-ind. (#)
+- Action: Allerting-ind. (#)
+- Action: SET (Now + t301, timer T301) (Annex H)
+- State: U4 - Call Delivered
+
+**U3 - Outgoing Call Proceeding Process:**
+
+- State: U3 - Outgoing Call Proceeding (See Annex H)
+- Action: ALERTING (#)
+- Action: Verify-Msg
+- Decision: Result
+ - RAP: Status (Cause, CS = U4) → RESET T310
+ - OK: RESET T310
+ - CLR: D (Connector)
+ - RAI: Status (Cause, CS = U3) → U3 - Outgoing Call Proceeding
+ - I: Allerting-ind. (#)
+- Action: Allerting-ind. (#)
+- Action: SET (Now + t301, timer T301) (Annex H)
+- State: U4 - Call Delivered
+
+Flowcharts for U2 and U3 call processes. Both start with a state (U2 - Overlap Sending or U3 - Outgoing Call Proceeding), followed by ALERTING (#), Verify-Msg, and a Result decision. The Result decision leads to RAP, OK, CLR, RAI, or I options. The OK path leads to RESET T304 (for U2) or RESET T310 (for U3), then Allerting-ind. (#), SET (Now + t301, timer T301), and finally U4 - Call Delivered. The CLR path leads to a connector D. The RAI path leads to a Status (Cause, CS = U2) or Status (Cause, CS = U3) box, which then leads to the U2 or U3 state respectively. The RAP path leads to a Status (Cause, CS = U4) box, which then leads to the RESET T304 or RESET T310 box. The I path leads to the Allerting-ind. (#) box. Annex H is referenced for the SET (Now + t301, timer T301) box in both processes.
+
+T1163800-94/d127
+
+
+
+Extensions for symmetric call operation
+
+```
+graph TD; A[U4 - Call Delivered] -- Annex H --> B[Timeout T301]; A --> C[CONNECT #]; B --> D1[Cause := 19]; D1 --> E((D)); C --> F[Verify-Msg]; F --> G{Result}; G -- RAP --> H[Status (Cause, CS = U10)]; H -- Annex H --> I[RESET T301]; G -- OK --> I; G -- CLR --> J((D)); G -- RAI --> K[STATUS (Cause, CS = U4)]; K --> L[U4 - Call Delivered]; I --> M[Setup-conf. #]; M --> N[CONNECT ACKNOWLEDGE #]; N --> O[U10 - Active]; K -- I --> L; P[T1163810-94/d128]
+```
+
+Flowchart for symmetric call operation extensions. It starts with 'U4 - Call Delivered' (Annex H) leading to 'Timeout T301' (Cause := 19, D) and 'CONNECT (#)' (Verify-Msg, Result). The 'Result' leads to 'RAP' (Status (Cause, CS = U10), Annex H), 'OK' (RESET T301, Annex H), 'CLR' (D), 'RAI' (STATUS (Cause, CS = U4), U4 - Call Delivered), and 'I'. 'RESET T301' leads to 'Setup-conf. (#)' and 'CONNECT ACKNOWLEDGE (#)' (U10 - Active). 'STATUS (Cause, CS = U4)' also leads to 'U4 - Call Delivered'. Reference T1163810-94/d128.
+
+
+
+Additional procedures related to interworking
+
+U1 - Call Initiated --- See 6.5.2
+
+SETUP-ACKNOWLEDGE (#)
+
+Info.req. (#)
+
+Verify-Msg
+
+Result
+
+RAP OK CLR RAI I
+
+Status (Cause, CS = U2)
+
+D
+
+RESET T303
+
+STATUS (Cause, CS = U1)
+
+U4 - Call Initiated
+
+T1163820-94/d129
+
+T303 implemented
+
+Yes No
+
+SET (Now + t304, timer T304)
+
+More-info.ind. (#)
+
+U2 - Overlap Sending
+
+```
+graph TD; U1([U1 - Call Initiated]) --- S652[See 6.5.2]; U1 --> SA[SETUP-ACKNOWLEDGE (#)]; U1 --> IR[Info.req. (#)]; SA --> VM[Verify-Msg]; VM --> R{Result}; R -- RAP --> S2[Status (Cause, CS = U2)]; R -- OK --> RT[RESET T303]; R -- CLR --> D((D)); R -- RAI --> S1[STATUS (Cause, CS = U1)]; R -- I --> U4([U4 - Call Initiated]); S2 --> RT; S1 --> U4; RT --> TI{T303 implemented}; TI -- Yes --> SET[SET (Now + t304, timer T304)]; TI -- No --> SET; SET --> MI[More-info.ind. (#)]; MI --> U2([U2 - Overlap Sending]);
+```
+
+Flowchart for PROCESS Q.2931-U; starting with 'U1 - Call Initiated' and ending with 'U2 - Overlap Sending'. It includes steps like 'SETUP-ACKNOWLEDGE (#)', 'Verify-Msg', 'Result', 'RESET T303', and 'More-info.ind. (#)'.
+
+
+
+```
+graph TD; A[Additional procedures related to interworking] --> B((U2 - Overlap Sending)); B -.-> C[See 6.5.2]; B --> D1{Info.req. (#)}; B --> D2{Timeout T304}; B --> D3{Progress (#)}; D1 --> E[INFORMATION (#)]; E --> F{T304 implemented}; F -- Yes --> G[SET (Now + t304, timer T304)]; F -- No --> H((U2 - Overlap Sending)); G --> H; D2 --> I[Cause := 102]; I --> J((D)); D3 --> K[Verify-Msg]; K --> L{Result}; L -- RAP --> M[Status (Cause, CS = U2)]; L -- OK --> N[Progress-ind. (interworking, #)]; L -- CLR --> O((D)); L -- RAI --> P[STATUS (Cause, CS = U2)]; L -- I --> Q[ ]; M --> N; M --> P; N --> R((U2 - Overlap Sending)); P --> S((U2 - Overlap Sending));
+```
+
+Flowchart for U2 - Overlap Sending process. It starts with 'Additional procedures related to interworking' leading to 'U2 - Overlap Sending'. From there, it branches into three paths: 'Info.req. (#)' leading to 'INFORMATION (#)' and then a decision 'T304 implemented'; 'Timeout T304' leading to 'Cause := 102' and connector 'D'; and 'Progress (#)' leading to 'Verify-Msg' and decision 'Result'. The 'Result' decision has five branches: RAP, OK, CLR, RAI, and I. RAP leads to 'Status (Cause, CS = U2)'. OK and RAI lead to 'Progress-ind. (interworking, #)' and 'STATUS (Cause, CS = U2)' respectively. CLR leads to connector 'D'. Both 'Progress-ind.' and 'STATUS' lead to 'U2 - Overlap Sending'. The 'T304 implemented' decision has 'Yes' leading to 'SET (Now + t304, timer T304)' and 'No' leading to 'U2 - Overlap Sending'. 'SET' also leads to 'U2 - Overlap Sending'. A note 'See 6.5.2' is associated with the initial 'U2 - Overlap Sending' block.
+
+T1163830-94/d130
+
+
+
+Additional procedures related to interworking
+
+
+
+```
+
+graph TD
+ U2([U2 - Overlap Sending]) --- Note[See 6.5.2]
+ U2 --> CP[/CALL-PROCEEDING (#)/]
+ U2 --> AL[/ALERTING (#)/]
+
+ subgraph Left_Path [CALL-PROCEEDING Path]
+ CP --> VM1[[Verify-Msg]]
+ VM1 --> R1{Result}
+ R1 -- RAP --> S1[/Status
+ (Cause, CS = U3)/]
+ R1 -- OK --> RT1[RESET T304]
+ R1 -- CLR --> D1((D))
+ R1 -- RAI --> S2[/STATUS
+ (Cause, CS = U2)/]
+ R1 -- I --> S2
+ S1 --> RT1
+ RT1 --> PI[/Proceeding-ind. (#)/]
+ PI --> U3([U3 - Outgoing Call Proceeding])
+ S2 --> U2_back1([U2 - Overlap Sending])
+ end
+
+ subgraph Right_Path [ALERTING Path]
+ AL --> VM2[[Verify-Msg]]
+ VM2 --> R2{Result}
+ R2 -- RAP --> S3[/Status
+ (Cause, CS = U4)/]
+ R2 -- OK --> RT2[RESET T304]
+ R2 -- CLR --> D2((D))
+ R2 -- RAI --> S4[/STATUS
+ (Cause, CS = U2)/]
+ R2 -- I --> S4
+ S3 --> RT2
+ RT2 --> AI[/Alerting-ind. (#)/]
+ AI --> U4([U4 - Call Delivered])
+ S4 --> U2_back2([U2 - Overlap Sending])
+ end
+
+```
+
+T1163840-94/d131
+
+
+
+Additional procedures related to interworking
+
+```
+graph TD; A([U2 - Overlap Sending]) --> B[/CONNECT (#)/]; B --> C[Verify-Msg]; C --> D{Result}; D -- RAP --> E[/Status (Cause, CS = U10)/]; D -- OK --> F[RESET T304]; D -- CLR --> G((D)); D -- RAI --> H[/STATUS (Cause, CS = U2)/]; D -- I --> I2([U2 - Overlap Sending]); E --> F; F --> J[/Setup-conf. (#)/]; H --> I2; I2 --> J; J --> K[/CONNECT ACKNOWLEDGE (#)/]; K --> L([U10 - Active]);
+```
+
+U2 - Overlap Sending --- See 6.5.2
+
+CONNECT (#)
+
+Verify-Msg
+
+Result
+
+RAP
+
+OK
+
+CLR
+
+RAI
+
+I
+
+Status (Cause, CS = U10)
+
+D
+
+RESET T304
+
+STATUS (Cause, CS = U2)
+
+U2 - Overlap Sending
+
+Setup-conf. (#)
+
+CONNECT ACKNOWLEDGE (#)
+
+U10 - Active
+
+T1163850-94/d132
+
+Flowchart for PROCESS Q.2931-U showing the sequence of messages and states for interworking. It starts with 'U2 - Overlap Sending' (referencing 6.5.2), followed by 'CONNECT (#)', 'Verify-Msg', and a 'Result' decision. The 'Result' decision has five branches: RAP, OK, CLR, RAI, and I. The RAP branch leads to 'Status (Cause, CS = U10)'. The OK branch leads to 'RESET T304'. The CLR branch leads to a circle labeled 'D'. The RAI branch leads to 'STATUS (Cause, CS = U2)'. The I branch leads to 'U2 - Overlap Sending'. All five branches converge to a common path leading to 'Setup-conf. (#)', 'CONNECT ACKNOWLEDGE (#)', and finally 'U10 - Active'.
+
+
+
+Additional procedures related to interworking
+
+```
+graph TD; C1([U3 - Outgoing Call Proceeding]) --> P[PROGRESS (#)]; P --> V[Verify-Msg]; V --> R{Result}; R -- RAP --> S1>Status (Cause, CS = U3); S1 --> PI[Progress-ind. (#)]; PI --> C2([U3 - Outgoing Call Proceeding]); R -- OK --> C2; R -- CLR --> D((D)); D --> C2; R -- RAI --> S2>Status (Cause, CS = U3); S2 --> C2; R -- I --> C2;
+```
+
+See 6.6
+U3 also on page 3
+
+Flowchart for U3 - Outgoing Call Proceeding. It starts with a connector, followed by PROGRESS (#), Verify-Msg, and a Result decision. The Result decision has five branches: RAP, OK, CLR, RAI, and I. RAP leads to Status (Cause, CS = U3) then Progress-ind. (#) then the connector. OK leads directly to the connector. CLR leads to a connector D. RAI leads to STATUS (Cause, CS = U3) then the connector. I leads directly to the connector. A note 'See 6.6 U3 also on page 3' is next to the first connector.
+
+T1163860-94/d133
+
+
+
+```
+graph TD; A[Additional procedures related to interworking] --> B((U4 - Call Delivered)); B -.-> B_note[See 6.6]; B --> C[/PROGRESS (#)/]; C --> D[Verify-Msg]; D --> E{Result}; E -- RAP --> F[/Status (Cause, CS = U4)/]; E -- OK --> G[/Progress-ind. (#)/]; E -- CLR --> H((D)); E -- RAI --> I[/STATUS (Cause, CS = U4)/]; E -- I --> J((U4 - Call Delivered)); F --> G; G --> J; I --> J;
+```
+
+Flowchart for U4 - Call Delivered process. It starts with 'Additional procedures related to interworking', followed by 'U4 - Call Delivered' (with a note 'See 6.6'), 'PROGRESS (#)', 'Verify-Msg', and a 'Result' decision. The 'Result' decision has five branches: RAP, OK, CLR, RAI, and I. RAP leads to 'Status (Cause, CS = U4)'. OK leads to 'Progress-ind. (#)'. CLR leads to a connector 'D'. RAI leads to 'STATUS (Cause, CS = U4)'. I leads to the bottom 'U4 - Call Delivered'. Both 'Progress-ind. (#)' and 'STATUS (Cause, CS = U4)' lead to 'U4 - Call Delivered'.
+
+T1163870-94/d134
+
+
+
+```
+graph TD; A[Additional procedures related to interworking] --> B((U6 - Call Present)); B -.-> B_ref[See 6.5.3]; B --> C[/More-info.req. (#)/]; C --> D[/SETUP ACKNOWLEDGE (#)/]; D --> E[set (Now + t302, timer t302)]; E --> F((U25 - Overlap Receiving));
+```
+
+T1163880-94/d135
+
+Flowchart for PROCESS Q.2931-U; page 27 of (31). The flowchart starts with a box 'Additional procedures related to interworking', followed by a state 'U6 - Call Present' (linked to 'See 6.5.3'), then a message 'More-info.req. (#)', then a message 'SETUP ACKNOWLEDGE (#)', then a state 'set (Now + t302, timer t302)', and finally a state 'U25 - Overlap Receiving'. The diagram is labeled T1163880-94/d135.
+
+
+
+```
+graph TD; A[Additional procedures related to interworking] --> B((U9 - Incoming Call Proceeding)); B -.-> B_ref[See 6.6]; B --> C[/Progress.req. (#)/]; C --> D[/PROGRESS (#)/]; D --> E((U9 - Incoming Call Proceeding));
+```
+
+T1163890-94/d136
+
+Flowchart for PROCESS Q.2931-U; page 28 of (31). The flowchart starts with a box 'Additional procedures related to interworking', followed by a state 'U9 - Incoming Call Proceeding' (linked to 'See 6.6'), then a message 'Progress.req. (#)', then a message 'PROGRESS (#)', and finally a state 'U9 - Incoming Call Proceeding'. The diagram is labeled T1163890-94/d136.
+
+
+
+```
+
+ graph TD
+ Start[Additional procedures related to interworking] --> U25_1((U25 - Overlap Receiving))
+ U25_1 --- Note1[See 6.5.3]
+
+ U25_1 --> INFO[/INFORMATION (#)/]
+ U25_1 --> T302[/Timeout T302/]
+ U25_1 --> PR[/Progress-req./]
+
+ INFO --> VM[Verify-Msg]
+ VM --> Res{Result}
+
+ Res -- RAP --> Status1[/Status
+Cause, CS = U25/]
+ Status1 --> InfoInd[Info-ind. (#)]
+ Res -- OK --> InfoInd
+ Res -- CLR --> D((D))
+ Res -- RAI --> Status2[/Status
+Cause, CS = U25/]
+ Status2 --> U25_2((U25 - Overlap Receiving))
+ Res -- I --> U25_2
+
+ InfoInd --> SC{SC IE present}
+ SC -- Yes --> Reset1[RESET T302]
+ Reset1 --> U25_3((U25 - Overlap Receiving))
+ SC -- No --> Set[SET Now + t302,
+timer T302]
+ Set --> U25_3
+ SC --- Note3[SC means Sending Complete]
+
+ T302 --> TI[Timeout-ind.]
+ TI --> U25_4((U25 - Overlap Receiving))
+ TI --- Note2[Application Process
+determines action]
+
+ PR --> Reset2[RESET T302]
+ Reset2 --> Prog[/PROGRESS (#)/]
+ Prog --> U25_5((U25 - Overlap Receiving))
+
+ style Note1 stroke-dasharray: 5 5
+ style Note2 stroke-dasharray: 5 5
+ style Note3 stroke-dasharray: 5 5
+
+```
+
+T1163900-94/d137
+
+SDL Flowchart for U25 - Overlap Receiving process in Recommendation Q.2931.
+
+
+
+```
+graph TD; U25((U25 - Overlap Receiving)) --- Note[See 6.5.3]; U25 --- Branch(( )); Branch --> P[Proceeding-req. (#)]; Branch --> A[Alerting-req. (#)]; Branch --> S[Setup-resp. (#)]; P --> R1[RESET T302]; R1 --> CP[CALL-PROCEEDING (#)]; CP --> U9((U9 - Incoming Call Proceeding)); A --> R2[RESET T302]; R2 --> AL[ALERTING (#)]; AL --> U7((U7 - Call Received)); S --> R3[RESET T302]; R3 --> CO[CONNECT (#)]; CO --> SET[SET (Now + t313, timer T313)]; SET --> U8((U8 - Connect Request));
+```
+
+Flowchart for U25 - Overlap Receiving process. It branches into three paths: Proceeding-req. (#), Alerting-req. (#), and Setup-resp. (#). Each path has a RESET T302 step, followed by a message (CALL-PROCEEDING (#), ALERTING (#), or CONNECT (#)), leading to a state (U9 - Incoming Call Proceeding, U7 - Call Received, or U8 - Connect Request). The U8 path includes a SET (Now + t313, timer T313) step. A box at the top indicates 'Additional procedures related to interworking'. A note 'See 6.5.3' is next to the U25 state.
+
+T1163910-94/d138
+
+Additional procedures related to interworking
+
+Clearing with In-band Tones & Announcements
+
+
+
+```
+
+graph TD
+ Start([*
+(except U0, U11, U12)]) -.->|Replace the transition with this one| Release[RELEASE
+(Progress Ind. #8 "In-band info", Cause. #)]
+ Release --> Verify[Verify-Msg]
+ Verify --> Result{Result}
+ Result --> RAP
+ Result --> OK
+ Result --> CLR
+ Result --> RAI
+ Result --> I
+ RAP --> Reset[RESET ALL TIMERS]
+ OK --> Reset
+ CLR --> Reset
+ RAI --> Reset
+ I --> Reset
+ Reset --> ReleaseInd{Release-ind.
+(Progress Ind. #8 "In-band info", Cause. #)}
+ ReleaseInd -.->|After receiving this primitive, the Application process shall connect the user to the virtual channel (if not already connected)| End([U12 - Release Indication])
+
+```
+
+Flowchart for PROCESS Q.2931-U showing steps: \*, RELEASE (Progress Ind. #8 'In-band info', Cause. #), Verify-Msg, Result (RAP, OK, CLR, RAI, I), RESET ALL TIMERS, Release-ind. (Progress Ind. #8 'In-band info', Cause. #), U12 - Release Indication. Includes callouts: 'Replace the transition with this one' and 'After receiving this primitive, the Application process shall connect the user to the virtual channel (if not already connected)'.
+
+T1163920-94/d139
+
+# Annex B
+
+## Compatibility checking
+
+(This annex forms an integral part of this Recommendation)
+
+## B.1 Introduction
+
+This annex describes the various compatibility and address checks which should be carried out to ensure that the best match of user and network capabilities is achieved on a Broadband ISDN call.
+
+For 64 kbit/s based circuit-mode ISDN services, the compatibility checking procedures of Annex B/Q.931 shall apply for the N-BC, N-HLC and N-LLC information elements.
+
+Three different processes of checking shall be performed:
+
+- At the user-to-network interface on the calling side (see B.2);
+- At the network-to-user interface on the called side (see B.3.2); and
+- User-to-user (see B.3.3).
+
+NOTE – In this context and throughout this annex, the term “called user” is the endpoint entity which is explicitly addressed. This may be an Addressed Interworking Unit (IWU); see the I.500-Series of Recommendations.
+
+## B.2 Calling side compatibility checking
+
+At the calling side, the network shall check that the bearer service requested by the calling user in the Broadband bearer related information elements match with the bearer services provided to that user by the network. If a mismatch is detected, then the network shall reject the call using one of the causes listed in 5.1.5.
+
+Network services are described in Recommendations I.230 and I.240 as bearer services and teleservices, respectively.
+
+## B.3 Called side compatibility and address checking
+
+In this subclause, the word “check” means that the user examines the contents of the specified information element.
+
+### B.3.1 Checking of addressing information
+
+If an incoming SETUP message is offered with addressing information (i.e. subaddress or the appropriate part of the called party number), the following actions will occur:
+
+- If a number or sub-address is assigned to a user, then the information in a Called party number or Called party sub-address information element of the incoming call shall be checked by the user against the corresponding part of the number assigned to the user or the user's sub-address. In case of a mismatch, the user shall reject the call. In the case of a match, the compatibility checking described in B.3.2 and B.3.3 will follow.
+- If a user has no assigned number or sub-address, then the Called party number and Called party sub-address information elements shall be ignored. The compatibility checking described in B.3.2 and B.3.3 will follow.
+
+NOTE – According to the user's requirements, compatibility checking can be performed in various ways from the viewpoint of execution order and information to be checked; e.g. first assigned number/sub-address and then compatibility or vice versa.
+
+### B.3.2 Network-to-user compatibility checking
+
+When the network is providing a bearer service at the called side, the user shall check that the bearer service offered by the network in the Broadband bearer related information elements match the bearer services that the user is able to support. If a mismatch is detected in the Broadband bearer capability, then the user shall reject the offered call using cause No. 88, “incompatible destination”. When the user is unable to provide the requested QOS, cause No. 49, “Quality of Service unavailable” should be returned. When the user is unable to support the indicated peak cell rate, cause No. 47, “resource unavailable” should be returned.
+
+Upon receipt of a SETUP message, the user shall examine the following information elements:
+
+- Broadband bearer capability;
+- Quality of Service parameter;
+- ATM traffic descriptor; and
+- OAM traffic descriptor (if present).
+
+The user may also examine the end-to-end transit delay information element (if present).
+
+### **B.3.3 User-to-user compatibility checking**
+
+Next, the called side terminal equipment shall perform the following checks:
+
+- Whether or not it can support the type of AAL requested and any associated parameters specified in the AAL parameters information element.
+- Whether or not the Broadband Low Layer Information (B-LLI) information element is compatible with the functions it supports. The B-LLI information element (if available) shall be used to check compatibility of low layers (e.g. layer 2 and layer 3, if layered according to the OSI model).
+- The called terminal equipment may check the Broadband High Layer Information (B-HLI) information element (if present) as part of user-to-user compatibility checking procedures.
+
+If a mismatch is detected in checking any of the information elements above, then the terminal equipment shall either ignore or reject the offered call using cause No. 88, "incompatible destination".
+
+With regard to the presence or absence of the B-HLI and B-LLI information elements, two cases arise:
+
+- Compatibility assured with the available description of the call – Terminal equipment implements (i.e. understands the contents of) the AAL parameters, B-HLI and B-LLI information elements. Thus, based on the AAL parameters and B-LLI and B-HLI information element encoding, they are capable of accepting a call for which they have the requested functionality.
+- Compatibility not assured with the available description of the call – The terminal equipment does not recognize (i.e. ignore) either the AAL parameters, B-HLI or B-LLI information elements. There is a danger that a terminal equipment which has incorrect functionality will accept the call.
+
+Therefore, in order to assure compatibility with incoming calls, it is recommended that the terminal equipment check the B-LLI, B-HLI and AAL parameter information elements.
+
+NOTE – Some terminal equipment, upon agreement with other users or in accordance with other standards (e.g. Recommendation X.213), may employ the user-to-user information element for additional compatibility checking. Such terminal equipment shall check the user-to-user information element in a manner identical to that described here for the Broadband high layer information information element assured case.
+
+# **Annex C**
+
+## **Broadband low layer information negotiation**
+
+(This annex forms an integral part of this Recommendation)
+
+This annex describes additional procedures for the use of the Broadband Low Layer Information (B-LLI) information element by the user.
+
+## **C.1 General**
+
+The purpose of the B-LLI information element is to provide a means which should be used for compatibility checking by an addressed entity (e.g. a remote user or an interworking unit or high layer function network node addressed by the calling user). The B-LLI information element is transferred transparently by a B-ISDN between the call originating entity (e.g. the calling user) and the addressed entity.
+
+The user information protocol fields of the B-LLI information element indicate the low layer protocols (i.e. layer 3 and layer 2 protocols above the AAL) used between endpoints (users). This information is not interpreted by the B-ISDN and therefore the bearer capability provided by the B-ISDN is not affected by this information. The addressed entity may modify the low layer attributes by the negotiation described below if that can be supported by the bearer capability actually provided by the B-ISDN.
+
+The Broadband low layer information information element is coded according to 4.5.9.
+
+## **C.2 Low layer compatibility notification to the called user**
+
+When the calling user wishes to notify the called user of its low layer protocols above the ATM adaptation layer (i.e. as identified in octets 6 and 7 of the B-LLI information element) to be used during the call, then the calling user shall include a B-LLI information element in the SETUP message; this element is conveyed by the network and delivered to the called user. However, if the network is unable to convey this information element, it shall act as described in 5.6.8.1 (unrecognized information element).
+
+## **C.3 B-LLI negotiation between users**
+
+The B-LLI supports the indication of certain parameters of acknowledged mode HDLC elements of procedures. If they are included, parameter(s) may be negotiated. In this case, the called user accepting the call may include a B-LLI information element in the CONNECT message. This element will be conveyed transparently by the network and delivered to the calling user in the CONNECT message. If the calling user can not support the parameters in the CONNECT message, the calling user shall initiate call clearing procedures as described in 5.4.3.
+
+NOTE – The lower layer protocol parameters which may be negotiated by this capability are: mode (octet 6a), window size (octet 6b), user-specified layer 2 information (octet 6a), default packet size (octet 7b), and packet window size (octet 7c).
+
+If, for any reason, the network is unable to convey this information element, it shall act as described in 5.6.8.1 (unrecognized information element) except that the cause value No. 43, “access information discarded” shall be used in the STATUS message.
+
+If the calling user rejects the B-LLI information element contents in the CONNECT message, the calling user shall initiate clearing with cause No. 100, “invalid information element contents”.
+
+## **C.4 Alternate requested values**
+
+If the calling user wishes to indicate alternative values of B-LLI parameters (e.g. alternative protocol suites or protocol parameters), the B-LLI information element is repeated in the SETUP message. Up to three B-LLI information elements may be included in a SETUP message. The first B-LLI information element in the message is preceded by the Broadband repeat indicator information element specifying “priority list for selecting one possibility (descending order of priority)”. The order of appearance of the B-LLI information elements indicates the order of preference of end-to-end low layer parameters.
+
+If the network or called user does not support repeating of the B-LLI information element, and therefore discards the Broadband repeat indicator information element and the subsequent B-LLI information elements, only the first B-LLI information element is used in the negotiation. In addition, if the network discards the B-LLI information element, it shall send a STATUS message with cause value No. 43, “access information discarded”.
+
+The called user indicates a single choice from among the options offered in the SETUP message by including the B-LLI information element in the CONNECT message. Absence of a B-LLI information element in the CONNECT message indicates acceptance of the first B-LLI information element in the SETUP message.
+
+If the calling user rejects the B-LLI information element contents in the CONNECT message, the calling user shall initiate clearing with cause No. 100, “invalid information element contents”.
+
+# Annex D
+
+## Transit network selection
+
+(This annex forms an integral part of this Recommendation)
+
+This annex describes the processing of the transit network selection information element.
+
+## D.1 Selection not supported
+
+Some networks may not support transit network selection. In this case, when a Transit network selection information element is received, that information element is processed according to the rules for unimplemented non-mandatory information elements (see 5.6.8.1).
+
+## D.2 Selection supported
+
+When transit network selection is supported, the user identifies the selected transit network(s) in the SETUP message. One Transit network selection information element is used to convey a single network identification.
+
+The user may specify more than one transit network. Each identification is placed in a separate information element. The call would then be routed through the specified transit networks in the order listed in the SETUP. For example, a user lists networks A and B, in that order, in two Transit network selection information elements within a SETUP message. The call is first routed to network A (either directly or indirectly), and then to network B (either directly or indirectly), before being delivered.
+
+As the call is delivered to each selected network, the corresponding transit selection may be stripped from the call establishment signalling, in accordance with the relevant inter network signalling arrangement. The Transit network selection information element(s) is/are not delivered to the called user.
+
+No more than four Transit network selection information elements may be used in a single SETUP message.
+
+When a network cannot route the call due to insufficient bandwidth, the network shall initiate call clearing in accordance with 5.4, with cause No. 37, "user cell rate unavailable".
+
+If a network does not recognize the specified Transit network, the network shall initiate call clearing in accordance with 5.4, with cause No. 2, "no route to specified transit network". The diagnostic field shall contain a copy of the contents of the Transit network selection information element identifying the unreachable network.
+
+A network may screen all remaining Transit network selection information elements to:
+
+- a) avoid routing loops; or
+- b) ensure an appropriate business relationship exists between selected networks; or
+- c) ensure compliance with national and local regulations.
+
+If the transit network selection is of an incorrect format, or fails to meet criteria a), b) or c), the network shall initiate call clearing in accordance with 5.4, with cause No. 91, "invalid transit network selection".
+
+When a user includes the Transit network selection information element, pre-subscribed default transit network selection information (if any) is overridden.
+
+# Annex E
+
+## Mapping functions to support 64 kbit/s based circuit-mode ISDN services in B-ISDN and interworking between N-ISDN and B-ISDN (DSS 1/DSS 2)
+
+(This annex forms an integral part of this Recommendation)
+
+## E.1 Introduction
+
+This annex specifies the functions to be performed by an Interworking Function (IWF) installed between the B-ISDN and the N-ISDN. As regards the mapping function, only the interworking between the access protocols involved is covered. Interworking scenarios including the B-ISUP and the N-ISUP protocols are out of the scope of this annex.
+
+The communication scenario is described in Annex A/I.580 [58], scenario B. It should be noted that the functions and the mapping described in this section also apply to a Terminal Adapter (TA) at the UNI connecting a N-ISDN terminal to a B-ISDN network.
+
+Interworking functions between N-ISDN and B-ISDN are only provided for circuit-mode 64 kbit/s based N-ISDN services. Interworking functions to support packet and frame mode bearer services are not in the scope of this Recommendation.
+
+For the interworking functions between N-ISDN and B-ISDN, the following principles shall apply:
+
+### A) *Interworking B-ISDN → N-ISDN*
+
+- 1) If a B-ISDN specific service is requested at the DSS 2 side of the IWF, the call shall be rejected by the IWF.
+- 2) If a N-ISDN service is requested at the DSS 2 side of the IWF but the bearer class in the B-BC information element does not indicate BCOB-A, then the call shall be rejected by the IWF. The same applies when the ATM traffic descriptor and/or the AAL parameters information elements do not specify values in accordance with E.4.
+- 3) In the direction from DSS 2 to DSS 1, the IWF places the information elements to be transferred to the N-ISDN side into the ascending order required by Recommendation Q.931.
+
+### B) *Interworking N-ISDN → B-ISDN*
+
+- 1) If the IWF receives a request for a N-ISDN service at its DSS 1 side, it will select an ATM user cell rate for the B-ISDN side which is able to carry the 64 kbit/s (or n x 64 kbit/s) bit rate of the N-ISDN service.
+- 2) If the IWF receives a request for a N-ISDN service at its DSS 1 side, it will select Bearer Class A (CBR, CO, end-to-end timing required), and AAL type 1 or the AAL for voice as default values for the B-ISDN side. The value for the field “susceptibility to clipping” in the B-BC information element is set to “susceptible to clipping”.
+
+## E.2 Mapping functions for the direction DSS 2 → DSS 1
+
+The mapping functions performed by the IWF for the direction from DSS 2 to DSS 1 are illustrated by the examples given below. These examples are not exhaustive. The same mapping principles also apply for other circuit-switched N-ISDN services.
+
+The IWF will relay the content of the N-BC, N-LLC and N-HLC information elements transparently to the N-ISDN. No further processing is required, except for the changes needed to accommodate the different coding rules. The B-BC, ATM traffic descriptor, QOS parameter, end-to-end transit delay, OAM traffic descriptor and AAL parameters information elements are discarded.
+
+### E.2.1 A B-ISDN user requests the 3.1 kHz audio N-ISDN bearer service
+
+See Table E.1.
+
+TABLE E.1/Q.2931
+
+##### **Mapping performed by the IWF for the 3.1 kHz audio bearer service (direction DSS 2 → DSS 1)**
+
+| | |
+|-------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|
+| DSS 2:
Emulation of the N-ISDN bearer service 3.1 kHz audio | DSS 1:
3.1 kHz audio bearer service |
+| N-BC: – 3.1 kHz audio
– Circuit mode
– 64 kbit/s
– Rec. G.711, A- or µ-law | BC: – 3.1 kHz audio
– Circuit mode
– 64 kbit/s
– Rec. G.711, A- or µ-law |
+| N-HLC: Optional | HLC: Present, if provided |
+| N-LLC: Optional | LLC: Present, if provided |
+| B-BC: – BCOB-A
– Susceptible to clipping | – |
+| ATM traffic descriptor: Equal to 64 kbit/s | – |
+| Quality of Service: Unspecified QOS class | – |
+| AAL parameters: AAL for voice | – |
+| End-to-end transit delay: See 4.5.17 (optional) | – |
+| OAM traffic descriptor: See 4.5.24 (optional) | – |
+
+#### E.2.2 A B-ISDN user requests the N-ISDN unrestricted digital information bearer service
+
+See Table E.2.
+
+TABLE E.2/Q.2931
+
+##### **Mapping performed by the IWF for the unrestricted digital information bearer service (direction DSS 2 → DSS 1)**
+
+| | |
+|-----------------------------------------------------------------------------------|-------------------------------------------------------------------------|
+| DSS 2:
Emulation of the N-ISDN unrestricted digital information bearer service | DSS 1:
Unrestricted digital information bearer service |
+| N-BC: – Unrestricted digital information
– Circuit mode
– 64 kbit/s | BC: – Unrestricted digital information
– Circuit mode
– 64 kbit/s |
+| N-HLC: Optional | HLC: Present, if provided |
+| N-LLC: Optional | LLC: Present, if provided |
+| B-BC: – BCOB-A
– Susceptible to clipping | – |
+| ATM traffic descriptor: Equal to 64 kbit/s | – |
+| Quality of Service: Unspecified QOS class | – |
+| AAL parameters: AAL type 1 | – |
+| End-to-end transit delay: See 4.5.17 (optional) | – |
+| OAM traffic descriptor: See 4.5.24 (optional) | – |
+
+#### E.2.3 A B-ISDN user requests the N-ISDN telephony teleservice
+
+See Table E.3.
+
+TABLE E.3/Q.2931
+
+##### **Mapping performed by the IWF for the N-ISDN telephony teleservice (direction DSS 2 → DSS 1)**
+
+| | |
+|-----------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
+| DSS 2:
Emulation of the N-ISDN telephony teleservice | DSS 1:
Telephony teleservice |
+| N-BC: – Speech
– Circuit mode
– 64 kbit/s
– Rec. G.711, A- or $\mu$ -law | BC: – Speech
– Circuit mode
– 64 kbit/s
– Rec. G.711, A- or $\mu$ -law |
+| N-HLC: Telephony | HLC: Telephony |
+| N-LLC: Optional | LLC: Present, if provided |
+| B-BC: – BCOB-A
– Susceptible to clipping | – |
+| ATM traffic descriptor: Equal to 64 kbit/s | – |
+| Quality of Service: Unspecified QOS class | – |
+| AAL parameters: AAL for voice | – |
+| End-to-end transit delay: See 4.5.17 (optional) | – |
+| OAM traffic descriptor: See 4.5.24 (optional) | – |
+
+#### E.2.4 A B-ISDN user requests the N-ISDN videotelephony teleservice based on the unrestricted digital information with tones/announcements bearer capability
+
+See Table E.4.
+
+TABLE E.4/Q.2931
+
+##### **Mapping performed by the IWF for the videotelephony teleservice (direction DSS 2 → DSS 1)**
+
+| | |
+|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|
+| DSS 2:
Emulation of the N-ISDN videotelephony teleservice | DSS 1:
Videotelephony teleservice |
+| N-BC: – Unrestricted digital information
with tones/announcements
– Circuit mode
– 64 kbit/s
– Recommendations H.221 and H.242 | BC: – Unrestricted digital information
with tones/announcements
– Circuit mode
– 64 kbit/s
– Recommendations H.221 and H.242 |
+| N-HLC: Videotelephony (Recommendation F.721) | HLC: Videotelephony (Recommendation F.721) |
+| N-LLC: Optional | LLC: Present, if provided |
+| B-BC: – BCOB-A
– Susceptible to clipping | – |
+| ATM traffic descriptor: Equal to 64 kbit/s | – |
+| Quality of Service: Unspecified QOS class | – |
+| AAL parameters: See E.4 | – |
+| End-to-end transit delay: See 4.5.17 (optional) | – |
+| OAM traffic descriptor: See 4.5.24 (optional) | – |
+
+## E.3 Mapping functions for the direction DSS 1 → DSS 2
+
+The mapping functions performed by the IWF for the direction from DSS 1 to DSS 2 are illustrated by the examples given below. These examples are not exhaustive. The same principles also apply to other circuit-switched ISDN services.
+
+The IWF will relay the content of the BC, LLC and HLC information elements transparently to the B-ISDN. No further processing is required, except for the changes needed to accommodate the different coding rules. The B-BC, ATM traffic descriptor, QOS parameter, and AAL parameters information elements are generated by the IWF, using default values specified in E.4 and the information provided by the DSS 1 information elements.
+
+The “susceptibility to clipping” field of the B-BC information element in DSS 2 is always set to “susceptible to clipping”.
+
+#### E.3.1 A N-ISDN user requests the 3.1 kHz audio bearer service
+
+See Table E.5.
+
+TABLE E.5/Q.2931
+
+##### Mapping performed by the IWF for the 3.1 kHz audio bearer service (direction DSS 1 → DSS 2)
+
+| | |
+|----------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|
+| DSS 1:
3.1 kHz audio bearer service | DSS 2:
Emulation of the N-ISDN 3.1 kHz audio bearer service |
+| BC: – 3.1 kHz audio
– Circuit mode
– 64 kbit/s
– Rec. G.711, A- or $\mu$ -law | N-BC: – 3.1 kHz audio
– Circuit mode
– 64 kbit/s
– Rec. G.711, A- or $\mu$ -law |
+| HLC: Optional | N-HLC: Present, if provided |
+| LLC: Optional | N-LLC: Present, if provided |
+| – | B-BC: See E.4 |
+| – | ATM traffic descriptor: See E.4 |
+| – | Quality of Service: See E.4 |
+| – | AAL parameters: See E.4 |
+
+#### E.3.2 A N-ISDN user requests the unrestricted digital information bearer service
+
+See Table E.6.
+
+TABLE E.6/Q.2931
+
+##### **Mapping performed by the IWF for the unrestricted digital information bearer service (direction DSS 1 → DSS 2)**
+
+| | |
+|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------|
+| DSS 1:
Unrestricted digital information bearer service | DSS 2:
Emulation of the N-ISDN unrestricted digital information bearer service |
+| BC: – Unrestricted digital information
– Circuit mode
– 64 kbit/s | N-BC: – Unrestricted digital information
– Circuit mode
– 64 kbit/s |
+| HLC: Optional | N-HLC: Present, if provided |
+| LLC: Optional | N-LLC: Present, if provided |
+| – | B-BC: See E.4 |
+| – | ATM traffic descriptor: See E.4 |
+| – | Quality of Service: See E.4 |
+| – | AAL parameters: See E.4 |
+
+#### E.3.3 A N-ISDN user requests the telephony teleservice
+
+See Table E.7.
+
+TABLE E.7/Q.2931
+
+##### **Mapping performed by the IWF for the telephony teleservice (direction DSS 1 → DSS 2)**
+
+| | |
+|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|
+| DSS 1:
Telephony teleservice | DSS 2:
Emulation of the N-ISDN telephony teleservice |
+| BC: – Speech
– Circuit mode
– 64 kbit/s
– Rec. G.711, A- or $\mu$ -law | N-BC: – Speech
– Circuit mode
– 64 kbit/s
– Rec. G.711, A- or $\mu$ -law |
+| HLC: Telephony | N-HLC: Telephony |
+| LLC: Optional | N-LLC: Present, if provided |
+| – | B-BC: See E.4 |
+| – | ATM traffic descriptor: See E.4 |
+| – | Quality of Service: See E.4 |
+| – | AAL parameters: See E.4 |
+
+#### **E.3.4 A N-ISDN user requests the videotelephony teleservice based on the unrestricted digital information with tones/announcements bearer capability**
+
+See Table E.8.
+
+TABLE E.8/Q.2931
+
+##### **Mapping performed by the IWF for the videotelephony teleservice (direction DSS 1 → DSS 2)**
+
+| | |
+|---------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| DSS 1:
Videotelephony teleservice | DSS 2:
Emulation of the N-ISDN videotelephony teleservice |
+| BC: – Unrestricted digital information with tones/announcements
– Circuit mode
– 64 kbit/s
– Recommendations H.221 and H.242 | N-BC: – Unrestricted digital information with tones/announcements
– Circuit mode
– 64 kbit/s
– Recommendations H.221 and H.242 |
+| HLC: Videotelephony (Recommendation F.721) | N-HLC: Videotelephony (Recommendation F.721) |
+| LLC: Optional | N-LLC: Present, if provided |
+| – | B-BC: See E.4 |
+| – | ATM traffic descriptor: See E.4 |
+| – | Quality of Service: See E.4 |
+| – | AAL parameters: See E.4 |
+
+## **E.4 Codepoint values of information elements to support 64 kbit/s based circuit-mode ISDN services in B-ISDN**
+
+#### **E.4.1 Introduction**
+
+This subclause provides the codepoint values of B-ISDN specific information elements to support 64 kbit/s based circuit-mode ISDN services in B-ISDN. The codepoints shall be used by terminal equipment connected to the B-ISDN if it requests a N-ISDN service and by an IWF for generation of the appropriate B-ISDN codepoints.
+
+### **E.4.2 Codepoints of information elements used for emulated N-ISDN services**
+
+#### **E.4.2.1 Broadband bearer capability**
+
+| Octet | Information element field | Field value |
+|-------|-------------------------------------|-------------------------|
+| 5 | Bearer class | BCOB-A |
+| 6 | Susceptibility to clipping | Susceptible to clipping |
+| | User plane connection configuration | Point-to-point |
+
+#### E.4.2.2 ATM traffic descriptor
+
+##### E.4.2.2.1 ATM traffic descriptor for N-BC information transfer capabilities of unrestricted digital information and restricted digital information
+
+| Octet | Information element field | Field value if no OAM cells are used (Note 1) | Field value if 1 OAM cells/sec. is used (Note 2) | Field value with maximal OAM support (Note 3) |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|---------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------------|
+| 7.1
7.2
7.3 | Forward peak cell rate
(CLP = 0 + 1) | 0000 0000
0000 0000
1010 1011
(171 cells/sec.) | 0000 0000
0000 0000
1010 1100
(172 cells/sec.) | 0000 0000
0000 0000
1010 1111
(175 cells/sec.) |
+| 8.1
8.2
8.3 | Backward peak cell rate
(CLP = 0 + 1) | 0000 0000
0000 0000
1010 1011
(171 cells/sec.) | 0000 0000
0000 0000
1010 1100
(172 cells/sec.) | 0000 0000
0000 0000
1010 1111
(175 cells/sec.) |
+| NOTES
1 These values are based on an AAL type 1 payload of 47 octets per cell (i.e. no partially filled cell) for user information and no cell rate allocation for OAM cells.
2 These values are based on an AAL type 1 payload of 47 octets per cell (i.e. no partially filled cell) for user information and on 1 cell/sec. allocation for OAM cells.
3 These values are based on an AAL type 1 payload of 47 octets per cell (i.e. no partially filled cell) for user information and the following cell rate allocation for OAM: two percent of the user cell rate and an additional 1 cell/sec. | | | | |
+
+##### E.4.2.2.2 ATM traffic descriptor for N-BC information transfer capabilities of speech and 3.1 kHz audio
+
+The field values used for these information transfer capabilities are for further study (see Recommendation I.580 [58]).
+
+#### E.4.2.3 QOS parameter
+
+| Octet | Information element field | Field value |
+|-------|---------------------------|-----------------------|
+| 5 | QOS-class forward | Unspecified QOS class |
+| 6 | QOS-class backward | Unspecified QOS class |
+
+#### E.4.2.4 AAL parameters
+
+##### E.4.2.4.1 AAL parameters for N-BC information transfer capabilities of unrestricted digital information and restricted digital information
+
+| Octet | Information element field | Field value |
+|-----------|-------------------------------------|---------------------------------------|
+| 5 | AAL-Type | 0000 0001 (AAL Type 1) |
+| 6.1 | Subtype | 0000 0010 (circuit transport) |
+| 7.1 | CBR Rate | 0000 0001 (64 kbit/s) |
+| 9.1 | Source Clock Frequency | 0000 0000 (Null) (Note) |
+| 10.1 | Error Correction method | 0000 0000 (Null) (Note) |
+| 11.1/11.2 | Structured data transfer block size | 0000 0000 0000 0000 (block size of 1) |
+| 12.1 | Partially filled cells method | 0000 0000 (Null) (Note) |
+
+NOTE – These fields may also be absent which is equivalent to the null coding.
+
+###### E.4.2.4.2 AAL parameters for N-BC information transfer capabilities of speech and 3.1 kHz audio
+
+| Octet | Information element field | Field value |
+|-------|---------------------------|---------------------------|
+| 5 | AAL-Type | 0000 0000 (AAL for voice) |
+
+###### E.4.2.4.3 AAL parameters for N-BC information transfer capabilities of unrestricted digital information with tones/announcements
+
+The field values used for this information transfer capability are for further study.
+
+# Annex F
+
+## ATM adaptation layer parameters indication and negotiation
+
+(This annex forms an integral part of this Recommendation)
+
+This annex describes procedures for the use of the ATM adaptation layer parameters information element by endpoint equipment.
+
+## F.1 General
+
+The purpose of the ATM adaptation layer parameters information element is to provide a means which may be used for conveying information related to the ATM adaptation layer between endpoints. The ATM adaptation layer parameters information element is transferred transparently between ATM endpoints by the network.
+
+## F.2 ATM adaptation layer parameter indication in the SETUP message
+
+When the calling endpoint wishes to indicate to the called endpoint the AAL common part parameters and service specific part to be used during the call, the calling endpoint shall include an ATM adaptation layer parameters information element in the SETUP message. This information element is conveyed by the network and delivered to the called user.
+
+The ATM adaptation layer parameters information element may include the following parameters for different AAL connection types:
+
+- a) *For AAL Connection type 1*
+ - Subtype;
+ - CBR Rate;
+ - Source Clock Frequency Recovery Method;
+ - Error Correction;
+ - Structured Data Transfer Blocksize;
+ - Partially Filled Cells Indicator.
+- b) *For AAL Connection type 3/4*
+ - Forward Maximum CPCS-SDU size;
+ - Backward Maximum CPCS-SDU size;
+ - MID range;
+ - SSCS Type.
+- c) *For AAL Connection type 5*
+ - Forward Maximum CPCS-SDU size;
+ - Backward Maximum CPCS-SDU size;
+ - SSCS Type.
+
+NOTE – Forward maximum CPCS-SDU size and backward maximum CPCS-SDU size shall either both be present or both be absent in the ATM adaptation layer parameters information element. For unidirectional ATM virtual connections, the backward maximum CPCS-SDU size shall be set to “0”.
+
+If the called endpoint receives an ATM adaptation layer parameters information element in the SETUP message which contains the forward or backward maximum CPCS-SDU size but not both, the called endpoint should clear the call with cause No. 100, “invalid information element contents”.
+
+## F.3 Maximum CPCS-SDU size negotiation
+
+When the called user has received an ATM adaptation layer parameters information element in a SETUP message and the AAL type is either AAL 3/4 or AAL 5, the ATM adaptation layer parameters information element shall be included in the CONNECT message. The ATM adaptation layer parameters information element shall include the forward maximum CPCS-SDU size, indicating the size of the largest CPCS-SDU that the called user is able to receive, and the backward maximum CPCS-SDU size, indicating the size of the largest CPCS-SDU that it will transmit. The values for the forward and backward maximum CPCS-SDU size indicated in the CONNECT message shall not be greater than the values indicated by the calling user in the SETUP message. The ATM adaptation layer parameters information element will be conveyed to the calling user.
+
+NOTE – For unidirectional ATM virtual connections, the backward maximum CPCS-SDU size shall be set to 0.
+
+If the called user does not include the CPCS-SDU size in the CONNECT message, the calling user shall assume that the called user accepts the values of the forward and backward maximum CPCS-SDU size indicated by the calling user in the SETUP message.
+
+If the calling party cannot use the forward or backward maximum CPCS-SDU size indicated in the CONNECT message (i.e. because the value negotiated by the called party is unacceptably small), then the call shall be cleared with cause No. 93, “AAL parameters can not be supported”.
+
+If the calling endpoint receives an ATM adaptation layer parameters information element in the CONNECT message which:
+
+- a) contains octet groups other than the forward and backward maximum CPCS-SDU size and/or MID range;
+- b) contains a maximum SDU size which is greater than the maximum SDU size which was sent in the SETUP message; or
+- c) is missing the forward or backward maximum CPCS-SDU size;
+
+the calling endpoint should clear the call with cause No. 100, "invalid information element contents".
+
+## **F.4 MID range negotiation**
+
+When the called user receives the ATM adaptation layer parameters information element in the SETUP message which indicates AAL type 3/4, the called user shall check the MID range value. If the called user cannot support the indicated MID range but it can support a smaller range, the called user includes an ATM adaptation layer parameters information element in the CONNECT message containing the MID range that it can support.
+
+The calling user will either accept the MID range contained in the CONNECT message or will clear the call with cause No. 93, "AAL parameters can not be supported".
+
+If the called user does not include the MID range in the CONNECT message, the calling user shall assume that the called user accepts the MID range indicated by the calling user in the SETUP message.
+
+If the calling endpoint receives an ATM adaptation layer parameters information element in the CONNECT message which:
+
+- a) contains octet groups other than the forward and backward maximum CPCS-SDU size and/or MID range; or
+- b) contains a MID range which is greater than the MID range which was sent in the SETUP message;
+
+the calling endpoint should clear the call with cause No. 100, "invalid information element contents".
+
+## **F.5 Use of forward and backward maximum CPCS-SDU size by the AAL entity in the user plane**
+
+The values of forward and backward maximum CPCS-SDU size resulting from AAL parameters negotiation shall be used by the AAL entities in the user plane. The AAL entity in the calling user equipment shall not send a CPCS-SDU size larger than the indicated value specified in the forward maximum CPCS-SDU size parameter, and may allocate its internal resources based on the value indicated in the backward maximum CPCS-SDU size parameter. Similarly, the AAL entity in the called user equipment shall not send a CPCS-SDU size larger than the indicated value specified in the backward maximum CPCS-SDU size parameter, and may allocate its internal resources based on the value indicated in the forward maximum CPCS-SDU size parameter.
+
+# **Annex G**
+
+This annex is reserved for future use.
+
+# Annex H
+
+## Extensions for symmetric call operation
+
+(This annex forms an integral part of this Recommendation)
+
+For support of symmetric call operation on a point-to-point access configuration, the additional optional procedures detailed below are required:
+
+- 1) When call establishment information is received, a CALL PROCEEDING, an ALERTING or a CONNECT message, as appropriate, is transferred across the interface.
+- 2) Upon receipt of a SETUP message, the equipment enters the Call Present state. Valid response to the SETUP message is a CALL PROCEEDING, an ALERTING, a CONNECT or a RELEASE COMPLETE message.
+- 3) At the originating interface:
+ - When the user receives the ALERTING message, the user may begin an internally generated alerting indication; stop T303 or T310 (if running) and shall enter the Call Delivered state.
+ - On receipt of the CONNECT message, the calling user shall stop timer T303 or T310 (if running) in addition to procedures described in 5.1.7.
+- 4) User endpoints implement the network side timer T301 along with the corresponding network side procedures for actions taken upon expiration of the timer.
+
+# Annex I
+
+## Handling of the OAM traffic descriptor
+
+(This annex forms an integral part of this Recommendation)
+
+The use of the Operation And Maintenance information flows, in particular of the end-to-end OAM F5 for fault management and for performance monitoring, is defined in Recommendation I.610.
+
+## I.1 Use of the OAM traffic descriptor information element
+
+The OAM traffic descriptor information element is included by the calling user in the SETUP message to provide a specification of the end-to-end OAM flow as a fraction of the aggregate of the user and end-to-end OAM F5 flow.
+
+The OAM traffic descriptor information element defined in 4.5.24 may, optionally, be included in the SETUP message by the calling user; however, its absence does not in itself mean that no OAM flow will be used within this call (see 3.1.7). The support of this information element is network dependent.
+
+If the network or the user does not support this information element, it shall be treated as an unrecognized information element according to the procedures defined in 5.6.
+
+## I.2 Handling of the OAM traffic descriptor information element in the SETUP message
+
+If supported, the network shall, as a minimum, transfer this information element and include it in the SETUP message delivered to the called user. Once the call and the connection are established and the CONNECT message has been received by the calling user, the calling user and the called user will negotiate the use of the end-to-end OAM F5 information flow according to the procedures defined by Recommendation I.610.
+
+The use of an ATM traffic shaping is a network option, if no ATM traffic shaping is applied, the network shall transfer the Shaping indicator subfield of the OAM traffic descriptor information element transparently to the destination user.
+
+The Shaping indicator subfield shall be interpreted by networks which apply ATM traffic shaping.
+
+Networks which apply ATM traffic shaping but cannot support the user request to avoid aggregate ATM user information and end-to-end OAM F5 flow shaping shall clear the call and return cause No. 63, "service or option not available, unspecified", to the calling user.
+
+In the case of separate shaping required by the user, the network may shape only the user data information flow on the basis of its specific Peak Emission Interval (or Peak Cell Rate), letting the OAM information flow by-pass the shaping function, provided that the network can accommodate the resulting traffic incurred by the OAM cell stream. If, as a network option, the network performs traffic shaping in conjunction with suitable Usage Parameter Control (UPC) function, the network may perform user data and OAM F5 aggregate shaping or separate shaping, according to the requirement specified by the user in the Shaping indicator field of the OAM traffic descriptor information element.
+
+The handling of the ATM traffic descriptor information element in conjunction with the OAM traffic descriptor information element, when supported, for the purpose of Call Admission Control (CAC), Usage or Network Parameter Control (UPC and NPC) and traffic shaping shall be performed according to Recommendation I.371.
+
+## **I.3 Procedure at the destination user-network interface**
+
+The called user shall, if it supports the OAM traffic descriptor information element and the specified OAM traffic descriptor, include the corresponding OAM traffic descriptor information element in the CONNECT message returned to the network. The network shall then transfer transparently this OAM traffic descriptor information element and deliver it to the calling user in the CONNECT message, to confirm the availability of the end-to-end OAM F5 flow.
+
+If the OAM traffic descriptor is not included by the called user in the CONNECT message and if its Compliance indicator was set to "mandatory" in the SETUP message, the destination exchange shall initiate call clearing and send cause No. 63, "service or option not available, unspecified", to the called user and to the calling user. If the Compliance indicator was set to "optional" in the SETUP message, the call completion shall proceed. The calling user shall interpret the absence of the OAM traffic descriptor in the received CONNECT message as an indication that the end-to-end OAM F5 flow is not available.
+
+NOTE – In the case of interworking with non-B-ISDN, the Interworking function may discard the OAM traffic descriptor information element and continue the establishment of the call. Therefore the calling user should interpret the absence of the OAM traffic descriptor information element in the received CONNECT message as an indication that the end-to-end OAM F5 flow is not available even if the Compliance indicator was set to "mandatory" in the SETUP message.
+
+# **Annex J**
+
+## **Definitions, Abbreviations and References**
+
+(This annex forms an integral part of this Recommendation)
+
+## **J.1 Definitions**
+
+For the purposes of this Recommendation, the following definition apply:
+
+**J.1.1 access:** The set of equipment at a point of a network where a user connects to it. This includes the user equipment and the equipment in the network to which the user connects, i.e. the exchange termination, network termination and terminal equipment.
+
+**J.1.2 access information:** Information contained in access information elements. These information elements are transported transparently through the network without being processed. They have only end-to-end relevance.
+
+**J.1.3 access information elements:** A generic term for the following information elements:
+
+- Narrow-band low layer compatibility;
+- Narrow-band high layer compatibility;
+- Broadband low layer information;
+- Broadband high layer information;
+
+- AAL parameters;
+- Calling party sub-address;
+- Called party sub-address.
+
+Other Recommendations may also define additional information elements as access information elements.
+
+**J.1.4 alert:** The action of attempting to make a user aware that a call is waiting to be answered at his terminal, for example by ringing the telephone bell.
+
+**J.1.5 answer (a call):** The response of a user when he accepts a call to which he has been alerted, for example by lifting the telephone handset off the hook when it is ringing.
+
+**J.1.6 asynchronous transfer mode (ATM):** A transfer mode in which the information is organized into cells; it is asynchronous in the sense that the recurrence of cells containing information from an individual user is not necessarily periodic. It is a protocol within the OSI layer 1. An ATM cell consists of a 5 octet header followed by 48 octets of data. See also Recommendation I.361.
+
+**J.1.7 ATM adaptation layer (AAL):** The AAL enhances the service provided by the ATM layer to support functions required by the next higher layer. It is an OSI layer 2 protocol. The AAL is different, depending on the needs of the next higher layer. This Recommendation uses an AAL called Signalling AAL. See also Recommendations I.362, I.363 and Q.2100.
+
+**J.1.8 ATM cell header:** This contains a VPI, a VCI and other information necessary for functions such as routing the cell, cell delineation and maintenance. It has a different format depending on what part of the network it is being used in.
+
+**J.1.9 backward:** The backward direction is defined as the direction from the called user to the calling user.
+
+**J.1.10 basic call/connection control:** The set of functions used to process a basic call and associated connections (e.g. provide service features and establish, supervise, maintain and release connections). A basic call is a simple call between two parties without any supplementary services being active.
+
+**J.1.11 broadband connection oriented bearer service:** A bearer service that establishes logical connections between users before transferring digital information. In general, information transfer is in real time, in sequence and bidirectional. The service attempts to deliver information unchanged from source to destination. Parameters such as transfer delay, bit rate in each direction and constant or variable bit rate can be specified by the user. See also Recommendation F.811.
+
+**J.1.12 broadband ISDN:** An ISDN that provides transmission channels capable of supporting rates greater than 2 Mbits/s. It uses ATM as the transfer mode. See also Recommendation I.311.
+
+**J.1.13 called user:** A user to which a call is made. Often called B-party.
+
+**J.1.14 calling user:** A user which initiates a call. Often called A-party.
+
+**J.1.15 circuit mode:** An information transfer mode in which transmission is achieved by allocation of constant bandwidth between transfer end points. It behaves as if a cable were placed between the end points. It is to be compared with packet mode.
+
+**J.1.16 clipping:** An impairment in which the first fraction of a second of information to be transferred is lost. It occurs after a call is answered and before an associated connection is switched through.
+
+**J.1.17 connection:** An association of transmission channels or circuits, switching and other functional units set up to provide a means of transfer of information between two or more points in a telecommunication network.
+
+**J.1.18 connection admission control:** The procedure within the control part of network nodes used to decide whether or not a request for a connection can be accepted based on the requested usage parameters and already established connections.
+
+**J.1.19 connection oriented:** An information transfer mode in which a connection is established between end users before information is transferred. Compare with connectionless.
+
+**J.1.20 connectionless:** An information transfer mode in which blocks of data to be transferred are individually addressed and routed to their destination. Compare with connection oriented.
+
+**J.1.21 cross-connect:** A network element which connects links and is directed by management plane functions and not by control plane functions. A VP cross-connect connects VP links; it translates VPI (not VCI) values. A VC cross-connect connects VC links; it terminates VPCs and translates VCI values. See also Recommendation I.311.
+
+**J.1.22 data link connection:** An error free connection provided by the data link layer (OSI layer 2). For the purposes of this Recommendation, it connects the user to the network and is provided by the signalling AAL.
+
+**J.1.23 dual seizure:** The condition when both the user and the network attempt to seize the same virtual channel at the same time for different connections.
+
+**J.1.24 *en bloc*:** A method of signalling the address in which all the address digits are sent in a single message. In *en bloc* sending, the user must be aware of the last digit in order to initiate sending of the message. Compare with overlap.
+
+**J.1.25 end-to-end:** Communication between terminals as opposed to communication between terminal and network or between network nodes.
+
+**J.1.26 field:** A contiguous set of bits in an information element that represent information.
+
+**J.1.27 forward:** The forward direction is defined as the direction from the calling user to the called user.
+
+**J.1.28 ignore:** The information shall be treated as if it was not received.
+
+**J.1.29 information element:** The components of a message are information elements. A particular information element type may be a component of more than one message type. An information element is composed of one or more octet groups.
+
+**J.1.30 integrated services digital network:** A network that provides or supports a range of different telecommunication services using digital connections.
+
+**J.1.31 interface:** The shared boundary between two entities across which they communicate.
+
+**J.1.32 interwork:** The act of translating signals from a source signalling system to a destination signalling system that is different, such that the meaning of the translated signals is as close to that of the original as possible.
+
+**J.1.33 layer 2:** The OSI data link layer. In this Recommendation, it refers to the SAAL.
+
+**J.1.34 layer 3:** The OSI network layer.
+
+**J.1.35 layer management:** Functions related to the management of the (N)-layer partly performed in the (N)-layer itself according to the (N)-protocol of the layer (activities such as activation and error control) and partly performed as a subset of systems-management. See also Recommendation X.200.
+
+**J.1.36 message:** A block of information that is sent from a source entity to one or more destination entities. It is sent as a result of an event taking place in the source entity that requires an action in the destination entities. In addition to informing of the event, a message may contain additional information necessary or helpful to the destination entities in reacting to the event. A message is composed of information elements. Ideally, a message occupies zero time. In practice, a message occupies an interval of time. This interval is due only to limitations in the equipment processing the message and is as short as possible.
+
+**J.1.37 meta-signalling:** A form of signalling used to establish a signalling relationship where none already exists. For the purposes of this Recommendation, the signalling relationship is a signalling virtual channel. See also Recommendation Q.2120.
+
+**J.1.38 narrow-band ISDN:** ISDN before the advent of broadband ISDN. It is called narrow-band ISDN in order to distinguish it from broadband ISDN.
+
+**J.1.39 network connection:** The part of a connection that is entirely within the network.
+
+**J.1.40 network termination:** The functional group on the network side of a user-network interface. It is not necessarily co-located with the local exchange.
+
+- J.1.41 octet:** A byte consisting of 8 bits. See clause 4.
+- J.1.42 octet group:** The components of an information element. See 4.5.1.
+- J.1.43 originating access:** The access used by the calling user.
+- J.1.44 overlap:** A method of signalling the address in which all the address digits are not sent in a single message, typically one message for each digit. The network may begin routing before all digits are received. The network may determine when enough digits have been received. Compare with *en bloc*.
+- J.1.45 peak cell rate:** The inverse of the minimum time interval between two requests to send an ATM-PDU. An ATM-PDU results in the transmission of a cell.
+- J.1.46 peer entities:** Communicating entities in the same OSI layer but in different systems. The entities communicate using the underlying OSI layers. See also Recommendation X.200.
+- J.1.47 permanent data link connection:** A data link connection that is established and released by subscription. It cannot be established, re-established or released by user equipment.
+- J.1.48 point-to-multipoint configuration (at the UNI):** A configuration where more than one terminal equipment is supported by a single network termination at a user-network interface.
+- J.1.49 protocol data unit:** A data unit that is transferred by a layer to its peer, i.e. across the lower boundary of the layer.
+- J.1.50 restart:** To return the indicated virtual channel to the idle state. See 5.5.
+- J.1.51 semi-permanent connection:** A connection that is established and released by subscription. It cannot be established, re-established or released by user equipment.
+- J.1.52 service access point:** The point at which an OSI layer provides services to the next higher layer.
+- J.1.53 service data unit:** A data unit that is transferred by a layer across a service access point, i.e. across the upper boundary of the layer.
+- J.1.54 signalling AAL:** The AAL that is used for signalling. It is the next lower OSI layer from Q.2931. See also Recommendation Q.2100.
+- J.1.55 signalling channel:** The bidirectional channel used for the transfer of Q.2931 messages.
+- J.1.56 signalling virtual channel:** The virtual channel used for the transfer of Q.2931 messages.
+- J.1.57 teleservice:** A type of telecommunication service that provides the complete capability, including terminal equipment functions, for communication between users according to protocols established by agreement between Administrations and/or ROAs.
+- J.1.58 terminal equipment:** The functional group on the user side of a user-network interface.
+- J.1.59 terminating access:** The access used by the called user.
+- J.1.60 user-network interface:** The shared boundary between the network and user terminal equipment across which they communicate.
+- J.1.61 virtual channel (VC):** A facility, provided by the ATM layer, for the transfer of digital data across an interface. The transfer is bidirectional, as near to real time as possible and in sequence. The data is sent in ATM cells. The VCI included in the cell header associates the data with the VC. The VCI is unique within the interface. See also Recommendation I.311.
+- J.1.62 virtual path (VP):** A grouping of one or more VCs. The VPI included in the ATM cell header associates the VCs with the VP. The VPI is unique within the interface. See also Recommendation I.311.
+- J.1.63 virtual path connection (VPC):** A concatenation of VP links that extends between the point where the VCI values are assigned and the point where those values are translated or removed. The VPI values of two concatenated VP links may be different. See also Recommendation I.311.
+
+## J.2 Abbreviations
+
+For the purposes of this Recommendation, the following abbreviations are used:
+
+| | |
+|----------|--------------------------------------------------------------------------------------------|
+| AAL | ATM Adaptation Layer |
+| AFI | Authority and Format Identifier |
+| ATM | Asynchronous Transfer Mode |
+| B-BC | Broadband Bearer Capability |
+| B-HLI | Broadband High Layer Information |
+| B-ISDN | Broadband ISDN |
+| B-LLI | Broadband Low Layer Information |
+| BC | Bearer Capability |
+| BCD | Binary Coded Decimal |
+| BCOB | Broadband Connection Oriented Bearer class |
+| CBR | Constant Bit Rate |
+| CLP | Cell Loss Priority |
+| CN | Customer Network |
+| CPCS-SDU | Common Part Convergence Sub-layer (of AAL) – Service Data Unit (see Recommendation Q.2130) |
+| DCE | Data Circuit terminating Equipment |
+| DSP | Domain Specific Part |
+| DTE | Data Terminal Equipment |
+| ET | Exchange Termination |
+| HLC | High Layer Compatibility |
+| HLI | High Layer Information |
+| IDI | Initial Domain Identifier |
+| IE | Information Element |
+| IEC | International Electrotechnical Commission |
+| ISDN | Integrated Services Digital Network |
+| ISO | International Organisation for Standardization |
+| IWF | Interworking Function |
+| LLC | Low Layer Compatibility |
+| LLI | Low Layer Information |
+| MID | Multiplexing Identifier (see Recommendation I.363) |
+| N-BC | Narrow-band Bearer Capability |
+| N-HLC | Narrow-band High Layer Compatibility |
+| N-ISDN | Narrow-band ISDN |
+| N-LLC | Narrow-band Low Layer Compatibility |
+| NPC | Network Parameter Control |
+| NSAP | Network Service Access Point |
+| OAM | Operations, Administration and Maintenance |
+| PDU | Protocol Data Unit |
+| QOS | Quality of Service |
+| SAAL | Signalling AAL |
+| SAP | Service Access Point |
+
+| | |
+|-------|------------------------------------------------------------------------------------|
+| SDT | Structured Data Transfer |
+| SPC | Semi-Permanent Connection |
+| SSCOP | Service Specific Connection Oriented Protocol (of AAL) (see Recommendation Q.2110) |
+| SSCS | Service Specific Convergence Sub-layer (of AAL) (see Recommendation Q.2130) |
+| SVC | Signalling Virtual Channel |
+| TE | Terminal Equipment |
+| UNI | User-Network Interface |
+| UPC | Usage Parameter Control |
+| VBR | Variable Bit Rate |
+| VC | Virtual Channel |
+| VCC | Virtual Channel Connection |
+| VCI | Virtual Channel Identifier |
+| VP | Virtual Path |
+| VPCI | Virtual Path Connection Identifier |
+| VPI | Virtual Path Identifier |
+
+## J.3 References
+
+The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of currently valid ITU-Recommendations is regularly published.
+
+- [1] Recommendation E.164, *Numbering plan for the ISDN era*.
+- [2] Recommendation F.811, *Broadband connection-oriented bearer service*.
+- [3] Recommendation G.711, *Pulse Code Modulation (PCM) of voice frequencies*.
+- [4] Recommendation G.721, *32 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM)*.
+- [5] Recommendation G.722, *7 kHz audio-coding within 64 kbit/s*.
+- [6] Recommendation H.221, *Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices*.
+- [7] Recommendation H.230, *Frame-synchronous control and indication signals for audiovisual systems*.
+- [8] Recommendation H.242, *System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s*.
+- [9] Recommendation I.230, *Definition of bearer service categories*.
+- [10] Recommendation I.240, *Definition of teleservices*.
+- [11] Recommendation I.311, *B-ISDN general network aspects*.
+- [12] Recommendation I.327, *B-ISDN functional architecture*.
+- [13] Recommendation I.330, *ISDN numbering and addressing principles*.
+- [14] Recommendation I.334, *Principles relating ISDN numbers/sub-addresses to the OSI reference model network layer addresses*.
+- [15] Recommendation I.361, *B-ISDN ATM layer specification*.
+- [16] Recommendation I.362, *B-ISDN ATM Adaptation Layer (AAL) functional description*.
+
+- [17] Recommendation I.363, *B-ISDN ATM Adaptation Layer (AAL) specification.*
+- [18] Recommendation I.371, *Traffic control and congestion control in B-ISDN.*
+- [19] Recommendation I.413, *B-ISDN user-network interface.*
+- [20] Recommendation I.460, *Multiplexing, rate adaption and support of existing interfaces.*
+- [21] Recommendation I.500, *General structure of the ISDN interworking Recommendations.*
+- [22] Recommendation I.610, *Organization and maintenance principles of the B-ISDN access.*
+- [23] ISO 1745, *Information processing basic mode control procedures for data communication systems.*
+- [24] ISO 4335, *Information technology – Telecommunications and information exchange between systems – High-level Data Link Control (HDLC) procedures – Elements of procedures.*
+- [25] ISO 7776, *Information processing systems – Data communications – High-level data link control procedures – Description of the X.25 LAPB compatible DTE data link procedures.*
+- [26] ISO/IEC 8208, *Information technology – Data communications – X.25 Packet Layer Protocol For Data Terminal Equipment.*
+- [27] ISO 8473, *Information processing systems – Data communications – Protocol for providing the connectionless-mode network service.*
+- [28] ISO 8802/2, *Information processing systems – Local area networks – Part 2: Logical link control.*
+- [29] ISO/IEC TR 9577, *Information technology – Telecommunications and information exchange between systems – Protocol identification in the network layer.*
+- [30] Recommendation Q.850, *Use of cause and location in the digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN user part.*
+- [31] Recommendation Q.921, *ISDN user-network interface – Data link layer specification.*
+- [32] Recommendation Q.922, *ISDN data link layer specification for frame mode bearer services.*
+- [33] Recommendation Q.931, *ISDN user-network interface layer 3 specification for basic call control.*
+- [34] Recommendation Q.933, *ISDN Digital Subscriber Signalling System No. 1 (DSS 1) – Signalling specification for frame mode bearer service.*
+- [35] Recommendation Q.2010, *Broadband integrated services digital network overview signalling capability set 1, release 1.*
+- [36] Recommendation Q.2120, *B-ISDN meta-signalling protocol.*
+- [37] Recommendation Q.2650, *Broadband-ISDN, – Interworking between Signalling System No. 7 broadband ISDN user part (B-ISUP) and Digital Subscriber Signalling System No. 2 (DSS 2).*
+- [38] Recommendation Q.2100, *B-ISDN Signalling ATM Adaptation Layer (SAAL) overview description.*
+- [39] Recommendation T.50/ISO 646, *International Alphabet No. 5.*
+- [40] Recommendation T.70, *Network-independent basic transport service for the telematic services.*
+- [41] Recommendation T.71, *Link Access Protocol Balanced (LAPB) extended for half-duplex physical level facility.*
+- [42] Recommendation T.90, *Characteristics and protocols for terminals for telematic services in ISDN.*
+- [43] Recommendation V.110/X.30, *Support of Data Terminal Equipments (DTEs) with V-Series type interfaces by an integrated services digital network.*
+
+- [44] Recommendation V.120, *Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing.*
+- [45] Recommendation X.25, *Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit.*
+- [46] Recommendation X.31, *Support of packet mode terminal equipment by an ISDN.*
+- [47] Recommendation X.75, *Packet-switched signalling system between public networks providing data transmission services.*
+- [48] Recommendation X.121, *International number plan for public data networks.*
+- [49] Recommendation X.200, *Reference model of Open Systems Interconnection for CCITT applications.*
+- [50] Recommendation X.213/ISO 8348, *Network service definition for Open Systems Interconnection for CCITT applications.*
+- [51] Recommendation X.223/ISO 8878, *Use of X.25 to provide the OSI connection-mode network service for CCITT applications.*
+- [52] Recommendation Q.2110, *B-ISDN ATM adaptation layer – Service Specific Connection Oriented Protocol (SSCOP).*
+- [53] Recommendation Q.2130, *B-ISDN signalling ATM adaptation layer – Service specific coordination function for support of signalling at the user-to-network interface (SSCF at UNI).*
+- [54] Recommendation Q.2761, *Broadband Integrated Services Digital Network (B-ISDN) – Functional description of the B-ISDN user part (B-ISUP) of Signalling System No. 7.*
+- [55] Recommendation Q.2762, *Broadband Integrated Services Digital Network (B-ISDN) – General functions of messages and signals of the B-ISDN user part B-ISUP of Signalling System No. 7.*
+- [56] Recommendation Q.2763, *Broadband Integrated Services Digital Network (B-ISDN) – Signalling System No. 7 B-ISDN user part (B-ISUP) – Formats and codes.*
+- [57] Recommendation Q.2764, *Broadband Integrated Services Digital Network (B-ISDN) – Signalling System No. 7 B-ISDN user part (B-ISUP) – Basic call procedures.*
+- [58] Recommendation I.580, *General arrangements for interworking between B-ISDN and 64 kbit/s based ISDN.*
+
+# **Annex K**
+
+## **Handling of the End-to-end transit delay information element**
+
+(This annex forms an integral part of this Recommendation)
+
+## **K.1 General**
+
+This annex describes the use of the End-to-end transit delay information element.
+
+The support of the End-to-end transit delay information element and the procedures described in this annex is mandatory for the network and optional for the user.
+
+The purpose of the End-to-end transit delay information element is to indicate the maximum end-to-end transit delay acceptable for a call, and to indicate the cumulative transit delay to be expected for a virtual channel connection.
+
+The calling user may indicate a maximum end-to-end transit delay value to specify end-to-end transit delay requirements for a given call or indicate that any end-to-end transit delay is acceptable.
+
+The cumulative transit delay expected for the transmission of user data from the calling terminal equipment to the network boundary may be indicated by the calling user.
+
+NOTE 1 – The handling of this information within the network is described in the B-ISUP Recommendations [54], [55], [56], [57]. These Recommendations state that the cumulative transit delay value is updated sequentially along the route of the call to determine the end-to-end transit delay to be expected for the call. The B-ISUP clears the call if the maximum end-to-end transit delay requirement cannot be met.
+
+The network shall include an End-to-end transit delay information element in the SETUP message which is sent to the called user if the calling user included an End-to-end transit delay information element in the SETUP message.
+
+It is recommended that the called user updates the cumulative transit delay value received from the network.
+
+NOTE 2 – This is particularly important if the transmission line between the network boundary and the called terminal equipment causes substantial further delay (e.g. a satellite link).
+
+If a maximum end-to-end transit delay value is specified, it is recommended that the called user takes appropriate action (e.g. call rejection) when the cumulative transit delay value exceeds the specified maximum end-to-end transit delay value.
+
+If the called user accepts the call, it is recommended that the called user includes an End-to-end transit delay information element in the CONNECT message specifying the final cumulative transit delay value for the call.
+
+NOTE 3 – The B-ISUP Recommendations state that the cumulative transit delay value which the network receives in the CONNECT message will be passed transparently to the calling user.
+
+Further details about the handling of the End-to-end transit delay information element are given below.
+
+## **K.2 Handling of the End-to-end transit delay information element in the SETUP message at the originating UNI**
+
+The inclusion of the End-to-end transit delay information element in the SETUP message by the calling user is optional.
+
+If the calling user includes an End-to-end transit delay information element in the SETUP message, both the cumulative transit delay subfield and the maximum end-to-end transit delay subfield shall be present. The user may set the maximum end-to-end transit delay subfield to any end-to-end transit delay value acceptable, deliver cumulative end-to-end transit delay value to the called user if any end-to-end transit delay is acceptable.
+
+If the network receives an End-to-end transit delay information element which contains only the maximum end-to-end transit delay subfield or only the cumulative transit delay subfield, the network shall handle the End-to-end transit delay information element as a non-mandatory information element with content error.
+
+## **K.3 Handling of the End-to-end transit delay information element in the SETUP message at the destination UNI**
+
+The network shall include an End-to-end transit delay information element if the calling user included an End-to-end transit delay information element in the SETUP message. Both the cumulative transit delay subfield and the maximum end-to-end transit delay subfield shall be present.
+
+## **K.4 Handling of the End-to-end transit delay information element by the called user**
+
+It is recommended that the called user updates the cumulative transit delay value received from the network. If the cumulative transit delay value exceeds the maximum end-to-end transit delay value specified by the calling user, it is also recommended that the called user rejects the call with cause No. 49, "Quality of Service not available".
+
+#### **K.5 Handling of the End-to-end transit delay information element in the CONNECT message at the destination UNI**
+
+If the SETUP message sent to the called user included an End-to-end transit delay information element, the called user may include an End-to-end transit delay information element in the CONNECT message specifying the final cumulative transit delay value for the call. No maximum end-to-end transit delay subfield shall be included. If the network receives an End-to-end transit delay information element in the CONNECT message containing a maximum end-to-end transit delay subfield, this field shall be discarded.
+
+The network does not check the correctness of the cumulative transit delay value provided.
+
+#### **K.6 Handling of the End-to-end transit delay information element in the CONNECT message at the originating UNI**
+
+The network shall include an End-to-end transit delay information element in the CONNECT message sent to the calling user if the called user included an End-to-end transit delay information element in the CONNECT message. No maximum end-to-end transit delay subfield shall be included.
+
+### **Annex L**
+
+#### **Examples for Message Structure and Information Element Format**
+
+(This annex forms an integral part of this Recommendation)
+
+#### **L.1 Introduction**
+
+This annex shows an example of the structure of a Q.2931 information element.
+
+#### **L.2 Structure using of an information subfield identifiers**
+
+An example of the structure of a Q.2931 information element using subfield identifiers is shown in Figure L.1.
+
+
+
+| Bits | | | | | | | | Octets |
+|-------------------------------------------|-----------------|---|----------------------|------|----------------|---|---|----------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Information element identifier | | | | | | | | 1 |
+| 1 ext. | Coding standard | | IE instruction field | | | | | 2 |
+| | | | Flag | Res. | IE action ind. | | | |
+| Length of contents of information element | | | | | | | | 3 |
+| Subfield identifier | | | | | | | | 4 (Note) |
+| Contents of subfield | | | | | | | | 5.1 |
+| | | | | | | | | 5.2 |
+| Subfield identifier | | | | | | | | X |
+| Contents of subfield | | | | | | | | X.1 |
+| | | | | | | | | X.2 |
+
+T1175680-95/d140
+
+NOTE – Some information elements are structured using subfield identifiers, e.g. ATM traffic descriptor.
+
+FIGURE L.1/Q.2931
+**Structure of a Q.2931 information element using subfield identifiers**
+
+### L.3 The ordering of information elements
+
+An example of the structure of a Q.2931 message clarifying the ordering of information elements is shown in Figure L.2.
+
+
+
+The diagram illustrates the structure of a Q.2931 message, showing the sequence of information elements (IEs) and their components. The message is composed of octets, each containing 8 bits. The first octet is the Protocol discriminator, with bits 0 0 0 0 1 0 0 1. The second octet contains the Length of call reference value, with bits 0 0 0 0 0 0 1 1. The third octet starts with a Flag bit, followed by the Call reference value. The fourth octet contains the Message type, and the fifth octet contains the Message Length. The diagram then shows various information elements: Broadband repeat indicator information element identifier, followed by repeated information elements (the highest priority, then the second priority). This is followed by a section for IEs repeated not using the Broadband repeat indicator IE, where the priority is specified case by case. Next is a Broadband non-locking shift information element followed by a Shifted information element. Finally, a Broadband-locking shift information element is shown, followed by another Shifted information element. Annotations explain the ordering rules: 'Free ordering until a Broadband locking-shift information element is present', 'IEs repeated using the Broadband repeat indicator IE', 'IE repeated not using the Broadband repeat indicator IE. In this case, the priority of the repeated information element is specified case by case.', 'The next single information element is interpreted according to the codeset specified in the Broadband non-locking shift information element.', and 'The following information elements until another Broadband locking-shift information element is interpreted according to the codeset specified in the Broadband locking-shift information element.'
+
+| Bits | Octets |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
+| 8 7 6 5 4 3 2 1 | |
+| Protocol discriminator
0 0 0 0 1 0 0 1 | 1 |
+| Length of call reference value
0 0 0 0 0 0 1 1 | 2 |
+| Flag | 3 |
+| Call reference value | 4 |
+| | 5 |
+| Message type | 6 |
+| Message Length | 7 |
+| | 8 |
+| | 9 |
+| Free ordering until a Broadband locking-shift information element is present | |
+| Broadband repeat indicator information element identifier | |
+| The first repeated information element (the highest priority) | |
+| The second repeated information element (the second priority) | |
+| IEs repeated using the Broadband repeat indicator IE | |
+| The first repeated information element | |
+| the second repeated information element | |
+| IE repeated not using the Broadband repeat indicator IE. In this case, the priority of the repeated information element is specified case by case. | |
+| Broadband non-locking shift information element | |
+| Shifted information element | |
+| The next single information element is interpreted according to the codeset specified in the Broadband non-locking shift information element. | |
+| Broadband-locking shift information element | |
+| Shifted information element | |
+| The following information elements until another Broadband locking-shift information element is interpreted according to the codeset specified in the Broadband locking-shift information element. | |
+
+T1175690-95/d141
+
+Diagram of a Q.2931 message structure showing octets, bits, and information elements. The diagram includes fields like Protocol discriminator, Length of call reference value, Flag, Call reference value, Message type, Message Length, Broadband repeat indicator, repeated information elements, Broadband non-locking shift information element, Shifted information element, and Broadband-locking shift information element. Annotations explain the ordering rules for these elements.
+
+FIGURE L.2/Q.2931
+
+Examples of the structure of a Q.2931 message clarifying the ordering of information elements
+
+## Appendix I
+
+### Guidelines for the use of Instruction indicators
+
+(This appendix does not form an integral part of this Recommendation)
+
+For the current Q.2931 messages and information elements related to B-ISDN basic call/connection control, interworking, and for the global call reference related procedures, the Instruction indicator flag needs not to be set to "Follow explicit instructions". Recommendations for Instruction indicator codings are shown in Tables I.1 and I.2.
+
+For the Q.2931 messages and information elements related to Release 1 supplementary services, the Instruction indicator value to be used will be specified in the respective specification.
+
+For DSS 2 messages and information elements which are defined in other Recommendations, the Instruction indicator flag may be set as "Follow explicit instructions". The coding of the Instruction field is defined according to the forward/backward compatibility requirements.
+
+For information elements containing codepoints, which are not defined in this Recommendation, the Instruction indicator flag may also be set as "Follow explicit instructions".
+
+The following abbreviations have been used in the tables:
+
+| | |
+|----------|-----------------------------------|
+| Used | Follow explicit instructions |
+| Not used | Instruction field not significant |
+| N | Network |
+| U | User |
+
+TABLE I.1/Q.2931
+
+### Typical use of Instruction indicators for the Q.2931 messages which are related to the basic call control
+
+| Message | Flag | Origin | Action indicator |
+|---------------------|----------|--------|------------------|
+| ALERTING | Not used | N&U | Not significant |
+| CALL PROCEEDING | Not used | N&U | Not significant |
+| CONNECT | Not used | N&U | Not significant |
+| CONNECT ACKNOWLEDGE | Not used | N&U | Not significant |
+| INFORMATION | Not used | N&U | Not significant |
+| NOTIFY | Not used | N&U | Not significant |
+| PROGRESS | Not used | N&U | Not significant |
+| SETUP | Not used | N&U | Not significant |
+| SETUP ACKNOWLEDGE | Not used | N&U | Not significant |
+| STATUS | Not used | N&U | Not significant |
+| STATUS ENQUIRY | Not used | N&U | Not significant |
+| RELEASE | Not used | N&U | Not significant |
+| RELEASE COMPLETE | Not used | N&U | Not significant |
+| RESTART | Not used | N&U | Not significant |
+| RESTART ACKNOWLEDGE | Not used | N&U | Not significant |
+
+TABLE I.2/Q.2931
+
+**Typical use of Instruction indicators for the Q.2931 information elements
+which are related to the basic call control**
+
+| Information elements | Flag | Origin | Action indicator |
+|--------------------------------------|----------|--------|------------------|
+| Broadband-locking shift | Not used | N&U | Not significant |
+| Broadband-non-locking shift | Not used | N&U | Not significant |
+| ATM adaptation layer parameter | Not used | N&U | Not significant |
+| ATM traffic descriptor | Not used | N&U | Not significant |
+| Broadband bearer capability | Not used | N&U | Not significant |
+| Broadband high layer information | Not used | N&U | Not significant |
+| Broadband low layer information | Not used | N&U | Not significant |
+| Call state | Not used | N&U | Not significant |
+| Called party number | Not used | N&U | Not significant |
+| Called party sub-address | Not used | N&U | Not significant |
+| Calling party number | Not used | N&U | Not significant |
+| Calling party sub-address | Not used | N&U | Not significant |
+| Cause | Not used | N&U | Not significant |
+| Connection identifier | Not used | N&U | Not significant |
+| End-to-end transit delay | Not used | N&U | Not significant |
+| Quality of Service parameter | Not used | N&U | Not significant |
+| Broadband repeat indicator | Not used | N&U | Not significant |
+| Restart indicator | Not used | N&U | Not significant |
+| Broadband sending complete | Not used | N&U | Not significant |
+| Transit network selection | Not used | N&U | Not significant |
+| Notification indicator | Not used | N&U | Not significant |
+| OAM traffic descriptor | Not used | N&U | Not significant |
+| Narrow-band bearer capability | Not used | N&U | Not significant |
+| Narrow-band high layer compatibility | Not used | N&U | Not significant |
+| Narrow-band low layer compatibility | Not used | N&U | Not significant |
+| Progress indicator | Not used | N&U | Not significant |
+
+## Appendix II
+
+### Information items for connection establishment in B-ISDN
+
+(This appendix does not form an integral part of this Recommendation)
+
+#### II.1 Scope
+
+This appendix clarifies information items for connection establishment in B-ISDN.
+
+#### II.2 Information items specified by the calling terminal
+
+##### II.2.1 Information items used for B-ISDN specific services
+
+- 1) B-BC (Broadband bearer capability):
+ - Bearer Class;
+ - Traffic type (CBR or VBR) ← only for bearer class X;
+ - Timing requirement (required or not required) ← only for bearer class X;
+ - Susceptibility to clipping;
+ - User plane connection configuration.
+- 2) ATM traffic descriptor.
+- 3) Quality of Service parameter.
+- 4) AAL parameters.
+- 5) End-to-end transit delay.
+- 6) B-LLI (Broadband low layer information).
+- 7) B-HLI (Broadband high layer information).
+- 8) OAM traffic descriptor.
+
+##### II.2.2 Emulation of N-ISDN bearer services and interworking with N-ISDN
+
+The calling terminal generally cannot identify the type of called terminal (ATM terminal or N-ISDN terminal) at call-setup. Therefore, the same procedure shall apply for both emulation of N-ISDN bearer services between ATM terminals and interworking with N-ISDN (Figure II.1).
+
+The following summarizes the main information items required for emulation of N-ISDN bearer services between ATM terminals and for interworking with N-ISDN.
+
+- 1) N-BC (Narrow-band bearer capability):
+ - Information transfer capability (speech, unrestricted digital information, restricted digital information, 3.1 kHz audio, unrestricted digital information with tone/announcement, video).
+ - Transfer mode (circuit, packet, frame).
+ - Information transfer rate (bit/s).
+ - User information layer 1 protocol (A-law, ....).
+- 2) B-BC (Broadband bearer capability):
+ - Bearer Class (BCOB-A).
+ - Susceptibility to clipping (susceptible to clipping).
+ - User plane connection configuration (point-to-point).
+
+3) ATM traffic descriptor:
+
+The two types of cell rate defined by Recommendation I.371 are included as follows:
+
+- a) Peak cell rate for CLP = 0:
+ - Forward cell rate;
+ - Backward cell rate.
+ - b) Peak cell rate for CLP = 0 + 1:
+ - Forward cell rate;
+ - Backward cell rate.
+- 4) Quality of Service parameter.
+- 5) AAL parameters.
+- 6) End-to-end transit delay.
+- 7) N-LLC (Narrow-band low layer compatibility).
+- 8) N-HLC (Narrow-band high layer compatibility).
+- 9) OAM traffic descriptor.
+
+
+
+The diagram illustrates the network architecture for B-ISDN and N-ISDN interworking. At the top is a large rounded rectangle labeled 'B-ISDN'. Below it is another rounded rectangle labeled 'N-ISDN'. Between them is a square labeled 'IWF' (Interworking Function). On the left, an 'ATM terminal' (represented by a rectangle) is connected to the B-ISDN cloud. On the right, another 'ATM terminal' is connected to the B-ISDN cloud, and an 'N-ISDN terminal' (represented by a triangle) is connected to the N-ISDN cloud. Two communication paths are shown starting from the left ATM terminal: Path ① is a horizontal dotted line going straight through the B-ISDN cloud to the right ATM terminal. Path ② is a dotted line that enters the B-ISDN cloud, goes down through the IWF, and then through the N-ISDN cloud to the N-ISDN terminal. A text box on the left with an arrow pointing to the left ATM terminal contains the note: 'The same procedure shall apply for both communication types ( ① and ② ) because the originating terminal commonly does not know the type of destination terminal'. The technical reference 'T1175700-95/d142' is printed at the bottom right of the diagram.
+
+Diagram illustrating two communication types for emulation of N-ISDN bearer services in B-ISDN. It shows an ATM terminal connected to a B-ISDN network, which is connected via an IWF to an N-ISDN network, which in turn connects to an N-ISDN terminal. Two communication paths are shown: (1) ATM terminal to ATM terminal, and (2) ATM terminal to N-ISDN terminal. A note indicates that the same procedure applies for both types because the originating terminal does not know the type of destination terminal.
+
+FIGURE II.1/Q.2931
+
+**Two communication types for emulation of N-ISDN bearer services in B-ISDN**
+
+## Appendix III
+
+### Status monitoring procedures for Semi-Permanent Virtual Channel Connections
+
+(This appendix does not form an integral part of this Recommendation)
+
+The support of the procedures of this appendix is optional for both the user and the network provider. When supported, their provision requires bilateral agreement between the subscribers and the network provider. However, it should be taken into consideration that studies are currently being undertaken in parallel in other bodies addressing the complete area of management of SPC and PVC to support network operations. Therefore, the status monitoring mechanism for SPC as contained in this appendix may in the future be provided by alternative mechanisms contained in more comprehensive Recommendations other than B-ISDN signalling Recommendations; the progress and introduction of which should not be prejudiced by this appendix. This appendix will not be further enhanced to introduce new functionality or expand existing functionality. If such functionality is required, it will be the subject of Recommendations other than B-ISDN signalling Recommendations.
+
+If implemented, these procedures are supported to co-exist with 1.610 procedures; the functionality provided by the procedures of this appendix is supported to complement the 1.610 functions.
+
+The procedures of this appendix are intended to be used for real time operational purposes. In the following, they are specified in terms of protocol elements (messages, information elements and procedures) for the monitoring of the status of Semi-Permanent Virtual Channel Connections (SPCs).
+
+These procedures include:
+
+- Real time notification of the:
+ - SPC initial configuration;
+ - SPC activation;
+ - SPC addition (indication: “new” SPC);
+ - SPC deactivation;
+ - SPC deletion (indication: “delete” SPC).
+- Interrogation of the bulk status of the availability (i.e. SPC in activated state) or unavailability (i.e. SPC in deactivated state) of configured SPCs.
+
+The procedures for status monitoring of SPCs may be initiated by management entities in the equipment on either side of the user-network interface that supports SPCs and the un-assured data transfer procedures specified in Annex B/Q.2130 (SSCF at UNI for SPC control).
+
+The procedures comprise of a real time bidirectional query/response transaction between management entities in user equipment and in the network, regarding the operational status of SPCs previously configured.
+
+The high level sequence diagram is shown in Figure III.4.
+
+Although these procedures perform a real time SPC status monitoring function, they are based on a small subset of the Q.2931 protocol and the messages use the protocol discriminator of Q.2931 messages. As such, they constitute higher layer management procedures for monitoring SPCs and provide information that complements the information provided by other management procedures such as OAM F5 flows, etc. They are meant to enable the management entities on the user side and on the side of the service provider to take necessary action.
+
+The status monitoring procedures require that the management entity at the network side of the user-network interface is always aware of the status of the SPCs. The means by which this can be guaranteed (e.g. OAM F5 flow) is outside the scope of this appendix. Furthermore, the establishment and the release of SPCs is outside the scope of this appendix.
+
+### III.1 Messages used for SPC status
+
+All messages for SPC monitoring use the SPC call reference. These messages are SPC UPDATE STATUS, SPC UPDATE STATUS ACK, SPC STATUS ENQUIRY and SPC STATUS REPORT. The messages are sent on the virtual channel for SPC control (VCI = 31).
+
+They are sent across the UNI using the un-assured data transfer procedures of Annex B/Q.2130 (definition of SSCF at UNI for SPC control). See Table III.1.
+
+TABLE III.1/Q.2931
+
+#### Messages used for SPC status
+
+| Message | Reference |
+|-----------------------|-----------|
+| SPC STATUS REPORT | III.1.1 |
+| SPC UPDATE STATUS ACK | III.1.2 |
+| SPC STATUS ENQUIRY | III.1.3 |
+| SPC UPDATE STATUS | III.1.4 |
+
+#### III.1.1 SPC STATUS REPORT message
+
+This message is sent in response to an SPC STATUS ENQUIRY message to indicate the status of one or more SPCs. This message is used only for reporting the availability of the requested existing SPCs. See Table III.2.
+
+TABLE III.2/Q.2931
+
+#### SPC STATUS REPORT
+
+| Message type: SPC STATUS REPORT
Direction: Both
Significance: Local | | | | |
+|---------------------------------------------------------------------------|-----------|-----------|------------|-----------------|
+| Information element | Reference | Direction | Type | Length (octets) |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference (Note 1) | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Transaction number | III.3.1 | Both | M | 5 |
+| SPC report type | III.3.2 | Both | M | 5 |
+| SPC status | III.3.3 | Both | O (Note 2) | 9-10 |
+
+NOTES
+
+- Only the SPC call reference is used.
+- If the SPC report type indicates SPC list, it contains one SPC status information element for each SPC request. If the SPC report type indicates SPC range, it contains SPC status information elements up to 256 for the configured SPCs. In the case of SPC range, the SPC status information elements are arranged in the ascending order of the connection identifier (VPCI/VCI).
+
+### III.1.2 SPC UPDATE STATUS ACK message
+
+The SPC UPDATE STATUS ACK message is sent in response to an SPC UPDATE STATUS message to acknowledge the SPC UPDATE STATUS message. See Table III.3.
+
+TABLE III.3/Q.2931
+
+#### SPC UPDATE STATUS ACK
+
+| Message type: SPC UPDATE STATUS ACK
Direction: Both
Significance: Local | | | | |
+|-------------------------------------------------------------------------------|-----------|-----------|------------|-----------------|
+| Information element | Reference | Direction | Type | Length (octets) |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference (Note 1) | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Transaction number | III.3.1 | Both | M | 5 |
+| SPC status | III.3.3 | Both | O (Note 2) | 9-10 |
+
+NOTES
+
+- 1 Only the SPC call reference is used.
+- 2 Only included if the status of particular SPC is different from the status report in the SPC UPDATE STATUS message.
+
+### III.1.3 SPC STATUS ENQUIRY message
+
+The SPC STATUS ENQUIRY message is sent to request the status of one or more SPCs. Sending an SPC STATUS REPORT message in response to an SPC STATUS ENQUIRY is mandatory. See Table III.4.
+
+### III.1.4 SPC UPDATE STATUS message
+
+The SPC UPDATE STATUS message is sent to indicate a change in the status of one or more SPCs. The change of status includes notification of SPC addition or deletion and notification of SPC availability (active) or unavailability (inactive). See Table III.5.
+
+## III.2 General information elements
+
+### III.2.1 Protocol discriminator
+
+See 4.2.
+
+### III.2.2 Call reference
+
+The SPC call reference shall be used. The value of the SPC call reference is all 1. See 4.3.
+
+### III.2.3 Message type
+
+See 4.4.
+
+### III.2.4 Message length
+
+See 4.4.
+
+### III.2.5 Connection identifier
+
+See 4.5.
+
+TABLE III.4/Q.2931
+
+**SPC STATUS ENQUIRY**
+
+| Message type: SPC STATUS ENQUIRY
Direction: Both
Significance: Local | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------|-----------------|
+| Information element | Reference | Direction | Type | Length (octets) |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference (Note 1) | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Transaction number | III.3.1 | Both | M | 5 |
+| SPC report type | III.3.2 | Both | M | 5 |
+| Connection identifier | 4.5 | Both | O | 9 (Note 2) |
+| NOTES
1 Only the SPC call reference is used.
2 If the SPC report type indicates SPC list, the connection identifier information element may be repeated to request the status of more than one SPC. If the SPC report type indicates SPC range, the connection identifier information element will indicate the start of the SPC range. | | | | |
+
+TABLE III.5/Q.2931
+
+**SPC UPDATE STATUS**
+
+| Message type: SPC UPDATE STATUS
Direction: Both
Significance: Local | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------|-----------------|
+| Information element | Reference | Direction | Type | Length (octets) |
+| Protocol discriminator | 4.2 | Both | M | 1 |
+| Call reference (Note 1) | 4.3 | Both | M | 4 |
+| Message type | 4.4 | Both | M | 2 |
+| Message length | 4.4 | Both | M | 2 |
+| Transaction number | III.3.1 | Both | M | 5 |
+| SPC status | III.3.3 | Both | M | 9-10 (Note 2) |
+| NOTES
1 Only the SPC call reference is used.
2 The SPC STATUS REPORT message contains one or more SPC information elements each of which is 9 or 10 octets long. The SPC UPDATE STATUS message contains one SPC status information element for each SPC that has experienced a status change. | | | | |
+
+### III.3 Other information elements
+
+The following other information element identifiers are used:
+
+- *Information element identifiers*
+
+Bits
+
+8 7 6 5 4 3 2 1
+
+0 1 1 0 0 1 0 0 Transaction Number
+
+0 1 1 0 0 1 0 1 SPC Status
+
+0 1 1 0 0 1 1 0 SPC Report Type
+
+#### III.3.1 Transaction number
+
+The purpose of the transaction number is to associate a response with a request. Each new SPC STATUS ENQUIRY message or SPC UPDATE STATUS message will have a new transaction number. See Figure III.1.
+
+
+
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets |
+|---------------------------------------------------|-----------------|---|------|------|----------------------------|---|----------------|--------|
+| Transaction number information element identifier | | | | | | | | 1 |
+| 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | |
+| 1 ext. | Coding standard | | Flag | Res. | IE instruction field Spare | | IE action ind. | 2 |
+| Length of transaction number contents | | | | | | | | 3 |
+| Value of the transaction number (Note) | | | | | | | | 4 |
+| | | | | | | | | 5 |
+
+T1175710-95/d143
+
+NOTE – It is suggested that implementations avoid immediate re-use of the transaction number after the transaction is completed. The transaction number is binary encoded.
+
+FIGURE III.1/Q.2931
+
+#### Transaction number information element
+
+#### III.3.2 SPC report type
+
+The purpose of the SPC report type information element is to indicate the type of report requested when included in an SPC STATUS ENQUIRY message or to indicate the contents of the SPC STATUS REPORT message. The length of this information element is 5 octets. See Figure III.2.
+
+#### III.3.3 SPC status
+
+The purpose of the SPC status information element is to indicate the status of configured SPCs. This information element can be repeated, as necessary, in a message to indicate the status of two or more SPCs. The maximum length of this information element is 10 octets. See Figure III.3.
+
+A new SPC is one that has been recently configured but for which a status report has not yet been sent across the UNI. A new SPC is indicated by setting the new (N) bit to “1”.
+
+An SPC is active if it is operational and it is inactive if it is configured but not available for use. The active (A) bit is set to “1” for an active SPC and set to “0” for an inactive SPC.
+
+An SPC is deleted if it is not configured. The deleted (D) bit is set to indicate the SPC is not configured when it is necessary to explicitly do so as described in III.4.
+
+
+
+| | | | | | | | | |
+|------------------------------------------------|-----------------|------|----------------------|-------|-----------------|---|---|--------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets |
+| SPC report type information element identifier | | | | | | | | 1 |
+| 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | |
+| 1 ext. | Coding standard | | IE instruction field | | | | | 2 |
+| | | Flag | Res. | Spare | IE action field | | | |
+| Length of SPC report type contents | | | | | | | | 3 |
+| | | | | | | | | 4 |
+| Type of report (Note1) | | | | | | | | 5 |
+
+T1175720-95/d144
+
+#### NOTES
+
+- Type of report (octet 5):
+ Bits
+ 8 7 6 5 4 3 2 1
+ 0 0 0 0 0 1 0 0 SPC list
+ 0 0 0 0 0 1 0 1 SPC range (Note 2).
+- In the case of the SPC report type is SPC range, the SPC STATUS REPORT message may contain an order list of the provision SPCs up to a maximum number of 256.
+
+FIGURE III.2/Q.2931
+
+#### SPC report type information element
+
+### III.4 Procedures across the UNI
+
+#### III.4.1 SAAL procedures
+
+The un-assured mode of the SAAL is used to provide the transport for these signalling procedures. All message used in these procedures are sent in the order they were generated and with the same priority using AAL-UNIT-DATA primitive.
+
+#### III.4.2 Initial UNI status
+
+At the time of SAAL initialization, both the user equipment and the network may report the status of all configured SPCs through one or more SPC UPDATE STATUS messages.
+
+While a SAAL is released, no SPC UPDATE STATUS message can be delivered. Therefore, the reporting entity will be unable to clear the “new” status of a newly configured SPC. When the SAAL is restored, the new bit will be set for that SPC in the SPC UPDATE STATUS message that is sent as a result of SAAL restoration. Subclause III.4.5 describes these procedures.
+
+#### III.4.3 Requesting SPC status
+
+The status of one or more SPCs can be requested at any time. When the SPC report type indicates “SPC list”, a connection identifier information element shall be included for each requested SPC. When the SPC report type indicates “SPC range”, a connection identifier information element shall be included which indicates the start of the range.
+
+The SPC STATUS ENQUIRY message includes a transaction number, which is used to verify that the SPC STATUS ENQUIRY message is acknowledged with a subsequent SPC STATUS REPORT message. When the SPC STATUS ENQUIRY message is sent, timer T393 is started, and retry counter N394 is set to “1”. When an SPC STATUS REPORT message is received, the transaction number is verified. If the transaction number matches the transaction number of the last transmitted SPC STATUS ENQUIRY message, timer T393 is stopped, and the status of each reported SPC may be updated. If the transaction number does not match the transaction number of the last transmitted SPC STATUS ENQUIRY message, the SPC STATUS REPORT message is discarded.
+
+
+
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octets |
+|-------------------------------------------|-----------------|------|--------------------------|---------|------------|----------------|-------|---------------------|
+| SPC status information element identifier | | | | | | | | 1 |
+| 0 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | |
+| 1 ext. | Coding standard | | IE instruction field | | | | | 2 |
+| | | Flag | Res. | Spare | | IE action ind. | | |
+| Length of SPC status content | | | | | | | | 3 |
+| | | | | | | | | 4 |
+| VPCI | | | | | | | | 5 |
+| | | | | | | | | 6 |
+| VCI | | | | | | | | 7 |
+| | | | | | | | | 8 |
+| Ext. 1/0 | Spare | | | New "N" | Delete "D" | Active "A" | Spare | 9 (Note 1) (Note 2) |
+| | 0 | 0 | 0 | | | | 0 | |
+| Ext. 1 | Spare | | Inactive reason (Note 3) | | | | | 9a* (Note 1) |
+| | 0 | 0 | | | | | | |
+
+T1175730-95/d145
+
+NOTES
+
+- 1 If the active bit is set to "0", then octet 9a will be included.
+ - VPCI (octets 5 and 6) See 4.5.
+ - VCI (octets 7 and 8) See 4.5.
+ - New "N" (octet 9)
+ - Bit 4
+ - 0 SPC is already present.
+ - 1 SPC is new.
+ - Delete "D" (octet 9)
+ - Bit 3
+ - 0 SPC is configured.
+ - 1 SPC is deleted.
+- 2 When this bits is set to "1", the new and active bits have no significance and should be set to "0". The delete bit is set to "0" when the new or active bits have significance and are set to "1".
+ - Active "A" (octet 9)
+ - Bit 2
+ - 0 SPC is inactive.
+ - 1 SPC is active.
+- 3 The reporting entity sets this bit to "0" when it determines that the SPC is not operational.
+ - Inactive reason (octet 9a)
+
+
+The inactive reason field is used to indicate why an SPC has become inactive. Coding for this field is as follows:
+
+Bits
+
+| 5 | 4 | 3 | 2 | 1 | |
+|---|---|---|---|---|-------------------------------------------------|
+| 0 | 0 | 0 | 0 | 0 | SPC inactive in adjacent network. |
+| 0 | 0 | 1 | 0 | 0 | SPC deleted in adjacent network. |
+| 0 | 1 | 0 | 0 | 1 | Interface inactive to adjacent network or user. |
+| 0 | 1 | 0 | 1 | 0 | SPC non-operational in the network. |
+| 0 | 1 | 0 | 1 | 1 | SPC inactive at UNI. |
+| 0 | 1 | 1 | 0 | 0 | SPC deleted in this network. |
+
+All other values are reserved.
+
+FIGURE III.3/Q.2931
+SPC status information element
+
+
+
+```
+
+sequenceDiagram
+ participant User
+ participant Network
+ Note left of User: Start T393
+ User->>Network: SPC STATUS ENQUIRY #7
+ Note right of Network: Start T394
+ Network-->>User: SPC STATUS REPORT #7
+ Note right of Network: Expire T394
+ Note right of Network: Start T394
+ Network->>User: SPC UPDATE STATUS #1
+ User-->>Network: SPC UPDATE STATUS ACK #1
+ Note right of Network: Stop T394
+
+```
+
+T1175740-95/d146
+
+Sequence diagram illustrating the independent processing of SPC UPDATE STATUS versus SPC STATUS REPORT messages between a User and a Network. The diagram shows two parallel interactions. In the first, the Network sends an SPC UPDATE STATUS #1 to the User, who responds with an SPC UPDATE STATUS ACK #1. In the second, the User sends an SPC STATUS ENQUIRY #7 to the Network, which responds with an SPC STATUS REPORT #7. The User also sends an SPC UPDATE STATUS #1 to the Network, which responds with an SPC UPDATE STATUS ACK #1. Timers T393 and T394 are shown starting and stopping at various points in the sequence.
+
+FIGURE III.4/Q.2931
+**Independent processing of SPC UPDATE STATUS
+ versus SPC STATUS REPORT messages**
+
+If timer T393 expires before the receipt of an SPC STATUS REPORT message with the correct transaction number, and the maximum retry count has not been exceeded, then the same SPC STATUS ENQUIRY message with the same transaction number may be retransmitted. If the message is retransmitted, timer T393 is restarted, and retry counter N394 is incremented.
+
+If the maximum retry count has been exceeded (check before retransmission), SAAL (the link) shall be considered to be inactive.
+
+These procedures assume that only one SPC STATUS ENQUIRY message may be outstanding at any time.
+
+#### III.4.4 Reporting SPC status
+
+When an SPC STATUS ENQUIRY message is received, an SPC STATUS REPORT message is sent which reports the current status of the requested SPCs. The SPC report type and transaction number contained in the SPC STATUS ENQUIRY message will be included.
+
+If the SPC report type indicates “SPC range”, the SPC STATUS REPORT message contains an order list of the provision SPCs up to maximum number of 256.
+
+One SPC status information element is included for each requested SPCs. An SPC STATUS REPORT message shall not contain more than one SPC status information element for a given SPC. The receiving entity is not required to check for duplicate SPC status information elements.
+
+If the SPC STATUS ENQUIRY message requests the status of an SPC that is not configured within the SPC list (SPC report type equal to SPC list), the receiving entity shall respond with an SPC STATUS REPORT message that contains a corresponding SPC status information element with the D bit set to “1”.
+
+Use of the above reporting procedures will not clear a status of ‘new’ for any SPC.
+
+### III.4.5 Reporting asynchronous status
+
+When the status of one or more SPC has changed (i.e. active, inactive, or deleted), or when an SPC is initially configured, an SPC UPDATE STATUS message is sent. Also, the reporting of all configured SPCs is necessary during SAAL initialization.
+
+SPC status information elements shall be ordered in the sequence in which the events they report were detected. The grouping of SPC status information elements into SPC UPDATE STATUS message is implementation option to send the single or group (up to 256) of SPC status information element in SPC UPDATE STATUS message. Therefore, it is possible for two or more SPC status information elements in an SPC UPDATE STATUS message to specify the same SPC. The support of receiving SPC UPDATE STATUS message with a single or multiple SPC status information element is mandatory.
+
+An SPC UPDATE STATUS message shall not include SPC status information elements for SPCs whose status has not changed.
+
+The SPC UPDATE STATUS message includes a transaction number, which is used to verify that the SPC UPDATE message is acknowledged with a subsequent SPC UPDATE STATUS ACK message. When the SPC UPDATE STATUS message is sent, timer T394 is started and retry counter N395 is set to "1". When an SPC UPDATE STATUS ACK message is received, the transaction number is verified. If the transaction number matches the transaction number of the last transmitted SPC UPDATE STATUS message, timer T394 is stopped, and the status of each reported SPC shall be updated. If the transaction number does not match the transaction number of the last transmitted SPC UPDATE STATUS message, the SPC UPDATE STATUS ACK message is discarded.
+
+If timer T394 expires before the receipt of an SPC UPDATE STATUS ACK message with the correct transaction number, and the maximum retry count has not been exceeded, the same SPC UPDATE STATUS message with the same transaction number shall be retransmitted. If the message is retransmitted, timer T394 is started, and retry counter N395 is incremented.
+
+If the maximum retry count has been exceeded (check before transmission), SAAL (the link) shall be considered to be inactive.
+
+#### III.4.5.1 Reporting new SPCs
+
+One of the functions of the SPC UPDATE STATUS message is to notify the receiving entity of the newly configured SPCs. An SPC must be deleted by the SPC management entity before another SPC is added with the same VPCI/VCI. The procedures are as follows:
+
+- When a new SPC has been added, the reporting entity sends an SPC UPDATE STATUS message with the 'new' (N) bit in the status information element set to "1".
+- When a SPC is newly configured, its initial status may be inactive or active. This is indicated in the initial status report.
+
+The 'new' status of an SPC will not be cleared until the SPC UPDATE STATUS message reporting the 'new' status has been acknowledged.
+
+#### III.4.5.2 Reporting the availability of SPCs
+
+One of the functions of the SPC UPDATE STATUS message is to indicate the changes in status of configured SPCs. The SPC UPDATE STATUS message is sent whenever the status of an SPC changes. The changed status, inactive or active, is indicated by setting the 'active' (A) bit to "0" or "1" respectively.
+
+Since there is a delay between the time an SPC becomes active and the time the SPC's change in status is received by the other entity, a receiving entity may receive cells for an inactive SPC. The action of the user equipment at the UNI is implementation dependent. The action the network takes is also implementation dependent and may include discarding of received cells.
+
+If the network receives an SPC UPDATE STATUS message for an SPC which is not configured, there are two cases. If the 'delete' (D) bit is 0, then the network sends an SPC UPDATE STATUS message with the 'delete' (D) bit set to "1". Otherwise, no action concerning the status is required.
+
+#### **III.4.5.3 Reporting deleted SPCs**
+
+To indicate that a SPC has been deleted, an SPC UPDATE STATUS message is sent with the 'delete' (D) bit set to "1" for the affected SPC. The 'deleted' status in one direction is independent of the 'deleted' status in the other direction.
+
+When an entity receives an SPC UPDATE STATUS message with 'delete' (D) bit set to "1", and the corresponding SPC is present, an inactive status may be propagated toward the remote user. Otherwise, no action concerning the status is required.
+
+#### **III.4.6 Acknowledgement of SPC UPDATE STATUS message**
+
+When an SPC UPDATE STATUS message is received, an SPC UPDATE STATUS ACK message shall be sent with the same transaction number that was indicated in the received SPC UPDATE STATUS message.
+
+#### **III.4.7 ATM OAM flow 5 procedures**
+
+On the ATM connection used for these SPC status procedures, the OAM F5 fault and performance monitoring management procedures (see Recommendation I.610) can be used. The F5 fault management procedures provide detection and verification of the availability of the ATM connection.
+
+### **III.5 Error conditions**
+
+#### **III.5.1 UNI procedures for operational errors**
+
+The reporting entity at the UNI shall report an SPC as inactive if it detects a service affecting condition.
+
+#### **III.5.2 Signalling protocol errors**
+
+Layer 3 status signalling protocol errors are handled according to procedures defined in 5.6 and 5.7 (i.e. protocol discriminator, message type, message length, call reference and mandatory information element errors).
+
+#### **III.5.3 UNI failure**
+
+When the network detects that the UNI is inoperative, it notifies users of the SPCs that the SPCs are inactive.
+
+#### **III.5.4 Network response to SPC status change**
+
+When the network determines that the status of a SPC has changed, either because of a network failure or repair or because it has received a SPC UPDATE STATUS message from the user specifying a status change for the SPC, the SPC status change may be propagated toward the remote user.
+
+If the network element at the UNI receives an indication from the remote interface that a SPC's status has changed, it reports this across the UNI to the user.
+
+### **III.6 System timers**
+
+See Table III.6.
+
+### **III.7 System parameters**
+
+See Table III.7.
+
+TABLE III.6/Q.2931
+
+**System timers**
+
+| Timer | Description | Range (seconds) | Default (seconds) | Cause for started | Cause for normal stop | Action at the expire | Implementation | Reference |
+|-------|--------------------------|-----------------|-------------------|-------------------------|--------------------------------|----------------------------------------------------------------------|----------------|-----------|
+| T393 | SPC STATUS ENQUIRY timer | 5-30 | 10 | SPC STATUS ENQUIRY sent | SPC STATUS REPORT received | The same SPC STATUS ENQUIRY is retransmitted and N394 is incremented | Mandatory | III.4.3 |
+| T394 | SPC UPDATE STATUS timer | 5-30 | 10 | SPC UPDATE STATUS sent | SPC UPDATE STATUS ACK received | The same SPC UPDATE STATUS is retransmitted and N395 is incremented | Mandatory | III.4.5 |
+
+TABLE III.7/Q.2931
+
+**System parameters**
+
+| Parameter | Description | Default value | Action at the expire | Implementation | Reference |
+|-----------|------------------------------------------------------------------------------|---------------|---------------------------|----------------|-----------|
+| N394 | Maximum value of retry counter N394 for SPC STATUS ENQUIRY/REPORT procedures | 3 | Considered to be inactive | Mandatory | III.4.3 |
+| N395 | Maximum value of retry counter N395 for SPC UPDATE STATUS/ACK procedures | 3 | Considered to be inactive | Mandatory | III.4.5 |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2931F-200012-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2931F-200012-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..038e7f748cfdee8cf0be58a9f82fe5b9c21df206
--- /dev/null
+++ b/marked/Q/T-REC-Q.2931F-200012-I_PDF-E/raw.md
@@ -0,0 +1,269 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.2931 F**
+
+(12/2000)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Broadband ISDN – B-ISDN application protocols for
+access signalling
+
+---
+
+**Broadband integrated services digital network
+(B-ISDN) – Digital subscriber signalling system
+No. 2 (DSS2) – User-network interface (UNI)
+layer 3 specification for basic call/connection
+control: Abstract Test Suite (ATS) and partial
+Protocol Implementation eXtra Information for
+Testing (PIXIT) proforma for the network**
+
+ITU-T Recommendation Q.2931 F
+
+(Formerly CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+# SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| General aspects | Q.2000-Q.2099 |
+| Signalling ATM adaptation layer (SAAL) | Q.2100-Q.2199 |
+| Signalling network protocols | Q.2200-Q.2299 |
+| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600-Q.2699 |
+| B-ISDN application protocols for the network signalling | Q.2700-Q.2899 |
+| B-ISDN application protocols for access signalling | Q.2900-Q.2999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **Broadband integrated services digital network (B-ISDN) – Digital subscriber signalling system No. 2 (DSS2) – User-network interface (UNI) layer 3 specification for basic call/connection control: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network**
+
+## **Summary**
+
+This Recommendation specifies Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network at the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in ITU-T I.413 [4]) of implementations conforming to the procedures for the support of point-to-point release 1 switched virtual channel connections between the calling party and the called party of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2931 [1].
+
+Other ITU-T Recommendations of the Q.2931 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Test Suite Structure and Test Purposes (TSS & TP) based on this Recommendation.
+
+NOTE – This Recommendation related to protocol conformance is published only in English; it is based on an external SDO's standard published in one language, English.
+
+### **Source**
+
+ITU-T Recommendation Q.2931 F was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 6 December 2000.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2001
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+## CONTENTS
+
+| | Page |
+|--------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Endorsement ..... | 2 |
+| 4 Coverage ..... | 2 |
+| 5 Modifications ..... | 2 |
+| 5.1 General modifications..... | 2 |
+| 5.2 Technical modifications..... | 3 |
+| 5.2.1 AAL parameters IE..... | 3 |
+| 5.2.2 QoS selection procedures ..... | 3 |
+| Appendix I – Bibliography ..... | 4 |
+
+## **Broadband integrated services digital network (B-ISDN) – Digital subscriber signalling system No. 2 (DSS2) – User-network interface (UNI) layer 3 specification for basic call/connection control: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network**
+
+## **1 Scope**
+
+This Recommendation specifies Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network at the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in ITU-T I.413 [4]) of implementations conforming to the procedures for the support of point-to-point release 1 switched virtual channel connections between the calling party and the called party of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2931 [1].
+
+Further parts of the series specify the Protocol Implementation Conformance Statement (PICS) proforma and Test Suite Structure and Test Purposes (TSS & TP) based on this Recommendation.
+
+This Recommendation is applicable to equipment, supporting point-to-point B-ISDN release 1 calls/connections, to be attached at either side of a $T_B$ reference point or coincident $S_B$ and $T_B$ reference point when used as an access to the public B-ISDN.
+
+The ATS realizes test purposes identified in the TSS & TP part of the Recommendation and groups them according to the test suite structure given in the TSS & TP. Test purposes defined in the TSS & TP part but not testable are identified in this part of the Recommendation.
+
+The supplier of a protocol implementation that is claimed to conform to ITU-T Q.2931 [1] is required to complete a copy of the PICS proforma and the PIXIT proforma provided by the testlab. The PIXIT proforma shall contain the tables identified in the partial PIXIT proforma part of this Recommendation and may contain additional information required by the testlab to be able to appropriately execute the test campaign.
+
+# **2 References**
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- [1] ITU-T Q.2931 (1995), *Digital Subscriber Signalling System No. 2 – User-Network Interface (UNI) layer 3 specification for basic call/connection control.*
+- [2] ITU-T Q.2931 B (2000), *Broadband integrated services digital network (B-ISDN) – Digital subscriber signalling system No. 2 (DSS2) – User-network interface layer 3 specification for basic call/connection control: Protocol implementation conformance statement (PICS) proforma.*
+- [3] ITU-T Q.2931 E (2000), *Broadband integrated services digital network (B-ISDN) – Digital subscriber signalling system No. 2 (DSS2) – User-network interface layer 3 specification*
+
+*for basic call/bearer control: Test Suite Structure and Test Purposes (TSS&TP) for the Network.*
+
+- [4] ITU-T I.413 (1993), *B-ISDN user-network interface.*
+- [5] ETSI EN 300 443-6 V1.2.1 (2000-10), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basic call/bearer control; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network.*
+
+# 3 Endorsement
+
+The text of ETSI Standard EN 300 443-6 [5] was approved by ITU-T as Recommendation Q.2931 F with agreed modifications as given below.
+
+NOTE – Underlining and/or strike-out is used to highlight new or deleted text where detailed indication of modifications is necessary.
+
+# 4 Coverage
+
+This Recommendation covers ITU-T Q.2931 [1] as modified by Amendment 1 (1997), Amendment 2 (1999) and Amendment 3 (1999).
+
+# 5 Modifications
+
+## 5.1 General modifications
+
+Throughout the text of ETSI Standard EN 300 443-6 [5] replace references and text as shown in the following table:
+
+| Reference in EN 300 443-6 | Modified reference |
+|---------------------------|----------------------------------------|
+| EN 300 443-1 | ITU-T Q.2931 |
+| EN 300 443-2 | ITU-T Q.2931 B |
+| EN 300 443-5 | ITU-T Q.2931 E |
+| EN 300 443 | Q.2931 series of ITU-T Recommendations |
+| EN 300 443-6 | ITU-T Q.2931 F |
+| Standard | Recommendation |
+
+### Page 5, Intellectual Property Rights
+
+Delete the whole section.
+
+### Page 5, Foreword
+
+Delete the whole Foreword.
+
+NOTE – It is replaced by the Foreword of this Recommendation.
+
+###### Page 6, Clause 1 Scope
+
+Replace the whole clause with the following:
+
+#### "1 Scope
+
+See clause 1 Scope of this Recommendation above."
+
+###### Page 30, History
+
+Delete the whole clause "History".
+
+### 5.2 Technical modifications
+
+NOTE – Modifications in the TTCN part of this Recommendation are described in terms of changes in the TTCN.GR representation.
+
+#### 5.2.1 AAL parameters IE
+
+In the TTCN, Declarations Part, Test Suite Type Definitions, ASN.1 Type Definitions alter definition for the type "AAL\_contents" as below:
+
+"OCTET STRING(SIZE(1..2017))".
+
+NOTE – This limitation may be removed in later versions of the TTCN part.
+
+#### 5.2.2 QoS selection procedures
+
+In the document part, on page 13, in clause A.6 "Test Campaign Report", delete test case LBN\_04\_01 from the table.
+
+In the document part, on page 27, in clause B.6.5 "Parameter Values", delete the row "Quality of service" and PIXIT item 4.14 from table B.4 "Parameter values".
+
+In the TTCN, Declarations Part, delete from the table "Test Suite Parameter Declarations" the following parameters:
+
+PX\_QOS\_NOT\_PROV\_EXISTS
+PX\_QOS\_NOT\_PROVIDED
+
+In the TTCN, Declarations Part, add the following new constant to table "Test Suite Constant Declarations":
+
+| Constant Name | Type | Value Reference | Comments |
+|-------------------------------|----------------|-----------------|----------------------------------------------------|
+| PX_QOS_NOT_PROV_EXISTS | BOOLEAN | FALSE | Automatically deselects
LBN_04_01 |
+
+NOTE – The same effect can be achieved by leaving the TTCN untouched and setting the PIXIT value "PX\_QOS\_NOT\_PROV\_EXISTS" to FALSE at runtime.
+
+## APPENDIX I
+
+## Bibliography
+
+- [A] ETSI EN 300 443-1 V1.3.5 (1998), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basic call/bearer control; Part 1: Protocol specification.*
+- [B] ETSI EN 300 443-2 V1.2.3 (1999), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basic call/bearer control; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification.*
+- [C] ETSI EN 300 443-3 V1.1.3 (1999), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basic call/bearer control; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user.*
+- [D] ETSI EN 300 443-4 V1.1.2 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basic call/bearer control; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network.*
+- [E] ETSI EN 300 443-5 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basic call/bearer control; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network.*
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cb9177792c7746d994c710873cc965becff1171f
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45a5635eb956077e9d3ff71cc98008987c0ba0786ce159b789fd9dcbcb567c07
+size 78623
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..903f2b9b06d51072371e64a04bef376553b3b8a8
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fcd47945d511cd19bd6872100189dc606d5ad44d3d10d6d183b8538848398082
+size 152841
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cbb42e39cdfebb68ec61d08e4e823d3d580742e8
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df6aea6c6bdc07f18970d212d6072d358332a6419874ce8633e12eadc5a7a16e
+size 80269
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..43c87fcfd5c9ff9aecbf3d4cda85d913ee8cfa68
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1190bf5a2a57071cb8c73f8a716c45a7831d66aa1ff9a8a5c565582101d630ae
+size 110928
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6a2ca327a12bca8c6e5413ab9c64ac1c8a6137b2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:920f6ab7c4934f035b47f521df5cf44d0dea43a6472ae7f9872ce4f9647d73df
+size 183484
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..674ac2bda0a82f85c28f0a3463ef8999c96c827e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ea9c98f82db80a946bd6cdc8aa312e58298fad08d418f227fd0256dede3a8f3
+size 85974
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64941ffa7ae3a093f0ea135608558dcfd1d7d1c6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77382484ae2cb17be199b0766ed445da503aa91c381a501cd21a9563ef2e1799
+size 108585
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b77816f0879456b67117a35c680e085792b5ea66
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd33e3308522f3c10f0c33d015c22de9dda48612b3af923065ac23f34ab6fe1e
+size 108110
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..597350198bf183a462cef91611cc21dc746957d4
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30a6e102b1da0d13af03d660db963eef109c7d460e75a8e2594ffa6362039a83
+size 8212
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c8fd67cb2fef0be2d4aedc7d70f14645c52db20
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af04380bf5c54d485f8524c16a04726717f45cd2ac0a2cf8ea65d5f139c90312
+size 122550
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8396cc4c1d4d45a0afa1703b0ebc32de55e9f28c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/32ff77da4286b58c4778033acaa10836_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c72b17f0a52b650e0d3642f14287e1d03c2ba3a2cf720677a972dcbdd0c39b47
+size 72400
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef3f73779c9bc66a8e7b236ac5cf60eb90277a8c
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b48e8f4889bae3649dff10d54ed5dcb07a8f22dde6a50cea2c639316472c4c06
+size 154865
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d3d76661cbd4b51581881fbcc7efae1adeea0bc
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87297820ea12eb0a7821c254c48918982621149c8297ba74bb62d00e4a8226f6
+size 108171
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04261f1e0dd36244aa79645dcb59b3a56f6e62f2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a8414fa0373f15261d3acb31570b54eb42a8bc6c1ec15ca47263f47c1d5c4da
+size 137587
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..75dd28bdb3d020323fc310fbcc82b3467b603142
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c2c53f33d26d429da36dbcb58268c2e7c51889179538092d7e2cfc4b2c7ebf79
+size 109581
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6dc75e599a8c937c5800e6ef0f606f888b9cee18
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9734cb6a7b9c0a04106b7bee48a661546eddf257b9e3a48bda455721837fac10
+size 93244
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d020953fd21032c16065e62c767ac3f020639f99
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62a3466d053fbec5180f88e153cb4e865b87203e94b333c036def2484538c2fe
+size 62611
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bff84e13bf188807c4ba59c00ded1c0e49aa5f8d
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:396d82b37af025606605d761e135a7a1f6ff9e9047940129810dfad3a3bc1627
+size 74066
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..86bf00a6c4ff244b188c50dc3a923a4ab3665fb6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:894ab17d2eeb96c91e9471360a05794cd3d4f2ee15d4575cdcbb7859e3b75c5d
+size 146722
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4a4be6a9340b3dd6d511ee5896ee6e7b2f9ea66b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11585ffb3b82aafbe414b3509e703e5afb95f0132435cbd11072937af676253d
+size 80529
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f47833395cc3f916048849dc79011ba776c07ee
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:084007cdc3b9524d7240e1536b5a37286e51ddc293095f1e39fe7983e914469c
+size 53210
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e509cfb4db5f284df5ddc2738b209337b981e8bf
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:174ae0943089b15b6dd22e4b5aba0efd493b2b17c9333d125383166b30aeeaaa
+size 53551
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2608080f79a719a52c1ba9c27971138537138513
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d277841f8854fa45b4501acc1239b8d7aece68993c6ce5d3b1c93378cbbdda14
+size 54120
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..694510aafc8a285833d1ae54d150bdc24104e669
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37262f6e20e638650526a5424705bb203e0b271450114228db00aa830c71c7dd
+size 133009
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ab3de6d13fd3d0d13ce52cdbccffa6d8348f7be
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c6c59df14baa2abf2510dfbbad45c68652100e2e5bb6076eac1068ba59b7ced
+size 55799
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7562839f8ebaed7cb5c89f512787c17400d800fb
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cdf3710a3f2e72140e4a83c7652de20531ecaaba62e5925c5412303d2f15bd3a
+size 132670
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01ac37b582141bf24ed0e48453555d1e2e25cc12
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58e3d3fbc849378d7f491ada490cd19b366396143a9d51d86cf553dbf6612cdd
+size 157452
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a61ced818119299bdd206da1d8b0df15e66f2984
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1fbbb677422a0a66127dfe57bede5ef3a74e70a2767e2fe6a67729ae26a70b4b
+size 57628
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ad5092880fd827d51149038f40e530039beb7bf6
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae774e8bac128a362863b21fd0c33499709191a54fd7a057450fceba95181896
+size 97160
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9692657849002b37c795bab62a7cd52c4f8f69ca
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/a4de02b04a1a8f6cb8121ac2e11bf95a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:970e75ff0499235989c9f3d32913a338b032ddb8a024ef8848d95cfea75c09f9
+size 93854
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..67f4093a4d2397cf19790069880ebd86e6e48de7
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:65a8412e1d1d4435aba2f1b0bd61ea945e624ce12b24efa2426ee06b4ac0c450
+size 83937
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e9bc200112a22ec8665c9303d173d92c5d145fcd
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c8712e94f458d7c2a202466176f4773f7e6b807bee4181da85835ba6a1bc5ff4
+size 94821
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c07e21a8d65991db04263322f859c94f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9edefe060a4ac9143de6464cacaad13c588b7ca0
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c07e21a8d65991db04263322f859c94f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec141e1bb58e63e843dd8a2e54e96c23d045253a03d6ee262ba849e2781bb0ef
+size 20718
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89953a96818e0580d1a53b920ea59e63df6fbeed
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58d87819c14ca5b2e01966eb6dba4c4f517d0af74e7894e2956f1a713d28a1d0
+size 46296
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e30ffaf1bcf51c381c3cb868486e26193b18c34
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97a375a5885790670ed17681432ad396f860639ca876f35d34989a0fcf942727
+size 136509
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6a83b90f69e96876fec403c91c7bf02a36aa2d0
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bba51e827105cf99f3e9c4cc5b7ba8bea79ef0af824c14efc80689867b687766
+size 15562
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c7e27041e661260fd0c8e89c763bb32e_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c7e27041e661260fd0c8e89c763bb32e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..65a08d9d605f904c238ddd55bb05afa541eec1df
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/c7e27041e661260fd0c8e89c763bb32e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53a0665751deebc8a785b0bd24eb14e6c8eb87e58b7a0ce640e42f3f1b817b3e
+size 33064
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f0a9a519d4dfa4cf472c8ba46b5ed90ddabd4470
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3d81b9dfa98d855e80db8d59b4b6fc315643d6f12b1aaf53fe36f7ff21a0689
+size 24841
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5fa71503a341fca34e3cce137eba96af472f25b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cffd2d4fced8cc981c91142d3dfa5fb8d7f0b1f64bfb309aaa6caed869cb88f6
+size 55394
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4b67b6f5af53da9bab2be4cbfb47d4f2da3ff3e
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:842b3b57cfdf6087d11d57a0b4fe78736e1712251bcec9fb3193aca2da9feb5a
+size 42032
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..83439c27de897a3356a49974c7c5df45dc0422b5
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec203152569a194a871955f35a6f16677a048b6e38f6be4070421c253e321a57
+size 62833
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f9adab76afe17a1f9c0f8e8a9b41172573b560eb
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:296754e378902638d14ad7ed305b09f40fe2159c7c854327427091df6b6a1ab0
+size 111173
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d38743850020fe2fee12597ffe712334845c6bf0
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04e2a12aecbdf8de781e22d1a0cdaa17460e619624cbeba3ee73b1687d42f43b
+size 91416
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..842388a586d66e4e3e9271ed33c0a1ffff2f9a99
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bcbded0328f79a7f9725d15996346bfab4e2ed8d7f6186a297116254bbf0997
+size 53566
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2faf5778123c621dabb61f5756351051e85f6ee9
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b47bd2bcd528be168405b4510342255a1a069965606603bf4333c0369467cb8
+size 52778
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01e45d67b9ea03542ed953b915b2e1fdb64d77c9
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c49bf1a6a12839e38ab5b9b9dd7497cc0761eb7e36d72da5b9bc4ef30a61a2da
+size 92353
diff --git a/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f3a2fe79b2d6025b8f79fd235aa15de060e66186
--- /dev/null
+++ b/marked/Q/T-REC-Q.2932.1-199607-I_PDF-E/fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87aad63ebdd3afa7387c3eec92cc5f3b7f71fb012f32954f9740ca4aee52f7d4
+size 158167
diff --git a/marked/Q/T-REC-Q.2934-199805-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.2934-199805-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff
--- /dev/null
+++ b/marked/Q/T-REC-Q.2934-199805-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae
+size 8196
diff --git a/marked/Q/T-REC-Q.2934-199805-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/Q/T-REC-Q.2934-199805-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..46afb0ae34773513d72b5aa872a70c428d1c052b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2934-199805-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a038070ecd51f434e2ae29a90d8ee7786d1e74b281918c0de18cb06e92a5aaf7
+size 36701
diff --git a/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dca7afde55f0e663d4708d76a3952c8b671ac87b
--- /dev/null
+++ b/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d4e9f3d189b03d35d54f5634532af971329aa39d157f08f3f489f57d49b2bcf
+size 107875
diff --git a/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..06617df7a60bbfcaa00b85ed2254222a4ef45efa
--- /dev/null
+++ b/marked/Q/T-REC-Q.2955.1-199706-I_PDF-E/raw.md
@@ -0,0 +1,930 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.2955.1**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(06/97)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Broadband ISDN – B-ISDN application protocols for
+access signalling
+
+---
+
+**Stage 3 description for community of interest
+supplementary services using B-ISDN Digital
+Subscriber Signalling System No. 2 (DSS 2):
+Closed User Group (CUG)**
+
+ITU-T Recommendation Q.2955.1
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|--------------------------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| General aspects | Q.2000–Q.2099 |
+| Signalling ATM adaptation layer (SAAL) | Q.2100–Q.2199 |
+| Signalling network protocols | Q.2200–Q.2299 |
+| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600–Q.2699 |
+| B-ISDN application protocols for the network signalling | Q.2700–Q.2899 |
+| B-ISDN application protocols for access signalling | Q.2900–Q.2999 |
+
+For further details, please refer to ITU-T List of Recommendations.
+
+# **STAGE 3 DESCRIPTION FOR COMMUNITY OF INTEREST SUPPLEMENTARY SERVICES USING B-ISDN DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 2 (DSS 2): CLOSED USER GROUP (CUG)**
+
+## **Summary**
+
+This Recommendation specifies the DSS 2 signalling protocol for the support of the CUG supplementary service in B-ISDN. The protocol can be used at the $T_B$ and at the coincident $S_B$ and $T_B$ reference point.
+
+The CUG supplementary service enables users to form groups, to and from which access is restricted. Members of a specific closed user group can communicate among themselves but not, in general, with users outside the group. Specific CUG members can have additional capabilities that allow them to originate calls to destinations outside the group, and/or to receive calls from outside the group. Specific CUG members can have additional restrictions that prevent them from originating calls to other members of the CUG or from receiving calls from other members of the CUG. A specific user may be a member of one or more closed user groups.
+
+### **Source**
+
+ITU-T Recommendation Q.2955.1 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 5th of June 1997.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1998
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|--------|------------------------------------------------------------------------------------------------|----|
+| 1 | Closed User Group (CUG)..... | 1 |
+| 1.1 | Scope ..... | 1 |
+| 1.2 | References ..... | 2 |
+| 1.3 | Definitions ..... | 3 |
+| 1.4 | Abbreviations ..... | 4 |
+| 1.5 | Description ..... | 4 |
+| 1.6 | Operational requirements ..... | 5 |
+| 1.6.1 | Provision and withdrawal..... | 5 |
+| 1.6.2 | Requirements on the originating network side..... | 6 |
+| 1.6.3 | Requirements on the destination network side..... | 6 |
+| 1.7 | Coding requirements ..... | 7 |
+| 1.7.1 | Messages and closed user group information element..... | 7 |
+| 1.7.2 | Cause information element ..... | 8 |
+| 1.8 | Primitive and state definitions..... | 8 |
+| 1.8.1 | Primitive definitions..... | 8 |
+| 1.8.2 | State definitions..... | 8 |
+| 1.9 | Signalling procedures at the coincident S B and T B reference point..... | 8 |
+| 1.9.1 | Activation, deactivation and registration ..... | 8 |
+| 1.9.2 | Invocation and operation..... | 8 |
+| 1.10 | Procedures at the T B reference point for interworking with private B-ISDNs..... | 13 |
+| 1.11 | Procedures for interworking between the DSS 1 and the DSS 2 protocol..... | 13 |
+| 1.12 | Interactions with other networks ..... | 15 |
+| 1.13 | Interactions with (other) supplementary services..... | 15 |
+| 1.13.1 | Connected line identification presentation..... | 15 |
+| 1.13.2 | Connected line identification restriction ..... | 15 |
+| 1.13.3 | Calling line identification presentation ..... | 15 |
+| 1.13.4 | Calling line identification restriction ..... | 15 |
+| 1.13.5 | Closed User Group..... | 16 |
+| 1.13.6 | Direct-Dialling-In..... | 16 |
+| 1.13.7 | User-to-user signalling..... | 16 |
+| 1.13.8 | Multiple subscriber number ..... | 16 |
+| 1.13.9 | Sub-addressing..... | 16 |
+| 1.14 | Parameter values..... | 16 |
+| 1.15 | Dynamic description (SDL)..... | 16 |
+| 1.15.1 | The closed user group process ..... | 16 |
+| 1.15.2 | Relation to basic call/connection control ..... | 19 |
+
+| | Page |
+|-------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Annex A – Symmetric operation ..... | 20 |
+| Annex B – Protocol extensions to this Recommendation for calls/connections using the procedures of Recommendation Q.2971 [13] ..... | 20 |
+
+## **STAGE 3 DESCRIPTION FOR COMMUNITY OF INTEREST SUPPLEMENTARY SERVICES USING B-ISDN DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 2 (DSS 2): CLOSED USER GROUP (CUG)**
+
+*(Geneva, 1997)*
+
+###### **1 Closed User Group (CUG)**
+
+## **1.1 Scope**
+
+This Recommendation specifies the stage 3 of the Closed User Group (CUG) supplementary services for the Broadband Integrated Services Digital Network (B-ISDN) at the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in Recommendation I.413 [1]) by means of the Digital Subscriber Signalling System No. 2 (DSS 2) protocol. Stage 3 identifies the protocol procedures and switching functions needed to support a telecommunications service (see Recommendation I.130 [2]).
+
+In addition, this Recommendation specifies the protocol requirements at the $T_B$ reference point where the service is provided to the user via an intermediate private B-ISDN.
+
+This Recommendation does not specify the additional protocol requirements where the service is provided to the user via a telecommunications network that is not a B-ISDN.
+
+The CUG supplementary service enables users to form groups, to and from which access is restricted. A specific user may be a member of one or more closed user groups. Members of a specific closed user group can communicate among themselves but not, in general, with users outside the group. Specific CUG members can have additional capabilities that allow them to originate calls to destinations outside the group, and/or to receive calls from outside the group. Specific CUG members can have additional restrictions that prevent them from originating calls to other members of the CUG, or from receiving calls from other members of the CUG.
+
+The CUG supplementary service is applicable to all telecommunication services.
+
+Further part(s) of this Recommendation shall specify the method of testing required to identify conformance to this Recommendation.
+
+This Recommendation is applicable to equipment, supporting the CUG supplementary service, to be attached at either side of a $T_B$ reference point or coincident $S_B$ and $T_B$ reference point when used as an access to the public B-ISDN.
+
+The main part of this Recommendation specifies the protocol to support the CUG supplementary service in association with point-to-point connections using the procedures described in Recommendation Q.2931 [7]. To support CUG also in other connection configurations, the modifications required are specified in annexes to this Recommendation. Annex B, for example, specifies the CUG-protocol for point-to-multipoint connections using the procedures of Recommendation Q.2971 [13].
+
+The protocol specified in this Recommendation distinguishes two different types of CUG calls:
+
+- Type 1 considers CUG calls with emulated N-ISDN services. These services can be identified by the presence of the N-BC information element.
+
+NOTE – The exact basic telecommunications service is specified by the content of the N-BC and, if present, of the N-HLC information elements [7].
+
+For these services, the control of the CUG supplementary service depends on the ISDN numbers (calling and called party) **and** on the basic telecommunications service involved in the call. This service dependency is required in order to guarantee CUG integrity in the same manner as in N-ISDN.
+
+- Type 2 considers CUG calls with B-ISDN applications for which CUG is provided without basic service dependence. No emulated N-ISDN services are involved, and no B-ISDN service type has been specified for these applications. These calls can be identified by the absence of the N-BC information element [7] and by the absence of a coding specifying a B-ISDN service type in the SETUP message (see the paragraph below). For these applications, the control of the CUG supplementary service depends only on the ISDN numbers (calling and called party) involved in the call.
+
+In future, the necessity may be given to distinguish a third type of CUG call. This type will cover connections with B-ISDN basic services for which a service type is defined (see Recommendation I.371 [12]). This type of CUG call is not supported by this Recommendation.
+
+In this Recommendation, the control of the CUG supplementary service is based on the usage of a CUG specific information element. In order to ease interworking with N-ISDN, some networks may wish to support the control of CUG also by the ROSE components specified in CCITT clause 1/Q.955 [6]. If this additional feature is offered, then the CUG supplementary service shall be provided on the basis of Recommendation Q.955.1 [6] with the following additions:
+
+- the service types as listed above have to be taken into account;
+- Note 8 against Table 3 of this Recommendation has to be respected;
+- the facility information element shall be coded as specified in Recommendation Q.2932 [9];
+- in the case of interworking with the N-ISDN, the facility information element shall be mapped in accordance with 6.3 and 6.4/Q.2931 [7]. The content of the components remains unchanged; and
+- the mapping of return error and cause values shall be in alignment with 1.11.
+
+## 1.2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- [1] ITU-T Recommendation I.413 (1993), *B-ISDN user-network interfaces*.
+- [2] CCITT Recommendation I.130 (1988), *Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN*.
+- [3] ITU-T Recommendation I.112 (1993), *Vocabulary and terms for ISDNs*.
+- [4] ITU-T Recommendation I.210 (1993), *Principles of telecommunication services supported by an ISDN and the means used to describe them*.
+- [5] CCITT Recommendation E.164 (1991), *Numbering plan for the ISDN era*.
+- [6] CCITT Recommendation Q.955.1 (1992), *Stage 3 description for community of interest supplementary services using DSS 1: Closed user group*.
+
+- [7] ITU-T Recommendation Q.2931.1 (1995), *Digital Subscriber Signalling System No. 2 – User-Network Interface (UNI) layer 3 specification for basic call/connection control.*
+- [8] CCITT Recommendation Z.100 (1988), *Functional specification and description language (SDL).*
+- [9] ITU-T Recommendation Q.2932.1 (1996), *Digital subscriber Signalling System No. 2 – Generic functional protocol: Core functions.*
+- [10] CCITT Recommendation Q.85.1 (1992), *Stage 3 description for community of interest supplementary services using DSS 1: Closed user group.*
+- [11] ITU-T Recommendation Q.2610 (1995), *Usage of cause and location in B-ISDN user part and DSS 2.*
+- [12] ITU-T Recommendation I.371 (1996), *Traffic control and congestion control in B-ISDN.*
+- [13] See Annex B of this Recommendation.
+- [14] CCITT Recommendation X.180 (1988), *Administrative arrangements for international Closed User Groups (CUGs).*
+- [15] ITU-T Recommendation Q.932 (1993), *Generic procedures for the control of ISDN supplementary services.*
+
+## 1.3 Definitions
+
+This Recommendation defines the following terms:
+
+**1.3.1 basic telecommunications service:** A bearer service or teleservice. The terms "bearer service" and "teleservice" are defined in 2.2/I.112 [3], definitions 202 and 203.
+
+**1.3.2 CUG call:** A CUG call is a call which is restricted to a predefined group of users.
+
+**1.3.3 CUG index:** The closed user group index is a parameter used by the calling user to select a particular closed user group when originating a call. The index is also used by the network to indicate to the called user the closed user group from which an incoming call has originated. This index has only local significance, i.e. the index used by the calling user is, in general, different from the index used by the called user to identify the same closed user group.
+
+**1.3.4 CUG interlock code:** This is a means of identifying closed user group membership within the network. At the calling side, if a closed user group match exists, the CUG index identifying a closed user group maps to the closed user group interlock code for that closed user group. If a closed user group match exists at the called side, the closed user group interlock code identifying a closed user group maps to the CUG index representing that closed user group. Closed user group interlock code is not an access concept, but is used to uniquely identify a CUG inside a given network.
+
+**1.3.5 CUG-only service:** A user with CUG-only service is limited to making calls to, and receiving calls from, members of those CUGs of which the user is a member.
+
+**1.3.6 default number:** An ISDN number registered within the public ISDN following prior agreement between the user and the public ISDN.
+
+**1.3.7 emulated N-ISDN service:** A basic telecommunications service originally defined for N-ISDN, but supported in a B-ISDN environment.
+
+**1.3.8 incoming access:** Incoming access allows a CUG user, in addition to the CUG only service (with or without incoming calls barred within the CUG), to receive calls from all other non-CUG users and also from those other CUG users that allow outgoing access. An incoming access arrangement applies to an ISDN number and not to a specific CUG.
+
+**1.3.9 incoming calls barred within a closed user group:** This restriction means that a CUG member cannot receive CUG calls from other members of that group.
+
+**1.3.10 ISDN number:** A number conforming to the numbering plan and structure specified in CCITT Recommendation E.164 [5].
+
+**1.3.11 network:** The DSS 2 protocol entity at the network side of the user-network interface.
+
+**1.3.12 outgoing access:** An arrangement which allows a member of a CUG to make calls to other non-CUG members and also to those other CUG members that allow incoming access. An outgoing access arrangement applies to an ISDN number and not to a specific CUG.
+
+**1.3.13 outgoing calls barred within a closed user group:** This restriction means that a CUG member cannot make CUG calls to other members of that group.
+
+**1.3.14 preferential CUG:** A closed user group user subscribing to preferential closed user group nominates a CUG index which the network uses as a default to identify the required closed user group in the absence of any closed user group information in the outgoing call request. A preferential closed user group applies to an ISDN number and not to a specific closed user group.
+
+**1.3.15 supplementary service:** see 2.4/I.210 [4].
+
+**1.3.16 user:** The DSS 2 protocol entity at the user side of the user-network interface.
+
+## 1.4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|--------|-------------------------------------------------------------------|
+| B-BC | Broadband bearer capability (information element) |
+| B-ISDN | Broadband Integrated Services Digital Network |
+| CUG | Closed User Group |
+| DDI | Direct-Dialling-in |
+| DSS 1 | Digital Subscriber Signalling System No. 1 |
+| DSS 2 | Digital Subscriber Signalling System No. 2 |
+| IA | Incoming Access |
+| IC | Interlock Code |
+| ICB | Incoming Calls Barred within a closed user group |
+| MSN | Multiple Subscriber Number |
+| N-BC | Narrow-band Bearer Capability (information element) |
+| N-HLC | Narrow-band High Layer Compatibility (information element) |
+| N-ISDN | Narrow-band (64 kbit/s-based) Integrated Services Digital Network |
+| OA | Outgoing Access |
+| OCB | Outgoing Calls Barred within a closed user group |
+
+## 1.5 Description
+
+Essentially, normal call/connection establishment procedures shall apply but, additionally, to provide the CUG supplementary service, the network shall analyse the call request from the calling user in conjunction with the closed user group attributes associated with both the calling and called users
+
+(as identified by their ISDN numbers). As a result of this analysis, the call can either fail for CUG supplementary service reasons or be allowed to proceed.
+
+NOTE – In the case where a user has subscribed to the DDI supplementary service, attributes are associated with that part of the ISDN number which the network can recognize or with the default number valid for that access.
+
+The network provider may define the maximum number of closed user groups of which a user can be a member.
+
+Since the fundamental purpose of the CUG supplementary service is to prevent certain connections, the network shall strictly control interactions with some other supplementary services to protect closed user group integrity.
+
+## **1.6 Operational requirements**
+
+### **1.6.1 Provision and withdrawal**
+
+The provision of the CUG supplementary service to a new member and also the assignment of the various CUG supplementary service options to a new or existing member, shall require a prior arrangement between the member and the network provider.
+
+The assignment of a CUG index value to be associated with the CUG and also the assignment of any preferential CUG requires prior arrangement between the (new) member and the network provider. However, when a CUG spans over several networks, e.g. an international CUG, then some administrative arrangements concerning the interlock code used between the networks are required. Guidelines for such arrangements are contained in Recommendation X.180 [14].
+
+The CUG supplementary service shall be provided on a subscription basis. As a network provider option, the CUG supplementary service may be offered with subscription options.
+
+The options can be divided into two groups:
+
+- a) For applications other than emulated N-ISDN services, the options shown in Table 1 shall apply per ISDN number.
+
+For emulated N-ISDN services, the option values may be assigned individually for each emulated N-ISDN service available at the ISDN number with the CUG supplementary service.
+
+- b) The option shown in Table 2 shall apply per closed user group provided at the ISDN number with the CUG supplementary service.
+
+**Table 1/Q.2955.1 – Options available per ISDN number, or, in case of emulated N-ISDN services, for an individual emulated N-ISDN service at that ISDN number (Note 1)**
+
+| Option | Values |
+|-----------------------------|-------------------------------------------------------|
+| 1) Preferential CUG | Nominated CUG index or none designated. |
+| 2) Outgoing access (Note 2) | Allowed permanently, allowed per call or not allowed. |
+| 3) Incoming access | Allowed or not allowed. |
+
+NOTE 1 – The following statements are valid for ISDN numbers at which emulated N-ISDN services are used.
+If, for a user with the CUG supplementary service, an emulated N-ISDN service is not included in at least one closed user group, then:
+
+- preferential CUG shall have the "none designated" option value;
+- outgoing access shall have the "allowed permanently" option value if normal outgoing calls using that emulated N-ISDN service are required;
+- incoming access shall have the "allowed" option value if incoming calls using that emulated N-ISDN service are required.
+
+NOTE 2 – The "allowed per call" outgoing access option is alternatively known as "outgoing access (explicit)" and the "allowed permanently" outgoing access option is alternatively known as "outgoing access (implicit)".
+
+**Table 2/Q.2955.1 – Options available per closed user group**
+
+| Option | Values |
+|--------------------------------------|-----------------------------------------|
+| Barring within the closed user group | None, incoming calls or outgoing calls. |
+
+The options assigned to a closed user group member shall be stored in the network.
+
+NOTE – Whether or not the storage of these options for CUG are centralized or decentralized is beyond the scope of this Recommendation and is defined in the stage 2 Recommendation on the CUG supplementary service (see Recommendation Q.85.1 [10]).
+
+Withdrawal of the CUG supplementary service shall be as a result of a network provider action either at the request of a particular member, or for administrative reasons.
+
+### **1.6.2 Requirements on the originating network side**
+
+For correct interactions with certain other supplementary services, the originating network side shall store, for the duration of the call, details of whether a normal or a CUG call (with or without outgoing access) was requested in the information sent to the destination network side. The CUG interlock code (if any) of the call request to the destination network side shall also be retained.
+
+### **1.6.3 Requirements on the destination network side**
+
+For correct interactions with certain other supplementary services, the destination network side shall store, for the duration of the call, details of whether a normal or a CUG call (with or without
+
+outgoing access) request was passed to the called user. The CUG interlock code (if any) of the call request shall also be retained.
+
+## 1.7 Coding requirements
+
+### 1.7.1 Messages and closed user group information element
+
+The following messages are applicable to the invocation and control of the CUG supplementary service:
+
+- a) RELEASE (Note 1);
+- b) RELEASE COMPLETE (Note 1);
+- c) SETUP (Note 2).
+
+These messages are defined in Recommendation Q.2931 [7].
+
+NOTE 1 – The cause information element with CUG-related information may be included in a clearing message sent in the network-to-user direction if the calling user requests the CUG supplementary service, and if the network cannot allow the call to proceed. In the user-to-network direction, the cause information element may be included in the first clearing message if the called user cannot allow the call to proceed.
+
+NOTE 2 – In the user-to-network direction, the closed user group information element will be included if the calling user explicitly requests the CUG supplementary service. In the network-to-user direction, the closed user group information element will be included if a CUG call is requested.
+
+The following information element is applicable to the invocation and control of the CUG supplementary service:
+
+
+
+| Bits | | | | | | | | Octets |
+|-------------------------------------------------------------------------------|-------|---|---|---|--------------|---|---|-----------|
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
+| Closed user group information element | | | | | | | | 1 |
+| 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | |
+| Coding standard, info elem. instr. field and length of contents of info elem. | | | | | | | | 2, 3, 4 |
+| 1 ext. | Spare | | | | OA requested | | | 5 |
+| = CUG index code (binary coded integer) = | | | | | | | | 6.1*-6.2* |
+
+Figure 1/Q.2955.1 – Closed user group information element
+
+OA requested (octet 5)
+
+Bits
+
+2 1
+
+0 0 OA not requested
+
+0 1 OA requested
+
+All other values are reserved.
+
+CUG index code (octets 6.1-6.2): The CUG index code can be omitted. If omitted, the preferential CUG is assumed. For details, see Table 3.
+
+### **1.7.2 Cause information element**
+
+The cause information element is specified in Recommendation Q.2610 [11].
+
+The cause values for use in the cause information element in certain CUG service related circumstances are listed in 1.9.2.1.1.2 and 1.9.2.1.2.2.
+
+## **1.8 Primitive and state definitions**
+
+### **1.8.1 Primitive definitions**
+
+The primitives used for communication between the call/connection control process and the closed user group process are specified in 1.15.1.
+
+### **1.8.2 State definitions**
+
+No specific call/connection states in addition to those defined in Recommendation Q.2931 [7] as protocol control states shall apply for the CUG supplementary service.
+
+To facilitate understanding of the supplementary service, the following closed user group process states are used in the dynamic description (SDL):
+
+- CUG idle;
+- outgoing CUG;
+- incoming CUG.
+
+These states are specified for the purpose of the protocol definition; they need not be provided in an implementation.
+
+## **1.9 Signalling procedures at the coincident SB and TB reference point**
+
+### **1.9.1 Activation, deactivation and registration**
+
+No signalling procedure is necessary for activation, deactivation and registration of the CUG supplementary service.
+
+### **1.9.2 Invocation and operation**
+
+The CUG supplementary service shall be invoked by:
+
+- a call originating from a CUG supplementary service user. The user may explicitly request the CUG supplementary service, but in the absence of an explicit request the CUG supplementary service default procedures shall be automatically applied;
+- a call terminating at a CUG supplementary service user.
+
+#### **1.9.2.1 Actions at the originating local exchange**
+
+##### **1.9.2.1.1 Call originating from a user with the CUG supplementary service (explicit request)**
+
+###### **1.9.2.1.1.1 Normal operation**
+
+To establish a CUG call, the calling user shall include in the SETUP message the CUG information element specifying the CUG index of the requested CUG. The CUG information shall indicate also whether outgoing access is requested or not.
+
+If the user does not provide a calling party number, provides an invalid number or provides a number the network cannot screen, then the default number stored in the originating network shall be used for the assignment of the closed user group.
+
+The network shall perform internal checks appropriate to the originating network based on the contents of the CUG information element, the calling party number information element, the narrow-band bearer capability information element (if present) and the CUG attributes of the calling user. The outcome of these checks are defined in Table 3 (including Notes).
+
+NOTE – The network may respond to the SETUP message with a SETUP ACKNOWLEDGE or CALL PROCEEDING message or the call may be cleared for some reason unrelated to the CUG supplementary service before the checks are completed.
+
+If the result of the checks relevant to the originating network side allows the call to proceed, then the destination network shall perform further internal checks based on the CUG attributes (if any) of the called user. The outcomes of these checks are defined in Table 4 (including Notes).
+
+If the call is successfully offered to the called user, an ALERTING or CONNECT message according to basic call/connection control procedures shall be returned to the calling user.
+
+###### **1.9.2.1.1.2 Exceptional procedures**
+
+If, as a result of the checks relevant to either the originating or destination network, the network cannot allow the call to proceed for a CUG supplementary service related reason, then the network shall fail the call attempt and include in the clearing message returned to the user a cause information element with the appropriate cause value as defined by Tables 3 and 4 (including Notes). The following cause values may be returned in the clearing message:
+
+- No. 29 – Facility rejected.
+- No. 50 – Requested facility not subscribed.
+- No. 53 – Outgoing calls barred within CUG.
+- No. 55 – Incoming calls barred within CUG.
+- No. 62 – Inconsistency in designated outgoing access information and subscriber class.
+- No. 87 – User not member of CUG.
+- No. 90 – Non-existent CUG.
+
+If the call attempt fails for a reason unrelated to the CUG supplementary service, then a cause information element with the appropriate cause value related to the event causing the failure shall be returned to the calling user.
+
+The possibility of "simultaneous" failure for a CUG supplementary service-related reason and a reason unrelated to the CUG supplementary service is not precluded. In this case the cause shall be determined by the event not related to the CUG supplementary service which caused the call failure.
+
+##### **1.9.2.1.2 Call originating from a user with the CUG supplementary service (implicit request)**
+
+###### **1.9.2.1.2.1 Normal operation**
+
+If the calling user does not include in the outgoing SETUP message a CUG information element, then the network shall perform internal checks appropriate to the originating network only based on the CUG attributes of the preferential CUG of the calling user and the narrow-band bearer capability information element (if present). The outcome of these checks are defined in Table 3 (including Notes).
+
+If no calling party number information element is included by the calling user in the SETUP message, the default number stored in the originating network shall be used for the assignment of the CUG.
+
+###### **1.9.2.1.2.2 Exceptional procedures**
+
+If, as a result of the checks relevant to either the originating or destination network, the network cannot allow the call to proceed for a reason related to the CUG supplementary service, then the network shall initiate call clearing using one of the following causes:
+
+- No. 29 – Facility rejected;
+- No. 55 – Incoming calls barred within CUG;
+- No. 87 – User not member of CUG.
+
+When a call fails for a reason unrelated to the CUG supplementary service, then no CUG supplementary service related procedures shall apply.
+
+##### **1.9.2.1.3 Call originating from a user without the CUG supplementary service**
+
+###### **1.9.2.1.3.1 Normal operation**
+
+A user without the CUG supplementary service can make a call to a user with the CUG supplementary service. If such a calling user does not include a CUG information element, then the checks in Table 3 (including Notes) shall apply.
+
+The destination network shall then perform further checks based on the CUG attributes (if any) of the called user. The outcomes of these checks are defined in Table 4 (including Notes).
+
+###### **1.9.2.1.3.2 Exceptional procedures**
+
+If the calling user includes in the outgoing SETUP message a CUG information element and if the network can recognize it, then the network shall fail the call and initiate clearing with cause No. 50 "Requested facility not allowed".
+
+If the network cannot recognize the CUG information element, then the exceptional procedures of Recommendation Q.2931 for unrecognized information elements shall apply.
+
+If the calling user does not include a CUG information element in the outgoing SETUP message and the call fails as a result of the checks relevant to the destination network, then the network shall fail the call attempt and initiate clearing with cause No. 87 "User not member of CUG".
+
+#### **1.9.2.2 Actions at the destination local exchange**
+
+##### **1.9.2.2.1 Call terminating at a user with the CUG supplementary service**
+
+###### **1.9.2.2.1.1 Normal operation**
+
+At the destination network side, the internal checks will have to determine the type of CUG call. This Recommendation supports CUG calls of types 1 and 2 (see 1.1).
+
+If the internal checks defined in Table 4 (including Notes) result in a requirement for a CUG call (with or without outgoing access) to the called user, then the incoming SETUP message shall include a CUG information element to convey the necessary CUG call information.
+
+The network shall then expect either:
+
+- an ALERTING or CONNECT message according to basic call/connection control received from the user if the call is successfully offered to the called user; or
+- a clearing message with a cause information element indicating the reason of the clearing. The cause value received from the called user shall be relayed by the destination network to the originating network and an appropriate indication shall be delivered in the first clearing message to the calling user.
+
+###### 1.9.2.2.1.2 Exceptional procedures
+
+If the cause information element is absent in the clearing message received from the called user, the destination network shall continue clearing by indicating a cause unrelated to the CUG supplementary service and clear the call towards the calling user.
+
+When a user receives a SETUP message with a CUG information element it does not understand, it shall follow the CUG information element instruction indicator. The destination network shall code the CUG information element instruction indicator as "discard information element and proceed".
+
+#### 1.9.2.3 CUG checks at the originating and destination network
+
+Table 3 shall be used to determine the type of call request sent to the destination network or rejection indication returned to the calling user.
+
+NOTE – The type of call request derived from Table 3 shall determine the linkage to Table 4.
+
+Table 4 shall be used to determine the type of call request sent to the destination user or the type of rejection indication returned to the calling user.
+
+**Table 3/Q.2955.1 – Closed user group checks at the originating network**
+
+| CUG attributes of calling user for requested B-ISDN service | | CUG information received from calling user in SETUP | | | | No CUG call request received | |
+|-------------------------------------------------------------|---------|-----------------------------------------------------|------------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|--|
+| | | CUG call request received | | | | | |
+| | | OA not requested, CUG index | OA requested, CUG index | OA not requested, no CUG index | OA requested, no CUG index | | |
+| No preferential CUG, OA not allowed | Not OCB | CUG call IC = specific CUG (Note 1) | CUG call IC = specific CUG (Note 1) | Rejected with cause value = 62 (Note 4) | Rejected with cause value = 62 (Note 4) | Rejected with cause value = 29 (Note 4) | |
+| | OCB | Rejected with cause value = 53 | Rejected with cause value = 53 | | | | |
+| No preferential CUG, OA allowed per call | Not OCB | CUG call IC = specific CUG (Note 1) | CUG + OA call IC = specific CUG (Note 1) | Rejected with cause value = 62 (Note 4) | Normal call (Note 4) | Rejected with cause value = 29 (Note 4) | |
+| | OCB | Rejected with cause value = 53 | Normal call | | | | |
+| No preferential CUG, OA allowed permanently | Not OCB | CUG + OA call IC = specific CUG (Note 1) | CUG + OA call IC = specific CUG (Note 1) | Normal call (Note 4) | Normal call (Note 4) | Normal call (Note 4) | |
+| | OCB | Normal call | Normal call | | | | |
+| Preferential CUG nominated, OA not allowed | Not OCB | CUG call IC = specific CUG (Note 2) | CUG call IC = specific CUG (Note 2) | CUG call IC = preferential CUG | Rejected with cause value = 62 | CUG call IC = preferential CUG | |
+| | OCB | Rejected (Note 3) with cause value = 53 | Rejected (Note 3) with cause value = 53 | Combination barred (Note 5) | Combination barred (Note 5) | Combination barred (Note 5) | |
+
+**Table 3/Q.2955.1 – Closed user group checks at the originating network (concluded)**
+
+| CUG attributes of calling user for requested B-ISDN service | | CUG information received from calling user in SETUP | | | | |
+|-------------------------------------------------------------|---------|-----------------------------------------------------|---------------------------------------------|-----------------------------------|----------------------------------------|-----------------------------------|
+| | | CUG call request received | | | | No CUG call request received |
+| | | OA not requested, CUG index | OA requested, CUG index | OA not requested, no CUG index | OA requested, no CUG index | |
+| Preferential CUG nominated, OA allowed per call | Not OCB | CUG call
IC = specific CUG (Note 2) | CUG + OA call
IC = specific CUG (Note 2) | CUG call
IC = preferential CUG | Normal call | CUG call
IC = preferential CUG |
+| | OCB | Rejected (Note 3)
cause value = 53 | Normal call (Note 3) | Combination barred (Note 5) | Combination barred (Note 5) | Combination barred (Note 5) |
+| Preferential CUG nominated, OA allowed permanently | Not OCB | CUG + OA call
IC = specific CUG (Note 2) | CUG + OA call
IC = specific CUG (Note 2) | (Note 8) | CUG + OA call
IC = preferential CUG | (Note 8) |
+| | OCB | Normal call (Note 3) | Normal call (Note 3) | Combination barred (Note 5) | Combination barred (Note 5) | Combination barred (Note 5) |
+| Not a CUG user | | Rejected with cause value = 50 | Rejected with cause value = 50 | Rejected with cause value = 50 | Rejected with cause value = 50 | Normal call (Note 6) |
+
+IC CUG interlock code
+OA Outgoing Access
+OCB Outgoing Calls Barred within a closed user group
+
+NOTE 1 – Assumes that the match between CUG index and IC exists.
+If no match exists, then:
+
+- if the CUG index exists but is not appropriate to the requested emulated N-ISDN service, then the call shall be rejected with cause value = 29. This includes the case when the requested emulated N-ISDN service is not included in any closed user group;
+- if the CUG index does not exist, the call shall be rejected with cause value = 90.
+
+NOTE 2 – Assumes that the match between CUG index and IC exists for the requested emulated N-ISDN service. If no match exists, then:
+
+- if the CUG index exists but is not appropriate to the requested emulated N-ISDN service, the call shall be rejected with cause value = 29;
+- if the CUG index does not exist, the call shall be rejected with cause value = 90.
+
+NOTE 3 – If the CUG index identifies the preferential CUG, then this combination is barred in the options data, i.e. the preferential CUG cannot be assigned to the "outgoing calls" barring within the CUG option.
+
+NOTE 4 – This includes the case when the requested emulated N-ISDN service is not included in any CUG.
+
+NOTE 5 – This combination is barred in the options data, i.e. the preferential CUG cannot be assigned to the "outgoing calls" barring within the CUG option.
+
+NOTE 6 – This represents the normal case of a user without the CUG supplementary service making a normal call.
+
+NOTE 7 – Not used.
+
+NOTE 8 – Both "preferential CUG" and "allowed permanently" outgoing access options imply that either of them can be requested without including a closed user group information element in the outgoing SETUP message. When a user subscribes to both options, the originating network shall send a call request of the type CUG + OA (IC = preferential CUG) to the destination network.
+
+**Table 4/Q.2955.1 – Closed user group checks at the destination network**
+
+| Type of CUG indication from the network | M or NM | CUG attributes of the called user for the requested ISDN number, or, in case of an emulated N-ISDN service, the attributes for this requested service at the ISDN number | | | | Not a CUG user | |
+|-----------------------------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------------------------|--------------------------------|--------------------------------|--|
+| | | IA not allowed | | IA allowed | | | |
+| | | Not ICB | ICB | Not ICB | ICB | | |
+| CUG call with no OA indication | M | CUG call | Rejected with cause value = 55 | CUG call | Rejected with cause value = 55 | Rejected with cause value = 87 | |
+| | NM | Rejected with cause value = 87 (Note 1) | | Rejected with cause value = 87 (Note 1) | | | |
+| CUG call with OA indication | M | CUG call with OA request | Rejected with cause value = 55 | CUG call with OA request | Normal call | Normal call | |
+| | NM | Rejected with cause value = 87 (Note 1) | | Normal call (Note 2) | | | |
+| Normal call | – | Rejected with cause value = 87 | | Normal call (Note 2) | | Normal call (Note 3) | |
+
+M Match between IC and CUG index exists
+NM No match between IC and CUG index exists
+CUG call The closed user group information element in the SETUP message identifies CUG index but does not request outgoing access
+Normal call No closed user group information element in the SETUP message
+IC CUG interlock code
+IA Incoming Access
+ICB Incoming Calls Barred within a closed user group
+
+NOTE 1 – Assumes that the match between the CUG index and IC fails because the IC does not exist for the called user. If the IC exists but is not appropriate to the requested emulated N-ISDN service, then this call shall be rejected with cause value = 29.
+NOTE 2 – This includes the case when the requested emulated N-ISDN service is not included in any closed user group.
+NOTE 3 – This represents the normal case of a user without the CUG supplementary service receiving a normal call.
+
+## 1.10 Procedures at the TB reference point for interworking with private B-ISDNs
+
+When a public network CUG interacts with a private CUG by way of an access, it is possible, by mapping between the two CUG domains in the gateway (e.g. in the PBX), to arrange for CUG users to perceive the concatenated CUG domains as a single CUG.
+
+Under these circumstances the access must behave for CUG purposes as an internodal link.
+
+If the private network with a private network CUG domain is the originating network, a public CUG index shall be indicated in a SETUP message whenever the CUG supplementary service is requested so that the private network can receive proper indications of public CUG failures or destination private CUG failures.
+
+Therefore, when the private network anticipates interaction with a public CUG domain at the originating side, it shall use only the explicit request of CUG service.
+
+If the private network is the destination network, no special procedures are required.
+
+## 1.11 Procedures for interworking between the DSS 1 and the DSS 2 protocol
+
+For the closed user group information element, the principles specified in 6.3 and 6.4/Q.2931 [7] shall apply with the following additions:
+
+a) In the direction B-ISDN → N-ISDN:
+
+– Mapping of the SETUP message:
+
+A facility information element and a cUGCallOperation invoke component have to be generated by the interworking unit. The facility information element is specified in Recommendation Q.932 [15]. The cUGCallOperation invoke component is specified in Recommendation Q.955.1 [6]. The values of the parameters "CUGIndex" and "OARequested" shall be set according to the content of the "OA requested" and "CUG index code" fields of the closed user group information element.
+
+– Mapping of RELEASE, RELEASE COMPLETE message:
+
+The cause values contained in the DSS 2 messages RELEASE or RELEASE COMPLETE shall be mapped to the same messages of the DSS 1 protocol as follows in Table 5:
+
+**Table 5/Q.2955.1 – Mapping in the direction DSS 2 → DSS 1**
+
+| Cause value received from the DSS 2 user | Type of CUG request at the calling DSS 1 user | Information sent to the calling DSS 1 user | |
+|------------------------------------------|-----------------------------------------------|--------------------------------------------|--------------|
+| | | Cause value | Return error |
+| No. 29 | Explicit request | No. 29 | Note 2 |
+| | Default request | No. 87 | None |
+| | Not a CUG request | No. 87 | None |
+| No. 55 | Explicit request | No. 29 | Note 1 |
+| | Default request | No. 29 | None |
+| No. 87 | Explicit request | No. 29 | Note 2 |
+| | Default request | No. 87 | None |
+| | Not a CUG request | No. 87 | None |
+| Other | Explicit request | According to basic call | Note 3 |
+| | Default request | | None |
+| | Not a CUG request | | None |
+
+NOTE 1 – Error value "incomingCallsBarredWithinCUG".
+NOTE 2 – Error value "userNotMemberOfCUG".
+NOTE 3 – Error value "basicServiceNotProvided".
+Cause No. 29 – "Facility rejected".
+Cause No. 55 – "Incoming calls barred within CUG".
+Cause No. 87 – "User not member of CUG".
+
+b) In the direction N-ISDN → B-ISDN:
+
+– Mapping of SETUP message:
+
+A closed user group information element has to be generated by the interworking unit. The values of the "OA requested" and "CUG index code" fields have to be set according to the values of the parameters "OARequested" and "CUGIndex" of the cUGCallOperation invoke component.
+
+– Mapping of DISCONNECT, RELEASE and RELEASE COMPLETE messages:
+
+These messages may carry a return error component which shall be mapped as follows in Table 6:
+
+**Table 6/Q.2955.1 – Mapping in the direction DSS 1 → DSS 2**
+
+| Information received from the DSS 1 side | | Cause value used in the DSS 2 protocol |
+|------------------------------------------|-------------|----------------------------------------|
+| Return error | Cause value | |
+| Notes 1, 3 | X | No. 87 |
+| Note 2 | X | No. 90 |
+| Note 4 | X | As received from DSS 1 |
+| Note 5 | X | No. 55 |
+| Note 6 | X | As received from DSS 1 |
+| None | X | As received from DSS 1 |
+
+NOTE 1 – Error value "userNotMemberOfCUG".
+NOTE 2 – Error value "invalidOrUnregisteredCUGIndex".
+NOTE 3 – Error value "requestedBasicServiceViolatesCUGConstraints".
+NOTE 4 – Error value "inconsistencyInDesignatedFacilityAndSubscriberClass".
+NOTE 5 – Error value "incomingCallsBarredWithinCUG".
+NOTE 6 – Error value "basicServiceNotProvided".
+X – Any basic call cause value unrelated to CUG.
+Cause No. 55 – "Incoming calls barred within CUG".
+Cause No. 87 – "User not member of CUG".
+Cause No. 90 – "Non-existent CUG".
+
+For the setting of the information element instruction indicator, see 1.9.2.2.1.2.
+
+## 1.12 Interactions with other networks
+
+When a CUG fails at a gateway to a network that does not support the CUG supplementary service, then, if the CUG supplementary service was explicitly invoked, cause No. 29 "Facility rejected" should be returned to the calling user.
+
+## 1.13 Interactions with (other) supplementary services
+
+### 1.13.1 Connected line identification presentation
+
+No interaction.
+
+### 1.13.2 Connected line identification restriction
+
+No interaction.
+
+### 1.13.3 Calling line identification presentation
+
+No interaction.
+
+### 1.13.4 Calling line identification restriction
+
+No interaction.
+
+### **1.13.5 Closed User Group**
+
+Not relevant.
+
+### **1.13.6 Direct-Dialling-In**
+
+When the user has also subscribed to the DDI supplementary service, the CUG supplementary service is provided on the basis of that part of the ISDN number which the network can recognize or with the default number valid for that access. However, CUG membership shall not be available on a per DDI number basis, but instead shall be on the basis of the entire range of DDI numbers applicable at an access or group of accesses.
+
+### **1.13.7 User-to-user signalling**
+
+#### **1.13.7.1 Service 1**
+
+No interaction.
+
+### **1.13.8 Multiple subscriber number**
+
+It shall be possible to provide separate CUG supplementary services for each ISDN number both at the calling and called sides.
+
+If the calling user does not identify his MSN, then the CUG attributes assigned to the default number shall be applied at the originating network side.
+
+### **1.13.9 Sub-addressing**
+
+No interaction.
+
+## **1.14 Parameter values**
+
+No additional timers are defined for the CUG supplementary service.
+
+## **1.15 Dynamic description (SDL)**
+
+The SDL description in Figures 2 and 3 is based on the model of protocol control and call/connection control as defined in Recommendation Q.2931 [7]. Where there is an ambiguity in the text description, then the SDL should be used to resolve the conflict. Where the text description and SDL are in disagreement, then the text shall be used as the definitive source. The SDL is not intended to constrain implementations.
+
+The dynamic description is specified according to Recommendation Z.100 [8].
+
+### **1.15.1 The closed user group process**
+
+Figures 2 and 3 provide the SDL description of the closed user group process at the originating and destination network sides, respectively. No user side SDL diagrams are provided.
+
+The closed user group process is modelled as an extension of the call/connection control process. Information can pass between the call/connection control and closed user group process by means of primitives.
+
+The call/connection control process communicates certain call/connection control events and parameters to the closed user group process and then waits for instructions to proceed from the closed user group process. The primitives from the closed user group process fall into two categories:
+
+- a) Continue – The continue primitive shall prompt the call/connection control process to proceed but shall not change the course of call/connection control in establishing or clearing
+
+the call attempt. It may provide additional instructions from the closed user group process to call/connection control, e.g.:
+
+- Normal – no additional instructions to call/connection control;
+ - Apply checks – call/connection control required to perform the appropriate closed user group checks and then proceed (note that the stage 2 description functional entities FE3 "outgoing closed user group control", and FE5 "incoming closed user group control", are not modelled as part of the stage 3 description "closed user group process");
+ - Cause value – call/connection control required to include a cause information element with the indicated value in the first clearing message to the calling user.
+- b) Clear call – The clear call primitive shall cause call/connection control to move from call establishment to appropriate call clearing procedures using the additional information provided by the closed user group process.
+
+
+
+```
+
+graph TD
+ Start([CUG idle]) --> Outgoing[Outgoing SETUP]
+ Start --> CallFail[Call fail reason]
+ Start --> Alerting[Called party ALERTING]
+ Start --> Connect[Called party CONNECT]
+
+ Outgoing --> Sub{CUG subscription?}
+ Sub -- Yes --> ContCheck{{Continue apply checks}}
+ Sub -- No --> SetCause[Set cause value = 50]
+ SetCause --> ClearCause{{Clear call cause value}}
+ ContCheck --> OutgoingCUG([Outgoing CUG])
+ ClearCause --> Idle1([CUG idle])
+
+ CallFail --> ContNormal1{{Continue normal}}
+ ContNormal1 --> Idle2([CUG idle])
+
+ Alerting --> ContNormal1
+
+ Connect --> ContNormal1
+ ContNormal1 --> Idle2
+
+ OutgoingCUG --> Alerting2[Called party ALERTING]
+ OutgoingCUG --> Connect2[Called party CONNECT]
+ OutgoingCUG --> CallFail2[Call fail reason]
+
+ Alerting2 --> ContNormal2{{Continue normal}}
+ ContNormal2 --> Idle3([CUG idle])
+
+ Connect2 --> ContNormal2
+ ContNormal2 --> Idle3
+
+ CallFail2 --> ContCause{{Continue cause value}}
+ ContCause --> Idle3
+
+```
+
+Flowchart of Closed user group process – Outgoing call (network side). The process starts at 'CUG idle' and branches into four main paths: 'Outgoing SETUP', 'Call fail (reason)', 'Called party ALERTING', and 'Called party CONNECT'. The 'Outgoing SETUP' path leads to a decision 'CUG subscription?'. If 'Yes', it goes to 'Continue (apply checks)' and then to 'Outgoing CUG'. If 'No', it goes to 'Set cause value = 50', then 'Clear call (cause value)', and finally to 'CUG idle'. The 'Called party CONNECT' path leads to 'Continue (normal)' and then to 'CUG idle'. The 'Outgoing CUG' path leads to three sub-paths: 'Called party ALERTING', 'Called party CONNECT', and 'Call fail (reason)'. 'Called party ALERTING' and 'Called party CONNECT' both lead to 'Continue (normal)' and then to 'CUG idle'. 'Call fail (reason)' leads to 'Continue (cause value)' and then to 'CUG idle'. A small text 'T1182550-96' is located near the bottom right of the diagram.
+
+Figure 2/Q.2955.1 – Closed user group process – Outgoing call (network side)
+
+
+
+```
+
+graph TD
+ Start([CUG idle]) --> J1((1))
+ J1 --> S1[Incoming SETUP
+(non-CUG)]
+ J1 --> S2[Incoming SETUP
+(CUG)]
+ J1 --> S3[Incoming SETUP
+(CUG + OA)]
+ S1 --> C1{Continue
+(normal)}
+ C1 --> End1([CUG idle])
+ S2 --> C2{Continue
+(apply checks)}
+ C2 --> End2([Incoming CUG])
+ End2 --> J2((1))
+ J2 --> S4[Called party
+ALERTING]
+ J2 --> S5[Called party
+CONNECT]
+ J2 --> S6[Call fail
+(reason)]
+ S4 --> C3{Continue
+(normal)}
+ S6 --> C4{Continue
+(cause value)}
+ C3 --> J3((1))
+ C4 --> J3
+ J3 --> S7[Called party
+ALERTING]
+ J3 --> S8[Called party
+CONNECT]
+ J3 --> S9[Call fail
+(reason)]
+ S7 --> C5{Continue
+(normal)}
+ S8 --> C5
+ S9 --> C5
+ C5 --> End3([CUG idle])
+ C4 --> End3
+
+```
+
+Flowchart of the Closed user group process for an incoming call on the network side. The process starts with 'CUG idle' and branches based on the type of incoming SETUP message: non-CUG, CUG, or CUG + OA. It then proceeds through various states like 'Continue (normal)', 'Continue (apply checks)', 'Called party ALERTING', 'Called party CONNECT', and 'Call fail (reason)' to either 'CUG idle' or 'Incoming CUG'.
+
+T1182560-96
+
+Figure 3/Q.2955.1 – Closed user group process – Incoming call (network side)
+
+### 1.15.2 Relation to basic call/connection control
+
+The basic call/connection control protocol as defined in Recommendation Q.2931 [7] shall apply with the enhancement that whenever the destination network receives a cause value from the called user, this error value shall be relayed by the network to the originating network and shall be delivered in the first clearing message to the calling user.
+
+## ANNEX A
+
+### Symmetric operation
+
+The operation of the CUG supplementary service has no impact on symmetric call operation and vice versa.
+
+## ANNEX B
+
+### Protocol extensions to this Recommendation for calls/connections using the procedures of Recommendation Q.2971 [13]
+
+This annex contains the necessary protocol extensions to allow the CUG supplementary service to be used in association with point-to-multipoint calls/connections.
+
+### Subclause 1.2 of this Recommendation
+
+Add to the end of 1.2:
+
+"[13] ITU-T Recommendation Q.2971 (1995), *Broadband Integrated Services Digital Network (B-ISDN) – Digital Subscriber Signalling System No. 2 (DSS 2) – User-network interface layer 3 specification for point-to-multipoint call/connection control.*"
+
+### Subclause 1.5 of this Recommendation
+
+Include as a new paragraph after the first paragraph:
+
+"If the CUG supplementary service is applied for point-to-multipoint connections, then the same CUG shall be used for all parties of the call."
+
+### Subclause 1.6.2 of this Recommendation
+
+Add to the end of 1.6.2:
+
+"In the case of a point-to-multipoint call, the CUG interlock code of the original call request shall be included in each add party request."
+
+### Subclause 1.7.1 of this Recommendation
+
+Add to the end of the first paragraph of 1.7.1:
+
+#### d) ADD PARTY (Note 3)
+
+NOTE 3 – The closed user group information element shall be included in the network-to-user direction if CUG was invoked by the calling user.
+
+In the user-to-network direction (originating side), the ADD PARTY message shall not include CUG related information.
+
+#### e) ADD PARTY REJECT (Note 4)
+
+NOTE 4 – The cause information element with the appropriate cause number shall be included in the user-to-network direction if the customer network cannot allow the call to proceed for CUG reasons.
+
+In the network-to-user direction (originating side), the cause information element shall be included in accordance with 1.9.2.1.1.2, 1.9.2.1.2.2 and 1.11.
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression: definitions, symbols, classification
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Overall network operation, telephone service, service operation and human factors
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media, digital systems and networks
+- Series H Audiovisual and multimedia systems
+- Series I Integrated services digital network
+- Series J Transmission of television, sound programme and other multimedia signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality, telephone installations, local line networks
+- Series Q Switching and signalling**
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminals for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communication
+- Series Z Programming languages
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2961D-200012-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2961D-200012-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3127d1b02a75e4fcd3fa79502b0e7d5a42b0580
--- /dev/null
+++ b/marked/Q/T-REC-Q.2961D-200012-I_PDF-E/raw.md
@@ -0,0 +1,262 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.2961 D**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(12/2000)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Broadband ISDN – B-ISDN application protocols for
+access signalling
+
+---
+
+**Digital subscriber signalling system No. 2
+(DSS2) – Additional traffic parameters:
+Abstract test suite (ATS) and partial protocol
+implementation extra information for testing
+(PIXIT) proforma for the user**
+
+ITU-T Recommendation Q.2961 D
+
+(Formerly CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| General aspects | Q.2000-Q.2099 |
+| Signalling ATM adaptation layer (SAAL) | Q.2100-Q.2199 |
+| Signalling network protocols | Q.2200-Q.2299 |
+| Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking | Q.2600-Q.2699 |
+| B-ISDN application protocols for the network signalling | Q.2700-Q.2899 |
+| B-ISDN application protocols for access signalling | Q.2900-Q.2999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **Digital subscriber signalling system No. 2 (DSS2) – Additional traffic parameters: Abstract test suite (ATS) and partial protocol implementation extra information for testing (PIXIT) proforma for the user**
+
+## **Summary**
+
+This Recommendation specifies Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the user attached to the $T_B$ reference point or coincident $S_B$ and $T_B$ reference point (as defined in ITU-T I.413 [9]) of implementations conforming to the procedures for the handling of additional traffic parameters that may be used for basic call and connection control of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2961 [1], [2], [3], [4], [5] and [6].
+
+Other Recommendations of the Q.2961 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Test Suite Structure and Test Purposes (TSS & TP) based on this Recommendation.
+
+NOTE – This Recommendation related to protocol conformance is published only in English; it is based on an external SDO's standard published in English.
+
+### **Source**
+
+ITU-T Recommendation Q.2961 D was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 6 December 2000.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2001
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+## CONTENTS
+
+| | Page |
+|----------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References ..... | 1 |
+| 3 Endorsement..... | 2 |
+| 4 Coverage ..... | 2 |
+| 5 Modifications ..... | 2 |
+| 5.1 General modifications..... | 2 |
+| 5.2 Technical modifications..... | 3 |
+| 5.2.1 AAL parameters IE..... | 3 |
+| Appendix I – Bibliography ..... | 4 |
+
+## **Digital subscriber signalling system No. 2 (DSS2) – Additional traffic parameters: Abstract test suite (ATS) and partial protocol implementation extra information for testing (PIXIT) proforma for the user**
+
+# 1 Scope
+
+This Recommendation specifies Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the user attached to the TB reference point or coincident SB and TB reference point (as defined in ITU-T I.413 [9]) of implementations conforming to the procedures for the handling of additional traffic parameters that may be used for basic call and connection control of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2961 [1], [2], [3], [4], [5] and [6].
+
+Other Recommendations of the Q.2961 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Test Suite Structure and Test Purposes (TSS & TP) based on this Recommendation.
+
+This Recommendation is applicable to equipment, supporting capabilities for the indication of traffic parameters above of the peak cell rate at connection request time, to be attached at either side of a TB reference point or coincident SB and TB reference point when used as an access to the public B-ISDN.
+
+The ATS realizes test purposes identified in the TSS & TP part of the Recommendation and groups them according to the test suite structure given in the TSS & TP. Test purposes defined in the TSS & TP part but not testable are identified in this Recommendation.
+
+The supplier of a protocol implementation that is claimed to conform to capabilities defined in a Q.2961-series Recommendation is required to complete a copy of the PICS proforma and the PIXIT proforma provided by the testlab. The PIXIT proforma shall contain the tables identified in the partial PIXIT proforma part of this Recommendation and may contain additional information required by the testlab to be able to appropriately execute the test campaign.
+
+NOTE – No conformance test service can be provided and therefore no PICS and PIXIT proforma is required to be completed for implementation capabilities not covered by this Recommendation. For coverage of capabilities refer to clause 4.
+
+# 2 References
+
+The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of currently valid ITU-T Recommendations is regularly published.
+
+- [1] ITU-T Q.2961.1 (1995), *Digital subscriber signalling system No. 2 – Additional signalling capabilities to support traffic parameters for the tagging option and the sustainable cell rate parameter set.*
+- [2] ITU-T Q.2961.2 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Support of ATM transfer capability in the broadband bearer capability information element.*
+
+- [3] ITU-T Q.2961.3 (1997), Digital subscriber signalling system No. 2 – Additional traffic parameters: Signalling capabilities to support traffic parameters for the available bit rate (ABR) ATM transfer capability.
+- [4] ITU-T Q.2961.4 (1997), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Signalling capabilities to support traffic parameters for the ATM block transfer (ABT) ATM transfer capability.*
+- [5] ITU-T Q.2961.5 (1999), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional traffic parameters for cell delay variation tolerance indication.*
+- [6] ITU-T Q.2961.6 (1998), *Digital subscriber signalling system No. 2 – Additional traffic parameters: Additional signalling procedures for the support of the SBR2 and SBR3 ATM transfer capabilities.*
+- [7] ITU-T Q.2931 (1995), *Digital subscriber signalling system No. 2 – User-network interface (UNI) layer 3 specification for basic call/connection control.*
+- [8] ITU-T Q.2961 B (2000), *Digital subscriber signalling system No. 2 (DSS2) – Additional traffic parameters: Protocol implementation conformance statement (PICS) proforma.*
+- [9] ITU-T I.413 (1993), *B-ISDN user-network interface.*
+- [10] ITU-T Q.2931 B (2000), *Broadband Integrated Services Digital Network (B-ISDN) – Digital subscriber signalling system No. 2 (DSS2) – User-network interface (UNI) layer 3 specification for basic call/bearer control: Protocol implementation conformance statement (PICS) proforma.*
+- [11] ETSI EN 301 068-4 V1.1.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user.*
+
+# 3 Endorsement
+
+The text of ETSI EN 301 068-4 [11] was approved by ITU-T as Recommendation Q.2961 D with agreed modifications as given below.
+
+NOTE 1 – Underlining and/or strike-out is used to highlight new or deleted text where detailed indication of modifications is necessary.
+
+# 4 Coverage
+
+This Recommendation covers ITU-T Q.2961.1 [1], Q.2961.2 [2], Q.2961.3 [3], Q.2961.4 [4] and Q.2961.6 [6].
+
+NOTE – For testing of Q.2961.6, test groups for checking conformance to Q.2961.1 and Q.2961.2 shall be used with the exception of test groups 02 and 08 ("Traffic management option for support of tagging"). All the signalled parameters (valid and invalid B-BC values, valid and invalid ATM traffic descriptor values, etc.) necessary for testing Q.2961.6 requirements are entered via relevant PIXIT values.
+
+# 5 Modifications
+
+## 5.1 General modifications
+
+Throughout the text of ETSI EN 301 068-4 [11] replace references and text as shown in the following table:
+
+| Reference in ETSI EN 301 068-4 | Modified reference |
+|--------------------------------|-------------------------------|
+| EN 300 443-1 | ITU-T Q.2931 |
+| EN 300 443-2 | ITU-T Q.2931 B |
+| EN 301 068-1 | Q.2961-series Recommendations |
+| EN 301 068-2 [4] | ITU-T Q.2961 B [8] |
+| EN 301 068-4 | ITU-T Q.2961 D |
+| Standard | Recommendation |
+
+### Page 4, Intellectual Property Rights
+
+Delete the whole clause.
+
+### Page 4, Foreword
+
+Delete the whole clause.
+
+NOTE 1 – It is replaced by the Foreword of this Recommendation.
+
+### Page 5, Clause 1 Scope
+
+Replace the whole clause with the following:
+
+#### "1 Scope
+
+See clause 1 Scope of this Recommendation above."
+
+###### Page 20, Bibliography
+
+Delete the whole clause.
+
+NOTE 2 – It is replaced by Appendix I "Bibliography" of this Recommendation.
+
+###### Page 21, History
+
+Delete the whole clause.
+
+## 5.2 Technical modifications
+
+NOTE – Modifications in the TTCN part of this Recommendation are described in terms of changes in the TTCN.GR representation.
+
+#### 5.2.1 AAL parameters IE
+
+In the TTCN, Declarations Part, Test Suite Type Definitions, ASN.1 Type Definitions alter definition for the type "AAL\_contents" as below:
+
+"OCTET STRING(SIZE(1.. 4720))".
+
+NOTE – This limitation may be removed in later versions of the TTCN part.
+
+# APPENDIX I
+
+## Bibliography
+
+- [A] ETSI EN 300 443-1 V1.3.5 (1998), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basic call/bearer control; Part 1: Protocol specification.*
+- [B] ETSI EN 301 068-1 V1.2.4 (1998), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 1: Protocol specification.*
+- [C] ETSI EN 301 068-2 V1.1.3 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 2: Protocol implementation conformance statement (PICS) proforma specification.*
+- [D] ETSI EN 301 068-3 V1.1.2 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user.*
+- [E] ETSI EN 301 068-5 V1.1.2 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network.*
+- [F] ETSI EN 301 068-6 V1.1.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; ATM transfer capability and traffic parameter indication; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network.*
+- [G] ETSI ETS 300 406 (1995), *Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology.*
+
+## **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.2963.1E-200012-I_PDF-E/raw.md b/marked/Q/T-REC-Q.2963.1E-200012-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b30ecbb3c2e53fe8b580e9ddd12e60831b29da2
--- /dev/null
+++ b/marked/Q/T-REC-Q.2963.1E-200012-I_PDF-E/raw.md
@@ -0,0 +1,227 @@
+
+
+
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.2963.1 E**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(12/2000)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Broadband ISDN – B-ISDN application protocols for
+access signalling
+
+---
+
+**Digital subscriber signalling system No. 2 –
+Connection modification: Peak cell rate
+modification by the connection owner: Test
+suite structure and test purposes (TSS & TP) for
+the network**
+
+ITU-T Recommendation Q.2963.1 E
+
+(Formerly CCITT Recommendation)
+
+---
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|-----------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| B-ISDN application protocols for access signalling | Q.2900-Q.2999 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner: Test suite structure and test purposes (TSS & TP) for the network**
+
+## **Summary**
+
+This Recommendation specifies the Test Suite Structure and Test Purposes (TSS & TP) for the network at the TB reference point or coincident SB and TB reference point (as defined in ITU-T I.413 [2]) of implementations conforming to the procedures for the modification of the peak cell rate traffic parameter by the connection owner in the active phase of the call of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2963.1 [1].
+
+Other Recommendations of the Q.2963.1 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this Recommendation.
+
+NOTE – This Recommendation related to protocol conformance is published only in English; it is based on an external SDO's standard published in English.
+
+### **Source**
+
+ITU-T Recommendation Q.2963.1 E was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 6 December 2000.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2001
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+## CONTENTS
+
+| | Page |
+|---------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References ..... | 1 |
+| 3 Endorsement..... | 2 |
+| 4 Coverage ..... | 2 |
+| 5 Modifications ..... | 2 |
+| Appendix I – Bibliography ..... | 2 |
+
+## **Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner: Test suite structure and test purposes (TSS & TP) for the network**
+
+## 1 Scope
+
+This Recommendation specifies the Test Suite Structure and Test Purposes (TSS & TP) for the network at the TB reference point or coincident SB and TB reference point (as defined in ITU-T I.413 [2]) of implementations conforming to the procedures for the modification of the peak cell rate traffic parameter by the connection owner in the active phase of the call of the Digital Subscriber Signalling System No. 2 (DSS2) protocol for the Broadband Integrated Services Digital Network (B-ISDN), ITU-T Q.2963.1 [1].
+
+Other Recommendations of the Q.2963.1 family specify the Protocol Implementation Conformance Statement (PICS) proforma and Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on this Recommendation.
+
+This Recommendation is applicable to equipment, supporting the modification of the peak cell rate traffic parameters of the connection in the active phase of the call by the connection owner, to be attached at either side of a TB reference point or coincident SB and TB reference point when used as an access to the public B-ISDN.
+
+The test suite structure provides the grouping of tests in the test suite, the test purposes part is a list of test purposes realized in the ATS part of the Recommendation. Test purposes are generated from the protocol specification, refer to observable events only but give no guarantee that each test purpose defined is testable. Untestable test purposes are identified in the ATS part.
+
+## 2 References
+
+The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of currently valid ITU-T Recommendations is regularly published.
+
+- [1] ITU-T Q.2963.1 (1999), *Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner.*
+- [2] ITU-T I.413 (1993), *B-ISDN user-network interface.*
+- [3] ETSI EN 301 003-5 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network.*
+- [4] ITU-T Q.2931 (1995), *Digital subscriber signalling system No. 2 (DSS2) – User-network interface (UNI) layer 3 specification for basic call/connection control.*
+- [5] ITU-T Q.2963.1 B (2000), *Digital subscriber signalling system No. 2 – Connection modification: Peak cell rate modification by the connection owner: Protocol implementation conformance statement (PICS) proforma.*
+
+## 3 Endorsement
+
+The text of ETSI EN 301 003-5 [3] was approved by ITU-T as Recommendation Q.2963.1 E with agreed modifications as given below.
+
+## 4 Coverage
+
+This Recommendation covers ITU-T Q.2963.1 [1].
+
+## 5 Modifications
+
+Throughout the text of ETSI EN 301 003-5 [3] replace references and text as shown in the following table:
+
+| Reference in ETSI EN 301 003-5 | Modified reference |
+|--------------------------------|----------------------|
+| EN 301 003-1 | ITU-T Q.2963.1 |
+| EN 300 443-1 [2] | ITU-T Q.2931 [4] |
+| EN 301 003-2 [4] | ITU-T Q.2963.1 B [5] |
+| Standard | Recommendation |
+
+### Page 4, Intellectual Property Rights
+
+Delete the whole section.
+
+### Page 4, Foreword
+
+Delete the whole Foreword.
+
+NOTE 1 – It is replaced by the Foreword of this Recommendation.
+
+### Page 5, Clause 1 Scope
+
+Replace the whole clause with the following:
+
+### "1 Scope
+
+See clause 1 Scope of this Recommendation above."
+
+### Page 18, Bibliography
+
+Delete the whole clause "Bibliography".
+
+NOTE 2 – It is replaced by Appendix I "Bibliography" of this Recommendation.
+
+### Page 19, History
+
+Delete the whole clause "History".
+
+## APPENDIX I
+
+### Bibliography
+
+- [A] ETSI EN 300 443-1 V1.3.5 (1998), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; B-ISDN user-network interface layer 3 specification for basic call/bearer control; Part 1: Protocol specification.*
+- [B] ETSI EN 301 003-1 V1.1.3 (1999), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection*
+
+*characteristics; Peak cell rate modification by the connection owner; Part 1: Protocol specification.*
+
+- [C] ETSI EN 301 003-2 V1.1.3 (1999), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification.*
+- [D] ETSI EN 301 003-3 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user.*
+- [E] ETSI EN 301 003-4 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user.*
+- [F] ETSI EN 301 003-6 V1.2.1 (2000), *Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection characteristics; Peak cell rate modification by the connection owner; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network.*
+- [G] ISO/IEC 9646-3:1998, *Information technology – Open Systems Interconnection – Conformance testing methodology and framework – Part 3: The Tree and Tabular Combined Notation (TTCN).*
+
+### SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3040-201008-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8073c3055abc7731de1ae66c36e362f11443a0c
--- /dev/null
+++ b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4b4de5adc1d3cdb5e156cd79f5bd52f6701f25e443a1f8d3f0d1dce155ed63f9
+size 7472
diff --git a/marked/Q/T-REC-Q.3040-201008-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc1213f1da0096b6fa4d1f86b0217d421801c7fd
--- /dev/null
+++ b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:808e4a9469a6e0ea8300dc9f4aecd9b80ad362a1dfd9fcd6a8dba8163bb9bc6c
+size 290826
diff --git a/marked/Q/T-REC-Q.3040-201008-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62cca4dcd473b8e34a2bc55a7d2848289668e870
--- /dev/null
+++ b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c84832a8b221cfde1cd1b7fc3f92abe2ba0b78fd0915f319e18e7350411f274c
+size 315157
diff --git a/marked/Q/T-REC-Q.3040-201008-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..daeda9d446aa79cb59dc4a3818ccdff46fe3fe80
--- /dev/null
+++ b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:622fe089fe103b76b88261873f243a7cc8cfa6fc3f0656cb2bb6b14cab6e6aa1
+size 54183
diff --git a/marked/Q/T-REC-Q.3040-201008-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2bd1dfc4e8682c1684083f256178496f3c442e1f
--- /dev/null
+++ b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf0ae77304a12c30b80ae6e65eec9476b88e3a31fa2e8b09d2e579289367b9bf
+size 59145
diff --git a/marked/Q/T-REC-Q.3040-201008-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..32c0ee7c27865e9ac80cc1fa7d98333eb7cdbe79
--- /dev/null
+++ b/marked/Q/T-REC-Q.3040-201008-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4618f6e99ca5dd29472e1dc39a2c4941a1d443164a58f7b2ee71eca8bd5e5aab
+size 317426
diff --git a/marked/Q/T-REC-Q.3055-201912-I_PDF-E/0ab720844e454afef91e5d68f4ab8ad9_img.jpg b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/0ab720844e454afef91e5d68f4ab8ad9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a93a4bcfa879edb82856e5d98eba16a70dfb7097
--- /dev/null
+++ b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/0ab720844e454afef91e5d68f4ab8ad9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7dae253b206018708f595114271da880b759cf9196746e2ee4a3a85bb9b8f5ec
+size 42838
diff --git a/marked/Q/T-REC-Q.3055-201912-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd7c24e83d75a6b1baa7fb4210f76345166390c9
--- /dev/null
+++ b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5866ab521163bd4f911ae6e27d0a1cf1f491c665e9b87b7d7076098a143f4bff
+size 3944
diff --git a/marked/Q/T-REC-Q.3055-201912-I_PDF-E/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/3f1987804d7d78bc3b3bc560e974280a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..771b116482002d4a55c214430a333a2d2cd85c17
--- /dev/null
+++ b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/3f1987804d7d78bc3b3bc560e974280a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:68994a6890e69d1c9cea8a57963ffc4bf328ca602bb53e809084b49bfbed6e3e
+size 26244
diff --git a/marked/Q/T-REC-Q.3055-201912-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..65616673ace4d49319bb510c5528e61a60142d8d
--- /dev/null
+++ b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1f07ce22bfd9bdcb8ca88e4bab025082ba00825a50afee5da337d7b51f585f87
+size 34439
diff --git a/marked/Q/T-REC-Q.3055-201912-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7e6b8f63c98be0a9db30079179f528f092c745c1
--- /dev/null
+++ b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:726546760a1cf96b3c2ebeafd7200e0beb59e0d94bb828ad0a9bbe5ebfea0a57
+size 32585
diff --git a/marked/Q/T-REC-Q.3055-201912-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d75b33e48bb34dc995e23ecbf0f4e7715608dead
--- /dev/null
+++ b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d26d591eb7c9820693f78016223b937940042fe7d6938b009bccd403f9af7c3
+size 107111
diff --git a/marked/Q/T-REC-Q.3055-201912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..9f5a83449e8295fbb2e69011b942789f7cdd8288
--- /dev/null
+++ b/marked/Q/T-REC-Q.3055-201912-I_PDF-E/raw.md
@@ -0,0 +1,891 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3055**
+
+(12/2019)
+
+SERIES Q: SWITCHING AND SIGNALLING, AND
+ASSOCIATED MEASUREMENTS AND TESTS
+
+Signalling requirements and protocols for the NGN –
+Network signalling and control functional architecture
+
+---
+
+**Signalling protocol for heterogeneous Internet
+of things gateways**
+
+Recommendation ITU-T Q.3055
+
+# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS**
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3616 |
+| Service and session control protocols – supplementary services based on SIP-IMS | Q.3617–Q.3639 |
+| VoLTE/ViLTE network signalling | Q.3640–Q.3655 |
+| NGN applications | Q.3700–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T Q.3055
+
+## Signalling protocol for heterogeneous Internet of things gateways
+
+## Summary
+
+A heterogeneous gateway is a hardware and software system used for the interaction of Internet of things (IoT) devices with each other and with remote IoT services. It comprises an IoT gateway infrastructure (IoT GI) and a semantic IoT gateway (SIoTG). The IoT GI is a hardware and software system comprising IoT device hardware, network interfaces, operating system, and simulator or virtualization system (virtual machine, containers, etc.). It is used to ensure compatibility of the different network technologies. The SIoTG is a software program and part of the heterogeneous IoT gateway, and is used for the mapping of different protocols, applications and IoT services among themselves.
+
+The SIoTG that forms part of the heterogeneous gateway is supposed to ensure the mapping of different IoT solutions (protocols, applications and services) among themselves, independently of the configuration of the IoT devices themselves. Use of scenarios for the mapping of IoT solutions among themselves without using a special signalling protocol for the SIoTG is possible only if a standard configuration is used for each solution (e.g., for the mapping of protocols: a standard network port number for the protocol being mapped; no encryption of data embedded in the message, etc.). Otherwise, there is no standard solution for mapping procedures, and the need then arises for interaction with the SIoTG for the purpose of configuring the IoT solution mapping scenario.
+
+Recommendation ITU-T Q.3055 describes the signalling protocol for heterogeneous IoT gateways.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3055 | 2019-12-14 | 11 | 11.1002/1000/14141 |
+
+## Keywords
+
+Gateway, heterogeneous, Internet of things, protocols, semantic.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2020
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|------------------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 2 |
+| 6 Network architecture for IoT heterogeneous gateway..... | 3 |
+| 7 Semantic gateway architecture ..... | 3 |
+| 8 Database interaction and data collection: Replicated object notation ..... | 5 |
+| Appendix I – Replicated object notation..... | 6 |
+| Appendix II – RON use case..... | 17 |
+| II.1 Data bees ..... | 17 |
+| II.2 RON use case: vehicle fleet telemetry..... | 17 |
+
+
+
+## Recommendation ITU-T Q.3055
+
+## Signalling protocol for heterogeneous Internet of things gateways
+
+## 1 Scope
+
+This Recommendation describes the signalling protocol for heterogeneous Internet of things gateways. In particular, it:
+
+- Addresses the overall network model necessary for mapping and signalling procedures;
+- Addresses the software architecture necessary for mapping and signalling procedures;
+- Describes possible scenarios for the use of signalling.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T Q.4060] Recommendation ITU-T Q.4060 (2018), *The structure of the testing of heterogeneous Internet of things gateways in a laboratory environment.*
+- [ITU-T Y.4000] Recommendation ITU-T Y.4000/Y.2060 (2012), *Overview of the Internet of things.*
+- [ITU-T Y.4050] Recommendation ITU-T Y.4050/Y.2069 (2012), *Terms and definitions for the Internet of things.*
+- [ITU-T Y.4100] Recommendation ITU-T Y.4100/Y.2066 (2014), *Common requirements of the Internet of things.*
+- [ITU-T Y.4101] Recommendation ITU-T Y.4101/Y.2067 (2017), *Common requirements and capabilities of a gateway for Internet of things applications.*
+- [ITU-T Y.4113] Recommendation ITU-T Y.4113 (2016), *Requirements of the network for the Internet of things.*
+- [ITU-T Y.4418] Recommendation ITU-T Y.4418 (2018), *Gateway functional architecture for Internet of things applications.*
+- [IETF RFC 4122] IETF RFC 4122 (2005), *A Universally Unique Identifier (UUID) URN Namespace.*
+- [IETF RFC 7574] IETF RFC 7574 (2015), *Peer-to-Peer Streaming Peer Protocol (PPSPP).*
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 device** [ITU-T Y.4000]: With regard to the Internet of things, this is a piece of equipment with the mandatory capabilities of communication and the optional capabilities of sensing, actuation, data capture, data storage and data processing.
+
+**3.1.2 Internet of things (IoT)** [ITU-T Y.4000]: A global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on existing and evolving interoperable information and communication technologies.
+
+## **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 data aggregator:** Either end-point data collection device or a reliably connected device relaying the data to the cloud.
+
+**3.2.2 semantic gateway:** A software system that is used for conversion between various IoT protocols, applications and services and is included in heterogeneous gateway systems.
+
+**3.2.3 IoT/mobile device:** A data-producing device that lacks reliable communication links (IoT, mobile, disaster management, etc.).
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|----------|--------------------------------------------------------|
+| AMQP | Advanced Message Queuing Protocol |
+| CBOR | Concise Binary Object Representation |
+| CoAP | Constrained Application Protocol |
+| CRDT | Conflict-free Replicated Data Type |
+| GI | Gateway Infrastructure |
+| HTTP | Hypertext Transfer Protocol |
+| ICF | Intermediary Conversion Format |
+| IoT | Internet of Things |
+| JSON | JavaScript Object Notation |
+| MQTT | Message Queuing Telemetry Transport |
+| RAM | Random Access Memory |
+| RON | Replicated Object Notation |
+| RTPS-DDS | Real-Time Publish Subscribe- Data Distribution Service |
+| SHA | Secure Hash Algorithm |
+| SIoTG | Semantic Internet of Things Gateway |
+| UML | Unified Modelling Language |
+| UUID | Universally Unique Identifier |
+| XMPP | Extensible Messaging and Presence Protocol |
+
+# **5 Conventions**
+
+None.
+
+# 6 Network architecture for IoT heterogeneous gateway
+
+Figures 6-1 and 6-2 show the general network architecture of the hardware and software system for heterogeneous IoT gateways.
+
+
+
+Diagram illustrating the general network architecture using heterogeneous IoT gateways. An IoT device is connected via redundant unreliable links to two IoT gateways. Both IoT gateways are connected via redundant unreliable links to a Data aggregator.
+
+Figure 6-1: General network architecture using heterogeneous IoT gateways. The diagram shows an IoT device on the left connected via dashed lines labeled 'Redundant unreliable links' to two IoT gateways in the center. Each IoT gateway is then connected via similar dashed lines to a Data aggregator on the right. The diagram is labeled Q.3055(19)\_F6-1 at the bottom right.
+
+Figure 6-1 – General network architecture using heterogeneous IoT gateways
+
+
+
+Diagram illustrating the typical structure of interaction of heterogeneous IoT gateways elements. An IoT/mobile device is connected via redundant unreliable links to three IoT gateways. The IoT gateways are interconnected, and the rightmost IoT gateway is connected via a redundant unreliable link to a Data aggregator.
+
+Figure 6-2: Typical structure of interaction of heterogeneous IoT gateways elements. The diagram shows an IoT/mobile device on the left connected via dashed lines labeled 'Redundant unreliable links' to three IoT gateways (represented by blue cubes with arrows). These three gateways are interconnected with each other. The rightmost gateway is connected via a dashed line to a Data aggregator on the right. The diagram is labeled Q.3055(19)\_F6-2 at the bottom right.
+
+Figure 6-2 – Typical structure of interaction of heterogeneous IoT gateways elements
+
+The system comprises:
+
+- IoT/mobile device: a data-producing device lacking reliable communication links (IoT, mobile, disaster management, etc.).
+- Redundant unreliable links: a wireless network with unreliable/fluid topology.
+- IoT/mobile gateway: data relay devices, either mobile or unreliably connected:
+ - data aggregator: either end-point data collection device or a reliably connected device relaying the data to the cloud.
+
+This network architecture facilitates the implementation of possible interaction scenarios for the heterogeneous IoT gateway and devices connected to it.
+
+# 7 Semantic gateway architecture
+
+Figure 6-3 shows the UML-model for semantic IoT gateway software.
+
+
+
+```
+
+classDiagram
+ class HTTP
+ class CoAP
+ class Layer {
+ <>
+ }
+ class Protocol_conversion_interface {
+ <>
+ -Send message()
+ -Get message()
+ -Check message layer()
+ }
+ class Conversion_interface_control {
+ -Open interface()
+ -Close interface()
+ }
+ class ICT_IoT_convert {
+ -Convert to ICF IoT()
+ -Convert to layer()
+ }
+ class Procedure_control {
+ -Create new interface()
+ -Save message to database()
+ -Registrate object()
+ -Delete object()
+ }
+ class Interaction_with_database {
+ -Save message()
+ -Load message()
+ -Delete message()
+ -Save object()
+ -Load object()
+ -Delete object()
+ -Log conversion procedure()
+ }
+ class Signalling_interface {
+ -Get message()
+ -Send message()
+ -Parse message()
+ }
+ class ICF_IoT {
+ <>
+ }
+ class Signal_message_format {
+ <>
+ }
+
+ HTTP ..|> Layer
+ CoAP ..|> Layer
+ Layer ..|> ICT_IoT_convert
+ Protocol_conversion_interface ..|> ICT_IoT_convert
+ Conversion_interface_control o-- Protocol_conversion_interface
+ Conversion_interface_control o-- Procedure_control
+ Procedure_control o-- Interaction_with_database
+ Procedure_control o-- Signalling_interface
+ ICT_IoT_convert ..|> ICF_IoT
+ Signalling_interface ..|> Signal_message_format
+
+```
+
+UML-model for semantic IoT gateway software. The diagram shows a central 'Layer' interface at the top, implemented by protocols like HTTP and CoAP. Below 'Layer' is the 'ICT IoT convert' class, which implements the 'Protocol conversion interface' and interacts with 'ICF IoT' structure. 'ICT IoT convert' is associated with 'Procedure control', which in turn is associated with 'Conversion interface control', 'Interaction with database', and 'Signalling interface'. 'Signalling interface' interacts with 'Signal message format' structure. 'Procedure control' also has a bidirectional association with 'Interaction with database'.
+
+**Figure 6-3 – UML-model for semantic IoT gateway software**
+
+This model comprises:
+
+Procedure control – this class is responsible for monitoring the implementation of conversion procedures, according to incoming signalling messages.
+
+Signalling interface – this class is responsible for managing the virtual network interface (socket), which receives and processes signalling messages.
+
+Conversion interface control – this class is responsible for managing the virtual network interfaces for IoT protocol conversion.
+
+Protocol conversion interface – this class is responsible for receiving, sending and verifying incoming messages for the IoT protocol conversion interface.
+
+Intermediary conversion format (ICF) IoT convert – this class is responsible for converting messages from/to specific IoT protocol formats to/from intermediary conversion format for IoT.
+
+Interaction with database – this class is responsible for interaction with the local or remote database containing messages for conversion, descriptions of IoT objects (protocols, applications, services) connected to the heterogeneous gateway, and notes on procedure implementation for the semantic gateway (e.g., protocol conversion).
+
+Layer – the interface serving as the basis for the implementation of specific protocols supported by the semantic IoT gateway (e.g., HTTP, CoAP, MQTT, AMQP, RTPS-DDS, XMPP, etc.).
+
+Intermediary conversion format for Internet of things (ICF IoT) – the structure reflecting the intermediary conversion format used for storing information on messages in the database and memory during IoT protocol conversion procedures.
+
+Signal message format – the structure reflecting the format of signalling messages used for storing information on signalling messages during IoT protocol conversion procedures.
+
+# 8 Database interaction and data collection: Replicated object notation
+
+Replicated object notation (RON) is a data-centric protocol for data delivery/dissemination in an unreliable distributed environment. RON puts an emphasis on mitigating inconsistencies introduced by unreliable heterogeneous environments, such as arbitrary delivery paths, data loss, duplication and reordering, arbitrary delays, scattered and/or mobile sources and/or receivers among others.
+
+RON is data-centric event-sourced format with a simplified tabular structure. RON relies on universally unique identifiers (UUIDs) to resolve inconsistencies and assemble the full state of separately arriving pieces of partial information. The internal structure of the protocol is simple and uniform to ease implementation and use.
+
+Any RON construct is composed of four types of "atoms": strings/buffers, integers, floats and UUIDs. A basic unit of exchange is an immutable "op" corresponding to an atomic event of data change. An op has four metadata UUIDs (data type, object id, event id and a "reference") and an arbitrary number of payload atoms.
+
+A transactional unit of transmission is a frame, which is a sequence of ops.
+
+A library of data recovery/reconciliation algorithms relies on the op metadata to resolve ambiguities and reassemble the data at a collection point.
+
+RON data is effectively independent in the context of any particular transmission or storage. Hence, RON effectively blurs the border between storage/caching and delivery/transmission. Only the eventual propagation of data matters. All means of storage are equally valid as means of transmission. Consequently, RON is especially suitable for networks with unstable topology, redundant but unreliable delivery paths and/or unpredictable or extreme delays.
+
+## Appendix I
+
+### Replicated object notation
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### Replicated Object Notation
+
+Replicated Object Notation (RON) is a format for distributed live data. RON's primary mission is continuous data synchronization. A RON object may naturally have any number of replicas, which may synchronize in real-time or intermittently.
+
+JSON, protobuf, and many other formats implicitly assume serialization of separate state snapshots. RON handles state and updates all the same: state is change and change is state. RON includes metadata, versioning and addressing, all built in. Every object, every change, every version has a UUID. Pieces of data reference each other by UUIDs. Every RON data type is a conflict-free replicated data type (CRDT). With RON metadata, state and updates could always be pieced together. It always merges, it always converges.
+
+From another perspective, RON is like a metric system for data. The imperial system employed various usage-based units: feet, lines, furlongs, links, cables, etc. The metric system defines one unit (a meter), then derives other units from that. Similarly, data might be packed into usage-based units: snapshots, logs, chunks, batches, patches. RON defines an immutable *op*, then derives other units from that, in the form of data structures (arrays, maps, sets, etc.) or storage/transmission units (snapshots, batches/patches, logs, etc.).
+
+The following is a simple object serialized in RON:
+
+```
+@1fLDV+biQFvtGV :lww ,
+ 'id' '20MF000CUS',
+ 'type' 'laptop',
+ 'cpu' 'i7-8850H',
+ 'display' '15.6" UHD IPS multi-touch, 400nits',
+ 'RAM' '16 GB DDR4 2666MHz',
+ 'storage' '512 GB SSD, PCIe-NVME M.2',
+ 'graphics' 'NVIDIA GeForce GTX 1050Ti 4GB',
+@1fLDk4+biQFvtGV
+ 'wlan' 'Intel 9560 802.11AC vPro',
+ 'camera' 'IR & 720p HD Camera with microphone',
+@sha3 'SfiKqD1atGU5xxv1NLp8uZbAcHQDcX~a1HVK5rQFy_nq';
+```
+
+Key RON principles are:
+
+- **Immutability** – RON sees data as a collection of immutable timestamped ops. The example above depicts an object state consisting of ten ops (object creation op at line #1, the initial changeset #2 to #8, another changeset of two ops #9/10 and #11). An op may be referenced, transmitted, stored, applied or rolled back, garbage collected, etc. Every RON data structure (array, object, map, set, etc.) is a collection of immutable ops. Similarly, every data storage or transmission unit is made of ops (patch, state, chain, chunk, frame, object graph, log, yarn, etc.).
+- **Addressability** of everything. Changes, versions, objects and every piece of data is uniquely identified and globally referenceable. Above, the first op has an id 1fLDV+biQFvtGV, the second one is 1fLDV00001+biQFvtGV, the third
+
+is 1fLDV00002+biQFvtGV and so on (the notation skips incremental ids). The last two ops (#9-10 and #11) belong to a later changeset, so their ids are 1fLDk4+biQFvtGV, 1fLDk40001+biQFvtGV.
+
+NOTE – RON has no notational nesting (no brackets). Instead, data pieces reference each other by UUIDs, thus forming arbitrary graphs.
+
+- **Causality.** Each RON operation explicitly *references* what other op it is based on. No matter how and when the data is obtained, the correct order and location of data pieces can always be reconstructed. As described above, ops form an orderly chain, so references are skipped, except for the object creation op at line #1 which references its data type lww.
+- **Efficiency.** RON data is optimized to make metadata overhead bearable. An op is a very fine-grained unit of change. Thus, RON has to optimize per-op metadata overhead in numerous ways. Op ids get skipped if they go incrementally. References are skipped if they point to the previous op (an op chain is a convenient default). For example, the op at line #2 mentions neither its own id (the first plus 1) nor its reference (the first op). The binary variant of RON employs more sophisticated metadata compression techniques. With no abbreviations, the object would look like a tabular log of ops, two metadata UUIDs per op:
+
+```
+@1fLDV00000+biQFvtGV :lww !
+@1fLDV00001+biQFvtGV :1fLDV00000+biQFvtGV 'id' '20MF000CUS',
+@1fLDV00002+biQFvtGV :1fLDV00001+biQFvtGV 'type' 'laptop',
+...
+```
+
+- **Integrity**, as ops form a Merkle structure. If necessary, the data is integrity-checked to the last bit, like in git, BitTorrent, BitCoin and other such systems. In the example above, ten ops form a Merkle chain, so the hash of the last op (line #12) covers them all.
+
+RON's vision is swarms of mobile devices communicating over unreliable wireless networks in an untrusted environment.
+
+#### UUIDs
+
+RON relies heavily on UUIDs to globally and unambiguously address everything it operates with: operations, patches, versions, objects, hashes, etc.
+
+RON employs its own UUID flavours and custom efficient serialization. Unlike RFC 4122, RON UUIDs:
+
+- can be sorted lexicographically,
+- can be efficiently compressed,
+- can function as lamport clocks,
+- can represent human-friendly string constants.
+
+RON UUIDs are serialized as a pair of 64-bit integers encoded with custom base64 encoding:
+
+A/LED0000000+XU5eRJ0000
+
+aaaa vvvv vvvvvvvv vvvvvvvv vvvvvvvv vvvvvvvv vvvvvvvv vvvvvvvv
+
+00eeoooo ooooooooo ooooooooo ooooooooo ooooooooo ooooooooo ooooooooo ooooooooo
+
+The bit layout is backwards-compatible with RFC 4122 (hijacking the 0 variant, NCS backward compatibility). Third and fourth bits of 9th byte are used to encode version (blue), four most significant bits of 1st byte are used to encode variety (orange). The bulk of the bits are taken by value (green) and origin (violet).
+
+#### Versions
+
+Two version bits are encoded using \$, %, + or – as separator:
+
+- \$ for 00: human readable names,
+- % for 01: numbers and hashes,
+- + for 10: events (Lamport timestamp, and origin),
+- – for 11: derived events (same as event).
+
+#### Varieties
+
+Four variety bits are encoded using single hex digit 0..F followed by a slash /.
+
+Variety flavour is defined by version.
+
+Variety of zero 0 can be omitted.
+
+##### Varieties for version \$ (names):
+
+- 0000: transcendental/hardcoded name (lww, rga) or a scoped name (myvar\$gritzko),
+- 0001: ISBN (1/978\$1400075997,
+- 0011: EAN-13 bar code (3/4006381\$333931,
+- 0100: SI units (4/m, 4/kg,
+- 0101: zip codes (5/2628CD\$NL, 5/620078\$RU,
+- 1010: IATA airport code (A/LED,
+- 1011: ticker name (B/GOOG\$NASDAQ,
+- 1100: ISO 4217 currency code (C/USD, C/GBP,
+- 1101: short DNS name (D/google\$com,
+- 1110: E.164 intl phone num (E/7999\$5631415,
+- 1111: ISO 3166 country code (F/RU, F/FRA...).
+
+##### Varieties for version % (numbers and hashes):
+
+- 0000..0011: Decimal index (up to 9999999999%, also 2D indices 4%5),
+- 0100: SHA-2, plain chunk hash, first 120 bits,
+- 0101: SHA-3, plain chunk hash,
+- 0110: SHA-2 based RFC 7574 Merkle hash,
+- 0111: SHA-3 based RFC 7574 Merkle hash,
+- 1000..1011: Random number (A/k3R9w\_2F8w%Le~6dDScsw),
+- 1100..1111: Crypto id, public key fingerprint.
+
+##### Varieties for versions + and – (events)
+
+Timestamp type:
+
+- 00\_\_: Base64 calendar (MMDHmSsnn),
+- 01\_\_: Logical (400000000001),
+- 10\_\_: Epoch (RFC 4122 epoch, 100ns since 1582),
+
+bitwise and with replica id assignment rule:
+
+- \_\_00: trie-forked,
+- \_\_01: crypto-forked,
+- \_\_10: record-forked,
+
+- \_\_11: application-specific.
+
+#### **UUID compression**
+
+Most of RON UUIDs can be efficiently compressed by only encoding highest significant bits.
+
+Base 64×64 tailing zeroes can be omitted:
+
+A/LED0000000+00000000000 = A/LED+0
+
+A/LED0000000\$123 = A/LED\$123
+
+If version is \$ and second component is zero, it can be fully omitted:
+
+A/LED0000000\$00000000000 = A/LED\$0 = A/LED
+
+If variety is 0, it can be omitted as well:
+
+0/lww0000000\$00000000000 = lww0000000\$00000000000 = lww\$0 = lww
+
+#### **RON term glossary**
+
+
+
+The diagram illustrates the structure of RON terms. It is divided into three sections:
+
+- Atoms:** Four colored boxes representing basic data types: STRING (orange), UUID (purple), INT (green), and FLOAT (pink).
+- Ops ~ "molecules":** A horizontal row of three boxes: id (purple), ref (purple), and value (green).
+- Op log ~ "replicating DNA":** A vertical stack of four rows, each containing id (purple), ref (purple), and value (green) boxes. The values in the stack are: value (green), value (purple), value (green), and value (orange).
+
+Diagram illustrating RON terms: Atoms (STRING, UUID, INT, FLOAT), Ops ~ 'molecules' (id, ref, value), and Op log ~ 'replicating DNA' (a sequence of ops with id, ref, and value fields).
+
+Q.3055(19)\_Fl.1
+
+- RON UUID – a 128-bit globally unique identifier, one of four *versions*:
+ - time-based (a logical/hybrid timestamp, 60 bits of timestamp, 60 bits of event *origin* id)
+ - name (a human readable name of some predefined concept, e.g., a data type or an error type)
+ - numeric (either an arbitrary number or a hash)
+- Atom – an immutable value of one of four types:
+ - RON UUID
+ - Integer (64-bit signed)
+ - String (UTF-8)
+ - Floating-point number (IEEE 754-2008, 64 bit)
+- Op – an immutable unit of change, consists of:
+ - specifier (metadata)
+ - own RON UUID (id, identifies the op)
+ - reference RON UUID (ref, identifies the op's location in the data graph)
+
+- value (payload data)
+ - any number (zero or more) of value atoms (UUIDs, ints, strings, floats)
+
+If RON atoms are compared to real (chemistry) atoms, then RON ops are "molecules", composed of "atoms". Then, an op log is our "DNA" – it contains all the replicated data. Other higher-value constructs are like polypeptides, proteins and suchlike – they are composed of ops. Fundamentally, they are either subsets or projections of the op log (the "DNA"). A replicated op log is the foundation of all this machinery.
+
+#### Op-collection construct
+
+- Chain – a sequence of ops from the same origin, where each next op references the previous one.
+- Span – (chain span) – a chain where each op's id is exactly an increment of the previous id (1gABC+origin, 1gABC00001+origin, 1gABC00002+origin...).
+- Yarn – a linear log of all ops from the same origin (corresponds to a Lamport process).
+- Tree – a causally ordered group of ops forming a tree (each next op references some preceding op from the tree, except for the root op).
+- Object – largely synonymous to a tree, although op ordering depends on the data type (RDT).
+- Header – the object creation op (its id becomes the object's id; the header op is the root of the object's op tree).
+- Patch – a group of ops modifying the same tree/object (causally consistent, i.e., referencing the existing ops of the tree or previous ops of the patch).
+- Frame – largely synonymous to a "write batch"; a group of ops to be applied atomically, in a single transaction.
+- Chunk – a group of object's ops, preceded by the object's header, e.g., object state or a patch.
+- Log – a causally ordered sequence of ops, like a database op log. While yarns are linearly ordered, a log only has partial (causal) order; different replicas of a log may go in slightly different orders.
+- Graph – a group of objects referencing each other.
+- Graph patch – a group of object patches and full object states, a causally consistent change of an object graph.
+- Segments – a log segment, a yarn segment, a chain segment, etc. – a subset of the construct retaining its key features.
+
+#### Other terms
+
+- Annotation – a pseudo-op that is not itself a data change, but some derived/secondary information, related to some op (e.g., its hash or other metadata).
+- Vector timestamp – an array of time-based UUIDs, one per origin; a timestamp produced by vector clocks.
+
+##### Nominal format
+
+Nominal RON is a simple memory layout that stores uncompressed RON ops. It serves three purposes:
+
+- exchange RON ops within the same address space,
+- define the canonical representation, e.g., content hashing,
+- serve as an intermediary format in any conversions, mappings, filters and transformations.
+
+Normally, a serialized RON frame is read by an iterator/parser/cursor which creates a nominal-RON representation of each next op. A builder/serializer/writer converts a nominal-RON op into the resulting format.
+
+The nominal format per se is not intended as a frame serialization format, as it would be too inefficient.
+
+The nominal RON may be highly beneficial in mixed environments, e.g., when a C++ implementation is used from a node.js program through the bindings. If the js part may consume/produce nominal-RON data, it needs no own parsers and no own builders. Instead, it may consume parsed data from a scratchpad buffer. The same applies to bizzare situations, e.g., C++ engine/parsers/builders running in a browser under wasm, used by a Java program running under GWT.
+
+##### Overall layout
+
+The nominal format is made of 128-bit atoms, consisting of two 64-bit words each. Words use the 4+60 bit layout. Nominally, the byte layout is big-endian (e.g., a hash function expects big-endian words). Although, an implementation may use little-endian words if requested. All pictures assume big-endian words.
+
+An op is a concatenation of its atoms, starting with its id and ref UUIDs.
+
+In all atoms except UUIDs, the origin word specifies a byte range in the original RON buffer (text RON, binary, JSON, CBOR). The maximum allowed frame size is 1 GB, so the byte range is given as two 30-bit unsigned ints for the offset and the length. The raw buffer is supposed to be available.
+
+Caveats:
+
+- String values only reside in the raw buffer.
+- UUID atoms are fully parsed, so no range provided.
+
+##### Frame header
+
+(rarely used)
+
+Bytes 0-3 (mmmm) contain magic bytes, RON2 for closed RON, ROP2 for open.
+
+Bytes 4-7 (cccc) is the number of ops in the frame, as a big-endian integer.
+
+Bits 4-7 in byte 8 are set to 1100.
+
+Bytes 8-15 contain the byte range within the raw unparsed buffer.
+
+```
+mmmmmmmm mmmmmmmm mmmmmmmm mmmmmmmm cccccccc cccccccc cccccccc cccccccc
+1100oooo ooooooooo ooooooooo ooooooooo oo111111 11111111 11111111 11111111
+```
+
+Again, frame header is supposed to be rarely used, as entire frames are rarely uncompressed at once.
+
+###### Op header
+
+(less rarely used)
+
+Bytes 0-3 (mmmm) contain magic bytes, ron2 for closed RON, rop2 for open.
+
+Bytes 4-7 (cccc) contain the number of atoms in the op, as a big-endian integer.
+
+Bits 4-7 in byte 8 (11\_\_) indicate the op type:
+
+- 1100 raw,
+- 1101 reduced,
+- 1110 header,
+- 1111 query.
+
+Bytes 8-15 contain location of *raw buffer* location with unparsed op content.
+
+mmmmmmmm mmmmmmmm mmmmmmmm mmmmmmmm cccccccc cccccccc cccccccc cccccccc
+11\_\_oooo ooooooooo ooooooooo ooooooooo oo111111 11111111 11111111 11111111
+
+#### UUID atom
+
+A 128-bit RON UUID:
+
+vvvv.....
+00ss.....
+
+Bits 4-7 in byte 0 (vvvv) represent UUID *variety*.
+
+Bits 6-7 in byte 8 are set to 00, indicating that this atom is a UUID.
+
+Bits 4-5 in byte 8 (ss) represent UUID *version*.
+
+(That is the usual RON UUID in-memory layout, except implementations that are likely to use platform endiannes internally.)
+
+##### Integer atom
+
+Bytes 0-7 (iiii) a 4-bit signed integer.
+
+Bytes 8-15 contain location of *raw buffer* location with unparsed integer representation.
+
+Bits 4-7 in byte 8 are set to 0101, indicating that this atom is integer atom.
+
+60 value bits of the origin word (ooo, lll) contain the raw buffer range for the original unparsed value. ooo is the offset, lll is the length, both are 30-bit unsigned integers.
+
+iiiiiiii iiiiiiii iiiiiiii iiiiiiii iiiiiiii iiiiiiii iiiiiiii iiiiiiii
+0101oooo ooooooooo ooooooooo ooooooooo oo111111 11111111 11111111 11111111
+
+##### Float atom
+
+Bytes 0-7 (ffff) contain a 64-bit float (should be IEEE 754).
+
+Bits 4-7 in byte 8 are set to 0111, indicating that this atom is a float.
+
+Bytes 8-15 contain a *raw buffer* range for the unparsed float representation, same as integer.
+
+ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
+0111oooo ooooooooo ooooooooo ooooooooo oo111111 11111111 11111111 11111111
+
+##### String atom
+
+The value word contains string metrics: byte length bbb and codepoint length ccc. These metrics are relative to a pure UTF-8 string, all escapes etc., replaced.
+
+Bits 4-7 in byte 8 are set to 0110, indicating that this atom is a string.
+
+Bytes 8-15 contain a *raw buffer* range (note the raw byte length may not match the UTF-8 byte length).
+
+0000bbbb bbbbbbbb bbbbbbbb bbbbbbbb bbcccccc cccccccc cccccccc cccccccc
+0110oooo ooooooooo ooooooooo ooooooooo oo111111 11111111 11111111 11111111
+
+#### Text format (Grammar)
+
+Text-based RON is a regular language, mostly used for its human readability.
+
+The Ragel grammar for RON UUID is:
+
+```
+
+# digits (base64, hex)
+DGT = [0-9a-zA-Z~_];
+HEX = [0-9A-F];
+
+# RON UUID variety (1st word flag bits)
+VARIETY = HEX "/" @variety;
+
+# RON UUID version char (2nd word flag bits)
+VERSION = [\$\%\+\-] @version;
+
+# 60+4 bit word (the most significant 4 bits are flags, the rest is payload)
+WORD = DGT+;
+
+# UUID value (the 1st word)
+VALUE = WORD >begin_value %end_value;
+
+# UUID origin (the 2nd word)
+ORIGIN = WORD >begin_origin %end_origin;
+
+# RON UUID (128 bits, two 60+4 bit words)
+UUID = ( VARIETY? VALUE ( VERSION ORIGIN )? ) >begin_uuid %end_uuid;
+# examples: lww, A/LED, 12345+origin, 1/0000000001+origin, some_hash%12345375868
+
+```
+
+The Ragel grammar for the text-based RON is:
+
+```
+
+# int64_t
+SGN = [\-\+];
+DIGITS = digit+;
+INT = (SGN? DIGITS ) >begin_int %end_int;
+
+# 64-bit (double) float TODO ISO syntax
+FRAC = "." DIGITS;
+EXP = [eE] SGN? DIGITS;
+FLOAT = ( SGN? DIGITS ( FRAC EXP? | EXP ) ) >begin_float %end_float;
+
+# a char TODO UTF8, escapes, \u escapes
+# UTF8 = TODO;
+
+# JSON-ey string
+UNIESC = "\\u" [0-9a-fA-F]{4};
+ESC = "\\ " [nrt\\b'"/];
+CHAR = CODEPOINT - ['\\n\\r\\"];
+
+```
+
+```
+
+STRING = ( (UNIESC|ESC|CHAR)* ) >begin_string %end_string;
+
+# op term (header op, raw/reduced op, query op)
+OPTERM = [,;:!?] @op_term;
+
+# value atom (payload) - int, float, string, UUID
+BARE_ATOM = INT | FLOAT | UUID %end_bare_uuid;
+QUOTED_ATOM =
+ "=" space* INT |
+ "^" space* FLOAT |
+ ['] STRING ['] |
+ ">" space* UUID %end_quoted_uuid ;
+ATOM = QUOTED_ATOM | space BARE_ATOM ;
+
+# op's specifier, @id :ref
+SPEC = '@' UUID %end_id space* ( ':' UUID %end_ref )? ;
+ATOMS = ATOM (space* ATOM)* ;
+
+# RON op: an immutable unit of change
+OP = (SPEC|BARE_ATOM)? space* ATOMS? space* OPTERM ;
+
+# a frame terminator (mandatory in the streaming mode)
+DOT = ".\n" ;
+
+# RON frame (open text coding)
+TEXT_FRAME = (space* OP)* space* DOT? ;
+
+```
+
+#### Binary format
+
+The binary RON format is more efficient because of higher bit density. It is also simpler and safer to parse because of explicit field lengths. Obviously, it is not human-readable.
+
+Like the text format, the binary one is only optimized for iteration. As a result of compression, records are inevitably of variable length, so random access is not possible. Also, compression depends on iteration, as UUIDs get abbreviated relative to similar preceding UUIDs.
+
+A binary RON frame starts with magic bytes RON2 and frame length. The rest of the frame is a sequence of *fields*. Each field starts with a *descriptor* specifying the type of the field and its length.
+
+Frame length is serialized as a 32-bit big-endian integer. The maximum length of a frame is $2^{30}$ bytes (a *gibibyte*). If the length value has its most significant bit set to 1, then the frame is *chunked*. A chunked frame is followed by a continuation frame. A continuation frame has no magic bytes, just a 4-byte length field. The last continuation frame must have the m.s.b. of its length set to 0.
+
+A descriptor's first byte spends four most significant (m.s.) bits to describe the type of the field, other four bits describe its length.
+
+| 128 | 64 | 32 | 16 | 8 | 4 | 2 | 1 |
+|------------|----|------------|----|--------------|---|---|---|
+| Major type | | Minor type | | Field length | | | |
+
+Field descriptor major/minor type bits are set as follows:
+
+- 1) 00 RON op descriptor,
+ - 0000 raw op,
+ - 0001 reduced op,
+ - 0010 header op,
+ - 0011 query header op.
+- 2) 01 Reserved (for binary data)
+ - 0100 type (reducer) id,
+ - 0101 object id,
+ - 0110 event id,
+ - 0111 ref/location id
+- 3) 10 Atoms, compressed (zipped chains)
+ - 1000 UUID, backreference
+ - 1001 integer list
+ - 1010 char list
+ - 1011
+- 4) 11 Atom
+ - 1100 UUID, uncompressed (lengths 1..16)
+ - 1101 integer (big-endian, zigzag-coded, lengths 1, 2, 4, 8)
+ - 1110 string (UTF-8, length $0..2^{31}-1$ )
+ - 1111 float (IEEE 754-2008, binary 16, 32 or 64, lengths 2, 4, 8 resp)
+
+A descriptor's four least significant bits encode the length of the field in question. The length value given by a descriptor does not include the length of the descriptor itself.
+
+If a field or a frame is 1 to 16 bytes long, then it has its length coded directly in the four l.s. bits of the descriptor. Zero stands for the length of 16 because most field types are limited to that length. Op terms specify no length. With string atoms, zero denotes the presence of an extended length field which is either 1 or 4 bytes long. The maximum allowed string length is 1Gb (30 bits). In case the descriptor byte is exactly 1110 0000, the m.s. bit of the next byte denotes the length of the extended length field (0 for one, 1 for four bytes). The rest of the next byte (and possibly other three) is a big-endian integer denoting the byte length of the string.
+
+Consider a time value query frame: \*now?.
+
+- 4 bytes are magic bytes (RON, 0101 0010 0100 1111 0100 1110 0011 0010)
+- frame length: 4 bytes (length 5, 0000 0000 0000 0000 0000 0000 0000 0101)
+- op term descriptor: 1 byte (0011 0000)
+- uncompressed UUID descriptor: 1 byte (cited length 3, 0100 0011)
+- now RON UUID: 3 bytes (0000 1100 1011 0011 1110 1100, the "uncompressed" coding still trims a lot of zeroes, see below).
+
+As UUID length is up to 16 bytes, UUID fields never use a separate length number. UUID descriptors are always 1 byte long. The length of 0 stands for 16.
+
+Length bits 0000 stand for:
+
+- zero length for op terms,
+- 16 for integer/float atoms, zipped/unzipped UUIDs,
+- for strings, that signals an extended length record (1 or 4 bytes).
+
+An extended length record is used for strings, as those can be up to 2 GB long. An extended length record is either 1 or four bytes. Four-byte record is a big-endian 32-bit int having its m.s. bit set to 1. Thus, strings of 127 bytes and shorter may use 1 byte long length record.
+
+#### Ops
+
+Op term fields may have cited length of 0000 or be skipped if they match the previous op's term. Nevertheless, sometimes it is necessary to introduce redundancy, CRC/checksumming, hashing, etc. Exactly for this purpose non-empty terms may be used. The checksumming method is specified by the field length (TODO).
+
+#### Atoms
+
+Strings are serialized as UTF-8.
+
+Integers are serialized using the zig-zag coding (the l.s. bit conveys the sign).
+
+Floats are serialized as IEEE 754 floats (4-byte and 8-byte support is required, other lengths are optional).
+
+## Appendix II
+
+### RON use case
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### II.1 Data bees
+
+The use case envisions drones collect data from geographically distributed sensors, e.g., in agriculture. Solar-powered sensors have limited power capacity, hence only able to carry out short-distance radio communication. There is no requirement of real-time data delivery. Still, the complete time series data has to be collected with a reasonable lag. No wired infrastructure is feasible in this case. Radio-relay networks are also difficult to maintain in the given circumstances.
+
+The solution is to use "data bees" – drones flying over the area and collecting the data using high-bandwidth short-range communication. The sensor data is accumulated in the drone's memory. Once the drone is back from the fields, the data is uploaded to the database. Sensors may not be aware of their coordinates or even current date/time. Such an information may be added by the drone. Drones launched from a mobile platform (e.g., a car) introduce an additional leg of data transfer.
+
+As all the devices and all RON events have globally unique identifiers, the data is independent of its collection procedure or place of storage, can be freely annotated and cross-referenced, matched with data from other sources. The event-based nature of RON allows for incremental synchronization.
+
+
+
+A diagram showing a drone in the center of a circular flight path, indicated by a grey arrow. The drone is positioned over a light green oval area representing a field. Scattered throughout the field are several small icons representing sensors, each consisting of a tree and a radio antenna. In the background, there is a city skyline with two buildings and a blue body of water on the left. A larger radio tower icon is positioned at the top of the field. The entire scene is enclosed within a larger light green oval boundary.
+
+Diagram illustrating the Data bee use case. A drone is shown flying in a circular path over a field. The field contains several small sensor nodes (represented by trees with antennas) and a larger base station (represented by a radio tower). The drone is collecting data from the sensors. The background shows a city skyline and a body of water.
+
+Q.3055(19)\_FII.1
+
+Figure II.1 – Data bee
+
+### II.2 RON use case: vehicle fleet telemetry
+
+The use case envisions a fleet of vehicles producing non-trivial amounts of telemetry data. The data cannot be transferred by air due to lack of coverage, lack of bandwidth and/or lack of urgency. Nevertheless, the data can be recorded locally, as a vehicle's data storage capacity is practically unlimited. Some parts of the data may be uploaded by the wireless connection in real-time, some by a wired connection during maintenance, some only inspected locally, or never inspected.
+
+RON relies on globally unique part identifiers (64 bit) used to produce globally unique event identifiers (128 bit). The latter allow to address/reference any telemetry event, globally. Independent of the particular route the data had to take, there is no confusion possible. Telemetry events may reference each other, e.g., a high-level aggregate referencing sensor data of its parts or a vehicle referencing the data from other vehicles.
+
+Uploading complete datasets might turn unfeasible. The data might as well be processed locally, with derived data referencing the original data. Another option for telemetry upload is simply sending the storage device by regular mail. Despite the intermittent connectivity of vehicular networks and all the various paths the data might take, RON data forms a single network, a "Web of machines".
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.31-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.31-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/Q/T-REC-Q.31-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..78f1238b2e8063dd5755b09fcf56979878ba8a02
--- /dev/null
+++ b/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e6805f9346b8759c0272765174ff9caacaf1133ac97a420a866f4e68a48c83e
+size 8211
diff --git a/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcd5884a9a5af41770757c8450d082cba2e93cfd
--- /dev/null
+++ b/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da26867fb7be6d7daf8a8acf5b069ad740cb76bad7df1a649dc1a96f18de5788
+size 254169
diff --git a/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg b/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c24804c61374e654ea9a1178fd6e21babebb7d73
--- /dev/null
+++ b/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/ad29805cd4f64ad2828e14feb66de664_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fe442e676181d48dd90dca2ebbe0c22fbb4a925edc78fd77873b72c859ec0fc
+size 35243
diff --git a/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e61034063b380441e8bb5aebf6e78b80847b9c71
--- /dev/null
+++ b/marked/Q/T-REC-Q.310-Q.332-198811-I_PDF-E/raw.md
@@ -0,0 +1,929 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.310-Q.332**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(11/1988)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+# --- **Specifications of Signalling System R1**
+
+ITU-T Recommendation Q.310-Q.332
+
+(Formerly CCITT Recommendation)
+
+---
+
+## ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------------------------|--------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| Basic Recommendations | Q.4–Q.9 |
+| Numbering plan and dialling procedures in the international service | Q.10–Q.11 |
+| Routing plan for international service | Q.12–Q.19 |
+| General Recommendations relative to signalling and switching systems (national or international) | Q.20–Q.34 |
+| Tones for use in national signalling systems | Q.35–Q.39 |
+| General characteristics for international telephone connections and circuits | Q.40–Q.47 |
+| Signalling for satellite systems | Q.48–Q.49 |
+| Signalling for circuit multiplication equipment | Q.50–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| Methodology | Q.60–Q.67 |
+| Basic services | Q.68–Q.79 |
+| Supplementary services | Q.80–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| General clauses | Q.100–Q.109 |
+| Transmission clauses for signalling | Q.110–Q.114 |
+| Control of echo suppressors | Q.115 |
+| Abnormal conditions | Q.116–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
+| Specifications of Signalling System No. 4 | Q.120–Q.139 |
+| Specifications of Signalling System No. 5 | Q.140–Q.179 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| General considerations | Q.600–Q.609 |
+| Logic procedures | Q.610–Q.697 |
+| Interworking of Signalling Systems No. 7 and No. 6 | Q.698 |
+| Interworking between Digital Subscriber Signalling System No. 1 and Signalling System No. 7 | Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# **Specifications of Signalling System R1**
+
+## **Summary**
+
+System R1 may be applied for automatic and semi-automatic operation of one-way and both-way circuits, within an international region (world numbering zone). When utilized in an integrated world numbering zone (e.g. Zone 1) the numbering and routing plans and operating facilities of that zone should apply.
+
+The system is applicable to all types of circuits (except TASI derived circuits) meeting CCITT transmission standards, including satellite circuits.
+
+###### **Source**
+
+ITU-T Recommendations Q.310-Q.332 was prepared by CCITT Study Group XI (1985-1988) and approved by WTSC on 18 November 1988. Those texts were originally published in Blue Book, Fascicle VI.4.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendations may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendations, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendations. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2002
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+## CONTENTS
+
+# Part I – Specifications of Signalling System R1
+
+| Rec. No. | | Page |
+|---------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------|
+| INTRODUCTION – Principles of Signalling System R1 ..... | | 1 |
+| SECTION 1 – Definition and function of signals | | |
+| Q.310 | 1. Definition and function of signals ..... | 3 |
+| SECTION 2 – Line signalling | | |
+| Q.311 | 2.1 2600 Hz line signalling..... | 5 |
+| Q.312 | 2.2 2600 Hz line signal sender (transmitter)..... | 6 |
+| Q.313 | 2.3 2600 Hz line signal receiving equipment ..... | 7 |
+| Q.314 | 2.4 PCM line signalling ..... | 9 |
+| Q.315 | 2.5 PCM line signal sender (transmitter)..... | 9 |
+| Q.316 | 2.6 PCM line signal receiver ..... | 11 |
+| Q.317 | 2.7 Further specification clauses relative to line signalling..... | 12 |
+| Q.318 | 2.8 Double seizing with both-way operation..... | 12 |
+| Q.319 | 2.9 Speed of switching in international exchanges..... | 13 |
+| SECTION 3 – Register signalling | | |
+| Q.320 | 3.1 Signal code for register signalling ..... | 14 |
+| Q.321 | 3.2 End-of-pulsing conditions – Register arrangements concerning ST signal ..... | 15 |
+| Q.322 | 3.3 Multifrequency signal sender ..... | 16 |
+| Q.323 | 3.4 Multifrequency signal receiving equipment ..... | 16 |
+| Q.324 | 3.5 Analysis of address information for routing..... | 17 |
+| Q.325 | 3.6 Release of registers..... | 18 |
+| Q.326 | 3.7 Switching to the speech position ..... | 18 |
+| SECTION 4 – Testing arrangements | | |
+| Q.327 | 4.1 General arrangements ..... | 19 |
+| Q.328 | 4.2 Routine testing of equipment (local maintenance) ..... | 19 |
+| Q.329 | 4.3 Manual testing ..... | 20 |
+| Q.330 | 4.4 Automatic transmission and signalling testing ..... | 20 |
+| Q.331 | 4.5 Test equipment for checking equipment and signals..... | 21 |
+| | Annex A to the specifications of signalling system R1 ..... | 23 |
+| Part II – Interworking of Signalling System R1 with other standardized systems | | |
+| Q.332 | 5. Interworking ..... | 25 |
+
+
+
+# PART I – SPECIFICATIONS OF SIGNALLING SYSTEM R1
+
+## INTRODUCTION
+
+## PRINCIPLES OF SIGNALLING SYSTEM R1
+
+### *General*
+
+The development of new exchanges, especially those utilizing stored programme control, has introduced new concepts in the division of functions between various components of signalling and switching systems. To allow the maximum freedom in incorporating new concepts which can contribute to the overall economy and efficiency of the system, the requirements as covered in this specification are for the combination of equipments necessary to provide a function. For example, the requirements for line signal receiving equipment as given here may be met by various subdivisions of functions between signal receiver, trunk relay sets and stored programme control.
+
+System R1 may be applied for automatic and semi-automatic operation of one-way and both-way circuits, within an international region (world numbering zone). When utilized in an integrated world numbering zone (e.g. Zone 1) the numbering and routing plans and operating facilities of that zone should apply.
+
+The system is applicable to all types of circuits (except TASI derived circuits)1) meeting CCITT transmission standards, including satellite circuits.
+
+The signalling equipment used in System R1 consists of two parts:
+
+- a) line signalling for line or supervisory signals; and
+- b) register signalling for address signals.
+
+#### a) *Line signalling*
+
+#### 1) *2600 Hz signalling*
+
+Continuous tone type in-band line-signalling is used for the link-by-link transmission of all supervisory signals except the ring-forward (forward-transfer) signal which is a spurt signal. A single frequency, 2600 Hz, is used in each direction of the 4-wire transmission path, the presence or absence of this frequency indicates a specific signal dependent upon when it occurs in the signalling sequence and in certain cases upon its duration. When the circuit is idle, a low level signalling tone is continuously present in both directions.
+
+#### 2) *PCM signalling*
+
+The 2600 Hz line signalling described in 1) is not normally applied to the speech paths of circuits working on PCM systems unless the PCM channels are connected in cascade with analogue channels to form a circuit. The signalling on PCM systems in the North American region is channel associated, in-slot, providing two signalling channels per speech channel, and utilizing bit stealing of the eighth bit of each channel every sixth frame.
+
+---
+
+1) Register signalling can be made compatible with TASI by providing a TASI locking tone.
+
+### b) *Register signalling*
+
+Link-by-link multifrequency (MF) in-band pulse signalling is used for the transmission of address information. The signalling frequencies are 700 Hz to 1700 Hz, in 200 Hz steps, and combinations of two, and two only, determine the signal. The address information is preceded by a KP signal (start-of-pulsing) and terminated by an ST signal (end-of-pulsing). Either *en bloc*2), or *en bloc* overlap2), or overlap sending may apply. This register signalling arrangement is used extensively with other in-band and out-band line signalling systems.
+
+Compandors may affect signalling, particularly short pulse compound register signals, due to pulse length distortion and the production of intermodulation frequencies. By virtue of the link-by-link signalling and the adopted duration of register and line signal pulses, System R1 functions correctly in the presence of compandors designed in accordance with CCITT recommendations.
+
+---
+
+2) See Recommendation Q.151, Note to § 3.1.1 for an explanation of these terms.
+
+## SECTION 1
+
+### DEFINITION AND FUNCTION OF SIGNALS
+
+### Recommendation Q.310
+
+## Specifications of Signalling System R1
+
+### 1. DEFINITION AND FUNCTION OF SIGNALS1)
+
+#### 1.1 **connect (seizing) signal** (sent in the forward direction)
+
+This line signal is transmitted at the beginning of a call to initiate circuit operation at the incoming end of the circuit to busy the circuit and to seize equipment for switching the call.
+
+#### 1.2 **delay-dialling signal** (sent in the backward direction)
+
+This line signal is transmitted by the incoming exchange following the recognition of the connect (seizing) signal to verify receipt of the connect (seizing) signal and to indicate that the incoming register equipment is not yet attached or ready to receive address signals.
+
+#### 1.3 **start-dialling (proceed-to-send) signal** (sent in the backward direction)
+
+This line signal is sent from the incoming exchange subsequent to the sending of a delay-dialling signal to indicate that the incoming register equipment has been connected and is ready to receive address signals.
+
+#### 1.4 **KP (start-of-pulsing) signal** (sent in the forward direction)
+
+This register signal is sent subsequent to the recognition of a start-dialling signal and is used to prepare the incoming multifrequency register for the receipt of subsequent interregister signals.
+
+##### 1.5 **address signal** (sent in the forward direction)
+
+This register signal is sent to indicate one decimal element of information (digit 1, 2, ..., 9 or 0) about the called party's number. For each call a succession of address signals is sent.
+
+##### 1.6 **ST (end-of-pulsing) signal** (sent in the forward direction)
+
+This register signal is sent to indicate that there are no more address signals to follow. The signal is always sent in semi-automatic as well as automatic working.
+
+---
+
+1) In this part the North American designation for line signals is used. The designation of the signal in System No. 5 which most nearly corresponds to a particular North American signal is shown in parentheses. There is not always exact correspondence in function, e.g. the ring-forward signal can only be effective when a connection has been established through an incoming operator.
+
+##### 1.7 **answer signal** (sent in the backward direction)2), 3)
+
+This line signal is sent to the outgoing exchange to indicate that the called party has answered.
+
+In semi-automatic working, the signal has a supervisory function.
+
+In automatic working, it is used:
+
+- to start metering the charge to the calling subscriber;
+- to start the measurement of call duration for international accounting purposes, if this is desired.
+
+##### 1.8 **hang-up (clear-back) signal** (sent in the backward direction)2)
+
+This line signal is sent to the outgoing exchange to indicate that the called party has cleared. In the semi-automatic service it performs a supervisory function.
+
+In automatic working, arrangements are made to clear the connection, stop the charging, and stop the measurement of call duration if within 10 to 120 seconds4) after recognition of the hang-up signal, the calling subscriber has not cleared. Clearing of the connection should preferably be controlled from the point where the charging is carried out.
+
+#### 1.9 **ring-forward (forward-transfer) signal** (sent in the forward direction)
+
+This line signal is initiated by an operator to recall an operator at a point further ahead in the connection.
+
+#### 1.10 **disconnect (clear-forward) signal** (sent in the forward direction)
+
+This line signal is sent in the forward direction at the end of a call when:
+
+- a) in semi-automatic working, the operator at the outgoing exchange withdraws the plug from the jack, or when an equivalent operation is performed;
+- b) in automatic working, the calling party hangs up, or when the time-out period of 10 to 120 seconds as discussed in § 1.8 above occurs.
+
+#### 1.11 *Diagrams showing signal sequence*
+
+Typical sequences of signals in semi-automatic and automatic working are shown in Annex A to these Specifications of Signalling System R1.
+
+---
+
+2) Notes on the answer and hang-up (clear-back) signals. – See corresponding notes in Recommendation Q.120, § 1.8, Volume VI-2 of the *Green Book*.
+
+3) See Recommendation Q.27 for the actions to be taken to assure that answer signals, both national and international, are transmitted as quickly as possible.
+
+4) In word numbering Zone 1, 13 to 32 seconds is used.
+
+## SECTION 2
+
+### LINE SIGNALLING
+
+#### Recommendation Q.311
+
+### 2.1 2600 HZ LINE SIGNALLING
+
+The line-signal coding arrangement is based on the application and removal of a single frequency tone (2600 Hz) as shown in Table 1/Q.311.
+
+TABLE 1/Q.311
+Line signal code
+
+| Signal | Signal direction 1), 2) | Transmitted (sending) duration | Transmitted state 5), 6) | |
+|-------------------------------------------|------------------------------------|--------------------------------|-------------------------------------|-----------------|
+| | | | Originating end | Terminating end |
+| Idle | ←→ | continuous | 0 | 0 |
+| Connect (seizing) | ---→ | continuous | 1 | 0 |
+| Delay-dialling | ←--- | continuous 3) | 1 | 1 |
+| Start-dialling (proceed-to-send) | ←--- | continuous 3) | 1 | 0 |
+| Answer | ←--- | continuous | 1 | 1 |
+| Hang-up (clear-back) | ←--- | continuous | 1 | 0 |
+| Disconnect (clear-forward) | → | continuous | 0 | 0 or 1 |
+| Ring-forward (forward-transfer) | → | 65-135 ms | 0 | 0 or 1 |
+| Busy, re-order (congestion) 4) | ←--- | – | off | on |
+
+1) →, ---→ indicates forward signalling state 0 or 1, respectively.
+
+2) ←, ←--- indicates backward signalling state 0 or 1, respectively.
+
+3) The durations of these signals are variable and depend upon when the succeeding signal occurs. To ensure proper registration of these signals, the transmitted signal durations should not be less than 140 ms.
+
+4) Busy and re-order (congestion) conditions are indicated by audible tones.
+
+5) 0: Tone on, or signalling bit state 0 in PCM systems.
+
+6) 1: Tone off, or signalling bit state 1 in PCM systems.
+
+By taking advantage of the fixed order of occurrence of specific signals, both tone-on and tone-off signals are used to indicate more than one signal condition. For example, in the backward direction tone-on is used to indicate start-dialling (proceed-to-send), and terminating end hang-up (clear-back) signals without conflict. The equipment must retain memory of the preceding signal states and the direction of signals in order to differentiate between tone-on and tone-off signals.
+
+### **2.2 2600 HZ LINE SIGNAL SENDER1) (TRANSMITTER)**
+
+##### **2.2.1 *Signal frequency***
+
+$2600 \pm 5$ Hz.
+
+##### **2.2.2 *Transmitted signal level of tone-on signals***
+
+$-8 \pm 1$ dBm0 for the duration of the signal or for a minimum of 300 ms (whichever is shorter) and for a maximum of 550 ms after which the level of the signal shall be reduced to $-20 \pm 1$ dBm0.
+
+##### **2.2.3 *Transmitted signal durations***
+
+The transmitted signal durations are shown in Table 1/Q.311.
+
+##### **2.2.4 *Signal frequency leak***
+
+The level of signal frequency leak power transmitted to the line should not exceed $-70$ dBm0, during the tone-off condition.
+
+##### **2.2.5 *Extraneous frequency components***
+
+The total power of extraneous frequency components accompanying a tone signal should be at least 35 dB below the fundamental signal power.
+
+##### **2.2.6 *Transmitting line split***
+
+The following splitting arrangements are required when transmitting line signals to prevent incorrect operation of the receiving equipment due to transients caused by the opening or closing of direct current circuits in the exchange at the transmitting end:
+
+- a) when a tone-on signal is to be transmitted, the speech path from the exchange shall be split (disconnected), if not already split, within an interval from 20 ms before, to 5 ms2) after tone is applied to the line, and remain split for a minimum of 350 ms and a maximum of 750 ms;
+- b) when a tone-off signal is to be transmitted, the speech path from the exchange shall be split (disconnected), if not already split, within an interval from 20 ms before to 5 ms after tone is removed from the line, and remain split for a minimum of 75 ms and a maximum of 160 ms after the tone is removed;
+- c) when the signalling equipment is receiving and sending tones simultaneously the split shall be maintained until:
+ - i) the transmitted tone is terminated, in which case the split must be removed in the interval from 75 to 160 ms after tone is removed [as in b)]; or
+ - ii) the incoming tone ceases, in which case the split must be removed in the interval from 350 to 750 ms after tone ceases;
+- d) when the signalling equipment is sending tone, a split shall be introduced, if not already split, within 250 ms of receipt of an incoming tone.
+
+The above requirements given in a), b), c) and d) establish a transmitting path split at both ends of the circuit during the idle condition.
+
+---
+
+1) See also Recommendation Q.112.
+
+2) The 5 ms may be relaxed to 15 ms if tone is applied while tone is being received.
+
+#### **2.3 2600 HZ LINE SIGNAL RECEIVING EQUIPMENT1)**
+
+##### **2.3.1 *Operate limits (tone-on signals)***
+
+The receiving equipment shall operate on a received tone signal, in the presence of the maximum noise expected on an international circuit, $-40$ dBm0 uniform spectral energy over the range of 300 to 3400 Hz, that meets the conditions listed below:
+
+- a)* $2600 \pm 15$ Hz;
+- b)* to ensure proper operation in the presence of noise, the signal level of the initial portion of each tone-on signal shall be augmented by 12 dB (see § 2.2.2).
+
+As a result, the following requirement reflects both the augmented and steady-state signal levels. The absolute power level $N$ of each signal is within the limits $(-27 + n \leq N \leq -1 + n)$ dBm where $n$ is the relative power level at the input to the receiving equipment. The minimum absolute power level $N = (-27 + n)$ gives a margin of 7 dB on the steady-state nominal absolute power level of the received signal at the input to the receiving equipment. With augmentation the effective margin is increased from 7 to 19 dB.
+
+The maximum absolute power level $N = (-1 + n)$ gives a margin of 7 dB on the augmented nominal absolute power level of the received signal at the input to the receiving equipment.
+
+The above tolerances are to allow for variations at the sending end and variations in line transmission.
+
+*Note* – Since higher steady noise as well as impulsive noise may be encountered on intra-regional circuits especially over certain compandored carrier systems, the maximum expected noise within a region must be taken into account in the design of equipment for that region.
+
+##### **2.3.2 *Non-operate limits***
+
+- 1) The receiving equipment shall neither operate on signals originating from subscriber stations (or other sources) if the total power in the band from 800 Hz to 2450 Hz equals or exceeds the total power present at the same time in the band from 2450 Hz to 2750 Hz, as measured at the station, nor degrade these signals. Allowances shall be made in the receiving equipment design to accommodate expected deviations from these values due to attenuation distortion and carrier frequency shift on the total transmission path between the station and the receiving equipment.
+- 2) The receiving equipment shall not operate on any tone or signal whose absolute power level at the point of connection of the receiving equipment is $(-17 - 20 + n)$ dBm or less, $n$ being the relative power level at this point.
+
+##### **2.3.3 *Recognition of signals***
+
+- 1) System R1 must be protected against false signal recognition caused by:
+ - a)* signal simulation of tone-on or tone-off signals by speech or other signals;
+ - b)* signal simulation of tone-off signals by momentary interruptions of the transmission path.
+
+The method of providing this protection is left to each Administration concerned to allow for maximum flexibility in the implementation of the signalling and switching system design. However, the overall system requirements given in 2) and 3) below shall be met.
+
+- 2) The following requirements for signal recognition are specified in terms of signal duration at the input to the signal receiving equipment and further assumes that signal levels, frequency and accompanying noise are within the limits specified in § 2.3.1:
+ - a)* A tone-on signal lasting 30 ms or less must be rejected; that is, it must not be recognized as a signal.
+
+---
+
+1) See also Recommendation Q.112.
+
+- b) A tone-off signal lasting 40 ms or less must be rejected if the previous tone-on signal is 350 ms or longer; that is, it must not be recognized as a signal.
+- c) Subsequent to establishing the cross office path, a tone-on ring-forward (forward-transfer) spurt signal lasting between 65 and 135 ms must be recognized as a valid signal.
+- d) A tone-on forward signal lasting 300 ms or longer must be recognized as a valid disconnect (clear-forward) signal. Prior to attaching a register, a forward tone-on signal lasting 30 ms or longer may be recognized as a valid disconnect (clear-forward) signal.
+- e) To protect against a momentary interruption in the transmission facility causing a continuous succession of false connect (seizing) and disconnect (clear-forward) signals, the incoming equipment should be arranged to delay responding to the second of two closely spaced connect (seizing) signals. The timed delay introduced should be started at the end of initial connect (seizing) signal or on recognition of the disconnect (clear-forward) signal. The delay introduced should be a function of the round trip signalling time. For satellite circuits the recommended time is $1300 \pm 100$ ms. For terrestrial circuits the recommended time is $500 \pm 100$ ms. If the second connect (seizing) signal persists beyond this timed interval, the signal should be considered valid and a delay dialling signal returned.
+- f) Other tone-on and tone-off signals should be recognized as valid signals, subsequent to the minimum limits imposed by a) and b) above, as soon as possible.
+
+*Note* – Delays introduced by line signalling equipment should be held to a minimum consistent with the requirements covered herein to minimize signal transfer times. Minimizing the delay is especially important in the case of the answer signal and in the case of satellite circuit operation. In this latter case, if a hang-up (clear-back) signal has not been sent prior to recognition of a disconnect (clear-forward) signal, it is necessary that the idle tone-on signal, sent by the incoming exchange in response to the disconnect signal, be recognized by the outgoing exchange prior to the elapse of the guard timing specified in Recommendation Q.317, § 2.7.1.
+
+- 3) The following signal simulation rates shall not be exceeded.
+ - a) On the average not more than one false recognition of a disconnect (clear-forward) signal shall occur per 1500 call hours of speech, at the *minimum* disconnect recognition time, as selected according to § 2.3.3, 2) c) and d). (In some older designs, this requirement may not be met, but for these cases the call hours figure must not be less than 5002) call hours.)
+ - b) On the average, not more than one false ring-forward (forward-transfer) signal shall occur per 702) call hours of speech, at the *minimum* ring-forward recognition time.
+ - c) Speech or other electrical signals as audible-tone signals, with levels up to + 10 dBm0 shall not cause any false simulation of answer signals.
+ - d) The number and characteristics of false splits of the speech path caused by speech or other signals shall not cause a noticeable reduction in the transmission quality of the circuit.
+
+##### 2.3.4 Receiving line split
+
+To prevent line signals of the signalling system from causing disturbances to signalling systems on subsequent circuits, the receiving transmission path to the connected exchange should be split when the signal frequency is received to ensure that no portion of any signal exceeding 20 ms duration may pass out of the circuit. The use of a band-stop filter for splitting is necessary since in the case of non-charged calls a continuous signal tone persists in the return transmission path during conversation. The level of signal leak current transmitted to the subsequent circuit with the band-stop filter inserted should be at least 35 dB below the received signal level. In addition, the band-stop filter must not introduce more than 5 dB loss at frequencies 200 Hz or more above or below the midband frequency nor more than 0.5 dB loss at frequencies 400 Hz or more above or below the midband frequency.
+
+The receiving line split must be maintained for the duration of the incoming tone signal, but must cease within 300 ms of tone removal.
+
+*Note* – In some existing designs, the initial cut may be a physical line disconnection but the filter must be inserted within 100 ms of tone reception.
+
+---
+
+2) In the case when no answer signal is transmitted (non-charged calls), the simulation rates specified in §§ 3 a) and 3 b) may, in some existing designs, be somewhat in excess of the values quoted.
+
+### **2.4 PCM LINE SIGNALLING**
+
+Individual channel line signalling is provided in the format of the CCITT primary multiplex operating at 1544 kbit/s (Recommendation G.733). Designated signalling bits are marked 0 or 1 corresponding to tone-on, tone-off in the single frequency in-band arrangement as shown in Table 1/Q.311. As in the in-band system, the same signalling state is used to indicate more than one signal by taking advantage of the fixed order of occurrence of specific signals. The equipment must retain memory of the preceding signal states and the direction of signals in order to differentiate between like state 0 and state 1 signals.
+
+#### **2.5 PCM LINE SIGNAL SENDER (TRANSMITTER)**
+
+##### **2.5.1 *Signalling format***
+
+The primary multiplex format is shown in Figure 1/Q.315. Per channel, in-slot signalling is accomplished by utilizing bit No. 8 in each time slot of the designated frames (6, 12, etc.) for signalling purposes. Bit No. 8 of each time slot in the intervening frames (1-5, 7-11, etc.) is used for encoding speech. Two signalling channels per speech channel are provided in the format. The multiframe alignment required for signalling purposes is obtained by subdividing the 8 kbit/s framing pulse stream into two 4 kbit/s streams, one for terminal framing and one for signalling framing (S-bits). The relationship of the framing and multiframing signals to the signalling bits is given in Table 2/Q.315. Since only one line signalling channel is required for System R1, the same signalling information is sent over both signalling channels A and B.
+
+##### **2.5.2 *Transmitted signal duration***
+
+The transmitted signal durations are given in Table 1/Q.311 of Recommendation Q.311.
+
+##### **2.5.3 *Transmitting line split***
+
+Since signalling is out-band, no transmitting line split is required.
+
+
+
+Timing diagram of a frame showing 24 time slots. The total frame duration is 125 µs (1 ± 50 × 10⁻⁶). The diagram shows a sequence of bits (5, 1, 2, 3, 4, 5, 6, 7, 8) repeating across time slots 1, 2, and 24. The label CCITT-49150 is present at the bottom right.
+
+Sampling frequency $8000 (1 \pm 50 \times 10^{-6}) \text{ Hz} = 8000 \pm 0.4 \text{ Hz}$
+ Output bit rate $1544 (1 \pm 50 \times 10^{-6}) \text{ kbit/s} = 1544 \text{ kbit/s} \pm 77 \text{ bit/s}$
+ Bits/frame 193
+ Time slots/frame 24
+ Signalling Eighth bit every sixth frame as shown in Table 2/Q.315.
+ The 8 bits in each time slot are defined in Table 2/Q.315.
+ The F-bit is time shared between terminal framing and signalling framing (S) as shown in Table 2/Q.315.
+
+FIGURE 1/Q.315
+Primary multiplex format
+
+TABLE 2/Q.315
+
+###### Multiframe structure
+
+| Frame number | Frame alignment signal | Multiframe alignment signal (S-bit) | Bit number(s) in each channel time slot | | Signalling channel |
+|--------------|------------------------|-------------------------------------|-----------------------------------------|----------------|--------------------|
+| | | | For character signal | For signalling | |
+| 1 | 1 | — | 1 to 8 | — | |
+| 2 | — | 0 | 1 to 8 | — | |
+| 3 | 0 | — | 1 to 8 | — | |
+| 4 | — | 0 | 1 to 8 | — | |
+| 5 | 1 | — | 1 to 8 | — | |
+| 6 | — | 1 | 1 to 7 | 8 | A |
+| 7 | 0 | — | 1 to 8 | — | |
+| 8 | — | 1 | 1 to 8 | — | |
+| 9 | 1 | — | 1 to 8 | — | |
+| 10 | — | 1 | 1 to 8 | — | |
+| 11 | 0 | — | 1 to 8 | — | |
+| 12 | — | 0 | 1 to 7 | 8 | B |
+
+Note 1 – The sequence shown is repetitive.
+
+Note 2 – For System R1 the same signalling information is sent on signalling channels A and B.
+
+#### **2.6 PCM LINE SIGNAL RECEIVER**
+
+##### **2.6.1 *Recognition of signals***
+
+System R1 must be protected against false signal recognition caused by signal simulation due to momentary loss of synchronization of the PCM system. The method of providing this protection is left to each Administration concerned to allow for maximum flexibility in the implementation of the signalling and switching system design. However, the overall system requirements given below must be met.
+
+- a)* A state 0 signal lasting 30 ms or less must be rejected; that is, it must not be recognized as a signal.
+- b)* A state 1 signal lasting 40 ms or less must be rejected if the previous state 0 signal is 350 ms or longer; that is, it must not be recognized as a signal.
+- c)* Subsequent to establishing the speech path, a state 0 ring-forward (forward-transfer) signal lasting 65-135 ms must be recognized as a valid signal.
+- d)* A state 0 forward signal lasting 300 ms or longer must be recognized as a valid disconnect (clear-forward) signal. Prior to attaching a register, a forward state 0 signal lasting 30 ms or longer may be recognized as a valid disconnect (clear-forward) signal.
+- e)* To protect against a momentary fault causing a continuous succession of false connect (seizing) and disconnect (clear-forward) signals, the incoming equipment should be arranged to delay responding to the second of two closely spaced connect (seizing) signals. The time delay introduced should be started at the end of the initial connect (seizing) signal or on recognition of the disconnect (clear-forward) signal. The delay introduced should be a function of the round trip signalling time. For satellite circuits the recommended time is $1300 \pm 100$ ms. For terrestrial circuits the recommended time is $500 \pm 100$ ms. If the second connect (seizing) signal persists beyond this timed interval, the signal should be considered valid and a delay dialling signal returned.
+- f)* Other state 0 and state 1 signals should be recognized as valid signals subsequent to the minimum limits imposed by *a)* and *b)* above, as soon as possible.
+
+*Note* – Delays introduced by line signalling equipment should be held to a minimum consistent with the requirements covered herein to minimize signal transfer times. Minimizing the delay is especially important in the case of the answer signal and in the case of satellite circuit operation. In this latter case, if a hang-up (clear-back) signal has not been sent prior to recognition of a disconnect (clear-forward) signal, it is necessary that the idle state 0 signal, sent by the incoming exchange in response to the disconnect signal, be recognized by the outgoing exchange prior to the elapse of the guard timing specified in Recommendation Q.317, § 2.7.1.
+
+##### **2.6.2 *Receiving line split***
+
+Since signalling is out-band, no receiving line split is required.
+
+##### **2.6.3 *Action on receipt of an alarm***
+
+When the PCM primary multiplex has detected a fault and given an alarm (see Recommendation G.733, § 3.2) appropriate action shall be taken to remove automatically the affected circuits from service, and to terminate calls in progress, i.e. stop charging, release interconnected circuits, etc. When the alarm has been cleared the affected circuits should be automatically restored to service.
+
+#### Recommendation Q.317
+
+#### 2.7 FURTHER SPECIFICATION CLAUSES RELATIVE TO LINE SIGNALLING
+
+2.7.1 Access to the outgoing circuits shall be denied (guarded) for 750 to 1250 ms (1050 ms to 1250 ms for satellite circuits) after initiation of the disconnect (clear-forward) signal to ensure sufficient time for the release of the equipment at the incoming exchange. [See also the Note to § 2.3.3, 2) of Recommendation Q.313 and to § 2.6.1 of Recommendation Q.316.]
+
+2.7.2 The disconnect (clear-forward) signal may be sent at any time in the call sequence.
+
+2.7.3 The release of the chain of circuits in an established connection is only initiated from the originating exchange or the charge-recording exchange.
+
+2.7.4 The start of metering the charge should be delayed by an appropriate time after recording of the answer signal to prevent false charging resulting from possible false recognition of an invalid answer signal.
+
+#### Recommendation Q.318
+
+### 2.8 DOUBLE SEIZING WITH BOTH-WAY OPERATION
+
+##### 2.8.1 *General*
+
+To minimize the probability of double seizing, the circuit selection at the two ends of both-way circuit groups should be such that, as far as possible, double seizing can occur only when a single circuit of the group remains free (e.g. by selection of circuits in opposite order at the two ends of the circuit group).
+
+#### 2.8.2 *Unguarded interval*
+
+In general the unguarded interval is small, except in the case of satellite operation where the circuit propagation time is long. However, System R1 does provide a means of detecting double seizing.
+
+##### 2.8.3 *Detection of double seizing*
+
+In the event of double seizing, the incoming connect (seizing) signal is recognized at each end as a delay-dialling signal. If a start-dialling (proceed-to-send) signal is not received within the time-out interval (e.g. 5 seconds) double seizing is assumed.
+
+In this event, either of the following arrangements may apply:
+
+- a) an automatic repeat attempt to set up the call; or
+- b) a recorder indication is given to the operator or to the calling subscriber and no automatic repeat attempt is made.
+
+With either method, means must be provided to ensure positive release of the double seized circuit. To achieve the release it is recommended that the office which first assumes (based on timing) that dual seizure has occurred transmits a tone-on (0 state) signal followed by a tone-off (1 state) signal before the final tone-on (0 state) signal (disconnect) is sent. The duration of initial tone-on (0 state) signal should be a minimum of 100 ms and a maximum of 200 ms. The tone-off (1 state) signal should be recognized as an unexpected tone-off (1 state) signal at the distant end, after which the action specified in § 3.6.2, 1) c) of Recommendation Q.325 applies.
+
+### **2.9 SPEED OF SWITCHING IN INTERNATIONAL EXCHANGES**
+
+2.9.1 It is recommended that the equipment in international exchanges shall have a high switching speed so that the switching time may be as short as possible.
+
+2.9.2 At the outgoing, transit and incoming international exchanges, the seizing of the circuit and the setting up of the connection should take place as soon as possible after receipt of the digits of the address that are necessary to determine the routing.
+
+2.9.3 At international exchanges the delay-dialling signal should be returned as soon as possible after recognition of the connect (seizing) signal. The start-dialling (proceed-to-send) signal should be returned as soon as possible but in any case, the return should be before the time-out of the outgoing register. [See § 3.6.2, 1) *a*) and *b*) of Recommendation Q.325.]
+
+## SECTION 3
+
+### REGISTER SIGNALLING1)
+
+#### Recommendation Q.320
+
+### 3.1 SIGNAL CODE FOR REGISTER SIGNALLING
+
+#### 3.1.1 General
+
+- 1) Either semi-automatic working (with automatic machine or direct operator access), or automatic working (with automatic machine access) may be used for outgoing traffic. With automatic machine access the incoming address signals are stored in a register until sufficient address information is received to route the call properly, at which time a free circuit may be selected and a connect (seizing) line signal sent. Subsequent to the recognition of a delay-dialling line signal and a start-dialling (proceed-to-send) line signal a KP (start-of-pulsing) signal followed by the address and ST (end-of-pulsing) signals are transmitted. The KP signal, which is nominally 100 ms in duration, prepares the receiving equipment to accept subsequent register signals. The transmission of the KP signal should be delayed by a minimum of 140 ms, but not more than 300 ms, after recognition of the start-dialling line signal.
+- 2) Link-by-link register signalling applies.
+- 3) Register signalling is in a forward direction only and shall be in accordance with the two-out-of-six multifrequency code shown in Table 3/Q.320. Three of the 15 possible codes are unused in international service and are available for special purposes.
+- 4) The receiving equipment must furnish a two-and-two only frequency check on each received signal to ensure its validity.
+
+#### 3.1.2 Sending sequence of register signals
+
+- 1) The sending sequence of address signals conforms to the sequence indicated in Recommendation Q.107. However, for traffic within an integrated world numbering zone (e.g. Zone 1) the language or discriminating digit and country codes may have no application and may not be sent. In Zone 1, the sequence of signals sent from the operator or subscriber is as follows:
+ - a) *Semi-automatic working for calls to a subscriber within Zone 1:*
+ - i) KP;
+ - ii) national (significant) number of the called subscriber;
+ - iii) ST.
+ - b) *Semi-automatic working for calls to operators within Zone 1:*
+ - i) KP;
+ - ii) special decimal numbers; 2)
+ - iii) ST.
+
+---
+
+1) As used in this Recommendation, the term register includes traditional registers in electromechanical exchanges and also the equivalent receiving device, memory and logic in stored program exchanges.
+
+2) The special numbers used to reach operators are by agreement between Administrations.
+
+- c) *Automatic working for calls to a subscriber within Zone 1:*
+- i) national (significant) number of the called subscriber.
+- 2) The sending sequence of register signals shall conform to Table 3/Q.320, noting the following:
+- a) a KP (start-of-pulsing) signal shall precede the sequence of signals in all cases;
+- b) the ST (end-of-pulsing) signal shall follow the sequence of signals in all cases.
+
+TABLE 3/Q.320
+
+##### **Register signal code of System R1**
+
+| Signals | Frequencies (compound) Hz |
+|-----------------------|---------------------------|
+| KP (start-of-pulsing) | 1100 + 1700 |
+| Digit 1 | 700 + 900 |
+| Digit 2 | 700 + 1100 |
+| Digit 3 | 900 + 1100 |
+| Digit 4 | 700 + 1300 |
+| Digit 5 | 900 + 1300 |
+| Digit 6 | 1100 + 1300 |
+| Digit 7 | 700 + 1500 |
+| Digit 8 | 900 + 1500 |
+| Digit 9 | 1100 + 1500 |
+| Digit 0 | 1300 + 1500 |
+| ST (end-of-pulsing) | 1500 + 1700 |
+| Spare | 700 + 1700 |
+| Spare | 900 + 1700 |
+| Spare | 1300 + 1700 |
+
+#### **Recommendation Q.321**
+
+### **3.2 END-OF-PULSING CONDITIONS – REGISTER ARRANGEMENTS CONCERNING ST SIGNAL**
+
+3.2.1 The register signalling arrangements shall provide for the sending of an ST signal for both semi-automatic and automatic operation; the arrangements in the outgoing international register for recognizing the ST (end-of-pulsing) signal condition may vary as follows:
+
+- a) *Semi-automatic operation*
+
+The ST condition is determined by the receipt of the end-of-pulsing signal initiated by the operator.
+
+- b) *Automatic operation*
+
+- i) Where the ST condition is determined by the originating national network, an ST signal is transmitted to the outgoing international register. No further arrangements are necessary in that register for this purpose.
+- ii) Where the ST condition is not received from the originating national network, the outgoing international register will be required to determine the ST condition. (See for example the requirements for System No. 5, Recommendation Q.152, *Green Book*).
+
+#### **3.3 MULTIFREQUENCY SIGNAL SENDER**
+
+3.3.1 Signalling frequencies 700, 900, 1100, 1300, 1500 and 1700 Hz. A signal shall consist of a combination of any two of these six frequencies. The frequency variation shall not exceed $\pm 1.5\%$ of each nominal frequency.
+
+3.3.2 Transmitted signal level $-7 \pm 1$ dBm0 per frequency. The difference in transmitted level between the two frequencies comprising a signal shall not exceed 0.5 dB.
+
+3.3.3 Signal frequency leak and modulation products. The level of the signal leak current transmitted to the line should be at least:
+
+- a) 50 dB below the single frequency level when a multifrequency signal is not being transmitted;
+- b) 30 dB below the transmitted signal level of either of the two frequencies when a multifrequency signal is being transmitted. The modulation products of a signal shall be at least 30 dB below the transmitted level of either of the two frequencies comprising the signal.
+
+3.3.4 *Signal durations*
+
+KP signal: $100 \pm 10$ ms.
+
+All other signals: $68 \pm 7$ ms.
+
+Interval between all signals: $68 \pm 7$ ms.
+
+3.3.5 *Compound signal tolerance*
+
+The interval of time between the moments when the two frequencies comprising a signal are sent must not exceed 1 ms. The interval of time between the moments when the two frequencies cease must not exceed 1 ms.
+
+#### **3.4 MULTIFREQUENCY SIGNAL RECEIVING EQUIPMENT**
+
+3.4.1 *Operate limits*
+
+The signal receiving equipment must operate satisfactorily on any combination of two of the frequencies received as a single pulse or train of pulses in the presence of maximum expected noise on an international circuit, $-40$ dBm0 uniform spectral energy over the range of 300 to 3400 Hz, that meets the conditions listed below:
+
+- a) each frequency of the received signal is within $\pm 1.5\%$ of the nominal signalling frequency;
+- b) the absolute power level $N$ of each received frequency is within the limits
+
+$$(-14 + n \leq N \leq +0 + n) \text{ dBm}$$
+
+where $n$ is the relative power level at the signal receiver input. Assuming a nominal circuit loss of 0 dB these limits give a margin of $\pm 7$ dB on the nominal absolute level of each received signal. Considering that a single equipment may serve circuits whose designed loss (nominal loss) is greater than 0 dB (e.g., circuits that are not equipped with echo suppressors) account must be taken of the highest circuit loss in the design of the receiving equipment (e.g., by increasing must-operate sensitivity) to ensure that the minimum margin is 7 dB;
+
+- c) the difference in level between the frequencies comprising a received signal is less than 6 dB;
+
+- d)* the signal receiving equipment must accept signals meeting the following conditions:
+ - i)* signals within the limits specified in *a)*, *b)*, and *c)* above in the presence of maximum expected noise and subject to the maximum expected delay distortion;
+ - ii)* the duration of each frequency comprising a signal is 30 ms or greater; and
+ - iii)* the silent interval preceding the signal is 20 ms or greater.
+
+The tolerances given in *a)*, *b)*, and *c)* are to allow for variations at the sending end and in line transmission.
+
+The test values indicated in *d)* are less than the working values. The difference between the test value and the working values will allow for pulse distortion, variations in registration devices, etc.
+
+*Note* – Since higher steady noise as well as impulsive noise may be encountered on intraregional circuits, especially over certain compandored carrier systems, the maximum expected noise within a region must be taken into account in the design of equipment for that region.
+
+#### 3.4.2 *Non-operate limits*
+
+- 1) The receiving equipment shall not operate on any signal whose absolute power level at the point of the receiving equipment is 9 dB or more below the must-operate sensitivity required to satisfy the conditions established in § 3.4.1 *b)*.
+- 2) The receiving equipment shall release when the signal level falls 1 dB below the level established in § 1) above.
+- 3) Operation of the receiving equipment shall be delayed for a minimum period necessary to guard against false operation due to spurious signals generated internally on reception of any signal.
+- 4) The receiving equipment should not operate on a pulse signal of 10 ms or less. This signal may be of a single frequency or two frequencies received simultaneously. Likewise, after operation the equipment shall ignore short interruptions of the signal frequencies.
+
+#### 3.4.3 *Input impedance*
+
+The value of the input impedance should be such that the return loss over a frequency range of 500 to 2700 Hz against a 600-ohm non-inductive resistor in series with a two-microfarad capacitor is greater than 27 dB.
+
+#### **Recommendation Q.324**
+
+### **3.5 ANALYSIS OF ADDRESS INFORMATION FOR ROUTING**
+
+In the application of System R1 to intraregional networks, the routing plan of that network shall apply. The routing plan is such that analysis is limited to a maximum of six digits.
+
+*Note* – An ISC processing an incoming call on a circuit using System R1, if encountering a barred routing or unallocated number condition, should preferably send the special information tone toward the originating subscriber.
+
+### **3.6 RELEASE OF REGISTERS**
+
+#### **3.6.1 *Normal release conditions***
+
+- 1) An outgoing register shall be released when it has transmitted the ST signal.
+- 2) An incoming register shall be released on the forward transmission of the ST signal to the next exchange, or when all pertinent information has been transferred to an outgoing register.
+
+#### **3.6.2 *Abnormal release conditions***
+
+- 1) An outgoing register shall release in any of the following situations:
+ - a) on failure to recognize a delay-dialling signal within 5 seconds of circuit seizure unless a longer interval is preferred for particular traffic conditions;
+ - b) on failure to recognize a start-dialling (proceed-to-send) signal within 5 seconds of recognition of the delay-dialling signal unless a longer interval is preferred for particular traffic conditions;
+ - c) on recognition of an unexpected tone-off (0 state) line signal subsequent to the recognition of a start-dialling (proceed-to-send) signal, but prior to completion of outpulsing. This signal sequence will occur in the event of double seizing and therefore a repeat attempt may be invoked and as a result the register may not be released prior to completion of the second attempt. (See Recommendation Q.318.);
+ - d) on exceeding overall register timing of 240 seconds.
+- 2) An incoming register shall release in any of the following situations:
+ - a) on failure to receive the KP signal within 10 to 20 seconds of register seizure;
+ - b) on failure to receive the 1st through 3rd digits within 10 to 20 seconds of receipt of the KP signal;
+ - c) on failure to receive the 4th through 6th digits within 10 to 20 seconds of the registration of the 3rd digit;
+ - d) on failure to receive the remaining digits and ST signal within 10 to 20 seconds of registration of the 6th digit;
+ - e) on error detection such as receipt of one or more than two frequencies in a pulse;
+ - f) on failure to gain access to associated switching equipment within appropriate intervals of time.
+
+The timing intervals given in 1) and 2) above are representative values but need not necessarily apply to all types of switching systems or all traffic loads.
+
+An abnormal release of an outgoing register on failure to receive a delay-dialling signal as discussed in 1) a) above, shall result in the circuit being locked out which maintains the tone-off (1 state) condition toward the distant end. The maintenance personnel should be alerted.
+
+Abnormal releases should result in the return of an audible re-order (congestion) tone toward the originating end. If this condition (re-order) persists for more than 1 to 2 minutes, maintenance personnel should be alerted.
+
+### **3.7 SWITCHING TO THE SPEECH POSITION**
+
+At all exchanges, the circuit shall be switched to the speech position when the registers (incoming or outgoing) are released.
+
+## SECTION 4
+
+### TESTING ARRANGEMENTS
+
+### Recommendation Q.327
+
+### 4.1 GENERAL ARRANGEMENTS
+
+The guiding principles for the maintenance of automatic circuits as covered in Recommendations M.700 to M.734 are in general applicable to testing of System R1.
+
+#### Recommendation Q.328
+
+### 4.2 ROUTINE TESTING OF EQUIPMENT (LOCAL MAINTENANCE)
+
+4.2.1 Test equipment for routine testing of individual items of equipment such as circuit equipment, connecting circuits, registers, etc., should be provided in every international exchange. Routine tests should be made in accordance with the practice followed in each country for the local maintenance of switching equipment and may be made with suitable semi-automatic or automatic test equipment if available.
+
+4.2.2 The testing equipment must conform to the following principles:
+
+- a) an item of equipment must not be taken for test until it is free;
+- b) an item of equipment taken for test will be marked engaged (busy) for the duration of the test. Before a circuit equipment is taken for test, the circuit will be withdrawn from service at both international exchanges;
+- c) as an alternative to b), a like item of equipment, known to be properly adjusted, may be switched in, and the item of equipment to be tested is switched out during the test.
+
+4.2.3 Testing of the circuit and signalling equipment should include a check that the specifications of System R1 are met in regard to the following:
+
+- a) *2600 Hz line signalling system:*
+ - signal frequency;
+ - transmitted signal levels;
+ - signal frequency leak;
+ - receiving equipment operate and non-operate limits;
+ - receiving-end line split;
+ - sending-end line split;
+ - sending duration of signals.
+- b) *PCM line signalling equipment:*
+ - receiving equipment operate and non-operate limits;
+ - sending duration of signals.
+
+- c) *Register signalling system:*
+- signal frequencies;
+ - transmitted signal levels;
+ - signal frequency leak;
+ - sending duration of signals;
+ - receiving equipment operate and non-operate limits;
+ - operation of the receiving equipment in response to a series of pulses;
+ - error checking features.
+
+#### **Recommendation Q.329**
+
+### 4.3 **MANUAL TESTING**
+
+#### 4.3.1 *Functional testing of signalling arrangements*
+
+Functional tests from one end of the circuit to the other can be made by verification of satisfactory signal transmission by initiating a test call to:
+
+- a) technical personnel at the distant-end international exchange; or
+- b) a test call signal testing and answering device, if such equipment is available at the distant-end international exchange.
+
+#### 4.3.2 *Test calls*
+
+- 1) Steps in the verification of satisfactory transmission of signals, involved in the completion of test calls (manual method):
+ - a) place a call to the technical personnel at the distant international exchange;
+ - b) on completion of the connection the audible ringing tone should be heard and the answer signal should be received when the call is answered at the distant end;
+ - c) request distant end to initiate a hang-up (clear-back) signal, followed by a re-answer signal;
+ - d) a hang-up (clear-back) signal should be received and recognized when the distant end hangs up and a second answer signal should be received and recognized when the distant end re-answers the call;
+ - e) initiate a ring-forward (forward-transfer) signal which should be recognized at the distant end;
+ - f) terminate the call and observe that the circuit restores to the idle condition.
+- 2) If incoming signalling testing devices are available at the distant international exchange, the signal verification tests should be made using this equipment to the extent that the applicable features indicated in 1) above are available.
+
+##### **Recommendation Q.330**
+
+### 4.4 **AUTOMATIC TRANSMISSION AND SIGNALLING TESTING**
+
+Considering that automatic transmission and signalling testing of international circuits is extremely desirable, Administrations using or intending to use System R1 are encouraged to provide for this type of testing. Existing automatic testing equipment presently in use in world numbering Zone 1, may be used. When the automatic transmission measuring and signalling testing equipment (ATME) No. 2 becomes available, it may be used as an alternative by agreement of the Administrations concerned.
+
+#### **4.5 TEST EQUIPMENT FOR CHECKING EQUIPMENT AND SIGNALS**
+
+#### **4.5.1 General**
+
+For local checks of correct equipment operation and for readjusting the equipment, international exchanges should have test equipment available which includes:
+
+- a)* line and register signal generators;
+- b)* signal-measuring apparatus.
+
+##### **4.5.2 Signal generators**
+
+The signal generators should be able to simulate all line and register signals. The generators may be part of test equipment which cycles the equipment to be tested through actual signalling sequences, in a manner which enables rapid complete testing to determine whether the equipment meets system specifications.
+
+##### **1) Line signal generator characteristics as follows:**
+
+- a)* signal frequency should be within $\pm 5$ Hz of the nominal signal frequency and shall not vary during the time required for testing;
+- b)* signal levels should be variable between the limits given in the specification and be able to be set within $\pm 0.2$ dB;
+- c)* signal durations should be long enough so that the signals can be recognized. See Recommendation Q.313, § 2.3.3.
+
+##### **2) Register signal generator characteristics as follows:**
+
+- a)* signal frequencies should be within $\pm 1.5\%$ of the nominal signal frequency or frequencies and shall not vary during the time required for testing;
+- b)* signal levels should be variable between the limits given in the specification and be able to be set within $\pm 0.2$ dB;
+- c)* signal durations and intervals between signals shall be within the limits given in the specification in Recommendation Q.322, § 3.3.4, for normal operate values and in Recommendation Q.323, § 3.4.1 *d)*, for test operate values.
+
+##### **4.5.3 Signal-measuring equipment**
+
+Equipment capable of measuring signal frequencies, signal levels, signal durations and other significant signal time intervals may be part of the test equipment referred to in § 4.5.2, or separate instruments.
+
+##### **1) Line signal measuring equipment characteristics as follows:**
+
+- a)* signal frequency between the extreme limits given in the specification should be measured with an accuracy of $\pm 1$ Hz;
+- b)* level of the signal frequency measured over the range given in the specification should be measured with an accuracy of $\pm 0.2$ dB;
+- c)* signal durations, and other significant time intervals as given in the specification should be measured with an accuracy of $\pm 1$ ms or $\pm 1\%$ of the nominal duration, whichever yields the higher value.
+
+- 2) *Register signal measuring equipment characteristics as follows:*
+- a) signal frequency or frequencies between the extreme limits given in the specification, should be measured with an accuracy of $\pm 1$ Hz;
+ - b) level of the signal frequency or frequencies over the range given in the specification should be measured with an accuracy of $\pm 0.2$ dB;
+ - c) signal duration and intervals between signals as given in the specification should be measured with an accuracy of $\pm 1$ ms.
+- 3) In regard to measuring time intervals a recorder having a minimum of two input channels may be useful. The recorder characteristic should conform with the accuracy requirements quoted in 1) and 2) above and be easily connected to the circuit under test. The recorder input characteristic should be such as to have a negligible effect on circuit performance.
+
+## **ANNEX A TO THE SPECIFICATIONS OF SIGNALLING SYSTEM R1**
+
+### **SIGNAL SEQUENCE**
+
+TABLE A-1
+
+### **Semi-automatic (SA) and automatic (A) traffic in Zone 1**
+
+
+
+| Outgoing (or transit) exchange | | Incoming (or transit) exchange | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| Idle | CALL TO FREE SUBSCRIBER
2600 Hz (0) | Idle | |
+| | ← 2600 Hz (0) | | |
+| | (1) | | |
+| The connect (seizing) signal is sent forward after the circuit is selected (the speech path is open as long as the register is attached).. | — — — — — → | Receipt of the connect (seizing) signal causes the circuit to be made busy, a delay-dialling signal to be sent (removal of tone), and the selection process of the register to be started. | |
+| | ← — — — — — | | |
+| | (1) | | |
+| 140 ms after receipt of the start-dialling (proceed-to-send) signal interregister signals are sent as follows:
– KP 3
– national significant number,
– ST. | 2600 Hz (0) | When a register is attached and ready to receive address information, a start-dialling (proceed-to-send) signal is returned (the speech path is open as long as the incoming register is attached). | |
+| | ← MF 2/6 code | | |
+| | → | The address signals are received in the incoming register. The register starts setting up the call when sufficient information has been received to determine the routing. The incoming register releases and establishes the speech path as soon as it has sent forward all the necessary information. | |
+| | | | |
+| The outgoing register releases after the ST (end-of-pulsing) signal has been sent. The speech path through the outgoing exchange is established. | | | |
+| SA: The operator or
A: the calling subscriber hears the ringing tone. | ← - - - - - | The ringing tone of the country of destination is sent back. | |
+| | | | |
+| SA: An answer indication is given to the controlling operator.
A: Charging and measurement of the call duration begins after an appropriate delay. | ← — — — — — (1) | The called subscriber answers; an answer signal (removal of tone) is sent back. | |
+| | | | |
+| SA: A clearing supervisory signal is given to the controlling operator.
A: After 13-32 seconds, if there is no disconnect (clear-forward) signal the connection is released and the charging and measurement of the call duration are ceased. | ← 2600 Hz (0) | The called subscriber clears, the hang-up (clear-back) signal is sent back. | |
+| | | | |
+| The outgoing operator (SA) or calling subscriber (A) clears. A disconnect (clear-forward) signal is sent. | 2600 Hz (0) → | | |
+| | | | |
+| The outgoing access is maintained busy for
750 to 1250 ms (cable circuits),
1050 à 1250 ms (satellite circuits). | | The disconnect (clear-forward) signal causes the release of the incoming equipment and the circuit. The disconnect signal is repeated to the next link. | |
+
+TABLE A-1 (cont.)
+
+| Outgoing (or transit) exchange | Incoming (or transit) exchange |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CALL TO A BUSY SUBSCRIBER OR CONGESTION | |
+| The signal sequence is the same as for a call to a free subscriber, up to the release of the incoming register | |
+| The operator (SA) or calling subscriber (A) hears the audible tone and clears. The disconnect (clear-forward) signal is sent.
| Busy subscriber. The audible busy tone of the country of destination is returned. Congestion. The audible congestion tone of the country of destination is returned.
|
+| SPECIAL CONDITIONS | |
+| 1. Ring-forward (forward-transfer)
Following a call established by operators, if the outgoing controlling operator wishes to recall the incoming operator, a ring-forward (forward-transfer) signal is sent.
2. Double seizing
The outgoing end sends the connect (seizing) signal.
| 2600 Hz (0) pulse ( ms)
Recalls the incoming operator.
(1) (1)
The incoming end also sends the connect (seizing) signal.
|
+| Each end interprets the connect (seizing) signal as a delay-dialling signal. If the start-dialling (proceed-to-send) signal is not recognized within the specified timing interval, double seizing is assumed and the following may apply:
- a) an automatic repeat attempt is made, or
- b) a re-order (congestion) audible tone is given to the calling subscriber or operator and no automatic repeat attempt is made.
(See Recommendation Q.318.)
| |
+
+In this table the arrows have the following meanings:
+
+- transmission of a signalling frequency (permanent or pulse emission).
+- - → end of transmission of the signalling frequency in the case of its permanent transmission.
+- - - → transmission of an audible tone.
+
+# **PART II – Interworking of Signalling System R1 with other standardized systems**
+
+#### **Recommendation Q.332**
+
+### **5. INTERWORKING**
+
+#### **5.1 *General***
+
+System R1 is capable of interworking with any of the CCITT standardized signalling systems.
+
+Specifications on interworking of System R1 with other CCITT signalling systems are not yet available.
+
+Typical information is found in Recommendation Q.180 of Fascicle VI.2.
+
+
+
+
+
+### SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3203-201108-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ad98c6e45b6c52f074f0054407ca88a640d8f1d
--- /dev/null
+++ b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58019f38be268f19eaa80c6d56d0f6b39d5741569a8f3ccc04117fa95d9c6465
+size 4016
diff --git a/marked/Q/T-REC-Q.3203-201108-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec54d4318493a3e4c9c8d5bdba17678c52bc155a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ee7446ba4ba9e62b6ffc07917f0a2eee3ff1ecf980680e05478eccbabb56d13
+size 8916
diff --git a/marked/Q/T-REC-Q.3203-201108-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1ec12a28acc9645a91d2ef1e22180a413f6a16e0
--- /dev/null
+++ b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6d0f67dfc78de3e209c7196aa25c37bc43fa2622eb6f2ae627fc1c2a0c5cf63
+size 73076
diff --git a/marked/Q/T-REC-Q.3203-201108-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..66d88125b68298669de0ea80bfc064f997f82954
--- /dev/null
+++ b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06d729a3db40ec21852668523404fafed671eec6e44f51dd1d4f838dfdbc28a5
+size 30008
diff --git a/marked/Q/T-REC-Q.3203-201108-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a39eaf17b4a61f2bcd701d9ae540367195c51a27
--- /dev/null
+++ b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/90ee16ccc0ad16aeca48087797d7b07f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00e8f88a7171d9df0b3102afd7fa2c192e1afb0f1b32034f1b1f413a30ba9162
+size 10787
diff --git a/marked/Q/T-REC-Q.3203-201108-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..988abf5a4ee05985b802ebb10931b371327ee8b1
--- /dev/null
+++ b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7bd0d152cd75a0553aec74d1c9d6845a17fe6583e360312a25686d8d090fe72
+size 25222
diff --git a/marked/Q/T-REC-Q.3203-201108-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ff2361d482738f71513dfecd2ad06f1f83ba0ed
--- /dev/null
+++ b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89dbe571517ce29a2b76586240cb5f09744242d14e44669b083f2ae8c077a9dd
+size 11997
diff --git a/marked/Q/T-REC-Q.3203-201108-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c9c47a4d7eea7e862a0e08945fb339b9866e7fc
--- /dev/null
+++ b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d70a28651a2ee31bb911a4e9e3c76c5883d413c6da615f024118988fb70f2a5
+size 74370
diff --git a/marked/Q/T-REC-Q.3203-201108-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..25d47025ed1d1f96dd3f452e48161cbf08e3e6be
--- /dev/null
+++ b/marked/Q/T-REC-Q.3203-201108-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b62cff880a4a41893e669cdec6a37fe0d32a1ebe02fcccf74da63ae76875ebb
+size 35101
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eeb6a866f5c6eeb2bcadd6c95ea9c7ca38cc65d3
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/07b17a620c75522d53916a11e12d1bff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4809676f3c871bfbabee66924c64ae9dedf1aa413023691185bcb805115dfc87
+size 91113
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abb9e3ec6dfc8364cedc39a68cf796e9d3ff5529c79a1811eedeb12c6d6e7583
+size 3787
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..00691e92038b5f3f5660402adfe4cb5d751778bb
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a4c18237361e6ddd6ad3abe4a1281e7f9c832e028be3d9bc845d6cd25f6a2e3
+size 97954
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b15bdeefb0aa95249d25f797c4f5b6676524b23
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07bd185114f6e9fd259f14b430aa134b5cd2fd5f09ca0b7adf3e8e449df77213
+size 94607
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f28e1beb80f16bb8f0a211bb7cac395f4e6e8d3e
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a31b5cc863298d3a3b37055b70353e0f655301186f09bcd91959ff966cb60c72
+size 59532
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..74e3e34e9c325f3b84501afe34517735447e001b
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f57eb8599d8ee0303c8cb1cf795e5bc9e569dd042409aba46ce5273c9096c370
+size 59794
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c8a9bf0942d471ffecc6310018975d892bb86c6
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6577808ea3eb901f4ed5c0d232710187ad95eafa0b9d98d0915bfb611342f56
+size 60651
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..53f531e284f2a84581847caa481434576ed9c291
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cdf58d126ac27ab2482345a7d01ef7fb0be60377365ec2c73bce9136fc1b6561
+size 65714
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc7c07140e902a65460d781c0761e0cb722f598f
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1fcbd16c9f92b9d1b51c63abd2798d38e5822698763d7475116259691a91bbb4
+size 84142
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8d34b9e794d3ae13585edadca63ca94c817584b
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b6b2d29a5dcda721105d3c18b147f93fd8b72c6f8e9e71968d5e865d7af46f71
+size 62951
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..95e8da736fea1858b21f7a2afb11555e1e430d1a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:929cdaca9b77348c7aa89fdc9daead6d85bbda3610b5966cb5aa38e6cf138d00
+size 63954
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16c6600a96f97a0b790dd5dc89e3d3671b266000
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:917d3f7187e261088b5670c82d76dea84123d593a48b9f6986030ddb74d8c08f
+size 89961
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8188829c76b7f80d3f31b2a26e1ee320d637213
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4515144f288c0c77867614017b5cbad45a650cec9641890197d8eb91fc7b4139
+size 62536
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0afad2b8c57443d202364d114af8b1ace2374b6a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c12df6f37de205e811d7404ef774b962dd4c57e80c1c326b353e7f47958c39f3
+size 79011
diff --git a/marked/Q/T-REC-Q.3405-201810-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a96bf0358ad89347db66ae51c62c7b3dbb4ef2cc
--- /dev/null
+++ b/marked/Q/T-REC-Q.3405-201810-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8a64203cb871e4b88ec0b574ef140290239268692acb1901fbf8d4df20490cfe
+size 80748
diff --git a/marked/Q/T-REC-Q.3611-200906-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..cca544bfddf1b0ee61a3fbc2aa2ba397d48b0121
--- /dev/null
+++ b/marked/Q/T-REC-Q.3611-200906-I_PDF-E/raw.md
@@ -0,0 +1,1756 @@
+
+
+**ITU-T**
+
+**Q.3611**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(06/2009)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for the NGN –
+Service and session control protocols – supplementary
+services
+
+---
+
+**Signalling requirements and protocol profiles
+for NGN customized ringing tone service**
+
+Recommendation ITU-T Q.3611
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3649 |
+| NGN applications | Q.3700–Q.3849 |
+| Testing for NGN networks | Q.3900–Q.3999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **Recommendation ITU-T Q.3611**
+
+## **Signalling requirements and protocol profiles for NGN customized ringing tone service**
+
+## **Summary**
+
+Recommendation ITU-T Q.3611 specifies the signalling requirements and protocol profiles for next generation network (NGN) customized ringing tone (CRT).
+
+## **Source**
+
+Recommendation ITU-T Q.3611 was approved on 29 June 2009 by ITU-T Study Group 11 (2009-2012) under Recommendation ITU-T A.8 procedures.
+
+## **Keywords**
+
+Call server, CRT, IMS, NGN, SDP, SIP.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2010
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+| | Page |
+|----------------------------------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 2 |
+| 3.1 Terms defined elsewhere ..... | 2 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 CRT service and architecture..... | 4 |
+| 5.1 General description..... | 4 |
+| 5.2 General architecture..... | 4 |
+| 5.3 Possible CRT service architectures ..... | 4 |
+| 6 Service models..... | 5 |
+| 7 Media formats..... | 6 |
+| 7.1 Audio ..... | 6 |
+| 7.2 Video ..... | 6 |
+| 7.3 Text..... | 6 |
+| 7.4 Still image..... | 6 |
+| 8 Signalling requirements ..... | 6 |
+| 8.1 Requirements for the terminating UE..... | 6 |
+| 8.2 Requirements for the terminating P-CSC-FE..... | 7 |
+| 8.3 Requirements for the I-CSC-FE ..... | 7 |
+| 8.4 Requirements for the S-CSC-FE ..... | 7 |
+| 8.5 Requirements for the IBC-FE..... | 8 |
+| 8.6 Requirements for the call server..... | 8 |
+| 8.7 Requirements for the AS-FE ..... | 8 |
+| 9 Protocol profiles..... | 10 |
+| 9.1 IMS-based CRT service ..... | 10 |
+| 9.2 Call-server based CRT service ..... | 12 |
+| 10 Interactions between networks ..... | 12 |
+| 10.1 Providing circuit switched network CRT to the terminating UE in the
NGN domain ..... | 12 |
+| 10.2 Providing NGN CRT to the called party in the circuit switched network
domain ..... | 13 |
+| 11 Interactions with other services on NGN..... | 13 |
+| 11.1 Originating identification presentation (OIP)..... | 13 |
+| 11.2 Originating identification restriction (OIR)..... | 13 |
+| 11.3 Terminating identification presentation (TIP)..... | 13 |
+| 11.4 Terminating identification restriction (TIR)..... | 13 |
+
+| | Page | |
+|-------------------------------------|-----------------------------------------------------------------------|----|
+| 11.5 | Communication HOLD (HOLD) ..... | 13 |
+| 11.6 | Call Waiting (CW) services..... | 14 |
+| 11.7 | Communication diversion (CDIV) services ..... | 14 |
+| 11.8 | Explicit communication transfer (ECT) service..... | 14 |
+| 11.9 | Originating CRT service interacting with terminating CRT service..... | 14 |
+| 12 | Security considerations ..... | 14 |
+| Annex A – Multi-dialog mode ..... | | 16 |
+| A.1 | General description..... | 16 |
+| A.2 | Signalling requirements ..... | 16 |
+| Appendix I – Signalling flows ..... | | 18 |
+| I.1 | CRT service using gateway model ..... | 18 |
+| I.2 | CRT service using application server model..... | 23 |
+| I.3 | CRT service using HTTP model ..... | 27 |
+| I.4 | CRT service priority using application server model..... | 29 |
+| Bibliography..... | | 37 |
+
+# Recommendation ITU-T Q.3611
+
+## Signalling requirements and protocol profiles for NGN customized ringing tone service
+
+# 1 Scope
+
+This Recommendation specifies signalling requirements and protocol profiles for NGN customized ringing tone (CRT) service. This Recommendation also contains signalling flows.
+
+The CRT service is defined in the next generation network (NGN), including IP multimedia subsystem (IMS) and call-server based networks. This Recommendation is based on [b-ITU-T Y.2214] and covers in this version only the signalling requirements and protocol profiles for the presentation features of CRT. The capability for the CRT filtering features is for further study.
+
+This Recommendation covers the protocol profiles over user network interface (UNI) and network-to-network interface (NNI) based on [ITU-T Q.3402] and [ITU-T Q.3401], respectively. Detailed protocol profiles for other interfaces may be subject to future specifications.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T Q.763] Recommendation ITU-T Q.763 (1999), *Signalling System No. 7 –ISDN User Part formats and codes*.
+- [ITU-T Q.3401] Recommendation ITU-T Q.3401 (2007), *NGN NNI signalling profile (Protocol Set 1)*; Amendment 1 (2008).
+- [ITU-T Q.3402] Recommendation ITU-T Q.3402 (2008), *NGN UNI signalling profile (Protocol Set 1)*.
+- [ITU-T T.81] Recommendation ITU-T T.81 (1992) | ISO/IEC 10918-1:1994, *Information technology – Digital compression and coding of continuous-tone still images – Requirements and guidelines*.
+- [ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), *Functional requirements and architecture of the NGN release 1*.
+- [ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), *Security requirements for NGN release 1*.
+- [IETF RFC 2616] IETF RFC 2616 (1999), *Hypertext Transfer Protocol – HTTP/1.1*.
+- [IETF RFC 3261] IETF RFC 3261 (2002), *SIP: Session Initiation Protocol*.
+- [IETF RFC 3262] IETF RFC 3262 (2002), *Reliability of Provisional Responses in the Session Initiation Protocol (SIP)*.
+- [IETF RFC 3311] IETF RFC 3311 (2002), *The Session Initiation Protocol (SIP) UPDATE Method*.
+
+- [IETF RFC 3372] IETF RFC 3372 (2002), *Session Initiation Protocol for Telephones (SIP-T), Context and Architectures*.
+- [IETF RFC 3515] IETF RFC 3515 (2003), *The Session Initiation Protocol (SIP) Refer Method*.
+- [IETF RFC 3959] IETF RFC 3959 (2004), *The Early Session Disposition Type for the Session Initiation Protocol (SIP)*.
+- [IETF RFC 3960] IETF RFC 3960 (2004), *Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)*.
+- [IETF RFC 5009] IETF RFC 5009 (2007), *Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 early media** [IETF RFC 3959]: The media (e.g., audio and video) that is exchanged before a particular session is accepted by the called user.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 called CRT service subscriber**: The called party who subscribes to the called party configured CRT service.
+
+**3.2.2 calling CRT service subscriber**: The calling party who subscribes to the CRT service.
+
+**3.2.3 CRT service user**: The called party who experiences the CRT service.
+
+**3.2.4 early media for CRT**: Early media that are delivered to the called party with the media contents configured by the service subscriber. It can be generated by the originating network or the terminating network, depending on the location of service subscriptions.
+
+**3.1.5 icon ring tone server (IRT server)**: Icon ring tone server (IRT) stores the ringing tone media such as audio, video and picture files. The IRT server behaves as a web server and can be provided by content providers or operators. A user terminal can interact with the IRT server via, for example, HTTP, to download the ringing tone media.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-------|---------------------------------------|
+| AS | Application Server |
+| AS-FE | Application Support Functional Entity |
+| AVP | Audio Video Profile |
+| CDIV | Communication DIVersion |
+| CFNR | Call Forwarding on No Reply |
+| CRT | Customized Ringing Tone |
+| CSN | Circuit Switched Network |
+| ECT | Explicit Communication Transfer |
+| HOLD | Communication HOLD |
+
+| | |
+|----------|----------------------------------------------------------|
+| HTTP | HyperText Transfer Protocol |
+| IAM | Initial Address Message |
+| IBC-FE | Interconnection Border Gateway Control Functional Entity |
+| I-CSC-FE | Interrogating Call Session Control Functional Entity |
+| IMS | IP Multimedia Subsystem |
+| IRT | Icon Ring Tone |
+| MGC-FE | Media Gateway Control Functional Entity |
+| MRC-FE | Media Resource Control Functional Entity |
+| MRFC | Media Resource Function Controller |
+| MRP-FE | Media Resource Processing Functional Entity |
+| NGN | Next Generation Network |
+| NNI | Network-to-Network Interface |
+| OIP | Originating Identification Presentation |
+| OIR | Originating Identification Restriction |
+| P-CSC-FE | Proxy Call Session Control Functional Entity |
+| RTCP | RTP Control Protocol |
+| RTP | Real-Time Transport Protocol |
+| S-CSC-FE | Serving Call Session Control Functional Entity |
+| SDP | Session Description Protocol |
+| SIP | Session Initiation Protocol |
+| SIP UA | SIP User Agent |
+| SUP-FE | Service User Profile Functional Entity |
+| TIP | Terminating Identification Presentation |
+| TIR | Terminating Identification Restriction |
+| UAC | User Agent Client |
+| UAS | User Agent Server |
+| UDP | User Datagram Protocol |
+| UE | User Equipment |
+| UE-A | User Equipment for user A |
+| UE-B | User Equipment for user B |
+| UNI | User-to-Network Interface |
+| URL | Uniform Resource Locator |
+| UUI | User-to-User Information |
+
+# 5 CRT service and architecture
+
+## 5.1 General description
+
+The customized ringing tone (CRT) service provides the called party with the calling party's customized ringing tone. The service can be subscribed by the calling party or the called party. The service is invoked to provide customized ringing tone to the called party, according to the service configuration. The CRT contents can be multimedia representing avatar, business card, etc. The calling party subscribed to CRT is always triggered at the originating network's service system. Otherwise, the called party subscribed to CRT is always triggered at the terminating network's service system.
+
+To protect the called party from possible malicious CRT contents, the network should provide the capability for the called party to reject CRT (e.g., reject CRT unconditionally, for unknown parties, for black listed parties, etc.). The capability for the CRT filtering features is for further study.
+
+## 5.2 General architecture
+
+The CRT service is defined and provided in the NGN architecture, which is either IMS-based or call-server based. Figure 5-1 shows a general architecture that is compliant with [ITU-T Y.2012] for providing the CRT service based on IMS and call-server networks, respectively.
+
+
+
+The diagram illustrates the functional architecture for the CRT service across two networks: the Originating network and the Terminating network, connected via an NGN NNI (Network-to-Network Interface). Both networks share a similar three-layer structure:
+
+- Service stratum:** Contains the **ASF/SSF** (Application Server/Service Server) which hosts the **CRT service**.
+- SCF (Service Control Function):** Contains the **Call server component** and the **IMS component**.
+- Transport stratum:** The bottom layer responsible for data transport.
+
+Vertical connections within each network show the **Service stratum** connected to the **SCF**, which is in turn connected to the **Transport stratum**. The **SCF** in the originating network is connected to the **SCF** in the terminating network via the **NGN NNI**. On the far right, a **Terminating end user function** is connected to the **Transport stratum** of the terminating network via the **NGN UNI** (Network-to-User Interface). The diagram is labeled with 'Q.3611(09)\_F5.1' in the bottom right corner.
+
+Figure 5-1: CRT service functional architecture diagram showing the flow between an originating network and a terminating network.
+
+**Figure 5-1 – CRT service functional architecture**
+
+## 5.3 Possible CRT service architectures
+
+Originating IMS-based and call-server based possible service architectures for the CRT service are shown in Figures 5-2 and 5-3, respectively. The terminating IMS-based possible scenarios for the calling party configured CRT service are shown in Figure 5-4.
+
+These figures show general scenarios assuming that the originating network is different from the terminating network. Although the functional architectures are different for IMS- and call-server based networks, the service control mechanisms are identical.
+
+
+
+Figure 5-2: Originating IMS-based CRT service architecture diagram. The diagram shows an 'Originating network' containing a 'CRT service' block with SUP-FE, AS-FE, MRC-FE, S-CSF-FE, and P-CSC-FE. An I-CSF-FE is shown in a dashed box. Below the service stratum is a 'Transport stratum' with MRP-FE. This connects to a 'Terminating network' which also has 'Service stratum' and 'Transport stratum' layers. The transport stratum connects to a 'CRT service user' box containing 'Terminating end user function'. Reference Q.3611(09)\_F5.2 is at the bottom right.
+
+**Figure 5-2 – Originating IMS-based CRT service architecture**
+
+
+
+Figure 5-3: Originating call-server based CRT service architecture diagram. The 'Originating network' contains a 'CRT service' block with SUP-FE, AS-FE, MRC-FE, a 'Call server', and IBC-FE (in a dashed box). Below is the 'Service stratum' and 'Transport stratum' with MRP-FE. It connects to a 'Terminating network' with similar strata, which then connects to a 'CRT service user' box with 'Terminating end user function'. Reference Q.3611(09)\_F5.3 is at the bottom right.
+
+**Figure 5-3 – Originating call-server based CRT service architecture**
+
+
+
+Figure 5-4: Terminating IMS-based CRT service architecture diagram. The 'Originating network' has 'Service stratum' and 'Transport stratum' layers. It connects to a 'Terminating network' containing a 'CRT service' block with AS-FE, SUP-FE, MRC-FE, S-CSC-FE, and P-CSC-FE. An I-CSC-FE is shown in a dashed box. Below the service stratum is a 'Transport stratum' with MRP-FE. This connects to a 'CRT service user' box containing 'Terminating end user function'. Reference Q.3611(09)\_F5.4 is at the bottom right.
+
+**Figure 5-4 – Terminating IMS-based CRT service architecture**
+
+# 6 Service models
+
+There are three models for ringing tone generations. The CRT service is provided based on at least one of these service models, and can be provided with more than one model.
+
+**Gateway model** is to establish early media sessions in the same way as regular sessions, using an offer/answer exchange. The gateway model consists of managing early media sessions using offer/answer exchanges in reliable provisional exchanges, PRACKs, and
+
+UPDATES [IETF RFC 3960]. In case of non-reliable provisional exchanges, re-INVITE can be used.
+
+| | |
+|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Application server model | is to establish early media by distinguishing early sessions from regular sessions by using the early-session option tag. By indicating support of the early-session disposition type in the user agent server (UAS), the user agent client (UAC) knows that offer/answer exchanges for early media (early-session disposition type) are kept separate from regular media (session disposition type) [IETF RFC 3960]. |
+| HTTP model | is to provide the web URL of the subscriber's repository for CRT contents to be presented during early session. This information is filled by and delivered from the CRT service system, within the initial INVITE. |
+
+# 7 Media formats
+
+In order to guarantee a certain level of early media support and compatibility between the calling and called party terminals, appropriate media formats shall be negotiated or selected to play the CRT contents.
+
+## 7.1 Audio
+
+If audio is supported, the codec list shall be as specified in clause 8.1 of [ITU-T Q.3401] and [ITU-T Q.3402].
+
+## 7.2 Video
+
+If video is supported, the codec list shall be as specified in clause 8.1 of [ITU-T Q.3401] and [ITU-T Q.3402].
+
+## 7.3 Text
+
+If plain text is supported, any character encoding (charset) that contains a subset of the logical characters (e.g., Unicode [b-Unicodelist]) may be used.
+
+## 7.4 Still image
+
+If still image is supported, JPEG encoding in compliance with [ITU-T T.81] shall be supported. In addition, the interchange format described in [b-JFIF] may be used with JPEG. Other encoding formats (e.g., GIF ([b-GIF87a], and [b-GIF89a]), or PNG ([b-IETF RFC 2083])) may be supported.
+
+# 8 Signalling requirements
+
+The following clauses describe the signalling requirements for providing CRT services in each functional entity.
+
+## 8.1 Requirements for the terminating UE
+
+### 8.1.1 Requirements for supporting CRT on gateway model
+
+If the terminating user equipment (UE) receives an initial INVITE request, and wishes to receive early media, it should:
+
+- Send out SDP answer via a response bearing a 18x code to the initial INVITE request towards the originating side, or
+- Send SDP answer in the response of UPDATE [IETF RFC 3311] method.
+
+### **8.1.2 Requirements for supporting CRT on application server model**
+
+If the terminating UE wishes to receive early media authorization descriptions, as described in [IETF RFC 3959], when it receives the initial INVITE request which has set the "early-session" option tag in the Require header field, it shall reply with a normal provisional response bearing a 18x code indicating that the terminating UE supports early-session disposition type SDP and should set the "100rel" option tag in the Require header field.
+
+### **8.1.3 Requirements for supporting CRT on HTTP model**
+
+The terminating UE shall support Alert-Info and/or Call-Info header field as specified by [IETF RFC 3261] and [IETF RFC 3960].
+
+If the media file indicated in the Alert-Info or Call-Info header field has been downloaded, the terminating UE should play the downloaded information to override the locally generated ring information, except if the user denies or stops it.
+
+### **8.1.4 Requirements for supporting multiple CRT service models**
+
+When multiple models are applied, the terminating UE may be configured to determine whether to play downloaded information only and/or early media information if different media types are involved, and if the same media type is involved, then the preference is set by the local policy.
+
+### **8.1.5 Requirements when user answers the communication**
+
+For the gateway model, the terminating UE does not need to distinguish between early media and regular media before a final answer is received, so there is no requirement for the terminating UE in this case.
+
+For the application server model, if the terminating UE uses a different media port and/or a connect address for regular media and early media, when the user answers the dialog, the UE should stop playing early media information.
+
+If the HTTP model is applied, the terminating UE should have the local policy to determine whether to keep playing the CRT contents while conversing with the originating UE.
+
+## **8.2 Requirements for the terminating P-CSC-FE**
+
+### **8.2.1 Requirements for supporting CRT on gateway model**
+
+The P-CSC-FE may add, remove, or modify the P-Early-Media header field within the forwarded SIP requests and responses, according to the procedures in [IETF RFC 5009].
+
+### **8.2.2 Requirements for supporting CRT on application server model**
+
+The P-CSC-FE may add, remove, or modify, the early-session SDP within the forwarded SIP requests and responses, according to procedures in [IETF RFC 3959].
+
+### **8.2.3 Requirements for supporting CRT on HTTP model**
+
+The P-CSC-FE may have local policy to remove, or modify the Alert-Info, and/or Call-Info header field.
+
+## **8.3 Requirements for the I-CSC-FE**
+
+CRT has no impact on this FE.
+
+## **8.4 Requirements for the S-CSC-FE**
+
+CRT has no impact on this FE.
+
+## **8.5 Requirements for the IBC-FE**
+
+### **8.5.1 Requirements for supporting CRT on gateway model**
+
+The IBC-FE may add, remove, or modify the P-Early-Media header field within the forwarded SIP requests and responses, according to the operator's policy.
+
+### **8.5.2 Requirements for supporting CRT on application server model**
+
+The IBC-FE may add, remove, or modify the early-session SDP within the forwarded SIP requests and responses, according to the operator's policy.
+
+### **8.5.3 Requirements for supporting CRT on HTTP model**
+
+The IBC-FE may have the local policy to remove, or modify the Alert-Info, and/or Call-Info header field.
+
+## **8.6 Requirements for the call server**
+
+CRT has no impact on this FE.
+
+## **8.7 Requirements for the AS-FE**
+
+The requirements in this clause are for invocation and operation of the CRT service. The activation, deactivation, and configuration of the CRT service are out of scope of this Recommendation.
+
+The AS-FE provides CRT service regardless of whether the session systems are call-server or IMS-based.
+
+### **8.7.1 Requirements for providing CRT service by gateway model**
+
+The AS-FE shall apply CRT service after receiving a response bearing a 18x code with SDP answer to the initial INVITE request.
+
+If the CRT service can be applied, the AS-FE shall:
+
+- a) Send a CRT SDP offer via PRACK/UPDATE request towards the terminating side; and
+- b) If the initial INVITE request carries a SDP offer with precondition, send the SDP answer in the response bearing a 18x code towards the originating side.
+
+The AS-FE may not forward the originating side SDP offer in the PRACK/UPDATE request towards the terminating side.
+
+The AS-FE may set all the media types bandwidth in the SDP towards the originating side to 0, in order to avoid RTCP error.
+
+### **8.7.2 Requirements for providing CRT service by application server model**
+
+If the initial INVITE request is received, then the AS-FE shall:
+
+- a) If the provisional response has no "early-session" option tag in the Require header field, set the "early-session" option tag in the Require header field;
+- b) If the provisional response has no "100 rel" option tag in the Require header field, set the "100rel" option tag in the Require header field;
+- c) Send the INVITE request towards the terminating UE.
+
+If the INVITE request's 420 error response with "early-session" option tag in the Unsupported header field is received, it indicates that the terminating UE does not support early-session, then the AS-FE shall:
+
+- a) Provide CRT service by gateway model or HTTP model or multi-dialogue model;
+
+- b) Remove the "early-session" option tag in the Require header field in the previous INVITE request;
+- c) Send the revised INVITE request towards the terminating UE.
+
+If the INVITE request provisional response bearing a 18x code is received, it indicates that the terminating UE supports early-session, then the AS-FE shall:
+
+- a) If the provisional response has no "100rel" option tag in the Require header field, set the "100rel" option tag in the Require header field;
+- b) Send the provisional response towards the originating UE.
+
+If a PRACK request to the INVITE request provisional response bearing a 18x code is received, according to [IETF RFC 3959], the AS-FE shall:
+
+- a) If terminating side does not indicate "100rel" in the Require header field, transfer the PRACK request to the UPDATE request;
+- b) Acquire SDP for CRT from MRFC;
+
+NOTE – The SDP for CRT can be acquired by sending an INVITE request without SDP to MRFC.
+
+- c) Add new message body that has early-session disposition type in the PRACK/UPDATE request to contain the acquired SDP;
+- d) Set "early-session" option tag in the Require header field if it does not exist;
+- e) Send the PRACK/UPDATE request towards the terminating UE.
+
+If a final answer is received by the AS-FE on a dialog, the AS-FE should stop the early media CRT information on the answering dialog.
+
+### **8.7.3 Requirements for providing CRT service by HTTP model**
+
+If an initial INVITE request is received, then, according to [IETF RFC 3261] and [IETF RFC 3960], the CRT AS-FE is required to act as follows:
+
+- a) If an iconic photo, photo explanation text, and/or card information need to be presented on the terminating UE's screen, the AS-FE should add a Call-Info header field in the INVITE request, and, according to [IETF RFC 3261], set the HTTP protocol address of the iconic photo file in the Call-Info header field using "icon" value for the purpose parameter, set the photo explanation text in the Call-Info header field using "info" value for the purpose parameter, and/or set the card information in the Call-Info header field using "card" value for the purpose parameter;
+- b) If a multimedia information needs to be played on the terminating UE, the AS-FE may add an Alert-Info and/or Call-Info header field, and set the HTTP URL of the multimedia file to the value of the Alert-Info/Call-Info header field;
+- c) Shall send the INVITE request towards the terminating UE.
+
+NOTE – It is recommended that the size of the multimedia file and photo file be small in order not to delay communication establishment.
+
+### **8.7.4 Requirements for supporting multiple models**
+
+If either gateway model or application server model is applied, the AS-FE should have the policy to determine whether to play downloaded information and/or early media information if different media types are involved, and if the same media type is involved, then preference is set by the policy.
+
+This policy should be configured by the calling CRT service subscriber, the called CRT service subscriber, the originating network's operator or the terminating network's operator.
+
+### 8.7.5 Requirements when user answers the communication
+
+If the CRT service is provided by the application server model/gateway model, the AS-FE should stop the early media CRT information on the answering dialog.
+
+If the CRT service is provided by the gateway model, before forwarding the final answer, the AS-FE shall:
+
+- send the originator's SDP offer via a re-INVITE request towards the terminating side, then after getting the SDP answer from the terminating side, send it via a "200 OK" response towards the originating side; or
+- query the terminator's SDP offer by sending a re-INVITE request without SDP towards the terminating side, then after getting the SDP offer, send it via a "200 OK" response towards the originating side.
+
+If the CRT service is provided by the HTTP model, there is no requirement.
+
+# 9 Protocol profiles
+
+The protocol profiles for CRT service shall be based on the following ITU-T Recommendations.
+
+**Table 9-1 – Base Recommendations for CRT protocol profiles**
+
+| Profile | Interval | Protocol | Recommendation |
+|---------|-------------------------------------------------------------------------------------------------------|----------|----------------|
+| NGN UNI | Between the terminating end user function and the service control function in the terminating network | SIP/SDP | [ITU-T Q.3402] |
+| NGN NNI | Between the service control functions of originating and terminating networks | SIP/SDP | [ITU-T Q.3401] |
+
+This clause provides CRT service specific messages and headers among the above Recommendations and relevant RFCs.
+
+Other messages and headers that are not specific for CRT may be supported, as specified in the base Recommendations in Table 9-1, if they are not explicitly specified in this Recommendation.
+
+The three service models (gateway, application server and HTTP) defined in clause 6 are not applicable to legacy terminals (e.g., terminals which are not attached via NGN UNI) in the terminating network.
+
+## 9.1 IMS-based CRT service
+
+### 9.1.1 Protocol profiles for gateway model
+
+If early media is established with the gateway model, the UPDATE method shall be used as defined in [IETF RFC 3311].
+
+If early media connection is established by the exchanges of initial INVITE and non-reliable provisional response, after finishing early media session, regular session can be made by media re-negotiation exchanging second Offer SDP and Answer SDP after completion of the first dialogue.
+
+Unidirectional early media may also be supported by responding to initial INVITE with non-reliable provisional response before sending actual media. The regular session is then established by responding with final SDP answer to the initial INVITE.
+
+Table 9-2 illustrates the SIP messages that are specific to the CRT service. Other SIP messages may be supported as specified in the base Recommendations in Table 9-1.
+
+**Table 9-2 – CRT service specific methods and headers for gateway model**
+
+##### **a) Early session establishment**
+
+| Method/response | Code | Header | Code | Option tag | References |
+|-----------------|------|--------|------|------------|------------|
+| UPDATE | M | – | – | – | RFC 3311 |
+
+##### **b) Regular session establishment**
+
+| Method/response | Code | Header | Code | Tag | Reference |
+|--------------------|------|--------|------|-----|-----------|
+| UPDATE – 200 OK | M | – | – | – | RFC 3311 |
+| re-INVITE – 200 OK | O | – | – | – | RFC 3261 |
+
+In order to make regular dialogue after early dialogue finishes, there are two possibilities:
+
+- a) final response 200 OK delivery regular Answer
+- b) re-establishment of session with re-INVITE
+
+See clause I.1 for detailed signalling flows and messages.
+
+### **9.1.2 Protocol profiles for application server model**
+
+##### **9.1.2.1 SIP profile**
+
+Initial INVITE shall include SDP. If early media session is established with the reliable provisional response, the PRACK method shall be used as defined in [IETF RFC 3262].
+
+If early media session is provided, the option tag "early-session" shall be supported, the disposition type "early-session" shall be supported, and the content type "multipart/mixed" may be supported to specify distinctive session types (e.g., regular session and early session) within a single message, as defined in [IETF RFC 3959].
+
+Table 9-3 illustrates the SIP messages that are specific to the CRT service. Other SIP messages may be supported as specified in the base Recommendations in Table 9-1.
+
+**Table 9-3 – CRT service specific methods and headers for application server model**
+
+| SCF/CRT AS-FE → Terminating EUF | | | | | |
+|---------------------------------|------|--------------|------|----------------------------------|-----------|
+| Request method | code | Header | code | Description | Reference |
+| INVITE | M | Supported | M | Supported: 100rel, early-session | RFC 3262 |
+| | | Require | M | Require: 100rel, early-session | |
+| | | Content-Type | O | Content-Type: multipart/mixed | |
+| PRACK | M | RAck | M | – | |
+
+| Terminating EUF → SCF/CRT AS-FE | | | | | |
+|----------------------------------------|-------------|---------------|-------------|--------------------------------|------------------|
+| Response method | code | Header | code | Description | Reference |
+| 18x | M | RSeq | O | – | RFC 3262 |
+| | | Require | O | Require: 100rel, early-session | RFC 3959 |
+
+#### 9.1.2.2 SDP profile
+
+Different types of media such as audio, video, text and image can be utilized as different ringing tones. Each media type shall be specified in "m=" line (i.e., m=text, m=audio, m=video).
+
+### 9.1.3 Protocol profiles for HTTP model
+
+If the CRT URL information is delivered in provisional response, INVITE shall include Call-Info header and 'purpose' parameters or/and Alert-Info header as defined in [IETF RFC 3261].
+
+Table 9-4 illustrates the SIP messages that are specific to the CRT service
+
+**Table 9-4 – CRT service specific methods and headers for HTTP model**
+
+| SCF/CRT AS-FE → Terminating EUF | | | | | |
+|----------------------------------------|-------------|---------------|-------------|-------------------|------------------|
+| Method/response | Code | Header | Code | Option tag | Reference |
+| INVITE | M | Call-Info | M | purpose | RFC 3261 |
+| | | Alert-Info | O | – | |
+
+The called party shall support HTTP/1.1 as defined in [IETF RFC 2616] in order to get CRT contents.
+
+See clause I.3 for signalling flows and message usages.
+
+## 9.2 Call-server based CRT service
+
+For the originating call-server based network, the protocol profiles described in clause 9.1 are applicable for the service models : gateway model, application server model, and HTTP model.
+
+For the terminating call-server based network, CRT is not applicable.
+
+# 10 Interactions between networks
+
+## 10.1 Providing circuit switched network CRT to the terminating UE in the NGN domain
+
+For the CRT service activated in circuit switched networks (CSN), upon receipt of the initial address message (IAM) with the CRT text in UUI [ITU-T Q.763], and if the MGC-FE supports the Call-Info header as a UUI mapping option, and has received the CRT text in the IAM request, then the MGC-FE shall send INVITE with CRT content information in Call-Info header.
+
+Service providers may send a service indicator in UUI to MGC-FE, and MGC-FE may retrieve the CRT contents.
+
+
+
+Sequence diagram showing signalling interaction from CSN to NGN. A vertical line represents the MGC-FE. An arrow labeled 'INVITE (CRT text in call-info)' points left from the MGC-FE. Another arrow labeled 'IAM (CRT text in UUI)' points right towards the MGC-FE. A dashed line below the first arrow is labeled 'CRT information' and 'Q.3611(09)\_F10.1'.
+
+**Figure 10-1 – Signalling interaction from CSN to NGN**
+
+## 10.2 Providing NGN CRT to the called party in the circuit switched network domain
+
+For the CRT service activated in the NGN, upon receipt of the INVITE with the CRT text in Call-Info header, and if the MGC-FE supports the UUI as a network option, and has received the CRT text in the INVITE request, then the MGC-FE shall send IAM with a CRT text in UUI.
+
+
+
+Sequence diagram showing signalling interaction from NGN to CSN. A vertical line represents the MGC-FE. An arrow labeled 'INVITE (CRT text in Call-Info)' points left from the MGC-FE. Another arrow labeled 'IAM (CRT text in UUI)' points right towards the MGC-FE. A dashed line below the first arrow is labeled 'CRT information' and 'Q.3611(09)\_F10.2'.
+
+**Figure 10-2 – Signalling interaction from NGN to CSN**
+
+Service providers may send a service indicator in the Call-Info header to MGC-FE, and MGC-FE may retrieve the CRT contents.
+
+# 11 Interactions with other services on NGN
+
+## 11.1 Originating identification presentation (OIP)
+
+No impact on CRT service.
+
+## 11.2 Originating identification restriction (OIR)
+
+If the CRT service is associated with the originator's id information, CRT AS-FE shall not apply the service on the communication if OIR service has restriction rules on the originating identity information.
+
+## 11.3 Terminating identification presentation (TIP)
+
+No impact on CRT service.
+
+## 11.4 Terminating identification restriction (TIR)
+
+No impact on CRT service.
+
+## 11.5 Communication HOLD (HOLD)
+
+No impact on CRT service.
+
+## **11.6 Call Waiting (CW) services**
+
+In case of B having an existing session with C, and A calling B with CRT service, B experiences either the CRT service or the default communication waiting indication according to the operator's policy or subscription options.
+
+## **11.7 Communication diversion (CDIV) services**
+
+### **11.7.1 General**
+
+No impact on CRT service.
+
+If the diverting party has CDIV active, and the calling party has CRT service active, then the CRT service of the calling party shall be applied to the session by the AS-FE providing the CRT service of diverted-to party, except in the case of call forwarding on no reply (CFNR).
+
+If the diverting party has CDIV active, and the calling party has CRT service active, then the CRT of the calling party should be applied to the diverted-to user, if the diverted-to user has subscribed to the CRT service to receive such services.
+
+### **11.7.2 Call forwarding on no reply (CFNR)**
+
+If the diverting party has CFNR active, and the calling party has CRT service active, then the CRT service of the calling party shall be applied to the session by the AS-FE providing CRT service for the calling party until the CFNR timer expires. Upon the CFNR timer expiry, the AS-FE providing the CRT service for the calling party shall deliver the CRT service to the diverted-to party.
+
+## **11.8 Explicit communication transfer (ECT) service**
+
+If the calling party has CRT service active, the AS-FE providing CRT service shall apply the calling party's CRT to the transfer target in the case of blind transfer. The AS-FE providing the CRT service shall not apply the calling party's CRT in the case of consultative transfer while the call is being transferred to the transfer target.
+
+## **11.9 Originating CRT service interacting with terminating CRT service**
+
+If the originating CRT service is triggered and the terminating CRT service is also triggered, and as both services provide early media to the called party, a conflict occurs.
+
+In this case, some priority mechanism is required and the priority mechanism within SIP is for further study.
+
+Another mechanism is to configure the priority between service operators by pre-arrangement. The configuration is set on the service profiles by subscribers or operators. In this case, since the called party is usually the subscriber of the terminating CRT, the terminating CRT has higher priority over the originating CRT.
+
+The signalling flows for priority service between the originating and terminating CRT is presented in clause I.4.
+
+# **12 Security considerations**
+
+The CRT service is required to use appropriate security mechanisms to meet the general security requirements of NGN [ITU-T Y.2701]).
+
+Also, the CRT service provides early/regular media transport and signalling messages, the NGN network infrastructure for the CRT service should ensure the confidentiality and integrity of the signalling flows transported on it.
+
+Therefore, it is recommended to provide the transport and/or network security (respectively, e.g., TLS [b-IETF RFC 2246] and/or IPSec [b-IETF RFC 2401]) and/or the application security (such as
+
+S/MIME [b-IETF RFC 2633]) for signalling messages using SIP between two endpoints, as described in the security considerations of the core SIP specification [IETF RFC 3261], the Early Media and Ringing Tone Generation specification [IETF RFC 3960], and Session Initiation Protocol for Telephones (SIP-T [IETF RFC 3372]).
+
+In the gateway model and the application server model, the transport and network security and/or the application security should be applied.
+
+In the HTTP model, the application-layer security should be applied, because the body of the signalling message (e.g., Alert-info of SIP [IETF RFC 3261]) contains the web URL. Placing the URL in the header field can pose a security risk. If a called party (UE-B) fetches the URLs provided by a malicious caller (UE-A), the called party may be at risk for displaying inappropriate or offensive content, dangerous or illegal content, and so on. Hence, the application security (e.g., S/MIME) should be applied in order to provide the message authentication mechanism.
+
+# Annex A
+
+## Multi-dialog mode
+
+(This annex forms an integral part of this Recommendation)
+
+## A.1 General description
+
+Multi-dialog model establishes both early and regular dialog together during the establishment of the communication. Since it uses a forking mechanism for making both dialogs, they are correlated with the CRT service.
+
+## A.2 Signalling requirements
+
+#### A.2.1 Requirements for the terminating UE
+
+If the terminating UE supports the P-Early-Media header, and wishes to receive early media authorization indications as described in [IETF RFC 5009], upon receiving a REFER request on the early dialog created by the initial INVITE request, whose Refer-to header field has P-Early-Media header parameter with the value of "supported", the terminating UE shall:
+
+- a) Apply normal REFER handling procedures according to [IETF RFC 3515];
+- b) Add a P-Early-Media header field with the value of "supported" in the resulting INVITE request;
+- c) If the user limits the early media type, add a session SDP to the resulting INVITE request, which includes all the media types that the user permits; otherwise, no session SDP is added to the INVITE request.
+
+If the user answers a dialog, the terminating UE may send a CANCEL request to terminate the dialog(s) that result from the REFER request on the early dialog, whose Refer-to header field has P-Early-Media header parameter.
+
+#### A.2.2 Requirements for the AS-FE
+
+If the INVITE request provisional response bearing a 18x code without P-Early-Media header and without "early-session" option tag in the Supported header is received, then the AS-FE shall:
+
+- a) Create a REFER request on the dialog created by the provisional response;
+- b) Create a CRT Session Identifier URI addressed to this AS-FE. The URI shall be created in such a way that a new dialog set-up towards this URI can be easily correlated with the current REFER dialog;
+- c) Set the Refer-to header field of the REFER request to the value of the CRT Session Identifier URI, and add a P-Early-Media header parameter with the value of "supported"; (This will help the CRT AS-FE to terminate the early dialog created by the result INVITE request.)
+- d) Send the REFER request towards the terminating UE.
+
+NOTE 1 – It depends on the operator's policy or user configuration whether the CRT information needs to be provided to all the terminators, or some terminators, or only one terminator, if the INVITE request has been forked.
+
+If a new initial INVITE request is received targeting the CRT Session Identifier URI created earlier, according to [IETF RFC 5009], the AS-FE shall:
+
+- a) Acquire SDP for CRT from MRFC;
+
+NOTE 2 – The SDP for CRT can be acquired by sending an INVITE request without SDP to MRFC.
+
+- b) Create a provisional response bearing a 18x code to the INVITE request;
+
+- c) Add a P-Early-Media header field in the created provisional response, the value of the P-Early-Media header field has one of the following values: "sendonly", or "inactive";
+- d) Add a message body that has session disposition type to the created provisional response, if there is no session SDP in the INVITE request, the body will contain the acquired SDP for CRT; otherwise, based on the acquired SDP for CRT, the body will contain the SDP answer to the SDP offer of the INVITE request;
+- e) Send the created provisional response towards the terminating UE.
+
+If a final answer is received on a dialog, the AS-FE should stop the early media CRT information on the dialog between the terminating UE and a CRT Session Identifier URI, which is correlated to the answering dialog, or, may terminate the correlated dialog by sending a 486 (Busy) response.
+
+# Appendix I
+
+## Signalling flows
+
+(This appendix does not form an integral part of this Recommendation)
+
+The detailed message examples are not shown for simplicity and most of the headers are shown in the first message which includes the significant ones.
+
+### I.1 CRT service using gateway model
+
+Figure I.1 signalling flow shows an IMS-based CRT service provided by the gateway model scenario:
+
+NOTE – This signalling flow shows the case of regular session establishment with re-INVITE.
+
+
+
+```
+sequenceDiagram
+ participant UE-A
+ participant P/S/I-CSC-FE
+ participant CRT AS-FE
+ participant MRC/P-FE
+ participant Terminating Net. UE-B
+
+ Note right of Terminating Net. UE-B: CRT play
+ Note right of Terminating Net. UE-B: Answer
+
+ UE-A->>P/S/I-CSC-FE: S1:INVITE(offer A)
+ P/S/I-CSC-FE->>CRT AS-FE: S2:INVITE(offer A)
+ CRT AS-FE->>Terminating Net. UE-B: S3:INVITE(offer A)
+ Terminating Net. UE-B-->>CRT AS-FE: S4:183(ans B)
+ CRT AS-FE-->>P/S/I-CSC-FE: S5:183(ans B)
+ P/S/I-CSC-FE-->>UE-A: S6:183(ans B)
+ UE-A->>P/S/I-CSC-FE: S7:PRACK
+ P/S/I-CSC-FE->>CRT AS-FE: S8:PRACK
+ CRT AS-FE->>Terminating Net. UE-B: S9:PRACK
+ Terminating Net. UE-B-->>CRT AS-FE: S10:200OK(PRACK)
+ CRT AS-FE-->>P/S/I-CSC-FE: S11:200OK(PRACK)
+ P/S/I-CSC-FE-->>UE-A: S12:200OK(PRACK)
+ CRT AS-FE->>MRC/P-FE: Connection & Acquire CRT SDP
+ P/S/I-CSC-FE->>CRT AS-FE: S15:UPDATE(sdp MRP)
+ CRT AS-FE->>Terminating Net. UE-B: S16:UPDATE(sdp MRP)
+ Terminating Net. UE-B-->>CRT AS-FE: S17:200OK(SDP B)
+ CRT AS-FE-->>P/S/I-CSC-FE: S18:200OK(SDP B)
+ CRT AS-FE->>MRC/P-FE: Media Control
+ MRC/P-FE->>Terminating Net. UE-B: Play CRT with RTP
+ Note right of Terminating Net. UE-B: CRT play
+ Note right of Terminating Net. UE-B: Answer
+ Terminating Net. UE-B-->>CRT AS-FE: S22:200OK
+ CRT AS-FE-->>P/S/I-CSC-FE: S23:200OK
+ CRT AS-FE->>MRC/P-FE: Disconnection
+ P/S/I-CSC-FE-->>UE-A: S26:200OK
+ UE-A->>P/S/I-CSC-FE: S27:ACK
+ P/S/I-CSC-FE->>CRT AS-FE: S28:ACK
+ CRT AS-FE->>Terminating Net. UE-B: S29:ACK
+ Note right of CRT AS-FE: Re-Invite transaction
+ Note right of CRT AS-FE: A-B with RTP
+ CRT AS-FE->>UE-A:
+ Note right of UE-A:
+ Note right of P/S/I-CSC-FE:
+ Note right of CRT AS-FE:
+ Note right of MRC/P-FE:
+ Note right of Terminating Net. UE-B:
+```
+
+Sequence diagram showing signalling flows for CRT service using gateway model. Lifelines: UE-A, P/S/I-CSC-FE, CRT AS-FE, MRC/P-FE, Terminating Net. UE-B. The sequence includes INVITE, 183, PRACK, 200OK, UPDATE, Media Control, Play CRT with RTP, Disconnection, and ACK messages.
+
+Figure I.1 – Signalling flows for CRT service using gateway model
+
+The procedures of SIP signalling are as follows:
+
+#### **S1 INVITE (UE-A to AS-FE)**
+
+The INVITE request is sent from the UE-A to S-CSC-FE of the originating side. The S-CSC-FE evaluates the initial filter criteria. (The initial filter criteria identifies that the requested URI is subscribed to the CRT service.) If that matches, the S-CSC-FE will send the request toward the indicated CRT AS-FE. At this time, the contact value includes the UE-A's SIP URI that contains the IP address.
+
+```
+INVITE tel:+1-222-333-4444 SIP/2.0
+Route: ,
+From: ;tag=171828
+To:
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+P-Preferred-Identity: ,
+Privacy: none
+Contact:
+Supported: timer, early-session
+Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, MESSAGE, INFO, REFER, NOTIFY, SUBSCRIBE
+Accept: application/sdp
+Session-Expires: 3600;refresher=uac
+Content-Type: application/sdp
+...
+```
+
+#### **S2-S3 INVITE (AS-FE to UE-B)**
+
+INVITE is sent toward the UE-B through network elements. The contact value includes the AS-FE's SIP URI.
+
+```
+INVITE sip:192.100.200.52:5080 SIP/2.0
+From: ;tag=asfe171828
+To:
+Call-ID : asfed03a0sasfe0234123
+CSeq: 101 INVITE
+Supported : 100rel
+Contact:
+Content-Type: application/sdp
+...
+```
+
+#### **S4-S6 183 (UE-B to AS-FE)**
+
+If 100rel option tag is presented in the 183 message with require/RSeq header SDP, it is sent toward the AS-FE through network elements. The Contact value includes the UE-B's SIP URI.
+
+```
+SIP/2.0 183 Session Progress
+From: ;tag=asfe171828
+To: ;tag=22222122
+Call-ID : asfed03a0sasfe0234123
+Require: 100rel
+RSeq: 113
+Cseq: 101 INVITE
+Contact:
+Content-Type: application/sdp
+...
+```
+
+#### **S7 PRACK (UE-A to AS-FE)**
+
+UE-A is requested to send a PRACK request back, in order to acknowledge the provisional 183 (Session in Progress) response.
+
+```
+PRACK sip:192.100.100.100:5070 SIP/2.0
+From: ;tag=171828
+To: ;tag=asfe22222122
+Call-ID : ueacb03a0suea00234123
+RAck: 113 101 INVITE
+Cseq: 102 PRACK
+Content-Type: application/sdp
+...
+```
+
+#### **S8-S9 PRACK (AS-FE to UE-B)**
+
+PRACK is sent toward the UE-B through network elements.
+
+```
+PRACK sip:192.100.100.100:5070 SIP/2.0
+From: ;tag=asfe171828
+To: ;tag=22222122
+Call-ID : asfed03a0sasfe0234123
+RAck: 113 101 INVITE
+Cseq: 102 PRACK
+Content-Type: application/sdp
+...
+```
+
+#### **S10-S12 200 OK (UE-B to UE-A)**
+
+The UE-B responds to the PRACK (S11) with a 200 OK. Then 200 OK is sent toward the UE-A through network elements.
+
+```
+SIP/2.0 200 OK
+From: ;tag=asfe171828
+To: ;tag=22222122
+Call-ID : asfed03a0sasfe0234123
+Cseq: 102 PRACK
+...
+```
+
+#### **S15-S16 UPDATE (AS-FE to UE-B)**
+
+AS-FE generates an UPDATE message with the SDP of the MRC-FE. UPDATE is sent toward the UE-B through network elements. The contact value includes the AS-FE's SIP URI.
+
+```
+UPDATE sip:192.100.200.51:5080 SIP/2.0
+From: ;tag= asfe171828
+To: ;tag= 22222122
+Call-ID : asfed03a0sasfe0234123
+CSeq: 222 UPDATE
+Contact:
+Content-Type: application/SDP
+...
+```
+
+#### **S17-S18 200 OK (UE-B to S-CSC-FE)**
+
+The UE-B responds to the UPDATE (S15) with a 200 OK including the SDP of the UE-A. Then 200 OK is sent toward the AS-FE through network elements. The contact value includes the UE-A's SIP URI.
+
+```
+SIP/2.0 200 OK
+From: ;tag= asfe171828
+To: ;tag= 22222122
+Call-ID : asfed03a0sasfe0234123
+CSeq: 222 UPDATE
+Contact:
+Content-Type: application/SDP
+```
+
+#### **S22-S23 200 OK (UE-B to AS-FE)**
+
+When the called party answers, the UE-B sends a 200 OK final response to the INVITE request (S3). The S-CSC-FE forwards the 200 OK response to the AS-FE. The contact value includes the UE-B's SIP URI.
+
+```
+SIP/2.0 200 OK
+From: ;tag=asfe171828
+To: ;tag=22222122
+Call-ID : asfed03a0sasfe0234123
+CSeq: 101 INVITE
+Contact:
+Content-Type: application/sdp
+```
+
+#### **S25-26 200 OK (AS-FE to UE-A)**
+
+The S-CSC-FE forwards the 200 OK response to the UE-A. The contact value includes the AS-FE's SIP URI.
+
+```
+SIP/2.0 200 OK
+From: ;tag=171828
+To: ;tag= asfe22222122
+Call-ID : ueacb03a0suea00234123
+Contact:
+CSeq: 101 INVITE
+...
+```
+
+#### **S27-29 ACK (UE-A to UE-B)**
+
+The UE-A responds to the 200 OK with an ACK request to the UE-B. The UE-A and the UE-B should change the RTP session after re-INVITE transaction.
+
+```
+ACK sip:192.100.100.100:5070 SIP/2.0
+From: ;tag=171828
+To: ;tag= asfe22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 101 INVITE
+```
+
+### I.2 CRT service using application server model
+
+Figure I.2 signalling flow shows a CRT service provided by the application server model scenario:
+
+
+
+```
+
+sequenceDiagram
+ participant UE-A as UE-A/P/S/I-CSC-FE
+ participant CRT AS-FE as CRT AS-FE
+ participant MRC-P-FE as MRC/P-FE
+ participant P-CSC-FE as P-CSC-FE
+ participant UE-B as Terminating Net. UE-B
+
+ Note right of UE-B: CRT play
+ Note right of UE-B: Answer
+ Note right of UE-B: CRT stop
+
+ UE-A->>CRT AS-FE: S1:INVITE(offer A)
+ CRT AS-FE->>MRC-P-FE: S2:INVITE(offer A)
+ MRC-P-FE->>P-CSC-FE: S2:INVITE(offer A)
+ P-CSC-FE->>UE-B: S3:183 (answerA')
+ P-CSC-FE->>MRC-P-FE: S3:183 (answerA')
+ MRC-P-FE->>CRT AS-FE: S4:183 (answerA')
+ CRT AS-FE->>UE-A: S4:183 (answerA')
+ UE-A->>CRT AS-FE: S5:PRACK
+ CRT AS-FE->>MRC-P-FE: Connect and acquire CRT sdp
+ MRC-P-FE->>P-CSC-FE: S8:PRACK(offer CRT)
+ P-CSC-FE->>UE-B: S8:PRACK(offer CRT)
+ P-CSC-FE->>MRC-P-FE: S9:200 (answer CRT')
+ MRC-P-FE->>CRT AS-FE: S9:200 (answer CRT')
+ CRT AS-FE->>UE-A: S10:200OK
+ CRT AS-FE->>MRC-P-FE: Media control
+ MRC-P-FE->>UE-B: Play CRT
+ UE-B->>MRC-P-FE: CRT play
+ MRC-P-FE->>CRT AS-FE: S13:180 ring
+ CRT AS-FE->>UE-A: S13:180 ring
+ UE-B->>MRC-P-FE: Answer
+ MRC-P-FE->>P-CSC-FE: S14:200OK
+ P-CSC-FE->>MRC-P-FE: S14:200OK
+ MRC-P-FE->>CRT AS-FE: S15:200OK
+ CRT AS-FE->>UE-A: S15:200OK
+ CRT AS-FE->>MRC-P-FE: Disconnection
+ MRC-P-FE->>CRT AS-FE: S16:ACK
+ CRT AS-FE->>P-CSC-FE: S17:ACK
+ P-CSC-FE->>UE-B: S17:ACK
+ UE-A->>UE-B: A-B with RTP
+
+```
+
+Q.3611(09)\_FI.2
+
+Sequence diagram showing the signalling flow for CRT service using application server model. The diagram involves five main entities: UE-A/P/S/I-CSC-FE, CRT AS-FE, MRC/P-FE, P-CSC-FE, and Terminating Net. UE-B. The sequence starts with S1:INVITE(offer A) from UE-A to CRT AS-FE. CRT AS-FE sends S2:INVITE(offer A) to MRC/P-FE. MRC/P-FE sends S2:INVITE(offer A) to P-CSC-FE. P-CSC-FE sends S3:183 (answerA') to Terminating Net. UE-B. P-CSC-FE sends S3:183 (answerA') to MRC/P-FE. MRC/P-FE sends S4:183 (answerA') to CRT AS-FE. CRT AS-FE sends S4:183 (answerA') to UE-A. UE-A sends S5:PRACK to CRT AS-FE. CRT AS-FE sends 'Connect and acquire CRT sdp' to MRC/P-FE. MRC/P-FE sends S8:PRACK(offer CRT) to P-CSC-FE. P-CSC-FE sends S8:PRACK(offer CRT) to Terminating Net. UE-B. P-CSC-FE sends S9:200 (answer CRT') to MRC/P-FE. MRC/P-FE sends S9:200 (answer CRT') to CRT AS-FE. CRT AS-FE sends S10:200OK to UE-A. CRT AS-FE sends 'Media control' to MRC/P-FE. MRC/P-FE sends 'Play CRT' to Terminating Net. UE-B. UE-B sends 'CRT play' to MRC/P-FE. MRC/P-FE sends S13:180 ring to CRT AS-FE. CRT AS-FE sends S13:180 ring to UE-A. UE-B sends 'Answer' to MRC/P-FE. MRC/P-FE sends S14:200OK to P-CSC-FE. P-CSC-FE sends S14:200OK to MRC/P-FE. MRC/P-FE sends S15:200OK to CRT AS-FE. CRT AS-FE sends S15:200OK to UE-A. CRT AS-FE sends 'Disconnection' to MRC/P-FE. MRC/P-FE sends S16:ACK to CRT AS-FE. CRT AS-FE sends S17:ACK to P-CSC-FE. P-CSC-FE sends S17:ACK to Terminating Net. UE-B. Finally, a thick line labeled 'A-B with RTP' connects UE-A and UE-B.
+
+**Figure I.2 – Signalling flows for CRT service using application server model**
+
+The procedures of SIP signalling are as follows:
+
+#### S1 INVITE (originating side to S-CSC-FE)
+
+The INVITE request is sent from the UE-A to the S-CSC-FE of the terminating side. The S-CSC-FE evaluates the initial filter criteria. (The initial filter criteria identifies that the requested URI is subscribed to the CRT service.) Therefore, the S-CSC-FE forwards the INVITE to the CRT AS-FE. The contact value includes the UE-A's SIP URI that contains the IP address.
+
+```
+
+INVITE sip:ue-b@term_ngn.net SIP/2.0
+Route: ,
+From: ;tag=171828
+To:
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+P-Preferred-Identity: ,
+Privacy: none
+Contact:
+Supported: timer
+Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, MESSAGE, INFO, REFER, NOTIFY, SUBSCRIBE
+Accept: application/sdp
+Session-Expires: 3600;refresher=uac
+Content-Type: application/sdp
+...
+
+```
+
+#### S2 INVITE (AS-FE to UE-B)
+
+INVITE is sent toward the UE-B through network elements (AS-FE may be the Proxy server). The contact value includes the UE-A's SIP URI.
+
+```
+
+INVITE sip:192.100.200.52:5080 SIP/2.0
+From: ;tag=171828
+To:
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Supported: timer, early-session
+Require:100rel, early-session
+Contact:
+Content-Type: application/sdp
+...
+
+```
+
+#### S3-S4 183 (UE-B to UE-A)
+
+183 (Session Progress) is sent toward the AS-FE through network elements. The contact value includes the UE-B's SIP URI.
+
+```
+
+SIP/2.0 183 Session Progress
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Contact:
+Content-Type: application/sdp
+...
+
+```
+
+#### S5 PRACK (UE-A to AS-FE)
+
+PRACK is sent toward the AS-FE through network elements.
+
+```
+PRACK sip:ue-b@term_ngn.net SIP/2.0
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 PRACK
+Contact:
+Content-Length: 0
+```
+
+#### S8 PRACK (AS-FE to UE-B)
+
+The AS-FE inserts an early-session SDP within PRACK request. PRACK is sent toward the UE-B through network elements.
+
+```
+PRACK sip:ue-b@term_ngn.net SIP/2.0
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 PRACK
+Require: early-session
+Contact:
+Content-Type: application/sdp
+Content-Disposition: early-session
+...
+```
+
+#### S9 200 (UE-B to AS-FE)
+
+200 (OK) is sent toward the AS-FE through network elements.
+
+```
+SIP/2.0 200 OK
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 PRACK
+Contact:
+Content-Type: application/sdp
+Content-Disposition: early-session
+...
+```
+
+#### **S10 200 OK (AS-FE to UE-A)**
+
+200 (OK) is sent toward the UE-A through network elements.
+
+```
+SIP/2.0 200 OK
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 PRACK
+Contact:
+Content-Length: 0
+```
+
+#### **S13 180 (AS-FE to UE-A)**
+
+180 (ringing) is sent toward the UE-A through network elements. The contact value includes the UE-B's SIP URI.
+
+```
+SIP/2.0 180 Ringing
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Contact:
+...
+```
+
+#### **S14-S15 200 (UE-B to UE-A)**
+
+200 (OK) is sent toward the UE-A through network elements. The contact value includes the UE-B's SIP URI.
+
+```
+SIP/2.0 200 OK
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Contact:
+Content-Type: application/sdp
+Content-Disposition: session
+...
+```
+
+#### **S16-S17 ACK (UE-A to UE-B)**
+
+The UE-A responds to the 200 OK with an ACK request to the UE-B.
+
+```
+ACK sip:192.100.200.52:5080 SIP/2.0
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Content-Length: 0
+```
+
+### I.3 CRT service using HTTP model
+
+Figure I.3 signalling flow shows a CRT service provided by the HTTP model scenario:
+
+
+
+```
+
+sequenceDiagram
+ participant UE-A
+ participant P/S/I-CSC-FE
+ participant CRT AS-FE
+ participant IconRingTone server
+ participant Terminating Net. UE-B
+
+ Note right of Terminating Net. UE-B: CRT play
+ Note right of Terminating Net. UE-B: Answer
+ Note right of Terminating Net. UE-B: CRT stop
+
+ UE-A->>P/S/I-CSC-FE: S1:INVITE(offer A)
+ P/S/I-CSC-FE->>CRT AS-FE: S4:INVITE(offer A)
+ CRT AS-FE->>IconRingTone server: H2:GET(with URI)
+ IconRingTone server-->>CRT AS-FE: H3:200OK(URL)
+ CRT AS-FE->>P/S/I-CSC-FE: S5:INVITE(offer A)
+ P/S/I-CSC-FE->>Terminating Net. UE-B: S6:180
+ Terminating Net. UE-B-->>P/S/I-CSC-FE: S7:180
+ P/S/I-CSC-FE->>CRT AS-FE: S8:180
+ CRT AS-FE->>IconRingTone server: H9:GET(File URL)
+ IconRingTone server-->>CRT AS-FE: H10:200OK(with file)
+ Note right of IconRingTone server: File download with TCP
+ IconRingTone server->>Terminating Net. UE-B: File download with TCP
+ Terminating Net. UE-B->>CRT AS-FE: S11:200OK(ans B)
+ CRT AS-FE->>P/S/I-CSC-FE: S12:200OK(ans B)
+ P/S/I-CSC-FE->>UE-A: S13:200OK(ans B)
+ UE-A->>P/S/I-CSC-FE: S14:ACK
+ P/S/I-CSC-FE->>CRT AS-FE: S15:ACK
+ CRT AS-FE->>Terminating Net. UE-B: S16:ACK
+ Note right of P/S/I-CSC-FE: A-B with RTP
+ P/S/I-CSC-FE->>Terminating Net. UE-B: A-B with RTP
+
+```
+
+Sequence diagram showing signalling flows for CRT service using HTTP model. Lifelines: UE-A, P/S/I-CSC-FE, CRT AS-FE, IconRingTone server, Terminating Net. UE-B. The sequence involves INVITE, GET, 200OK, and ACK messages between these components, leading to a file download and RTP stream.
+
+Figure I.3 – Signalling flows for CRT service using HTTP model
+
+The procedures of SIP signalling are as follows:
+
+#### S1 INVITE (UE-A to AS-FE)
+
+The INVITE request is sent from the UE-A to the S-CSC-FE of the originating side. The S-CSC-FE evaluates the initial filter criteria (The initial filter criteria identifies that the requested URI is subscribed to the CRT service.). If that matches, the S-CSC-FE will send the request toward the indicated CRT AS-FE. At this time, the contact value includes the UE-A's SIP URI that contains the IP address.
+
+```
+
+INVITE tel:+1-222-333-4444 SIP/2.0
+Route: ,
+From: ;tag=171828
+To:
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+P-Preferred-Identity: ,
+Privacy: none
+Contact:
+
+```
+
+```
+Supported: timer, early-session
+Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, MESSAGE, INFO, REFER, NOTIFY, SUBSCRIBE
+Accept: application/sdp
+Session-Expires: 3600;refresher=uac
+Content-Type: application/sdp
+...
+```
+
+#### **H2-H3 HTTP or SOAP (between AS-FE and CRT HTTP server)**
+
+The AS-FE gets CRT URL from the HTTP server using TCP-based protocol.
+
+#### **S4-S5 INVITE (AS-FE to UE-B)**
+
+The AS-FE inserts the Call-Info header or Alert-Info header within the INVITE request. The contact value includes the UE-A's SIP URI.
+
+```
+INVITE sip:192.100.200.52:5080 SIP/2.0
+From: ;tag=171828
+To:
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Contact:
+Content-Type: application/SDP
+Call-Info : ; purpose=icon,
+ ; purpose=info
+Alert-Info : http://crt_as.ngn.com/mmcid/bimg20001000000001731.wav
+...
+```
+
+#### **S6-S7 180 (UE-B to AS-FE)**
+
+180 (ringing) is sent toward the UE-A through the network elements. The contact value includes the UE-B's SIP URI.
+
+```
+SIP/2.0 180 Ringing
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Contact:
+...
+```
+
+#### **H9-H10 HTTP GET and File downloading (between AS-FE and CRT HTTP server)**
+
+The UE-B requests HTTP GET Message with URL. Then, the UE-B downloads and plays the CRT media file.
+
+#### **S11-S13 200 OK (UE-B to UE-A)**
+
+When the called party answers, the UE-B sends a 200 OK (with SDP B) response to the INVITE request. Then, the UE-B stops the CRT media play. The contact value includes the UE-B's SIP URI.
+
+```
+SIP/2.0 200 OK
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Contact:
+Content-Type: application/sdp
+...
+```
+
+#### **S14-S16 ACK (UE-A to UE-B)**
+
+The UE-A responds to the 200 OK with ACK request to the UE-B.
+
+```
+ACK sip:192.100.200.52:5080 SIP/2.0
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+...
+```
+
+### **I.4 CRT service priority using application server model**
+
+Figure I.4 signalling flow shows an IMS-based CRT service priority provided by the application server model where the terminating side has higher priority.
+
+
+
+```
+
+sequenceDiagram
+ participant UEA as Originating Net. UE-A
+ participant PSCFEO as Originating P/S/I-CSC-FE
+ participant CRTASFEO as Originating CRT AS-FE
+ participant MRCFEO as Originating MRC/P-FE
+ participant PSCFET as Terminating P/S-CSC-FE
+ participant CRTASFET as Terminating CRT AS-FE
+ participant MRCFET as Terminating MRC/P-FE
+ participant UEB as Terminating Net. UE-B
+
+ UEA->>PSCFEO: S1: INVITE(offer A)
+ PSCFEO->>CRTASFEO: S2: INVITE(offer A)
+ CRTASFEO->>PSCFET: S2: INVITE(offer A)
+ PSCFET->>CRTASFET: S2: INVITE(offer A)
+ CRTASFET->>PSCFET: S3: INVITE(offer A)
+ PSCFET->>UEB: S3: INVITE(offer A)
+ UEB->>PSCFET: S4: 183(answer B)
+ PSCFET->>CRTASFET: S4: 183(answer B)
+ CRTASFET->>PSCFET: S4: 183(answer B)
+ PSCFET->>CRTASFEO: S4: 183(answer B)
+ CRTASFEO->>PSCFEO: S4: 183(answer B)
+ PSCFEO->>UEA: S4: 183(answer B)
+ UEA->>PSCFEO: S5: PRACK
+ PSCFEO->>CRTASFEO: S5: PRACK
+ CRTASFEO->>MRCFEO: Connect and acquire CRT-O sdp
+ MRCFEO->>CRTASFEO: S6: PRACK(CRT-O offer)
+ CRTASFEO->>PSCFET: S6: PRACK(CRT-O offer)
+ PSCFET->>CRTASFET: S6: PRACK(CRT-O offer)
+ CRTASFET->>MRCFET: Connexion and acquire CRT-T sdp
+ MRCFET->>CRTASFET: S7: PRACK(CRT-T offer)
+ CRTASFET->>PSCFET: S7: PRACK(CRT-T offer)
+ PSCFET->>UEB: S8: 200 OK(PRACK)(CRT-T answer)
+ UEB->>PSCFET: S8: 200 OK(PRACK)(CRT-T answer)
+ PSCFET->>CRTASFET: S8: 200 OK(PRACK)(CRT-T answer)
+ CRTASFET->>PSCFET: S9: 200 OK(PRACK)(CRT-O answerport=0)
+ PSCFET->>CRTASFEO: S9: 200 OK(PRACK)(CRT-O answerport=0)
+ CRTASFEO->>PSCFEO: S9: 200 OK(PRACK)(CRT-O answerport=0)
+ PSCFEO->>CRTASFEO: Disconnection
+ CRTASFEO->>PSCFEO: S10: 200OK(PRACK)
+ PSCFEO->>UEA: S10: 200OK(PRACK)
+ UEB->>PSCFET: S11: 180
+ PSCFET->>CRTASFET: S11: 180
+ CRTASFET->>MRCFET: Media Control
+ MRCFET->>UEB: Play CRT
+ UEB->>CRTASFET: Answer
+ CRTASFET->>PSCFET: S11: 180
+ PSCFET->>CRTASFEO: S11: 180
+ CRTASFEO->>PSCFEO: S11: 180
+ PSCFEO->>UEA: S11: 180
+ UEB->>PSCFET: S12: 200OK(answer B)
+ PSCFET->>CRTASFET: S12: 200OK(answer B)
+ CRTASFET->>MRCFET: Disconnection
+ MRCFET->>CRTASFET: S13: 200OK(answer B)
+ CRTASFET->>PSCFET: S13: 200OK(answer B)
+ PSCFET->>CRTASFEO: S13: 200OK(answer B)
+ CRTASFEO->>PSCFEO: S14: 200OK(answer B)
+ PSCFEO->>UEA: S14: 200OK(answer B)
+ UEA->>PSCFEO: S15: ACK
+ PSCFEO->>CRTASFEO: S16: ACK
+ CRTASFEO->>PSCFET: S16: ACK
+ PSCFET->>CRTASFET: S16: ACK
+ CRTASFET->>MRCFET: S17: ACK
+ MRCFET->>UEB: S17: ACK
+ Note over UEA, UEB: A-B with RTP
+
+```
+
+Sequence diagram showing signalling flows for CRT service with priority using application server model. Lifelines: Originating Net. UE-A, Originating P/S/I-CSC-FE, Originating CRT AS-FE, Originating MRC/P-FE, Terminating P/S-CSC-FE, Terminating CRT AS-FE, Terminating MRC/P-FE, Terminating Net. UE-B. The diagram shows the exchange of INVITE, PRACK, 200 OK, 180, and ACK messages between these entities, with internal actions like 'Connect and acquire CRT-O sdp' and 'Play CRT'.
+
+**Figure I.4 – Signalling flows for CRT service with priority using application server model**
+
+The procedures of SIP signalling are as follows:
+
+#### **S1-S3 INVITE (UE-A toward UE B)**
+
+The INVITE request is sent from the UE-A to the S-CSC-FE of the originating side. The originating S-CSC-FE evaluates the initial filter criteria and forwards the INVITE to the originating CRT AS-FE. AS-FE forwards the INVITE to the terminating S-CSC-FE, and the terminating S-CSC-FE evaluates the initial filter criteria and forwards the INVITE to the terminating CRT AS-FE, the terminating CRT AS-FE checks the CRT priority setting, then the terminating CRT finally forwards the INVITE to the UE-B. The contact value includes the UE-A's SIP URI that contains the IP address. The "early-session" and "100rel" option-tag is added by the CRT AS-FE into the Require header of the INVITE request.
+
+```
+INVITE sip:ue-b@term_ngn.net SIP/2.0
+From: ;tag=171828
+To:
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+P-Preferred-Identity: ,
+Privacy: none
+Contact:
+Supported: timer, early-session, 100rel
+Require:100rel,early-session
+Accept: application/sdp
+Session-Expires: 3600;refresher=uac
+Content-Type: application/sdp
+...
+```
+
+#### **S4 183 (UE-B toward UE-A)**
+
+The UE B responds with "183 Session Progress" towards the terminating CRT AS-FE which indicates the UE-B supporting the early session.
+
+```
+SIP/2.0 183 Session Progress
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Contact:
+Content-Type: application/sdp
+...
+```
+
+#### **S5 PRACK (UE-A toward originating CRT AS-FE)**
+
+The UE-A sends PRACK of the 183 response to the originating CRT AS-FE.
+
+```
+PRACK sip:ue-b@term_ngn.net SIP/2.0
+From: ;tag=171828
+To: ;tag=2222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 PRACK
+Contact:
+```
+
+#### S6 PRACK (originating CRT AS-FE toward terminating CRT AS-FE)
+
+The originating CRT AS-FE adds the CRT-O offer SDP in the PRACK message and forwards the PRACK message to the terminating CRT AS-FE.
+
+```
+PRACK sip:ue-b@term_ngn.net SIP/2.0
+From: ;tag=171828
+To: ;tag=2222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 PRACK
+Contact:
+Content-Type: application/sdp
+Content-Disposition: early-session
+Content-Length: (...)
+
+v=0
+o= 2987933616 2987933616 IN IP4 aaa:bbb:eee:fff
+s=-
+c=IN IP4 ccc:aaa:bbb:acc
+t=0 0
+m=audio 3456 RTP/AVP 97
+b=AS:25.4
+a=curr:qos local sendrecv
+a=curr:qos remote none
+a=des:qos mandatory local sendrecv
+a=des:qos mandatory remote sendrecv
+a=rtpmap:97 AMR
+a=fmtp:97 mode-set=0,2,5,7; maxframes
+m=video 3400 RTP/AVP 98
+b=AS:75
+a=curr:qos local none
+a=curr:qos remote none
+a=des:qos mandatory local sendrecv
+a=des:qos none remote sendrecv
+a=rtpmap:98 H263
+```
+
+#### S7 PRACK (terminating CRT AS-FE toward UE-B)
+
+Due to the fact that the terminating CRT has priority according to the priority setting, the terminating CRT AS-FE adds CRT-T offer SDP, instead of CRT-O offer, in a PRACK request and forwards the PRACK to the UE-B.
+
+```
+PRACK sip:ue-b@term_ngn.net SIP/2.0
+From: ;tag=171828
+To: ; tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 PRACK
+Contact:
+Content-Type: application/sdp
+Content-Disposition: early-session
+Content-Length: (...)
+
+v=0
+o=- 2987933616 2987933616 IN IP4 eee:fff:aaa:bbb
+s=
+c=IN IP4 ccc:aaa:bbb:acc
+t=0 0
+m=audio 3456 RTP/AVP 97
+b=AS:25.4
+a=curr:qos local sendrecv
+a=curr:qos remote none
+a=des:qos mandatory local sendrecv
+a=des:qos mandatory remote sendrecv
+a=rtpmap:97 AMR
+a=fmtp:97 mode-set=0,2,5,7; maxframes
+m=video 3400 RTP/AVP 98
+b=AS:75
+a=curr:qos local none
+a=curr:qos remote none
+a=des:qos mandatory local sendrecv
+a=des:qos none remote sendrecv
+a=rtpmap:98 H263
+```
+
+#### S8 200 OK (UE-B toward terminating CRT AS-FE)
+
+The UE-B completes the terminating CRT media negotiation and sends 200 OK of PRACK with a CRT-T answer SDP to the terminating CRT AS-FE. The contact value includes the UE-B's SIP URI.
+
+```
+SIP/2.0 200 OK
+From: ;tag=171828
+To: ; tag=22222122
+Call-ID : ueacb03a0suea00234123
+```
+
+```
+
+CSeq: 1 PRACK
+Contact:
+Content-Type: application/sdp
+Content-Disposition: early-session
+Content-Length: (...)
+
+v=0
+o=- 2987933616 2987933616 IN IP4 aaa:bbb:ccc:ddd
+s=-
+c=IN IP4 aaa:bbb:ccc:ddd
+t=0 0
+m=audio 3466 RTP/AVP 97
+b=AS:25.4
+a=curr:qos local sendrecv
+a=curr:qos remote sendrecv
+a=des:qos mandatory local sendrecv
+a=des:qos none remote sendrecv
+a=rtpmap:97 AMR
+a=fmtp:97 mode-set=0,2,5,7; maxframes...
+m=video 3400 RTP/AVP 98
+b=AS:75
+a=curr:qos local none
+a=curr:qos remote none
+a=des:qos mandatory local sendrecv
+a=des:qos none remote sendrecv
+a=rtpmap:98 H263
+
+```
+
+#### **S9 200 OK (terminating CRT AS-FE toward originating CRT AS-FE)**
+
+The terminating CRT AS-FE adds the CRT-O answer SDP setting port to refuse the originating CRT media negotiation in the 200 OK response, instead of the previous CRT-T answer SDP, and forwards the 200 OK to the originating CRT AS-FE.
+
+```
+
+SIP/2.0 200 OK
+From: ;tag=171828
+To: ; tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 PRACK
+Contact:
+Content-Type: application/sdp
+Content-Disposition: early-session
+Content-Length: (...)
+
+v=0
+o=- 2987933616 2987933616 IN IP4 aaa:bbb:ccc:ddd
+
+```
+
+```
+
+s=-
+c=IN IP4 aaa:bbb:ccc:ddd
+t=0 0
+m=audio 0 RTP/AVP 97
+b=AS:25.4
+a=curr:qos local sendrecv
+a=curr:qos remote sendrecv
+a=des:qos mandatory local sendrecv
+a=des:qos none remote sendrecv
+a=rtpmap:97 AMR
+a=fmtp:97 mode-set=0,2,5,7; maxframes...
+m=video 0 RTP/AVP 98
+b=AS:75
+a=curr:qos local none
+a=curr:qos remote none
+a=des:qos mandatory local sendrecv
+a=des:qos none remote sendrecv
+a=rtpmap:98 H263
+
+```
+
+#### S10 200 OK (originating CRT AS-FE toward UE-A)
+
+The originating CRT AS-FE removes the CRT-O answer SDP and forwards the 200 OK to the UE-A.
+
+```
+
+SIP/2.0 200 OK
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 PRACK
+Contact:
+
+```
+
+#### S11 180 (UE-B toward UE-A)
+
+The UE-B sends a 180 Ring response to the UE-A through network elements. When the terminating CRT AS-FE receives the response, the terminating CRT AS-FE plays the terminating CRT to the UE-B.
+
+```
+
+SIP/2.0 180 Ringing
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Require :100rel
+Contact:
+
+```
+
+#### **S12-14 200 (UE-B toward UE-A)**
+
+200 (OK) is sent toward the UE-A through network elements. The contact value includes the UE-B's SIP URI.
+
+```
+SIP/2.0 200 OK
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Contact:
+Content-Type: application/sdp
+Content-Disposition: session
+...
+```
+
+#### **S15-17 ACK (UE-A toward UE-B)**
+
+The UE-A responds to the 200 OK with an ACK request to the UE-B.
+
+```
+ACK sip:192.100.200.52:5080 SIP/2.0
+From: ;tag=171828
+To: ;tag=22222122
+Call-ID : ueacb03a0suea00234123
+CSeq: 1 INVITE
+Content-Length: 0
+```
+
+# Bibliography
+
+- [b-ITU-T Q.1912.5] Recommendation ITU-T Q.1912.5 (2004), *Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part*.
+- [b-ITU-T Q.3030] Recommendation ITU-T Q.3030 (2008), *Signalling architecture for the NGN service control plane*.
+- [b-ITU-T Q-Sup.55] ITU-T Q-series Recommendations – Supplement 55 (2007), *Signalling requirements at the interface between AS-FE and S-CSC-FE*.
+- [b-ITU-T Y.2021] Recommendation ITU-T Y.2021 (2006), *IMS for Next Generation Networks*.
+- [b-ITU-T Y.2031] Recommendation ITU-T Y.2031 (2006), *PSTN/ISDN emulation architecture*.
+- [b-ITU-T Y.2211] Recommendation ITU-T Y.2211 (2007), *IMS-based real-time conversational multimedia services over NGN*.
+- [b-ITU-T Y.2214] Recommendation ITU-T Y.2214 (2009), *Service requirements and functional models for customized multimedia ring services*.
+- [b-IETF RFC 2083] IETF RFC 2083 (1997), *PNG (Portable Network Graphics) Specification Version 1.0*.
+- [b-IETF RFC 2246] IETF RFC 2246 (1999), *The TLS Protocol Version 1.0*.
+- [b-IETF RFC 2401] IETF RFC 2401 (1998), *Security Architecture for the Internet Protocol*.
+- [b-IETF RFC 2633] IETF RFC 2633 (1999), *S/MIME Version 3 Message Specification*.
+- [b-IETF RFC 3264] IETF RFC 3264 (2002), *An Offer/Answer Model with the Session Description Protocol (SDP)*.
+- [b-IETF RFC 4566] IETF RFC 4566 (2006), *SDP: Session Description Protocol*.
+- [b-Unicode] The Unicode Consortium (1996), *The Unicode Standard, Version 2.0*, Addison-Wesley Developers Press, ISBN 0-201-48345-9.
+- [b-GIF87a] CompuServe Incorporated (1987), *GIF Graphics Interchange Format: A Standard defining a mechanism for the storage and transmission of raster-based graphics information*.
+- [b-GIF89a] CompuServe Incorporated, Columbus, Ohio (1990), *Graphics Interchange Format (Version 89a)*.
+- [b-JFIF] *JPEG File Interchange Format, Version 1.02*, September 1, 1992.
+
+
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3619-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3619-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..90f23c5ef36a0e3c145a6b88653546fa92ad2a97
--- /dev/null
+++ b/marked/Q/T-REC-Q.3619-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:609b79b1efd94f0ee710d499d6659605494b7dc4207d9696660c0baebb206830
+size 3849
diff --git a/marked/Q/T-REC-Q.3619-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3619-201602-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c0f5cf0ea14700c4c7e88dbfa463f8ade6dbe71b
--- /dev/null
+++ b/marked/Q/T-REC-Q.3619-201602-I_PDF-E/raw.md
@@ -0,0 +1,181 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3619**
+
+(02/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for the NGN –
+Service and session control protocols – supplementary
+services based on SIP-IMS
+
+---
+
+**Communication HOLD using IP multimedia core
+network subsystem – Protocol specification**
+
+Recommendation ITU-T Q.3619
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3616 |
+| Service and session control protocols – supplementary services based on SIP-IMS | Q.3617–Q.3639 |
+| NGN applications | Q.3700–Q.3849 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.3619
+
+## Communication HOLD using IP multimedia core network subsystem – Protocol specification
+
+## Summary
+
+Recommendation ITU-T Q.3619 v.1 (2016) specifies requirements for supplementary service such as HOLD to be provided on the IMS platform.
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.3619, and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+This Recommendation endorses ETSI TS 124 610 V10.2.0 (2013-10), "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.610 version 10.2.0 Release 10)".
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3619 v.1 | 2016-02-13 | 11 | 11.1002/1000/12717 |
+
+## Keywords
+
+HOLD, IMS, network side, SDP, SIP, testing, user side.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Recommendation ITU-T Q.3619
+
+## Communication HOLD using IP multimedia core network subsystem – Protocol specification
+
+## 1 Scope
+
+This Recommendation specifies the requirements to protocols implementation for providing supplementary service such as HOLD on the IMS basis.
+
+The Recommendation endorses ETSI TS 124 610 V10.2.0 (2013-10), "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.610 version 10.2.0 Release 10)".
+
+## 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+[ETSI TS 124 610 V10.2.0] ETSI TS 124 610 V10.2.0 (2013-10), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.610 version 10.2.0 Release 10)*.
+
+## 3 Definitions
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+IMS IP Multimedia Subsystem
+
+IP Internet protocol
+
+## 5 Conventions
+
+None.
+
+## 6 Endorsement
+
+[ETSI TS 124 610 V10.2.0].
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3625-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3625-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a308271fb239928318c461337c31936dd84fe604
--- /dev/null
+++ b/marked/Q/T-REC-Q.3625-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6a0f146a2a7abe73d858cf87904646fa5525273febbbbb82a1db78580ee044a
+size 3757
diff --git a/marked/Q/T-REC-Q.3625-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3625-201602-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5d18c560e1cbb240d8af09c132e6f876d4623f27
--- /dev/null
+++ b/marked/Q/T-REC-Q.3625-201602-I_PDF-E/raw.md
@@ -0,0 +1,187 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3625**
+
+(02/2016)
+
+# **SERIES Q: SWITCHING AND SIGNALLING**
+
+Signalling requirements and protocols for the NGN –
+Service and session control protocols – supplementary
+services based on SIP-IMS
+
+---
+
+**Completion of communications to busy
+subscriber and completion of communications
+by no reply using IP multimedia core network
+subsystem – Protocol specification**
+
+Recommendation ITU-T Q.3625
+
+## ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3616 |
+| Service and session control protocols – supplementary services based on SIP-IMS | Q.3617–Q.3639 |
+| NGN applications | Q.3700–Q.3849 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+### Recommendation ITU-T Q.3625
+
+### Completion of communications to busy subscriber and completion of communications by no reply using IP multimedia core network subsystem – Protocol specification
+
+## Summary
+
+Recommendation ITU-T Q.3625 v.1 (2016) specifies requirements for supplementary services such as completion of communications to busy subscriber (CCBS) and completion of communications by no reply (CCNR) to be provided on the IMS platform.
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.3625, and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+This Recommendation endorses ETSI TS 124 642 V10.7.0 (2013-07), "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.642 version 10.7.0 Release 10)".
+
+### History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3625 v.1 | 2016-02-13 | 11 | 11.1002/1000/12723 |
+
+### Keywords
+
+CCBS, CCNR, IMS, network side, SDP, SIP, testing, user side.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+### Recommendation ITU-T Q.3625
+
+### Completion of communications to busy subscriber and completion of communications by no reply using IP multimedia core network subsystem – Protocol specification
+
+## 1 Scope
+
+This Recommendation specifies the requirements to protocols implementation for providing supplementary services such as completion of communications to busy subscriber (CCBS) and completion of communications by no reply (CCNR) on the IMS basis.
+
+The Recommendation endorses ETSI TS 124 642 V10.7.0 (2013-07), "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.642 version 10.7.0 Release 10)".
+
+## 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+[ETSI TS 124 642 V10.7.0] ETSI TS 124 642 V10.7.0 (2013-07), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.642 version 10.7.0 Release 10)*.
+
+## 3 Definitions
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+CCBS Completion of Communications to Busy Subscriber
+
+CCNR Completion of Communications by No Reply
+
+IMS IP Multimedia Subsystem
+
+IP Internet Protocol
+
+## 5 Conventions
+
+None.
+
+## 6 Endorsement
+
+[ETSI TS 124 642 V10.7.0].
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3644-201912-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Q/T-REC-Q.3644-201912-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ade0f3997145120847439e3c826dd04673bd2f1
--- /dev/null
+++ b/marked/Q/T-REC-Q.3644-201912-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4b9a313697798c63ca2581ea7d39f83312ff3ffda3c34499ac5f712e1bad245
+size 76069
diff --git a/marked/Q/T-REC-Q.3644-201912-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.3644-201912-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8fa827552020835dc92ee6b1d1cc1b2bf31dbe1e
--- /dev/null
+++ b/marked/Q/T-REC-Q.3644-201912-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a56579502d0970e123ece9d57178818795ace3518009f100c4be5281e9ad07a7
+size 83746
diff --git a/marked/Q/T-REC-Q.3644-201912-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/Q/T-REC-Q.3644-201912-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426
--- /dev/null
+++ b/marked/Q/T-REC-Q.3644-201912-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d
+size 3828
diff --git a/marked/Q/T-REC-Q.3644-201912-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Q/T-REC-Q.3644-201912-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..32fb5534d2c2db705a885d3c89492a9bc3ab5ee7
--- /dev/null
+++ b/marked/Q/T-REC-Q.3644-201912-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:300c6df85118a7cf5101f426b62c8295109c5219c266b55876b5dd7b312e4e0d
+size 94667
diff --git a/marked/Q/T-REC-Q.3644-201912-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3644-201912-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4d78b4e0ba07ec028db41b4f8ac03268b2a2cadc
--- /dev/null
+++ b/marked/Q/T-REC-Q.3644-201912-I_PDF-E/raw.md
@@ -0,0 +1,538 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3644**
+
+(12/2019)
+
+SERIES Q: SWITCHING AND SIGNALLING, AND
+ASSOCIATED MEASUREMENTS AND TESTS
+
+Signalling requirements and protocols for the NGN –
+VoLTE/ViLTE network signalling
+
+# --- **Requirements for signalling network analyses and optimization in VoLTE**
+
+Recommendation ITU-T Q.3644
+
+## ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS**
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3616 |
+| Service and session control protocols – supplementary services based on SIP-IMS | Q.3617–Q.3639 |
+| VoLTE/ViLTE network signalling | Q.3640–Q.3655 |
+| NGN applications | Q.3700–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.3644
+
+# Requirements for signalling network analyses and optimization in VoLTE
+
+## Summary
+
+Recommendation ITU-T Q.3644 specifies the requirements for signalling network analyses and optimization in voice over LTE (VoLTE) in which the signalling network refers to the network entities and the signalling exchange which are related to telecommunications services. This Recommendation covers the aspects including an overview of a signalling network, requirements for signalling collecting, requirements for signalling network analyses, requirements for signalling network optimization and general security considerations in VoLTE.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3644 | 2019-12-14 | 11 | 11.1002/1000/14143 |
+
+## Keywords
+
+IMS, signalling collecting, signalling network analyses, signalling network optimization, VoLTE.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2020
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+###### Page
+
+| | | |
+|-----|------------------------------------------------------------------------------------|----|
+| 1 | Scope..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 1 |
+| 3.1 | Terms defined elsewhere ..... | 1 |
+| 3.2 | Terms defined in this Recommendation ..... | 1 |
+| 4 | Abbreviations and acronyms ..... | 2 |
+| 5 | Conventions ..... | 3 |
+| 6 | Overview of signalling network in VoLTE ..... | 3 |
+| 7 | Requirements for signalling collecting in VoLTE..... | 4 |
+| 7.1 | General requirements for signalling collecting in VoLTE ..... | 4 |
+| 7.2 | Interfaces to be collected in VoLTE signalling network..... | 4 |
+| 8 | Requirements for signalling network analyses in VoLTE..... | 5 |
+| 8.1 | General functional requirements for signalling network analyses in VoLTE..... | 5 |
+| 8.2 | Quota requirements for signalling network analyses in VoLTE ..... | 6 |
+| 8.3 | Status information requirements for signalling network analyses in VoLTE..... | 8 |
+| 9 | Requirements for signalling network optimization in VoLTE ..... | 8 |
+| 9.1 | General requirements for signalling network optimization in VoLTE ..... | 8 |
+| 9.2 | Preconditions of signalling network optimization..... | 8 |
+| 9.3 | Requirements for signalling network optimization on network entities ..... | 9 |
+| 9.4 | Requirements for optimization of signalling exchange between network entities..... | 10 |
+| 10 | General security considerations ..... | 12 |
+
+
+
+## Recommendation ITU-T Q.3644
+
+# Requirements for signalling network analyses and optimization in VoLTE
+
+# 1 Scope
+
+This Recommendation presents the requirements for signalling collecting, signalling network analyses and signalling network optimization in a voice over LTE (VoLTE) network.
+
+The signalling network refers to the network entities and the signalling exchange which are related to telecommunications services. Making use of the information obtained in signalling collecting on interfaces, signalling network analyses and optimization can be implemented on a VoLTE network.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendation and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ETSI TS 123 216] ETSI TS 123 216 V14.0.0 (2017-05), *Single Radio Voice Call Continuity (SRVCC)*.
+- [ETSI TS 123 218] ETSI TS 123 218 V15.0.0 (2018-06), *IP Multimedia (IM) session handling; IM call model*.
+- [ETSI TS 123 228] ETSI TS 123 228 V14.6.0 (2018-01), *IP Multimedia Subsystem (IMS)*.
+- [ETSI TS 123 401] ETSI TS 123 401 V14.10.0 (2018-12), *General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+None.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+- 3.2.1 signalling network:** Refers to the network entities and the signalling exchange which are related to telecommunications services.
+- 3.2.2 signalling collecting:** Refers to signalling collecting on the interfaces which are related to the signalling processes of telecommunications services.
+- 3.2.3 signalling network analyses:** Refers to analyses on quotas using the information obtained in signalling collecting, and analyses on status information of signalling network.
+- 3.2.4 signalling network optimization:** Refers to signalling network optimization on network entities and optimization of signalling exchange between network entities in a signalling network, on the basis of signalling network analyses.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|----------|----------------------------------------------------------|
+| AI | Artificial Intelligence |
+| AS | Application Server |
+| BGCF | Breakout Gateway Control Function |
+| BICC | Bearer Independent Call Control |
+| BSF | Bootstrapping Server Function |
+| CS | Circuit Switched |
+| CSCF | Call Session Control Function |
+| eNodeB | evolved Node B |
+| GTP | GPRS Tunnel Protocol |
+| HLR | Home Location Register |
+| HSS | Home Subscriber Server |
+| IBCF | Interconnection Border Control Function |
+| I-CSCF | Interrogating Call Session Control Function |
+| IMS | IP Multimedia Subsystem |
+| IP-SM-GW | IP Short Message Gateway |
+| LTE | Long Term Evolution |
+| MAP | Mobile Application Part |
+| MGCF | Media Gateway Control Function |
+| MME | Mobility Management Entity |
+| MO | Mobile Originated |
+| MRFC | Multimedia Resource Function Controller |
+| MSC | Mobile Switching Center |
+| MT | Mobile Terminated |
+| NAF | Network Application Function |
+| PCRF | Policy and Charging Rules Function |
+| P-CSCF | Proxy Call Session Control Function |
+| PGW | Packet Gateway |
+| PS | Packet Switched |
+| S-CSCF | Serving Call Session Control Function |
+| SGW | Serving Gateway |
+| SIP | Session Initiation Protocol |
+| SRVCC | Single Radio Voice Call Continuity |
+| UE | User Equipment |
+| VoLTE | Voice over LTE |
+| XCAP | Extensible Markup Language Configuration Access Protocol |
+
+# 5 Conventions
+
+In this Recommendation:
+
+The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed.
+
+The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+
+# 6 Overview of signalling network in VoLTE
+
+The signalling network in voice over LTE (VoLTE) refers to the network entities and interfaces which are related to the signalling processes of VoLTE services in IP multimedia subsystem (IMS), packet switched (PS) and circuit switched (CS) domains. The network entities in a VoLTE signalling network include serving call session control function (S-CSCF), interrogating call session control function (I-CSCF), proxy call session control function (P-CSCF), application server (AS), home subscriber server (HSS), IP short message gateway (IP-SM-GW), interconnection border control function (IBCF), breakout gateway control function (BGCF), media gateway control function (MGCF), multimedia resource function controller (MRFC), policy and charging rules function (PCRF), mobility management entity (MME), etc. The interfaces in VoLTE signalling network include Cx, Rx, Sh, Gm, ISC, Mw, Sv, etc., which exchange signalling between network entities. The interfaces in a VoLTE signalling network are based on the protocols of Diameter, session initiation protocol (SIP), GTP-C, etc. Figure 1 shows the main network entities and interfaces of a signalling network in VoLTE.
+
+
+
+The diagram illustrates the network architecture for VoLTE, showing the interaction between the User Equipment (UE) and various network functions across different domains. The UE connects to an eNodeB, which is part of the LTE domain. The eNodeB connects to an MME via the S1-MME interface. The MME connects to an SGW via the S1-U interface. The SGW connects to a PGW (PCEF) via the S5/S8 interface. The PGW connects to an HSS/HLR via the S6a interface. The HSS/HLR connects to a PCRF via the Gx interface. The PCRF connects to the PGW via the Rx interface. The MME also connects to a BSF/NAF via the Ut interface. The BSF/NAF connects to the IMS via the Zh interface. The IMS contains several entities: AS, MRFC, S/I-CSCF, BGCF, IBCF, IP-SM-GW, P-CSCF, and MGCF/IM-MGW. The S/I-CSCF connects to the AS via the Ma interface, to the MRFC via the Mr interface, to the IBCF via the Mx interface, to the IP-SM-GW via the ISC interface, to the P-CSCF via the Mw interface, and to the MGCF/IM-MGW via the Mj and Mg interfaces. The P-CSCF connects to the HSS/HLR via the Sh/J interface and to the PGW via the SGi interface. The MGCF/IM-MGW connects to the eMSC in the CS domain via the Imc interface. The eMSC connects to the PGW via the C/D interface. The UE also has a direct connection to the IMS via the Ut interface. The HSS/HLR connects to the IMS via the Cx/Dx interface. The diagram is labeled with Q.3644(19)\_F01.
+
+Diagram of the main network entities and interfaces of a signalling network in VoLTE. The diagram shows three main domains: IMS (dashed box), LTE (dashed box), and CS domain (dashed box). Entities include UE, eNodeB, MME, SGW, PGW (PCEF), HSS/HLR, PCRF, BSF/NAF, AS, MRFC, S/I-CSCF, BGCF, IBCF, IP-SM-GW, P-CSCF, MGCF/IM-MGW, and eMSC. Interfaces shown include Ut, Sh, Cx/Dx, Zh, S6a, S11, S1-MME, S1-U, S5/S8, Gx, Rx, SGi, Gm, Sv, ISC, Ma, Mr, Mx, Mw, Mj, Mg, and Imc.
+
+Figure 1 – The main network entities and interfaces of a signalling network in VoLTE
+
+# **7 Requirements for signalling collecting in VoLTE**
+
+## **7.1 General requirements for signalling collecting in VoLTE**
+
+This clause presents the general requirements for signalling collecting on the interfaces which are related to the signalling processes of VoLTE services.
+
+The interfaces to be collected in VoLTE signalling network are divided into the following categories:
+
+- Interfaces based on Diameter protocol, e.g., Cx, Rx, Sh;
+- Interfaces based on SIP protocol, e.g., Gm, ISC, Mw;
+- Interfaces based on GTP/GTP-C protocol, e.g., Sv, S1-MME, S11;
+- Interfaces based on extensible markup language configuration access protocol (XCAP), e.g., Ut;
+- Interfaces based on mobile application part (MAP) protocol, e.g., C/D, J;
+- Interfaces based on BICC/ISUP protocol, e.g., Imc.
+
+The signalling collecting function is required to meet the requirements as follows:
+
+- Signalling is required to be collected from all the interfaces shown in Figure 1 for end-to-end signalling analyses.
+- Specified signalling can be collected for one interface or signalling exchange between two network entities.
+- Signalling collecting function is required to support all the interfaces and protocols to be collected.
+- The information to be collected in signalling collecting is required to be configurable.
+- The information collected in signalling collecting is required to be accurate and brief as possible.
+- Signalling collecting function is required to cache the information obtained in signalling collecting for subsequent information processing.
+- Signalling collecting function is required to support flexible extension capability to meet the new requirements of operators and adapt to the evolution of VoLTE network.
+- Signalling collecting function is required to not influence the functions of the network entities related to the collected interfaces.
+- Signalling collecting function is required to avoid the impact on the performance of the network entities related to the collected interfaces.
+- It is recommended to use artificial intelligence (AI) technologies to assist in signalling collecting.
+
+## **7.2 Interfaces to be collected in VoLTE signalling network**
+
+The interfaces to be collected and corresponding protocols and connected network entities in VoLTE signalling network are listed in Table 1. Based on the network status and capabilities of signalling collecting system, the collected interfaces can be customized by the operator.
+
+**Table 1 – Interfaces to be collected in VoLTE signalling network**
+
+| Interface | Protocol | Connected network entities |
+|------------------|-----------------|------------------------------------------------------------------|
+| S6a | Diameter | MME and HSS |
+| Gx | Diameter | PGW and PCRF |
+| Rx | Diameter | P-CSCF and PCRF |
+| Cx | Diameter | S/I-CSCF and HSS |
+| Sh | Diameter | AS and HSS |
+| Zh | Diameter | BSF and HSS |
+| ISC | SIP | S-CSCF and AS |
+| Ma | SIP | I-CSCF and AS |
+| Mg | SIP | S/I-CSCF and MGCF |
+| Mj | SIP | BGCF and MGCF |
+| Mw | SIP | P-CSCF and S/I-CSCF; S/I-CSCF and S/I-CSCF;
S/I-CSCF and eMSC |
+| Mx | SIP | S/I-CSCF and IBCF; BGCF and IBCF |
+| Mr | SIP | S-CSCF and MRFC |
+| Gm | SIP | UE and P-CSCF |
+| Sv | GTP | MME and eMSC |
+| S1-MME | GTP-C | MME and eNodeB |
+| S11 | GTP-C | MME and SGW |
+| S5/S8 | GTP-C | SGW and PGW |
+| Ut | XCAP | UE and BSF; UE and NAF; NAF and AS |
+| C/D | MAP | HLR and eMSC |
+| Sh/J | Diameter/MAP | HSS and IP-SM-GW |
+| Imc | BICC/SIP/ISUP | MGCF and Entities in CS Domain |
+
+# **8 Requirements for signalling network analyses in VoLTE**
+
+## **8.1 General functional requirements for signalling network analyses in VoLTE**
+
+The following functions can be supported by signalling network analyses:
+
+- Signalling from different interfaces can be related for the same call to form end to end signalling procedures for quota calculating and fault fixing. In addition, signalling can be interpreted for specified interface.
+- Calls with the same failure code can be counted. In addition, end-to-end signalling for specified failure call can be presented.
+- Quotas which are needed by operators to exam quality of VoLTE can be obtained by signalling network analyses.
+- The methods and quotas of signalling network analyses in VoLTE need to support customization to meet the various requirements of different operators.
+- The status information of network entities and signalling exchange between network entities is also recommended to be obtained and analysed in the processes of signalling
+
+network analyses, which can be used in analyses of quotas, also in the following processes of signalling network optimization.
+
+- It is recommended to use AI technologies to assist in signalling network analyses.
+
+## 8.2 Quota requirements for signalling network analyses in VoLTE
+
+The following quotas can be obtained by signalling network analyses:
+
+- IMS registration success rate
+
+IMS registration success rate = (P-CSCF initial registration request success times/P-CSCF initial registration request times) \*100%
+
+According to the registration information flow described in [ETSI TS 123 228], the P-CSCF initial registration request times means the times P-CSCF sends Register messages and the P-CSCF initial registration request success times means the times P-CSCF receives 200 OK messages corresponding to the Register messages in a specified period.
+
+- call setup success rate
+
+call setup success rate = (S-CSCF call setup request success times/S-CSCF call setup request times received) \*100%
+
+According to the origination procedures and termination procedures described in [ETSI TS 123 228], S-CSCF call setup request times received means the times S-CSCF receives Invite messages and S-CSCF call setup request success times means the times S-CSCF sends Ringing messages corresponding to the Invite messages which were received by S-CSCF in a specified period.
+
+- MO call setup success rate
+
+MO call setup success rate = (P-CSCF original call setup request success times/P-CSCF original call setup request times) \*100%
+
+According to the origination procedures described in [ETSI TS 123 228], P-CSCF original call setup request times means the times P-CSCF sends Invite messages and P-CSCF original call setup request success times means the times P-CSCF receives Ringing messages corresponding to the Invite messages which were sent by P-CSCF in a specified period.
+
+- MT call setup success rate
+
+MT call setup success rate = (S-CSCF MT call setup request success times/S-CSCF MT call setup request times) \*100%
+
+According to the origination procedures described in [ETSI TS 123 228], S-CSCF MT call setup request times means the times S-CSCF receives Invite messages and S-CSCF MT call setup request success times means the times S-CSCF sends Ringing messages corresponding to the Invite messages which were received by S-CSCF in a specified period.
+
+- speech call setup success rate
+
+speech call setup success rate = (S-CSCF speech call setup request success times/S-CSCF speech call setup request times received) \*100%
+
+According to the origination procedures and termination procedures described in [ETSI TS 123 228], S-CSCF speech call setup request times received means the times S-CSCF receives Invite messages with SDP only speech included and S-CSCF speech call setup request success times means the times S-CSCF sends Ringing messages corresponding to the Invite messages with SDP only speech included which were received by S-CSCF in a specified period.
+
+– video call setup success rate
+
+video call setup success rate = (S-CSCF video call setup request success times/S-CSCF video call setup request times received) \*100%
+
+According to the origination procedures and termination procedures described in [ETSI TS 123 228], S-CSCF video call setup request times received means the times S-CSCF receives Invite messages with SDP speech and video included and S-CSCF video call setup success times means the times S-CSCF sends Ringing messages corresponding to the Invite messages with SDP speech and video included which were received by S-CSCF in a specified period.
+
+– call answer rate
+
+call answer rate = (S-CSCF call answer times/S-CSCF call setup request times received) \*100%
+
+According to the origination procedures and termination procedures described in [ETSI TS 123 228], S-CSCF call setup request times received means the times S-CSCF receives Invite messages and S-CSCF call answer times means the times S-CSCF sends 200 OK messages corresponding to the Invite messages which were received by S-CSCF in a specified period.
+
+– average call setup latency
+
+average call setup latency = average of interval between SIP message 180 and Invite in P-CSCF
+
+According to the origination procedures described in [ETSI TS 123 228], Interval between SIP message 180 and Invite in P-CSCF means the time that P-CSCF receives Ringing message subtracted by the time that P-CSCF sends Invite message for the same session.
+
+– IMS dedicated bearer setup success rate
+
+IMS dedicated bearer setup success rate = (SAE GW IMS dedicated bearer setup success times/SAE GW IMS dedicated bearer setup times) \*100%
+
+According to dedicated bearer activation described in [ETSI TS 123 401], SAE GW IMS dedicated bearer setup times means the times SAE GW sends Create Bearer Request for IMS dedicated bearer and SAE GW IMS dedicated bearer setup success times means the times SAE GW receives Create Bearer Response with EPS Bearer Identity, S5/S8-TEID and User Location Information (ECGI) corresponding to the Create Bearer Request which were sent by SAE GW in a specified period.
+
+– SRVCC handover success rate
+
+SRVCC handover success rate = (SRVCC handover complete times received by MME/SRVCC handover request times sent by MME) \*100%
+
+According to the SRVCC handover procedures described in [ETSI TS 123 216], SRVCC handover request times sent by MME means the times MME sends PS to CS handover request messages to eMSC in a specified period, and SRVCC handover complete times received by MME means the times MME receives PS to CS handover complete messages from eMSC in a specified period.
+
+– SRVCC handover latency
+
+SRVCC handover latency = average of interval between MME receiving SRVCC handover complete message and MME sending SRVCC handover request message
+
+According to the SRVCC handover procedures described in [ETSI TS 123 216], interval between MME receiving SRVCC handover complete message and MME sending SRVCC handover request messages means the time MME receives PS to CS handover complete message from eMSC subtracted by the time MME sends PS to CS handover request message to eMSC for the same SRVCC handover session.
+
+## **8.3 Status information requirements for signalling network analyses in VoLTE**
+
+The status information of VoLTE signalling network is recommended to be obtained and analysed in signalling network analyses. This clause presents the common status information to be obtained.
+
+- The status information of network entities, which refers to the status information of all the network entities in VoLTE signalling network, which includes hardware capacity, software capacity, real-time load, computing resources, storage resources, network resources, signalling process configuration, etc.
+- The status information of signalling exchange between network entities, which refers to the status information of all the signalling exchange in VoLTE signalling network, which includes signalling route mechanism, signalling transmission mechanism, signalling messages and their parameters, etc.
+
+# **9 Requirements for signalling network optimization in VoLTE**
+
+## **9.1 General requirements for signalling network optimization in VoLTE**
+
+This clause presents the general requirements for optimization of VoLTE signalling network, which is implemented based on the results of signalling network analyses.
+
+The signalling network optimization function is required to meet the requirements as follows:
+
+- By adjusting the configuration of the network entities related to the signalling processes of VoLTE services, the performance of VoLTE signalling network can be improved.
+- By dynamically increasing the computing resources, storage resources and network resources of the bottle-neck network entities related to the signalling processes of VoLTE services, the performance of the bottle-neck network entities and VoLTE signalling network can be improved.
+- Optimization of the signalling exchange between the network entities by:
+ - Adjusting the mechanisms of signalling route selection, signalling route failover and failback, signalling route reselection, signalling retransmission, etc.
+ - Removing the unnecessary or optional parameters in signalling messages of signalling exchange.
+- By locating the overloaded network entities or malfunction network entities in advance, the disaster failover and failback operations can be avoided in some cases, in this way the performance of VoLTE signalling network can be improved.
+- Signalling network optimization function is required to support both manual operation and automatic operation based on optimization instructions.
+- Signalling network optimization function is required to support flexible extension capability to meet the various requirements of operators and adapt to the evolution of VoLTE network. Both the forward compatibility issues and the backward compatibility issues are required to be addressed.
+- Signalling network optimization function is required to not influence the functions of the network entities in VoLTE signalling network, also it is required to have no negative effects on the performance of VoLTE signalling network.
+- It is recommended to use AI technologies to assist in signalling network optimization.
+
+## **9.2 Preconditions of signalling network optimization**
+
+The operation of signalling network optimization has the preconditions as follows:
+
+- The quotas of signalling network which can reflect the network status have been obtained in the processes of signalling network analyses.
+
+- The status information of network entities and signalling exchange between network entities, which can assist in the generation of optimization instructions, has been obtained in the processes of signalling network analyses.
+- The quotas of signalling network can be translated to the optimization instructions with the assistance of the status information of VoLTE signalling network. The optimization instructions are machine-readable and human-readable messages which contain operational details.
+- The network entities support dynamic configuration based on the optimization instructions.
+- The signalling exchange between network entities supports dynamic configuration based on the optimization instructions.
+- The network entities and the signalling exchange between network entities support fallback mechanism in case of failed or invalid signalling network optimization.
+- The network entities support the automatic generation of signalling network optimization reports for future reference or manual intervention.
+
+## 9.3 Requirements for signalling network optimization on network entities
+
+On the basis of quotas of signalling network and status information of network entities, the signalling network optimization on network entities is implemented. Figure 2 describes the process of signalling network optimization on network entities.
+
+
+
+```
+
+graph TD
+ A[Dynamically monitor the quotas of signalling network] --> B{Compare the quotas with the threshold requirements}
+ B -- "Quotas satisfy the threshold requirements" --> C([Fall back])
+ B -- "Quotas do not satisfy the threshold requirements" --> D[Check the status information of network entities]
+ D --> E[Generate the optimization instructions on network entities]
+ E --> F[Optimization on related network entities]
+ F --> G{Check the effect of signalling network optimization}
+ G -- "Quotas have been improved" --> H([End])
+ G -- "Quotas have not been improved" --> C
+ C --> A
+ H --> A
+
+```
+
+Q.3644(19)\_F02
+
+Flowchart of the signalling network optimization process. The process starts with 'Dynamically monitor the quotas of signalling network', followed by 'Compare the quotas with the threshold requirements'. If 'Quotas satisfy the threshold requirements', it goes to 'Fall back'. If 'Quotas do not satisfy the threshold requirements', it proceeds to 'Check the status information of network entities', then 'Generate the optimization instructions on network entities', and 'Optimization on related network entities'. After optimization, it checks the effect. If 'Quotas have been improved', it ends. If 'Quotas have not been improved', it goes to 'Fall back'. A feedback loop from 'Fall back' returns to the initial monitoring step. Source: Q.3644(19)\_F02.
+
+**Figure 2 – The process of signalling network optimization on network entities**
+
+- 1) The system dynamically monitors the quotas of signalling network, the monitor process is executed periodically.
+- 2) The system compares the quotas of signalling network with the preconfigured threshold requirements. If quotas satisfy the threshold requirements, the system continues to monitor the quotas. If quotas do not satisfy the threshold requirements, the system initiates the operation of signalling network optimization on network entities.
+- 3) The system checks the status information of network entities to find out the possible aspects to be improved, e.g., configuration of network entities, performance of network entities.
+- 4) The system generates the optimization instructions on related network entities, e.g., modifying the signalling processing configuration of network entity A, initiating the overload control mechanism on network entity B, dynamically increasing the computing resources of network entity C.
+- 5) The related network entities perform optimization based on the optimization instructions.
+- 6) The system checks the effect of signalling network optimization on network entities. If quotas have been improved, the signalling network optimization ends successfully with a success report been generated, and the system continues to monitor the quotas. If quotas have not been improved, the system instructs related network entities to fall back to the previous status, a failure report calling for manual intervention is generated, and the system continues to monitor the quotas.
+
+## **9.4 Requirements for optimization of signalling exchange between network entities**
+
+On the basis of quotas of signalling network and status information of signalling exchange, the optimization of signalling exchange between network entities is implemented. Figure 3 describes the process of optimization of signalling exchange between network entities.
+
+
+
+```
+
+graph TD
+ A[Dynamically monitor the quotas of signalling network] --> B{Compare the quotas with the threshold requirements}
+ B -- "Quotas satisfy the threshold requirements" --> A
+ B -- "Quotas do not satisfy the threshold requirements" --> C[Check the status information of signalling exchange between network entities]
+ C --> D[Generate the optimization instructions on signalling exchange between network entities]
+ D --> E[Optimization on related signalling exchange between network entities]
+ E --> F{Check the effect of signalling network optimization}
+ F -- "Quotas have been improved" --> G([End])
+ G --> A
+ F -- "Quotas have not been improved" --> H([Fall back])
+ H --> A
+
+```
+
+Q.3644(19)\_F03
+
+Flowchart illustrating the process of optimization of signalling exchange between network entities. The process starts with 'Dynamically monitor the quotas of signalling network', followed by 'Compare the quotas with the threshold requirements'. If 'Quotas satisfy the threshold requirements', it loops back to monitoring. If 'Quotas do not satisfy the threshold requirements', it proceeds to 'Check the status information of signalling exchange between network entities', then 'Generate the optimization instructions on signalling exchange between network entities', and 'Optimization on related signalling exchange between network entities'. A decision diamond 'Check the effect of signalling network optimization' follows. If 'Quotas have been improved', it ends at 'End' and loops back to monitoring. If 'Quotas have not been improved', it goes to 'Fall back' and loops back to monitoring.
+
+**Figure 3 – The process of optimization of signalling exchange between network entities**
+
+- 1) The system of signalling network optimization dynamically monitors the quotas of signalling network, the monitor process is executed periodically.
+- 2) The system compares the quotas of signalling network with the preconfigured threshold requirements. If quotas satisfy the threshold requirements, the system continues to monitor the quotas. If quotas do not satisfy the threshold requirements, the system initiates the operation of optimization of signalling exchange between network entities.
+- 3) The system checks the status information of signalling exchange between network entities to find out the possible aspects to be improved, e.g. signalling route mechanism, signalling messages and their parameters.
+- 4) The system generates the optimization instructions on related signalling exchange, e.g. adjusting the signalling route selection mechanism of signalling exchange A-B, adjusting the signalling retransmission mechanism of signalling exchange B-C, removing the unnecessary or optional parameters in signalling messages of signalling exchange A-C.
+- 5) The network entities which are related to the signalling exchange perform optimization based on the optimization instructions.
+- 6) The system checks the effect of optimization of signalling exchange between network entities. If quotas have been improved, the signalling network optimization ends successfully with a success report been generated, and the system continues to monitor the quotas. If quotas have not been improved, the system instructs related signalling exchange
+
+to fall back to the previous status, a failure report calling for manual intervention is generated, and the system continues to monitor the quotas.
+
+NOTE 1 – Signalling network optimization on network entities and optimization of signalling exchange between network entities can be implemented simultaneously or separately, depends on the strategy configured by the operator.
+
+NOTE 2 – AI technologies are recommended to be applied in signalling network optimization on network entities and optimization of signalling exchange between network entities.
+
+# **10 General security considerations**
+
+The general security considerations about signalling collecting, signalling network analyses and signalling network optimization in VoLTE are as follows:
+
+### - Information security
+
+To ensure the user information security and network information security, the information obtained in the processes of signalling collecting, signalling network analyses and signalling network optimization in VoLTE should be protected from leakage, unauthorized access and misuse, with the application of mature technologies of access control, authentication and authorization, transport security and data encryption.
+
+### - Network operation security
+
+To ensure the security of telecommunications network operation, the functions of the network entities in VoLTE signalling network should not be influenced in the processes of signalling collecting, signalling network analyses and signalling network optimization. In addition, the signalling network optimization should not have negative effects on the performance of VoLTE signalling network, both on network entities and signalling exchange between network entities.
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3645-202009-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc2ed15a8a433942734b04484694a25134da2a2c
--- /dev/null
+++ b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/053f1077d592e6622cd21dc4bb4cb366_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:653d27830db84398baf02c87ee8bc6d2a0c8712575f55f4f5bda780617c1ae12
+size 24860
diff --git a/marked/Q/T-REC-Q.3645-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd85c5f0cf29767d5fce2cdb865aece52387c01d
--- /dev/null
+++ b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09082581f21d9548df66739aba3c0950a4cd19b319365b8f1c69a3129a386b3c
+size 4070
diff --git a/marked/Q/T-REC-Q.3645-202009-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6def9b183816a21dd8340582705d7eaf0b616381
--- /dev/null
+++ b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/410562339ce067fdc6fa41940c118658_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71a6b1c0cd2dbabcb36ed89689591185fa0f6bf2265c0c630a05c6a56805c8f8
+size 24388
diff --git a/marked/Q/T-REC-Q.3645-202009-I_PDF-E/740442c999390734911677f01af0316d_img.jpg b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/740442c999390734911677f01af0316d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a84ef1ec5c2549bba8de5770a2a17dabe17e733
--- /dev/null
+++ b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/740442c999390734911677f01af0316d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a7ae0f14f81bb1044197ee87da054fee049fe6a912586cbae799815e55da64a
+size 37215
diff --git a/marked/Q/T-REC-Q.3645-202009-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ed577632c5e642c7b10b0d6f07845c30a244381
--- /dev/null
+++ b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/7f17c430b9598e4d748a8041457810b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c07b5862accccfd23d9d2bd6744941d17c3f0b5e05ec7f22cc0401d3a0f66344
+size 23468
diff --git a/marked/Q/T-REC-Q.3645-202009-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..37cc5bec11974bb7257ff778f671e29dc7fd3e88
--- /dev/null
+++ b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:245a6a66cec83ea47b9039288058e56d6db6327fee2e39ba44d12506adb0585c
+size 23556
diff --git a/marked/Q/T-REC-Q.3645-202009-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..847b5a571a20508f2035fdd5af903f2095282d32
--- /dev/null
+++ b/marked/Q/T-REC-Q.3645-202009-I_PDF-E/dbe553cf16dd14073b89a8263a428664_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66f7caacd354e999fcc3e91cd0311dc51b9a33383389d996820724d05e09334f
+size 23706
diff --git a/marked/Q/T-REC-Q.3711-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426
--- /dev/null
+++ b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d
+size 3828
diff --git a/marked/Q/T-REC-Q.3711-201608-I_PDF-E/5a95b187de0044da69b7322e04761b86_img.jpg b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/5a95b187de0044da69b7322e04761b86_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f3c3ba975578d9759a6e49cce481c9afb5deef9a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/5a95b187de0044da69b7322e04761b86_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6412ea3870c1b7f65c2364b7d2c928a5635e738ea2dcd6b18d24f8eea8ed8007
+size 15602
diff --git a/marked/Q/T-REC-Q.3711-201608-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..259ff54a23b464263970f9a9d8229694abe10d5f
--- /dev/null
+++ b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/a234352dfaccdc24745c88eef7724cc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd9078f50400c0f81b5062b548785ebbd3d9d366070dc8d703a62ab48f45623c
+size 45361
diff --git a/marked/Q/T-REC-Q.3711-201608-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..770b1c1fb764461117fe2a943370bb1806b45794
--- /dev/null
+++ b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d1c82564756336df1d2dfe781ebd2dd233a47971fe80fed7e2eb98a8ece89ff
+size 94638
diff --git a/marked/Q/T-REC-Q.3711-201608-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7bbde555b6a038a2a982980daa5b55ad9bbb42cb
--- /dev/null
+++ b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ed08cc3c71a9fd4feaa88c0eabb0830376b973c621177863a890037a6b3d8b26
+size 50232
diff --git a/marked/Q/T-REC-Q.3711-201608-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d71bcc41acd211c5063e787d05ee2e320566185
--- /dev/null
+++ b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3007b1776a227c7e47dda7bd43e57c9c888a000275d9c812fc3c9d4d9a12e83f
+size 19822
diff --git a/marked/Q/T-REC-Q.3711-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ec8b6337044d485bc2a7b5fb73ed922e1d65c719
--- /dev/null
+++ b/marked/Q/T-REC-Q.3711-201608-I_PDF-E/raw.md
@@ -0,0 +1,997 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3711**
+
+(08/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for SDN – Resource control protocols
+
+# --- **Signalling requirements for software-defined broadband access network**
+
+Recommendation ITU-T Q.3711
+
+## ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000-Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710-Q.3899 |
+| Resource control protocols | Q.3710-Q.3739 |
+| TESTING SPECIFICATIONS | Q.3900-Q.4099 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.3711
+
+# Signalling requirements for software-defined broadband access network
+
+## Summary
+
+Recommendation ITU-T Q.3711 provides an overview of software-defined broadband access network (SBAN) and its procedures, and specifies the signalling requirements of the northbound interface and southbound interface of SBAN model.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3711 | 2016-08-29 | 11 | 11.1002/1000/12989 |
+
+## Keywords
+
+BAN, broadband access network, SDN, software-defined networking.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and acronyms ..... | 1 |
+| 5 Conventions ..... | 3 |
+| 6 Introduction of SBAN..... | 3 |
+| 7 Procedures..... | 4 |
+| 7.1 SBAN node initialization ..... | 4 |
+| 7.2 Registration..... | 5 |
+| 7.3 Status query ..... | 5 |
+| 7.4 Service creation ..... | 5 |
+| 8 The signalling requirements of SBAN ..... | 6 |
+| 8.1 Overview of signalling requirements ..... | 6 |
+| 8.2 Signalling requirements for southbound interface ..... | 7 |
+| 8.3 Signalling requirements for northbound interface..... | 13 |
+| 9 Security considerations ..... | 18 |
+| Appendix I – An example of SBAN ..... | 19 |
+| Bibliography..... | 21 |
+
+
+
+## Recommendation ITU-T Q.3711
+
+## Signalling requirements for software-defined broadband access network
+
+## 1 Scope
+
+This Recommendation specifies software-defined broadband access network (SBAN) by providing:
+
+- Overview of SBAN;
+- Procedures of SBAN;
+- Signalling requirements of the northbound interface and southbound interface of SBAN model;
+- Example of SBAN.
+
+## 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+[ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 access network** [b-ITU-T Q.1742.11]: Network that connects access technologies such as a radio access network to the core network.
+
+**3.1.2 software-defined networking** [ITU-T Y.3300]: A set of techniques that enables to directly program, orchestrate, control and manage network resources, which facilitates the design, delivery and operation of network services in a dynamic and scalable manner.
+
+## 3.2 Terms defined in this Recommendation
+
+None.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|----------|---------------------------------------|
+| APP | Application |
+| APP-ASQ | SDN Application Status Query |
+| APP-ASQP | SDN Application Status Query Response |
+| APP-RE | SDN Application Register |
+| APP-REP | SDN Application Register Response |
+
+| | |
+|-----------|-------------------------------------------|
+| BAN | Broadband Access Network |
+| BTS | Base Transceiver Station |
+| CE | Customer Edge |
+| eNodeB | Evolved Node B |
+| ID | Identification |
+| IP | Internet Protocol |
+| MAC | Media Access Control |
+| MPLS | Multi-Protocol Label Switching |
+| OAM | Operation, Administration and Maintenance |
+| OPEX | Operating Expense |
+| QoS | Quality of Service |
+| RAN | Radio Access Network |
+| RNC | Radio Network Controller |
+| SBAN | Software-defined Broadband Access Network |
+| SBAN-FI | SBAN Flow Initiation |
+| SBAN-FIP | SBAN Flow Initiation Response |
+| SBAN-FQ | SBAN Flow Query |
+| SBAN-FQP | SBAN Flow Query Response |
+| SBAN-NQ | SBAN Network Query |
+| SBAN-NQP | SBAN Network Query Response |
+| SBAN-NSI | SBAN Network Service Initiation |
+| SBAN-NSIP | SBAN Network Service Initiation Response |
+| SBAN-NSQ | SBAN Network Service Query |
+| SBAN-NSQP | SBAN Network Service Query Response |
+| SBAN-PR | SBAN Node Port Register |
+| SBAN-PRP | SBAN Node Port Register Response |
+| SBAN-PSQ | SBAN Node Port Status Query |
+| SBAN-PSQP | SBAN Node Port Status Query Response |
+| SBAN-RE | SBAN Node Register |
+| SBAN-REP | SBAN Node Register Response |
+| SBAN-SQ | SBAN Node Status Query |
+| SBAN-SQP | SBAN Node Status Query Response |
+| SCTP | Stream Control Transmission Protocol |
+| SDN | Software-Defined Networking |
+| TCP | Transmission Control Protocol |
+| TLS | Transport Layer Security |
+| UDP | User Datagram Protocol |
+
+# 5 Conventions
+
+In this Recommendation:
+
+- {A}: indicates that the parameter A is mandatory;
+- [B]: indicates that the parameter B is optional;
+- \*: indicates that the parameter may be multiple items.
+
+# 6 Introduction of SBAN
+
+Broadband business has become the main source of revenue for carriers, and broadband access network (BAN) plays an important role in carriers' network. But there are still a number of challenges which need to be addressed in BAN, especially for IP radio access network (RAN), see Appendix I.
+
+BAN includes two types of nodes: access nodes and aggregate nodes. The access nodes connect the user devices, such as: base transceiver station (BTS), evolved node B (eNodeB), or customer edge (CE), and the aggregate nodes connect the network devices, such as radio network controller (RNC), the IP metropolitan area network nodes or the IP backbone network nodes. The network topology between access nodes and aggregate nodes can be ring, chain or tree structure. Taking IP RAN for example, IP RAN usually uses a ring structure for network robustness, which is depicted in Figure 6-1.
+
+
+
+Q.3711(16)\_F6-1
+
+Figure 6-1 – Ring structure of BAN. The diagram shows a ring topology of nodes. On the left, a box labeled 'BTS/eNodeB/CE' is connected to an 'Access node'. This node is part of a ring of seven nodes: five 'Access nodes' and two 'Aggregate nodes'. The 'Aggregate nodes' are connected to a box on the right labeled 'RNC/network node'. Each node has three types of ports: 'Access port' (white circle), 'Aggregate port' (black circle), and 'Internal port' (circle with an 'X'). The 'Access ports' connect to user devices or other nodes, while 'Aggregate ports' connect to the RNC/network node. 'Internal ports' connect nodes to each other in the ring.
+
+**Figure 6-1 – Ring structure of BAN**
+
+In Figure 6-1, access ports belong to access nodes that connect user devices, and aggregate ports belong to aggregate nodes that connect other network nodes. Within access nodes and aggregate nodes, there are internal ports that connect to other access nodes or other aggregate nodes.
+
+There are a lot of network equipment and multiple protocols in BAN, and the network topology of BAN is complicated, so network deployment and configuration of BAN requires complex implementation and high maintenance costs. On the other hand, new value-added services and applications emerge rapidly, but it takes weeks or even months for networks to incorporate them.
+
+According to the above, SBAN aims to enable to separate the forwarding function and control function of network equipment, and to provide an open interface to applications and network managers.
+
+The functional entities of the SBAN model consist of forwarding devices, SDN controller, SDN application, southbound interface and northbound interface. Considering the large number of access
+
+nodes, there is a difference between SBAN and other SDN scenarios. It is difficult for the SDN controller in SBAN to link all forwarding devices directly, especially for all access nodes. So in SBAN, the SDN controller only links the aggregate nodes, and abstracts the aggregate nodes and the access nodes as a single node composed of access ports and aggregate ports, which is called an SBAN node and depicted in Figure 6-2.
+
+
+
+The diagram illustrates the SBAN model hierarchy. At the top is a box labeled 'SDN application'. Below it is a dashed horizontal line labeled 'Northbound interface'. A double-headed vertical arrow connects the 'SDN application' box to the 'Northbound interface' line. Below the 'Northbound interface' line is a box labeled 'SDN controller'. Below this box is another dashed horizontal line labeled 'Southbound interface'. A double-headed vertical arrow connects the 'SDN controller' box to the 'Southbound interface' line. Below the 'Southbound interface' line is a box labeled 'SBAN node'. This box has a vertical stack of five small circles on its left side and two small circles on its right side. Below the 'SBAN node' box is the text 'Q.3711(16)\_F6-2'.
+
+Diagram of the SBAN model showing the hierarchy: SDN application, SDN controller, and SBAN node.
+
+**Figure 6-2 – SBAN model**
+
+SBAN significantly contributes to reducing operating expense (OPEX) by 1) elimination of both constant maintenance and upgrades to the network equipment; 2) easy deployment of new services; and 3) improvement of the service provisioning.
+
+In SBAN, SBAN nodes perform the actions made by the SDN controller. The SDN controller provides SBAN capabilities to applications and controls SBAN nodes to meet SDN applications' requirements.
+
+The southbound interface is the interface between the SBAN nodes and the SDN controller, which carry messages from the SBAN nodes to the SDN controller (e.g., the link status message) and messages from the SDN controller to the SBAN nodes (e.g., the quality of service (QoS) policy).
+
+The northbound interface is the interface between the SDN controller and the SDN applications, which carries messages from the SDN controller to the SDN application (e.g., the network status message) and messages from the SDN application to the SDN controller (e.g., the network service query).
+
+# 7 Procedures
+
+## 7.1 SBAN node initialization
+
+First, the access nodes and the aggregate nodes are initialized without the SDN controller. The access nodes send their information to the aggregate nodes through the internal interface, such as: manufacturer identification, equipment models, media access control (MAC) address, access ports, internal ports. The aggregate nodes collect the information from the access nodes or the other aggregate nodes in the same network.
+
+Then the aggregate nodes negotiate with each other to elect the master aggregate node and the slave aggregate nodes. The master aggregate node communicates on behalf of the SBAN node with the SDN controller, as depicted in Figure 7-1.
+
+
+
+The diagram illustrates the network topology for SBAN node initialization. At the bottom center is a rectangular box labeled "SBAN node". It has five small circles (Access ports) on its left side and two solid black circles (Aggregate ports) on its right side. Above the SBAN node is a large green downward-pointing arrow. Above the arrow is a ring of nodes. The ring consists of six "Access node" ovals and two "Aggregate node" ovals. Each "Access node" is connected to the SBAN node via a dashed vertical line and has two small circles (Access ports) on its outer edge and two crossed circles (Internal ports) on its inner edge. Each "Aggregate node" is also connected to the SBAN node via a dashed vertical line and has one solid black circle (Aggregate port) on its outer edge and two crossed circles (Internal ports) on its inner edge. The nodes are interconnected in a ring by solid lines. A legend on the left side of the diagram defines the symbols: a small circle for "Access port", a solid black circle for "Aggregate port", a crossed circle for "Internal port", and a dashed line for "Internal interface". The text "Q.3711(16)\_F7-1" is located in the bottom right corner of the diagram area.
+
+Diagram of SBAN node initialization showing a ring of nodes connected to an SBAN node.
+
+**Figure 7-1 – SBAN node initialization**
+
+The master aggregate node has all the information about the access ports and the aggregate ports, and synchronizes with the slave aggregate nodes. When the master aggregate node fails, one of the slave aggregate nodes will become the new master aggregate node which represents the SBAN nodes to maintain communication with the SDN controller.
+
+The internal interface between the aggregate nodes and the access nodes is not included in this Recommendation.
+
+## 7.2 Registration
+
+After the SBAN node finishes its initialization, the master aggregate node is registered in the SDN controller as the representation of the SBAN node. In this process, the master aggregate node announces its information to the SDN controller, such as: address information, the slave aggregate nodes information. The SDN controller responds with the registration information, and allocates an SBAN node identification (ID) to the master aggregate node.
+
+The master aggregate node registers all the ports, including the access ports and the aggregate ports of the SBAN node, by using the SBAN node ID in the SDN controller.
+
+Meanwhile, the SDN application is registered in the SDN controller.
+
+## 7.3 Status query
+
+After the SBAN node and the SDN application are registered in the SDN controller, the SDN controller queries the their status. And the SDN application queries the topology and abilities of the SBAN nodes through the SDN controller.
+
+## 7.4 Service creation
+
+The SDN application initiates the network service of the SBAN nodes, and the SDN controller receives and translates the initiation. Then the SDN controller initiates the flows in the SBAN nodes.
+
+# 8 The signalling requirements of SBAN
+
+## 8.1 Overview of signalling requirements
+
+For controlling the SBAN network, the messages over the southbound interface and the northbound interface are classified by the following three categories.
+
+### Category 1: Registration
+
+- 1-1 (southbound) SBAN Node Register message and response message;
+- 1-2 (southbound) SBAN Node Port Register message and response message;
+- 1-3 (northbound) SDN application Register message and response message.
+
+### Category 2: Status query
+
+- 2-1 (southbound) SBAN Node Status Query message and response message;
+- 2-2 (southbound) SBAN Node Port Status Query message and response message;
+- 2-3 (southbound) SBAN Flow Query message and response message;
+- 2-4 (northbound) SDN application Status Query message and response message;
+- 2-5 (northbound) SBAN Network Query message and response message;
+- 2-6 (northbound) SBAN Network Service Query message and response message.
+
+### Category 3: Service creation
+
+- 3-1 (northbound) SBAN Network Service Initiation message and response message;
+- 3-2 (southbound) SBAN Flow Initiation message and response message.
+
+NOTE – No transport protocol for the signalling messages is specified here. No message content format is specified here either.
+
+The signalling messages may be extensible markup language (XML)-based messages over (or carried by) transmission control protocol (TCP), user datagram protocol (UDP), stream control transmission protocol (SCTP), transport layer security (TLS), etc. All of the messages consist of the message header and the message body.
+
+The message format is described in Figure 8-1 as follows:
+
+
+
+| | | | |
+|--------------|----------------|----------------|--------------|
+| Message type | Message length | Transaction ID | Message body |
+|--------------|----------------|----------------|--------------|
+
+Message header
+
+Q.3711(16)\_F8-1
+
+Diagram of message composition showing a header with four fields: Message type, Message length, Transaction ID, and Message body. The first three are grouped as the 'Message header'.
+
+**Figure 8-1 – Message composition**
+
+The message header field contains the following information:
+
+- 1) Message type: uniquely specifies the type of message;
+- 2) Message length: specifies the length of the message body;
+- 3) Message transaction ID: generated by the sender of the message. If there is a response message for the request message, the transaction IDs of the request and response messages are the same.
+
+The message body field contains the message contents.
+
+## 8.2 Signalling requirements for southbound interface
+
+#### 8.2.1 Signalling requirements for registration
+
+#### 8.2.1.1 SBAN Node Register message and response message
+
+The SBAN Node Register message is defined as SBAN-RE message.
+
+The SBAN-RE message, indicated by the message type in the message header field, is sent by the master aggregate node to be registered in the SDN controller.
+
+Message format:
+
+```
+< SBAN-RE-Message > ::= < Message header >
+ { SDN-controller-Address }
+ { Master-Aggregate-node-Address }
+ *{ Slave-Aggregate-node-Address }
+ *{ SBAN-node-Attribute }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) Master-Aggregate-node-Address uniquely specifies the master aggregate node;
+- 3) Slave-Aggregate-node-Address uniquely specifies the slave aggregate node. There may be multiple slave aggregate nodes;
+- 4) SBAN-node-Attribute is used for the aggregate node attributes. There may be multiple node attribute items.
+
+The response message to the SBAN-RE message is defined as SBAN-REP message.
+
+The SBAN-REP message, indicated by the message type in the message header field, is sent by the SDN controller to the master aggregate node in response to the SBAN-RE message.
+
+Message format:
+
+```
+< SBAN-REP-Message > ::= < Message Header >
+ { SDN-controller-Address }
+ { Master-Aggregate-node-Address }
+ { SBAN-node-ID }
+ { Result }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) Master-Aggregate-node-Address uniquely specifies the master aggregate node, which may be renamed as SBAN-node-Address when the master aggregate node represents SBAN node;
+- 3) SBAN-node-ID uniquely specifies the SBAN node, which is assigned by the SDN controller and is globally validated. After the SBAN node has registered successfully, this ID is used in subsequent messages, including the messages from the SDN controller to the SBAN node and from the SBAN node to the SDN controller;
+- 4) Result shows the handling results of registering the SBAN node in the SDN controller.
+
+##### 8.2.1.2 SBAN Node Port Register message and response message
+
+The port information of the SBAN Node Port Register message is defined as SBAN-PR message.
+
+The SBAN-PR message, indicated by the message type in the message header field, is sent by the master aggregate node to be registered in the SDN controller.
+
+Message format:
+
+```
+< SBAN-PR-Message > ::= < Message header >
+ { SDN-controller-Address }
+ { SBAN-node-Address }
+ { SBAN-node-ID }
+ *{ Port-ID }
+ *{ Port-Type-ID }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SBAN-node-Address uniquely specifies the SBAN node address, which may be equal to Master-Aggregate-node-Address;
+- 3) SBAN-node-ID uniquely specifies the SBAN node;
+- 4) Port-ID uniquely specifies the port of the SBAN node;
+- 5) Port-Type-ID uniquely specifies the type of the port, such as access port or aggregate port.
+
+The response message to the SBAN-PR message is defined as SBAN-PRP message.
+
+The SBAN-PRP message, indicated by the message type in the message header field, is sent by the SDN controller to the SBAN node, which is represented by the master aggregate node, in response to the SBAN-PR message.
+
+Message format:
+
+```
+< SBAN-PRP-Message > ::= < Message Header >
+ { SDN-controller-Address }
+ { SBAN-node-Address }
+ { SBAN-node-ID }
+ { Result }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SBAN-node-Address uniquely specifies the SBAN node address, which may be equal to Master-Aggregate-node-Address;
+- 3) SBAN-node-ID uniquely specifies the SBAN node;
+- 4) Result shows the handling results of registering the ports in the SDN controller.
+
+#### 8.2.2 Signalling requirements for status query
+
+##### 8.2.2.1 SBAN Node Status Query message and response message
+
+The SBAN node status request message is defined as SBAN-SQ message.
+
+The SBAN-SQ message, indicated by the message type in the message header field, is sent by the SDN controller to the master aggregate node in order to get the node status of the SBAN node.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SBAN-node-Address }
+ { SBAN-node-ID }
+ *{ Node-Type-ID }
+ *[ Node-Parameter-ID ]
+ *[ Auto-Node-ID ]
+ *[ Auto-Node-Parameter-ID ]
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SBAN-node-Address uniquely specifies the SBAN node address, which may be equal to Master-Aggregate-node-Address;
+- 3) SBAN-node-ID uniquely specifies the SBAN node;
+- 4) Node-Type-ID uniquely specifies the type of status enquired by the SDN controller;
+- 5) Node-Parameter-ID is optional, some of the status may need this ID to specify the intended status. One possible example would be the port number (or ID) of the designated port;
+- 6) Auto-Node-ID and Auto-Node-Parameter-ID are optional and have the same meaning with item 4 and item 5, respectively. The auto here means the aggregate node will automatically report the specified status to the SDN controller in case of changes.
+
+The SBAN node status response message is defined as SBAN-SQP message.
+
+The SBAN-SQP message, indicated by the message type in the message header field, is sent by the master aggregate node to the SDN controller in response to the SBAN-SQ message.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SBAN-node-Address }
+ { SBAN-node-ID }
+ *{ Node-Type-ID }
+ *[ Node-Parameter-ID ]
+ *{ Node-Status-Value }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SBAN-node-Address uniquely specifies the SBAN node address, which is equal to Master-Aggregate-node-Address;
+- 3) SBAN-node-ID uniquely specifies the SBAN node;
+- 4) Node-Type-ID uniquely specifies the type of status enquired by the SDN controller;
+- 5) Node-Parameter-ID is optional, some of the status may need this ID to specify the intended status. One possible example would be the port number (or ID) of the designated port;
+- 6) Node-Status-Value is used for describing the status of the SBAN node specified by Node-Type-ID.
+
+##### 8.2.2.2 SBAN Node Port Status Query message and response message
+
+The SBAN node status request message is defined as SBAN-PSQ message.
+
+The SBAN-PSQ message, indicated by the message type in the message header field, is sent by the SDN controller to the master aggregate node in order to get the port status of the SBAN node.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SBAN-node-Address }
+ { SBAN-node-ID }
+ { Port-ID }
+ *{ Port-Type-ID }
+ *[ Port-Parameter-ID ]
+ *[ Auto-Port-ID ]
+ *[ Auto-Port-Parameter-ID ]
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SBAN-node-Address uniquely specifies the SBAN node address, which may be equal to Master-Aggregate-node-Address;
+- 3) SBAN-node-ID uniquely specifies the SBAN node;
+- 4) Port-ID uniquely specifies the port of the SBAN node;
+- 5) Port-Type-ID uniquely specifies the type of the port enquired by the SDN controller;
+- 6) Port-Parameter-ID is optional, some of the status may need this ID to specify the intended status;
+- 7) Auto-Port-ID and Auto-Port-Parameter-ID are optional and have the same meaning with item 5 and item 6, respectively. The auto here means the SBAN node will automatically report the specified status to the SDN controller in case of changes.
+
+The SBAN node status response message is defined as SBAN-PSQP message.
+
+The SBAN-PSQP message, indicated by the message type in the message header field, is sent by the master aggregate node to the SDN controller in response to the SBAN-PSQ message.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SBAN-node-Address }
+ { SBAN-node-ID }
+ { Port-ID }
+ *{ Port-Type-ID }
+ *[ Port-Parameter-ID ]
+ *{ Port-Status-Value }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+
+- 2) `SBAN-node-Address` uniquely specifies the SBAN node address, which may be equal to `Master-Aggregate-node-Address`;
+- 3) `SBAN-node-ID` uniquely specifies the SBAN node;
+- 4) `Port-ID` uniquely specifies the port of the SBAN node;
+- 5) `Port-Type-ID` uniquely specifies the type of the port enquired by the SDN controller;
+- 6) `Port-Parameter-ID` is optional, some of the status may need this ID to specify the intended status;
+- 7) `Port-Status-Value` is used for describing the status of the port specified by `Port-ID`.
+
+##### 8.2.2.3 SBAN Flow Query message and response message
+
+The SBAN Flow Query message is defined as SBAN-FQ message.
+
+The SBAN-FQ message, indicated by the message type in the message header field, is sent by the SDN controller to the master aggregate node in order to get the flow information of the SBAN node.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SBAN-node-Address }
+ { SBAN-node-ID }
+ *{ Flow-ID }
+ *[ Flow-Parameter-ID ]
+ *[ Auto-Flow-ID ]
+ *[ Auto-Flow-Parameter-ID ]
+```
+
+Meanings and explanations:
+
+- 1) `SDN-controller-Address` uniquely specifies the SDN controller;
+- 2) `SBAN-node-Address` uniquely specifies the SBAN node address, which may be equal to `Master-Aggregate-node-Address`;
+- 3) `SBAN-node-ID` uniquely specifies the SBAN node;
+- 4) `Flow-ID` uniquely specifies the flow enquired by the SDN controller;
+- 5) `Flow-Parameter-ID` is optional, some of the status may need this ID to specify the intended status;
+- 6) `Auto-Flow-ID` and `Auto-Flow-Parameter-ID` are optional and have the same meaning with item 4 and item 5, respectively. The auto here means the aggregate node will automatically report the specified status to the SDN controller in case of changes.
+
+The SBAN Flow Query response message is defined as SBAN-FQP message.
+
+The SBAN-FQP message, indicated by the message type in the message header field, is sent by the master aggregate node to the SDN controller in response to the SBAN-FQ message.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SBAN-node-Address }
+ { SBAN-node-ID }
+ *{ Flow-ID }
+ *[ Flow-Parameter-ID ]
+ *{ Flow-Status-Value }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SBAN-node-Address uniquely specifies the SBAN node address, which may be equal to Master-Aggregate-node-Address;
+- 3) SBAN-node-ID uniquely specifies the SBAN node;
+- 4) Flow-ID uniquely specifies the flow enquired by the SDN controller;
+- 5) Flow-Parameter-ID is optional; some of the flow may need this ID to specify the intended status;
+- 6) Flow-Status-Value is used for describing the status of the flow specified by Flow-ID.
+
+#### 8.2.3 Signalling requirements for service creation
+
+##### 8.2.3.1 SBAN Flow Initiation message and response message
+
+The SBAN Flow Initiation message is defined as SBAN-FI message.
+
+The SBAN-FI message, indicated by the message type in the message header field, is sent by the SDN controller to the aggregate node in order to initiate the flow in the SBAN node.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SBAN-node-Address }
+ { SBAN-node-ID }
+ { Port-ID }
+ *{ Flow-ID }
+ *[ Flow-Parameter-ID ]
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SBAN-node-Address uniquely specifies the SBAN node address, which may be equal to Master-Aggregate-node-Address;
+- 3) SBAN-node-ID uniquely specifies the SBAN node;
+- 4) Port-ID uniquely specifies the port of the SBAN node;
+- 5) Flow-ID uniquely specifies the flow sent by the SDN controller;
+- 6) Flow-Parameter-ID is optional; some of the parameter status may need this ID to specify the intended flow status.
+
+The SBAN Flow Initiation response message is defined as SBAN-FIP message.
+
+The SBAN-FIP message, indicated by the message type in the message header field, is sent by the master aggregate node to the SDN controller in response to the SBAN-FI message.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SBAN-node-Address }
+ { SBAN-node-ID }
+ *{ Flow-ID }
+ *[ Flow-Parameter-ID ]
+ *{ Flow-Status-Value }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SBAN-node-Address uniquely specifies the SBAN node address, which is equal to Master-Aggregate-node-Address;
+- 3) SBAN-node-ID uniquely specifies the SBAN node;
+- 4) Flow-ID uniquely specifies the flow sent by the SDN controller;
+- 5) Flow-Parameter-ID is optional, some of the status may need this ID to specify the intended status;
+- 6) Flow-Status-Value is used for describing the status of the flow specified by Flow-ID.
+
+## 8.3 Signalling requirements for northbound interface
+
+#### 8.3.1 Signalling requirements for registration
+
+#### 8.3.1.1 SDN application Register message and response message
+
+The SDN application Register message is defined as APP-RE message.
+
+The APP-RE message, indicated by the message type in the message header field, is sent by the SDN application to be registered in the SDN controller.
+
+Message format:
+
+```
+< APP-RE-Message > ::= < Message header >
+ { SDN-controller-Address }
+ { SDN-application-Address }
+ { SDN-application-ID }
+ *{ SDN-application-Attribute-ID }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SDN-application-Address uniquely assigned to the SDN application;
+- 3) SDN-application-ID uniquely specifies the SDN application;
+- 4) SDN-application-Attribute-ID is used for the SDN application attributes. There may be multiple SDN application attribute items.
+
+The response message to the APP-RE message is defined APP-REP message.
+
+The APP-REP message, indicated by the message type in the message header field, is sent by the SDN controller to the SDN application in response to the APP-RE message.
+
+Message format:
+
+```
+< APP-REP-Message > ::= < Message Header >
+ { SDN-controller-Address }
+ { SDN-application-Address }
+ { SDN-application-ID }
+ { Result }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SDN-application-Address uniquely assigned to the SDN application;
+- 3) SDN-application-ID uniquely specifies the SDN application;
+- 4) Result shows the handling results of registering the SDN application in the SDN controller.
+
+#### 8.3.2 Signalling requirements for querying status
+
+##### 8.3.2.1 SDN application Status Query message and response message
+
+The SDN application Status Query message is defined as APP-ASQ message.
+
+The APP-ASQ message, indicated by the message type in the message header field, is sent by the SDN controller to the SDN application in order to get the status of the SDN application.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SDN-application-Address }
+ { SDN-application-ID }
+ *{ SDN-application-Attribute-ID }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SDN-application-Address uniquely assigned to the SDN application;
+- 3) SDN-application-ID uniquely specifies the SDN application;
+- 4) SDN-application-Attribute-ID is used for the SDN application attributes. There may be multiple SDN application attribute items.
+
+The SDN application Status Query response message is defined as APP-ASQP message.
+
+The APP-ASQP message, indicated by the message type in the message header field, is sent by the SDN application to the SDN controller in response to the APP-ASQ message.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SDN-application-Address }
+ { SDN-application-ID }
+ *{ SDN-application-Attribute-ID }
+ *{ SDN-application-Status-Value }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+
+- 2) SDN-application-Address uniquely assigned to the SDN application;
+- 3) SDN-application-ID uniquely specifies the SDN application;
+- 4) SDN-application-Attribute-ID is used for the SDN application attributes. There may be multiple SDN application attribute items;
+- 5) SDN-application-Status-Value is used for describing the status of the SDN application specified by SDN-application-Attribute-ID.
+
+##### 8.3.2.2 SBAN Network Query message and response message
+
+The SBAN network status request message is defined as SBAN-NQ message.
+
+The SBAN-NQ message, indicated by the message type in the message header field, is sent by the SDN application to the SDN controller in order to get the network status of the SBAN.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SDN-application-Address }
+ { SDN-application-ID }
+ *{ Network-ID }
+ *[ Auto-Network-ID ]
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SDN-application-Address uniquely assigned to the SDN application;
+- 3) SDN-application-ID uniquely specifies the SDN application;
+- 4) Network-ID uniquely specifies the network enquired by the SDN application;
+- 5) Auto-Network-ID is optional and has the same meaning with item 4. The auto here means the SDN controller will automatically report the specified network status in case of changes.
+
+The SBAN network status response message is defined as SBAN-NQP message.
+
+The SBAN-NQP message, indicated by the message type in the message header field, is sent by the SDN controller to the SDN application in response to the SBAN-NQ message.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SDN-application-Address }
+ { SDN-application-ID }
+ *{ Network-ID }
+ *{ Network-Status-Value }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SDN-application-Address uniquely assigned to the SDN application;
+- 3) SDN-application-ID uniquely specifies the SDN application;
+- 4) Network-ID uniquely specifies the network enquired by the SDN application;
+
+- 5) `Network-Status-Value` is used for describing the status of the SBAN network specified by `Network-Type-ID`.
+
+##### 8.3.2.3 SBAN Network Service Query message and response message
+
+The SBAN Network Service Query message is defined as SBAN-NSQ message.
+
+The SBAN-NSQ message, indicated by the message type in the message header field, is sent by the SDN application to the SDN controller in order to get the network service status of the SBAN.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SDN-application-Address }
+ { SDN-application-ID }
+ *{ Network-Service-ID }
+ *[ Auto-Services-ID ]
+```
+
+Meanings and explanations:
+
+- 1) `SDN-controller-Address` uniquely specifies the SDN controller;
+- 2) `SDN-application-Address` uniquely assigned to the SDN application;
+- 3) `SDN-application-ID` uniquely specifies the SDN application;
+- 4) `Network-Service-ID` uniquely specifies network service enquired by the SDN application;
+- 5) `Auto-Services-ID` is optional and has the same meaning with item 4. The auto here means the SDN controller will automatically report the specified service status in case of changes.
+
+The network service status response message is defined as SBAN-NSQP message.
+
+The SBAN-NSQP message, indicated by the message type in the message header field, is sent by the SDN controller to the SDN application in response to the SBAN-NSQ message.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SDN-application-Address }
+ { SDN-application-ID }
+ *{ Network-Service-ID }
+ *{ Services-Status-Value }
+```
+
+Meanings and explanations:
+
+- 1) `SDN-controller-Address` uniquely specifies the SDN controller;
+- 2) `SDN-application-Address` uniquely assigned to the SDN application;
+- 3) `SDN-application-ID` uniquely specifies the SDN application;
+- 4) `Network-Service-ID` uniquely specifies the network service enquired by the SDN application;
+- 5) `Services-Status-Value` is used for describing the service status specified by `Services-ID`.
+
+#### 8.3.3 Signalling requirements for service creation
+
+##### 8.3.3.1 SBAN Network Service Initiation message and response message
+
+The SBAN Network Service Initiation message is defined as SBAN-NSI message.
+
+The SBAN-NSI message, indicated by the message type in the message header field, is sent by the SDN application to the SDN controller in order to initiate the network service in the SBAN network.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SDN-application-Address }
+ { SDN-application-ID }
+ *{ Network-service-ID }
+ *[ Network-service-Parameter-ID ]
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SDN-application-Address uniquely assigned to the SDN application;
+- 3) SDN-application-ID uniquely specifies the SDN application;
+- 4) Network-service-ID uniquely specifies the network service sent by the SDN application;
+- 5) Network-service-Parameter-ID is optional; some of the parameter status may need this ID to specify the intended network service status.
+
+The SBAN Network Service Initiation response message is defined as SBAN-NSIP message.
+
+The SBAN-NSIP message, indicated by the message type in the message header field, is sent by the SDN controller to the SDN application in response to the SBAN-NSI message.
+
+Message format:
+
+```
+ ::= < Message Header >
+ { SDN-controller-Address }
+ { SDN-application-Address }
+ { SDN-application-ID }
+ *{ Network-service-ID }
+ *[ Network-service-Parameter-ID ]
+ *{ Network-service-Status-Value }
+```
+
+Meanings and explanations:
+
+- 1) SDN-controller-Address uniquely specifies the SDN controller;
+- 2) SDN-application-Address uniquely assigned to the SDN application;
+- 3) SDN-application-ID uniquely specifies the SDN application;
+- 4) Network-service-ID uniquely specifies the network service sent by the SDN application;
+- 5) Network-service-Parameter-ID is optional, some of the status may need this ID to specify the intended status;
+- 6) Network-service-Status-Value is used for describing the status of the network service specified by Network-service-ID.
+
+## **9 Security considerations**
+
+The SBAN includes the forwarding function (i.e., SBAN nodes), the control function (i.e., SDN controller) of network equipment and SDN applications, similar to the other SDN scenarios. SBAN follows the security consideration in [ITU-T Y.3300].
+
+## Appendix I
+
+## An example of SBAN
+
+(This appendix does not form an integral part of this Recommendation.)
+
+IP RAN is based on IP/multi-protocol label switching (MPLS) technology framework, through enhanced operation, administration and maintenance (OAM), protection, clock, network management and other capabilities, to meet the needs of wireless, access and other integrated services.
+
+Compared with other IP network, IP RAN has the following characteristics:
+
+- 1) IP RAN has only two kinds of topology: ring or chain structure. In most cases, it will be ring structure due to network robustness;
+- 2) An access node only belongs to a ring or a chain;
+- 3) One endpoint of the flow in the IP RAN is an access port, the other side is an aggregate port or an access port in the same ring or the same chain;
+- 4) Based on the ring structure, the work and backup path of each flow have only two options: clockwise or counter clockwise.
+
+Each ring or chain can be abstracted into a simple virtual switch which composed of access ports and aggregate ports, without considering the specific path.
+
+In software-defined IP RAN, each ring or chain can be abstracted into a virtual SDN switch composed of access ports and aggregate ports, which is called SBAN node and depicted in Figure I.1.
+
+
+
+The diagram illustrates two architectural views of a software-defined IP RAN. The top view shows a network topology:
+
+- An **SDN application** is at the top, connected to an **SDN controller** via a **Northbound interface** (dashed line).
+- The **SDN controller** connects to the network via a **Southbound interface** (dashed line).
+- The network consists of six **Access nodes** and two **Aggregate nodes** arranged in a ring-like structure.
+- A **BTS/eNodeB/CE** is connected to one **Access node**.
+- An **RNC/network node** is connected to the two **Aggregate nodes**.
+- Nodes are interconnected via **Internal ports** (crossed circles).
+
+An arrow points from the top network diagram down to a simplified representation:
+
+- An **SDN application** connects to an **SDN controller** via a **Northbound interface**.
+- The **SDN controller** connects to an **SBAN node** via a **Southbound interface**.
+- The **SBAN node** (large rectangle) represents the abstracted network.
+- A **BTS/eNodeB/CE** connects to the **SBAN node** via multiple **Access ports** (open circles).
+- An **RNC/network node** connects to the **SBAN node** via **Aggregate ports** (solid black circles).
+
+Legend:
+
+- Access port
+- Aggregate port
+- ⊗ Internal port
+
+Diagram illustrating the SBAN node in a software-defined IP RAN. The top part shows a mesh of access nodes connected to a BTS/eNodeB/CE and RNC/network node, managed by an SDN controller via Northbound and Southbound interfaces. The bottom part shows a simplified SBAN node architecture with similar connections.
+
+Q.3711(16)\_FI.1
+
+**Figure I.1 – SBAN node in software-defined IP RAN**
+
+## Bibliography
+
+- [b-ITU-T Q.1742.11] Recommendation ITU-T Q.1742.11 (2014), *IMT 2000 references (approved as of 31st December 2012) to ANSI-41-evolved core network with cdma2000 access network.*
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3740-201801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..072f073b6d42cbfa77c827c76c611f286177034a
--- /dev/null
+++ b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee72ddf991b7b1d543b2694b1687804845ecb97da77cc35e98e4c7dbf5ac163d
+size 4142
diff --git a/marked/Q/T-REC-Q.3740-201801-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03af21fbbdb03d427788d944aba056c97754d678
--- /dev/null
+++ b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a37f444db6e589480e4e52691894e26cfedc1670f99906c1120e8ee10eab61c4
+size 57270
diff --git a/marked/Q/T-REC-Q.3740-201801-I_PDF-E/55a593259a0749ce342bd5eac2ba6b58_img.jpg b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/55a593259a0749ce342bd5eac2ba6b58_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2cf8473b8553d029ad48ea77ccd212b07d592fe1
--- /dev/null
+++ b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/55a593259a0749ce342bd5eac2ba6b58_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e40c45d506ddddc86d291889abbaa95cb5792b9457cf0ef6b0ba4c81bc1fbe4
+size 16039
diff --git a/marked/Q/T-REC-Q.3740-201801-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..939fd4cded19479f15f14766846587667458d368
--- /dev/null
+++ b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63a11efb1db5b327b265c1008bc6bca20f5decee50dc0e46eafeb05b0f7c3750
+size 41043
diff --git a/marked/Q/T-REC-Q.3740-201801-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d960698b7bc93b63259dd4ae9bc7d361fab1b558
--- /dev/null
+++ b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6efc80a93dc37aa65b2d204a1486c602709a6755f59aa172078023df128c2507
+size 27889
diff --git a/marked/Q/T-REC-Q.3740-201801-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdc2263186385b9db13c64c510040769407d3f96
--- /dev/null
+++ b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7731a4b090b7fadb0990ad6d03d15dbf73aba5dc653965183d4df1d9331ba41
+size 45057
diff --git a/marked/Q/T-REC-Q.3740-201801-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..73be11abea2f046cc64e207d67d6db8b1afa76d3
--- /dev/null
+++ b/marked/Q/T-REC-Q.3740-201801-I_PDF-E/raw.md
@@ -0,0 +1,679 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3740**
+
+(01/2018)
+
+SERIES Q: SWITCHING AND SIGNALLING, AND
+ASSOCIATED MEASUREMENTS AND TESTS
+
+Signalling requirements and protocols for SDN – Network
+signalling and signalling requirements for services
+
+---
+
+**Signalling requirements for software-defined
+networking and network function virtualization-
+based central office services**
+
+Recommendation ITU-T Q.3740
+
+# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| Resource control protocols | Q.3710–Q.3739 |
+| Network signalling and signalling requirements for services | Q.3740–Q.3779 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T Q.3740
+
+## Signalling requirements for software-defined networking and network function virtualization-based central office services
+
+## Summary
+
+Recommendation ITU-T Q.3740 specifies the signalling requirements of an Si interface between a software-defined networking (SDN) controller and network function virtualization orchestration (NFVO) for SDN and central office (CO) services based on network function virtualization (NFV).
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3740 | 2018-01-13 | 11 | 11.1002/1000/13486 |
+
+## Keywords
+
+NFVO, SDN, Si interface, signalling requirements.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2018
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|-------------------------------------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and acronyms ..... | 1 |
+| 5 Convention..... | 3 |
+| 6 Background..... | 3 |
+| 7 Signalling requirements for Si..... | 4 |
+| 7.1 Overview of signalling requirements ..... | 4 |
+| 7.2 Signalling requirements for status request ..... | 5 |
+| 7.3 Signalling requirements for VNF creation ..... | 6 |
+| 7.4 Signalling requirements for resource scaling ..... | 7 |
+| 7.5 Signalling requirements for service chain creation ..... | 7 |
+| Appendix I – Signalling scenarios ..... | 9 |
+| I.1 Scenario 1: Traffic scheduling within the virtual broadband remote access service pool..... | 9 |
+| I.2 Scenario 2: Dynamic bandwidth adjustment..... | 10 |
+| I.3 Scenario 3: Service chain for enterprise..... | 11 |
+| Bibliography..... | 13 |
+
+
+
+## Recommendation ITU-T Q.3740
+
+## Signalling requirements for software-defined networking and network function virtualization-based central office services
+
+# 1 Scope
+
+This Recommendation specifies interface and signalling requirements of the Si interface between a software-defined networking (SDN) controller and network function virtualization orchestration (NFVO) based on the specific SDN-based central office (CO) services.
+
+NOTE – This Recommendation focuses on the signalling requirement of the Si interface. The candidate protocols for the Si interface are outside the scope of this Recommendation.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+[ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*.
+
+[ITU-T Y.3302] Recommendation ITU-T Y.3302 (2017), *Functional architecture of software-defined networking*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 service chain** [b-ITU-T Y.3512]: An ordered set of functions that is used to enforce differentiated traffic handling policies for a traffic flow.
+
+**3.1.2 software-defined networking** [ITU-T Y.3300]: A set of techniques that enables to directly program, orchestrate, control and manage network resources, which facilitates the design, delivery and operation of network services in a dynamic and scalable manner.
+
+**3.1.3 virtualized network function** [b-ITU-T Y.3321]: A network function whose functional software is decoupled from hardware, and runs on virtual machine(s).
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following term:
+
+**3.2.1 central office**: The telephone building that is the origin of the outside loop plant.
+
+NOTE – Based on the definition given in [b-ITU-T G.998.1].
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+AR Augmented Reality
+
+| | |
+|-----------|------------------------------------------------|
+| BRAS | Broadband Remote Access Service |
+| CO | Central Office |
+| CoA | Change of Authorization |
+| CGN | Carrier Grade Network address translation |
+| CPE | Customer Premises Equipment |
+| CPU | Central Processing Unit |
+| DPI | Deep Packet Inspection |
+| ID | Identifier |
+| IP | Internet Protocol |
+| MAN | Management |
+| MANO | Management and Orchestration |
+| NAT | Network Address Translation |
+| NFV | Network Function Virtualization |
+| NFVI | Network Function Virtualization Infrastructure |
+| NFVO | Network Function Virtualization Orchestration |
+| NFVRS-REP | NFV-related Resource Scaling Response |
+| NFVRS-REQ | NFV related Resource Scaling |
+| OLT | Optical Line Terminal |
+| PNF | Physical Network Function |
+| PPPoE | Point-to-Point Protocol over Ethernet |
+| QoS | Quality of Service |
+| SCC-REP | Service Chain Creation Response |
+| SCC-REQ | Service Chain Creation Request |
+| SDN | Software-Defined Networking |
+| SCTP | Stream Control Transmission Protocol |
+| TCP | Transmission Control Protocol |
+| TLS | Transport Layer Security |
+| UDP | User Datagram Protocol |
+| vBRAS | virtual Broadband Remote Access Service |
+| vCPE | virtual Customer Premises Equipment |
+| VIM | Virtualized Infrastructure Management |
+| VNF | Virtualized Network Function |
+| VNFC-REP | VNF Creation Response |
+| VNFC-REQ | VNF Creation Request |
+| VNFFG | VNF Forwarding Graph |
+| VNFL-REP | VNF List-related status Response |
+| VNFL-REQ | VNF List-related status Request |
+
+| | |
+|---------|-----------------------------------------|
+| VNFM | Virtualized Network Function Management |
+| VNF-REP | VNF-related status Response |
+| VNF-REQ | VNF-related status Request |
+| vOLT | virtual Optical Line Terminal |
+| VPN | Virtual Private Network |
+| VR | Virtual Reality |
+| XML | extensible Markup Language |
+
+# 5 Convention
+
+In the body of this Recommendation and its appendixes, the words shall, shall not, should, and may sometimes appear, in which case they are to be interpreted, respectively, as is required to, is prohibited from, is recommended, and can optionally. The appearance of such phrases or keywords in an appendix or in material explicitly marked as informative are to be interpreted as having no normative intent.
+
+{A}: indicates that the parameter A is mandatory;
+
+\*: indicates that the parameter may be multiple items.
+
+# 6 Background
+
+The CO is a common carrier switching centre in which trunks and loops are terminated and switched. Usually, it includes the access switches/optical line terminal (OLT) and network edge routers (BRAS), which cooperate to provide Internet access services to customers.
+
+The CO, which now is equipped with SDN and network function virtualization (NFV) technologies, gains the capabilities of developing diverse Internet access services much more easily and faster. Figure 6-1 shows the functional architecture of CO, which is aligned with the high-level architecture of SDN specified in [ITU-T Y.3300] and [ITU-T Y.3302], including the physical broadband remote access service (BRAS), customer premises equipment (CPE), OLT, virtual broadband remote access service (vBRAS), virtual customer premises equipment (vCPE), virtual optical line terminal (vOLT). The SDN controller can communicate with NFVO via the Si interface, and they can perform network function management and service orchestration.
+
+NOTE – The capabilities of NFVO are based on [b-ETSI GS NFV-MAN 001].
+
+
+
+The diagram illustrates the functional architecture of a central office. It is divided into two main vertical sections. The left section, labeled 'Central office', contains an 'SDN controller' at the top. Below it is a group of network functions arranged in two columns: physical functions (BRAS, CPE, OLT) and virtual functions (vBRAS, vCPE, vOLT). The right section contains three 'NFVO' (Network Function Virtualization Orchestrator) units stacked vertically, with a 'MANO' (Management and Orchestration) unit at the bottom. A red line labeled 'Si' connects the 'SDN controller' to the top 'NFVO' unit.
+
+Functional architecture of central office based on SDN and NFV technologies. The diagram shows a 'Central office' box containing an 'SDN controller' connected to a stack of physical and virtual network functions (BRAS, vBRAS, CPE, vCPE, OLT, vOLT). The SDN controller is also connected via a red line labeled 'Si' to a stack of NFVO units and a MANO unit.
+
+Q.3740(18)\_F6-1
+
+**Figure 6-1 – Functional architecture of central office based on SDN and NFV technologies**
+
+The Si interface is that between the SDN controller and the NFVO. A message can be exchanged between these two functional entities over this interface in support of the following interface requirements:
+
+- the SDN controller queries NFV-related resources from NFVO;
+
+- when the SDN controller receives a service request from a customer, it requests NFVO to create a specific virtualized network function (VNF), which does not exist;
+- when the existing VNF cannot satisfy the additional demands of the customer, the SDN controller requests NFVO to extend or shrink the virtual resources;
+- according to the specific service, which requires the combined VNFs in a certain sequence, the SDN controller requests NFVO to create the service chain.
+
+# 7 Signalling requirements for Si
+
+## 7.1 Overview of signalling requirements
+
+The messages over the Si interface are classified into the following four categories.
+
+NOTE 1 – NFV-related resources include VNF, service chain VNFG and network function virtualization infrastructure (NFVI), as well as resources such as central processing unit (CPU), memory and sessions.
+
+### Category 1: Status request
+
+- VNF and VNF list request message and response message.
+
+### Category 2: VNF creation
+
+- VNF creation message and response message.
+
+### Category 3: Resource scaling
+
+- NFV-related resource extension/shrink message and response message.
+
+### Category 4: Service chain creation
+
+- Service chain creation message and response message.
+
+NOTE 2 – No transport protocol for the signalling messages is specified here. No message content format is specified here either.
+
+The signalling messages may be XML-based messages over (or carried by) the transmission control protocol (TCP), user datagram protocol (UDP), stream control transmission protocol (SCTP), transport layer security (TLS), etc. All of the messages consist of the message header and the message body.
+
+The message format is described in Figure 7-1.
+
+
+
+| | | | |
+|--------------|----------------|----------------|--------------|
+| Message type | Message length | Transaction ID | Message body |
+|--------------|----------------|----------------|--------------|
+
+Message header
+
+Q.3740(18)\_F7-1
+
+A bracket under the first three columns of the table, labeled 'Message header'.
+
+**Figure 7-1 – Message composition**
+
+The message header field contains the following information.
+
+- Message type: uniquely specifies the type of the message.
+- Message length: specifies the length of the message body.
+- Message transaction identifier (ID): generated by the sender of the message. If there is a response message for the request message, the transaction IDs of the request and response messages are the same.
+
+The message body field contains the message contents.
+
+## 7.2 Signalling requirements for status request
+
+### 7.2.1 VNF list request message and response message
+
+The VNF list-related status request (VNFL-REQ) message, indicated by the message type in the message header field, is sent by the SDN controller to the NFVO in order to get the VNF list resources.
+
+Message format:
+
+| |
+|-------------------------------------------|
+| ::= < Message Header > |
+|-------------------------------------------|
+
+The VNF list response (VNFL-REP) message, indicated by the message type in the message header field, is sent by the NFVO to the SDN controller in response to the VNFL-REQ message.
+
+Message format:
+
+| |
+|------------------------------------------------------------------------------------|
+| ::= < Message Header >
* {VNF-Address}
* {VNF-Parameters} |
+|------------------------------------------------------------------------------------|
+
+VNF-Address uniquely specifies a VNF.
+
+VNF-Parameters mean one or multiple parameters of the VNF mentioned in the foregoing. It includes, but not limited to:
+
+- Available IPv4/IPv6 session uniquely specifies the available number of IPv4/IPv6 sessions;
+- Available Service Specific Session uniquely specifies the available number of service specific sessions;
+- Available CPU uniquely specifies the available CPU resources;
+- Available Memory uniquely specifies the available memory resources;
+- Available Bandwidth uniquely specifies the available bandwidth resources.
+
+### 7.2.2 VNF request message and response message
+
+The VNF-related status request (VNF-REQ) message, indicated by the message type in the message header field, is sent by the SDN controller to the NFVO in order to get the status of a specific VNF.
+
+Message format:
+
+| |
+|-----------------------------------------------------------|
+| ::= < Message Header >
{VNF-Address} |
+|-----------------------------------------------------------|
+
+Meanings and explanations:
+
+VNF-Address uniquely specifies a VNF.
+
+The VNF-related status response (VNF-REP) message, indicated by the message type in the message header field, is sent by the NFVO to the SDN controller in response to the VNF-REQ message.
+
+Message format:
+
+| |
+|---------------------------------------------------------------------------------|
+| ::= < Message Header >
{VNF-Address}
* {VNF-Parameters} |
+|---------------------------------------------------------------------------------|
+
+VNF-Address uniquely specifies the VNF.
+
+VNF-Parameters means one or multiple parameters of VNF. It includes, but is not limited to:
+
+- Available IPv4/IPv6 session uniquely specifies the available number of IPv4/IPv6 sessions;
+
+- Available service specific session uniquely specifies the available number of service specific sessions;
+- Available CPU uniquely specifies the available CPU resources;
+- Available Memory uniquely specifies the available memory resources
+- Available Bandwidth uniquely specifies the available bandwidth resources.
+
+## 7.3 Signalling requirements for VNF creation
+
+The VNF creation request (VNFC-REQ) message, indicated by the message type in the message header field, is sent by the SDN controller to the NFVO.
+
+Message format:
+
+| |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <VNFC-REQ -Message> ::= < Message Header > { VNF-name } * { Required-resource-parameters } |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Meanings and explanations:
+
+VNF-name uniquely specifies the VNF.
+
+Required-resource-parameters uniquely specifies required resource parameters for the specific VNF, it indicates but not limited to:
+
+- Required CPU uniquely specifies the CPU resources the VNF needed;
+- Required Memory uniquely specifies the memory resources the VNF needed;
+- Required Bandwidth uniquely specifies the bandwidth resources the VNF needed;
+- Required Service Specific Resources uniquely specify resources needed for the VNF.
+
+NOTE – For example, for the carrier grade network address translation (CGN) VNF, the specific resources needed are IPv4 and IPv6 session resources and IPv4 and IPv6 addresses.
+
+The VNF creation response (VNFC-REP) message, indicated by the message type in the message header field, is sent by the NFVO to the SDN controller.
+
+Message format:
+
+| |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <VNFC-REP-Message> ::= < Message Header > { VNF-name } {Instantiated-resources} |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Meanings and explanations:
+
+VNF-name uniquely specifies the name of VNF that is created.
+
+Instantiated-resources uniquely specifies the VNF resources instantiated for the VNF, it indicates but is not limited to:
+
+- Instantiated CPU uniquely specifies the CPU resources the VNF needs;
+- Instantiated Memory uniquely specifies the memory resources the VNF needs;
+- Instantiated Bandwidth uniquely specifies the bandwidth resources the VNF needs;
+- Instantiated Service Specific Resources uniquely specify the resources needed for certain VNFs.
+
+## 7.4 Signalling requirements for resource scaling
+
+The NFV-related resource scaling request (NFVRS-REQ) message, indicated by the message type in the message header field, is sent by the SDN controller to the NFVO.
+
+Message format:
+
+| |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <NFVRS-REQ-Message> ::= < Message Header > *{ VNF-address} *{required-resources} |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Meanings and explanations:
+
+NOTE – All the parameter values of this message could be positive or negative numbers. A positive number indicates resource extension; a negative number indicates resource shrink.
+
+VNF address uniquely specifies the required VNF.
+
+Required resources includes but is not limited to:
+
+- a) Required CPU resources uniquely specify the required CPU resource for scaling;
+- b) Required Memory resources uniquely specify the required memory for scaling;
+- c) Required Bandwidth uniquely specifies the required bandwidth for scaling;
+- d) Required Service specifies the service specific resources; it indicates but is not limited to:
+ - i) Required IPv4/IPv6\_session uniquely specifies the required IPv4/IPv6 session for scaling,
+ - ii) Required IPv4/IPv6 addresses uniquely specifies the required IPv4/IPv6 address for scaling.
+
+The NFV-related resource scaling response (NFVRS-REP) message, indicated by the message type in the message header field, is sent by the NFVO to the SDN controller in response to the NFVRS-REQ message.
+
+Message format:
+
+| |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <NFVRS-REP-Message> ::= < Message Header > *{ VNF-address } *{scaled-resources} |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Meanings and explanations:
+
+VNF-address uniquely specifies the VNF that needs resource scaling.
+
+Scaled-resources uniquely specifies the scaled resources, it indicates but is not limited to:
+
+Scaled CPU uniquely specifies the scaled CPU resources for the VNF:
+
+- a) Scaled Memory uniquely specifies the scaled memory for the VNF;
+- b) Scaled Bandwidth uniquely specifies the scaled bandwidth for the VNF;
+- c) Scaled Service specific resources, indicates but is not limited to:
+ - i) Scaled IPv4/IPv6\_session uniquely specifies the scaled IPv4/IPv6 session for scaling,
+ - ii) Scaled IPv4/IPv6 addresses uniquely specifies the scaled IPv4/IPv6 address for scaling.
+
+## 7.5 Signalling requirements for service chain creation
+
+The service chain creation request (SCC-REQ) message, indicated by the message type in the message header field, is sent by the SDN controller to NFVO in order to create the service chain.
+
+When the SDN controller receives a service request from a customer, the SDN controller sends this message to NFVO to request NFVO to create a service chain.
+
+Message format:
+
+| |
+|---------------------------------------------------------------------------------------------------|
+| ::= < Message Header >
{Service-Chain-ID}
{Required-VNF-forwarding-graph} |
+|---------------------------------------------------------------------------------------------------|
+
+Meanings and explanations:
+
+Service-Chain-ID uniquely specifies the identification of service chain in CO.
+
+Required-VNF-forwarding-graph (VNFFG) specifies the VNFFG required by the specific service chain.
+
+The service chain creation response (SCC-REP) message, indicated by the message type in the message header field, is sent by the NFVO to the SDN controller.
+
+Message format:
+
+| |
+|-------------------------------------------------------------------------------------------------------|
+| ::= < Message Header >
{Service-Chain-ID}
{Instantiated-VNF-forwarding-graph} |
+|-------------------------------------------------------------------------------------------------------|
+
+Service-Chain-ID uniquely specifies the identification of service chain in CO.
+
+Instantiated VNFFG specifies the VNFFG instantiated for specific services.
+
+## Appendix I
+
+### Signalling scenarios
+
+(This appendix does not form an integral part of this Recommendation.)
+
+NOTE – This appendix describes the typical scenarios in the CO and indicates specific information exchanged between an SDN controller and NFVO. The physical device and virtual device coexist in the CO and the SDN controller should consider them as a whole.
+
+### I.1 Scenario 1: Traffic scheduling within the virtual broadband remote access service pool
+
+The vBRAS pool can meet the real-time traffic demand by extending and shrinking the VNF and NFVI resources of vBRAS flexibly. One of the main targets of the vBRAS pool service is traffic scheduling, which means distributing the traffic among the vBRASs within the pool. Figure I.1 illustrates the signalling scenario of the point-to-point protocol over Ethernet (PPPoE) requests traffic scheduling within the vBRAS pool.
+
+
+
+```
+graph TD
+ SP[Service portal] -- Restful --> SDN[SDN controller]
+ SDN -- Si --> NFVO[NFVO]
+ NFVO --- VNFM[VNFM]
+ VNFM --- VIM[VIM]
+ SDN --> BRAS1[BRAS 1]
+ SDN --> vBRAS2[vBRAS 2]
+ SDN --> vBRAS3[vBRAS 3]
+ subgraph vBRAS_pool [vBRAS pool]
+ vBRAS2
+ vBRAS3
+ end
+ BRAS1 --- vBRAS2
+ BRAS1 --- vBRAS3
+ SDN --> SW[SW]
+ SW --> C[Customer]
+ C --> SP
+```
+
+Diagram illustrating the signalling scenario for traffic scheduling within the vBRAS pool. A Service portal connects to an SDN controller via a Restful interface. The SDN controller connects to a MANO (NFVO, VNFM, VIM) via an Si interface. The SDN controller also connects to a vBRAS pool (containing BRAS 1, vBRAS 2, and vBRAS 3) and a SW (Switch). The SW connects to a Customer. The diagram shows the flow of traffic scheduling requests from the Customer through the SW, vBRAS pool, and SDN controller to the Service portal.
+
+**Figure I.1 – Point-to-point protocol over Ethernet requests traffic scheduling within the virtual broadband remote access service pool**
+
+The following stepwise approach illustrates the roles and responsibilities of the management and orchestration (MANO) and SDN controller entities.
+
+- 1) Customer sends a network access request to the SDN controller through the service portal.
+- 2) When the SDN controller receives the access request, it checks the resource statistics based on the customer ID and finds whether there are PPPoE-related resources available in the related BRAS or vBRAS to meet the requirement.
+- 3) If one of the BRAS or vBRAS is available, the SDN controller sends the customer request to vBRAS1.
+- 4) If no BRAS or vBRAS in the pool is available, the SDN controller will send the request to the NFVO.
+- 5) NFVO interfaces with the virtualized network function management (VNFM) to configure and instantiate the vBRASs.
+- 6) NFVO interconnects with the SDN controller to deliver the certain vBRAS parameters.
+- 7) The SDN controller activates the vBRAS and goes to step 3).
+
+The information transferred from the SDN controller to NFVO is:
+
+- the required bandwidth;
+- the required number of PPPoE session;
+- the required number of Internet protocol (IP) address.
+
+The information delivered from NFVO to the SDN controller when received the request includes:
+
+- the available PPPoE sessions in specific vBRAS;
+- the available public IP address and related ports scope in the specific vBRAS;
+- the available bandwidth of each virtual interface and the remaining quality of service (QoS) queue in the specific vBRAS;
+- the information of the instantiated vBRASs, e.g., vBRAS addresses or names.
+
+BRAS/vBRAS are responsible for the control and management of customer access to the Internet. With increases in customer terminal numbers and traffic on the network, the carrier network is designed to have higher service capability.
+
+### I.2 Scenario 2: Dynamic bandwidth adjustment
+
+This service is traditionally supported by a platform that has several shortcomings for service provision. The problem happens on change of authorization (CoA), the interface between platform and BRAS. It is only capable of carrying service name and leaves no room for more service parameters. In this case, service parameters need to be pre-configured in every BRAS in management (MAN). If the service has any change, the related service parameters have to be rewritten for every BRAS and create a lot of work for network administrators.
+
+The SDN-based CO can utilize a programmable interface to convey flexible service parameters for customers in real time. Figure I.2 illustrates the detailed scenario.
+
+
+
+The diagram illustrates the dynamic bandwidth adjustment service scenario. At the top, a 'Service portal' is connected to an 'SDN controller' via a 'Restful' interface. The 'SDN controller' is a central component containing four sub-modules: 'Identification', 'Policy making', 'Resource counting', and 'Policy provisioning'. Below the SDN controller, there are two boxes labeled 'BRAS' and 'vBRAS', which are connected to the SDN controller via 'Openflow, Netconf,...' interfaces. Below these boxes, the text 'PPPOE/IPOE' indicates the connection to a 'Customer' box at the bottom. To the right of the SDN controller, a red line labeled 'Si' connects it to a 'MANO' stack. The 'MANO' stack is a vertical box containing three sub-components: 'NFVO', 'VNFM', and 'VIM'. On the left side, a blue line labeled 'Http/Https' connects the 'Service portal' directly to the 'Customer' box.
+
+Diagram of the dynamic bandwidth adjustment service scenario. A Service portal connects to an SDN controller via a Restful interface. The SDN controller contains modules for Identification, Policy making, Resource counting, and Policy provisioning. It connects to BRAS and vBRAS units via Openflow, Netconf, etc. The BRAS and vBRAS units connect to a Customer via PPPoE/IPOE. The SDN controller also connects to a MANO stack (NFVO, VNFM, VIM) via an Si interface. The Service portal also connects to the Customer via Http/Https.
+
+**Figure I.2 – Dynamic bandwidth adjustment service scenario**
+
+The following stepwise approach illustrates the roles and responsibilities of the MANO and SDN controller entities.
+
+- a) Customer requests bandwidth adjustment service via a web portal. This request carries the bandwidth and timeframe parameters.
+
+- b) When the SDN controller receives the request, it checks the resource statistics based on the customer ID and finds whether there are available bandwidth resources in the BRAS or vBRAS for the customer to access the Internet to meet the requirement.
+ - i) If there is bandwidth available in this BRAS or vBRAS, the SDN controller reallocates the bandwidth to the specific customer ID.
+ - ii) If not, the SDN controller sends the request to the NFVO to allocate more bandwidth resources.
+- c) NFVO sends the parameter of the newly assigned bandwidth to the SDN controller.
+
+The information transferred from the SDN controller to NFVO is:
+
+- bandwidth;
+- timeframe;
+- customer ID;
+- interface ID.
+
+The information delivered from NFVO to SDN controller includes the following.
+
+The bandwidth resources according to specific timeframe, customer ID and interface ID.
+
+With the development of 4K (high-definition TV), augmented reality (AR) and virtual reality (VR) services, the bandwidth demand of users is increasing and varies over time. Bandwidth utilization will improve by adopting a dynamic bandwidth adjustment strategy.
+
+### I.3 Scenario 3: Service chain for enterprise
+
+
+
+Diagram of the service chain scenario for enterprises. It shows three enterprises (Enterprise 1, 2, and 3) connected to a Service portal, which is connected via Restful to an SDN controller. The SDN controller is connected via Si to a MANO stack (NFVO, VNFM, VIM). The SDN controller manages a vPOP containing five service functions: DPI, FW, NAT, Cache, and VPN, all based on NFV. Arrows show traffic flow from the enterprises through the vPOP functions. Enterprise 1 (yellow) uses DPI, NAT, and VPN. Enterprise 2 (red) uses DPI, FW, and NAT. Enterprise 3 (green) uses DPI, FW, NAT, and Cache. The diagram is labeled Q.3740(18)\_FI.3.
+
+**Figure I.3 – The service chain scenario for enterprises**
+
+As shown in Figure I.3, besides vBRAS, there can be several virtualized value-added service functions in the CO, e.g., deep packet inspection (DPI), network address translation (NAT), cache and firewall.
+
+These functions serve a series of enterprise users. One function can be used by one or more enterprise users, and each enterprise user can select one or more functions according its service requirement. As shown in Figure I.3, there are three service chains, each chain serves an enterprise user and consists of a series of ordered functions.
+
+- Enterprise 1: Pays close attention to intranet service, it needs DPI, NAT and virtual private network (VPN) functions.
+- Enterprise 2: Pays close attention to Internet service, it needs DPI, firewall and NAT functions.
+
+- Enterprise 3: All services are relevant, it needs DPI, NAT, firewall, cache and VPN functionality.
+
+The following stepwise approach illustrates the roles and responsibilities of the MANO and SDN controller entities.
+
+- The enterprise customer requests service chaining service via a web portal.
+- This request triggers the SDN controller to make a list of all resources needed to deliver the service. The SDN controller also determines whether the request will be accepted, based on the real-time resource statistic [e.g. topologies and inventory of VNFs and physical network functions (PNFs)].
+- When the SDN controller receives the request, it checks the resource statistics based on the customer ID and finds whether there are available function resources (VNFs or PNFs) to meet the requirement.
+ - If there are function resources available in the CO, the SDN controller orchestrates and activates them to the specific customer ID.
+ - If not, there are two kinds of situation.
+ - Within those functions, some of them are PNFs and others are VNFs. The SDN controller takes charge of orchestration and service functions allocation among PNFs and VNFs. It also activates and connects the VNFs instance by MANO.
+ - All the functions are VNFs, NFVO takes charge of orchestration. The SDN controller plays the role of activating the VNFs and connecting them.
+
+The information transferred from the SDN controller to NFVO is:
+
+- service chain ID;
+- required VNFs and their related virtualized resources.
+
+The information delivered from NFVO to SDN controller includes:
+
+- service chain ID;
+- forwarding graph;
+- VNF information: CPU, storage, and session capacity;
+- information about the instantiated VNFs, e.g. VNF address.
+
+By deploying vCPE and value-added services in the CO, customers can select the services needed in the service chain to improve service allocation capability for their enterprises.
+
+# Bibliography
+
+- [b-ITU-T G.998.1] Recommendation ITU-T G.998.1 (2005), *ATM-based multi-pair bonding*.
+- [b-ITU-T Y.3321] Recommendation ITU-T Y.3321 (2015), *Requirements and capability framework for NICE implementation making use of software-defined networking technologies*.
+- [b-ITU-T Y.3512] Recommendation ITU-T Y.3512 (2014), *Cloud computing – Functional requirements of Network as a Service*.
+- [b-ETSI GS NFV-MAN 001] ETSI GS NFV-MAN 001 V1.1.1 (2014), *Network functions virtualisation (NFV); Management and orchestration*.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dad02182b30e94f721c7f50726f60641c96df521
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45bf920a7798c0111eed0c87f3f277105f8935167814eaedd42f96a3f983bba0
+size 4024
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..247bc720e9a3282acbe5beeb20ab2c68cb0dcf4e
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ea75c17c525612ac8d9a5e7315ca1cee305da31b930381e31248dd8d7db780f2
+size 41055
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/22869a12e33113937504835078800f31_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/22869a12e33113937504835078800f31_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..063f765e3b96d2681b25d2e350db2ada141c8df9
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/22869a12e33113937504835078800f31_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91685e783f67d769188c95f2bba6d59a4e309be6200b8fcc74899adb39b6ecfd
+size 41291
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e952bd8d82afda8fb89f810643514f9dd31a7ba8
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:43bdcbc57de65471f52a8346727433f8e487733f0d77ccc1dcd063c40c49a1b7
+size 36867
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0939d7bba675a963e227ed038cf0761206eb32ea
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06dbd675fb6569a31f0dc9294ad2c9423107723478cfc7f4389e372c5ee01458
+size 44008
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce45b43a911de9ebd7b46e8751add1984ced1da6
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f4e4f63843901ab86973447ab03df1ba6fe42565bcf8520b109980b8a43f5b1
+size 37330
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/8a595fb12673444b0647911603264350_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/8a595fb12673444b0647911603264350_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b62b91f8c46e920c00d1b9971885af9a1ea10dad
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/8a595fb12673444b0647911603264350_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04d27efd183fe581a5a8ca060a7ea67255784cd80269dd19f0d9bd8c35615d9f
+size 24885
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7dc3a9f00ce0369f2341ce049bf0f66cf2422343
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f41c01037a44fbb74934ad4af49028325acaeea498da3ec7a73fa19fd3f8367
+size 36578
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/8e96238d63f620a9dd3429e36158b307_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/8e96238d63f620a9dd3429e36158b307_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d295a4ed61b809484044858ac518c5fce5c62d00
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/8e96238d63f620a9dd3429e36158b307_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8140f9c06ad0649413af64bfcbe4600f2f7bdf2c65123b44f675011bdfd6a5d7
+size 25210
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/a13a4831ce80e432d758981c17bdcd24_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/a13a4831ce80e432d758981c17bdcd24_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2e52136c73e3a2fc5266889c7b7a543fb471886e
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/a13a4831ce80e432d758981c17bdcd24_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c882227a3b3f5ce7f4973c245e9c7c419cef46c06b139a51b2f3eacde709b9dd
+size 31128
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dcd14e32bf48dc50867ddcb19bdccb0f53201d87
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f02ffe2e6e8eba06374cf56b092f8160c616a17a955974574e4837042132f82c
+size 102521
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/a83b5d50b3b9c79d6564af4b6e4415e6_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/a83b5d50b3b9c79d6564af4b6e4415e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..33cbb73d9bcb73659eb2a24ba6ab78e4cd6e12a5
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/a83b5d50b3b9c79d6564af4b6e4415e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:beb265817c374ecf1b7cb51f51c5a18749168e112a978085748083d83716c79c
+size 23869
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e9f6dd14d5ce28ccd995eb6b6d1099fde9b58e97
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7dbc9fa72492d1657f6963b0e156430434d5ceb3b44b2d26ff53e498d298f605
+size 43584
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/c59cf0104cb29e0812e732e14fed5115_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/c59cf0104cb29e0812e732e14fed5115_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee634ee4fc4479bae13dabe12cc725e1c488dc7c
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/c59cf0104cb29e0812e732e14fed5115_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b532d3a29d07d8fb96efa7374fabf3a4190b24d86d7826a465938c278c09a0a1
+size 21899
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7cb10ce7a3e524f2d862cbc1a4f66c0ad5ebd453
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e450b2395015afc810c59026ef90fd8a4d2653c3e339a94949ba946d34b26096
+size 30868
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d663333e54bff03fbb3e1f8727623503da61836
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e005c727ac7bb7d012e2fe630d217032e0ab817dd38890b655e5f482accb182
+size 51140
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e1a52e43edb91904a7d76090591d64dc8d04e25b
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e77d9e3719ebf46f42fd00381d1d2d278c00c54cbb9f251f4d978b2b5ba95ab4
+size 41977
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3e7c1535f52b9c68365f9eacc1eced3ee4b9d185
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c81fe54c6867df3d6bff02e174a2675985047e36a5ab54c14807e42e46bf26e0
+size 38802
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e05cae40b7f016af83324134d431f499835f554
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf67f878a7ed881b250d6c9196fcbb9264e8ebfd6aacd88295258ac0a7e8b03e
+size 49329
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e8fffbff4a142f1b3a1f57370438e624_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e8fffbff4a142f1b3a1f57370438e624_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcaffd5b87226c1a2f3b8a9bef218913aa0bed39
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/e8fffbff4a142f1b3a1f57370438e624_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a702ed2fb44c64657bc38e31eb2091b42f983425426557bf3ede91e9c768ad9a
+size 24444
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/ea0e870e2f3087f34e4061d806b0356e_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/ea0e870e2f3087f34e4061d806b0356e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1b50af14aa9fa880b0cd1476822c3999c18fd32d
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/ea0e870e2f3087f34e4061d806b0356e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a9c3420645a1ca067c908ee686fc273f601cf0ecf52a6ee6dae6c7dfbbec6245
+size 44750
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f188844495b2308c545dc855574b807ed912a8ad
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf21c353b5e07b5c3be21a483a1b41ded585813265cdbedc3421512d3243fe26
+size 37140
diff --git a/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/ff70f9afd1d880ab8f9098ae28ebec79_img.jpg b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/ff70f9afd1d880ab8f9098ae28ebec79_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..14160c5852535652000320c70fc52dc0814df92d
--- /dev/null
+++ b/marked/Q/T-REC-Q.3906.1-201010-I_PDF-E/ff70f9afd1d880ab8f9098ae28ebec79_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61c5fd29bda6a7c6964c57cff06272c03b0851178ebdc561944bfc0fc9cafcb7
+size 29590
diff --git a/marked/Q/T-REC-Q.3910-201006-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3910-201006-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3a21ba4cf20aa6fc731880db81e3e60bbd6d8668
--- /dev/null
+++ b/marked/Q/T-REC-Q.3910-201006-I_PDF-E/raw.md
@@ -0,0 +1,998 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3910**
+
+(06/2010)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for the NGN –
+Testing for NGN networks
+
+# --- Parameters for monitoring NGN protocols
+
+Recommendation ITU-T Q.3910
+
+
+
+The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, symbolizing global connectivity and telecommunications. The text "International Telecommunication Union" is written in blue to the right of the globe.
+
+ITU logo
+
+## ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3649 |
+| NGN applications | Q.3700–Q.3849 |
+| Testing for NGN networks | Q.3900–Q.3999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# Recommendation ITU-T Q.3910
+
+# Parameters for monitoring NGN protocols
+
+# Summary
+
+Recommendation ITU-T Q.3910 defines the protocols for measuring and monitoring PSTN/ISDN emulation service (PES) and IP multimedia subsystem (IMS) solutions, including real-time transfer protocol/real-time transfer control protocol (RTP/RTCP), session initiation protocol (SIP), H.248/media gateway control protocol (H.248/MEGACO), signalling transport (SIGTRAN) and bearer independent call control (BICC). How to monitor these parameters is out of scope of this Recommendation.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0 | ITU-T Q.3910 | 2010-06-13 | 11 |
+
+## Keywords
+
+Monitoring parameters, NGN protocols.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+# INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2010
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|------|-------------------------------------------------------------|----|
+| 1 | Scope ..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 1 |
+| 4 | Abbreviations..... | 1 |
+| 5 | Conventions ..... | 3 |
+| 6 | Reference model ..... | 4 |
+| 7 | RTP/RTCP monitoring and measurement parameters ..... | 5 |
+| 7.1 | General ..... | 5 |
+| 7.2 | Parameters for RTP/RTCP node status ..... | 5 |
+| 7.3 | Parameters for RTP/RTCP fault and quality ..... | 5 |
+| 7.4 | Parameters for RTP/RTCP availability ..... | 6 |
+| 7.5 | Parameters for bandwidth utilization..... | 6 |
+| 8 | SIP monitoring and measurements parameters..... | 6 |
+| 8.1 | General ..... | 6 |
+| 8.2 | Parameters for SIP node status ..... | 7 |
+| 8.3 | Parameters for SIP availability ..... | 7 |
+| 8.4 | Parameters for SIP signalling utilization..... | 7 |
+| 8.5 | Parameters for SIP fault and quality..... | 9 |
+| 9 | H.248/MEGACO monitoring and measurement parameters..... | 9 |
+| 9.1 | General ..... | 9 |
+| 9.2 | Parameters for H.248/MEGACO node status ..... | 10 |
+| 9.3 | Parameters for H.248/MEGACO availability ..... | 10 |
+| 9.4 | Parameters for H.248/MEGACO utilization ..... | 10 |
+| 9.5 | Parameters for the quality of the H.248/MEGACO service..... | 11 |
+| 10 | SIGTRAN monitoring and measurement parameters ..... | 11 |
+| 10.1 | General ..... | 11 |
+| 10.2 | Parameters for SIGTRAN node status ..... | 12 |
+| 10.3 | Parameters for SCTP association availability ..... | 12 |
+| 10.4 | Parameters for SIGTRAN utilization ..... | 13 |
+| 10.5 | Parameters for SIGTRAN fault ..... | 14 |
+| 11 | BICC monitoring and measurement parameters..... | 15 |
+| 11.1 | General ..... | 15 |
+| 11.2 | Parameters for BICC node status ..... | 15 |
+| 11.3 | Parameters for BICC availability ..... | 15 |
+| 11.4 | Parameters for BICC signalling utilization ..... | 16 |
+| 11.5 | Parameters for BICC fault and quality ..... | 18 |
+
+| | Page |
+|-------------------------------------------|-------------|
+| Appendix I – Usage of parameters..... | 19 |
+| I.1 Traffic and network planning ..... | 19 |
+| I.2 Quality ..... | 19 |
+| I.3 Fault and performance ..... | 19 |
+
+# Recommendation ITU-T Q.3910
+
+# Parameters for monitoring NGN protocols
+
+# 1 Scope
+
+In order to effectively manage the resources provided by signalling over the NGN network, it is necessary to monitor and measure the present, and estimate the future performance, utilization and availability of these resources. Thus, NGN monitoring and measurement parameters standardization should be provided. This Recommendation defines the protocols for measuring and monitoring PSTN/ISDN emulation service (PES) and IP multimedia subsystem (IMS) solutions, including real-time transfer protocol/real-time transfer control protocol (RTP/RTCP), session initiation protocol (SIP), H.248/media gateway control protocol (H.248/MEGACO), signalling transport (SIGTRAN) and bearer independent call control (BICC). How to monitor and measure these parameters is out of the scope of this Recommendation.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through references in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), *Gateway control protocol: Version 3*.
+- [ITU-T Q.752] Recommendation ITU-T Q.752 (1997), *Monitoring and measurements for Signalling System No. 7 networks*.
+- [ITU-T Q.3902] Recommendation ITU-T Q.3902 (2008), *Operational parameters to be monitored when implementing NGN technical means in public telecommunication networks*.
+
+# 3 Definitions
+
+None.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------|--------------------------------------------|
+| ACM | Address Complete Message |
+| ANM | Answer Message |
+| APM | Application Transport |
+| BICC | Bearer Independent Call Control |
+| CFN | Confusion |
+| CGB | Circuit/CIC Group Blocking |
+| CGBA | Circuit/CIC Group Blocking Acknowledgement |
+| CGU | Circuit/CIC Group Unblocking |
+
+| | |
+|--------|----------------------------------------------|
+| CGUA | Circuit/CIC Group Unblocking Acknowledgement |
+| CIC | Circuit Identifier Code |
+| CON | Connect |
+| COT | Continuity |
+| CPG | Call Progress |
+| CQM | Circuit/CIC group Query Message |
+| CQR | Circuit/CIC group Query Response |
+| CRG | Charge information |
+| FAA | Facility Accepted |
+| FAC | Facility |
+| FAR | Facility Request |
+| FOT | Forward Transfer |
+| FRJ | Facility Reject |
+| GRA | Circuit/CIC Group Reset Acknowledgement |
+| GRS | Circuit/CIC Group Reset |
+| IAM | Initial Address Message |
+| IDR | Identification Request |
+| IMS | IP Multimedia Subsystem |
+| INF | Information |
+| INR | Information Request |
+| IP | Internet Protocol |
+| IRS | Identification Response |
+| IUA | ISDN User Adaptation layer |
+| LOP | Loop Prevention |
+| M2UA | MTP 2 User Adaptation layer |
+| M2PA | MTP2 User Peer-to-Peer Adaptation Layer |
+| M3UA | MTP 3 User Adaptation layer |
+| MG | Media Gateway |
+| MGC | Media Gateway Controller |
+| MEGACO | Media Gateway Control protocol |
+| MTP | Message Transfer Part |
+| NGN | Next Generation Network |
+| NMS | NGN Management System |
+| NRM | Network Resource Management |
+| PES | PSTN/ISDN Emulation Service |
+| PS | Packet Switching (network) |
+| PRI | Pre-Release Information |
+
+| | |
+|---------|----------------------------------------|
+| REL | Release |
+| RES | Resume |
+| RLC | Release Complete |
+| RSC | Reset Circuit/CIC |
+| RTCP | Real-time Transfer Control Protocol |
+| RTP | Real-time Transfer Protocol |
+| SAM | Subsequent Address Message |
+| SCCP | Signalling Connection Control Part |
+| SCTP | Session Control Transfer Protocol |
+| SDM | Subsequent Directory Number |
+| SGM | Segmentation |
+| SIGTRAN | Signalling Transport |
+| SIP | Session Initiation Protocol |
+| SLA | Service Level Agreement |
+| SLS | Service Level Specification |
+| SNMP | Simple Network Management Protocol |
+| SS7 | Signalling System No. 7 |
+| SUA | SCCP User Adaptation |
+| SUS | Suspend |
+| TM | Technical Means |
+| UCIC | Unequipped Circuit Identification Code |
+| URI | Uniform Resource Identifier |
+| V5UA | V5.2-User Adaptation layer |
+| UAL | User Adaptation Layer |
+| USR | User-to-user information |
+
+# 5 Conventions
+
+The NGN monitoring system is based on the evolution on the SS7 monitoring principles. According to [ITU-T Q.752], the following categories regarding the measured values should be defined in the NMS based on PES and IMS solutions:
+
+- **fault (F)**: Measurement for reporting processes and detecting problems, as well as for finding out some abnormal situations in the SS7, SIP and H.248/MEGACO signalling networks, and for NGN hardware, involving its reconfiguring and restarting procedures;
+- **quality (Q)**: Measurement for service level parameters intended for different traffic types involving voice and video under different services; for reporting processes; for assuming measures in providing the guaranteed service level, as well as for developing an operator's policy and strategy for providing a certain service level. It should be also used to have the SLA and/or SLS performed and relevant reports drawn up;
+- **traffic (T)**: Measurement for real-time traffic parameters based on IP-flow information for the purpose of identifying any unwanted or unauthorized traffic; studying any inside and
+
+outside impacts on network security; detecting any network abnormal events; defining the requested user-to-user, user-to-network or network-to-user interaction parameters; studying traffic changes trends; and conducting prevention management;
+
+- **accounting (A):** Measurement for providing accounting and estimation data reliability by comparison;
+- **network administration and planning (N):** Measurement for SS7 and NGN networks administration including the SIP and H.248/MEGACO signalling systems; making decisions on network development and network planning; optimizing network infrastructure enhancement investment; planning applications and services; preparing traffic data to have the network further designed;
+- **near-real-time measurements (R):** Measurement for detecting any faults in the network. It may be considered supplementary to the above-mentioned measurements.
+
+# 6 Reference model
+
+According to [ITU-T Q.3902], signalling system monitoring subsystems shall be independent of a vendor's NGN TM (for example, MGC, PS, MG). In order to gather and initially process any other subsystems information, the vendor's NGN TM management systems shall be used. SNMP or NetFlow may be used as the interaction protocol among the monitoring system central elements. The message format shall be specified by telecommunication administrations.
+
+
+
+```
+
+graph TD
+ NMS["NMS
+central element"]
+ NGN["NGN
+vendor's TM
+management system
+monitoring"]
+ SS7["SS7
+monitoring
+subsystem"]
+ SIP["SIP
+monitoring
+subsystem"]
+ H248["H.248
+monitoring
+subsystem"]
+ FMS["Faults monitoring
+subsystem"]
+ FRM["Faults and
+reconfiguring
+procedures
+monitoring
+subsystem"]
+ IFM["IP information flows
+monitoring subsystem"]
+ VSM["Voice (transfer)
+service level
+monitoring subsystem"]
+ VSLM["Video streaming
+service level
+monitoring subsystem"]
+ SLSM["SLA/SLS monitoring
+subsystem"]
+ ASM["Application server
+monitoring subsystem"]
+
+ NMS --- NGN
+ NMS --- SS7
+ NMS --- SIP
+ NMS --- H248
+ NMS --- FMS
+ NGN --- FRM
+ NGN --- IFM
+ NGN --- VSM
+ NGN --- VSLM
+ NGN --- SLSM
+ NGN --- ASM
+
+```
+
+Diagram showing the basic architecture of NMS (ITU-T Q.3902). The central element is the NMS central element, which is connected to the NGN vendor's TM management system monitoring. The NMS central element is also connected to four monitoring subsystems: SS7 monitoring subsystem, SIP monitoring subsystem, H.248 monitoring subsystem, and Faults monitoring subsystem. The NGN vendor's TM management system monitoring is connected to six monitoring subsystems: Faults and reconfiguring procedures monitoring subsystem, IP information flows monitoring subsystem, Voice (transfer) service level monitoring subsystem, Video streaming service level monitoring subsystem, SLA/SLS monitoring subsystem, and Application server monitoring subsystem.
+
+**Figure 1 – Basic architecture of NMS [ITU-T Q.3902]**
+
+# 7 RTP/RTCP monitoring and measurement parameters
+
+## 7.1 General
+
+RTP/RTCP performance, availability and utilization mostly depend on the IP network. RTP/RTCP node status, faults and quality, availability, and utilization indicators are detailed in Tables 1, 2, 3 and 4, respectively.
+
+The 'Usage' column indicates the categories applicable to each parameter.
+
+The 'Interval' column indicates the duration of each parameter.
+
+The 'Units' column is used to indicate the registration items applied at the interval.
+
+The 'Mandatory' column indicates those parameters which must be provided.
+
+## 7.2 Parameters for RTP/RTCP node status
+
+The following parameters give status information of RTP/RTCP node. The comparison of several parameters might give additional information.
+
+- Item 1.1 indicates the duration of unavailability of the destination node.
+- Items 1.2 and 1.3 indicate, respectively, the start and the end of the destination's unavailability.
+
+**Table 1 – RTP/RTCP node status parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|---------------------------------------------------|-------------|---------|---------------|-----------|
+| 1.1 | Duration of the destination node's unavailability | second/node | F, T, N | 60 min | Yes |
+| 1.2 | Start of 1.1 | event/node | F, R | On occurrence | Yes |
+| 1.3 | End of 1.1 | event/node | F, R | On occurrence | Yes |
+
+## 7.3 Parameters for RTP/RTCP fault and quality
+
+The most probable failure or poor performance reasons are listed as follows. In some cases, other reasons might apply. The comparison of several parameters might give additional information.
+
+- Item 2.1 indicates packet loss rate in one direction.
+- Item 2.2 indicates the maximum packet delay in one direction.
+- Item 2.3 indicates the variety of packet delay.
+- Item 2.4 indicates the rate of the error packets in the monitored duration.
+- Item 2.5 indicates the rate of supposititious packets in the monitored duration.
+
+**Table 2 – RTP/RTCP fault and quality parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|----------------------------|-------------------------|-------|----------|-----------|
+| 2.1 | One way packet loss rate | 1/destination | F, Q | 1 min | Yes |
+| 2.2 | One way delay | millisecond/destination | Q | 5 min | Yes |
+| 2.3 | Jitter | millisecond/destination | Q | 5 min | Yes |
+| 2.4 | Error packet rate | 1/destination | F, Q | 1 min | Yes |
+| | | 1/node | F, Q | 1 min | Yes |
+| 2.5 | Supposititious packet rate | 1/destination | Q | 5 min | Yes |
+| | | 1/node | Q | 5 min | Yes |
+
+## 7.4 Parameters for RTP/RTCP availability
+
+- Item 3.1 indicates the duration of the RTP/RTCP destination availability.
+- Item 3.3 can be derived from 3.2.
+
+**Table 3 – RTP/RTCP availability parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|----------------------------------------------|--------------------|-------|----------|-----------|
+| 3.1 | RTP/RTCP availability rate | 1/node | F | 60 min | No |
+| | | 1/destination | F | 60 min | No |
+| 3.2 | Duration of the destination's availability | second/destination | F | 60 min | No |
+| 3.3 | Duration of the destination's unavailability | second/destination | F | 60 min | Yes |
+| 3.4 | Total number of bytes received | bytes/destination | T | 30 min | No |
+| | | bytes/node | T | 30 min | No |
+
+## 7.5 Parameters for bandwidth utilization
+
+- Item 4.1 indicates the used bandwidth of RTP/RTCP for one node.
+- Item 4.2 indicates the maximum available bandwidth used for RTP/RTCP in the bandwidth pipe, based on the destination.
+- Item 4.3 indicates the minimum available bandwidth used for RTP/RTCP in the bandwidth pipe, based on the destination.
+- Item 4.4 indicates the mean value of the available bandwidth used for RTP/RTCP in the bandwidth pipe, based on the destination.
+
+**Table 4 – Bandwidth utilization parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|------------------------------------------------------------|-------------------|-------|----------|-----------|
+| 4.1 | Maximum available bandwidth, based on the node | bit/s/node | T, N | 60 min | Yes |
+| 4.2 | Maximum available bandwidth pipe, based on one destination | bit/s/destination | T, N | 60 min | Yes |
+| 4.3 | Minimum available bandwidth pipe, based on one destination | bit/s/destination | T, N | 60 min | No |
+| 4.4 | Mean available bandwidth pipe, based on one destination | bit/s/destination | T, N | 60 min | No |
+
+# 8 SIP monitoring and measurements parameters
+
+## 8.1 General
+
+Table 5 defines the SIP node status (adjacent node accessibility, routing performance) parameters.
+
+Table 6 defines the SIP availability parameters.
+
+Table 7 defines the SIP signalling utilization parameters.
+
+Table 8 defines the SIP fault and quality parameters.
+
+The 'Usage' column indicates the categories applicable to each parameter.
+
+The 'Interval' column indicates the duration of each parameter.
+
+The 'Units' column is used to indicate the registration items applied at the interval.
+
+The 'Mandatory' column indicates those parameters which must be provided.
+
+## 8.2 Parameters for SIP node status
+
+The following parameters give status information of SIP nodes. The comparison of several parameters might give additional information.
+
+- Item 5.1 indicates the duration of unavailability of the destination node.
+- Item 5.4 indicates the number of the messages discarded due to the transmission error.
+
+**Table 5 – SIP node status parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|------------------------------------------------------------------|--------------|---------|---------------|-----------|
+| 5.1 | Duration of the destination node's unavailability | second/node | F, R, N | 60 min | Yes |
+| 5.2 | Start of 5.1 | event/node | F, R | On occurrence | Yes |
+| 5.3 | End of 5.1 | event/node | F, R | On occurrence | Yes |
+| 5.4 | Total number of messages discarded due to the transmission error | message/node | N, F | 60 min | Yes |
+
+## 8.3 Parameters for SIP availability
+
+- Item 6.1 indicates the SIP node availability rate.
+- Items 6.2 and 6.3 indicate the duration of the SIP node availability and unavailability.
+- Items 6.4 and 6.5 indicate the total number of bytes the SIP node received and sent.
+
+**Table 6 – SIP availability parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|------------------------------------|-------------|-------|---------------|-----------|
+| 6.1 | SIP availability rate | 1/node | F | 60 min | No |
+| 6.2 | Duration of availability | second/port | F | 60 min | No |
+| 6.3 | Duration of unavailability | second/port | F | 60 min | Yes |
+| 6.4 | The total number of bytes received | bytes/port | T | 30 min | No |
+| | | bytes/node | T | 30 min | No |
+| 6.5 | The total number of bytes sent | bytes/port | F | 30 min | Yes |
+| | | bytes/node | F | 30 min | Yes |
+| 6.6 | Start of unavailability | event/port | F, R | On occurrence | Yes |
+| 6.7 | End of unavailability | event/port | F, R | On occurrence | Yes |
+
+## 8.4 Parameters for SIP signalling utilization
+
+- Items 7.1 and 7.2 indicate the total number of SIP registration requests sent and received.
+- Items 7.3 and 7.4 indicate the total number of SIP session requests sent and received.
+- Items 7.5 to 7.16 indicate the total number of sent and received response messages.
+- Items 7.17 and 7.18 indicate the total number of responses to session requests and session completed.
+
+- Items 7.19 and 7.20 indicate the total number of unanswered requests.
+- Items 7.21 and 7.22 indicate the total number of responses sent and received.
+
+**Table 7 – SIP signalling utilization parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|-------------|----------------------------------------------------------|--------------|--------------|-----------------|------------------|
+| 7.1 | Total number of SIP registration requests sent | message/node | T, R, F | 15 min | Yes |
+| 7.2 | Total number of SIP registration requests received | message/node | T, R | 15 min | Yes |
+| 7.3 | Total number of SIP session requests sent | message/node | T, N | 15 min | Yes |
+| 7.4 | Total number of SIP session requests received | message/node | T, N | 15 min | Yes |
+| 7.5 | Total number of 1xx messages sent | message/node | T, N | 15 min | No |
+| 7.6 | Total number of 1xx messages received | message/node | T, N | 15 min | No |
+| 7.7 | Total number of 2xx messages sent | message/node | T, N | 15 min | No |
+| 7.8 | Total number of 2xx messages received | message/node | T, N | 15 min | No |
+| 7.9 | Total number of 3xx messages sent | message/node | T, N | 15 min | No |
+| 7.10 | Total number of 3xx messages received | message/node | T, N | 15 min | No |
+| 7.11 | Total number of 4xx messages sent | message/node | T, N | 15 min | Yes |
+| 7.12 | Total number of 4xx messages received | message/node | T, N | 15 min | Yes |
+| 7.13 | Total number of 5xx messages sent | message/node | T, N | 30 min | Yes |
+| 7.14 | Total number of 5xx messages received | message/node | T, N | 30 min | Yes |
+| 7.15 | Total number of 6xx messages sent | message/node | T, N | 60 min | Yes |
+| 7.16 | Total number of 6xx messages received | message/node | T, N | 60 min | Yes |
+| 7.17 | Total number of responses to session requests | message/node | T, N | 15 min | Yes |
+| 7.18 | Total number of responses to session complete | message/node | T, N | 15 min | Yes |
+| 7.19 | Total number of unanswered responses to session requests | message/node | T, N | 15 min | Yes |
+| 7.20 | Total number of unanswered responses to session complete | message/node | T, N | 15 min | Yes |
+| 7.21 | Total number of responses sent | message/node | T, N | 15 min | Yes |
+| 7.22 | Total number of responses received | message/node | T, N | 15 min | Yes |
+
+## 8.5 Parameters for SIP fault and quality
+
+- Items 8.1, 8.2 and 8.3 indicate the delay of request messages.
+- Item 8.4 indicates the total number of failing transactions.
+- Item 8.5 indicates the total number of transactions.
+- Item 8.6 indicates the total number of received messages with unsupported URIs.
+- Item 8.7 indicates the total number of re-sent responses.
+- Items 8.8 to 8.10 respectively indicate the total number of the re-sent messages for three different requests.
+
+**Table 8 – SIP fault and quality parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|---------------------------------------------------------|--------------|------------|----------|-----------|
+| 8.1 | Mean delay of registration requests | second/node | T, R, Q, N | 15 min | Yes |
+| 8.2 | Mean delay of session requests | second/node | T, R, Q, N | 15 min | Yes |
+| 8.3 | Mean delay of session disconnects | second/node | T, R, Q, N | 15 min | Yes |
+| 8.4 | Total number of failing transactions | event/node | F, Q, R | 15 min | Yes |
+| 8.5 | Total number of transactions | event/node | T, N | 15 min | Yes |
+| 8.6 | Total number of messages with unsupported URIs received | message/node | F, R | 15 min | Yes |
+| 8.7 | Total number of responses re-sent | message/node | F, R | 15 min | Yes |
+| 8.8 | Total number of REGISTER requests re-sent | message/node | F, R | 15 min | Yes |
+| 8.9 | Total number of CANCEL requests re-sent | message/node | F, R | 15 min | Yes |
+| 8.10 | Total number of BYE requests re-sent | message/node | F, R | 15 min | Yes |
+
+# 9 H.248/MEGACO monitoring and measurement parameters
+
+## 9.1 General
+
+Table 9 defines the H.248/MEGACO [ITU-T H.248] node status parameters.
+
+Table 10 defines the H.248/MEGACO availability parameters.
+
+Table 11 defines H.248/MEGACO utilization parameters.
+
+Table 12 defines H.248/MEGACO service parameters.
+
+The 'Usage' column indicates the categories applicable to each parameter.
+
+The 'Interval' column indicates the duration of each parameter.
+
+The 'Units' column is used to indicate the registration items applied at the interval.
+
+The 'Mandatory' column indicates those parameters which must be provided.
+
+## 9.2 Parameters for H.248/MEGACO node status
+
+The following parameters give the most probable H.248/MEGACO failure reasons. In some cases, other reasons might apply. The comparison of several parameters might give additional information.
+
+- Item 9.1 indicates the duration of unavailability of the destination node.
+- Item 9.4 indicates the total number of messages discarded due to the transmission error.
+
+**Table 9 – H.248/MEGACO node status parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|------------------------------------------------------------------|--------------|---------|---------------|-----------|
+| 9.1 | Duration of the destination node's unavailability | second/node | F, R, N | 60 min | Yes |
+| 9.2 | Start of 9.1 | event/node | F, R | On occurrence | Yes |
+| 9.3 | End of 9.1 | event/node | F, R | On occurrence | Yes |
+| 9.4 | Total number of messages discarded due to the transmission error | message/node | N, F | 60 min | Yes |
+
+## 9.3 Parameters for H.248/MEGACO availability
+
+- Item 10.1 indicates the H.248/MEGACO node availability rate.
+- Items 10.2 and 10.3 indicate the duration of availability and unavailability of the interfaces.
+- Items 10.4 and 10.5 indicate the total number of bytes the interface received and sent.
+
+**Table 10 – H.248/MEGACO availability parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|----------------------------------|-------------|---------|---------------|-----------|
+| 10.1 | Local MEGACO availability rate | 1/node | T, F, N | 60 min | No |
+| 10.2 | Duration of local availability | second/node | T, N | 60 min | No |
+| 10.3 | Duration of local unavailability | second/node | F, R | 60 min | Yes |
+| 10.4 | Total number of bytes received | bytes/node | T, N | 30 min | Yes |
+| 10.5 | Total number of bytes sent | bytes/node | T, N | 30 min | Yes |
+| 10.6 | Start of local unavailability | event/node | F, R | On occurrence | Yes |
+| 10.7 | End of local unavailability | event/node | F, R | On occurrence | Yes |
+
+## 9.4 Parameters for H.248/MEGACO utilization
+
+- Items 11.1 and 11.2 indicate the total number of pending messages sent and received.
+- Items 11.3 and 11.4 indicate the total number of requests sent and received.
+- Items 11.5 and 11.6 indicate the total number of replies sent and received.
+- Item 11.7 indicates the total number of responses not received. This can be calculated from Items 11.1, 11.2 and 11.6.
+
+**Table 11 – H.248/MEGACO utilization parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|---------------------------------------------------------|--------------|-------|----------|-----------|
+| 11.1 | Total number of pending sent | message/node | T, N | 15 min | Yes |
+| 11.2 | Total number of pending received | message/node | T, N | 15 min | Yes |
+| 11.3 | Total number of requests sent | message/node | T, N | 15 min | Yes |
+| 11.4 | Total number of requests received | message/node | T, N | 15 min | No |
+| 11.5 | Total number of replies sent | message/node | T, N | 15 min | No |
+| 11.6 | Total number of replies received | message/node | T, N | 15 min | Yes |
+| 11.7 | Total number of requests that did not receive responses | message/node | F, R | 15 min | Yes |
+
+## **9.5 Parameters for the quality of the H.248/MEGACO service**
+
+- Item 12.1 indicates the total number of MGC messages sent.
+- Item 12.2 indicates the total number of MG messages received.
+- Items 12.3 and 12.4 indicate the total number of requests sent and received.
+- Items 12.5 and 12.6 indicate the one way delay of requests and replies.
+
+**Table 12 – Quality of H.248/MEGACO service parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|--------------------------------------|--------------|-------|----------|-----------|
+| 12.1 | Total number of MGC messages sent | message/node | T, N | 30 min | Yes |
+| 12.2 | Total number of MG messages received | message/node | T, N | 30 min | Yes |
+| 12.3 | Total number of requests sent | message/node | T, N | 30 min | Yes |
+| 12.4 | Total number of requests received | message/node | T, N | 30 min | Yes |
+| 12.5 | One way delay of requests | second/node | Q | 5 min | Yes |
+| 12.6 | One way delay of replies | second/node | Q | 5 min | Yes |
+
+# **10 SIGTRAN monitoring and measurement parameters**
+
+## **10.1 General**
+
+Table 13 defines the parameters related to the SIGTRAN node status.
+
+Table 14 defines SCTP association availability parameters.
+
+Table 15 defines the SIGTRAN utilization parameters.
+
+Table 16 defines the SIGTRAN fault and quality parameters.
+
+The 'Usage' column indicates the categories applicable to each parameter.
+
+The 'Interval' column indicates the duration of each parameter.
+
+The 'Units' column is used to indicate the registration items applied at the interval.
+
+The 'Mandatory' column indicates those parameters which must be provided.
+
+## 10.2 Parameters for SIGTRAN node status
+
+**Table 13 – SIGTRAN node status parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|----------------------------------------------------------------------|-------------|---------|---------------|-----------|
+| 13.1 | Duration of the endpoint's inaccessibility | second/node | F | 60 min | Yes |
+| 13.2 | Start of 13.1 | event/node | F, R | On occurrence | No |
+| 13.3 | End of 13.1 | event/node | F, R | On occurrence | No |
+| 13.4 | Total number of SCTP packets discarded due to the transmission error | packet/node | N, F, R | 30 min | Yes |
+
+## 10.3 Parameters for SCTP association availability
+
+**Table 14 – SCTP association availability parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|-------|---------------------------------------------------------------------------------|--------------------|-------|---------------|-----------|
+| 14.1 | SCTP association availability rate | 1/association | F | 60 min | No |
+| 14.2 | Duration of SCTP association's availability | second/association | F | 60 min | No |
+| 14.3 | Duration of SCTP association's unavailability | second/association | F, R | 60 min | Yes |
+| 14.4 | Duration of SCTP association | second/association | F | 60 min | Yes |
+| 14.5 | Duration of the association connection's failure due to loss of communication | second/association | F, R | 60 min | No |
+| 14.6 | Duration of the association connection's failure due to the communication error | second/association | F, R | 60 min | No |
+| 14.7 | Start of 14.5 | event/association | F, R | On occurrence | No |
+| 14.8 | End of 14.5 | event/association | F, R | On occurrence | No |
+| 14.9 | Start of 14.6 | event/association | F, R | On occurrence | No |
+| 14.10 | End of 14.6 | event/association | F, R | On occurrence | No |
+| 14.11 | Total number of bytes received by SCTP | bytes/association | T, N | 30 min | No |
+| 14.12 | Total number of bytes sent by SCTP | bytes/association | T, N | 30 min | No |
+
+## 10.4 Parameters for SIGTRAN utilization
+
+**Table 15 – SIGTRAN utilization parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|-------|---------------------------------------------------------|--------------------|-------|----------|-----------|
+| 15.1 | Total number of SCTP packets sent | packet/node | T, N | 30 min | Yes |
+| | | packet/association | T | 30 min | Yes |
+| 15.2 | Total number of SCTP packets received | packet/node | T, N | 30 min | Yes |
+| | | packet/association | T | 30 min | Yes |
+| 15.3 | Total number of sent SCTP packets with payload data | packet/node | T, N | 30 min | Yes |
+| | | packet/association | T | 30 min | Yes |
+| 15.4 | Total number of received SCTP packets with payload data | packet/node | T, N | 30 min | Yes |
+| | | packet/association | T | 30 min | Yes |
+| 15.5 | Total number of sent packets with M2UA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.6 | Total number of received packets with M2UA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.7 | Total number of sent packets with M2PA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.8 | Total number of received packets with M2PA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.9 | Total number of sent packets with SUA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.10 | Total number of received packets with SUA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.11 | Total number of sent packets with IUA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.12 | Total number of received packet with IUA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.13 | Total number of sent packets with M3UA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.14 | Total number of received packets with M3UA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.15 | Total number of sent packets with V5UA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+| 15.16 | Total number of received packets with V5UA | packet/node | T, N | 30 min | No |
+| | | packet/association | T | 30 min | No |
+
+## 10.5 Parameters for SIGTRAN fault
+
+**Table 16 – SIGTRAN fault parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|-------|----------------------------------------|---------------------|-------|---------------|-----------|
+| 16.1 | Failure caused by the SCTP association | event/association | F, R | On occurrence | Yes |
+| 16.2 | Failure due to the IUA connection | event/association | F, R | On occurrence | No |
+| 16.3 | Failure due to the SUA connection | event/association | F, R | On occurrence | No |
+| 16.4 | Failure due to the M2UA connection | event/association | F, R | On occurrence | No |
+| 16.5 | Failure due to the M2PA connection | event/association | F, R | On occurrence | No |
+| 16.6 | Failure due to the M3UA connection | event/association | F, R | On occurrence | No |
+| 16.7 | Total number of failing transactions | event/association | F | 30 min | Yes |
+| | | event/node | F, N | 30 min | Yes |
+| 16.8 | Total number of IUA messages re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+| 16.9 | Total number of SUA messages re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+| 16.10 | Total number of M2UA messages re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+| 16.11 | Total number of M2PA messages re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+| 16.12 | Total number of M3UA messages re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+| 16.13 | Total number of IUA responses re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+| 16.14 | Total number of SUA responses re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+| 16.15 | Total number of M2UA responses re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+| 16.16 | Total number of M2PA responses re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+| 16.17 | Total number of M3UA responses re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+| 16.18 | Total number of V5UA responses re-sent | message/association | F | 30 min | No |
+| | | message/node | F, N | 30 min | No |
+
+**Table 16 – SIGTRAN fault parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|-------|---------------------------------------|---------------------|-------|----------|-----------|
+| 16.19 | Total number of UAL messages re-sent | message/association | F | 30 min | Yes |
+| | | message/node | F, N | 30 min | Yes |
+| 16.20 | Total number of UAL responses re-sent | message/association | F | 30 min | Yes |
+| | | message/node | F, N | 30 min | Yes |
+
+# 11 BICC monitoring and measurement parameters
+
+## 11.1 General
+
+Table 17 defines the BICC node status parameters.
+
+Table 18 defines BICC node availability parameters.
+
+Table 19 defines the BICC signalling utilization parameters.
+
+Table 20 defines the BICC fault and quality parameters.
+
+The 'Usage' column indicates the categories applicable to each parameter.
+
+The 'Interval' column indicates the duration of each parameter.
+
+The 'Units' column is used to indicate the registration items applied at the interval.
+
+The 'Mandatory' column indicates those parameters which must be provided.
+
+## 11.2 Parameters for BICC node status
+
+The following parameters give the most probable BICC failure reasons. In some cases, other reasons might apply. The comparison of several measurements might give additional information.
+
+- Item 17.1 indicates the duration of unavailability of the destination node.
+- Item 17.4 indicates the total number of messages discarded due to the transmission error.
+
+**Table 17 – BICC node status parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|-----------------------------------------------------------------|--------------|---------|---------------|-----------|
+| 17.1 | Duration of the destination node's unavailability | second/node | F, R, N | 60 min | Yes |
+| 17.2 | Start of 17.1 | event/node | F, R | On occurrence | Yes |
+| 17.3 | End of 17.1 | event/node | F, R | On occurrence | Yes |
+| 17.4 | Total number of message discarded due to the transmission error | message/node | N, F | 60 min | Yes |
+
+## 11.3 Parameters for BICC availability
+
+- Item 18.1 indicates the BICC node availability rate.
+- Items 18.2 and 18.3 indicate the duration of BICC node availability and unavailability.
+- Items 18.4 to 18.7 indicate the total number of bytes and messages the node received and sent.
+
+**Table 18 – BICC availability parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|-----------------------------------|--------------|-------|---------------|-----------|
+| 18.1 | BICC availability rate | 1/node | F | 60 min | No |
+| 18.2 | Duration of availability | second/node | F | 60 min | No |
+| 18.3 | Duration of unavailability | second/node | F | 60 min | Yes |
+| 18.4 | Total number of bytes received | bytes/node | T | 30 min | No |
+| 18.5 | Total number of messages received | message/node | T | 30 min | No |
+| 18.6 | Total number of bytes sent. | bytes/node | F | 30 min | Yes |
+| 18.7 | Total number of messages sent | message/node | T | 30 min | Yes |
+| 18.8 | Start of unavailability | event/node | F, R | On occurrence | Yes |
+| 18.9 | End of unavailability | event/node | F, R | On occurrence | Yes |
+
+## **11.4 Parameters for BICC signalling utilization**
+
+– Items 19.1 to 19.78 indicate the total number of some important BICC messages sent and received.
+
+**Table 19 – BICC signalling utilization parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|-------|----------------------------------------|--------------|-------|----------|-----------|
+| 19.1 | Total number of IAM messages sent | message/node | T, N | 60 min | Yes |
+| 19.2 | Total number of IAM messages received | message/node | T, N | 60 min | Yes |
+| 19.3 | Total number of ACM messages sent | message/node | T, N | 60 min | Yes |
+| 19.4 | Total number of ACM messages received | message/node | T, N | 60 min | Yes |
+| 19.5 | Total number of ANM messages sent | message/node | T, N | 60 min | Yes |
+| 19.6 | Total number of ANM messages received | message/node | T, N | 60 min | Yes |
+| 19.7 | Total number of REL messages sent | message/node | T, N | 60 min | Yes |
+| 19.8 | Total number of REL messages received | message/node | T, N | 60 min | Yes |
+| 19.9 | Total number of RLC messages sent | message/node | T, N | 60 min | Yes |
+| 19.10 | Total number of RLC messages received | message/node | T, N | 60 min | Yes |
+| 19.11 | Total number of APM messages sent | message/node | T, N | 60 min | No |
+| 19.12 | Total number of APM messages received | message/node | T, N | 60 min | No |
+| 19.13 | Total number of CPG messages sent | message/node | T, N | 60 min | No |
+| 19.14 | Total number of CPG messages received | message/node | T, N | 60 min | No |
+| 19.15 | Total number of CGB messages sent | message/node | T, N | 60 min | No |
+| 19.16 | Total number of CGB messages received | message/node | T, N | 60 min | No |
+| 19.17 | Total number of CGBA messages sent | message/node | T, N | 60 min | No |
+| 19.18 | Total number of CGBA messages received | message/node | T, N | 60 min | No |
+| 19.19 | Total number of CQM messages sent | message/node | T, N | 60 min | No |
+| 19.20 | Total number of CQM messages received | message/node | T, N | 60 min | No |
+| 19.21 | Total number of CQR messages sent | message/node | T, N | 60 min | No |
+| 19.22 | Total number of CQR messages received | message/node | T, N | 60 min | No |
+| 19.23 | Total number of GRS messages sent | message/node | T, N | 60 min | No |
+
+**Table 19 – BICC signalling utilization parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|-------------|----------------------------------------|--------------|--------------|-----------------|------------------|
+| 19.24 | Total number of GRS messages received | message/node | T, N | 60 min | No |
+| 19.25 | Total number of GRA messages sent | message/node | T, N | 60 min | No |
+| 19.26 | Total number of GRA messages received | message/node | T, N | 60 min | No |
+| 19.27 | Total number of CGU messages sent | message/node | T, N | 60 min | No |
+| 19.28 | Total number of CGU messages received | message/node | T, N | 60 min | No |
+| 19.29 | Total number of CGUA messages sent | message/node | T, N | 60 min | No |
+| 19.30 | Total number of CGUA messages received | message/node | T, N | 60 min | No |
+| 19.31 | Total number of CRG messages sent | message/node | T, N | 60 min | No |
+| 19.32 | Total number of CRG messages received | message/node | T, N | 60 min | No |
+| 19.33 | Total number of CFN messages sent | message/node | T, N | 60 min | No |
+| 19.34 | Total number of CFN messages received | message/node | T, N | 60 min | No |
+| 19.35 | Total number of CON messages sent | message/node | T, N | 60 min | No |
+| 19.36 | Total number of CON messages received | message/node | T, N | 60 min | No |
+| 19.37 | Total number of COT messages sent | message/node | T, N | 60 min | No |
+| 19.38 | Total number of COT messages received | message/node | T, N | 60 min | No |
+| 19.39 | Total number of FAA messages sent | message/node | T, N | 60 min | No |
+| 19.40 | Total number of FAA messages received | message/node | T, N | 60 min | No |
+| 19.41 | Total number of FAC messages sent | message/node | T, N | 60 min | No |
+| 19.42 | Total number of FAC messages received | message/node | T, N | 60 min | No |
+| 19.43 | Total number of FAR messages sent | message/node | T, N | 60 min | No |
+| 19.44 | Total number of FAR messages received | message/node | T, N | 60 min | No |
+| 19.45 | Total number of FRJ messages sent | message/node | T, N | 60 min | No |
+| 19.46 | Total number of FRJ messages received | message/node | T, N | 60 min | No |
+| 19.47 | Total number of FOT messages sent | message/node | T, N | 60 min | No |
+| 19.48 | Total number of FOT messages received | message/node | T, N | 60 min | No |
+| 19.49 | Total number of IDR messages sent | message/node | T, N | 60 min | No |
+| 19.50 | Total number of IDR messages received | message/node | T, N | 60 min | No |
+| 19.51 | Total number of IRS messages sent | message/node | T, N | 60 min | No |
+| 19.52 | Total number of IRS messages received | message/node | T, N | 60 min | No |
+| 19.53 | Total number of INF messages sent | message/node | T, N | 60 min | No |
+| 19.54 | Total number of INF messages received | message/node | T, N | 60 min | No |
+| 19.55 | Total number of INR messages sent | message/node | T, N | 60 min | No |
+| 19.56 | Total number of INR messages received | message/node | T, N | 60 min | No |
+| 19.57 | Total number of LOP messages sent | message/node | T, N | 60 min | No |
+| 19.58 | Total number of LOP messages received | message/node | T, N | 60 min | No |
+| 19.59 | Total number of NRM messages sent | message/node | T, N | 60 min | No |
+| 19.60 | Total number of NRM messages received | message/node | T, N | 60 min | No |
+| 19.61 | Total number of PRI messages sent | message/node | T, N | 60 min | No |
+
+**Table 19 – BICC signalling utilization parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|-------|----------------------------------------|--------------|-------|----------|-----------|
+| 19.62 | Total number of PRI messages received | message/node | T, N | 60 min | No |
+| 19.63 | Total number of RES messages sent | message/node | T, N | 60 min | No |
+| 19.64 | Total number of RES messages received | message/node | T, N | 60 min | No |
+| 19.65 | Total number of RSC messages sent | message/node | T, N | 60 min | No |
+| 19.66 | Total number of RSC messages received | message/node | T, N | 60 min | No |
+| 19.67 | Total number of SAM messages sent | message/node | T, N | 60 min | No |
+| 19.68 | Total number of SAM messages received | message/node | T, N | 60 min | No |
+| 19.69 | Total number of SDM messages sent | message/node | T, N | 60 min | No |
+| 19.70 | Total number of SDM messages received | message/node | T, N | 60 min | No |
+| 19.71 | Total number of SGM messages sent | message/node | T, N | 60 min | No |
+| 19.72 | Total number of SGM messages received | message/node | T, N | 60 min | No |
+| 19.73 | Total number of SUS messages sent | message/node | T, N | 60 min | No |
+| 19.74 | Total number of SUS messages received | message/node | T, N | 60 min | No |
+| 19.75 | Total number of UCIC messages sent | message/node | T, N | 60 min | No |
+| 19.76 | Total number of UCIC messages received | message/node | T, N | 60 min | No |
+| 19.77 | Total number of USR messages sent | message/node | T, N | 60 min | No |
+| 19.78 | Total number of USR messages received | message/node | T, N | 60 min | No |
+
+## 11.5 Parameters for BICC fault and quality
+
+– Items 20.1 to 20.7 indicate the total number of some successful and failed call procedures.
+
+**Table 20 – BICC fault and quality parameters**
+
+| Item | Description of parameters | Units | Usage | Interval | Mandatory |
+|------|-----------------------------------------------------------------------------|------------|---------|----------|-----------|
+| 20.1 | Total number of successful call set-ups | event/node | F, R, N | 60 min | Yes |
+| 20.2 | Total number of successful call answers | event/node | F, R, N | 60 min | Yes |
+| 20.3 | Total number of resources unavailable | event/node | F, R, N | 60 min | Yes |
+| 20.4 | Total number of service not available | event/node | F, R, N | 60 min | Yes |
+| 20.5 | Total number of service not implemented | event/node | F, R, N | 60 min | Yes |
+| 20.6 | Total number of invalid messages
(e.g., protocol parameter out of range) | event/node | F, R, N | 60 min | Yes |
+| 20.7 | Total number of protocol errors
(e.g., unknown message) | event/node | F, R, N | 60 min | Yes |
+
+# Appendix I
+
+## Usage of parameters
+
+(This appendix does not form an integral part of this Recommendation)
+
+## I.1 Traffic and network planning
+
+The traffic situation of physical ports/nodes is always a concern because traffic reflects the equipment/network's load situation, and provides an important reference for further planning the network. The monitoring parameters which reflect traffic and network planning have been already included in this Recommendation. Examples of such parameters are given as follows:
+
+- total number of bytes received (Item 3.4);
+- maximum available bandwidth used for RTP/RTCP in the bandwidth pipe, based on the destination (Item 4.2);
+- minimum available bandwidth used for RTP/RTCP in the bandwidth pipe, based on the destination (Item 4.3);
+- mean value of the available bandwidth used for RTP/RTCP in the bandwidth pipe, based on destination (Item 4.4);
+- total number of SIP registration requests sent and received (Items 7.1 and 7.2);
+- total number of SIP session requests sent and received (Items 7.3 and 7.4);
+- total number of sent and received messages for different requests and responses (Items 7.5 to 7.16).
+
+## I.2 Quality
+
+The quality of service is always interesting for operators. The monitoring parameters which can reflect the quality of voice service are mentioned in this Recommendation. These parameters can be used for providing the service level guarantee, as well as for developing an operator's service level policy and strategy. They can also be used to draw up the SLA and/or SLS performance reports and relevant reports. Part of these parameters is listed as follows:
+
+- packet loss rate in one direction (Item 2.1);
+- maximum packet delay in one direction (Item 2.2);
+- variation in packet delay (Item 2.3).
+
+## I.3 Fault and performance
+
+Some parameters can be used for detecting problems, as well as for detecting some abnormal situations in the SIP and H.248/MEGACO signalling networks. They can also be used for detecting abnormal hardware situations which will result in reconfiguring and restarting the hardware. Part of these parameters is listed as follows:
+
+- duration of unavailability of the destination node (Item 5.1);
+- total number of the messages discarded due to the transmission error (Item 5.4);
+- duration of the SIP availability and unavailability (Items 6.2 and 6.3);
+- SIP node availability rate (Item 6.1);
+- total number of bytes the port received and sent (Items 6.4 and 6.5).
+
+
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3920-201608-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3920-201608-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..fecff2ffce969c6e0d7e9ce56257c9cc1dfd58ed
--- /dev/null
+++ b/marked/Q/T-REC-Q.3920-201608-I_PDF-E/raw.md
@@ -0,0 +1,313 @@
+
+
+International Telecommunication Union
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3920**
+
+(08/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for next generation networks
+
+---
+
+**Terms and definitions for conformance and interoperability**
+
+Recommendation ITU-T Q.3920
+
+ITU-T
+
+
+
+The logo of the International Telecommunication Union (ITU) features a stylized globe with a red lightning bolt striking across it. The letters 'ITU' are prominently displayed in blue and white within the globe.
+
+ITU logo
+
+International
+Telecommunication
+Union
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.3920
+
+### Terms and definitions for conformance and interoperability
+
+## Summary
+
+The activities on conformance and interoperability (C&I) are widespread in the information and communication technology (ICT) world, but there are different interpretations of terms and definitions which define similar concepts.
+
+To ensure the precision of the use of the C&I vocabulary in the activities of the ITU C&I programme, Recommendation ITU-T Q.3920 provides the list of terms and definitions related to conformance and interoperability.
+
+### History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3920 | 2016-08-29 | 11 | 11.1002/1000/12991 |
+
+### Keywords
+
+Conformance, definitions, interoperability, terms, testing, vocabulary.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation ..... | 4 |
+| 4 Abbreviations and acronyms ..... | 5 |
+| 5 Conventions ..... | 5 |
+| Bibliography..... | 6 |
+
+
+
+## Recommendation ITU-T Q.3920
+
+### Terms and definitions for conformance and interoperability
+
+## 1 Scope
+
+This Recommendation includes all the terms and definitions on conformance and interoperability (C&I) which are being used or to be used in the existing ITU-T Recommendations and standards of other standards development organizations (SDOs). This Recommendation will be revised on a regular basis.
+
+## 2 References
+
+None.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation collects the following terms defined elsewhere:
+
+**3.1.1 abstract test case** [b-ITU-T X.290]: A complete and independent specification of the actions required to achieve a specific test purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in a stable testing state and ending in a stable testing state. This specification may involve one or more consecutive or concurrent connections.
+
+**3.1.2 abstract test method (ATM)** [b-ITU-T X.290]: The description of how an implementation under test (IUT) is to be tested, given at an appropriate level of abstraction to make the description independent of any particular realization of a Means of Testing, but with enough detail to enable abstract test cases to be specified for this test method.
+
+**3.1.3 abstract test suite (ATS)** [b-ITU-T X.290]: A test suite composed of abstract test cases.
+
+**3.1.4 acceptance or acceptance of conformity assessment results** [b-ISO/IEC 17000]: Use of a conformity assessment result provided by another person or body.
+
+**3.1.5 accreditation** [b-ISO/IEC 17000]: Third-party attestation related to a conformity assessment body conveying formal demonstration of its competence to carry out specific conformity assessment tasks.
+
+**3.1.6 accreditation body** [b-ISO/IEC 17000]: Authoritative body that performs accreditation.
+
+**3.1.7 approval** [b-ISO/IEC 17000]: Permission for a product or process to be marketed or used for stated purposes or under stated conditions.
+
+**3.1.8 attestation** [b-ISO/IEC 17000]: Issue of a statement, based on a decision following review, that fulfilment of specified requirements has been demonstrated.
+
+**3.1.9 basic interconnection test (BIT)** [b-ITU-T X.290]: A test of an implementation under test (IUT) which has limited scope to determine whether or not there is sufficient conformance to the relevant protocol(s) for interconnection to be possible, without trying to perform thorough testing.
+
+**3.1.10 bilateral arrangement** [b-ISO/IEC 17000]: Arrangement whereby two parties recognize or accept each other's conformity assessment results.
+
+**3.1.11 certification** [b-ISO/IEC 17000]: Third-party attestation related to products, processes, systems or persons.
+
+- 3.1.12 conformance clause** [b-ITU-T Z.450]: A part of a standard or Recommendation which identifies what in the standard or Recommendation should be met in order to conform to the standard or Recommendation.
+- 3.1.13 conformity assessment** [b-ISO/IEC 17000]: Demonstration that specified requirements relating to a product, process, system, person or body are fulfilled.
+- 3.1.14 conformity assessment body** [b-ISO/IEC 17000]: Body that performs conformity assessment services.
+- 3.1.15 conformity assessment scheme** (or programme) [b-ISO/IEC 17000]: Conformity assessment system related to specified objects of conformity assessment, to which the same specified requirements, specific rules and procedures apply.
+- 3.1.16 declaration** [b-ISO/IEC 17000]: First-party attestation.
+- 3.1.17 electromagnetic compatibility** [b-IEC 60050-161] and [b-ITU-T K.63]: The ability of an equipment or system to function satisfactorily in its electromagnetic environment without introducing intolerable electromagnetic disturbance to anything in that environment.
+- 3.1.18 equal and national treatment** [b-ISO/IEC 17000]: Treatment accorded to products or processes originating in other countries that is no less favourable than that accorded to like products or processes of national origin, or originating in any other country, in a comparable situation.
+- 3.1.19 equal treatment** [b-ISO/IEC 17000]: Treatment accorded to products or processes from one supplier that is no less favourable than that accorded to like products or processes from any other supplier, in a comparable situation.
+- 3.1.20 first-party conformity assessment activity** [b-ISO/IEC 17000]: Conformity assessment activity that is performed by the person or organization that provides the object.
+- 3.1.21 implementation conformance statement (ICS)** [b-ITU-T X.290]: A statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented. The ICS can take several forms: protocol ICS, profile ICS, and information object ICS.
+- 3.1.22 implementation under test (IUT)** [b-ITU-T X.290]: An implementation of one or more open systems interconnection (OSI) protocols in an adjacent user/provider relationship, being that part of a real open system which is to be studied by testing.
+- 3.1.23 inspection** [b-ISO/IEC 17000]: Examination of a product design, product, process or installation and determination of its conformity with specific requirements or, on the basis of professional judgement, with general requirements.
+- 3.1.24 interoperability** [b-ITU-T Y.101]: The ability of two or more systems or applications to exchange information and to mutually use the information that has been exchanged.
+- 3.1.25 interoperability (management network)** [b-ITU-T M.60]: The ability of network management products and services from different suppliers to work together to manage communications between managed object classes.
+- 3.1.26 interoperability testing** [b-ITU-T Z.450]: Testing to assess the ability of two or more systems to exchange information and to make mutual use of the information that has been exchanged.
+- 3.1.27 market surveillance** [b-EU 765/2008/EC]: The activities carried out and measures taken by public authorities to ensure that products comply with the requirements set out in the relevant Community harmonisation legislation and do not endanger health, safety or any other aspect of public interest protection.
+
+- 3.1.28 model network** [b-ITU-T Q.3900]: Network which simulates the capabilities similar to those available in present telecommunication networks, has a similar architecture and functionality and uses the same telecommunication technical means.
+- 3.1.29 most favoured nation** [b-WTO]: Countries cannot normally discriminate between their trading partners, where one is granted a special favour (such as a lower customs duty rate for one of their products) then all other members must receive the same favour.
+- 3.1.30 multilateral arrangement** [b-ISO/IEC 17000]: Arrangement whereby more than two parties recognize or accept one another's conformity assessment results.
+- 3.1.31 mutual recognition arrangements (MRA/MLA)** [b-ISO/IEC 17011:2004]: Accreditation body members of the IAF and/or ILAC Multi-Lateral Mutual Recognition Arrangements (MLA/MRA) have the equivalence of their accreditation programmes recognized through a regular programme of evaluation by their peer accreditation bodies within the MLA/MRA.
+- 3.1.32 national accreditation body** [b-EU 765/2008/EC]: The sole body in a Member State that performs accreditation with authority derived from the State.
+- 3.1.33 national treatment** [b-ISO/IEC 17000]: Treatment accorded to products or processes originating in other countries that is no less favourable than that accorded to like products or processes of national origin, in a comparable situation.
+- 3.1.34 next generation network (NGN)** [b-ITU-T Y.2001]: A packet-based network able to provide telecommunication services and able to make use of multiple broadband, quality of service (QoS)-enabled transport technologies and in which service-related functions are independent of the underlying transport-related technologies. It enables unfettered access for users to networks and to competing service providers and/or services of their choice. It supports generalized mobility which will allow consistent and ubiquitous provision of services to users.
+- 3.1.35 next generation network (NGN) monitoring systems (NMS)** [b-ITU-T Q.3902]: A system which is responsible for online (under payload) measurement values of the NGN protocols carried out on the different NGN strata.
+- 3.1.36 next generation network (NGN) technical means** [b-ITU-T Q.3900]: The NGN basic equipment which serves as a basis for building new generation network solutions, including for application in public telecommunication networks.
+- 3.1.37 peer evaluation** [b-EU 765/2008/EC]: A process for the assessment of a national accreditation body by other national accreditation bodies.
+- 3.1.38 pluri-lateral agreement** [b-WTO]: An agreement which only some members have signed.
+- 3.1.39 protocol implementation conformance statement (PICS)** [b-ITU-T X.290]: An implementation conformance statement (ICS) for an implementation or system claimed to conform to a given protocol specification.
+- 3.1.40 quality of service (QoS) experienced/perceived by customer/user (QoSE)** [b-ITU-T E.800]: A statement expressing the level of quality that customers/users believe they have experienced.
+- 3.1.41 quality of service (QoS)** [b-ITU-T E.800]: Totality of characteristics of a telecommunications service that bear on its ability to satisfy stated and implied needs of the user of the service.
+- 3.1.42 recognition or recognition of conformity assessment results** [b-ISO/IEC 17000]: Acknowledgement of the validity of a conformity assessment result provided by another person or body.
+
+**3.1.43 review** [b-ISO/IEC 17000]: Verification of the suitability, adequacy and effectiveness of selection and determination activities, and the results of these activities, with regard to fulfilment of specified requirements by an object of conformity assessment.
+
+**3.1.44 scope of attestation** [b-ISO/IEC 17000]: Range or characteristics of objects of conformity assessment covered by attestation.
+
+**3.1.45 second-party conformity assessment activity** [b-ISO/IEC 17000]: Conformity assessment activity that is performed by a person or organization that has a user interest in the object.
+
+**3.1.46 specified requirement** [b-ISO/IEC 17000]: Need or expectation that is stated.
+
+**3.1.47 standard** [b-WTO TBT Agreement]: Document approved by a recognized body, that provides, for common and repeated use, rules, guidelines or characteristics for products or related processes and production methods, with which compliance is not mandatory. It may also include or deal exclusively with terminology, symbols, packaging, marking or labelling requirements as they apply to a product, process or production method.
+
+**3.1.48 supplier's declaration of conformity** [b-ISO/IEC 17000]: Is a "declaration" as defined in [b-ISO/IEC 17000], i.e., first-party attestation (see clause 3.1.16). For more details, refer to [b-ISO/IEC 17050].
+
+NOTE – To avoid any confusion with attestation by certification bodies, the term "self-certification" is deprecated and should not be used.
+
+**3.1.49 surveillance** [b-ISO/IEC 17000]: Systematic iteration of conformity assessment activities as a basis for maintaining the validity of the statement of conformity.
+
+**3.1.50 system under test (SUT)** [b-ITU-T X.290]: The real open system in which the implementation under test (IUT) resides.
+
+**3.1.51 technical regulation** [b-WTO TBT Agreement]: Document which lays down product characteristics or their related processes and production methods, including the applicable administrative provisions, with which compliance is mandatory. It may also include or deal exclusively with terminology, symbols, packaging, marking or labelling requirements as they apply to a product, process or production method.
+
+**3.1.52 testing** [b-ISO/IEC 17000]: Determination of one or more characteristics of an object of conformity assessment, according to a procedure.
+
+**3.1.53 test laboratory** [b-ITU-T X.290]: An organization that carries out conformance testing. This can be a third party, a user organization, a telecommunications administration or recognized private operating agency, or an identifiable part of a supplier organization.
+
+**3.1.54 test purpose** [b-ITU-T X.290]: A prose description of a well-defined objective of testing, focusing on a single conformance requirement or a set of related conformance requirements as specified in the appropriate open systems interconnection (OSI) specification (e.g., verifying the support of a specific value of a specific parameter).
+
+**3.1.55 (conformance) test suite** [b-ITU-T X.290]: A complete set of test cases, possibly combined into nested test groups, that is needed to perform dynamic conformance testing for one or more open systems interconnection (OSI) protocols.
+
+**3.1.56 third-party conformity assessment activity** [b-ISO/IEC 17000]: Conformity assessment activity that is performed by a person or body that is independent of the person or organization that provides the object, and of user interests in that object.
+
+**3.1.57 type approval** [b-ISO/IEC 17000]: See approval, clause 3.1.7.
+
+**3.1.58 unilateral arrangement** [b-ISO/IEC 17000]: Arrangement whereby one party recognizes or accepts the conformity assessment results of another party.
+
+### **3.2 Terms defined in this Recommendation**
+
+None.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------|-----------------------------------------------|
+| C&I | Conformance and Interoperability |
+| ICS | Implementation Conformance Statement |
+| ICT | Information and Communication Technology |
+| IUT | Implementation Under Test |
+| NGN | Next Generation Network |
+| NMS | NGN Monitoring System |
+| OSI | Open Systems Interconnection |
+| PICS | Protocol Implementation Conformance Statement |
+| QoSE | QoS Experienced/perceived by customer/user |
+| QoS | Quality of Service |
+| SDO | Standards Development Organization |
+
+## **5 Conventions**
+
+None.
+
+## Bibliography
+
+- [b-ITU-T E.800] Recommendation ITU-T E.800 (2008), *Definitions of terms related to quality of service.*
+- [b-ITU-T K.63] Recommendation ITU-T K.63 (2004), *Maintaining the suitability of production telecommunications equipment to its intended electromagnetic environment.*
+- [b-ITU-T M.60] Recommendation ITU-T M.60 (1993), *Maintenance terminology and definitions.*
+- [b-ITU-T Q.3900] Recommendation ITU-T Q.3900 (2006), *Methods of testing and model network architecture for NGN technical means testing as applied to public telecommunication networks.*
+- [b-ITU-T Q.3902] Recommendation ITU-T Q.3902 (2008), *Operational parameters to be monitored when implementing NGN technical means in public telecommunication networks.*
+- [b-ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts.*
+- [b-ITU-T Y.101] Recommendation ITU-T Y.101 (2000), *Global Information Infrastructure terminology: Terms and definitions.*
+- [b-ITU-T Y.2001] Recommendation ITU-T Y.2001 (2004), *General overview of NGN.*
+- [b-ITU-T Z.450] Recommendation ITU-T Z.450 (2008), *Quality aspects of protocol-related Recommendations.*
+- [b-IEC 60050-161] IEC 60050-161:1990, *International Electrotechnical Vocabulary. Chapter 161: Electromagnetic compatibility.*
+- [b-ISO/IEC 17000] ISO/IEC 17000:2004, *Conformity assessment – Vocabulary and general principles.*
+- [b-ISO/IEC 17050] ISO/IEC 17050 (All parts):2004, *Conformity assessment – Supplier's declaration of conformity.*
+- [b-ISO/IEC 17011] ISO/IEC 17011 (application): 2004, *Conformity assessment -- General requirements for accreditation bodies accrediting conformity assessment bodies*
+- [b-EU 765/2008/EC] EU 765/2008/EC, *setting out the requirements for accreditation and market surveillance relating to the marketing of products and repealing Regulation (EEC) No 339/93.*
+- [b-WTO] World Trade Organization – Glossary.
+- [b-WTO TBT Agreement] *WTO Agreement on Technical Barriers to Trade*, 2013.
+
+
+
+## **SERIES OF ITU-T RECOMMENDATIONS**
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22dc7ff0fb30f976cc1e576c45d2b7e65fa5ddc7
--- /dev/null
+++ b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055
+size 6859
diff --git a/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..234fa2ec1b615b6505529e8dad7a42a2ac83d1ed
--- /dev/null
+++ b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/5b4e774d63e0e0ed73801a9247755e5f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7af55adf847482378842af40f38f8831c33f3a1f2439f2bc5dba0f7f51641d3c
+size 176119
diff --git a/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c4a84cf1c701d79b8137cf0aee055540a14404c
--- /dev/null
+++ b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:56d267062a265d37ac909bb14738ac186cea3dfb76effb92fa1d0e58459d3b96
+size 129332
diff --git a/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c83bef6a54c065f408f42acdee65c9b1e14906aa
--- /dev/null
+++ b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c49340a76c6048b09f10dd92e8942468a6daeff4aa104e4fbc5025fef10b61a9
+size 67828
diff --git a/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f513772328e50b1948d3bc246303f8c257171a54
--- /dev/null
+++ b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91697ffaf35b214e91f16fc84832258291d7393860d0de1bebeef9316f8ffdc5
+size 65129
diff --git a/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d66f6c621af7d69398040ea657de311a6eec9afa
--- /dev/null
+++ b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:25030e59adcb53b5f8dabb82a21de4a0910bcf59fdd9eab6014d4e0d963b980e
+size 132914
diff --git a/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..21b6b0f52727e2bff55bd9e3ea7efbfafd13d17b
--- /dev/null
+++ b/marked/Q/T-REC-Q.3932.1-201506-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cfe67b022121301be058a3d90faf16f6ca9f34d5680d9b59121407823d8947d
+size 46176
diff --git a/marked/Q/T-REC-Q.3942.1-201304-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3942.1-201304-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ad98c6e45b6c52f074f0054407ca88a640d8f1d
--- /dev/null
+++ b/marked/Q/T-REC-Q.3942.1-201304-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58019f38be268f19eaa80c6d56d0f6b39d5741569a8f3ccc04117fa95d9c6465
+size 4016
diff --git a/marked/Q/T-REC-Q.3942.1-201304-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3942.1-201304-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c915e2ced19dbd1b40007f7cd29be15cc71ff066
--- /dev/null
+++ b/marked/Q/T-REC-Q.3942.1-201304-I_PDF-E/raw.md
@@ -0,0 +1,429 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3942.1**
+
+(04/2013)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Signalling requirements and protocols for the NGN –
+Testing for next generation networks
+
+---
+
+**Conformance test specification for the
+terminating identification restriction using IP
+multimedia core network subsystem – Part 1:
+Protocol implementation conformance
+statement**
+
+Recommendation ITU-T Q.3942.1
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## **SWITCHING AND SIGNALLING**
+
+| | |
+|---------------------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3999 |
+| General | Q.3000–Q.3029 |
+| Network signalling and control functional architecture | Q.3030–Q.3099 |
+| Network data organization within the NGN | Q.3100–Q.3129 |
+| Bearer control signalling | Q.3130–Q.3179 |
+| Signalling and control requirements and protocols to support attachment in NGN environments | Q.3200–Q.3249 |
+| Resource control protocols | Q.3300–Q.3369 |
+| Service and session control protocols | Q.3400–Q.3499 |
+| Service and session control protocols – supplementary services | Q.3600–Q.3649 |
+| NGN applications | Q.3700–Q.3849 |
+| Testing for next generation networks | Q.3900–Q.3999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## **Recommendation ITU-T Q.3942.1**
+
+# **Conformance test specification for the terminating identification restriction using IP multimedia core network subsystem – Part 1: Protocol implementation conformance statement**
+
+## **Summary**
+
+Recommendation ITU-T Q.3942.1 specifies the conformance test specification (applicable for network side and user side) for the protocol implementation conformance statement (PICS) for the terminating identification restriction (TIR) using IP multimedia (IM) core network (CN) subsystem.
+
+## **History**
+
+| Edition | Recommendation | Approval | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0 | ITU-T Q.3942.1 | 2013-04-29 | 11 |
+
+## **Keywords**
+
+PICS, TEST, TIP, TIR.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2013
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|---------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 2 |
+| 6 Guidance for completing the PICS proforma ..... | 2 |
+| 6.1 Purposes and structure..... | 2 |
+| 6.1.1 Abbreviations and conventions..... | 3 |
+| 6.2 Identification of the implementation ..... | 4 |
+| 6.3 Identification of ETSI TS 124 608 ..... | 5 |
+| 6.4 Global statement of conformance..... | 5 |
+| 6.5 Roles ..... | 6 |
+| 6.6 User role ..... | 6 |
+| 6.7 Network role..... | 6 |
+
+
+
+## Recommendation ITU-T Q.3942.1
+
+## Conformance test specification for the terminating identification restriction using IP multimedia core network subsystem – Part 1: Protocol implementation conformance statement
+
+## 1 Scope
+
+This Recommendation provides the protocol implementation conformance statement (PICS) proforma for the digital cellular telecommunications system (Phase 2+), the universal mobile telecommunications system (UMTS), LTE, terminating identification presentation (TIP) and terminating identification restriction (TIR) using IP multimedia (IM) core network (CN) subsystem and Protocol specification as defined in [ETSI TS 124 608] in compliance with the relevant requirements and in accordance with the relevant guidance given in [ITU-T X.296].
+
+## 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts* (twinned with ISO/IEC 9646-1).
+- [ITU-T X.296] Recommendation ITU-T X.296 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – Implementation conformance statements* (twinned with ISO/IEC 9646-7).
+- [ETSI TS 124 604] ETSI TS 124 604 (2012-07), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.604 Release 10)*.
+- [ETSI TS 124 608] ETSI TS 124 608 (2011-05), *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 Release 10)*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+- 3.1.1 **abstract test suite (ATS)**: [ITU-T X.290].
+- 3.1.2 **implementation under test (IUT)**: [ITU-T X.290].
+- 3.1.3 **PICS proforma**: [ITU-T X.290].
+
+- 3.1.4 **point of control and observation (PCO)**: [ITU-T X.290].
+- 3.1.5 **protocol implementation conformance statement (PICS)**: [ITU-T X.296].
+- 3.1.6 **system under test (SUT)**: [ITU-T X.290].
+- 3.1.7 **test purpose (TP)**: [ITU-T X.290].
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|--------|-----------------------------------------------|
+| AS | Application Server |
+| ATS | Abstract Test Suite |
+| CSCF | Call Session Control Function |
+| IUT | Implementation Under Test |
+| NNI | Network-Network Interface |
+| PICS | Protocol Implementation Conformance Statement |
+| S-CSCF | Serving CSCF |
+| SUT | System Under Test |
+| TIP | Terminating Identification Presentation |
+| TIR | Terminating Identification Restriction |
+| TP | Test Purpose |
+| TSS | Test Suite Structure |
+
+## 5 Conventions
+
+- is "protocol";
+- is "ETSI TS 124 608";
+- is "*Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 Release 10)*";
+- is "*Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification*".
+
+## 6 Guidance for completing the PICS proforma
+
+## 6.1 Purposes and structure
+
+The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in [ETSI TS 124 608] may provide information about the implementation in a standardized manner.
+
+The PICS proforma is subdivided into clauses for the following categories of information:
+
+- guidance for completing the PICS proforma;
+- identification of the implementation;
+- identification of [ETSI TS 124 608];
+
+- global statement of conformance;
+- roles;
+- user role;
+- major capabilities;
+- network role;
+- major capabilities;
+- CDIV capabilities.
+
+### 6.1.1 Abbreviations and conventions
+
+The PICS proforma contained in this clause is comprised of information in tabular form in accordance with the guidelines presented in [ITU-T X.296].
+
+#### Item column
+
+The item column contains a number which identifies the item in the table.
+
+##### Item description column
+
+The item description column describes in free text each respective item (e.g., parameters, timers, etc.). It implicitly means "is - supported by the implementation?".
+
+#### Status column
+
+The following notations, defined in [ITU-T X.296], are used for the status column:
+
+- o optional – the capability may be supported or not.
+- ci conditional – the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying an unique conditional status expression which is defined immediately following the table.
+- n/a not applicable – in the given context, it is impossible to use the capability.
+
+##### Reference column
+
+The reference column makes reference to [ETSI TS 124 608], except where explicitly stated otherwise.
+
+##### Support column
+
+The support column shall be filled in by the supplier of the implementation. The following common notations, defined in [ITU-T X.296], are used for the support column:
+
+- Y or y supported by the implementation.
+- N or n not supported by the implementation.
+- N/A, n/a or – no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status).
+
+If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to be able to answer that a capability is supported for one profile and not supported for another. In that case, the supplier shall enter the unique reference to a conditional expression, preceded by "?" (e.g., ?3). This expression shall be given in the space for comments provided at the bottom of the table. It uses predicates defined in the SCS, each of which refers to a single profile and which takes the value TRUE if and only if that profile is to be used.
+
+#### 6.1.2 Instructions for completing the PICS proforma
+
+The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an explicit answer shall be entered, in each of the supported column boxes provided, using the notation described in clause 6.1.1.
+
+If necessary, the supplier may provide additional comments in space at the bottom of the tables or separately.
+
+More detailed instructions are given at the beginning of the different clauses of the PICS proforma.
+
+## 6.2 Identification of the implementation
+
+Identification of the implementation under test (IUT) and the system in which it resides (the system under test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options.
+
+The product supplier information and client information should both be filled in if they are different.
+
+A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
+
+#### 6.2.1 Date of the statement
+
+| | |
+|-------------------------------|--|
+| Date of the statement: | |
+|-------------------------------|--|
+
+#### 6.2.2 Implementation under test (IUT) identification
+
+| | |
+|---------------------|--|
+| IUT name: | |
+| IUT version: | |
+
+#### 6.2.3 System under test (SUT) identification
+
+| | |
+|--------------------------------|--|
+| SUT name: | |
+| Hardware configuration: | |
+| Operating system: | |
+
+#### 6.2.4 Product supplier
+
+| | |
+|--------------------------------|--|
+| Name: | |
+| Address: | |
+| Telephone number: | |
+| Facsimile number: | |
+| E-mail address | |
+| Additional information: | |
+
+#### 6.2.5 Client (if different from product supplier)
+
+| | |
+|--------------------------------|--|
+| Name: | |
+| Address: | |
+| Telephone number: | |
+| Facsimile number: | |
+| E-mail address | |
+| Additional information: | |
+
+#### 6.2.6 PICS contact person
+
+A person to be contacted if there are any queries concerning the content of the PICS.
+
+| | |
+|--------------------------------|--|
+| Name: | |
+| Address: | |
+| Telephone number: | |
+| Facsimile number: | |
+| E-mail address | |
+| Additional information: | |
+
+## 6.3 Identification of ETSI TS 124 608
+
+This PICS proforma applies to the following standard:
+
+ETSI TS 124 608 (2011-05): *Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 Release 10).*
+
+## 6.4 Global statement of conformance
+
+| | |
+|----------------------------------------------------|-----------------|
+| | (Yes/No) |
+| Are all mandatory capabilities implemented? | |
+
+NOTE – Answering "No" to this question indicates non-conformance to the specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming, on pages attached to the PICS proforma.
+
+## 6.5 Roles
+
+**Table 6.5-1 – Roles**
+
+| Item | Role | Reference | Status | Support |
+|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|---------|
+| 1 | Is the implementation an originating user equipment? | 4.5.2.1 | o | |
+| 2 | Is the implementation a terminating user equipment? | 4.5.2.12 | o | |
+| 3 | Is the implementation an application server (AS) serving the terminating identification presentation (TIP) and terminating identification restriction (TIR) | 4.5.2.9 | o | |
+| Comments: | | | | |
+
+### 6.6 User role
+
+This clause contains the PICS proforma tables related to the user role. They need to be completed only for user equipment implementations:
+
+Prerequisite: 6.5.1/1 – user role
+
+#### 6.6.1 Major capabilities
+
+**Table 6.6-1 – User Equipment capabilities**
+
+| Item | Call direction | Reference | Status | Support |
+|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-----------|--------|---------|
+| 1 | Does the user equipment support the "from-change" tag in the supported header? | 4.5.2.12 | c21 | |
+| 2 | [2/6] Does the terminating user equipment send an UPDATE request if a "from-change" tag was received in the initial INVITE? | 4.5.2.12 | c22 | |
+| c21: IF 6.5.1/1 THEN o ELSE n/a.
c22: IF 6.5.1/2 THEN o ELSE n/a. | | | | |
+| Comments: | | | | |
+
+### 6.7 Network role
+
+This clause contains the PICS proforma tables related to the network role. They need to be completed only for application server implementations:
+
+Prerequisite: 6.5.1/2 – user role
+
+#### 6.7.1 Major capabilities
+
+**Table 6.7-1 – Network capabilities**
+
+| Item | Call direction | Reference | Status | Support |
+|------|-------------------------------------------------------------------------------------|-------------------|--------|---------|
+| 1 | Is the network able to divert a call? | [ETSI TS 124 604] | o | |
+| 2 | Does the network support the "special arrangement" for the terminating user? | 4.5.2.9 | o | |
+| 3 | Does the network support the terminating identification presentation (TIP) service? | 4.3.1.1 | o | |
+
+**Table 6.7-1 – Network capabilities**
+
+| Item | Call direction | Reference | Status | Support |
+|-----------|------------------------------------------------------------------------------------|-----------|--------|---------|
+| 4 | Does the network support the terminating identification restriction (TIR) service? | 4.3.1.2 | o | |
+| 5 | Does the network support the "TIR service in temporary mode"? | 4.3.1.2 | o | |
+| 6 | Does the network support the "TIR service in permanent mode"? | 4.3.1.2 | o | |
+| 7 | Does the network support the "override category for the TIR service"? | 4.6.3 | o | |
+| 8 | Does the network support the "special arrangement" for the terminating user? | 4.5.2.9 | o | |
+| Comments: | | | | |
+
+Prerequisite: 6.7.1/4 – Major capabilities
+
+#### 6.7.2 CDIV capabilities
+
+**Table 6.7-2 – CDIV network capabilities**
+
+| Item | Call direction | Reference | Status | Support |
+|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------|---------|
+| 1 | Is the subscription option " Originating user receives notification that his communication has been diverted (forwarded or deflected)" supported? | 4.3.1 [ETSI TS 124 604] | c31 | |
+| 2 | Is the subscription option "Served user allows the presentation of diverted to URI to originating user in diversion notification" supported? | 4.3.1 [ETSI TS 124 604] | c32 | |
+| c31: IF 6.7.1/4 THEN o ELSE n/a. | | | | |
+| c32: IF 6.7.1/4 AND 6.7.2/1 THEN o ELSE n/a. | | | | |
+| Comments: | | | | |
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d29af6b3efa454466288abe7adb598afea67a560
--- /dev/null
+++ b/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90e13aa5f19f8f8ba4967cca9bc86436bd756efed037db0e0a3358f1b22aee0b
+size 18039
diff --git a/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd85c5f0cf29767d5fce2cdb865aece52387c01d
--- /dev/null
+++ b/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09082581f21d9548df66739aba3c0950a4cd19b319365b8f1c69a3129a386b3c
+size 4070
diff --git a/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..799ac3ae815937e4ca873ed71a83e009de22c809
--- /dev/null
+++ b/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:54b9554f8ef5611be2355a8ec5ba9ff6d479c62866d0765caf7cf3805f61fb6a
+size 18085
diff --git a/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ea88d823d7b794efa8c130a0d8c0d7e10ee402f
--- /dev/null
+++ b/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d116710790c174d5f59e2111ba81d993559c2f37df2b26376a23ccdcf5d4af82
+size 17680
diff --git a/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4c57b76c1b383a6e5269c2be3ee51aefd5391ab
--- /dev/null
+++ b/marked/Q/T-REC-Q.3942.2-201506-I_PDF-E/raw.md
@@ -0,0 +1,539 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3942.2**
+
+(06/2015)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for next generation networks
+
+---
+
+**Conformance test specification for the terminating identification restriction using IP multimedia core network subsystem – Part 2: Network side; Test suite structure and test purposes**
+
+Recommendation ITU-T Q.3942.2
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T Q.3942.2
+
+# Conformance test specification for the terminating identification restriction using IP multimedia core network subsystem – Part 2: Network side; Test suite structure and test purposes
+
+## Summary
+
+Recommendation ITU-T Q.3942.2v1 specifies part 2 of the test suite structure (TSS) and test purposes (TP) for the terminating identification restriction (TIR) using IP multimedia core network subsystem; conformance test specification, applicable for the network side.
+
+The version number, v1, indicates that this is version one of Recommendation ITU-T Q.3942.2 and that it relates to release 10 of the relevant 3GPP/ETSI standard.
+
+This Recommendation contains the test specifications against requirements which are represented in Recommendation ITU-T Q.3617v1, "Terminating identification presentation and terminating identification restriction using IP multimedia core network subsystem. Protocol specification".
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3942.2 | 2015-06-13 | 11 | 11.1002/1000/12499 |
+
+## Keywords
+
+IMS, network side, session description protocol, SDP, session initiation protocol, SIP, terminating identification presentation, terminating identification restriction, testing, TIP, TIR, TSS&TP, user side.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|----------------------------------------------------------------------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 2 |
+| 6 Test suite structure (TSS) ..... | 2 |
+| 6.1 Configuration..... | 2 |
+| 7 Test purposes (TP)..... | 3 |
+| 7.1 Introduction ..... | 3 |
+| 7.2 TPs for terminating identification presentation (TIP) and terminating
identification restriction (TIR) network role ..... | 4 |
+| 7.3 Interaction with other services..... | 9 |
+
+
+
+## Recommendation ITU-T Q.3942.2
+
+## Conformance test specification for the terminating identification restriction using IP multimedia core network subsystem – Part 2: Network side; Test suite structure and test purposes
+
+## 1 Scope
+
+This Recommendation specifies part 2 of the test suite structure (TSS) and test purposes (TP) which can be used for testing against [ITU-T Q.3617] and in accordance with the relevant guidance given in [ITU-T X.290].
+
+This Recommendation contains the test specifications against requirements that are represented in [ITU-T Q.3617].
+
+## 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T Q.3617] Recommendation ITU-T Q.3617v1 (2015), *Terminating identification presentation and terminating identification restriction using IP multimedia core network subsystem. Protocol specification.*
+- [ITU-T Q.3942.1] Recommendation ITU-T Q.3942.1 (2013), *Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification; Part 1: Protocol Implementation Conformance Statement (PICS).*
+- [ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts.*
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+- 3.1.1 **implementation under test (IUT)** [ITU-T X.290]
+- 3.1.2 **protocol implementation conformance statement (PICS)** [ITU-T X.290]
+- 3.1.3 **system under test (SUT)** [ITU-T X.290]
+- 3.1.4 **test purpose (TP)** [ITU-T X.290]
+
+### 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------|-----------------------------------------------|
+| AS | Application Server |
+| CDIV | Communication Diversion |
+| IUT | Implementation Under Test |
+| PICS | Protocol Implementation Conformance Statement |
+| SUT | System Under Test |
+| TIP | Terminating Identification Presentation |
+| TIR | Terminating Identification Restriction |
+| TP | Test Purposes |
+| TSS | Test Suite Structure |
+| UE | User Equipment |
+| URI | Universal Resource Identifier |
+
+## 5 Conventions
+
+None.
+
+## 6 Test suite structure (TSS)
+
+The test suit structure is described in Figure 6-1.
+
+| | | |
+|----------------|---------------|--------------------|
+| Network entity | OrigAS | TIP_N01_xxx |
+| | DestAS | TIP_N02_xxx |
+| Interaction | | |
+| | CDIV | TIP_N03_xxx |
+
+Figure 6-1 – Test suite structure
+
+## 6.1 Configuration
+
+The scope of this Recommendation is to test the signalling and procedural aspects of the stage 3 requirements as described in [ITU-T Q.3617]. The stage 3 description describes the requirements for several network entities. Therefore, several interfaces (reference points) are addressed to satisfy the test of the different entities.
+
+To test the appropriate entities, the configurations below are applicable.
+
+#### 6.1.1 Testing of the application server (AS)
+
+The AS entity is responsible for performing and managing services. The ISC interface is the appropriate access point for testing. See Figure 6-2.
+
+
+
+```
+
+graph LR
+ TS1[Test system] --- ISC1[ISC] --- AS[Application server
+Implementation under test]
+ AS --- ISC2[ISC] --- TS2[Test system]
+
+```
+
+Diagram of Figure 6-2: Applicable interface to test AS functionalities. A central green box labeled 'Application server' and 'Implementation under test' is connected to two cyan boxes labeled 'Test system'. The connections are labeled 'ISC'.
+
+Q.3942.2(15)\_F6-2
+
+**Figure 6-2 – Applicable interface to test AS functionalities**
+
+If the ISC interface is not accessible, it is also possible to perform the test of the terminating AS using any NNI (Mw, Mg, Mx) interface (see Figure 6-3) or originating AS using any NNI (Mw, Mg, Mx) interface (see Figure 6-4).
+
+
+
+```
+
+graph LR
+ TS1[Test system] --- MwMgMx[Mw, Mg, Mx] --- CSCF[CSCF
+(and/or AS)
+Implementation under test]
+ CSCF --- Gm --- TS2[Test system]
+
+```
+
+Diagram of Figure 6-3: Applicable interfaces for tests using a (generic) NNI interface for terminating AS. A central green box labeled 'CSCF (and/or AS)' and 'Implementation under test' is connected to two cyan boxes labeled 'Test system'. The left connection is labeled 'Mw, Mg, Mx' and the right connection is labeled 'Gm'.
+
+Q.3942.2(15)\_F6-3
+
+**Figure 6-3 – Applicable interfaces for tests using a (generic) NNI interface for terminating AS**
+
+
+
+```
+
+graph LR
+ TS1[Test system] --- Gm --- CSCF[CSCF
+(and/or AS)
+Implementation under test]
+ CSCF --- MwMgMx[Mw, Mg, Mx] --- TS2[Test system]
+
+```
+
+Diagram of Figure 6-4: Applicable interfaces for tests using a (generic) NNI interface for originating AS. A central green box labeled 'CSCF (and/or AS)' and 'Implementation under test' is connected to two cyan boxes labeled 'Test system'. The left connection is labeled 'Gm' and the right connection is labeled 'Mw, Mg, Mx'.
+
+Q.3942.2(15)\_F6-4
+
+**Figure 6-4 – Applicable interfaces for tests using a (generic) NNI interface for originating AS**
+
+## 7 Test purposes (TP)
+
+### 7.1 Introduction
+
+For each test requirement, a TP is defined.
+
+All protocol implementation conformance statement (PICS) items referred to in this clause are as specified in [ITU-T Q.3942.1] unless indicated otherwise by another numbered reference.
+
+#### 7.1.1 TP naming convention
+
+TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network (see Table 7-1).
+
+**Table 7-1 – TP identifier naming convention scheme**
+
+| | |
+|----------------------|---------------------------------------------------------------------|
+| Identifier: | <ss>_<iut><group>_<nnn> |
+| <ss> | = supplementary service: e.g., "TIP" |
+| <iut> | = type of IUT: N Network entity |
+| <group> | = group 2 digit field representing group reference according to TSS |
+| <nnn> | = sequential number (001-999) |
+
+### 7.2 TPs for terminating identification presentation (TIP) and terminating identification restriction (TIR) network role
+
+#### 7.2.1 Actions at the AS serving the originating user equipment (UE)
+
+| TSS
Signalling/OrigAS | TP
TIP_N01_001 | TIP/TIR reference
4.3.2 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/3 |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|------------------------------------------|-------------------------------------------------------------------------------|
+| Test purpose:
The originating user subscribes to the TIP service.
Ensure that for originating users that subscribe to TIP simulation service, if network provided identity information about the terminator is available, and if presentation is not restricted, the AS shall pass that information in any non 100 response message defined as SIP_MESSAGE_VA | | | |
+| Precondition: The originating user has subscribed to the TIP service. | | | |
+| SIP messages: SIP_MESSAGE_VA1: P-Asserted-Identity
SIP_MESSAGE_VA2: P-Asserted-Identity | | | |
+| Comments: | | | |
+| Test equipment | AS | Test equipment | |
+| INVITE | → | → INVITE | |
+| SIP_MESSAGE_VA 2 | ← | ← SIP_MESSAGE_VA 1 | |
+
+| TSS
Signalling/OrigAS | TP
TIP_N01_002 | TIP/TIR reference
4.5.2.4 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/3 |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|--------------------------------------------|-------------------------------------------------------------------------------|
+| Test purpose:
The originating user does not subscribe to the TIP service P-Asserted-Identity header not present.
Ensure that the implementation under test (IUT) acting as AS serving the originating user that does not subscribe to the TIP service removes any P-Asserted-Identity header fields included in the SIP response defined as SIP_MESSAGE_VA before forwarding the response | | | |
+| Precondition: The originating user has not subscribed to the TIP service. | | | |
+| SIP messages: SIP_MESSAGE_VA1: P-Asserted-Identity
SIP_MESSAGE_VA2: P-Asserted-Identity not present | | | |
+| Comments: | | | |
+| Test equipment | AS | Test equipment | |
+| INVITE | → | → INVITE | |
+| SIP_MESSAGE_VA 2 | ← | ← SIP_MESSAGE_VA 1 | |
+
+| TSS
Signalling/OrigAS | TP
TIP_N01_003 | TIP/TIR reference
4.5.2.4 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/3 |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|--------------------------------------------|-------------------------------------------------------------------------------|
+| Test purpose:
The originating user does not subscribe to the TIP service Privacy header not present.
Ensure that the IUT acting as AS serving the originating user that does not subscribe to the TIP service removes any Privacy header fields included in the SIP response defined as SIP_MESSAGE_VA before forwarding the response | | | |
+| Precondition: The originating user has not subscribed to the TIP service. | | | |
+| SIP messages: SIP_MESSAGE_VA1: Privacy: id
SIP_MESSAGE_VA2: Privacy header not present | | | |
+| Comments: | | | |
+| Test equipment | AS | Test equipment | |
+| INVITE | → | → INVITE | |
+| SIP_MESSAGE_VA 2 | ← | ← SIP_MESSAGE_VA 1 | |
+
+| TSS
Signalling/OrigAS | TP
TIP_N01_004 | TIP/TIR reference
4.6.3 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/3 AND
PICS 4.7.1/7 | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|------------------------------------------|-------------------------------------------------------------------------------------|-----------------------|-----------|-----------------------|--------|---|----------|-----------------|---|-------------------|
+| Test purpose:
The originating user has TIR override category.
Ensure that, if the originating user has the override category, the AS removes Privacy header fields restricting the presentation of the terminating identity and sends the P-Asserted-Identity header in the SIP response defined as SIP_MESSAGE_VA before forwarding the response | | | | | | | | | | | | |
+| Precondition: The originating user has subscribed to the TIP service and originating user has the override category. | | | | | | | | | | | | |
+| SIP messages: SIP_MESSAGE_VA1: P-Asserted-Identity, Privacy = id
SIP_MESSAGE_VA2: P-Asserted-Identity, no Privacy header or Privacy = none | | | | | | | | | | | | |
+| Comments:
| Test equipment | AS | Test equipment |
| INVITE | → | → INVITE |
| SIP_MESSAGE_VA2 | ← | ← SIP_MESSAGE_VA1 |
| | | | Test equipment | AS | Test equipment | INVITE | → | → INVITE | SIP_MESSAGE_VA2 | ← | ← SIP_MESSAGE_VA1 |
+| Test equipment | AS | Test equipment | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | |
+| SIP_MESSAGE_VA2 | ← | ← SIP_MESSAGE_VA1 | | | | | | | | | | |
+
+| Values for tests purposes TIP_N01_001 to TIP_N02_004 | |
+|------------------------------------------------------|----------------------|
+| VA_01 | 180 Ringing |
+| VA_02 | 183 Session progress |
+| VA_03 | 200 OK |
+
+| TSS
Signalling/OrigAS | TP
TIP_N01_005 | TIP/TIR reference
4.5.2.4 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/3 | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|--------------------------------------------|-----------------------------------------------------------------|-----------------------|-----------|-----------------------|--------------------------------|---|----------------------------------|
+| Test purpose:
The originating user subscribes to the TIP service. The "from-change" tag is passed on.
Ensure that the IUT acting as AS serving the originating user that subscribes to the TIP service passes on the "from change" tag within the Supported header in a received initial INVITE request before forwarding the request | | | | | | | | | |
+| Precondition: The originating user has subscribed to the TIP service | | | | | | | | | |
+| SIP message: INVITE1 Supported "from-change"
INVITE2 Supported "from-change" | | | | | | | | | |
+| Comments:
| Test equipment | AS | Test equipment |
| INVITE1 with "from-change" tag | → | → INVITE2 with "from-change" tag |
| | | | Test equipment | AS | Test equipment | INVITE1 with "from-change" tag | → | → INVITE2 with "from-change" tag |
+| Test equipment | AS | Test equipment | | | | | | | |
+| INVITE1 with "from-change" tag | → | → INVITE2 with "from-change" tag | | | | | | | |
+
+| TSS
Signalling/OrigAS | TP
TIP_N01_006 | TIP/TIR reference
4.5.2.4 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/3 | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|--------------------------------------------|-----------------------------------------------------------------|-----------------------|-----------|-----------------------|-----------------------------------|---|----------------------------------|
+| Test purpose:
The originating user subscribes to the TIP service. The "from-change" tag is not received.
Ensure that the IUT acting as AS serving the originating user that subscribes to the TIP service, receiving an initial INVITE request without the "from-change" tag in the Supported header, does not insert the "from-change" tag into the Supported header before forwarding the request | | | | | | | | | |
+| Precondition: The originating user has subscribed to the TIP service | | | | | | | | | |
+| SIP message: INVITE1 Supported "from-change" not included
INVITE2 Supported "from-change" not included | | | | | | | | | |
+| Comments:
| Test equipment | AS | Test equipment |
| INVITE1 without "from-change" tag | → | → INVITE2 with "from-change" tag |
| | | | Test equipment | AS | Test equipment | INVITE1 without "from-change" tag | → | → INVITE2 with "from-change" tag |
+| Test equipment | AS | Test equipment | | | | | | | |
+| INVITE1 without "from-change" tag | → | → INVITE2 with "from-change" tag | | | | | | | |
+
+| TSS
Signalling/OrigAS | TP
TIP_N01_007 | TIP/TIR reference
4.5.2.4 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/3 |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------|----------------------------------------------------------|
+| Test purpose:
The originating user does not subscribe to the TIP service. The "from-change" tag is removed from the Supported header.
Ensure that the IUT acting as AS serving the originating user that does not subscribe to the TIP service removes the "from-change" tag from the Supported header in a received initial INVITE request before forwarding the request | | | |
+| Precondition: The originating user has not subscribed to the TIP service | | | |
+| SIP message: INVITE1 Supported "from-change"
INVITE2 Supported "from-change" not included | | | |
+| Comments:
Test equipment | | | |
+| INVITE1 with "from-change" tag | → | → | INVITE2 |
+
+#### 7.2.2 Actions at the AS serving the terminating UE
+
+| TSS
Network entity/DestAS | TP
TIP_N02_001 | TIP/TIR reference
4.5.2.9 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/4 AND
PICS 4.7.1/6 |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------|------------------------------------------------------------------------------|
+| Test purpose:
The AS inserts the Privacy id value in the response if the response does not contain any Privacy. The terminating user subscribes to TIR in permanent mode.
Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "permanent mode", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA without a Privacy header, the AS shall insert a Privacy header with privacy value "id" before forwarding the response | | | |
+| Precondition: The terminating user has subscribed to the TIR service in permanent mode. | | | |
+| SIP messages: SIP_MESSAGE_VA1
SIP_MESSAGE_VA2: Privacy: id | | | |
+| Comments:
Test equipment | | | |
+| INVITE | → | → | INVITE |
+| SIP_MESSAGE_VA 2 | ← | ← | SIP_MESSAGE_VA 1 |
+
+| TSS
Network entity/DestAS | TP
TIP_N02_002 | TIP/TIR reference
4.5.2.9 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/4 AND
PICS 4.7.1/6 |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------|------------------------------------------------------------------------------|
+| Test purpose:
The AS inserts the Privacy id value in the response if the response contains Privacy "none". The terminating user subscribes to TIR in permanent mode.
Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "permanent mode", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA with a Privacy header "none", the AS shall remove the "none" and insert a Privacy header with privacy value "id" before forwarding the response | | | |
+| Precondition: The terminating user has subscribed to the TIR service in permanent mode. | | | |
+| SIP messages: SIP_MESSAGE_VA1 Privacy: none
SIP_MESSAGE_VA2: Privacy: id | | | |
+| Comments:
Test equipment | | | |
+| INVITE | → | → | INVITE |
+| SIP_MESSAGE_VA 2 | ← | ← | SIP_MESSAGE_VA 1 |
+
+| | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------|-----------------------|-----------|-----------------------|--------|---|----------|------------------|---|--------------------|
+| TSS
Network entity/DestAS | TP
TIP_N02_003 | TIP/TIR reference
4.5.2.9 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/4 AND
PICS 4.7.1/5 | | | | | | | | | |
+| Test purpose:
The AS inserts the Privacy value "id" in the response if the response does not contain any Privacy. The user subscribes TIR temporary mode with default "presentation restricted".
Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "temporary mode" with default value "presentation restricted", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA without a Privacy header, the AS shall insert a Privacy header with privacy value "id" before forwarding the response | | | | | | | | | | | | |
+| Precondition: The terminating user has subscribed to the TIR service in temporary mode "presentation restricted". | | | | | | | | | | | | |
+| SIP messages: SIP_MESSAGE_VA1
SIP_MESSAGE_VA2: Privacy: id | | | | | | | | | | | | |
+| Comments:
| Test equipment | AS | Test equipment |
| INVITE | → | → INVITE |
| SIP_MESSAGE_VA 2 | ← | ← SIP_MESSAGE_VA 1 |
| | | | Test equipment | AS | Test equipment | INVITE | → | → INVITE | SIP_MESSAGE_VA 2 | ← | ← SIP_MESSAGE_VA 1 |
+| Test equipment | AS | Test equipment | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | |
+| SIP_MESSAGE_VA 2 | ← | ← SIP_MESSAGE_VA 1 | | | | | | | | | | |
+
+| | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------|-----------------------|-----------|-----------------------|--------|---|----------|----------------|---|------------------|
+| TSS
Network entity/DestAS | TP
TIP_N02_004 | TIP/TIR reference
4.5.2.9 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/4 AND
PICS 4.7.1/5 | | | | | | | | | |
+| Test purpose:
The AS passes the Privacy value 'id' in the response. The user subscribes TIR temporary mode with default "presentation not restricted".
Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "temporary mode" with default value "presentation not restricted", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA with a Privacy header set to 'id', the AS shall pass Privacy header with the privacy value before forwarding the response | | | | | | | | | | | | |
+| Precondition: The terminating user has subscribed to the TIR service in temporary mode "presentation not restricted". | | | | | | | | | | | | |
+| SIP messages: SIP_MESSAGE_VA1: Privacy: id
SIP_MESSAGE_VA2: Privacy: id | | | | | | | | | | | | |
+| Comments:
| Test equipment | AS | Test equipment |
| INVITE | → | → INVITE |
| SIP_MESSAGE_VA | ← | ← SIP_MESSAGE_VA |
| | | | Test equipment | AS | Test equipment | INVITE | → | → INVITE | SIP_MESSAGE_VA | ← | ← SIP_MESSAGE_VA |
+| Test equipment | AS | Test equipment | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | |
+| SIP_MESSAGE_VA | ← | ← SIP_MESSAGE_VA | | | | | | | | | | |
+
+| Values for tests purposes TIP_N02_001 to TIP_N01_004 | |
+|-------------------------------------------------------------|----------------------|
+| VA_01 | 180 Ringing |
+| VA_02 | 183 Session progress |
+| VA_03 | 200 OK |
+
+| | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------|-----------------------|-----------|-----------------------|--------------------------------|---|-------------------------------------|
+| TSS
Network entity/DestAS | TP
TIP_N02_005 | TIP/TIR reference
4.5.2.9 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/4 AND
PICS 4.7.1/6 | | | | | | |
+| Test purpose:
The AS removes the "from-change" tag from the Supported header. The user subscribes TIR in permanent mode.
Ensure that the IUT acting as AS serving the terminating user that subscribes to the TIR service in "permanent mode" removes the "from-change" tag from the Supported header in a received initial INVITE request before forwarding the request | | | | | | | | | |
+| Precondition: The terminating user has subscribed to the TIR service in permanent mode | | | | | | | | | |
+| SIP messages: INVITE1 Supported: "from-change"
INVITE2 Supported without "from-change" | | | | | | | | | |
+| Comments:
| Test equipment | AS | Test equipment |
| INVITE1 with "from-change" tag | → | → INVITE2 without "from-change" tag |
| | | | Test equipment | AS | Test equipment | INVITE1 with "from-change" tag | → | → INVITE2 without "from-change" tag |
+| Test equipment | AS | Test equipment | | | | | | | |
+| INVITE1 with "from-change" tag | → | → INVITE2 without "from-change" tag | | | | | | | |
+
+| TSS
Signalling/DestAS | TP
TIP_N02_006 | TIP/TIR reference
4.5.2.9 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/8 |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------|----------------------------------------------------------|
+| Test purpose:
The terminating user is not subscribed to the "no screening" special arrangement From header value does not match. | | | |
+| Ensure that, if the IUT attempt to match the information in the From header with the set of registered public user identities for the served user and if no match is found, the AS changes the value of the From header in the UPDATE to the public user identity of the served user if the terminating user is not subscribed to the "no screening" special arrangement | | | |
+| SIP messages: INVITE: Supported: from-change
UPDATE1: From
UPDATE2: From | | | |
+| Precondition: Terminating user is not subscribed to the "no screening" special arrangement | | | |
+| Comments: | | | |
+| Test equipment | AS | | Test equipment |
+| INVITE | → | → | INVITE |
+| 180 Ringing | ← | ← | 180 Ringing |
+| 200 OK INVITE | ← | ← | 200 OK INVITE |
+| ACK | → | → | ACK |
+| UPDATE2 | ← | ← | UPDATE1 |
+| 200 OK UPDATE | → | → | 200 OK UPDATE |
+
+| TSS
Signalling/DestAS | TP
TIP_N02_007 | TIP/TIR reference
4.5.2.9 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/8 |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------|----------------------------------------------------------|
+| Test purpose:
The terminating user is not subscribed to the "no screening" special arrangement From header value matches. | | | |
+| Ensure that, if the IUT attempt to match the information in the From header with the set of registered public user identities for the served user and if a match is found, the AS passes the value of the From header in the UPDATE if the terminating user is not subscribed to the "no screening" special arrangement | | | |
+| SIP messages: INVITE: Supported: from-change
18x/200: Supported: from-change
UPDATE1: From
UPDATE2: From | | | |
+| Precondition: Terminating user is not subscribed to the "no screening" special arrangement. | | | |
+| Comments: | | | |
+| Test equipment | AS | | Test equipment |
+| INVITE | → | → | INVITE |
+| 180 Ringing | ← | ← | 180 Ringing |
+| 200 OK INVITE | ← | ← | 200 OK INVITE |
+| ACK | → | → | ACK |
+| UPDATE2 | ← | ← | UPDATE1 |
+| 200 OK UPDATE | → | → | 200 OK UPDATE |
+
+| TSS
Signalling/DestAS | TP
TIP_N02_008 | TIP/TIR reference
4.5.2.9 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/8 |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------|----------------------------------------------------------|
+| Test purpose:
The terminating user is subscribed to the "no screening" special arrangement. | | | |
+| Ensure that, if the IUT passes the information in the From header in the UPDATE request if the terminating user is subscribed to the "no screening" special arrangement | | | |
+| SIP messages: INVITE: Supported: from-change
18x/200: Supported: from-change
UPDATE1: From
UPDATE2: From | | | |
+| Precondition: Terminating user is subscribed to the "no screening" special arrangement. | | | |
+| Comments: | | | |
+| Test equipment | AS | | Test equipment |
+| INVITE | → | → | INVITE |
+| 180 Ringing | ← | ← | 180 Ringing |
+| 200 OK INVITE | ← | ← | 200 OK INVITE |
+
+| TSS
Signalling/DestAS | TP
TIP_N02_008 | TIP/TIR reference
4.5.2.9 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/8 |
+|--------------------------|-------------------|------------------------------|----------------------------------------------------------|
+| ACK → | → | ACK | |
+| UPDATE2 ← | ← | UPDATE1 | |
+| 200 OK UPDATE → | → | 200 OK UPDATE | |
+
+### 7.3 Interaction with other services
+
+#### 7.3.1 Communication diversion (CDIV) services
+
+| TSS
Interaction/CDIV | TP
TIP_N03_001 | TIP/TIR reference
4.6.7 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/1 AND
PICS 4.7.2/1 AND
PICS 4.7.2/2 | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|--------------------------------------------------------------------------------------------------|-----------------------------------|-----|-----------------------------------|----------|---|--------|-------------------------------|--|--|---------------------------------------------------------|--|--|--------------------|---|------------------|-----------------------------|--|--|
+| Test purpose:
Ensure that if the served (diverting) user of the CDIV service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed to the TIR service in permanent mode and the originating user has subscribed to the TIP service, no P-Asserted-Identity header including the universal resource identifier (URI) of the diverted-to user and no history-entry identifying the diverted-to user is sent within the SIP_MESSAGE_VA response to the originating user. The History-Info header entry identifying the diverted-to user is removed from the History-Info header | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: Test equipment (Diverting user) activates CDIV unconditional with option "originating user is notified of diversion with the diverted-to address" | | | | | | | | | | | | | | | | | | | | | |
+| SIP messages: 181: History-Info diverted-to URI not present
SIP_MESSAGE_VA 2
History-Info diverted-to URI not present
Privacy: id | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (originating user) | SUT | Test equipment (diverted-to user) |
| INVITE → | → | INVITE |
| 181 Call is being forwarded ← | | |
| History-Info header without URI of the diverted-to user | | |
| SIP_MESSAGE_VA 2 ← | ← | SIP_MESSAGE_VA 1 |
| without P-Asserted-Identity | | |
| | | | Test equipment (originating user) | SUT | Test equipment (diverted-to user) | INVITE → | → | INVITE | 181 Call is being forwarded ← | | | History-Info header without URI of the diverted-to user | | | SIP_MESSAGE_VA 2 ← | ← | SIP_MESSAGE_VA 1 | without P-Asserted-Identity | | |
+| Test equipment (originating user) | SUT | Test equipment (diverted-to user) | | | | | | | | | | | | | | | | | | | |
+| INVITE → | → | INVITE | | | | | | | | | | | | | | | | | | | |
+| 181 Call is being forwarded ← | | | | | | | | | | | | | | | | | | | | | |
+| History-Info header without URI of the diverted-to user | | | | | | | | | | | | | | | | | | | | | |
+| SIP_MESSAGE_VA 2 ← | ← | SIP_MESSAGE_VA 1 | | | | | | | | | | | | | | | | | | | |
+| without P-Asserted-Identity | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Interaction/CDIV | TP
TIP_N03_002 | TIP/TIR reference
4.6.7 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/1 AND
PICS 4.7.2/1 AND
PICS 4.7.2/2 | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------|--------------------------------------------------------------------------------------------------|-----------------------------------|-----|-----------------------------------|----------|---|--------|-------------------------------|--|--|---------------------------------------------------------|--|--|--------------------|---|------------------|-----------------------------|--|--|
+| Test purpose:
Ensure that if the served (diverting) user of the CDIV service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed to the TIR service in temporary mode default "presentation restricted" and the originating user has subscribed to the TIP service, when the diverted-to user has sent no Privacy header within the SIP_MESSAGE_VA response, no P-Asserted-Identity header including the URI of the diverted-to user is sent within the SIP_MESSAGE_VA response to the originating user. The History-Info header entry identifying the diverted-to user is removed from the History-Info header | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: Test equipment (Diverting user) activates CDIV unconditional with option "originating user is notified of diversion with the diverted-to address" | | | | | | | | | | | | | | | | | | | | | |
+| SIP messages: 181: History-Info diverted-to URI not present
SIP_MESSAGE_VA 2
History-Info diverted-to URI not present
Privacy: id | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (originating user) | SUT | Test equipment (diverted-to user) |
| INVITE → | → | INVITE |
| 181 Call is being forwarded ← | | |
| History-Info header without URI of the diverted-to user | | |
| SIP_MESSAGE_VA 2 ← | ← | SIP_MESSAGE_VA 1 |
| without P-Asserted-Identity | | |
| | | | Test equipment (originating user) | SUT | Test equipment (diverted-to user) | INVITE → | → | INVITE | 181 Call is being forwarded ← | | | History-Info header without URI of the diverted-to user | | | SIP_MESSAGE_VA 2 ← | ← | SIP_MESSAGE_VA 1 | without P-Asserted-Identity | | |
+| Test equipment (originating user) | SUT | Test equipment (diverted-to user) | | | | | | | | | | | | | | | | | | | |
+| INVITE → | → | INVITE | | | | | | | | | | | | | | | | | | | |
+| 181 Call is being forwarded ← | | | | | | | | | | | | | | | | | | | | | |
+| History-Info header without URI of the diverted-to user | | | | | | | | | | | | | | | | | | | | | |
+| SIP_MESSAGE_VA 2 ← | ← | SIP_MESSAGE_VA 1 | | | | | | | | | | | | | | | | | | | |
+| without P-Asserted-Identity | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Interaction/CDIV | TP
TIP_N03_003 | TIP/TIR reference
4.6.7 | Selection expression
PICS 4.5.1/3 AND
PICS 4.7.1/1 AND
PICS 4.7.2/1 AND
PICS 4.7.2/2 | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------|------------------------------------------|------------|------------------------------------------|--------|---|----------|-----------------------------|---|--|---------------------------------------------------------|--|--|------------------|---|--------------------|-----------------------------|--|-------------------|
+| Test purpose:
Ensure that if the served (diverting) user of the CDIV service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed to the TIR service in temporary mode default "presentation not restricted" and the originating user has subscribed to the TIP service, when the diverted-to user has send a Privacy header with value "id" within the SIP_MESSAGE_VA response, no P-Asserted-Identity header including the URI of the diverted-to user is sent within the SIP_MESSAGE_VA response to the originating user. The History-Info header entry identifying the diverted-to user is removed from the History -Info header | | | | | | | | | | | | | | | | | | | | | |
+| Precondition: Test equipment (Diverting user) activates CDIV unconditional with option "originating user is notified of diversion with the diverted-to address" | | | | | | | | | | | | | | | | | | | | | |
+| SIP messages: 181: History-Info diverted-to URI not present
SIP_MESSAGE_VA 1
Privacy: id
SIP_MESSAGE_VA 2
History-Info diverted-to URI not present
Privacy: id | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| Test equipment (originating user) | SUT | Test equipment (diverted-to user) |
| INVITE | → | → INVITE |
| 181 Call is being forwarded | ← | |
| History-Info header without URI of the diverted-to user | | |
| SIP_MESSAGE_VA 2 | ← | ← SIP_MESSAGE_VA 1 |
| without P-Asserted-Identity | | with Privacy "id" |
| | | | Test equipment (originating user) | SUT | Test equipment (diverted-to user) | INVITE | → | → INVITE | 181 Call is being forwarded | ← | | History-Info header without URI of the diverted-to user | | | SIP_MESSAGE_VA 2 | ← | ← SIP_MESSAGE_VA 1 | without P-Asserted-Identity | | with Privacy "id" |
+| Test equipment (originating user) | SUT | Test equipment (diverted-to user) | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | | | | | | | | | | |
+| 181 Call is being forwarded | ← | | | | | | | | | | | | | | | | | | | | |
+| History-Info header without URI of the diverted-to user | | | | | | | | | | | | | | | | | | | | | |
+| SIP_MESSAGE_VA 2 | ← | ← SIP_MESSAGE_VA 1 | | | | | | | | | | | | | | | | | | | |
+| without P-Asserted-Identity | | with Privacy "id" | | | | | | | | | | | | | | | | | | | |
+
+| Values for tests purposes TIP_N03_001 to TIP_N03_003 | |
+|-------------------------------------------------------------|----------------------|
+| VA_01 | 180 Ringing |
+| VA_02 | 183 Session progress |
+| VA_03 | 200 OK |
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Terminals and subjective and objective assessment methods |
+| Series Q | Switching and signaling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.3957-202504-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Q/T-REC-Q.3957-202504-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb
--- /dev/null
+++ b/marked/Q/T-REC-Q.3957-202504-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d
+size 7219
diff --git a/marked/Q/T-REC-Q.3957-202504-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Q/T-REC-Q.3957-202504-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8e076f029ec7ad836201b8f7351e99adc6deeb46
--- /dev/null
+++ b/marked/Q/T-REC-Q.3957-202504-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3d0126316039317d899518843161fa2f8ec96b4156ee2737ce9595bc15cfcf5
+size 28020
diff --git a/marked/Q/T-REC-Q.3963-202004-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.3963-202004-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd85c5f0cf29767d5fce2cdb865aece52387c01d
--- /dev/null
+++ b/marked/Q/T-REC-Q.3963-202004-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09082581f21d9548df66739aba3c0950a4cd19b319365b8f1c69a3129a386b3c
+size 4070
diff --git a/marked/Q/T-REC-Q.3963-202004-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.3963-202004-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1aa516753537cd6fd66a802426f04723817fde6c
--- /dev/null
+++ b/marked/Q/T-REC-Q.3963-202004-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:704518e42afd7d4aa55db55558700f6ec3a9aacbd5e69cf85d36162de7669591
+size 36467
diff --git a/marked/Q/T-REC-Q.3963-202004-I_PDF-E/raw.md b/marked/Q/T-REC-Q.3963-202004-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..6478007daee8d29c57de545cf32948fae8260c2b
--- /dev/null
+++ b/marked/Q/T-REC-Q.3963-202004-I_PDF-E/raw.md
@@ -0,0 +1,318 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.3963**
+
+(04/2020)
+
+SERIES Q: SWITCHING AND SIGNALLING, AND
+ASSOCIATED MEASUREMENTS AND TESTS
+
+Testing specifications – Testing specifications for next
+generation networks
+
+---
+
+**Compatibility testing of software-defined
+networking (SDN)-based equipment using the
+OpenFlow protocol**
+
+Recommendation ITU-T Q.3963
+
+# ITU-T Q-SERIES RECOMMENDATIONS **SWITCHING AND SIGNALLING, AND ASSOCIATED MEASUREMENTS AND TESTS**
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3709 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR SDN | Q.3710–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+| Testing specifications for IMT-2020 and IoT | Q.4060–Q.4099 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2020 | Q.5000–Q.5049 |
+| COMBATING COUNTERFEITING AND STOLEN ICT DEVICES | Q.5050–Q.5069 |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T Q.3963
+
+# Compatibility testing of software-defined networking (SDN)-based equipment using the OpenFlow protocol
+
+## Summary
+
+One of the challenges in the area of software-defined networking (SDN) is to ensure the compatibility of solutions from various producers at all layers of the network function virtualization (NFV) and SDN network. There are many SDN solutions, both open-source and proprietary; each is unique in terms of the software implementation by the object, which, even if it delivers the functionality required by the standard, is still at risk in certain cases of the network failing or holding up traffic owing to a loss of the OpenFlow connection between the SDN switch and controller of the programmable network, exposing the operator (network owner) to the risk of financial and other losses (e.g., of customers).
+
+To prevent such situations, when installing equipment on a telecommunication network, the operator tests the equipment in question for compatibility with other devices already operating on the network. In the case of SDN, tests are required to check the compatibility of OpenFlow protocol modules of each version installed on the device being tested.
+
+Recommendation ITU-T Q.3963 has been developed with a view to harmonizing existing practices in the area of compatibility testing of devices using the OpenFlow operation system (OS).
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.3963 | 2020-04-29 | 11 | 11.1002/1000/14245 |
+
+## Keywords
+
+Integration testing, openFlow, software-defined networking.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2020
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 2 |
+| 6 Overview..... | 2 |
+| 7 General structure of OpenFlow device testing ..... | 2 |
+| 7.1 Test scenario for system start ..... | 3 |
+| 7.2 Test scenario for the system in operation ..... | 3 |
+| 8 Functions of elements ..... | 4 |
+| 8.1 Control server ..... | 4 |
+| 8.2 Test module A ..... | 4 |
+| 8.3 Test module B..... | 5 |
+| Bibliography..... | 6 |
+
+
+
+## Recommendation ITU-T Q.3963
+
+## Compatibility testing of software-defined networking (SDN)-based equipment using the OpenFlow protocol
+
+# 1 Scope
+
+This Recommendation describes compatibility testing of devices using the OpenFlow protocol. It also specifies the means and methods for testing using a model network under laboratory conditions.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+[ITU-R M.2083-0] Recommendation ITU-R M.2083-0 (2015), *IMT Vision – Framework and overall objectives of the future development of IMT for 2020 and beyond*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 control plane** [b-ITU-T Y.2011]: The set of functions that controls the operation of entities in the stratum or layer under consideration, plus the functions required to support this control.
+
+**3.1.2 data plane** [b-ITU-T Y.2011]: The set of functions used to transfer data in the stratum or layer under consideration.
+
+**3.1.3 future network (FN)** [b-ITU-T Y.3001]: A network able to provide services, capabilities, and facilities difficult to provide using existing network technologies. A future network is either:
+
+- a) a new component network or an enhanced version of an existing one, or
+- b) a heterogeneous collection of new component networks or of new and existing component networks that is operated as a single network.
+
+**3.1.4 IMT-2020** [b-ITU-T Y.3100]: Systems, system components, and related aspects that support to provide far more enhanced capabilities than those described in [b-ITU-R M.1645].
+
+NOTE – [b-ITU-R M.1645] defines the framework and overall objectives of the future development of IMT-2000 and systems beyond IMT-2000 for the radio access network.
+
+**3.1.5 network function** [b-ITU-T Y.3100]: In the context of IMT-2020, a processing function in a network.
+
+NOTE 1 – Network functions include but are not limited to network node functionalities, e.g., session management, mobility management and transport functions, whose functional behaviour and interfaces are defined.
+
+NOTE 2 – Network functions can be implemented on a dedicated hardware or as virtualized software functions.
+
+NOTE 3 – Network functions are not regarded as resources, but rather any network functions can be instantiated using the resources.
+
+**3.1.6 software-defined networking** [b-ITU-T Y.3300]: A set of technologies that enables to directly program, orchestrate, control and manage network resources, which facilitates the design, delivery and operation of network services in a dynamic and scalable manner.
+
+## **3.2 Terms defined in this Recommendation**
+
+None.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-----|--------------------------------------|
+| FN | Future Network |
+| ICT | Information Communication Technology |
+| NFV | Network Function Virtualization |
+| OS | Operation System |
+| SDN | Software-Defined Networking |
+
+# **5 Conventions**
+
+None.
+
+# **6 Overview**
+
+Future networks (FNs), according to clause 3.1.3, are able to provide different kinds of services that are difficult to supply using existing network technologies. Responsibility for ensuring the required network performance falls on the infrastructure of IMT-2020 telecommunication networks, which according to [ITU-R M.2083-0], should be based on software-defined networking (SDN) and network function virtualization (NFV), which in turn help to ensure high-level network scaling and flexibility in management, allowing delivery of new services. Thus, a large-scale implementation of such network technologies is expected.
+
+In this regard, this Recommendation specifies testing for compatibility of devices that support the protocols in order to maintain a multi-vendor approach to building information communication technology (ICT) infrastructure. As part of this Recommendation, the testing structure, types of testing, test scenarios, functions of the main elements and notes are given.
+
+# **7 General structure of OpenFlow device testing**
+
+Considering the framework of SDN defined in clause 3.1.6, Figure 1 shows the general structure of OpenFlow device testing. There are main functional elements of this structure: controller SDN, operation system (OS), test modules (A and B), control server and OpenFlow switch.
+
+The program-defined network controller is a complex object of the general architecture of SDN, which is responsible for both the functioning of the network as a whole, and for the operation of individual services and applications. One of the requirements for the designed and developed software-configured network is its fault tolerance, which depends on the correctness and stability of work between the OpenFlow controller and the OpenFlow device (switch) in various cases of operation.
+
+
+
+Diagram illustrating the general structure of OpenFlow device testing. The diagram shows a stack of layers for a controller: 'Controller SDN' and 'Test module A' on top of 'Operation system (OS)', which is on top of 'Server hardware'. Below this stack is a 'Network (Control layer)' cloud connected to a 'Control layer' box. The 'Control layer' box is connected to 'Test module B', which is connected to an 'OpenFlow switch' (represented by an icon with ports and an 'X'). A dashed orange arrow points from 'Test module A' to 'Test module B'. A solid blue arrow points from the 'Network (Control layer)' cloud to the 'Operation system (OS)' layer. A solid blue arrow points from the 'Control layer' box to the 'Network (Control layer)' cloud. A solid blue arrow points from the 'OpenFlow switch' to the 'Network (Control layer)' cloud. A solid blue arrow points from 'Test module B' to the 'OpenFlow switch'. The label 'Q.3963(20)\_F01' is at the bottom right of the diagram.
+
+**Figure 1 – The general structure of OpenFlow device testing**
+
+There are two types of test scenarios for compatibility testing of SDN-based equipment using the OpenFlow protocol:
+
+- system start;
+- system in operation.
+
+## 7.1 Test scenario for system start
+
+This type of test scenario combines various approaches to testing the operation of the OpenFlow protocol modules on each of the devices under study during their entry into operation. According to the specifications of the OpenFlow protocol, when devices are connected, the devices send an OpenFlow-hello message, while sending the maximum version of the supported OpenFlow protocol. Agreement is then sought on the version of the protocol to be used. Ultimately, both devices (controller and switch) must agree on the version of the protocol being used; usually, the minimum version is selected, supported by one of the devices. During the scenario, test module A intercepts OpenFlow traffic and sends it to the control server for subsequent analysis.
+
+## 7.2 Test scenario for the system in operation
+
+This type of testing includes a number of integration tests to verify the correct operation of the OpenFlow protocol modules in various modes: operational state (there is no high traffic activity at the data plane level) and high load (the high load generated traffic on the data plane level). As part of this test, the correctness of sending OpenFlow messages of various types approved in the OpenFlow specification [b-ONF] is checked. According to [b-ONF], the OpenFlow switch protocol supports three message types, each with multiple sub-types.
+
+### 7.2.1 Controller-to-switch
+
+Controller-to-switch messages are initiated by the controller and used to directly manage or inspect the state of the switch. These are the messages specified in OpenFlow:
+
+- Features;
+- Configuration;
+- Modify-State;
+
+- Read-State;
+- Packet-Out;
+- Barrier;
+- Role-request;
+- Asynchronous-Configuration.
+
+### 7.2.2 Asynchronous
+
+Asynchronous messages are initiated by the switch and used to update the controller about network events and changes to the switch state. These are the messages specified in OpenFlow:
+
+- Packet-In;
+- Packet-Out;
+- Flow-Mod;
+- Flow-Removed;
+- Port-Status.
+
+### 7.2.3 Symmetric
+
+Symmetric messages are initiated by either the switch or the controller and sent without solicitation. These are the messages specified in OpenFlow:
+
+- Hello;
+- Echo;
+- Experimenter.
+
+As part of the integration testing of OpenFlow devices, performance of comprehensive testing, which includes checking the correctness of the processing of messages indicated in the foregoing, is required. This includes consideration of the different load level at the data plane level of the SDN network.
+
+As part of this test, special attention needs to be paid to verifying the operation of Packet-In message generation logic by the SDN switch. According to the specifications of [b-ONF], this type of message is used to encapsulate messages at the data plane level to the management level (SDN controller). Thus, with the incorrect implementation of the OpenFlow protocol (in terms of implementing the logic of generating and processing Packet-In messages) by one of the devices, there is a risk of disrupting the SDN controller and violating security rules.
+
+# 8 Functions of elements
+
+The architecture of the system for testing (Figure 1) includes the elements specified in clauses 8.1 to 8.3.
+
+## 8.1 Control server
+
+This server provides monitoring and control of tests. This server implements a test module management system (A and B), the functions of generating test scenarios, and stores basic test scenarios. In addition, the server implements functions for analysing the information obtained from test modules (A and B).
+
+## 8.2 Test module A
+
+This module is a software solution for an OS in which an SDN controller is deployed. The main goal of this module is to intercept the OpenFlow traffic that comes to the controller port or is generated by the SDN controller for switches.
+
+## **8.3 Test module B**
+
+This module is a software or software-hardware solution, which works on the SDN data plane, and is connected with the OpenFlow switch. Also, module B is connected with the control server for management purposes. The main goal of this module is to generate traffic to the OpenFlow switch. Also, on test module B, another OpenFlow switch (software component) can be realized, if necessary, for interconnection testing between switches.
+
+# Bibliography
+
+- [b-ITU-T Y.2011] Recommendation ITU-T Y.2011 (2004), *General principles and general reference model for Next Generation Networks*.
+- [b-ITU-T Y.2012] Recommendation ITU-T Y.2012 (2010), *Functional requirements and architecture of next generation networks*.
+- [b-ITU-T Y.3001] Recommendation ITU-T Y.3001 (2011), *Future networks: Objectives and design goals*.
+- [b-ITU-T Y.3100] Recommendation ITU-T Y.3101 (2017), *Terms and definitions for IMT-2020 network*.
+- [b-ITU-T Y.3300] Recommendation ITU-T Y.3300 (2014), *Framework of software-defined networking*.
+- [b-ITU-R M.1645] Recommendation ITU-R M.1645 (06/2003), *Framework and overall objectives of the future development of IMT-2000 and systems beyond IMT-2000*.
+- [b-ONF] Open Networking Foundation (2020). *ONF SDN projects*. Available [viewed 2020-06-10] at: .
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/Q/T-REC-Q.4-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7
--- /dev/null
+++ b/marked/Q/T-REC-Q.4-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
+size 7392
diff --git a/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/raw.md b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..85bc7becaba49e360d38a41a07ad1f8c71b0c0eb
--- /dev/null
+++ b/marked/Q/T-REC-Q.400-Q.490-198811-I_PDF-E/raw.md
@@ -0,0 +1,4732 @@
+
+
+
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**Q.400-Q.490**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(11/1988)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+# --- **Specifications of Signalling System R2**
+
+ITU-T Recommendations Q.400-Q.490
+
+(Formerly CCITT Recommendations)
+
+---
+
+## ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------------------------|--------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
+| Basic Recommendations | Q.4-Q.9 |
+| Numbering plan and dialling procedures in the international service | Q.10-Q.11 |
+| Routing plan for international service | Q.12-Q.19 |
+| General Recommendations relative to signalling and switching systems (national or international) | Q.20-Q.34 |
+| Tones for use in national signalling systems | Q.35-Q.39 |
+| General characteristics for international telephone connections and circuits | Q.40-Q.47 |
+| Signalling for satellite systems | Q.48-Q.49 |
+| Signalling for circuit multiplication equipment | Q.50-Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
+| Methodology | Q.60-Q.67 |
+| Basic services | Q.68-Q.79 |
+| Supplementary services | Q.80-Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
+| General clauses | Q.100-Q.109 |
+| Transmission clauses for signalling | Q.110-Q.114 |
+| Control of echo suppressors | Q.115 |
+| Abnormal conditions | Q.116-Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 |
+| Specifications of Signalling System No. 4 | Q.120-Q.139 |
+| Specifications of Signalling System No. 5 | Q.140-Q.179 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 |
+| DIGITAL EXCHANGES | Q.500-Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
+| General considerations | Q.600-Q.609 |
+| Logic procedures | Q.610-Q.697 |
+| Interworking of Signalling Systems No. 7 and No. 6 | Q.698 |
+| Interworking between Digital Subscriber Signalling System No. 1 and Signalling System No. 7 | Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.799 |
+| Q3 INTERFACE | Q.800-Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
+| INTELLIGENT NETWORK | Q.1200-Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700-Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900-Q.1999 |
+| BROADBAND ISDN | Q.2000-Q.2999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# **Specifications of Signalling System R2**
+
+## **Summary**
+
+Signalling System R2 is used as an international signalling system within international regions. Suitable for both automatic and semi-automatic working, it provides sufficient signals in both directions to permit the transmission of numerical and other information relating to the called and calling subscribers' lines and to increase routing facilities.
+
+System R2 is specified for one-way operation on analogue and digital transmission systems and for both-way operation on digital transmission systems. Distinction is made between line signalling (supervisory signals) and interregister signalling (call set-up control signals). Versions of line signalling are specified for use on 4-wire carrier or PCM circuits. Nevertheless, the interregister signalling specified can also be used on 2-wire circuits.
+
+The interregister signalling is a compelled multifrequency code system which offers the possibility of end-to-end signalling.
+
+## **Source**
+
+ITU-T Recommendations Q.400-490 were prepared by CCITT Study Group XI (1985-1988) and approved by WTSC in Melbourne on 25 November 1988. Those texts were originally published in Blue Book, Fascicle VI.4.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendations may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendations, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendations. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2002
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
+
+## CONTENTS
+
+# Specifications of Signalling System R2
+
+| Rec. No. | | Page |
+|----------------|----------------------------------------------------------------------------------------------------------------------|------|
+| INTRODUCTION – | General ..... | 1 |
+| SECTION 1 – | Definitions and functions of signals | |
+| Q.400 | 1.1 Forward line signals ..... | 5 |
+| | 1.2 Backward line signals ..... | 5 |
+| | 1.3 Forward register signals ..... | 6 |
+| | 1.4 Backward register signals ..... | 7 |
+| SECTION 2 – | Line signalling, analogue version | |
+| Q.411 | 2.1 Line signalling code ..... | 9 |
+| Q.412 | 2.2 Clauses for exchange line signalling equipment ..... | 10 |
+| | 2.3 Clauses for transmission line signalling equipment ..... | 16 |
+| Q.414 | 2.3.1 Signal sender ..... | 16 |
+| Q.415 | 2.3.2 Signal receiver ..... | 18 |
+| Q.416 | 2.4 Interruption control ..... | 20 |
+| SECTION 3 – | Line signalling, digital version | |
+| Q.421 | 3.1 digital line signalling code ..... | 25 |
+| Q.422 | 3.2 clauses for exchange line signalling equipment ..... | 26 |
+| Q.424 | 3.3 protection against the effects of faulty transmission ..... | 31 |
+| Q.430 | 3.5 conversion between analogue and digital versions
of system R2 line signalling ..... | 32 |
+| SECTION 4 – | Interregister signalling | |
+| Q.440 | 4.1 General ..... | 53 |
+| Q.441 | 4.2 Signalling code ..... | 56 |
+| Q.442 | 4.3 Pulse transmission of backward signals A-3, A-4, A-6 or A-15 ..... | 66 |
+| | 4.4 Multifrequency signalling equipment ..... | 67 |
+| Q.450 | 4.4.1 General ..... | 67 |
+| Q.451 | 4.4.2 Definitions ..... | 68 |
+| Q.452 | 4.4.3 Requirements relating to transmission conditions ..... | 70 |
+| Q.454 | 4.4.4 The sending part of the multifrequency signalling equipment ..... | 71 |
+| Q.455 | 4.4.5 The receiving part of the multifrequency equipment ..... | 72 |
+| | 4.5 Range, speed and reliability of interregister signalling ..... | 75 |
+| Q.457 | 4.5.1 Range of interregister signalling ..... | 75 |
+| Q.458 | 4.5.3 Reliability of interregister signalling ..... | 79 |
+| | Annexes to Section 4: | |
+| | Annex A – Development of formulae for the power level of signalling frequencies ..... | 80 |
+| | Annex B – Possible method of improving protection from interruptions ..... | 81 |
+| | Annex C – Development of a formula for the admissible forward transmission loss
in a country of destination ..... | 82 |
+
+| Rec. N.º | | Page |
+|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------|
+| SECTION 5 – Signalling procedures | | |
+| Q.460 | 5.1 Normal call set-up procedures for international working ..... | 83 |
+| Q.462 | 5.1.2 Signalling between the outgoing international R2 register and an incoming R2 register in an international exchange..... | 84 |
+| Q.463 | 5.1.3 Signalling between the outgoing international R2 register and an incoming R2 register in a national exchange in the destination country..... | 86 |
+| Q.464 | 5.1.4 Signalling between the outgoing international R2 register and the last incoming R2 register..... | 87 |
+| Q.465 | 5.1.5 Particular cases ..... | 88 |
+| Q.466 | 5.1.6 Supervision and release of the call..... | 88 |
+| Q.468 | 5.2 Rounting and numbering for international working..... | 89 |
+| | 5.3 Termination of interregister signalling ..... | 89 |
+| Q.470 | 5.3.1 At an incoming R2 register situated in a transit exchange..... | 89 |
+| Q.471 | 5.3.2 At the last incoming R2 register situated in the exchange to which the called subscriber is connected..... | 90 |
+| Q.472 | 5.3.3 At the last incoming R2 register situated in a transit exchange ..... | 92 |
+| Q.473 | 5.3.4 Use of end-of-pulsing signal I-15 in international working..... | 93 |
+| Q.474 | 5.3.5 Use of group B signals..... | 94 |
+| Q.475 | 5.4 Normal Release of outgoing and incoming R2 registers..... | 95 |
+| Q.476 | 5.5 Abnormal release of outgoing and incoming R2 registers..... | 97 |
+| Q.478 | 5.6 Relay and regeneration of R2 interregister signals by an outgoing R2 register in a transit exchange ..... | 98 |
+| Q.479 | 5.7 Echo-suppressor control – signalling requirements ..... | 100 |
+| Q.480 | 5.8 Miscellaneous procedures..... | 104 |
+| SECTION 6 – Testing and maintenance | | |
+| Q.490 | Testing and maintenance..... | 106 |
+| | Annex A to Signalling System R2 Specifications –
Provision of a forward-transfer signalling facility ..... | 110 |
+
+# SPECIFICATIONS OF SIGNALLING SYSTEM R2
+
+## INTRODUCTION
+
+### *General*
+
+Signalling System R2 is used as an international signalling system within international regions (world numbering zones). Moreover, System R2 can be used for integrated international/national signalling if it is employed, in conformity with the present specifications, as a signalling system in the national networks of the region concerned. Suitable for both automatic and semi-automatic working it offers a high reliability in transmission of the information necessary for setting up a call. It allows for rapid call set-up and provides sufficient signals in both directions to permit the transmission of numerical and other information relating to the called and calling subscribers' lines and to increase routing facilities.
+
+System R2 is specified for one-way operation on analogue and digital transmission systems and for both-way operation on digital transmission systems. Distinction is made between line signalling (supervisory signals) and interregister signalling (call set-up control signals). Versions of line signalling are specified for use on 4-wire carrier or PCM circuits. Nevertheless, the interregister signalling specified can also be used on 2-wire circuits. System R2 is suitable for use on satellite links and 3 kHz spaced carrier circuits. It is not designed for use on transmission systems with speech interpolation but it may be used on digital transmission systems with speech interpolation as long as transparency for pulsed interregister signals is guaranteed.
+
+The interregister signalling is a compelled multifrequency code system. This offers the possibility of end-to-end signalling and to take advantage of modern switching systems by providing a sufficient number of signals in both directions.
+
+System R2 is capable of normal interworking with other CCITT signalling systems.
+
+### *Line signalling*
+
+The following versions of line signalling are specified:
+
+- line signalling for carrier systems called the analogue version;
+- line signalling for PCM systems called the digital version.
+
+Since multifrequency signalling permits exchange of a large amount of information between registers, the quantity of information that has to be transmitted in the form of line signals is small. The versions of line signalling for System R2 have been designed accordingly. The analogue line signalling version standardized originally for use on international circuits is also suitable for national working. An analogue (in-band) line signalling version is only described for the specific use on 3 kHz spaced carrier circuits of international submarine cables.
+
+The *analogue version* is link-by-link using an out-band, low-level continuous tone-on-idle signalling method. Signal transfer simply involves the transition from one signalling condition to the other, except for the clearing sequence which is based on additional timing criteria. It is necessary to have a device for protection against the effect of interruption in the signalling channel since interruption of the signalling frequency simulates a false seizure or answer signal (interruption control). The signalling frequency is transmitted at a low level which avoids overloading of the transmission system when the frequency is sent continuously in both directions on all circuits in the idle state.
+
+The *digital version* is link-by-link using two signalling channels in each direction of transmission per speech circuit. The signalling channels are two of the four provided for channel associated signalling in a 2048 kbit/s primary multiplex (see Recommendation G.732). Protection against the effects of faulty transmission is provided.
+
+The analogue version and the digital version of the line signalling can be converted to each other by a transmultiplexer or other conversion equipment. Such equipment forms a conversion point between analogue (FDM) transmission on one hand and digital (PCM) transmission on the other hand. The System R2 line signalling, however, must be treated separately because for both transmission systems different line signalling versions are specified. Although both versions are described in some detail, a description of the actual conversion is given in Recommendation Q.430. Although these versions do not include a forward-transfer signal, forward-transfer signalling may be introduced for international working by bilateral agreement.
+
+### Interregister signalling
+
+The interregister signalling is performed end-to-end using a 2-out-of-6 in-band multifrequency code with forward and backward compelled signalling. The signalling frequencies do not therefore overlap with the line signalling frequency and differ according to the direction of transmission with a view to possible use of the multifrequency part of the system on 2-wire circuits.
+
+System R2 is designed to use six signalling frequencies (1380, 1500, 1620, 1740, 1860 and 1980 Hz) in the forward direction and six signalling frequencies (1140, 1020, 900, 780, 660 and 540 Hz) in the backward direction. Nevertheless for national application less signalling frequencies may be used.
+
+End-to-end signalling is a method for signalling between registers over two or more links in tandem without signal regeneration in intermediate exchanges (see Figure 1).
+
+
+
+Diagram illustrating the principle of end-to-end R2 interregister signalling. It shows a sequence of four registers connected in tandem. From left to right: an 'Outgoing R2 register' (represented by a switch-like symbol), followed by two 'Incoming R2 register in a transit exchange' (represented by rectangles), and finally an 'Incoming R2 register in an international or national terminal exchange' (represented by a rectangle). Dashed lines with double-headed arrows connect the outgoing register to each of the incoming registers, indicating end-to-end signalling. Solid lines connect the outgoing register to the first transit exchange, and subsequent solid lines connect the transit exchanges to each other and to the terminal exchange. A small label 'T0209420-02' is present on the right side of the diagram.
+
+FIGURE 1
+
+### Principle of end-to-end R2 interregister signalling
+
+With this signalling method, in general only the address information needed for routing the call through an intermediate (transit) exchange is transferred from the outgoing register to the incoming register. In the intermediate exchange the speech path is immediately through-connected and the incoming register released. Then the outgoing register can exchange information directly with the incoming register of the next exchange. Such end-to-end signalling is advantageous as it reduces the interregister signalling equipment needed and minimizes the holding time of registers in transit exchanges.
+
+System R2 has been designed to allow end-to-end interregister multifrequency signalling over several links in tandem. However, in circumstances where transmission conditions do not comply with the requirements specified for System R2 and might consequently jeopardize the exchange of the interregister signals, or in case of using System R2 via a satellite link, the overall multi-link connection is divided into sections, each with its individual interregister signalling (signals being then relayed and regenerated by a register at the point where the division is made).
+
+In the case of satellite working, the register at the incoming end of the satellite link must act as an outgoing R2 register (see also Recommendation Q.7).
+
+Generally transmission conditions in a national network comply with the requirements specified for System R2 and as such allow end-to-end signalling over complete connections between local exchanges.
+
+In the case of international System R2 working transmission conditions impose division into at least two signalling sections, when both the outgoing and incoming countries use System R2 in the national network. The division must be made in an exchange in the outgoing country. The relaying or regenerating register situated at the point where the division is made is called *the outgoing international R2 register*. In the case when System R2 is not used in the outgoing country the outgoing international R2 register receives address information via a national signalling system and it controls the call set-up over the outgoing System R2 signalling section.
+
+*The outgoing R2 register* is generally defined as a register situated at the outgoing end of a signalling section on which System R2 interregister signalling, according to the present specifications, is used. It controls the call set-up over the whole signalling section. It sends forward interregister signals and receives backward interregister signals. The outgoing R2 register receives information via the preceding links of the connection in a form used by the signalling system applied over the last of these links; this system may be System R2, a decadic pulse system, or any other system. The preceding link may also be a subscriber's line.
+
+When an *R2 register in a transit exchange* is working according to the definition above it is also called an *outgoing R2 register*. *The outgoing international R2 register* is the special case of the outgoing R2 register when the outgoing signalling section comprises at least one international link.
+
+*The incoming R2 register* is defined as a register situated at the incoming end of a link on which System R2 interregister signalling, according to the present specification, is used. It receives forward interregister signals via the preceding link(s) and sends backward interregister signals. The information received is used completely or in part for the control of selection stages and may be sent in its entirety or in part to the succeeding equipment, in which case the signalling used for retransmission is never System R2. Interworking then takes place between System R2 and the other System. Thus every register not situated at the outgoing end of a System R2 signalling section is called an incoming R2 register independently of the exchange type.
+
+The following operational features are provided by using all the 15 forward and 15 backward combinations of the multifrequency code:
+
+- capability of transferring address information for automatic, semi-automatic and maintenance calls;
+- indicators in order to identify transit and maintenance (test) calls;
+- language digits or discriminating digit(s) for international calls;
+- transfer of the next digit or repetition of the last but one, the last but two, or the last but three digit on request by the register at the incoming end;
+- forward and backward signals for control of echo suppressors;
+- information concerning the nature and the origin of the call (calling party's category) can be transferred to the register at the incoming end, i.e. whether national or international, whether from an operator or from a subscriber, whether from data-transmission, maintenance or other equipment, etc.;
+- information concerning the nature of the circuit can be requested by the register at the incoming end, i.e. whether a satellite link is already included or not;
+- information on congestion, unallocated number and on the condition of the called subscriber's line can be transferred to the outgoing register, i.e. whether free, busy or out of service, etc.;
+- a restricted number of signals left to the discretion of Administrations for allocation of national meanings.
+
+The interregister signalling specified for System R2 can also be used together with any non-standardized line-signalling system. The resulting combination is not considered to be System R2.
+
+System R2 gives potential for a short post-dialling delay using overlap operation with dialling and end-to-end signalling. The outgoing R2 register starts call set-up as soon as it has received the minimum requisite information. Therefore signal transfer starts before the complete address information is received, i.e. before the caller finishes dialling. This practice particularly applies at an outgoing R2 register where the complete address information from a subscriber or operator is stored (e.g. local registers). This is in contrast to *en bloc* register signalling i.e. the transmission of all the address information as a whole in one sequence starting only after complete reception of the address information.
+
+Unused signalling capacity provides potential for development and allows for future requirements yet undefined. This spare capacity may be used for increasing the number of signals and signalling procedures e.g. for new services to be offered to subscribers.
+
+## SECTION 1
+
+## DEFINITIONS AND FUNCTIONS OF SIGNALS
+
+###### Recommendation Q.400
+
+### 1.1 FORWARD LINE SIGNALS
+
+#### 1.1.1 **seizing signal**
+
+A signal sent at the beginning of the call to initiate transition of the circuit at the incoming end from the idle state to seized state. At the incoming exchange it causes the association of equipment capable of receiving register signals.
+
+#### 1.1.2 **clear-forward signal**
+
+A signal sent to terminate the call or call attempt and to release in the incoming exchange and beyond it all switching units held on the call.
+
+The signal is sent when:
+
+- a) in semi-automatic working the operator of the outgoing international exchange takes the plug out or performs an equivalent operation;
+- b) in automatic working, the calling subscriber clears or performs an equivalent operation.
+
+This signal is also sent by the outgoing international exchange upon receiving a backward register signal requesting the outgoing international R2 register to clear the connection, or in the case of forced release of the connection as mentioned in Recommendation Q.118. This signal may also be sent as the result of abnormal release of the outgoing international R2 register.
+
+#### 1.1.3 **forward-transfer signal1)**
+
+A signal sent on semi-automatic calls when the outgoing international exchange operator wants the help of an operator at the incoming international exchange. The signal will usually bring an assistance operator (see Recommendation Q.101) into the circuit. If the call is completed via an incoming or delay operator at the incoming international exchange, the signal indicates that recall of this operator is wanted.
+
+### 1.2 BACKWARD LINE SIGNALS
+
+#### 1.2.1 **seizing-acknowledgement signal2)**
+
+A signal sent to the outgoing exchange to indicate the transition of the equipment at the incoming end from the idle state to seized state. Recognition of the seizing acknowledgement signal at the outgoing end causes the state of the circuit to change from seized to seizure acknowledged.
+
+---
+
+1) This signal is not provided in either the analogue or digital version of System R2 line signalling. Information about possible arrangements for such a signal and signalling procedures involved are contained in Annex A to the present Specifications.
+
+2) This signal is only used in the digital version of System R2 line signalling.
+
+#### 1.2.2 **answer signal**
+
+A signal sent to the outgoing international exchange to indicate that the called party has answered the call (see Recommendation Q.27). In semi-automatic working this signal has a supervisory function.
+
+In automatic working this signal is used:
+
+- to start metering the charge to the calling subscriber, unless the register signal indicating no charge has been sent previously;
+- to start measurement of the call duration for international accounting purposes.
+
+#### 1.2.3 **clear-back signal**
+
+A signal sent to the outgoing international exchange to indicate that the called party has cleared. In semi-automatic working, this signal has a supervisory function. In automatic working, arrangements must be made in accordance with Recommendation Q.118, and the Notes of Recommendation Q.120, § 1.8 also apply.
+
+#### 1.2.4 **release-guard signal**
+
+A signal sent to the outgoing exchange in response to a clear-forward signal to indicate that the latter has been fully effective in returning the switching units at the incoming end of the circuit to idle condition. An international circuit is protected against subsequent seizure as long as the release operations initiated by the clear-forward signal have not been completed at the incoming end.
+
+#### 1.2.5 **blocking signal**
+
+A signal sent on an idle circuit to the outgoing exchange to cause engaged conditions (blocking) to be applied to this circuit, guarding it against subsequent seizure.
+
+### 1.3 FORWARD REGISTER SIGNALS
+
+#### 1.3.1 **address signal**
+
+A signal containing one element of information (digit 1, 2, ..., 9 or 0, code 11, code 12 or code 13) about the called or calling party's number or the end of pulsing indication (code 15).
+
+For each call a series of address signals is sent (see Recommendations Q.101 and Q.107).
+
+#### 1.3.2 **country-code and echo-suppressor indicators**
+
+Signals indicating:
+
+- whether or not the country-code is included in the address information (international transit or terminal call);
+- whether or not an outgoing half-echo suppressor should be inserted in the first international exchange reached;
+- whether or not an incoming half-echo suppressor should be inserted (an outgoing half-echo suppressor having already been inserted in the connection).
+
+#### 1.3.3 **language or discriminating digit**
+
+A numerical signal occupying a predetermined position in the sequence of address signals indicating:
+
+- in semi-automatic working, the service language to be used in the incoming international exchange by the incoming, delay and assistance operators when they come in the circuit (language digit);
+- the automatic working or any other special characteristic of the call (discriminating digit).
+
+#### 1.3.4 **test call indicator**
+
+A signal occupying the position of the language digit when the call is originating from test equipment.
+
+#### 1.3.5 **nature of circuit indicators**
+
+Signals only sent on request by certain backward signals and using a second meaning of some signals, to indicate whether a satellite link is already included in the connection or not.
+
+#### 1.3.6 **end-of-pulsing signal**
+
+An address signal sent indicating (in semi-automatic service) that no other address signal will follow or (in automatic service) that the transmission of the code identifying the origin of the call is completed.
+
+#### 1.3.7 **calling party's category signals**
+
+A special group of signals providing, in addition to the information contained in the language or discrimination digit, supplementary information concerning the nature of the call (i.e. whether national or international) and its origin.
+
+Typical categories are:
+
+- operator capable of sending the forward-transfer signal;
+- ordinary subscriber or operator with no forward-transfer facility;
+- subscriber with priority;
+- data transmission call;
+- maintenance call.
+
+#### 1.3.8 *Signals for use on the national network*
+
+Some of the Group II forward signals (see Recommendation Q.441, § 4.2.3.2) have been allocated for national use. When the outgoing international R2 register receives them, it must react as specified in Recommendation Q.480.
+
+### 1.4 **BACKWARD REGISTER SIGNALS**
+
+#### 1.4.1 *Signals requesting transmission of address signals*
+
+Five backward signals without particular names are provided; four of them are interpreted with reference to the latest address signal sent:
+
+- signal requesting the transmission of the address signal following the latest address signal sent;
+- signal requesting repetition of the address signal preceding the latest address signal sent (last but one);
+- signal requesting the repetition of the last but two address signals sent;
+- signal requesting the repetition of the last but three address signals sent;
+- signal requesting the transmission or repetition of the language or discrimination digit.
+
+#### 1.4.2 *Signal requesting information about the circuit*
+
+A backward signal is provided to request the nature of the circuit.
+
+#### 1.4.3 *Signals requesting information about the call or calling party*
+
+Three backward signals without particular names are provided for this purpose:
+
+- signal inquiring the calling party's category;
+- signal requesting the repetition of the country-code indicator;
+- signal inquiring whether or not incoming half-echo suppressor should be inserted.
+
+#### 1.4.4 *Congestion signals*
+
+Two congestion signals are provided:
+
+- a signal indicating international congestion, i.e. that the call set-up attempt has failed owing to congestion of the group of international circuits, or congestion in the international switching equipment, or to time-out or abnormal release of an incoming R2 register in an international transit exchange;
+- a signal indicating national congestion, i.e. that the call set-up attempt has failed owing to congestion in the national network (excluding a busy called subscriber's line) or to time-out or abnormal release of an incoming R2 register in a terminal international exchange or a national exchange.
+
+#### 1.4.5 **address-complete signals**
+
+Signals indicating that it is no longer necessary to send another address signal, and
+
+- either cause immediate passage to the speech position to enable the calling subscriber to hear a tone or a recorded announcement of the national incoming network;
+- or announce the transmission of a signal indicating the condition of the called subscriber's line.
+
+#### 1.4.6 *Signals indicating the condition of the called subscriber's line*
+
+Six signals sent in the backward direction are provided to give information about the called subscriber's line and to indicate the end of interregister signalling. These signals are:
+
+- **send special information tone**
+a signal sent in the backward direction indicating that the special information tone should be returned to the calling party. This tone indicates that the called number cannot be reached for reasons not covered by other specific signals and that the unavailability is of a long term nature. (See also Recommendation Q.35);
+- **subscriber line busy**
+a signal indicating that the line or lines connecting the called subscriber to the exchange are busy;
+- **unallocated number**
+a signal indicating that the number received is not in use (e.g. an unused country code or an unused trunk code or subscriber number that has not been allocated);
+- **subscriber line free, charge**
+a signal indicating that the called subscriber's line is free and that the call is to be charged on answer;
+- **subscriber line free, no charge**
+a signal indicating that the called subscriber's line is free and that the call is not to be charged on answer. This signal is used only for calls to special destinations;
+- **subscriber line out of order**
+a signal indicating that the subscriber's line is out-of-service or faulty.
+
+#### 1.4.7 *Signals for use in the national network*
+
+Some of the backward signals have been allocated for national use. Since not all incoming registers can know the origin of the connection and since end-to-end signalling is used, it may happen that the above-mentioned signals are sent to the outgoing international R2 register. When this register receives them it must react as indicated in Recommendations Q.474 and Q.480.
+
+## SECTION 2
+
+## LINE SIGNALLING, ANALOGUE VERSION
+
+### Recommendation Q.411
+
+### 2.1 LINE SIGNALLING CODE
+
+#### 2.1.1 General
+
+The System R2 line signalling, analogue version, is intended for use on carrier circuits. The line signals are transmitted link-by-link. The code for the transmission of line signals is based on the *tone-on-idle* signalling method. It is required that the circuits on which the system is employed are equipped in each direction of transmission with a signalling channel outside the speech frequency band. When the circuit is in the idle state, a low-level signalling tone is sent continuously in both directions over the signalling channels. The tone is removed in the forward direction at the moment of seizure and in the backward direction when the called subscriber answers.
+
+The connection is released when the signalling tone is restored in the forward direction; release causes the tone to be restored in the backward direction. If the called party is the first to clear, the signalling tone is restored in the backward direction first. It is then restored in the forward direction either when the caller clears or when a certain interval has elapsed after recognition of the signalling tone in the backward direction. This signalling method, requiring only simple equipment, provides rapid signal recognition and retransmission. The signal transfer speed provided by continuous type signalling compensates for the need of signal repetition inherent in link-by-link transmission.
+
+The signalling system is specified for one-way operation of 4-wire carrier circuits.
+
+#### 2.1.2 Line conditions
+
+Tone-on or tone-off denotes a certain line signalling condition. The line thus has two possible conditions in each direction, i.e. a total of four line signalling conditions. Taking into account the time sequence, the circuit may resume one of the six characteristic states shown in Table 1/Q.411.
+
+TABLE 1/Q.411
+
+| State of the circuit | Line signalling condition | |
+|----------------------|---------------------------|----------------|
+| | Forward | Backward |
+| 1. Idle | Tone-on | Tone-on |
+| 2. Seized | Tone-off | Tone-on |
+| 3. Answered | Tone-off | Tone-off |
+| 4. Clear-back | Tone-off | Tone-on |
+| 5. Release | Tone-on | Tone-on or off |
+| 6. Blocked | Tone-on | Tone-off |
+
+The transition from one signalling condition to another corresponds to the transfer of a line signal according to the definitions in § 1. To change from the release state to the idle state additional criteria (timing) are necessary to ensure a defined sequence corresponding to the transfer of the release-guard signal (see § 2.2.2.6 below).
+
+### **2.2 CLAUSES FOR EXCHANGE LINE SIGNALLING EQUIPMENT1)**
+
+#### **2.2.1 *Recognition time for transition of signalling condition***
+
+The recognition time $t_r$ for a changed condition (transition from tone-on to tone-off or vice versa) is $40 \pm 10$ ms2). The recognition time is defined as the minimum duration that the presence or absence of a direct current signal must have at the output of the signal receiver in order to be recognized as a valid signalling condition by the exchange equipment. Thus the specified value does not include the response time $t_{rs}$ of signalling receivers (see Recommendation Q.415). However, it is determined on the assumption that there is interruption control (see Recommendation Q.416).
+
+#### **2.2.2 *States and procedures under normal conditions***
+
+##### **2.2.2.1 *Seizure***
+
+The outgoing end removes the tone in the forward direction. If seizure is immediately followed by release, removal of the tone must be maintained for at least 100 ms to make sure that it is recognized at the incoming end.
+
+##### **2.2.2.2 *Answering***
+
+The incoming end removes the tone in the backward direction. When another link of the connection using tone-on-idle continuous signalling precedes the outgoing exchange, the tone-off condition must be established on this link immediately after it is recognized in this exchange. When another signalling system is used on the preceding link, the rules for interworking are applicable.
+
+##### **2.2.2.3 *Clear-back***
+
+The incoming end restores the tone in the backward direction. When another link of the connection using tone-on-idle continuous signalling precedes the outgoing exchange the *tone-on* condition must be established on this link immediately after it is recognized in this exchange. When another signalling system is used on the preceding link, the rules for interworking are applicable. The provisions set forth in § 2.2.2.6 below must also be taken into consideration.
+
+##### **2.2.2.4 *Clear-forward procedure***
+
+The outgoing end restores the tone in the forward direction (see § 2.2.2.1 above). The forward connection is released and the release-guard sequence begins as soon as the changed signalling condition is recognized at the incoming end. In the outgoing exchange the circuit remains blocked until the release-guard sequence is terminated (see § 2.2.2.6 below).
+
+##### **2.2.2.5 *Blocking and Unblocking procedure***
+
+At the outgoing exchange the circuit stays blocked so long as the tone remains off in the backward direction.
+
+Restoration of the tone in the backward direction – accompanied by the presence of the tone in the forward direction – restores the circuit to the idle state. The circuit may then be seized for a new call.
+
+---
+
+1) Although the signalling condition (tone-on or tone-off) physically only appears in transmission equipment, it is used in this section as a reference criterion to specify functions of exchange equipment.
+
+2) Originally this value was $(20 \pm 7)$ ms. Since there will be no problem in the interworking between equipment having the original recognition time $t_r = (20 \pm 7)$ ms, and equipment having the new recognition time $t_r = (40 \pm 10)$ ms, existing equipment need not necessarily be changed to the value $t_r = (40 \pm 10)$ ms.
+
+##### 2.2.2.6 Release and release-guard sequence
+
+Release-guard must be ensured whatever the state of the circuit at the moment the clear-forward signal is sent – seized prior to answer, answered or cleared by the called party. It may also happen that answering or clearing by the called party occurs when release has already begun at the outgoing exchange. The cases are described below and shown in the Figures 2/Q.412 to 4/Q.412. The exact timing is shown in Figure 5/Q.412.
+
+###### a) Release prior to answered state
+
+The clear-forward signal is sent from the outgoing end by restoring the tone in the forward direction (see Figure 2/Q.412). Recognition of this tone has the following consequences at the incoming end:
+
+- i) the tone in the backward direction is removed;
+- ii) the release of the switching units is initiated;
+- iii) the release-guard sequence starts.
+
+When release operations at the incoming end are complete, but not before an interval $T_2$ has elapsed after the removal, the tone is again restored at the incoming end in the backward direction.
+
+
+
+The diagram illustrates the signaling sequence for 'Release prior to answered state'. It is divided into four horizontal sections: 'Circuit state', 'Outgoing end', 'Forward', and 'Backward' (top half), and 'Forward', 'Backward', 'Incoming end', and 'Legend' (bottom half).
+
+- Circuit state:** Shows three phases: 'Idle', 'Seized', and 'Release'.
+- Outgoing end:** Shows the 'Seizing' signal at the start of the 'Seized' state. During the 'Release' state, a 'Clear-forward' signal is sent. A timing interval $T_1$ is marked from the start of the 'Clear-forward' signal to the start of the 'Release-guard sequence'.
+- Forward:** Shows the 'Seizing' signal (Sending) at the start. During the 'Release' state, the 'Clear-forward' signal is shown as a thick line (Sending).
+- Backward:** Shows a tone (Sending) during the 'Seized' state. At the start of the 'Release' state, the tone is removed (indicated by an 'O'). At the 'Incoming end', the tone is restored (Sending) after the 'Release-guard sequence'.
+- Incoming end:** Shows the 'Release-guard sequence' starting when the backward tone is removed and ending when the tone is restored. A timing interval $T_2$ is marked from the start of the 'Release-guard sequence' to the restoration of the tone.
+- Legend:** Shows a single line for 'Sending' and a double line for 'Receiving'.
+- Timing:** Intervals $T_1$ and $T_2$ are marked. A small interval $t_r + t_i$ is marked at the transition from 'Release' to 'Idle'.
+- Text:** 'CCITT-49172' is in the bottom right. 'Legend: see Figure 5/Q.412.' is in the bottom left.
+
+Timing diagram for 'Release prior to answered state' showing circuit states, signal directions, and timing intervals T1, T2, and release-guard sequence.
+
+FIGURE 2/Q.412
+Release prior to answered state
+
+When $T_1$ has elapsed the outgoing end must recognize that the tone-off condition in the backward direction is established. After this recognition the restoring of the tone in the backward direction returns the circuit to the idle state and completes the release-guard sequence.
+
+At the incoming end the sending of an answer signal can only be prevented after the clear-forward signal has been recognized. To avoid any false operation should answer coincide with release, transition from *tone-on* to *tone-off* in the backward direction must not be interpreted, at the outgoing end, as part of the release-guard sequence during an interval $T_1$ . The interval $T_1$ starts with the sending of the tone in the forward direction. It is long enough to make quite sure that the clear-forward signal is recognized and the *tone-off* condition established at the incoming end.
+
+For the calculation of the intervals $T_1$ and $T_2$ see § 2.2.2.7 below.
+
+###### b) *Release in answered state*
+
+In this case, the release operations differ only from a) above in so far as i) does not apply. At the incoming end, however, sending of a clear-back signal can only be prevented after the clear-forward signal has been recognized. Should there be a clear-back signal the specified interval $T_1$ enables any resultant difficulties to be obviated (see Figure 3/Q.412).
+
+
+
+The diagram illustrates the timing and signaling for a 'Release in answered state' call. The top row shows the 'Circuit state' transitioning through 'Idle', 'Seized', 'Answered', 'Release', and back to 'Idle'. At the 'Outgoing end', a 'Seizing' signal is sent during the 'Seized' state, and a 'Clear-forward' signal is sent during the 'Release' state. At the 'Incoming end', an 'Answer' signal is received during the 'Answered' state, and a 'Release-guard sequence' is received during the 'Release' state. The interval $T_1$ is the time from the start of the 'Clear-forward' signal to the start of the 'Release-guard sequence'. The interval $T_2$ is the time from the start of the 'Release-guard sequence' to the start of the 'Idle' state. A legend indicates that solid lines represent 'Sending' and double lines represent 'Receiving'. The diagram is labeled 'CCITT-49182' and refers to Figure 5/Q.412 for the legend.
+
+Timing diagram for 'Release in answered state' showing circuit states and signal sequences at outgoing and incoming ends.
+
+FIGURE 3/Q.412
+**Release in answered state**
+
+###### c) *Release in clear-back state*
+
+The release operations are identical to those described in a) above. Should there be a second answer signal, the specified interval $T_1$ enables any resultant difficulties to be obviated (see Figure 4/Q.412).
+
+##### 2.2.2.7 *Calculation of the intervals $T_1$ and $T_2$ specified for release and release-guard operations*
+
+Figure 5/Q.412 shows the factors involved in calculating the intervals $T_1$ and $T_2$ .
+
+At the outgoing end when the interval $T_1$ has elapsed (Figure 5/Q.412, point D) the tone-off condition in the backward direction can be expected and recognized with certainty in all cases mentioned in § 2.2.2.6 above.
+
+Similarly, the interval $T_2$ preceding the restoring of the tone in the backward direction may be applied in all cases. To avoid false operation in the event of coinciding forward and backward signals or an irregular sequence of signals, the time interval $T_2$ must also be observed with the release operation [see § 2.2.2.6 b) above].
+
+
+
+Circuit state: Idle, Seized, Answered, Clear-back, Release, Idle
+
+Outgoing end: Forward (Seizing), Backward (Answer)
+
+Incoming end: Forward (Clear-forward, Release-guard sequence), Backward (Clear-back)
+
+Time intervals: $T_1$ , $T_2$ , $t_r + t_i$
+
+Legend:
+**—** Sending
+**—** Receiving
+
+CCITT-49192
+
+Legend: see Figure 5/Q.412.
+
+Timing diagram for Figure 4/Q.412 showing circuit states and signal sequences for outgoing and incoming ends. The diagram illustrates the sequence of events from Idle to Seized, Answered, Clear-back, Release, and back to Idle. It shows 'Seizing' and 'Answer' signals at the outgoing end, and 'Clear-forward', 'Clear-back', and 'Release-guard sequence' signals at the incoming end. Time intervals T1 and T2 are marked. A legend indicates that thick lines represent 'Sending' and thin lines represent 'Receiving'. The code CCITT-49192 is present in the bottom right.
+
+FIGURE 4/Q.412
+**Release in clear-back state**
+
+
+
+Outgoing end: Sending, Receiving
+
+Incoming end: Receiving, Sending
+
+Time intervals: $T_1 \text{ max.}$ , $T_1$ , $T_1 \text{ min.}$ , $t_p + t_o$ , $t_r$ , $t_i$ , $T_2 \text{ min.}$
+
+Points: A, B, C, D, E, F
+
+CCITT-48460
+
+Tone-on or -off pending circuit state in which release starts (see § 2.2.2.6)
+
+Timing diagram for Figure 5/Q.412 detailing the release-guard sequence. It shows signal transitions at the outgoing and incoming ends with various time intervals: T1 max., T1 min., tp + to, tr, ti, and T2 min. Points A through F are marked on the signal lines. The diagram starts from a 'Tone-on or -off pending circuit state'. The code CCITT-48460 is present in the bottom right.
+
+###### *Legend*
+
+- $t_p$ : Propagation time
+- $t_o$ : Overall response time of signalling sender and receiver
+- $t_r$ : Recognition time
+- $t_i$ : Internal operating time
+
+FIGURE 5/Q.412
+**Release-guard sequence**
+
+The minimum value of $T_1$ is the sum of the maximum values of the times required for the various operations which take place between application of the tone in the forward direction and recognition of the absence of tone in the backward direction.
+
+$T_2$ delays release of the circuit. It must therefore be as short as possible. However, it must be long enough to ensure recognition of the tone-off condition in the backward direction at the outgoing end when $T_1$ is at its maximum, even when this condition begins as early as possible.
+
+###### *a) Exclusive terrestrial circuits*
+
+The calculation is based on a maximum one-way transmission delay of 30 ms for a circuit. Thus, for circuits on high-velocity transmission systems via terrestrial lines (including submarine cables) the maximum operating range of the specified line signalling system is 4800 km3).
+
+Values used for the calculation of $T_1$ and $T_2$ :
+
+$$\begin{aligned} 0 < t_p < 30 \text{ ms} \\ 0 < t_o < 30 \text{ ms (see § 2.3.2.4)} \\ 30 \text{ ms} < t_r < 50 \text{ ms} \\ 0 < t_i < 20 \text{ ms} \end{aligned}$$
+
+Calculation of intervals $T_1$ and $T_2$ :
+
+$$\begin{aligned} T_1 > \overline{AC} \quad & T_1 > 2 (t_p + t_o) \text{ max.} + t_r \text{ max.} + t_i \text{ max.} \\ & T_1 > (2 \times 60 + 50 + 20) \text{ ms} \\ & T_1 > 190 \text{ ms} \end{aligned}$$
+
+Allowing a safety margin of 10 ms and a tolerance of $\pm 20\%$ , the specified value of $T_1$ is $(250 \pm 50)$ ms.
+
+$$\begin{aligned} T_2 > \overline{BF} \quad & T_2 > T_1 \text{ max.} + t_r \text{ max.} + t_i \text{ max.} - 2 (t_p + t_o) \text{ min.} - t_r \text{ min.} - t_i \text{ min.} \\ & T_2 > (300 + 50 + 20 - 0 - 30 - 0) \text{ ms} \\ & T_2 > 340 \text{ ms} \end{aligned}$$
+
+Allowing a safety margin of 20 ms and a tolerance of $\pm 20\%$ , the specified value of $T_2$ is $(450 \pm 90)$ ms.
+
+###### *b) Circuits including a satellite link*
+
+The calculation is based on the assumption that the complete connection includes two terrestrial sections with a maximum one-way transmission delay of 15 ms each and a satellite section with a one-way transmission delay of $(270 \pm 20)$ ms.
+
+Values used for the calculation of $T_1$ and $T_2$ :
+
+$$\begin{aligned} 250 < t_p < 320 \text{ ms} \\ 0 < t_o < 30 \text{ ms (see § 2.3.2.4)} \\ 30 < t_r < 50 \text{ ms} \\ 0 < t_i < 20 \text{ ms} \end{aligned}$$
+
+Calculation of intervals $T_1$ and $T_2$ :
+
+$$\begin{aligned} T_1 > \overline{AC} \quad & T_1 > 2 (t_p + t_o) \text{ max.} + t_r \text{ max.} + t_i \text{ max.} \\ & T_1 > (2 \times 350 + 50 + 20) \text{ ms} \\ & T_1 > 770 \text{ ms} \end{aligned}$$
+
+Allowing a safety margin of 30 ms and a tolerance of $\pm 20\%$ , the specified value of $T_1$ $(1000 \pm 200)$ ms.
+
+3) See Recommendation G.114, Fascicle III.1.
+
+$$\begin{aligned}
+T_2 > \overline{BF} \quad & T_2 > T_1 \max. + t_r \max. + t_i \max. - 2 (t_p + t_o) \min. - t_r \min. - t_i \min. \\
+& T_2 > (1200 + 50 + 20 - 2 \times 250 - 30 - 0) \text{ ms} \\
+& T_2 > 740 \text{ ms}
+\end{aligned}$$
+
+Allowing a safety margin of 60 ms and a tolerance of $\pm 20\%$ , the specified value of $T_2$ is $(1000 \pm 200)$ ms.
+
+###### c) *Terrestrial circuits and circuits including a satellite link*
+
+The situation in which equipment can serve terrestrial circuits as well as circuits including a satellite link is not to be preferred because for the case of terrestrial circuits the release sequence is unduly prolonged. The calculation is based on the same assumption as in b) above, but with a minimum for $(t_p + t_o) = 0$ . This does not affect the value of $T_1$ , so also in this situation $T_1 = 1000 \pm 200$ ms.
+
+Values used for the calculation of $T_2$ :
+
+$$\begin{aligned}
+0 < t_p < 320 \text{ ms} \\
+0 < t_o < 30 \text{ ms (see § 2.3.2.4)} \\
+30 < t_r < 50 \text{ ms} \\
+0 < t_i < 20 \text{ ms}
+\end{aligned}$$
+
+Calculation of interval $T_2$ :
+
+$$\begin{aligned}
+T_2 > \overline{BF} \quad & T_2 > T_1 \max. + t_r \max. + t_i \max. - 2 (t_p + t_o) \min. - t_r \min. - t_i \min. \\
+& T_2 > (1200 + 50 + 20 - 0 - 30 - 0) \text{ ms} \\
+& T_2 > 1240 \text{ ms}
+\end{aligned}$$
+
+Allowing a safety margin of 40 ms and a tolerance of $\pm 20\%$ , the specified value of $T_2$ is $(1600 \pm 320)$ ms.
+
+#### 2.2.3 *Abnormal conditions*
+
+The situations described below are those in which interruption control of signalling channels (see Recommendation Q.416) does not function and which occur only during interruptions of individual channels or in the event of a fault in a line-signalling equipment. In addition, the situations described in §§ 2.2.3.3 and 2.2.3.4 below may also result from operation of interruption control at the incoming end of the circuit. In that case the circuit automatically returns to normal at the command of interruption control.
+
+2.2.3.1 If an exchange recognizes tone-off condition in the backward direction (premature answer) before the outgoing R2 register has received a signal A-6 or a Group B-signal, the connection must be released. Congestion information is then sent backwards or a repeat attempt is made to set up the call.
+
+2.2.3.2 In the case of non-reception of the answer signal, of delay in clearing by the calling subscriber in automatic working, or of non-reception of the clear-forward signal by the incoming exchange after the clear-back signal has been sent, the provisions of Recommendation Q.118 apply.
+
+2.2.3.3 If, in the cases given in § 2.2.2.6 a) or c) above, the tone in the backward direction is not removed, the circuit will remain blocked, since it cannot return to the idle state of its own accord. The action to be taken in such cases is described in § 6.6.
+
+2.2.3.4 If after sending of the clear-forward signal the signalling tone in the backward direction is not restored, the circuit stays blocked, as described in section § 2.2.2.5 above. The same occurs when, in the idle state, the signalling tone in the backward direction is interrupted by a fault.
+
+2.2.3.5 When the signalling tone in the forward direction of an idle circuit is interrupted owing to a fault, the incoming end recognizes seizure and connects multifrequency signalling equipment, but no interregister signalling follows.
+
+- a) When the interruption is greater than the incoming R2 register time-out (see Recommendation Q.476) the register will release and the circuit must be brought into blocked state by removal of the signalling tone in the backward direction. As soon as the fault is cleared and the tone in the forward direction consequently restored, the circuit returns to the idle state in accordance with § 2.2.2.6 b) above.
+- b) When the interruption is shorter than the time-out, restoration of the signalling tone in the forward direction will return the circuit to the idle state in accordance with § 2.2.2.6 a) above.
+
+#### 2.2.4 *Alarms for technical staff*
+
+According to Recommendation Q.117, an alarm should in general be given to technical staff as soon as an abnormal condition is recognized as probably due to a fault.
+
+It is recommended that a delayed action alarm should be operated at the outgoing end for the conditions described in §§ 2.2.2.5, 2.2.3.3 and 2.2.3.4 above, i.e. when the circuit does not revert to the idle state after sending of the clear-forward signal or receipt of the blocking signal.
+
+Arrangements for the operation of the alarm will be made by each Administration.
+
+At both the outgoing and the incoming end, when interruption control (see Recommendation Q.416) functions, alarm condition must first be established for the transmission equipments. However, in this case a delayed-action alarm may also be given to the technical staff of the exchange.
+
+### 2.3 CLAUSES FOR TRANSMISSION LINE SIGNALLING EQUIPMENT
+
+#### Recommendation Q.414
+
+#### 2.3.1 SIGNAL SENDER
+
+##### 2.3.1.1 *Signalling frequency*
+
+The nominal value of the signalling frequency is 3825 Hz. Measured at the sending point, the frequency variation from the nominal value must not exceed $\pm 4$ Hz.
+
+##### 2.3.1.2 *Send level*
+
+The send level of the signalling frequency, measured at the group distribution frame or an equivalent point, must be $-20 \pm 1$ dBm0.
+
+##### 2.3.1.3 *Leaks*
+
+The level of the signal frequency which may be transmitted to line as a leak current (e.g. when static modulators are used), must be at least 25 dB below the level of the signalling tone.
+
+##### 2.3.1.4 *Phase distribution of the signalling frequencies*
+
+As the signalling frequency is sent on any circuit in idle state, the addition of these tones in moments of low traffic may give rise to the following phenomena on certain transmission systems:
+
+- high peak voltage on the line caused by the signalling tones and involving the possibility of overloading the system;
+- intelligible crosstalk due to third-order intermodulation;
+- unwanted tones coming from second-order intermodulation products and occurring within sound-programme circuits.
+
+The following special measures must be taken to avoid these effects:
+
+One method recommended is to inject the signalling frequencies with random 0 and $\pi$ radian phases in the channels. An equivalent method is to use carrier frequencies of which the phases are randomly distributed 0 and $\pi$ radians. With these methods the probability of occurrence of 0 and $\pi$ radian phases should be 0.51).
+
+Other methods may be used provided they give comparable results.
+
+---
+
+1) For further details on the method of random distribution of the phases of frequency 3825 Hz, see: Ekholm, O. and Johannesson, N.O.: "Loading Effects with Continuous Tone Signalling", English edition of *TELE*, No. 2, 1969. For further details on a systematic method of phase distribution, see: Rasch, J. and Kagelmann, H.: "On Measures for Reducing Voltage Peaks and Distortion Noise on Carrier Transmission Paths with Single Channel Supervision", *Nachrichtentechnische Zeitschrift (NTZ)*, 22 (1969), No. 1, pp. 24-31.
+
+##### 2.3.1.5 Protection of the signalling channel at the sending end
+
+This signalling channel must be protected at the sending end against disturbance from the associated and the adjacent speech channel.
+
+When a sinewave at $0$ dBm0 level is applied to the audio-frequency input of the associated channel, the level measured at the group distribution frame or at an equivalent point must not exceed the levels shown in Figure 6/Q.414.
+
+When a sinewave of frequency $f$ is applied to the audio-frequency input of the adjacent channel it produces two signals that appear on the frequency scale of Figure 6/Q.414 as having the frequencies $(4000 + f)$ and $(4000 - f)$ . The level of the $(4000 + f)$ signal, measured at the group distribution frame or at an equivalent point, shall not be higher than $-33$ dBm0 when the sinewave with frequency $f$ is applied to the audio-frequency input of the adjacent channel at a level shown in Figure 6/Q.414 for the frequency of $(4000 + f)$ . The level of the $(4000 - f)$ signal, measured at the group distribution frame or at an equivalent point, shall not be higher than $-33$ dBm0 when the sinewave with frequency $f$ is applied to the audio-frequency input of the adjacent channel at any level below the value shown in Figure 6/Q.414 for the frequency $(4000 - f)$ .
+
+
+
+| Frequency f (Hz) | Associated channel (dBm0) | Adjacent channel (dBm0) |
+|------------------|---------------------------|-------------------------|
+| 3550 | 0 | 0 |
+| 3750 | -33 | 0 |
+| 3900 | -33 | 0 |
+| 4100 | -33 | -23 |
+| 4250 | -33 | -33 |
+
+Figure 6/Q.414: Protection of the signalling channel at the sending end. A graph showing power levels in dBm0 versus frequency f in Hz. The y-axis ranges from -50 to +12 dBm0. The x-axis ranges from 3550 to 4250 Hz. Two curves are shown: a solid line for the 'Associated channel' and a dashed line for the 'Adjacent channel'.
+
+Note – The frequency of the virtual carrier of the associated speech channel is the origin of the frequency scale (zero frequency).
+
+FIGURE 6/Q.414
+Protection of the signalling channel at the sending end
+
+When the Go path is looped to the Return path at the group distribution frame or an equivalent point, the signal receiver must not change condition when:
+
+- the click generator shown in Figure 7/Q.414 is connected to the associated speech channel or to the adjacent speech channel at the very point where this channel is connected to the switching equipment;
+- to take the most difficult circumstances possible, the channel level adjusting devices are set to such values encountered in practice which give rise to the worst disturbance;
+- gain is introduced in the loop at the group distribution frame or at the equivalent point, so that the receive level at the point in question is $+3$ dBm0.
+
+
+
+Detailed description: The diagram shows a circuit labeled 'Click generator'. A switch 'S' is connected to two parallel horizontal lines. Each line contains a 100 Ω resistor. Between these two lines, there is a vertical branch containing two 500 Ω resistors in series with a 60 V DC source connected between them. To the right of this branch, each horizontal line has a 4 μF capacitor in series before reaching the output terminals. The diagram is identified by the code CCITT-49202.
+
+Circuit diagram of a click generator (FIGURE 7/Q.414).
+
+FIGURE 7/Q.414
+
+Click generator
+
+##### 2.3.1.6 *Response time*
+
+The response time of the signal sender is defined as the interval between the instant when the change signalling condition command is applied to the sender and the instant at which the envelope of the signalling frequency, measured at the group distribution frame or at an equivalent point, reaches half of its value in the steady state. For each of the two possible changes of signalling condition the response time must be less than 7 ms.
+
+###### Recommendation Q.415
+
+#### 2.3.2 SIGNAL RECEIVER
+
+##### 2.3.2.1 *Recognition of the tone-on condition*
+
+The receiver must have assumed or assume the *tone-on* condition when at the group distribution frame or at an equivalent point:
+
+- the level of the received frequency has risen to $-27$ dBm0 or more;
+- its frequency lies between $3825 \pm 6$ Hz.
+
+The level of $-27$ dBm0 specified above does not preclude the use of individual adjustments in the channel translating equipment to compensate for constant level deviations.
+
+##### 2.3.2.2 *Recognition of the tone-off condition*
+
+The receiver must have assumed or assume the *tone-off* condition when the level of the test frequency, at the group distribution frame or at an equivalent point, has dropped to the values shown in Figure 8/Q.415.
+
+
+
+Detailed description: The graph plots level in dBm0 on the y-axis against frequency f in Hz on the x-axis. The y-axis has marked values at +14, +4, 0, and -33. The x-axis has marked values at 2500, 3550, 3750, 3900, 4100, and 4250 Hz. The plot is a piecewise linear boundary. The area above the line represents the 'tone-off' recognition zone. The diagram is identified by the code CCITT-49210.
+
+| Frequency (Hz) | Level (dBm0) |
+|----------------|--------------|
+| 2500 | +14 |
+| 3550 | 0 |
+| 3750 | -33 |
+| 3900 | -33 |
+| 4100 | +4 |
+| 4250 | +14 |
+
+Graph showing level limits for recognition of the 'tone-off' condition (FIGURE 8/Q.415).
+
+FIGURE 8/Q.415
+
+**Level limits for recognition of the "tone-off" condition**
+
+##### 2.3.2.3 Protection against near-end disturbances
+
+The signal receiver must not change state when any one of the following disturbing signals is applied at the 4-wire output of the associated speech channel looped at the group distribution frame or at an equivalent point:
+
+- a sinusoidal signal whose level as a function of the frequency is shown in Figure 9/Q.415,
+- a transient signal produced by the click generator (described in § 2.3.1.5 above) applied at the point where the channel is connected to the switching equipment, all level adjusting devices being set to such values encountered in practice which give rise to the worst disturbance.
+
+
+
+The graph shows the level limit for a sinusoidal disturbance signal. The y-axis is labeled 'dBm0' and has markings at 0 and +15. The x-axis is labeled 'f' and 'Hz' and has markings at 2500 and 3500. The signal level is constant at +15 dBm0 from 0 to 2500 Hz. At 2500 Hz, the level begins to decrease linearly, reaching 0 dBm0 at 3500 Hz. For frequencies above 3500 Hz, the level remains at 0 dBm0. The text 'CCITT-49220' is printed below the x-axis.
+
+Figure 9/Q.415: Level limit for a sinusoidal disturbance signal. The graph shows dBm0 on the y-axis (0 to +15) and frequency f in Hz on the x-axis (2500 to 3500). The level is constant at +15 dBm0 from 0 to 2500 Hz, then decreases linearly to 0 dBm0 at 3500 Hz, and remains at 0 dBm0 for frequencies above 3500 Hz.
+
+FIGURE 9/Q.415
+
+**Level limit for a sinusoidal disturbance signal to which the signalling receiver must remain insensible**
+
+##### 2.3.2.4 Overall response time of signal sender and receiver
+
+When the modulation equipment is looped at the group distribution frame or at an equivalent point, the overall response time is defined as the interval between the instant when a change signalling condition command is applied to the sender and the moment when the changed signalling condition appears at the receiver output. For each of the two possible changes of signalling condition, the overall response time must be less than 30 ms.
+
+##### 2.3.2.5 Interference by carrier leaks
+
+The requirements stated in §§ 2.3.2.1, 2.3.2.3 and 2.3.2.4 above must be fulfilled in the presence of carrier leaks.
+
+It is assumed that:
+
+- when the receive level of the signalling tone is at its nominal value at the group distribution frame or an equivalent point, each carrier leak is present at a level of $-26$ dBm0;
+- the level of the carrier leak varies proportionally with any variations in the level of the signalling tone.
+
+##### 2.3.2.6 Interference by pilots
+
+The specified signalling system is not intended to work in the presence of those pilots specified by CCITT having a frequency differing by 140 Hz from the nearest multiple of 4 kHz (see Recommendation M.460).
+
+On the other hand, the requirements stated in §§ 2.3.2.1, 2.3.2.2, 2.3.2.3, 2.3.2.4 and 2.3.2.5 above must be met in the presence of any other pilot recommended by the CCITT.
+
+It is assumed that variations in level of the pilot and of the signalling tones are correlated.
+
+### **2.4 INTERRUPTION CONTROL**
+
+#### **2.4.1 General**
+
+In System R2, removal of the tone corresponds to the sending of the seizing and answer signals. Steps must be taken, therefore, to guard against unwanted interruption of the signalling channels resulting in false signalling. Special devices monitor a number of circuits and transmit an indication to each individual equipment as soon as an interruption occurs. The whole protection system against the effect of interruptions is designated by the term *interruption control*
+
+In each case, the response time of the interruption control must be based on the time required to recognize the signalling condition.
+
+The interruption control systems in the two directions of transmission operate independently of each other.
+
+The interruption control specified uses the group pilot to detect interruptions.
+
+#### **2.4.2 Mode of operation of interruption control**
+
+For each direction of transmission of a carrier circuit connection the equipment for interruption control comprises:
+
+- a group pilot generator at the outgoing end;
+- a pilot receiver and a wiring system for signalling the interruption at the incoming end.
+
+In principle, the existing pilots of the carrier system will be used.
+
+The receiver at one end supervises the pilot transmitted by the other end. When a considerable fall in the level of the pilot is detected it is assumed that an interruption has occurred on the signalling channels associated with the carrier circuits. The interruption control equipment then reacts to prevent the unwanted transmission of certain signals on those circuits which have already been seized or to ensure that idle circuits are blocked.
+
+Figure 10/Q.416 shows functionally an arrangement where the pilot receiver controls the relay sets of interrupted circuits.
+
+To ensure proper interruption control, it is essential that the individual transmission or switching equipments should not react to any change of signalling state due to a fault. The action initiated by the interruption control must therefore be completed in less time than the sum of the response time of the signalling receiver and the recognition time for the *tone-off* condition caused by interruption of the signalling channel. Again, to prevent the unwanted transfer of certain signals, interruption control, during re-establishment of the pilot, must return to *alarm off* after an interval long enough for the signalling equipment to revert to normal.
+
+To operate independently for each direction of transmission the incoming end interruption control supervises only the forward direction and, if necessary, initiates an operation at the outgoing end via the line signalling system. Conversely, interruption control at the outgoing end supervises the backward direction of transmission only.
+
+Blocking of a circuit at the outgoing end therefore takes place in two different ways:
+
+- immediate blocking by intervention of interruption control at the outgoing end;
+- blocking on recognition in the backward direction of the *tone-off* condition caused by interruption control intervention at the incoming end.
+
+When the transmission system is re-established, interruption control reverts to normal and the signalling equipment must automatically revert to normal operating.
+
+Since the action to be taken on the individual circuits differs according to their state at the time the fault occurs, the different possibilities are dealt with in detail below.
+
+
+
+The diagram illustrates the interruption control circuit for a four-wire system. It features two main vertical bars representing the outgoing relay set (GRD) on the left and the incoming relay set (GRA) on the right. Between these bars are two horizontal transmission paths. The top path contains a signalling sender (ES) on the left and a signalling receiver (RS) on the right. The bottom path contains a signalling receiver (RS) on the left and a signalling sender (ES) on the right. Pilot generators (GP) and pilot receivers (RP) are connected to the top and bottom paths. Arrows indicate the 'Direction of transmission' from left to right in the top path and right to left in the bottom path. External connections to 'Four-wire circuit' and 'Wiring to other line relay sets' are shown at the ends. The diagram is labeled CCITT-49230.
+
+GP = pilot generator
+ RP = pilot receiver
+ RS = signalling receiver
+ ES = signalling sender
+ GRD = outgoing relay set
+ GRA = incoming relay set
+
+Diagram of interruption control circuit (FIGURE 10/Q.416).
+
+FIGURE 10/Q.416
+**Protection from the effect of interruptions (interruption control)**
+
+##### 2.4.2.1 *Mode of operation of interruption control at the incoming end (transmission interrupted in the forward direction)*
+
+###### a) *Circuit in idle state*
+
+Transition of interruption control to alarm brings about:
+
+- i) removal of the tone in the backward direction by locking of the sending unit in the *tone-off* condition;
+- ii) locking of the receiving unit in its position, i.e. in the *tone-on* condition.
+
+The effect of operation i) is to block the circuit at the outgoing end against possible seizing; operation ii) prevents incorrect recognition of seizing of the incoming circuit.
+
+Return of interruption control to normal ensures return to the idle state of the circuits affected by the fault, by switching sending units at the incoming end to the *tone-on* condition.
+
+###### b) *Circuit seized prior to answered state*
+
+Transition of interruption control to alarm brings about:
+
+- i) locking of the sending unit in its position, i.e. in the *tone-on* condition;
+- ii) locking of the receiving unit in its position, i.e. in the *tone-off* condition;
+- iii) start of a time-out device which after a certain interval clears the chain beyond the faulty circuit; this timing arrangement may be the one specified in Recommendation Q.118, § 4.3.3.
+
+Operation i) prevents the transfer of an answer signal while interruption control is in action. If the called subscriber answers before the time out delay mentioned in iii) above has elapsed, then the timer is stopped. For existing equipment this requirement may not apply. If the called subscriber clears while interruption control is active, the part of the connection beyond the faulty circuit must be released immediately.
+
+Operation iii) prevents blocking of the called subscriber's line if the fault persists; short breaks, on the other hand, have no effect.
+
+When the caller clears, operations i) and ii) block the faulty circuit against any new seizure even when the backward signalling channel is still intact; since the release-guard signal has not been sent the outgoing circuit cannot return to the idle state.
+
+When interruption control reverts to normal before the called subscriber has answered, the call may still mature normally, provided the caller is holding.
+
+If the called subscriber has answered during the time-out delay and the interruption control reverts to normal with both the calling and called subscribers holding, the answer signal is sent immediately.
+
+If at the moment when interruption control reverts to normal the called subscriber has already cleared, operation ii) ensures that in all cases the release-guard sequence takes place as in § 2.2.2.6 a) above (either immediately if the outgoing exchange has already sent the clear-forward signal or when the caller clears). If, on the other hand, the called subscriber is still holding and the outgoing exchange is already sending the clear-forward signal when interruption control reverts to normal the circuit returns to the idle state at the outgoing end as described in § 2.2.2.6 b) above.
+
+###### c) *Circuit in answered state*
+
+Transition of interruption control to alarm brings about:
+
+- i) locking of the sending unit in its position, i.e. in the *tone-off* condition;
+- ii) locking of the receiving unit in its position, i.e. in the *tone-off* condition.
+
+When the caller clears, operation i) blocks the faulty circuit against any new seizure, even when the backward signalling channel is still intact; since the release-guard signal has not been sent, the outgoing circuit cannot return to the idle state.
+
+When the called subscriber clears, the part of the connection beyond the faulty circuit (including the called subscriber's line) must be released immediately.
+
+When interruption control reverts to normal with both subscribers still on the line, the connection is maintained.
+
+When the caller has already cleared by the time the interruption control reverts to normal, the release-guard sequence is carried out as in Recommendation Q.412, § 2.2.2.6 b) or c).
+
+###### d) *Circuit in clear-back state*
+
+Transition of interruption control to alarm causes:
+
+- i) locking of the sending unit in its position, i.e. in the *tone-on* condition;
+- ii) locking of the receiving unit in its position, i.e. in the *tone-off* condition;
+- iii) immediate release of the part of the connection beyond the faulty circuit (including the called subscriber's line).
+
+When interruption control reverts to normal, the release-guard signal is sent as in Recommendation Q.412, § 2.2.2.6 c) as soon as the clear-forward signal is recognized.
+
+###### e) *Circuit in release*
+
+When interruption control functions after a clear-forward signal has been recognized at the incoming end, it causes:
+
+- i) locking of the sending unit in the *tone-off* condition; if at the instant interruption control operates, the *tone-on* condition exists in the backward direction, it will be switched to the *tone-off* condition following recognition of the clear-forward signal and locking in the *tone-off* condition can take place as prescribed;
+- ii) locking of the receiving unit in its position, i.e. in the *tone-on* condition.
+
+The effect of operation i) is to guard the faulty circuit from a new seizure at the outgoing exchange.
+
+Operation ii) ensures the release of the part of the connection beyond the faulty circuit (including the called subscriber's line).
+
+When interruption control reverts to normal the *tone-on* condition is established in the backward direction and causes the circuit at the outgoing exchange to return to the idle state.
+
+##### 2.4.2.2 *Mode of operation of interruption control at the outgoing end* (transmission in the backward direction interrupted)
+
+###### a) *Circuit in idle state*
+
+Transition of interruption control to alarm is immediately followed by blocking of the outgoing circuit.
+
+###### b) *Circuit seized but not in answered state (including clear-back)*
+
+- i) Transition of interruption control to alarm causes locking of the receiving unit in its position, i.e. the *tone-on* condition. This operation prevents recognition of an answer signal or return to the *answered* state should the called subscriber have cleared.
+- ii) As soon as a clear-forward signal is sent on the part of the connection preceding the faulty circuit, it must be retransmitted; the tone must therefore be established in the forward direction to ensure, assuming that the forward signalling channel is left intact, that the part of the connection beyond the faulty circuit is released.
+- iii) When interruption control reverts to normal, the tone may already have been sent in the forward direction as a clear-forward signal. If the forward signalling channel has remained intact, recognition at the incoming end of the *tone-on* condition will have caused generation of the release-guard sequence which, because of the fault, will not have been received at the outgoing end. Exceptionally, therefore, return of the outgoing circuit to the idle state must take place simply on recognition of *tone-on* in the backward direction without necessarily taking into account time-out T1.
+
+###### c) *Circuit in answered state*
+
+In this case transition of interruption control to alarm does not cause immediate action. A clear-forward signal sent on the part of the connection preceding the faulty circuit must be repeated forward to ensure that, if the forward signalling channel is left intact, the part beyond the faulty circuit is cleared.
+
+Once the interruption control reverts to normal the connection is maintained provided the caller and the called subscriber are still holding. On the other hand, by the time the interruption control reverts to normal the clear-forward signal may already have been sent and the situation will be the one described in § 2.4.2.2 b), iii).
+
+###### d) *Circuit in release*
+
+[See § 2.4.2.2 b), iii).]
+
+#### 2.4.3 *Clauses on interruption control equipment*
+
+Adoption of thresholds with widely differing levels makes for economy in the design of interruption control equipment. Against this must be set the fact that the device cannot cope with the effects of certain slow drops in level. However, the probability of these occurring in practice is very small.
+
+##### 2.4.3.1 *Pilots*
+
+Interruption control uses the 84.08 kHz group pilot or by bilateral agreement and, at the request of the receiving end country, the 104.08 kHz group pilot.
+
+However, if the ends of the supergroup link coincide with the end of the five group links it is carrying, the supergroup pilot may also be used.
+
+##### 2.4.3.2 *Alarm-on threshold*
+
+Interruption control must pass to *alarm-on* when the pilot level, measured at the group distribution frame or at an equivalent point, drops to $-29$ dBm0.
+
+##### 2.4.3.3 *Alarm-off threshold*
+
+Interruption control must revert to *alarm-off*, i.e. normal when the pilot level, measured at the group distribution frame or at an equivalent point, rises to $-24$ dBm0.
+
+##### 2.4.3.4 *Response time for a drop in level*
+
+Interruption control must pass from normal to alarm-on within an interval $t \downarrow$ such that:
+
+$$5 \text{ ms} \leq t \downarrow \leq t_{rs \min} + 13 \text{ ms}$$
+
+when the pilot level, measured at the group distribution frame or at an equivalent point, suddenly drops from its nominal level to $-33$ dBm0.
+
+In the above formula, $t_{rs \min}$ is the minimum response time of the signalling receiver for a drop in level, taking into account a possible variation of $\pm 3$ dB in the signalling tone level from its nominal value, the level being measured on the receiving side of the group distribution frame or at an equivalent point.
+
+The figure of 13 ms in the above formula is derived on the assumption that the output of the interruption control equipment acts upon the input of the device which regulates the recognition time for the *tone-on* and *tone-off* conditions $(20 \pm 7 \text{ ms})^1$ , i.e. absence of a direct current signal at this input for a period of up to 13 ms has no relevance.
+
+##### 2.4.3.5 *Response time for rise in level*
+
+Interruption control must revert from the alarm-on to normal in an interval $t \uparrow$ such that:
+
+$$t_{rs \max} - 13 \text{ ms} \leq t \uparrow \leq 500 \text{ ms}$$
+
+when the pilot level, measured at the group distribution frame or at an equivalent point, suddenly rises from its nominal level to $-33$ dBm0.
+
+In the above formula, $t_{rs \max}$ is the maximum response time of the signalling receiver for a rise in level, taking into account a possible variation of $\pm 3$ dB in the signalling tone level from its nominal value, the level being measured on the receiving side of the group distribution frame or at an equivalent point.
+
+The figure of 13 ms in the above formula is derived on the assumption that the output of the interruption control equipment acts upon the input of the device which regulates the recognition time for *tone-on* and *tone-off* condition $(20 \pm 7 \text{ ms})^1$ i.e. absence of a direct current signal at this input for a period of up to 13 ms has no relevance.
+
+##### 2.4.3.6 *Precautions against noise*
+
+An interruption may produce increased noise on the group link. Interruption control must be capable of distinguishing between the pilot itself and a high level noise simulating the pilot.
+
+Interruption control must not revert to normal in the presence of white noise having a spectral power density of not more than $-47$ dBm0 per Hz.
+
+To facilitate the design of interruption control equipment operating satisfactorily at high noise levels, the upper limit of 500 ms for $t \uparrow$ has been specified.
+
+---
+
+1) If the value $(40 \pm 10)$ ms is exclusively applied, it is possible to use the minimum value of 30 ms instead of 13 ms for the interruption control device.
+
+## SECTION 3
+
+## LINE SIGNALLING, DIGITAL VERSION
+
+### Recommendation Q.421
+
+### 3.1 DIGITAL LINE SIGNALLING CODE
+
+#### 3.1.1 General
+
+Primary PCM multiplexes (see Recommendations G.732 and G.734) economically provide more than one signalling channel per speech circuit in each direction of transmission. By making use of the increased signalling capacity, simplification of the outgoing and incoming switching equipment can be achieved since the timing conditions necessary for the System R2 line signalling, analogue version, are not required. For this reason the digital version of System R2 line signalling is recommended for use on PCM systems in national and international public switched networks and is specified below.
+
+*Note* – The continuous line signalling scheme specified for FDM systems may also be used on PCM systems by utilizing one signalling channel only in each direction. In this case relay sets designed for the continuous line signalling system on FDM channels can be used provided that the functions specified for the interruption control on FDM circuits (see Recommendation Q.416) are performed by use of the local alarm facility provided by PCM equipment. This method of line signalling on PCM systems is not recommended for use on international circuits.
+
+The digital version of System R2 line signalling uses two signalling channels in each direction of transmission per speech circuit. These signalling channels are referred to as $a_f$ and $b_f$ for the forward direction (i.e. the direction of call set-up) and $a_b$ and $b_b$ for the backward direction.
+
+Under normal conditions:
+
+- The $a_f$ channel identifies the operating condition of the outgoing switching equipment and reflects the condition of the calling subscriber's line.
+- The $b_f$ channel provides a means for indicating a failure in the forward direction to the incoming switching equipment.
+- The $a_b$ channel reflects the condition of the called subscriber's line (on hook or off hook).
+- The $b_b$ channel indicates the idle or seized state of the incoming switching equipment.
+
+The line signals are transmitted link-by-link.
+
+The digital version of System R2 line signalling also specifies a means for appropriate action in the case of faulty transmission conditions on the PCM multiplex, see Recommendation Q.424.
+
+The signalling system is specified for one-way operation, but both-way operation is also possible (see § 3.2.7 below).
+
+#### 3.1.2 *Signalling code*
+
+Table 2/Q.421, shows the signalling code on the PCM line under normal conditions.
+
+TABLE 2/Q.421
+
+| State of the circuit | Signalling code | | | |
+|----------------------|-----------------|-------|----------|-------|
+| | Forward | | Backward | |
+| | $a_f$ | $b_f$ | $a_b$ | $b_b$ |
+| Idle/Released | 1 | 0 | 1 | 0 |
+| Seized | 0 | 0 | 1 | 0 |
+| Seizure acknowledged | 0 | 0 | 1 | 1 |
+| Answered | 0 | 0 | 0 | 1 |
+| Clear-back | 0 | 0 | 1 | 1 |
+| Clear-forward | 1 | 0 | 0 | 1 |
+| | | | or | |
+| | | | 1 | 1 |
+| Blocked | 1 | 0 | 1 | 1 |
+
+##### Recommendation Q.422
+
+### 3.2 CLAUSES FOR EXCHANGE LINE SIGNALLING EQUIPMENT
+
+#### 3.2.1 *Recognition of a change of signalling code*
+
+##### 3.2.1.1 *Signalling channel transitions*
+
+The recognition time for a transition from 0 to 1 or vice versa on a signalling channel is $20 \pm 10$ ms. This value presupposes the existence of protection against the effects of faulty transmission conditions on the PCM multiplex.
+
+The recognition time is defined as the duration that the signals representing 0 or 1 must have at the output of the terminal equipment of a signalling channel in order to be recognized by the exchange equipment.
+
+##### 3.2.1.2 *Change of signalling code*
+
+Recognition of a change of signalling code is thus defined as either of the following:
+
+- Recognition of a transition detected on one signalling channel with no transition detected on the second signalling channel during the recognition period.
+- Recognition of a transition detected on the second signalling channel during the recognition period already being applied to the first signalling channel. In this case, a change of signalling code is recognized only when both recognition timing periods have elapsed.
+
+#### 3.2.2 *Sent signal time tolerance*
+
+The time difference between application of transitions intended to be simultaneous on two signalling channels in the same direction of transmission must not exceed 2 ms.
+
+#### 3.2.3 *States and procedures under normal conditions* (see Table 2/Q.421)
+
+In the forward direction $b_f = 0$ is established permanently.
+
+##### 3.2.3.1 *Idle state*
+
+In the idle state the outgoing end sends $a_f = 1$ , $b_f = 0$ . At the incoming end this results in sending $a_b = 1$ , $b_b = 0$ in the backward direction, provided that the switching equipment at the incoming end of the circuit is idle.
+
+##### 3.2.3.2 *Seizing procedure*
+
+###### i) *Seizure*
+
+Seizing should occur only if $a_b = 1$ , $b_b = 0$ is recognized. The outgoing end changes $a_f = 1$ into $a_f = 0$ . The code $a_f = 0$ , $b_f = 0$ must be maintained until the seizing acknowledgement signal is recognized. In this way the outgoing switching equipment will only be able to send the clear-forward signal after recognition of the seizing acknowledgement signal.
+
+###### ii) *Seizure acknowledgement*
+
+After having recognized the seizing signal, the incoming end sends $a_b = 1$ , $b_b = 1$ as an acknowledgement.
+
+##### 3.2.3.3 *Answering*
+
+The off-hook condition of the called subscriber's line provokes the incoming switching equipment to send $a_b = 0$ , $b_b = 1$ .
+
+The answered state must be established on the preceding link immediately after it is recognized: see also § 3.2.3.6 below.
+
+##### 3.2.3.4 *Clear-back*
+
+The on-hook condition of the called subscriber's line provokes the incoming switching equipment to send $a_b = 1$ , $b_b = 1$ . The clear-back state must be established on the preceding link immediately after it is recognized: see also § 3.2.3.6 below.
+
+##### 3.2.3.5 *Clear-forward procedure*
+
+The cleared condition of the calling subscriber's line or the release of the outgoing switching equipment will normally result in sending $a_f = 1$ , $b_f = 0$ . The outgoing switching equipment will not be restored to the idle state until recognition of the code $a_b = 1$ , $b_b = 0$ : see also §§ 3.2.3.2, 3.2.3.6 and Table 3/Q.422.
+
+##### 3.2.3.6 *Release procedure*
+
+Recognition of the clear-forward signal in the incoming switching equipment initiates the release of the succeeding link even though answering or clearing by the called party has occurred. Upon complete release of the incoming switching equipment, the code $a_b = 1$ , $b_b = 0$ is established on the circuit. This will cause the circuit to be restored to the idle state and the outgoing switching equipment to become available for another call.
+
+##### 3.2.3.7 *Blocking and unblocking procedure*
+
+Blocking of an idle circuit to new calls at the outgoing end must occur as soon as $a_b = 1$ and $b_b = 1$ is recognized: see also Tables 3/Q.422 and 4/Q.422.
+
+The recognition of $a_b = 1$ , $b_b = 0$ restores the circuit to the idle state.
+
+#### 3.2.4 *Actions appropriate to various signalling conditions*
+
+In addition to normal conditions described in Table 2/Q.421 other conditions due to faults may be encountered. Tables 3/Q.422 and 4/Q.422 indicate the states appropriate to each signalling code recognized and the actions to be taken at the outgoing and incoming end respectively of a circuit operated with the digital version of System R2 line signalling.
+
+##### 3.2.4.1 Outgoing end
+
+TABLE 3/Q.422
+
+| Normal state at the out-going end | Sent code | Received code | | | |
+|-----------------------------------|--------------------|----------------------|----------------------|----------------------|----------------------|
+| | | $a_b = 0, b_b = 0$ | $a_b = 0, b_b = 1$ | $a_b = 1, b_b = 0$ | $a_b = 1, b_b = 1$ |
+| Idle/Released | $a_f = 1, b_f = 0$ | Abnormal, see Note 1 | Abnormal, see Note 1 | Idle | Blocked |
+| Seized | $a_f = 0, b_f = 0$ | Abnormal, see Note 2 | Abnormal, see Note 2 | Seized see Note 2 | Seizure acknowledged |
+| Seizure acknowledged | $a_f = 0, b_f = 0$ | Abnormal, see Note 3 | Answered | Abnormal, see Note 3 | Seizure acknowledged |
+| Answered | $a_f = 0, b_f = 0$ | Abnormal, see Note 4 | Answered | Abnormal, see Note 4 | Clear-back |
+| Clear-back | $a_f = 0, b_f = 0$ | Abnormal, see Note 4 | Answered | Abnormal, see Note 4 | Clear-back |
+| Clear-forward | $a_f = 1, b_f = 0$ | Abnormal, see Note 1 | Clear-forward | Released = Idle | Clear-forward |
+| Blocked | $a_f = 1, b_f = 0$ | Abnormal, see Note 1 | Abnormal, see Note 1 | Idle | Blocked |
+
+*Note 1* – In these abnormal conditions the outgoing end must prevent a new seizure of the circuit. A delayed alarm should also be given (see § 3.2.6).
+
+*Note 2* – Non-recognition of the seizing acknowledgement signal 100 ms-200 ms after sending the seizing signal on a terrestrial link or 1-2 seconds after sending the seizing signal on a satellite link results in an alarm and either congestion information being sent backward or a repeat attempt being made to set up the call. The outgoing end must prevent a new seizure of the circuit. When the seizing acknowledgement signal is recognized after the time-out period has elapsed, the clear-forward signal must be sent.
+
+*Note 3* – Receipt of $b_b = 0$ by the outgoing switching equipment for 1-2 seconds after recognition of the seizing acknowledgement signal and prior to recognition of the answer signal, results in an alarm and either congestion information being sent backward or a repeat attempt being made to set up the call. The outgoing end must prevent new seizures of the circuit. When $b_b$ reverts to 1 after the 1-2 seconds timeout period has elapsed, the clear-forward signal must be sent.
+
+*Note 4* – In the case of recognition of $b_b = 0$ whilst in the answered or clear-back state, immediate action is not necessary. On receipt of clearing from the preceding link, the clear-forward signal ( $a_f = 1, b_f = 0$ ) must not be sent until $b_b$ is restored to 1. A delayed alarm should also be given.
+
+##### 3.2.4.2 Incoming end
+
+TABLE 4/Q.422
+
+| Normal state at the incoming end | Sent code | Received code | | | |
+|----------------------------------|------------------------------------------------|-------------------------------|---------------------|-----------------------------|---------------------|
+| | | $a_f = 0, b_f = 0$ | $a_f = 0, b_f = 1$ | $a_f = 1, b_f = 0$ | $a_f = 1, b_f = 1$ |
+| Idle/Released | $a_b = 1, b_b = 0$ | Seized | Fault
see Note 1 | Idle | Fault
see Note 1 |
+| Seizure acknowledged | $a_b = 1, b_b = 1$ | Seizure acknowledged | Fault
see Note 2 | Clear-forward | Fault
see Note 2 |
+| Answered | $a_b = 0, b_b = 1$ | Answered | Fault
see Note 3 | Clear-forward | Fault
see Note 3 |
+| Clear-back | $a_b = 1, b_b = 1$ | Clear-back | Fault
see Note 4 | Clear-forward | Fault
see Note 4 |
+| Clear-forward | $a_b = 0, b_b = 1$
or
$a_b = 1, b_b = 1$ | Abnormal seized
see Note 7 | Fault
see Note 7 | Clear-forward
see Note 7 | Fault
see Note 7 |
+| Blocked | $a_b = 1, b_b = 1$ | Abnormal seized
see Note 5 | Fault
see Note 6 | Blocked | Fault
see Note 6 |
+
+*Note 1* – When in the idle/released state $b_f$ changes to 1, $b_b$ must be changed to 1.
+
+*Note 2* – In these cases a time-out device is started, which after a certain interval clears the connection beyond the faulty circuit: this timing arrangement may be the one specified in Recommendation Q.118, Section 4.3.3. If the answer signal is recognized during the time-out delay, the timer is stopped but the answer signal is not sent on the preceding link until recognition of $a_f = 0, b_f = 0$ . If the clear-back signal is recognized while the fault persists, the connection beyond the faulty circuit must be released immediately. Additionally, when the incoming register has not started to send the last backward signal, the rapid release procedure described in Note 5 may be used.
+
+*Note 3* – In these cases no action is taken until the clear-back signal is recognized, at which stage the connection beyond the faulty circuit is immediately released.
+
+*Note 4* – Under these conditions the succeeding link must be released immediately.
+
+*Note 5* – In this case immediate action is not necessary. However, rapid release of the circuit should occur if the incoming end simulates answer by sending $a_b = 0, b_b = 1$ .
+
+*Note 6* – Under these conditions no action is taken.
+
+*Note 7* – After clear-forward signal is recognized and until the code $a_b = 1, b_b = 0$ is sent, all transitions in the forward direction shall be ignored.
+
+#### 3.2.5 *Abnormal conditions*
+
+##### 3.2.5.1 *Special release arrangements*
+
+- a) If an exchange where an outgoing R2 register is situated recognizes $a_b = 0$ , $b_b = 1$ (premature answer) before an address-complete signal A-6 or a Group B signal is received, the connection must be released. Congestion information is then sent backward or a repeat attempt is made to set up the call.
+- b) In the cases of non-receipt of the answer signal, of delay in clearing by the calling subscriber in automatic working and of non-receipt of the clear-forward signal by the incoming exchange after the clear-back signal has been sent, the provisions of Recommendation Q.118 apply.
+
+##### 3.2.5.2 *Safeguard against failures*
+
+The PCM equipment and the exchange line signalling equipment should be designed in such a way that at least those faults which are most likely to occur in this equipment or in the interconnecting cables, result in blocking of the circuit at the outgoing end and in the ultimate clearing of the connection beyond the incoming switching equipment. This can be achieved, as far as possible, by ensuring that $a = 1$ , $b = 1$ is sent on line upon:
+
+- removal of PCM or switching equipment by maintenance personnel;
+- occurrences of abnormal conditions (e.g. open wire, low voltage) in switching equipment.
+
+#### 3.2.6 *Alarms for technical staff*
+
+According to Recommendation Q.117, an alarm must in principle be given to the technical staff upon recognition of abnormal conditions.
+
+Arrangements for these alarms are to be specified by the Administrations.
+
+It is recommended that a delayed alarm be given at the outgoing end for the procedure described under § 3.2.3.7 above (blocking) and for the following reasons:
+
+- when the abnormal conditions covered by Note 1 to Table 3/Q.422 are applicable;
+- when the seizing acknowledgement signal is not recognized within the time specified in Note 2 to Table 3/Q.422 after sending the seizing signal;
+- when, after recognition of the seizing acknowledgement signal and prior to recognition of the answer signal, $b_b = 0$ is received for 1-2 seconds;
+- when the abnormal conditions covered by Note 4 to Table 3/Q.422 are applicable.
+
+It is also recommended that a delayed alarm be given under PCM failure conditions specified in Recommendations G.732 and G.734.
+
+#### 3.2.7 *Both-way working*
+
+System R2 is specified for one-way working, but in principle the line signalling code detailed in Recommendation Q.421 is also suitable for use on both-way circuits. Where Administrations have undertaken, by bilateral agreement, to use both-way working, the clauses and additional specifications for exchange signalling equipment detailed in §§ 3.2.7.1 and 3.2.7.2 below, must be observed.
+
+##### 3.2.7.1 *Procedures under normal conditions*
+
+###### a) *Double seizure*
+
+Double seizure is assumed if the outgoing equipment is in a seized state and the signalling code $a_b = 0$ , $b_b = 0$ is recognized instead of $a_b = 1$ , $b_b = 1$ (seizure acknowledgement). In such a situation the connection must be released at both ends and congestion information sent to the calling subscriber or a repeat attempt must be made. On recognition of double seizure the line signalling equipment at both ends must maintain the seized state for a minimum of 100 ms after which the clear-forward signal $a_f = 1$ , $b_f = 0$ must be sent.
+
+100 ms after sending the clear-forward signal and on recognition of $a_b = 1$ , $b_b = 0$ each end may assume the idle state.
+
+The clear-forward state $a_f = 1$ , $b_f = 0$ must be maintained for at least 100 ms to ensure that it is recognized at the other end.
+
+In the sense of preventive action it is recommended that an opposite order of circuit selection be used by each exchange of a both-way circuit group to minimize double seizure.
+
+###### b) *Requirements for circuit release*
+
+When a both-way circuit is released, the end which acted as the incoming end must maintain the signalling code $a_b = 1$ , $b_b = 0$ for at least 100 ms to ensure that the signal is recognized at the other end after which the circuit becomes idle.
+
+###### c) *Blocking and unblocking procedure*
+
+When a both-way circuit is blocked manually in its idle state at one end (e.g. end B) the blocking signal must be sent to the other end (A). The circuit must then be kept blocked locally (at end A) against all calls in the A to B traffic direction as long as the blocked state persists in the B to A direction.
+
+In order to avoid permanent blocking, end A should maintain the signalling code $a = 1$ , $b = 0$ in the direction A to B.
+
+When the blocked state is removed, end B must send the clear-forward signal and must maintain that state for at least 100 ms, before assuming the idle state.
+
+##### 3.2.7.2 *Special arrangement*
+
+The physical realization of signalling equipment terminating a bothway circuit may allow that part of the equipment concerned with outgoing calls to be removed without preventing the remaining equipment from being used for incoming calls. In this case it is only necessary to block the circuit locally against outgoing calls and a blocking signal need not be sent to the other end.
+
+###### **Recommendation Q.424**
+
+### **3.3 PROTECTION AGAINST THE EFFECTS OF FAULTY TRANSMISSION**
+
+Faulty transmission conditions in PCM systems can lead to degradation of the speech channels and erroneous signalling. In the case of primary PCM multiplex equipment operating at 2048 kbit/s failures due to loss of frame or multi-frame alignment and/or failure of any other important function results in both PCM terminals going into alarm condition in accordance with Recommendations G.732 and G.734.
+
+Thus both PCM terminals apply the state corresponding to state 1 on the PCM line on each "receive" signalling channel at the interfaces with the switching equipment, as indicated in Table 4 of Recommendation G.732. In this way, the incoming switching equipment receives the equivalent of $a_f = 1$ , $b_f = 1$ on the PCM line and the outgoing switching equipment receives the equivalent of $a_b = 1$ , $b_b = 1$ .
+
+These characteristics are taken into account in the present specifications (see § 3.2.4) so that:
+
+- at the outgoing end (see Table 3/Q.422) a PCM fault results in a blocked state, seizure acknowledged state or clear-back state. This means that all circuits in the idle state of a faulty PCM multiplex will be blocked against seizure and that seized circuits will go to or remain in the seizure acknowledged or clear-back state;
+- at the incoming end (see Table 4/Q.422) a PCM fault can be identified and appropriate actions can be taken.
+
+When the signalling equipment is a part of a digital exchange, it may receive alarm indications in a form other than both signalling bits in state one. The failure may be detected by the signalling equipment or an indication be received from the PCM terminal according to Recommendation G.734.
+
+When the signalling equipment recognizes a failure it must:
+
+- block the detection of signalling transitions to avoid recognition of erroneous signalling codes caused by the failure. This action must be taken as soon as possible and at least within 3 ms as specified in Recommendation G.734 for a PCM terminal,
+- react as specified in Tables 3/Q.422 and 4/Q.422 when a signalling code $a = 1, b = 1$ is detected at the input of signalling equipment situated at the analogue access of a PCM terminal equipment complying with Recommendation G.732.
+
+#### Recommendation Q.430
+
+### 3.5 CONVERSION BETWEEN ANALOGUE AND DIGITAL VERSIONS OF SYSTEM R2 LINE SIGNALLING
+
+This Recommendation is applicable to a conversion equipment placed on the circuit between two switching exchanges each using one of the two versions specified for System R2 line signalling. Owing to this particular use, all the specifications for the two versions of the line signalling may not be fully observed. Nevertheless, the diagrams which follow are based on the principles of CCITT Recommendations Q.411, Q.412 and Q.416 for the analogue version and on Recommendations Q.421, Q.422 and Q.424, for the digital version. The only time conditions taken into account in this Recommendation are those set out in the aforementioned Recommendations. The operation of the interruption control device is also, wherever possible, that specified in Recommendation Q.416. As stated in that Recommendation, the receiver is blocked immediately whenever pilot tone off is detected: since this is a routine operation, it has not been represented explicitly in the diagrams.
+
+The conversion diagrams have been divided into four parts:
+
+- for conversion between the analogue version at the incoming end and the digital version at the outgoing end, into:
+ - incoming analogue,
+ - outgoing digital;
+- for conversion between the digital version at the incoming end and the analogue version at the outgoing end, into:
+ - incoming digital,
+ - outgoing analogue.
+
+It should be noted, however, that this Recommendation can be simplified with respect to alarm processing when the conversion equipment is connected directly at the input or output of a switching exchange; the processes necessary for this application are shown on the diagrams with thickened lines.
+
+#### 1 Drawing conventions
+
+- tone
+
+| | |
+|----------------------------|-------------------|
+| $tf = 1$ tone on forward | } When recognized |
+| $tf = 0$ tone off forward | |
+| $tb = 1$ tone on backward | |
+| $tb = 0$ tone off backward | |
+| $p = 1$ pilot tone on | |
+| $p = 0$ pilot tone off | |
+
+- signalling bits
+
+The conventions are those of Recommendation Q.421.
+
+#### 2 Conversion incoming analogue version to outgoing digital version
+
+##### 2.1 Incoming analogue
+
+
+
+A block diagram of a conversion unit. A central rectangular block has three input lines on its left side and five output lines on its right side. The input lines are labeled 'tf', 'p', and 'tb' from top to bottom. The output lines are labeled 'seizure', 'clear forward', 'answer', 'clear back', 'circuit free', and 'blocking' from top to bottom. Arrows indicate the direction of signal flow into and out of the block. Below the block, the text 'CCITT- 55980' is written.
+
+Block diagram of a conversion unit for incoming analogue signals.
+
+List of timers:
+
+T2: Recommendation Q.412 (§ 2.2.2.7)
+
+T3: 2 to 3 mn Recommendation Q.118 (§ 4.3.3)
+
+In sheets 2 and 4 the diagram for group pilot supervision is given.
+
+In sheets 3 and 5 the diagram for supergroup pilot supervision is given.
+
+Sheet 1 is for group and supergroup pilot supervision.
+
+
+
+Connector
+reference
+
+```
+
+stateDiagram-v2
+ state "00 Idle\ntf = 1, tb = 1, p = 1" as Idle
+ state "Seizure\ntf = 0" as SeizureInput
+ state "Seizure" as SeizureState
+ state "Blocking" as BlockingInput
+ state "Blocking\ntb = 0" as BlockingState
+ state "11 Blocked" as Blocked
+ state "Pilot off\np = 0" as PilotOffInput
+ state "Blocking\ntb = 0" as BlockingState2
+ state "13 Idle,\npilot off" as IdlePilotOff
+
+ [*] --> Idle
+ Idle --> SeizureInput
+ Idle --> BlockingInput
+ Idle --> PilotOffInput
+
+ SeizureInput --> SeizureState
+ SeizureState --> (21): 2, 3
+ (21) --> (11): 1
+
+ BlockingInput --> BlockingState
+ BlockingState --> Blocked: 11
+
+ PilotOffInput --> BlockingState2
+ BlockingState2 --> (13): 1
+ (13) --> IdlePilotOff
+
+ state "Seizure\ntf = 0" as SeizureInput2
+ state "14 Analogue\nseized,\ndigital\nblocked" as AnalogueSeized
+ state "Circuit\nfree" as CircuitFree
+ state "Unblocking\ntb = 1" as Unblocking
+ state "00 Idle" as Idle2
+ state "Pilot off\np = 0" as PilotOffInput2
+ state "12 Blocked,\npilot off" as BlockedPilotOff
+ state "Pilot on\np = 1" as PilotOnInput
+ state "Circuit\nfree" as CircuitFree2
+ state "Blocking" as BlockingInput2
+ state "Pilot on\np = 1" as PilotOnInput2
+ state "Unblocking\ntb = 1" as Unblocking2
+ state "00 Idle" as Idle3
+
+ Blocked --> SeizureInput2
+ Blocked --> CircuitFree
+ Blocked --> PilotOffInput2
+ Blocked --> BlockingInput2
+ Blocked --> PilotOnInput2
+
+ SeizureInput2 --> (14): 1
+ (14) --> AnalogueSeized
+ CircuitFree --> Unblocking
+ Unblocking --> Idle2
+ PilotOffInput2 --> BlockedPilotOff
+ BlockedPilotOff --> PilotOnInput
+ PilotOnInput --> (11): 1
+ BlockedPilotOff --> CircuitFree2
+ CircuitFree2 --> (13): 1
+ BlockingInput2 --> BlockedPilotOff
+ PilotOnInput2 --> Unblocking2
+ Unblocking2 --> Idle3
+
+ state "Clear\nforward\ntf = 1" as ClearForward
+ state "Start T2" as StartT2
+ state "Pilot off\np = 0" as PilotOffInput3
+ state "15 Pilot off,\ndigital\nblocked" as PilotOffDigitalBlocked
+ state "Pilot on\np = 1" as PilotOnInput3
+ state "Circuit\nfree" as CircuitFree3
+ state "Circuit\nfree" as CircuitFree4
+
+ AnalogueSeized --> ClearForward
+ ClearForward --> StartT2
+ StartT2 --> (32): 4, 5
+
+ AnalogueSeized --> PilotOffInput3
+ PilotOffInput3 --> PilotOffDigitalBlocked
+ PilotOffDigitalBlocked --> PilotOnInput3
+ PilotOnInput3 --> (14): 1
+ PilotOffDigitalBlocked --> CircuitFree4
+
+ AnalogueSeized --> CircuitFree3
+
+```
+
+11, 13
+21
+
+14
+
+11, 13
+
+32
+
+14
+
+CCITT-60881
+
+Flowchart showing the conversion of incoming analogue System R2 line signalling to outgoing digital version. It starts from an Idle state and branches into Seizure, Blocking, and Pilot off paths based on signal values for tf, tb, and p. States include Blocked, Analogue seized digital blocked, Idle pilot off, and Pilot off digital blocked. Transitions are triggered by signal changes like tf=0, tb=0, p=0, etc. Connector references like 11, 13, 14, 21, 32 are used to link different parts of the process.
+
+**System R2 line signalling: conversion of incoming analogue version to outgoing digital version**
+(Sheet 1 of 5)
+
+Connector reference
+
+
+
+```
+
+ graph TD
+ Start((1, 2, 3)) --> S1((21 Seized prior to answer))
+ S1 --> S1_params[tf = 0, tb = 1, p = 1]
+ S1_params --> A1[Answer]
+ S1_params --> CF1[Clear forward tf = 1]
+ S1_params --> PO1[Pilot off p = 0]
+
+ A1 --> A2{{Answer tb = 0}}
+ A2 --> C31((31 4, 5))
+
+ CF1 --> CF2{{Clear forward}}
+ CF2 --> C29((29 3, 4, 5))
+
+ PO1 --> ST3[Start T3]
+
+ C29 --> TB0_1{{tb = 0}}
+
+ TB0_1 --> ST2[Start T2]
+ ST2 --> C32((32 4, 5))
+
+ ST3 --> S2((22 Seized prior to answer, pilot off))
+
+ S2 --> A3[Answer]
+ S2 --> PO2[Pilot on p = 1]
+ S2 --> T3_bar[ $\overline{T3}$ ]
+
+ A3 --> ST3_stop[Stop T3]
+
+ PO2 --> ST3_stop2[Stop T3]
+
+ T3_bar --> CF3{{Clear forward}}
+
+ ST3_stop --> S3((24 Pilot off, digital answered))
+
+ ST3_stop2 --> C21((21 2, 3))
+
+ CF3 --> C23((23 2, 3, 4, 5))
+
+ S3 --> CB[Clear back]
+ S3 --> PO3[Pilot on p = 1]
+
+ CB --> CF4[Clear forward]
+
+ PO3 --> A4{{Answer tb = 0}}
+
+ CF4 --> C23_2((23 2, 3, 4, 5))
+
+ A4 --> C31_2((31 4, 5))
+
+ PO3 --> C39((39 4, 5))
+
+ C23 --> S4((23 Pilot off, digital cleared))
+
+ S4 --> CF5[Clear forward]
+
+ CF5 --> CF[Circuit free]
+
+```
+
+Flowchart for System R2 line signalling conversion. The diagram shows state transitions between 'Seized prior to answer', 'Answer', 'Clear forward', 'Pilot off', 'Start T3', 'Seized prior to answer, pilot off', 'Pilot on', 'Stop T3', 'Pilot off, digital answered', 'Pilot off, digital cleared', 'Circuit free', 'Clear back', and 'Start T2'. It includes connector references (21, 22, 23, 29, 31, 32, 39) and signal states (tf=0, tb=1, p=1).
+
+CCITT-60891
+
+System R2 line signalling: conversion of incoming analogue version to outgoing digital version, group pilot supervision
+
+(Sheet 2 of 5)
+
+
+
+Connector reference
+reference
+
+1, 2, 3 21
+
+21 Seized prior to answer $tf = 0$ $tb = 1$ $p = 1$
+
+Answer
+
+Clear forward $tf = 1$
+
+Pilot off $p = 0$
+
+Answer $tb = 0$
+
+Clear forward
+
+Start T3
+
+31 4, 5
+
+29 3, 4, 5
+
+22 Seized prior to answer pilot off
+
+$tb = 0$
+
+Start T2
+
+Answer
+
+Pilot on $p = 1$
+
+$\overline{T3}$
+
+32 4, 5
+
+Stop T3
+
+Stop T3
+
+Clear forward
+
+24 Pilot off, digital answered
+
+21 2, 3
+
+23 Pilot off, digital cleared
+
+23 2, 3, 4, 5
+
+Clear back
+
+Pilot on $p = 1$
+
+Pilot on $p = 1$
+
+Circuit free
+
+Clear forward
+
+Answer $tb = 0$
+
+3
+
+39 Digital cleared
+
+23 2, 3, 4, 5
+
+31 4, 5
+
+Circuit free
+
+Clear forward $tf = 1$
+
+Pilot off $p = 0$
+
+29 3, 4, 5
+
+23 2, 3, 4, 5
+
+T1115760-88
+
+Flowchart for System R2 line signalling conversion. The process starts at connector 21 (Seized prior to answer) with tf=0, tb=1, p=1. It branches into Answer (tb=0), Clear forward (tf=1), and Pilot off (p=0). The Answer path leads to connector 31. The Clear forward path leads to Start T2 and then connector 32. The Pilot off path leads to Start T3 and then connector 22 (Seized prior to answer pilot off). From connector 22, it branches into Answer, Pilot on (p=1), and T3-bar. Answer leads to Stop T3 and connector 24 (Pilot off, digital answered). Pilot on leads to Stop T3 and connector 21. T3-bar leads to Clear forward and connector 23 (Pilot off, digital cleared). From connector 24, it branches into Clear back, Pilot on (p=1), and Pilot on (p=1). Clear back leads to Clear forward and connector 23. Pilot on (p=1) leads to Answer (tb=0) and connector 31. Pilot on (p=1) leads to connector 3. From connector 3, it leads to connector 39 (Digital cleared). From connector 39, it branches into Circuit free, Clear forward (tf=1), and Pilot off (p=0). Clear forward leads to connector 29. Pilot off leads to connector 23.
+
+**System R2 line signalling: conversion of incoming analogue version to outgoing digital version, supergroup pilot supervision**
+
+(Sheet 3 of 5)
+
+Connector
+reference
+**31**
+
+
+
+```
+
+stateDiagram-v2
+ direction TB
+
+ state "31 Answered" as Answered {
+ direction TB
+ tf = 0
+ tb = 0
+ p = 1
+ }
+
+ [*] --> Answered : 2, 3, 4, 5 (31)
+
+ Answered --> ClearForward1 : Clear forward tf = 1
+ Answered --> ClearBack1 : Clear back
+ Answered --> PilotOff1 : Pilot off p = 0
+
+ ClearForward1 --> ClearForward2 : Clear forward
+ ClearForward2 --> StartT2 : Start T2
+ StartT2 --> Clearing : (32) 1, 2, 3, 4, 5
+
+ ClearBack1 --> ClearBack2 : Clear back tb = 1
+ ClearBack2 --> ClearBack3 : Clear back (36)
+
+ ClearBack3 --> ClearForward3 : Clear forward tf = 1
+ ClearForward3 --> ClearForward4 : Clear forward
+ ClearForward4 --> Connector29 : (29) 3, 4, 5
+
+ ClearBack3 --> Answer1 : Answer
+ Answer1 --> Answer2 : Answer tb = 0
+ Answer2 --> Connector31 : (31) 4, 5
+
+ ClearBack3 --> PilotOff2 : Pilot off p = 0
+ PilotOff2 --> ClearForward5 : Clear forward
+ ClearForward5 --> Connector23 : (23) 2, 3, 4, 5
+
+ PilotOff1 --> AnsweredPilotOff : (37) Answered, pilot off
+ AnsweredPilotOff --> PilotOn1 : Pilot on p = 1
+ PilotOn1 --> Connector31 : (31) 4, 5
+
+ AnsweredPilotOff --> ClearBack4 : Clear back
+ ClearBack4 --> ClearForward6 : Clear forward
+ ClearForward6 --> PilotOff3 : (38) Pilot off, clear back
+
+ PilotOff3 --> PilotOn2 : Pilot on p = 1
+ PilotOn2 --> ClearBack5 : Clear back tb = 1
+ ClearBack5 --> DigitalCleared : (39) 2, 5
+
+ PilotOff3 --> CircuitFree1 : Circuit free
+
+ state "32 Clearing" as Clearing
+ Clearing --> T2Bar1 : $\bar{T}2$
+ T2Bar1 --> AwaitingCircuitFree : (33) 4, 5
+
+ Clearing --> PilotOff4 : Pilot off p = 0
+ PilotOff4 --> ClearingPilotOff : (35) Clearing, pilot off
+ ClearingPilotOff --> PilotOn3 : Pilot on p = 1
+ PilotOn3 --> Connector32 : (32) 4, 5
+ ClearingPilotOff --> T2Bar2 : $\bar{T}2$
+ ClearingPilotOff --> CircuitFree2 : Circuit free
+
+ Clearing --> CircuitFree3 : Circuit free
+ Clearing --> DigitalCleared
+
+ state "39 Digital cleared" as DigitalCleared
+ DigitalCleared --> CircuitFree4 : Circuit free
+ DigitalCleared --> ClearForward7 : Clear forward tf = 1
+ ClearForward7 --> Connector29 : (29) 3, 4, 5
+ DigitalCleared --> PilotOff5 : Pilot off p = 0
+ PilotOff5 --> Connector23 : (23) 2, 3, 4, 5
+
+ state "33 Awaiting circuit free" as AwaitingCircuitFree
+ AwaitingCircuitFree --> CircuitFree5 : Circuit free
+ CircuitFree5 --> ReleaseGuard : Release guard tb = 1
+ ReleaseGuard --> Idle : (00) Idle
+
+ AwaitingCircuitFree --> PilotOff6 : Pilot off p = 0
+ PilotOff6 --> PilotOffAwaiting : (34) Pilot off, awaiting circuit free
+ PilotOffAwaiting --> PilotOn4 : Pilot on p = 1
+ PilotOn4 --> Connector33 : (33) 4, 5
+ PilotOffAwaiting --> CircuitFree6 : Circuit free
+
+```
+
+Flowchart for System R2 line signalling conversion. The diagram shows state transitions between 'Answered', 'Clearing', 'Awaiting circuit free', 'Idle', and 'Digital cleared' states. Transitions are triggered by signals like 'Clear forward', 'Clear back', 'Pilot off', and 'Start T2', and result in actions like 'Start T2', 'Release guard', or reaching a 'Circuit free' state. Connector references (31, 32, 33, 37, 38, 39, 00) and signal codes (tf, tb, p) are used throughout the flow.
+
+31
+
+32
+31
+
+29, 31, 23
+
+39
+
+33
+
+29, 23
+
+32
+
+33
+
+**System R2 line signalling: conversion of incoming analogue version to outgoing digital version, group pilot supervision**
+
+(Sheet 4 of 5)
+
+CCITT-60901
+
+
+
+```
+
+graph TD
+ Start((31)) -- "2, 3, 4, 5" --> S31[31 Answered]
+ S31 --> Var1["tf = 0, tb = 0, p = 1"]
+
+ Var1 --> In1{Clear forward tf = 1}
+ In1 --> Out1>Clear forward]
+ Out1 --> S39[39 Start T2]
+
+ Var1 --> In2{Clear back}
+ In2 --> Out2>Clear back tb = 1]
+ Out2 --> S36[36 Clear back]
+ S36 --> Conn39((39)) -- "2, 5" --> Jump39
+
+ Var1 --> In3{Pilot off p = 0}
+ In3 --> S37[37 Answered, pilot off]
+ S37 --> In4{Pilot on p = 1}
+ In4 --> Out3>Pilot on p = 1]
+ Out3 --> Conn31_1((31)) -- "4, 5" --> Jump31
+
+ S37 --> In5{Clear back}
+ In5 --> S38[38 Pilot off, clear back]
+ S38 --> In6{Pilot on p = 1}
+ In6 --> Out4>Pilot on p = 1]
+ Out4 --> Out5>Clear back tb = 1]
+ Out5 --> Conn39_2((39)) -- "4, 5" --> Jump39_2
+
+ S39 --> Conn32((32)) -- "1, 2, 3, 4, 5" --> S32[32 Clearing]
+ S32 --> In7{Clear forward tf = 1}
+ In7 --> Out6>Clear forward]
+ Out6 --> Conn29((29)) -- "3, 4, 5" --> Jump29
+
+ S32 --> In8{Answer}
+ In8 --> Out7>Answer tb = 0]
+ Out7 --> Conn31_2((31)) -- "4, 5" --> Jump31_2
+
+ S32 --> In9{Pilot off p = 0}
+ In9 --> Out8>Clear forward]
+ Out8 --> Conn23((23)) -- "2, 3, 4, 5" --> Jump23
+
+ S32 --> Timer1[[T2]]
+ Timer1 --> Conn33((33)) -- "4, 5" --> S33[33 Awaiting circuit free]
+ S33 --> In10{Circuit free}
+ In10 --> Out9>Release guard tb = 0]
+ Out9 --> S00[00 Idle]
+
+ S32 --> In11{Pilot off p = 0}
+ In11 --> S35[35 Clearing, pilot off]
+ S35 --> In12{Pilot on p = 1}
+ In12 --> Conn32_2((32)) -- "4, 5" --> Jump32
+
+ S35 --> Out10>Circuit free]
+
+ S33 --> In13{Pilot off p = 0}
+ In13 --> S34[34 Pilot off, awaiting circuit free]
+ S34 --> In14{Pilot on p = 1}
+ In14 --> Conn33_2((33)) -- "4, 5" --> Jump33
+
+ S34 --> Out11>Circuit free]
+
+```
+
+The diagram details the logic for handling 'Answered', 'Clearing', 'Awaiting circuit free', and 'Idle' states in System R2 line signalling, specifically focusing on pilot supervision (p=0 for off, p=1 for on) and clear forward/back signals (tf, tb). It includes timers (T2) and transitions between states based on these inputs and outputs.
+
+SDL flowchart for System R2 line signalling conversion, sheet 5 of 5.
+
+**System R2 line signalling: conversion of incoming analogue version to outgoing digital version, supergroup pilot supervision**
+
+(Sheet 5 of 5)
+
+##### 2.2 Outgoing digital
+
+
+
+The diagram shows a central rectangular block representing a signaling system interface. On the left side, there are two input signals pointing into the block: 'seizure' and 'clear forward'. On the right side, there are two output signals pointing out of the block: 'af' and 'bf'. Below these, on the left side, there are four output signals pointing out of the block: 'answer', 'clear back', 'circuit free', and 'blocking'. On the right side, there are two input signals pointing into the block: 'ab' and 'bb'. The text 'CCIITT-85990' is located below the block on the right side.
+
+Diagram of a signaling system interface with input and output signals.
+
+List of timers:
+
+T6: Recommendation Q.422 (§ 3.2.4.1, Note 2 to Table 3)
+
+Connector reference:
+
+11
+
+21
+
+11
+
+
+
+The diagram illustrates the state transitions for System R2 line signalling. It starts at the **Idle** state (00) with parameters $af = 1, bf = 0, ab = 1, bb = 0$ . A **Seizure** transition leads to a state with $af = 0, bf = 0$ . From there, a **Start T6** transition leads to state **12 Seized prior seizure acknowledgement**. From state 12, four transitions are possible: **Seizure acknowledgement** ( $ab = 1, bb = 1$ ) leading to **Stop T6** and then connector **21**; **T6** leading to **Answer** and then state **13 No seizure acknowledgement**; **Fault** ( $ab = 0, (bb = 0, 1)$ ); and **Clear forward**. From state 13, three transitions are possible: **Fault** ( $ab = 0, (bb = 0, 1)$ ); **Seizure acknowledgement** ( $ab = 1, bb = 1$ ) leading to **Clear forward** ( $af = 1, bf = 0$ ) and then state **14 Seizure acknowledgement received after T6**; and **Clear forward**. From state 14, two transitions are possible: **Clear forward** leading to connector **11**; and **Fault** ( $bb = 0, (ab = 0, 1)$ ). A **Blocking\* conditions** transition from the initial Idle state leads to the **Blocking** state, which connects via connector **11** (references 1, 2, 3) to state **11 Blocked**. From state 11, an **Unblocking signal** ( $ab = 1, bb = 0$ ) leads to **Circuit free** and back to the **Idle** state (00).
+
+\* Blocking conditions are the following:
+
+| | |
+|----------|----------|
+| $ab = 1$ | $bb = 1$ |
+| $ab = 0$ | $bb = 0$ |
+| $ab = 0$ | $bb = 1$ |
+
+State transition diagram for System R2 line signalling. The diagram shows states (Idle, Blocked) and transitions (Seizure, Start T6, Seizure acknowledgement, Stop T6, Answer, Fault, Clear forward, Unblocking signal, Circuit free). It includes connector references 11, 21, 11 and a list of blocking conditions.
+
+CCITT- 60911
+
+System R2 line signalling: conversion of incoming analogue version to outgoing digital version
+(Sheet 1 of 3)
+
+Connector reference
+
+21
+29
+31, 11
+21
+31
+
+
+
+```
+
+graph TD
+ Start((21
+1, 2)) --> State21[21 Seized prior to answer
+af = 0 bf = 0
+ab = 1 bb = 1]
+ State21 --> Answer1[Answer
+ab = 0
+bb = 1]
+ Answer1 --> Connector31_3((31
+3))
+ State21 --> ClearForward1[Clear forward]
+ ClearForward1 --> Connector29_3((29
+3))
+ Connector29_3 --> ClearForward2[Clear forward
+af = 1
+bf = 0]
+ ClearForward2 --> Connector11_1((11
+1))
+ State21 --> Fault[Fault
+bb = 0
+(ab = 0, 1)]
+ Fault --> State23[23 Fault unanswered]
+ State23 --> Ab1Bb1[ab = 1
+bb = 1]
+ Ab1Bb1 --> Connector21_2((21
+2))
+ State23 --> Ab0Bb1[ab = 0
+bb = 1]
+ Ab0Bb1 --> Answer2[Answer]
+ Answer2 --> Connector31_3_2((31
+3))
+ State23 --> ClearForward3[Clear forward]
+
+```
+
+Flowchart for System R2 line signalling conversion. It starts with connector 21 (1, 2) leading to state 21 'Seized prior to answer' (af=0, bf=0, ab=1, bb=1). From here, it branches into 'Answer' (ab=0, bb=1) leading to connector 31 (3), 'Clear forward' leading to connector 11 (1), and 'Fault' (bb=0, ab=0, 1) leading to state 23 'Fault unanswered'. State 23 then branches into 'ab=1, bb=1' leading to connector 21 (2), 'ab=0, bb=1' leading to 'Answer' and connector 31 (3), and 'Clear forward'. A connector 29 (3) is shown between 'Clear forward' and 'Clear forward' (af=1, bf=0).
+
+CCITT-60920
+
+System R2 line signalling: conversion of incoming analogue version to outgoing digital version
+(Sheet 2 of 3)
+
+Connector reference
+
+31
+
+
+
+```
+
+graph TD
+ Start31((31)) --> State31[31 Answered]
+ State31 -- "af = 0, ab = 0; bf = 0, bb = 1" --> Branch1
+ Branch1 --> ClearForward1[Clear forward]
+ ClearForward1 -- "af = 1, bf = 0" --> Exit11((11))
+ Branch1 --> ClearBack1[Clear back]
+ ClearBack1 -- "ab = 1, bb = 1" --> State32_1[32 Clear back]
+ Branch1 --> Fault1[Fault bb = 0, ab = 0, 1]
+ Fault1 --> State33[33 Fault answered]
+
+ State33 --> Branch2
+ Branch2 --> ab0bb1_1[ab = 0, bb = 1] --> Exit31_1((31))
+ Branch2 --> ClearBack2[Clear back] --> Exit32_1((32))
+ Branch2 --> ClearForward2[Clear forward] --> Exit31_2((31))
+
+ State32_1 --> Branch3
+ Branch3 --> ClearForward3[Clear forward] --> Exit29((29))
+ Branch3 --> Answer1[Answer] -- "ab = 0, bb = 1" --> Exit31_3((31))
+ Branch3 --> Fault2[Fault bb = 0, ab = 0, 1] --> State34[34 Fault clear back]
+
+ State34 --> Branch4
+ Branch4 --> ab1bb1[ab = 1, bb = 1] --> Exit32_2((32))
+ Branch4 --> ab0bb1_2[ab = 0, bb = 1] --> Answer2[Answer] --> Exit31_4((31))
+ Branch4 --> ClearForward4[Clear forward] --> Exit31_5((31))
+
+```
+
+The diagram illustrates the state transitions for System R2 line signalling. It begins at state **31** (indicated by a circle with '31' and '2, 3' below it) and proceeds to state **31 Answered**. From **31 Answered**, three transitions are possible: **Clear forward** (leading to state **11** with connector reference 1), **Clear back** (leading to state **32** with connector reference 3), and **Fault bb = 0 (ab = 0, 1)** (leading to state **33 Fault answered**). From **33 Fault answered**, three transitions are possible: **Clear forward** (leading to state **31** with connector reference 3), **Clear back** (leading to state **32** with connector reference 3), and **ab = 0 bb = 1** (leading to state **31** with connector reference 3). From **32** (connector reference 32), three transitions are possible: **Clear forward** (leading to state **29** with connector reference 2), **Answer** (leading to state **31** with connector reference 3), and **Fault bb = 0 (ab = 0, 1)** (leading to state **34 Fault clear back**). From **34 Fault clear back**, three transitions are possible: **ab = 1 bb = 1** (leading to state **32** with connector reference 3), **ab = 0 bb = 1** (leading to state **31** with connector reference 3), and **Clear forward** (leading to state **31** with connector reference 3). Signal codes (af, bf, ab, bb) are provided for several states and transitions.
+
+State transition diagram for System R2 line signalling conversion. It shows transitions between states like 'Answered', 'Fault answered', 'Clear back', and 'Fault clear back' based on signal conditions like 'Clear forward', 'Clear back', and specific bit values for ab and bb.
+
+32
+
+11
+
+31
+
+32
+
+29
+
+31
+
+32
+
+31
+
+CCITT-60930
+
+System R2 line signalling: conversion of incoming analogue version to outgoing digital version
+(Sheet 3 of 3)
+
+#### 3 Conversion incoming digital version to outgoing analogue version
+
+##### 3.1 *Incoming digital*
+
+
+
+The diagram shows a central rectangular block representing a conversion unit. On the left side, there are two input lines labeled 'af' and 'bf' entering the block. On the right side, there are two output lines labeled 'seizure' and 'clear forward' exiting the block. Below these, on the right side, there are four input lines labeled 'answer', 'clear back', 'circuit free', and 'blocking' entering the block. On the left side, below the first two inputs, there are two output lines labeled 'ab' and 'bb' exiting the block. Below the block, the text 'CCITT-56000' is written.
+
+Diagram of a conversion block for incoming digital signals.
+
+List of timers:
+
+T3: 2 to 3 mn Recommendation Q.118 (§ 4.3.3)
+
+
+
+Connector reference
+
+```
+
+stateDiagram-v2
+ [*] --> Idle
+ Idle --> Seizure
+ Idle --> Blocking
+ Idle --> Failure
+ Seizure --> Seizure_ack[Seizure acknowledgement]
+ Seizure_ack --> Seizure_out[Seizure]
+ Seizure_out --> [*]
+ Blocking --> Blocking_ack[Blocking]
+ Blocking_ack --> Blocked
+ Blocked --> Circuit_free
+ Blocked --> Failure
+ Blocked --> Seizure
+ Circuit_free --> [*]
+ Failure --> Blocking_ack
+ Blocking_ack --> Idle_digital[Idle, digital failure]
+ Idle_digital --> End_of_failure
+ Idle_digital --> Blocking
+ End_of_failure --> Unblocking
+ Unblocking --> Idle
+ End_of_failure --> [*]
+ Seizure --> Circuit_free
+ Seizure --> Failure
+ Seizure --> Seizure
+ Circuit_free --> [*]
+ Failure --> Blocked_digital[Blocked, digital failure]
+ Blocked_digital --> End_of_failure
+ Blocked_digital --> Circuit_free
+ Blocked_digital --> Clear_forward
+ Blocked_digital --> Circuit_free
+ Blocked_digital --> Failure
+ Clear_forward --> [*]
+
+```
+
+Connector reference
+
+00 Idle $af = 1$ $bf = 0$
+ $ab = 1$ $bb = 0$
+
+Seizure $af = 0$ $bf = 0$
+
+Blocking
+
+Failure $bf = 1$
+
+Seizure acknowledgement $ab = 1$ $bb = 1$
+
+Blocking $ab = 1$ $bb = 1$
+
+Seizure
+
+Blocked
+
+Idle, digital failure
+
+End of failure $bf = 0$
+
+Circuit free
+
+Unblocking $ab = 1$ $bb = 0$
+
+Digital seized, analogue blocked
+
+Blocked, digital failure
+
+Clear forward $af = 1$ $bf = 0$
+
+12, 15
+
+21
+
+19
+
+13
+
+13
+
+19
+
+12, 15
+
+12
+
+CCITT-60940
+
+State transition diagram for System R2 line signalling conversion. The diagram shows states (Idle, Blocked, Seizure, etc.) and transitions (Seizure, Blocking, Failure, etc.) with associated flags (af, bf, ab, bb). Connector references are listed on the left margin.
+
+System R2 line signalling: conversion of incoming digital version to outgoing analogue version
+(Sheet 1 of 3)
+
+
+
+Connector
+reference
+
+21
+
+22, 23
+
+19, 34
+
+21
+
+34
+
+31, 22
+
+19
+
+```
+
+graph TD
+ 21_1((21)) -- "1, 2" --> S21[21 Seized unanswered
+af = 0, ab = 1, bf = 0, bb = 1]
+ S21 --> Answer1[Answer]
+ S21 --> ClearForward1[Clear forward
+af = 1, bf = 0]
+ S21 --> Failure1[Failure
+bf = 1]
+ Answer1 --> Answer2[Answer
+ab = 0, bb = 1]
+ ClearForward1 --> ClearForward2[Clear forward]
+ Failure1 --> StartT3[Start T3]
+ Answer2 --> 22_1((22))
+ ClearForward2 --> 23_1((23))
+ StartT3 --> 24_1((24))
+ 22_1 -- "2, 3" --> S22[22 Answered]
+ 23_1 -- "3" --> S23[23 Clearing unanswered]
+ 24_1 --> S24[24 Failure prior to answer]
+ S22 --> ClearForward3[Clear forward
+af = 1, bf = 0]
+ S23 --> CircuitFree1[Circuit free]
+ CircuitFree1 --> 19_1((19)) -- "1" --> End1
+ S24 --> EndFailure1[End of failure
+bf = 0]
+ S24 --> T3_bar[T3 bar]
+ S24 --> Answer3[Answer]
+ EndFailure1 --> StopT3_1[Stop T3]
+ StopT3_1 --> 21_2((21)) -- "2" --> End2
+ T3_bar --> 34_1((34)) -- "3" --> End3
+ Answer3 --> StopT3_2[Stop T3]
+ StopT3_2 --> 26_1[26 Answered on failure]
+ 26_1 --> ClearBack1[Clear back]
+ ClearBack1 --> 34_2((34)) -- "3" --> End4
+
+ %% Lower section of the diagram
+ StartLower[ ] --> ClearForward4[Clear forward
+af = 1, bf = 0]
+ StartLower --> ClearBack2[Clear back]
+ StartLower --> Failure2[Failure
+bf = 1]
+ StartLower --> EndFailure2[End of failure
+bf = 0]
+ StartLower --> ClearBack3[Clear back]
+
+ ClearForward4 --> ClearForward5[Clear forward]
+ ClearForward5 --> 25_1[25 Clearing answered]
+ 25_1 --> CircuitFree2[Circuit free]
+ CircuitFree2 --> 19_2((19)) -- "1" --> End5
+
+ ClearBack2 --> ClearBack4[Clear back
+ab = 1, bb = 1]
+ ClearBack4 --> 31_1((31)) -- "3" --> End6
+
+ Failure2 --> 34_3((34)) -- "3" --> End7
+
+ EndFailure2 --> Answer4[Answer
+ab = 0, bb = 1]
+ Answer4 --> 22_2((22)) -- "2" --> End8
+
+```
+
+Flowchart for System R2 line signalling conversion. It starts at connector 21 in state 'Seized unanswered' (af=0, ab=1, bf=0, bb=1). Transitions include 'Answer' to connector 22 ('Answered'), 'Clear forward' to connector 23 ('Clearing unanswered'), and 'Failure' to connector 24 ('Failure prior to answer'). From 22, 'Clear forward' leads to connector 19 ('Circuit free'). From 23, 'Circuit free' leads to connector 19. From 24, 'End of failure' leads to connector 21, 'T3' leads to connector 34, and 'Answer' leads to connector 26 ('Answered on failure'). From 26, 'Clear back' leads to connector 34. From 21 (after 24), 'Clear forward' leads to connector 34 ('Clearing answered'), 'Clear back' leads to connector 31, and 'Failure' leads to connector 34. From 34 ('Clearing answered'), 'Circuit free' leads to connector 19. From 31, 'Clear back' leads to connector 22. From 22 (after 34), 'End of failure' leads to connector 21.
+
+CCITT-60950
+
+System R2 line signalling: conversion of incoming digital version to outgoing analogue version
+(Sheet 2 of 3)
+
+
+
+Connector reference
+
+31
+
+34
+
+23,22
+
+23
+
+```
+
+stateDiagram-v2
+ [*] --> 31: Clear back (af=0, bf=0, ab=1, bb=1)
+ 31 --> Clear_forward_1: Clear forward (af=1, bf=0)
+ 31 --> Failure_1: Failure (bf=1)
+ 31 --> Answer_1: Answer
+ Clear_forward_1 --> 23: Clear forward
+ Failure_1 --> 34: Clear forward
+ Answer_1 --> 22: Answer (ab=0, bb=1)
+ 34 --> 32: Digital failure analogue cleared
+ 32 --> End_of_failure: End of failure (bf=0)
+ 32 --> Circuit_free_1: Circuit free
+ End_of_failure --> 33: Cleared after digital failure
+ 33 --> Clear_forward_2: Clear forward (af=1, bf=0)
+ 33 --> Failure_2: Failure (bf=1)
+ 33 --> Circuit_free_2: Circuit free
+ Clear_forward_2 --> 23: Clear forward
+
+```
+
+CCITT-60960
+
+State transition diagram for System R2 line signalling. The diagram shows various states and transitions between them, with connector references 31, 34, 23, 22, and 23 on the left. States include 'Clear back' (31), 'Clear forward' (af=1, bf=0), 'Failure' (bf=1), 'Answer' (ab=0, bb=1), 'Digital failure analogue cleared' (32), 'End of failure' (bf=0), 'Circuit free', and 'Cleared after digital failure' (33). Transitions are labeled with connector references and signal parameters like af, bf, ab, and bb.
+
+System R2 line signalling: conversion of incoming digital version to outgoing analogue version
+
+(Sheet 3 of 3)
+
+
+
+The diagram shows a central rectangular block representing a signalling system interface. On the left side, there are two input arrows pointing into the block labeled 'seizure' and 'clear forward'. On the right side, there is one output arrow pointing out of the block labeled 'tf'. On the left side, there are four output arrows pointing out of the block labeled 'answer', 'clear back', 'circuit free', and 'blocking'. On the right side, there are two input arrows pointing into the block labeled 'tb' and 'p'. Below the block, the text 'CCITT-96010' is written.
+
+Diagram of a signalling system interface with inputs and outputs.
+
+List of timers:
+
+T1: Recommendation Q.412 (§ 2.2.2.7)
+
+T5: 100 ms Recommendation Q.412 (§ 2.2.2.1)
+
+Automatic restoration of an abnormally blocked circuit Recommendation Q.490 (§ 6.6)
+
+n: number of attempts made
+
+T4: 30 s to 2 mn
+
+T7: 2 to 3 s
+
+
+
+Connector reference
+
+12
+
+
+
+
+
+19
+19
+
+
+
+
+
+12
+
+
+
+
+21
+
+```
+
+stateDiagram-v2
+ state "00 Idle\ntf=1, tb=1, p=1" as Idle
+ state "Seizure" as Seizure
+ state "Seizure\ntf=0" as Seizure0
+ state "Start T5" as StartT5
+ state "11 Seized" as Seized
+ state "Blocking\ntb=0" as Blocking1
+ state "Blocking" as Blocking2
+ state "12 Blocked" as Blocked
+ state "Pilot off\np=0" as PilotOff1
+ state "Blocking" as Blocking3
+ state "14 Idle, pilot off" as IdlePilotOff
+ state "Unblocking\ntb=1" as Unblocking
+ state "Circuit free" as CircuitFree
+ state "Pilot off\np=0" as PilotOff2
+ state "13 Blocked, pilot off" as BlockedPilotOff
+ state "Pilot on\np=1" as PilotOn1
+ state "Pilot on\np=1" as PilotOn2
+ state "T5" as T5Bar
+ state "Clear forward" as ClearForward
+ state "Blocking\ntb=0" as Blocking4
+ state "Pilot off\np=0" as PilotOff3
+
+ [*] --> Idle
+ Idle --> Seizure
+ Idle --> Blocking1
+ Idle --> PilotOff1
+ Seizure --> Seizure0
+ Seizure0 --> StartT5
+ StartT5 --> Seized
+ Seized --> T5Bar
+ Blocking1 --> Blocking2
+ Blocking2 --> Blocked
+ PilotOff1 --> Blocking3
+ Blocking3 --> IdlePilotOff
+ Blocked --> Unblocking
+ Blocked --> PilotOff2
+ Blocked --> PilotOn1
+ Unblocking --> CircuitFree
+ CircuitFree --> Idle
+ PilotOff2 --> BlockedPilotOff
+ BlockedPilotOff --> PilotOn2
+ PilotOn2 --> Blocked
+ T5Bar --> ClearForward
+ T5Bar --> Blocking4
+ T5Bar --> PilotOff3
+ T5Bar --> 21
+
+```
+
+CCITT-60971
+
+Flowchart for System R2 line signalling conversion. It starts at 'Idle' (00) with variables tf=1, tb=1, p=1. Transitions lead to 'Seizure', 'Blocking', and 'Pilot off'. The 'Seizure' path goes through 'Seizure tf=0', 'Start T5', to 'Seized' (11). The 'Blocking' path leads to 'Blocked' (12). The 'Pilot off' path leads to 'Idle, pilot off' (14). From 'Blocked', paths lead to 'Unblocking', 'Pilot off', and 'Pilot on'. 'Unblocking' leads to 'Circuit free' and back to 'Idle' (00). The bottom section shows a transition from 'T5' (overline) to 'Clear forward', 'Blocking', and 'Pilot off', ending at connector 21.
+
+**System R2 line signalling: conversion of incoming digital version to outgoing analogue version**
+(Sheet 1 of 5)
+
+
+
+Connector reference
+
+```
+
+stateDiagram-v2
+ [*] --> Seized_unanswered : 21 (1, 2)
+ Seized_unanswered : tf = 0, tb = 1, p = 1
+ Seized_unanswered --> Answer : tb = 0
+ Seized_unanswered --> Clear_forward_1 : Clear forward
+ Seized_unanswered --> Pilot_off_1 : p = 0
+ Answer --> Answer_state : Answer
+ Answer_state --> 31 : 3
+ Clear_forward_1 --> Clear_forward_tf1 : Clear forward tf = 1
+ Clear_forward_tf1 --> Start_T1 : Start T1
+ Start_T1 --> 22 : 3
+ 22 --> Clearing_unanswered : Clearing unanswered
+ Clearing_unanswered --> tb_0 : tb = 0
+ Clearing_unanswered --> T1 : T1
+ Clearing_unanswered --> Pilot_off_2 : Pilot off p = 0
+ Pilot_off_2 --> Stop_T1 : Stop T1
+ Stop_T1 --> 25 : 2
+ Pilot_off_1 --> Unanswered_pilot_off : 24 Unanswered, pilot off
+ Unanswered_pilot_off --> Pilot_on : Pilot on p = 1
+ Pilot_on --> 21 : 2
+ Unanswered_pilot_off --> Clear_forward_2 : Clear forward
+ Clear_forward_2 --> Clear_forward_tf2 : Clear forward tf = 1
+ Clear_forward_tf2 --> 25 : 2, 3
+ 25 --> Cleared_unanswered_pilot_off : 25 Cleared unanswered, pilot off
+ Cleared_unanswered_pilot_off --> Pilot_on_2 : Pilot on p = 1
+ Pilot_on_2 --> 19 : 1
+
+```
+
+21
+
+29
+
+31
+
+22
+
+21
+
+25
+
+32, 41
+
+25
+
+19
+
+CCITT-60981
+
+State transition diagram for System R2 line signalling. The diagram shows transitions between states: 'Seized unanswered' (tf=0, tb=1, p=1), 'Answer' (tb=0), 'Clear forward' (tf=1), 'Pilot off' (p=0), 'Unanswered, pilot off' (24), 'Start T1', 'Pilot on' (p=1), 'Clearing unanswered' (22), 'tb=0', 'T1', 'Stop T1', and 'Cleared unanswered, pilot off' (25). Transitions are labeled with connector references (21, 29, 31, 22, 21, 25, 32, 41, 25, 19) and signal types (1, 2, 3, 4).
+
+System R2 line signalling: conversion of incoming digital version to outgoing analogue version
+(Sheet 2 of 5)
+
+Connector reference
+
+
+
+```
+
+graph TD
+ Start((31 2,3)) --> Answered[31 Answered tf=0 tb=0 p=1]
+ Answered --> CF1[Clear forward]
+ Answered --> CB1[Clear back tb=1]
+ Answered --> PO1[Pilot off p=0]
+ CF1 --> CF1_TF[Clear forward tf=1]
+ CF1_TF --> ST1[Start T1]
+ ST1 --> ClearingAnswered[32 Clearing answered 2,5]
+ CB1 --> CB1_TF[Clear back]
+ CB1_TF --> CB2[34 Clear back 3]
+ PO1 --> AnsweredPO[36 Answered, pilot off]
+ AnsweredPO --> CF2[Clear forward]
+ AnsweredPO --> PO2[Pilot on p=1]
+ PO2 --> End31((31 3))
+ CF2 --> CF2_TF[Clear forward tf=1]
+ CF2_TF --> ClearedPO[37 Cleared, pilot off 3]
+ ClearedPO --> PO3[Pilot on p=1]
+ PO3 --> End12((12 1))
+ CB2 --> CF3[Clear forward]
+ CB2 --> AnswerTB[Answer tb=0]
+ CB2 --> PO3_1[Pilot off p=0]
+ CF3 --> End29((29 2))
+ AnswerTB --> Answer[Answer]
+ Answer --> End31_2((31 3))
+ PO3_1 --> CB3[35 Clear back, pilot off]
+ CB3 --> PO4[Pilot on p=1]
+ CB3 --> CF4[Clear forward]
+ PO4 --> End34((34 3))
+ CF4 --> CF4_TF[Clear forward tf=1]
+ CF4_TF --> End25((25 2))
+ ClearingAnswered --> T1[ $\overline{T1}$ ]
+ ClearingAnswered --> TB1[tb=1]
+ ClearingAnswered --> PO5[Pilot off p=0]
+ T1 --> End12_1((12 1))
+ TB1 --> End22((22 2))
+ PO5 --> StopT1[Stop T1]
+ StopT1 --> End37((37 3))
+
+```
+
+Flowchart for System R2 line signalling conversion. It starts at connector 31 (2,3) in state 'Answered' (tf=0, tb=0, p=1). Transitions include 'Clear forward' (tf=1), 'Clear back' (tb=1), and 'Pilot off' (p=0). 'Clear forward' leads to 'Start T1' then connector 32 (2,5) in state 'Clearing answered'. 'Clear back' leads to connector 34 (3) in state 'Clear back'. 'Pilot off' leads to connector 36 in state 'Answered, pilot off', which then branches to 'Clear forward' (tf=1) leading to connector 37 (3) in state 'Cleared, pilot off', and 'Pilot on' (p=1) leading to connector 31 (3). Further transitions include 'Answer' (tb=0), 'Pilot on' (p=1), and 'Stop T1' leading to connector 37 (3). Connector references on the left include 31, 34, 32, 31, 37, 29, 31, 12, 34, 25, 12,22, and 37.
+
+System R2 line signalling: conversion of incoming digital version to outgoing analogue version
+(Sheet 3 of 5)
+
+CCITT-60991
+
+
+
+Connector reference
+
+```
+
+graph TD
+ 41((41
+2, 5)) --> n["n = n + 1"]
+ n --> n1{"n = 1"}
+ n1 -- No --> 42((42
+5))
+ 42 --> StartT4{{Start T4}}
+ StartT4 --> 51_5((51
+5))
+ n1 -- Yes --> StartT7{{Start T7}}
+ StartT7 --> 43_51[43
+Awaiting T7 elapse]
+ 43_51 --> T7[/T7/]
+ 43_51 --> tb0[/tb = 0/]
+ 43_51 --> PilotOff[/Pilot off
+p = 0/]
+ T7 --> Seize[Seize
+tf = 0]
+ Seize --> StartT5{{Start T5}}
+ StartT5 --> 52_5((52
+5))
+ tb0 --> StopT7_55[Stop T7]
+ StopT7_55 --> 55_5((55
+5))
+ PilotOff --> StopT7_56[Stop T7]
+ StopT7_56 --> 56_5((56
+5))
+
+```
+
+41
+
+42
+
+51
+
+55,56
+
+52
+
+CCITT-70001
+
+Flowchart for System R2 line signalling conversion. The process starts at connector 41 (2, 5), increments n to n+1, and checks if n=1. If No, it goes to connector 42 (5) and starts T4, leading to connector 51 (5). If Yes, it starts T7, leading to connector 43 (Awaiting T7 elapse). From 43, three paths emerge: T7 leads to Seize (tf=0) then Start T5 to connector 52 (5); tb=0 leads to Stop T7 then connector 55 (5); Pilot off (p=0) leads to Stop T7 then connector 56 (5). Connector references 41, 42, 51, 52, 55, 56 are on the left. Connector 43 is at 51. Connector 51 is at 51. Connector 52 is at 52. Connector 55 is at 55,56. Connector 56 is at 55,56.
+
+System R2 line signalling: conversion of incoming digital version to outgoing analogue version.
+Automatic restoration of analogue link
+(Sheet 4 of 5)
+
+
+
+Connector reference
+
+51
+
+55,56
+
+52
+
+42
+
+55
+
+32,41
+
+56
+
+```
+
+graph TD
+ 51((51)) --> 51a[51 Automatic restoration T4
+tf = 1 tb = 1 p = 1]
+ 51a --> T4[/T4/]
+ T4 --> Seizure[Seizure
+tf = 0]
+ Seizure --> StartT5[Start T5]
+ StartT5 --> 52((52))
+ 52 --> 52a[52 Seized for automatic restoration]
+ 52a --> T5[/T5/]
+ T5 --> ClearForward[Clear forward
+tf = 1]
+ ClearForward --> StartT1[Start T1]
+ StartT1 --> 53((53))
+ 53 --> 53a[53 Awaiting
+tb = 0]
+ 53a --> tb0_1[/tb = 0/]
+ 53a --> T1[/T1/]
+ 53a --> PilotOff_1[/Pilot off
+p = 0/]
+ tb0_1 --> 32((32))
+ T1 --> 41((41))
+ PilotOff_1 --> StopT1[Stop T1]
+ StopT1 --> 56((56))
+ 51a --> tb0_2[/tb = 0/]
+ tb0_2 --> StopT4[Stop T4]
+ StopT4 --> 55((55))
+ 55 --> 55a[55 Awaiting
+tb = 1]
+ 55a --> tb1[/tb = 1/]
+ 55a --> PilotOff_2[/Pilot off
+p = 0/]
+ 55a --> 57((57))
+ 57 --> 57a[57 Awaiting, pilot on
+tb = 0]
+ 57a --> PilotOn_1[/Pilot on
+p = 1/]
+ PilotOn_1 --> 55((55))
+ 51a --> PilotOff_3[/Pilot off
+p = 0/]
+ PilotOff_3 --> StopT4_2[Stop T4]
+ StopT4_2 --> 56((56))
+ 56 --> 56a[56 Awaiting, pilot on]
+ 56a --> PilotOn_2[/Pilot on
+p = 1/]
+ PilotOn_2 --> 42((42))
+
+```
+
+Flowchart for System R2 line signalling: conversion of incoming digital version to outgoing analogue version. Automatic restoration of the analogue link. The flowchart starts at connector 51 and branches based on conditions like tf=1, tb=1, p=1, and various waiting states (Awaiting tb=1, Awaiting tb=0, Awaiting, pilot on). It ends at connectors 32, 41, 42, 55, and 56.
+
+CCITT-T-700II
+
+System R2 line signalling: conversion of incoming digital version to outgoing analogue version.
+Automatic restoration of the analogue link
+(Sheet 5 of 5)
+
+# SECTION 4
+
+## INTERREGISTER SIGNALLING
+
+###### Recommendation Q.440
+
+### 4.1 GENERAL
+
+Interregister signals are of the multifrequency type using a 2-out-of-6 in-band code in both directions. The multifrequency combinations are sent and received by multifrequency signalling equipment which is assumed to be associated with the registers used to control the switching equipment at both ends of the inter-exchange link.
+
+#### 4.1.1 *End-to-end signalling method*
+
+In System R2 interregister signalling is generally performed end-to-end by a compelled procedure between the outgoing register and the incoming registers which come into action one after another. Signalling takes place over one or more links in tandem without signal regeneration in intermediate exchanges. With this signalling method only the address information needed for routing the call through an intermediate exchange is transferred from the outgoing register to the incoming registers. In an intermediate exchange the speech path is immediately through-connected and the incoming register released, then the outgoing register can exchange information directly with the incoming register of the next exchange (see Figure 11/Q.440). If any intermediate exchange has to carry out charging operations, additional address information can be transferred from the outgoing register to the incoming register of that exchange as required.
+
+
+
+The diagram illustrates a multi-link connection between two 'Not System R2' nodes. The connection consists of three 'end-to-end signalling sections' separated by intermediate exchanges. At the far left, an 'Outgoing R2 register' (represented by a hatched box) is connected to the first section. This is followed by a series of intermediate exchanges, each containing an 'incoming R2 register in a transit exchange' (represented by a 'T' in a box). The first section ends at the second intermediate exchange, the second at the third, and the third at the far right 'Incoming R2 register' (hatched box). Dashed lines with arrows above the links indicate the flow of signalling information through these sections. The diagram is labeled 'CCITT-49240' at the bottom right.
+
+I = outgoing international R2 register
+T = incoming R2 register in a transit exchange
+
+Diagram of an international three-section multi-link connection showing end-to-end signalling sections between R2 registers.
+
+FIGURE 11/Q.440
+An international three-section multi-link connection
+
+In circumstances where transmission conditions do not comply with the requirements specified for System R2 (see Recommendation Q.457) or where System R2 is used in a satellite link, and thus the exchange of the interregister signals over the complete System R2 connection is not permitted, the overall multi-link connection is divided into end-to-end signalling sections. When the number of multifrequency combinations available is not the same on all parts of the connection, the division should be made at an exchange between links having different numbers of multifrequency combinations to improve the transfer of information.
+
+The outgoing R2 register is situated at the outgoing end of a signalling section on which System R2 interregister signalling according to the present specifications is used. It controls the call set-up over the whole signalling section. It sends forward interregister signals and receives backward interregister signals.
+
+The outgoing R2 register receives information via the preceding links of the connection in a form used by the signalling system applied over the last of these links; this system may be System R2, a decadic pulse system, or any other system. The preceding link may also be a subscriber's line. When an R2 register in a transit exchange is working according to this definition, it is also called an *outgoing R2 register*.
+
+Special cases of the outgoing R2 register are the outgoing international R2 register (see § 4.1.2) and the outgoing R2 register at the incoming end of a satellite link.
+
+The incoming R2 register is situated at the incoming end of a link on which System R2 multifrequency interregister signalling according to the present specification is used. It receives forward interregister signals via the preceding link(s) and sends backward interregister signals. The information received is used completely or in part for the control of selection stages and may be sent in its entirety or in part to the succeeding equipment, in which case the signalling used for retransmission is never System R2. Interworking then takes place between System R2 and the other system. Thus every register not situated at the outgoing end of a System R2 signalling section is called an *incoming R2 register* independently of the exchange type.
+
+The term *incoming R2 register* may be applied also to devices controlling one or more selection stages, for example *markers* etc. It should be noted that in such equipment no provision is made for further transfer of the information received.
+
+#### 4.1.2 *International end-to-end working*
+
+The inclusion of a special *outgoing international R2 register* as shown in Figure 11/Q.440 is dictated by a number of considerations. An outgoing international R2 register is an outgoing R2 register which controls the call set-up on a signalling section which comprises at least one international link and possibly national links in tandem.
+
+Even when System R2 is used in the national network of the originating country an outgoing international R2 register must always be provided in the country of origin to divide the connection into two signalling sections for the following reasons:
+
+- to prevent the maximum number of links in a signalling section over which System R2 can function from being exceeded on international calls;
+- to permit the use of fewer signalling frequencies in the country of origin (e.g. 5 forward and 5 or 4 backward signalling frequencies);
+- to enable non-standardized meanings to be allocated to the spare national multifrequency combinations for use solely in the country of origin;
+- to provide criteria for distinction, at the incoming end, between national and international calls;
+- to have the facilities for routing and charging of international calls concentrated in one place if it is more economical than to equip every normal outgoing R2 register to perform these functions.
+
+In general the outgoing international R2 register is situated at the outgoing international exchange. However, it may be situated in a national exchange preceding the international exchange provided that the transmission requirements specified are fulfilled.
+
+End-to-end signalling from the outgoing international R2 register can be extended beyond the incoming international exchange even if a reduced number of signalling frequencies is used. However, such international/national end-to-end signalling requires:
+
+- that the transmission conditions in the national destination network comply with the System R2 specifications, and
+- that the routing principles employed in the national destination network are compatible with the System R2 signalling procedures for end-to-end transmission of address digits from the outgoing international R2 register to an incoming R2 register in a national exchange.
+
+#### 4.1.3 *Register requirements*
+
+Apart from signalling procedures specified in Section 5 the following characteristics of R2 registers are specified.
+
+##### 4.1.3.1 *Outgoing R2 registers*
+
+The multifrequency signalling equipment associated with outgoing R2 registers in national exchanges may be of the 2-wire or 4-wire type (see Recommendation Q.451).
+
+The multifrequency signalling equipment associated with outgoing international R2 registers must be of the 4-wire type. This is dictated by transmission constraints (see Recommendation Q.452).
+
+The outgoing R2 register controlling a given multi-link signalling section must be able to recognize at least all the backward signals used on that section.
+
+The outgoing international R2 register must be able to send all 15 forward multifrequency combinations with the meanings specified for international working. It must be able to receive all 15 backward multifrequency combinations and act upon the received information in the specified manner. In the case when System R2 is used on the preceding link the calling party's category signals have to be translated by the outgoing international R2 register as specified (see Recommendation Q.480).
+
+The outgoing R2 register must start call set-up as soon as it has received the minimum requisite information. Therefore signal transfer starts before the complete address information is received, i.e. before the caller finishes dialling. This *overlapping interregister signalling* particularly applies at an outgoing R2 register where the complete address information from a subscriber or operator is stored (e.g. local registers). This is in contrast to *en bloc register signalling* i.e. the transmission of all the address information as a whole in one sequence starting only after the complete reception of the address information.
+
+##### 4.1.3.2 *Incoming R2 registers*
+
+The multifrequency signalling equipment associated with incoming R2 registers may be of the 2-wire or 4-wire type (see Recommendation Q.451).
+
+The multifrequency signalling equipment associated with the incoming R2 register in an international exchange must be of the 4-wire type and equipped to send and receive all 15 multifrequency combinations.
+
+Every incoming R2 register in a multi-link signalling section must be able to recognize at least the forward signals used on that section and directed to that register.
+
+#### 4.1.4 *System R2 compelled signalling method*
+
+The compelled signalling operates as follows (see Figure 12/Q.440):
+
+- on seizure of a link, the outgoing R2 register automatically starts sending the first forward interregister signal,
+- as soon as the incoming R2 register recognizes this signal, it starts sending a backward interregister signal which has its own meaning and at the same time serves as an acknowledgement signal;
+- as soon as the outgoing R2 register recognizes the acknowledging signal, it stops sending the forward interregister signal;
+- as soon as the incoming R2 register recognizes the cessation of the forward interregister signal, it stops sending the backward interregister signal;
+- as soon as the outgoing R2 register recognizes the cessation of the acknowledging backward interregister signal it may, if necessary, start sending the appropriate next forward interregister signal.
+
+When the duration of the forward and backward signals is not controlled by the compelling mechanism described above, it is either limited by the time-out delay for release of the register or determined by the nature of the pulse imposed on them (see Recommendation Q.442).
+
+Figure 12/Q.440 shows a basic compelled signalling cycle.
+
+Figure 18/Q.457 shows in detail the build-up and time sequence of a compelled signalling cycle, including the operating and release times of multifrequency signalling equipment and other internal operating times of exchange equipment.
+
+Besides being a functional part of the compelled procedure, the acknowledging backward signals serve to convey special information concerning the required forward signals, to indicate certain conditions encountered during call set-up or to announce switchover to changed meanings of subsequent backward signals. Changeover to secondary meanings allows information concerning the state of the called subscriber's line to be transferred (see Recommendation Q.441, § 4.2.4). Therefore a choice of acknowledging backward signals is provided.
+
+
+
+Diagram of a compelled signalling cycle between an Outgoing register (Sending) and an Incoming register (Receiving). The diagram shows a sequence of signals over time. 1. A 'Forward signal' is sent from the Outgoing register to the Incoming register. 2. An 'Acknowledging backward signal' is sent from the Incoming register back to the Outgoing register. 3. A 'Next forward signal' is sent from the Outgoing register to the Incoming register. 4. Another 'Acknowledging backward signal' is sent from the Incoming register back to the Outgoing register. A vertical dashed line separates the 'Sending' (Outgoing register) and 'Receiving' (Incoming register) sides. A vertical arrow labeled 'Time' points downwards, indicating the sequence of events. The diagram is labeled 'CCITT-49250'.
+
+FIGURE 12/Q.440
+Compelled signalling cycle
+
+##### Recommendation Q.441
+
+### 4.2 SIGNALLING CODE
+
+#### 4.2.1 Multifrequency combinations
+
+Each interregister signal consists of the simultaneous sending of 2 out of a range of 6, 5 or 4 in-band frequencies (multifrequency combination). The band of the interregister signalling frequencies does not overlap with the frequency band generally used for line-signalling.
+
+This *2-out-of-n* code allows erroneous signals consisting of less or more than two frequencies to be detected and identified as faulty.
+
+To make the system suitable for application on 2-wire links, two different sets of 6 frequencies are defined for the composition of the forward and the backward signals.
+
+Table 5/Q.441 shows all multifrequency combinations which can be derived from the maximum of 6 signalling frequencies per direction provided by the system. For reference purposes each multifrequency combination of a given direction is identified by a serial number. The numerical value of this serial number can be calculated by adding the respective index and weight allocated to the two frequencies making up the combination.
+
+The number of multifrequency combinations depends upon the number of signalling frequencies used. When the maximum of 6 signalling frequencies are used, 15 multifrequency combinations are available.
+
+System R2 is designed for operation on international links with 15 multifrequency combinations in each direction. However, it can be used in national networks with a reduced number of signalling frequencies and still permit international/national end-to-end working of System R2 signalling in the case of incoming international traffic (see Figure 13/Q.441).
+
+The reduction naturally cuts the number of multifrequency combinations available but has the economic advantage of effecting savings in equipment. The resulting reduction in facilities is of less importance in automatic than semi-automatic service.
+
+TABLE 5/Q.441
+
+##### **Multifrequency combinations**
+
+| Combinations | | Frequencies (Hz) | | | | | | |
+|--------------|-------------------------------|------------------------------------------------|-------|-------|-------|-------|-------|-------|
+| No. | Numeral value
=
$x + y$ | Forward direction (signals of Groups I and II) | 1380 | 1500 | 1620 | 1740 | 1860 | 1980 |
+| | | Backward direction (signals of Groups A and B) | 1140 | 1020 | 900 | 780 | 660 | 540 |
+| | | Index ( $x$ ) | $f_0$ | $f_1$ | $f_2$ | $f_3$ | $f_4$ | $f_5$ |
+| | | Weight ( $y$ ) | 0 | 1 | 2 | 4 | 7 | 11 |
+| 1 | $0 + 1$ | | $x$ | $y$ | | | | |
+| 2 | $0 + 2$ | | $x$ | | $y$ | | | |
+| 3 | $1 + 2$ | | | $x$ | $y$ | | | |
+| 4 | $0 + 4$ | | $x$ | | | $y$ | | |
+| 5 | $1 + 4$ | | | $x$ | | $y$ | | |
+| 6 | $2 + 4$ | | | | $x$ | $y$ | | |
+| 7 | $0 + 7$ | | $x$ | | | | $y$ | |
+| 8 | $1 + 7$ | | | $x$ | | | $y$ | |
+| 9 | $2 + 7$ | | | | $x$ | | $y$ | |
+| 10 | $3 + 7$ | | | | | $x$ | $y$ | |
+| 11 | $0 + 11$ | | $x$ | | | | | $y$ |
+| 12 | $1 + 11$ | | | $x$ | | | | $y$ |
+| 13 | $2 + 11$ | | | | $x$ | | | $y$ |
+| 14 | $3 + 11$ | | | | | $x$ | | $y$ |
+| 15 | $4 + 11$ | | | | | | $x$ | $y$ |
+
+The following versions might be considered:
+
+- a) 6 forward frequencies (15 multifrequency combinations) and 5 backward frequencies (10 multifrequency combinations);
+- b) 6 forward frequencies (15 multifrequency combinations) and 4 backward frequencies (6 multifrequency combinations);
+- c) 5 forward frequencies (10 multifrequency combinations) and 5 backward frequencies (10 multifrequency combinations);
+- d) 5 forward frequencies (10 multifrequency combinations) and 4 backward frequencies (6 multifrequency combinations).
+
+In the forward direction the highest signalling frequency may be omitted (i.e. multifrequency combinations 1 to 10 remain). In the backward direction either the lowest or both the lowest and next lowest signalling frequency may be omitted (i.e. multifrequency combinations 1 to 10 or 1 to 6, respectively, remain).
+
+
+
+The diagram illustrates an international two-section multi-link connection. It consists of two main sections: the '1st section with end-to-end signalling' and the '2nd section with end-to-end signalling'. The connection starts with an 'Outgoing R2 register in a local or trunk exchange' (represented by a shaded box) and ends with an 'Incoming R2 register in a terminal exchange' (represented by a box labeled 'T'). Intermediate components include an 'Outgoing international R2 register' (shaded box), several 'T' (transit) exchanges, and an 'Incoming R2 register in a terminal international exchange' (shaded box). Arrows indicate the flow of signals: forward signals (10 or 6 backward m.c. / Up to 15 forward m.c. in the 1st section; 15 forward m.c. / 15 backward m.c. in the 2nd section; 10 forward m.c. / Up to 15 backward m.c. in the 2nd section) and backward signals. A legend at the bottom left defines 'm.c. = multifrequency combinations' and 'T = incoming R2 register in a transit exchange'. The diagram is labeled 'CCITT-49260' at the bottom right.
+
+Diagram of an international two-section multi-link connection showing signalling paths and multifrequency combinations.
+
+FIGURE 13/Q.441
+
+An international two-section multi-link connection
+
+#### 4.2.2 Allocation of interregister signals
+
+The signal coding consists of the association of the defined meaning of interregister telephone signals to the multifrequency combinations transmitted over the links. Certain combinations are left spare for the allocation of national or international signals. (For signalling procedures, see Recommendations Q.460 to Q.480.)
+
+##### 4.2.2.1 Multiple meaning
+
+The meaning of both the forward and backward multifrequency combinations can change after transmission of certain backward signals. The changed meaning is specific to the signal which caused or announced the change. In certain cases a change back to the original meaning is possible. The meaning of certain forward multifrequency combinations may also vary depending on their position in the signalling sequence.
+
+##### 4.2.2.2 Meanings of the forward multifrequency combinations
+
+There are two groups of meanings allocated to the forward multifrequency combinations. The Group I meanings are indicated in Table 6/Q.441 and the Group II meanings in Table 7/Q.441. The change from Group I to Group II meanings takes place when requested by the backward signals A-3 or A-5. Change back to Group I meanings is only possible when the change to Group II meanings was in response to signal A-5.
+
+The first forward signal transmitted in international working is used for additional routing information. It enables a distinction to be made between terminal and transit calls. In the case of terminal calls it carries the language or discriminating digit whereas, for transit calls, it serves the dual purpose of providing a country code indicator and to indicate whether an echo suppressor is required or not.
+
+The above arrangements obviate the need for two different seizing signals (line signals) to distinguish between transit and terminal traffic on links terminated in a transit exchange.
+
+##### 4.2.2.3 Meanings of the backward multifrequency combinations
+
+There are two groups of meanings allocated to the backward multifrequency combinations. The Group A meanings are indicated in Table 8/Q.441 and the Group B meanings in Table 9/Q.441. The change to Group B meanings is announced by the backward signal A-3. No change back is possible once a change to the Group B meanings of the backward multifrequency combinations has been indicated.
+
+##### 4.2.2.4 Integration of national and international signalling codes
+
+The utilization of Signalling System R2 in national networks is facilitated by the provision, in the specified signalling code, of signals specially assigned for national use. Under the specified code, specific national meanings are allocated to some of these signals, others are available for the allocation of national meanings at the discretion of each Administration.
+
+National allocations must not conflict with the present specifications in order to ensure end-to-end interregister signalling i.e. the direct dialogue between the outgoing international R2 register (in the originating country) and incoming R2 registers, in the national network of the destination country.
+
+The specified signalling code allows for a reduction of signalling frequencies in national networks (see § 4.2.1 above).
+
+#### 4.2.3 Forward signals
+
+##### 4.2.3.1 Group I forward signals
+
+Compelled interregister signalling must always begin with a Group I forward signal. For the signal codes see Table 6/Q.441.
+
+TABLE 6/Q.441
+Group I forward signals
+
+| Combination
(a) | Designation
of the signal
(b) | Meaning of the signal | | Remarks
(e) |
+|--------------------|-------------------------------------|----------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | (c) | (d) | |
+| 1 | I-1 | Language digit: French | Digit 1 | Col. (c) – These signals make up the first signal transmitted on an international link when it terminates in the country of destination of the call. When a link terminates in an international transit centre, however, these signals may be transmitted on the link after the country code indication and the country code.
See also Recommendation Q.107. |
+| 2 | I-2 | Language digit: English | Digit 2 | |
+| 3 | I-3 | Language digit: German | Digit 3 | |
+| 4 | I-4 | Language digit: Russian | Digit 4 | |
+| 5 | I-5 | Language digit: Spanish | Digit 5 | |
+| 6 | I-6 | Spare (language digit) | Digit 6 | |
+| 7 | I-7 | Spare (language digit) | Digit 7 | |
+| 8 | I-8 | Spare (language digit) | Digit 8 | |
+| 9 | I-9 | Spare (discriminating digit) | Digit 9 | |
+| 10 | I-10 | Discriminating digit | Digit 0 | |
+| 11 | I-11 | Country code indicator, outgoing half-echo suppressor required | Access to incoming operator (Code 11) | Col. (c) – First signal on an international link when it terminates in an international transit centre.
Col. (d) – Other than the first signal on an international link. |
+| 12 | I-12 | Country code indicator, no echo suppressor required | i) Access to delay operator (Code 12)
ii) Request not accepted | |
+| 13 | I-13 | Test call indicator (call by automatic test equipment) | i) Access to test equipment (Code 13)
ii) Satellite link not included | |
+| 14 | I-14 | Country code indicator, outgoing half-echo suppressor inserted | i) Incoming half-echo suppressor required
ii) Satellite link included | |
+| 15 | I-15 | Signal is not used | i) End-of-pulsing (Code 15)
ii) End of identification | |
+
+The *signals I-1 to I-10* are numerical signals indicating:
+
+- a) the *address* required for setting up the call (country code, national significant number); such address signals are sent by an outgoing R2 register or an outgoing international R2 register, either spontaneously and immediately after the seizure of the link or in response to one of the backward signals A-1, A-2, A-7 or A-8;
+- b) the country code (and possibly the area code as well) of the *location of the outgoing international R2 register*, in response to signals requesting the origin of the call. For national traffic, the telephone number of the calling subscriber's line (see Recommendation Q.480);
+- c) for automatic working the *discriminating digit* or, in the case of semi-automatic working, the service language to be used by the operator (i.e. *language digit*).
+
+The *signal I-11* is a non-numerical address signal. The meaning of the signal is dependent on its position within the sequence of address signals specified in Recommendation Q.107.
+
+- a) *Country code indicator, outgoing half-echo suppressor required*
+
+When signal I-11 is transmitted as the first forward signal it indicates that:
+
+- i) a country code will follow (international transit);
+- ii) the call requires echo suppressors;
+- iii) the outgoing half-echo suppressor has to be inserted.
+
+The use of this signal in international working is subject to bilateral agreement and is made in conformity with Recommendation Q.479.
+
+- b) *Access to incoming operator (code 11)*
+
+When signal I-11 is preceded by the language digit (and possibly by one further address digit) it indicates the address of the incoming operator's position and is then always followed by signal I-15 alone.
+
+For international working this signal is to be used only in conformity with Recommendation Q.107 *bis*. It can be used in national traffic only if the incoming R2 registers are equipped to receive all six forward frequencies. The necessary specifications are then the responsibility of the Administration concerned.
+
+The *signal I-12* is a non-numerical address signal. The meaning of the signal is dependent on its position in the sequence of address signals specified in Recommendation Q.107.
+
+- a) *Country code indicator, no echo suppressor required*
+
+When signal I-12 is transmitted as the first forward signal it indicates that:
+
+- i) a country code will follow (international transit);
+- ii) the call may not require any echo suppressor (see Recommendation Q.479).
+
+- b) *Access to delay operator (code 12)*
+
+When signal I-12 is preceded by the language digit (and possibly by one further address digit) it indicates that the call must be routed to the delay operator's position, either to a particular operator, or one of those operating a particular group of positions. It is then followed by further digits and the signal I-15 or by the signal I-15 alone.
+
+In international working this signal is to be used in conformity with Recommendation Q.107 *bis*. It can be used in national traffic only if the incoming R2 registers are equipped to receive all six forward frequencies. The necessary specifications are then the responsibility of the Administrations concerned.
+
+- c) *Request not accepted*
+
+An outgoing international R2 register which receives a signal A-9 or A-10, the use of which is exclusively national, or which receives by signal A-13 a request to which it is unable to reply, should indicate by transmitting signal I-12 that it cannot answer the query (see Recommendation Q.480). This signal may be similarly used in national traffic to indicate that response to signal A-9 or A-10 is not possible.
+
+The meaning of the non-numerical signal I-13 is dependent on its position in the sequence of address signals specified in Recommendation Q.107.
+
+- a) Test call indicator
+
+When in international working the signal I-13 is transmitted as the first forward signal it occupies the position of the language or discriminating digit. It serves then as a test call indicator and must be followed by the complete test equipment address information as specified in b) below.
+
+- b) *Access to test equipment (code 13)*
+
+To access automatic test equipment the second signal I-13 (the address digit) must be followed by two digits *xy* and the signal I-15.
+
+- c) *Satellite link not included*
+
+In response to signal A-13, the meaning of the signal I-13 is that up to the outgoing R2 register no satellite link is included.
+
+The meaning of the non-numerical *signal I-14* is dependent on its position in the sequence of address signals specified in Recommendation Q.107.
+
+- a) *Country code indicator, outgoing half-echo suppressor inserted*
+
+When signal I-14 is transmitted as the first forward signal it indicates that:
+
+- i) a country code will follow (international transit);
+- ii) the call requires echo suppressors;
+- iii) the outgoing half-echo suppressor has already been inserted.
+
+This signal is to be used in international working and only in conformity with Recommendation Q.479.
+
+- b) *Incoming half-echo suppressor required*
+
+In response to signal A-14, the meaning of the signal I-14 is that an incoming half-echo suppressor is necessary.
+
+- c) *Satellite link included*
+
+In response to signal A-13, the meaning of the signal I-14 is that up to the outgoing R2 register a satellite link is included in the connection.
+
+The non-numerical *signal I-15* indicates the end of a sequence of forward interregister signals. It is never sent as the first signal on an international link.
+
+- a) *End-of-pulsing*
+
+In international working, signal I-15 is used to indicate that there are no more address signals to follow (see Recommendations Q.107 and Q.473).
+
+- b) *End of identification*
+
+In national traffic, signal I-15 may be used to indicate that transmission of the sequence identifying the calling subscribers line is terminated (see Recommendation Q.480, § 5.8.2).
+
+##### 4.2.3.2 Group II forward signals
+
+The Group II forward signals are calling party's category signals sent by outgoing R2 registers or by outgoing international R2 registers in reply to the backward signals A-3 or A-5 and give information whether national or international working applies. For the signal codes see Table 5/Q.441.
+
+It is useful to identify calls according to type or function:
+
+- i) to indicate whether the forward transfer facility is required in international traffic;
+- ii) for adequate control of switching operations;
+- iii) to enable any additional meanings for the signals A-5 used in a national network but not internationally accepted (for example, to change the meanings of one or more following signals, forward or backward) to be made inoperative for incoming international calls;
+- iv) for maintenance purposes.
+
+The meanings of the calling party's category signals are detailed below:
+
+- a) The *signal II-1, subscriber without priority* indicates that the call is set up from a subscriber's line and is non-priority.
+- b) The *signals II-2 and II-9, subscriber with priority* indicate that the call is set up from a subscriber's line to which priority treatment of calls has been accorded. Signal II-2 is specified for national working only since there are no Recommendations regarding priority calls in automatic international working (see Recommendation Q.480).
+- c) The *signal II-3, maintenance equipment* indicates that the call comes from maintenance equipment.
+- d) The *signal II-5, operator* indicates that the call is set up from an operator's position.
+- e) The *signals II-6 and II-8, data transmission* indicate that the call will be used for data transmission.
+- f) The *signal II-7, subscriber* indicates that the call is set up from a subscriber's line, an operator's position or from maintenance equipment and that no forward transfer signal will be used.
+- g) The *signal II-10, operator with forward transfer facility* indicates that the call is set up from an operator's position with possibility of recourse to the forward transfer facility. Its use must be subject to bilateral agreement (see Annex A to the present Specifications).
+
+The signal II-4 and the signals II-11 to II-15 are spare. The meaning of signal II-4 will be decided later by international agreement.
+
+TABLE 7/G.441
+
+###### **Group II forward signals**
+
+| Combination
(a) | Designation
of the signal
(b) | Meaning of the signal
(c) | Remarks
(d) |
+|--------------------|-------------------------------------|---------------------------------------------------------------|-------------------------------------------------------------|
+| 1 | II-1 | Subscriber without priority | These signals
are solely used
for national
working |
+| 2 | II-2 | Subscriber with priority | |
+| 3 | II-3 | Maintenance equipment | |
+| 4 | II-4 | Spare | |
+| 5 | II-5 | Operator | |
+| 6 | II-6 | Data transmission | |
+| 7 | II-7 | Subscriber (or operator without
forward transfer facility) | These signals
are used
for international
working |
+| 8 | II-8 | Data transmission | |
+| 9 | II-9 | Subscriber with priority | |
+| 10 | II-10 | Operator with forward transfer facility | |
+| 11 | II-11 | Spare for national use | |
+| 12 | II-12 | | |
+| 13 | II-13 | | |
+| 14 | II-14 | | |
+| 15 | II-15 | | |
+
+*Note* – Signals II-7 to II-10 are used solely for international working. The rest of the Group II signals only apply for national working and are translated to signals II-7 to II-10 in the outgoing international R2 registers (see Recommendation Q.480). This enables the System R2 register at an incoming exchange to distinguish between national and international calls.
+
+#### 4.2.4 Backward signals
+
+##### 4.2.4.1 Group A backward signals
+
+Group A backward signals (for signal codes see Table 8/Q.441) are required to acknowledge Group I forward signals and under certain conditions, Group II forward signals. Besides that functional part of the compelled procedure, the Group A signals convey signalling information as detailed below:
+
+- a) The *signal A-1, send next digit* ( $n + 1$ ) requests transmission of the next digit ( $n + 1$ ) after reception of digit $n$ . The latest address signal sent is assumed to have the rank $n$ within the signal sequence specified in Recommendation Q.107.
+- b) The *signal A-2, send last but one digit* ( $n - 1$ ) requests the transmission of digit ( $n - 1$ ) after reception of digit $n$ . The latest address signal sent is assumed to have the rank $n$ within the signal sequence specified in Recommendation Q.107. This signal must not be used on a satellite link.
+
+TABLE 8/Q.441
+
+###### Group A backward signals
+
+| Combination
(a) | Designation
of the signal
(b) | Meaning of the signal
(c) |
+|--------------------|-------------------------------------|----------------------------------------------------------------------------------------------------------|
+| 1 | A-1 | Send next digit ( $n + 1$ ) |
+| 2 | A-2 | Send last but one digit ( $n - 1$ ) |
+| 3 | A-3 | Address-complete, changeover to reception of Group B signals |
+| 4 | A-4 | Congestion in the national network |
+| 5 | A-5 | Send calling party's category |
+| 6 | A-6 | Address-complete, charge, set-up speech conditions |
+| 7 | A-7 | Send last but two digit ( $n - 2$ ) |
+| 8 | A-8 | Send last but three digit ( $n - 3$ ) |
+| 9 | A-9 | } Spare for national use |
+| 10 | A-10 | |
+| 11 | A-11 | Send country code indicator |
+| 12 | A-12 | Send language or discrimination digit |
+| 13 | A-13 | Send nature of circuit |
+| 14 | A-14 | Request for information on use of an echo suppressor
(is an incoming half-echo suppressor required ?) |
+| 15 | A-15 | Congestion in an international exchange or at its output |
+
+- c) The *signal A-3, address-complete, changeover to reception of Group B signals* indicates that the incoming R2 register at the incoming end needs no additional address digit and is about to go over to transmission of a Group B signal conveying information about the condition of the equipment at the incoming exchange or the condition of the called subscriber's line (see Recommendation Q.442).
+- d) The *signal A-4, congestion in the national network* indicates:
+ - i) congestion of national links;
+ - ii) congestion in selection stages of terminal international or national exchanges;
+ - iii) occurrence of time-out or abnormal release of a System R2 register produced for any reason.
+
+For exception to these rules see n) below. See also signal B-4 and Recommendation Q.442.
+
+- e) The *signal A-5, send calling party's category* requests transmission of a Group II signal.
+- f) The *signal A-6, address-complete, charge – set-up speech conditions* indicates that the R2 register at the incoming end needs no additional digit, but will not send Group B signals. The call has to be charged on answer (see Recommendation Q.442).
+- g) The *signal A-7, send last but two digit ( $n - 2$ )* requests the sending of digit ( $n - 2$ ) after reception of digit $n$ . The latest address signal sent is to have the rank $n$ within the signal sequence specified in Recommendation Q.107. This signal must not be used on a satellite link.
+- h) The *signal A-8, send last but three digit ( $n - 3$ )* requests the sending of digit ( $n - 3$ ) after reception of digit $n$ . The latest address signal sent is to have the rank $n$ within the signal sequence specified in Recommendation Q.107. This signal must not be used on a satellite link.
+- i) The *signals A-9 to A-10* are spares available for allocation of national meanings. The use of signals A-9 and A-10 in national networks can be decided by each Administration. These signals must not be used on international satellite links.
+- j) The *signal A-11, send country code indicator* requests the country code indicator (transit indication) in acknowledgment of any forward signal. The signal is used in international transit calls only (see Recommendation Q.462). This signal must not be used on a satellite link.
+- k) The *signal A-12, send language or discriminating digit* requests the language digit or the discriminating digit in acknowledgment of any forward signal. This signal must not be used on a satellite link.
+- l) The *signal A-13, send nature of circuit* requests information regarding the nature of the circuits involved in the connection so far, i.e. satellite link (see Recommendation Q.480). This signal should only be used on a satellite link by bilateral agreement.
+- m) The *signal A-14, request for information on use of echo suppressor* (is an incoming half-echo suppressor required?) indicates that an incoming international exchange acknowledges the discrimination digit or the language digit and that it is possible to insert an incoming half-echo suppressor in that incoming international exchange if required. This signal must not be used on a satellite link.
+- n) The *signal A-15, congestion in an international exchange or at its output* indicates:
+ - i) congestion on international links;
+ - ii) congestion in selection stages at an international transit exchange or at a terminal international exchange and/or its outgoing links;
+ - iii) occurrence of time-out or abnormal release of a System R2 register produced for any reason (see Recommendation Q.442).
+
+##### 4.2.4.2 Group B backward signals
+
+Any Group B backward signal (for signal codes see Table 9/Q.441) acknowledges a Group II forward signal and is always preceded by the address-complete signal A-3 which indicates that the incoming R2 register has received all the Group I forward signals it requires from the outgoing international R2 register. Besides that functional part of the compelled procedure the Group B signals convey information about the condition of switching equipment in the incoming exchange, or about the condition of the called subscriber's line, to the outgoing international R2 register which can then take the necessary action as specified in Recommendation Q.474.
+
+TABLE 9/Q.441
+**Group B backward signals**
+
+| Combination
(a) | Designation
of the signal
(b) | Meaning of the signal
(c) |
+|--------------------|-------------------------------------|-----------------------------------------------------------------------------------|
+| 1 | B-1 | Spare for national use |
+| 2 | B-2 | Send special information tone |
+| 3 | B-3 | Subscriber line busy |
+| 4 | B-4 | Congestion (encountered after changeover from Group A signals to Group B signals) |
+| 5 | B-5 | Unallocated number |
+| 6 | B-6 | Subscriber's line free, charge |
+| 7 | B-7 | Subscriber's line free, no charge |
+| 8 | B-8 | Subscriber's line out of order |
+| 9 | B-9 | Spare for national use |
+| 10 | B-10 | |
+| 11 | B-11 | Spare for national use |
+| 12 | B-12 | |
+| 13 | B-13 | |
+| 14 | B-14 | |
+| 15 | B-15 | |
+
+The following Group B signals are specified:
+
+- a) The *signal B-1* is *spare* for national use and its meaning must be compatible with that of signal B-6 (see Recommendation Q.474).
+- b) The *signal B-2, send special information tone* indicates that the special information tone should be returned to the calling party. This tone indicates that the called number cannot be reached for reasons not covered by other specific signals and that the unavailability is of a long term nature (see also Recommendation Q.35).
+- c) The *signal B-3, subscriber's line busy* indicates that the line or lines connecting the called subscriber to the exchange are engaged.
+- d) The *signal B-4, congestion* indicates that congestion condition is encountered after the changeover from Group A signals to Group B signals. The signal B-4 shall be sent in the conditions specified for signal A-4 [see § 4.2.4.1, d) and Recommendation Q.474, § 5.3.5.1].
+- e) The *signal B-5, unallocated number* indicates that the number received is not in use (e.g. an unused country code, an unused trunk code or subscriber number that has not been allocated).
+- f) The *signal B-6, subscriber's line free, charge* indicates that the called party's line is free and that the call has to be charged on answer.
+- g) The *signal B-7, subscriber's line free, no charge* indicates that the called party's line is free but is not to be charged on answer. This signal permits non-chargeable calls without the need for transferring "no charge" information by line signals.
+- h) The *signal B-8, subscriber's line out of order* indicates that the subscriber's line is out-of-service or faulty.
+- i) *Signals B-9 and B-10* are spare for national use. Their meaning must not be incompatible with the sending of special information tone to the calling party (see Recommendation Q.474).
+- j) *Signals B-11 to B-15* are spare for national use. Their meaning can be allocated as required. Sending of these signals into the international network must be prevented.
+
+To deviate from this rule will result in the actions defined in Recommendation Q.474.
+
+### **4.3 PULSE TRANSMISSION OF BACKWARD SIGNALS A-3, A-4, A-6 OR A-15**
+
+Under certain conditions it may prove necessary or desirable to send one of the *signals A-3, A-4, A-6 or A-15* without prior reception of a forward signal. This can occur when the incoming R2 register, after acknowledging a recognized forward signal, is unable to complete the call (for example during congestion) and the next forward signal does not appear on the line; or when the address-complete signal must be sent after the last forward address signal has been acknowledged. It may be desirable to deliberately suspend compelled signalling by acknowledging the last address digit, and signal I-15 if received, with signal A-1 to avoid prolonging the transmission time of certain interregister signals. Such a course should certainly be considered when there is a possibility that a relatively long period may elapse between reception of the last digit and detection of the condition of the called subscriber's line. The average duration of such periods during the busy hour must be limited to 3 seconds in view of the load on the carrier systems in the case of international calls.
+
+The following conditions must be observed in transmitting pulsed interregister signals (see Figure 14/Q.442):
+
+- the minimum delay between the end of transmission of the last signal of the compelled cycle and the start of transmission of the pulse signal must be 100 ms;
+- the pulse duration must be $150 \pm 50$ ms.
+
+Reception of a pulse signal must cause interruption of any forward signal in course of transmission at the outgoing R2 register. It is sometimes impossible, however, to prevent a forward signal from being sent by the outgoing R2 register at the very moment when one of the backward signals A-3, A-4, A-6 or A-15 is sent in pulse form by the register at the incoming end.
+
+To reduce the operating difficulties which may result, the incoming R2 register must be so designed that no forward multifrequency combination can be recognized during and after the transmission of signals A-4, A-6 or A-15 in pulse form or during $300 \pm 100$ ms from the start of transmission of the address-complete signal A-3 in pulse form ( $900 \pm 180$ ms when signal A-3 is transmitted over a satellite link) (see Figures 14/Q.442 and 15/Q.442). When the end of a pulse signal A-3 has been recognized in the outgoing R2 register, a Group II signal must be sent forward. The incoming R2 register will acknowledge this signal by a Group B signal.
+
+On recognizing signal A-4, A-6 or A-15 no forward signal is sent by the outgoing R2 register. The end of these backward signals must cause the dismissal of the outgoing and incoming R2 registers in accordance with Recommendation Q.475.
+
+The conditions under which pulse transmission of the backward signals A-3, A-4, A-6 or A-15 apply are specified in Section 5.
+
+
+
+This timing diagram illustrates the sequence of signals between an Outgoing register and an Incoming register. The vertical axis represents time, with 'Sending' on the left and 'Receiving' on the right. The sequence of signals is as follows:
+
+- Group II signal**: A series of pulses sent from the outgoing register.
+- Group B signal**: A series of pulses sent from the outgoing register, following the Group II signal.
+- No forward signals can be recognized for $300 \pm 100$ ms ( $900 \pm 180$ ms)**: A period where no signals are sent.
+- Pulse signal A-3**: A pulse sent from the outgoing register, with a duration of $150 \pm 50$ ms.
+- > 100 ms**: A gap between Pulse signal A-3 and the last backward signal.
+- Last backward signal of a compelled sequence (e.g. A-1)**: A pulse sent from the incoming register back to the outgoing register.
+
+The diagram is labeled 'CCITT-49291' at the bottom.
+
+Timing diagram for pulse transmission of signal A-3 (CCITT-49291).
+
+FIGURE 14/Q.442
+Pulse transmission of signal A-3
+
+
+
+This timing diagram shows a variation of the previous one, where a 'Delayed forward signal' is introduced. The sequence is:
+
+- Group II signal** and **Group B signal** from the outgoing register.
+- No forward signals can be recognized for $300 \pm 100$ ms ( $900 \pm 180$ ms)**.
+- Pulse signal A-3** ( $150 \pm 50$ ms) from the outgoing register.
+- Delayed forward signal**: A signal sent from the incoming register, appearing after the start of Pulse signal A-3.
+- > 100 ms** gap.
+- Last backward signal of a compelled sequence (e.g. A-1)** from the incoming register.
+
+The diagram is labeled 'CCITT-49301' at the bottom.
+
+Timing diagram for pulse transmission of signal A-3 when delayed forward signal appears (CCITT-49301).
+
+FIGURE 15/Q.442
+Pulse transmission of signal A-3 when delayed forward signal appears
+
+### 4.4 MULTIFREQUENCY SIGNALLING EQUIPMENT
+
+#### Recommendation Q.450
+
+#### 4.4.1 GENERAL
+
+Since System R2 can provide, in international working, end-to-end signalling from the outgoing international R2 register to an incoming R2 register at the called subscriber's local exchange (see Recommendation Q.440), the specifications for multifrequency signalling equipment take account of transmission conditions in both the international and national networks. The incoming national network may include both 4-wire and 2-wire links.
+
+However, it is assumed in the following specifications for multifrequency signalling equipment for outgoing international R2 registers and incoming R2 registers in international exchanges including the incoming international exchange that the registers are directly connected by four wires to the virtual switching points of the links. The registers thus contain a multifrequency signalling equipment with a transmitting part and a receiving part, each separately connected to the GO and RETURN path of the 4-wire circuit respectively (see Figure 16/Q.451).
+
+When the outgoing international R2 register is situated in a national exchange preceding the outgoing international exchange, or when the incoming R2 register is situated in a national exchange following the incoming international exchange, special conditions apply (see Recommendation Q.457).
+
+The upper and lower limits specified for the sending level and for the national extension attenuation leave a degree of freedom, thus simplifying the problem of interworking among different networks. The outgoing international R2 register relays the interregister signals by the method described in Recommendation Q.478. The present specification ensures that the system has an adequate range.
+
+#### **4.4.2 DEFINITIONS**
+
+##### *4.4.2.1 Multifrequency signalling equipment*
+
+During the exchange of multifrequency combinations the link or multi-link section is terminated at both ends by equipment allowing multifrequency combinations to be sent and received under mutual, compelled control, as indicated in Recommendation Q.440. Generally speaking, the equipment involved in the signal transfer at each end of the multi-link section has the following functions:
+
+- reception of multifrequency combinations;
+- protection against disturbances (e.g. 2-out-of- $n$ -check, 0-out-of- $n$ -check, see Recommendation Q.458);
+- transfer of signals to and from the registers or equivalent equipment;
+- sending of multifrequency combinations.
+
+This equipment as a whole can be considered as a single functional unit, henceforth called the multifrequency signalling equipment.
+
+The functions of the multifrequency signalling equipment may be distributed among a number of sub-units, according to the design principles adopted in each particular case; these, within certain limits, are open to choice.
+
+For the purpose of the present specification, the multifrequency signalling equipment is divided into a sending part and a receiving part.
+
+###### *a) Four-wire multifrequency signalling equipment*
+
+Multifrequency signalling equipment connected to the speech path by two pairs of wires is called 4-wire multifrequency signalling equipment (see Figure 16/Q.451). In such cases, the speech path itself is generally 4-wire too.
+
+In Figure 16/Q.451, point B is the output of the sending part and point C the input to the receiving part of the 4-wire multifrequency signalling equipment. The latter includes the devices for protection against disturbances and the equipment for transferring signals to the register or equivalent equipment.
+
+###### *b) Two-wire multifrequency signalling equipment*
+
+Because different frequencies are used for interregister signalling in the two directions of transmission, a single pair of wires connecting the speech path to the multifrequency signalling equipment can be used for simultaneous sending and reception of multifrequency combinations.
+
+Multifrequency signalling equipment connected to the speech path by a single pair of wires is called 2-wire multifrequency signalling equipment (see Figure 17/Q.451).
+
+In Figure 17/Q.451, point A is the output of the sending part and, at the same time, the input to the receiving part. The latter includes the devices for protection against disturbances and for transferring signals to the register or equivalent equipment.
+
+##### *4.4.2.2 Operate and release times of the receiving part of the signalling equipment*
+
+The speed and reliability of the compelled interregister signal transfer is dependent on the operation and release times $T_0$ , $T_R$ , $T'_0$ and $T'_R$ defined below. These times include the minimum recognition times referred to in § 4.4.5.3 below.
+
+
+
+Diagram of four-wire multifrequency signalling equipment (CCITT-49310). It shows a box with four terminals on the left labeled S, S, R, and R. These are connected to two internal nodes, B and C. Node B is connected to an external line with impedance Z\_B and an arrow pointing 'To the 4-wire circuit'. Node C is connected to an external line with impedance Z\_C.
+
+R = receiving part
+ S = sending part
+ CD = coupling device (e.g. hybrid, set of directional filters, etc.)
+
+
+
+Diagram of two-wire multifrequency signalling equipment (CCITT-49320). It shows a box with four terminals on the left labeled S, S, R, and R. These are connected to a coupling device (CD) box. The output of the CD box is connected to a single external line at node A, with impedance Z\_A and an arrow pointing 'To the 2-wire circuit'.
+
+FIGURE 16/Q.451
+**Four-wire multifrequency signalling equipment**
+
+FIGURE 17/Q.451
+**Two-wire multifrequency signalling equipment**
+
+###### a) *Operation time*
+
+If the two frequencies making up a multifrequency combination are applied simultaneously to the input of the receiving part of the multifrequency signalling equipment, the time interval between the application of both frequencies and recognition of the multifrequency combination is called operation time $T_0$ .
+
+If one of the two frequencies making up a multifrequency combination is applied to the input of the receiving part of the multifrequency signalling equipment somewhat after the other frequency, the time interval between the application of the second frequency and recognition of the multifrequency combination is called operation time $T'_0$ .
+
+###### b) *Release time*
+
+If the two frequencies making up a multifrequency combination are simultaneously cut off from the input of the receiving part of the multifrequency signalling equipment, the time interval between the cut-off and recognition of the end of the multifrequency combination is called release time $T_R$ .
+
+If one of the two frequencies making up a multifrequency combination is cut off from the input of the receiving part of the multifrequency signalling equipment somewhat after the other frequency, the time interval between the cut-off of the second frequency and recognition of the end of the multifrequency combination is called release time $T''_R$ .
+
+##### 4.4.2.3 *Internal operation time*
+
+a) If the equipment at a switching centre has to analyse one or more of the signals received and if it has to carry out routing and switching operations before being able to determine which backward signal should be sent, it can delay completion of the compelled signalling cycle. Such delay depends on the function the centre has and on the design of the switching equipment used in it. The delay cannot therefore be specified.
+
+The time required by an incoming R2 register to determine which backward signal to send in reply to a forward signal is denoted as $T_{int 1}$ . The duration of the cycle is increased by the whole of this time, which must therefore be kept to a minimum. Its value will be zero if the signal to be sent is already determined.
+
+b) An outgoing R2 register sends a forward signal after interpreting the backward signal it has received. The time required to determine the appropriate signal is denoted as $T_{int 2}$ .
+
+c) At the end of a forward signal the incoming R2 register may have to perform certain functions in order to be ready to receive the next signal. The time required for these functions is denoted as $T_{int 3}$ .
+
+#### 4.4.3 REQUIREMENTS RELATING TO TRANSMISSION CONDITIONS
+
+##### 4.4.3.1 Impedances
+
+The impedance $Z_A$ measured at the terminals A (see Figure 17/Q.451) of a 2-wire multifrequency signalling equipment will have a nominal value equal to the nominal terminating impedance $Z_T$ of the links at the exchange under consideration and will be balanced to earth. In most cases this value $Z_T$ will be 600 ohms non-reactive. The impedance $Z_A$ will then satisfy the conditions:
+
+$$20 \log \left| \frac{600 + Z_A}{600 - Z_A} \right| \geq 10 \text{ dB} \quad (1)$$
+
+in the 300-3400 Hz band, and
+
+$$20 \log \left| \frac{600 + Z_A}{600 - Z_A} \right| \geq 16 \text{ dB} \quad (2)$$
+
+in the 520-1160 Hz and 1360-2000 Hz bands.
+
+The impedances $Z_B$ and $Z_C$ measured at the terminals B and C (see Figure 16/Q.451) of a 4-wire multifrequency signalling equipment will have a nominal value equal to the nominal terminating impedance $Z_T$ at the exchange under consideration and will be balanced to earth. In most cases this value $Z_T$ will be 600 ohms non-reactive. The impedances $Z_B$ and $Z_C$ will then satisfy condition (1) above in the 300-3400 Hz band and condition (2) above in the 520-1160 Hz or 1360-2000 Hz bands, according to the set of frequencies generated by the equipment concerned.
+
+All the above requirements must be met, whether signalling frequencies are being transmitted or not.
+
+##### 4.4.3.2 Echoes
+
+The balance return loss presented to the international link by different national networks varies considerably. Recommendation G.122 gives the desirable values based on transmission requirements and these values could hardly be improved on simply in order to facilitate signalling, especially as the balance return loss would then have to be very high.
+
+The multifrequency signalling equipment must therefore function with an echo signal. Allowance is made for this in the test conditions (see Recommendation Q.455).
+
+In order to eliminate disturbing and unwanted double-echo effects, outgoing international R2 registers must be provided with 4-wire signalling equipment; the 4-wire loop will then remain open at the outgoing end of the multi-link section during signalling.
+
+For the same reason, it is recommended that 4-wire signalling equipment be provided whenever 4-wire switching equipment is used.
+
+##### 4.4.3.3 Location and connection of multifrequency signalling equipment associated with outgoing international R2 registers
+
+The multifrequency signalling equipment of the outgoing international R2 registers is assumed to be directly connected to the virtual switching point of the links in an international exchange. This equipment may be situated in a national switching centre of the country of origin on the national network side of the outgoing international exchange provided that the 4-wire extension links between this centre and the outgoing international exchange have the same upper limit for the standard deviation of transmission loss variations with time (1 dB) as the international links.
+
+Should the national extension links not have a nominal transmission loss of 0.5 dB between the national exchange and the virtual switching point in the outgoing international exchange, there must be suitable compensation of the power level of the multifrequency combinations.
+
+#### 4.4.4 THE SENDING PART OF THE MULTIFREQUENCY SIGNALLING EQUIPMENT
+
+##### 4.4.4.1 *Signalling frequencies*
+
+The composition of the multifrequency combinations is specified in Recommendation Q.441.
+
+The frequencies in the forward direction are:
+
+$$f_0 = 1380, f_1 = 1500, f_2 = 1620, f_3 = 1740, f_4 = 1860, f_5 = 1980 \text{ Hz.}$$
+
+The frequencies in the backward direction are:
+
+$$f_0 = 1140, f_1 = 1020, f_2 = 900, f_3 = 780, f_4 = 660, f_5 = 540 \text{ Hz.}$$
+
+The frequency variation at the sending point must not exceed $\pm 4 \text{ Hz}$ relative to the nominal value.
+
+##### 4.4.4.2 *Absolute power level transmitted*
+
+a) Four-wire multifrequency signalling equipment for outgoing international R2 and incoming R2 registers assumed to be directly connected to the virtual switching point in an international exchange:
+
+- i) The absolute power level of each non-modulated signalling frequency transmitted by the sending part of the multifrequency signalling equipment in the international exchange concerned will have a nominal value of $-8 \text{ dBm0}$ with a tolerance $\pm 1 \text{ dB}$ . At an analogue input of the exchange, this corresponds to $-11.5 \text{ dBm} \pm 1 \text{ dB}$ .
+- ii) The difference in level between the two signalling frequencies making up a multifrequency combination must be less than $1 \text{ dB}$ .
+
+The tolerances specified apply to the sending point itself, i.e. terminal B in Figure 16/Q.451.
+
+b) Four-wire multifrequency signalling equipment for outgoing international R2 registers situated in a national exchange further down in the network of the country of origin:
+
+- i) The sending-level conditions mentioned above under a) are applicable in such national exchanges, provided that the national 4-wire extension links between the national exchange and the outgoing international exchange have the same nominal transmission loss ( $0.5 \text{ dB}$ ) and the same upper limit of standard deviation of transmission loss variations with time ( $1 \text{ dB}$ ) as the international links.
+- ii) If these national links do not have a nominal transmission loss of $0.5 \text{ dB}$ , the level of interregister frequencies must be compensated as required.
+
+c) Multifrequency signalling equipment for incoming R2 registers in national exchanges:
+
+The nominal absolute power level $N$ of a single signalling frequency transmitted by the sending part of the multifrequency signalling equipment (2-wire or 4-wire) in any national exchange must be chosen within the limits:
+
+$$N \geq A_b + 0,5 m + 2,3 \sqrt{(m + k) + (m + k + 1) 0,04} - 31 \text{ dBm} \quad (1)$$
+
+and
+
+$$N \leq A_b - 11,5 \text{ dBm} \quad (2)$$
+
+or
+
+$$N \leq A_b + 0,5 m - 2,3 \sqrt{(m + k) + (m + k + 1) 0,04} - 9 \text{ dBm} \quad (3)$$
+
+whichever of (2) or (3) yields the lower value.
+
+In order to avoid marginal operation, it is recommended that levels higher than the minimum levels given by formula (1) be specified.
+
+In these formulae:
+
+- $m$ = the number of 4-wire links switched in tandem between the outgoing international R2 register and the incoming international exchange. The number $m$ thus includes the national 4-wire extension links in the country of origin (see Recommendation Q.457) and the international links. In formula (1) $m$ should always be given the maximum value 4. In formula (3), $m$ should be given all its values, from minimum to maximum, and the lowest value so obtained or derived from formula (2) is to be taken as the upper limit of $N$ .
+- $k$ = the number of national 4-wire extension links switched in tandem between the incoming international terminal exchange and the national exchange. The maximum value of $k$ will be 4.
+- $A_b$ = the nominal transmission loss at 800 Hz in the backward direction between the output terminals of the sending part of the multifrequency signalling equipment of the incoming R2 register in the exchange under consideration and the *send* side of the virtual switching point of the backward speech path in the incoming international exchange.
+
+Formulae (1), (2) and (3) were derived as shown in Annex A to Section 4.
+
+The variation in level relative to the nominal value $N$ chosen for a given exchange must not exceed $\pm 1$ dB.
+
+However, the difference in level between the two signalling frequencies making up a multifrequency combination must not exceed 1 dB.
+
+##### 4.4.4.3 *Signalling frequency leak level*
+
+The total power level of the leak current transmitted to line must be:
+
+- a) at least 50 dB below the nominal level of one signalling frequency when no multifrequency combination is being sent;
+- b) at least 30 dB below the level of either of the signalling frequencies when a multifrequency combination is being sent. Furthermore, any single leak current must be at least 34 dB below the level of either of the signalling frequencies when a multifrequency combination is being sent.
+
+##### 4.4.4.4 *Harmonic distortion and intermodulation*
+
+The total power level of all frequencies due to harmonic distortion and intermodulation within the frequency band 300-3400 Hz must be at least 37 dB below the level of one signalling frequency.
+
+##### 4.4.4.5 *Time tolerance for multifrequency combinations*
+
+The time interval between the start of sending of each of the two frequencies constituting a multifrequency combination must not exceed 1 ms.
+
+The time interval between the cessation of sending of each of the two frequencies must not exceed 1 ms.
+
+##### Recommendation Q.455
+
+#### 4.4.5 THE RECEIVING PART OF THE MULTIFREQUENCY EQUIPMENT
+
+##### 4.4.5.1 *Sensitivity range*
+
+The power levels given below relate to the nominal impedance of the receiving part of the multifrequency signalling equipment.
+
+The receiving part of the multifrequency signalling equipment shall have a sensitivity range of $-31.5$ dBm0 to $-5$ dBm01).
+
+---
+
+1) For equipments already in service the sensitivity range is $-35$ dBm to $-5$ dBm.
+
+##### 4.4.5.2 Operate and release time requirements
+
+The operating and release times of the receiving part of the multifrequency signalling equipment depend on the design and, for a given design, on:
+
+- the time difference between the instants of reception of each of the two frequencies making up a multifrequency combination;
+- the level of each of the two frequencies;
+- the difference in level between the two frequencies;
+- the level, spectrum and instant of onset of the noise.
+
+The factors vary with transmission conditions. With certain types of switching equipment it may prove advisable to embody devices to counteract low-frequency disturbances in the multifrequency signalling equipment.
+
+Time requirements have been specified for two types of *multifrequency test combinations*, A and B, applied to the input of the receiving part of the multifrequency signalling equipment in the presence of disturbing signals as specified below.
+
+When test combinations and disturbing frequencies as specified under a) to c) below are applied to the terminals A (see Figure 17/Q.451) of 2-wire multifrequency signalling equipment or to the terminals C (see Figure 16/Q.451) of 4-wire multifrequency signalling equipment, the following time requirements must be met:
+
+- for type A test combinations:
+
+$$T_0 + T_R \leq 70 \text{ ms}$$
+
+- for type B test combinations:
+
+$$T_0 + T_R \leq 80 \text{ ms}$$
+
+- for test combinations of types A and B:
+
+$$(T'_0 + T'_R) \leq (T_0 + T_R) + 5 \text{ ms}$$
+
+For definitions of $T_0$ , $T'_0$ , $T_R$ , and $T'_R$ see Recommendation Q.451.
+
+For the third requirement, the only cases to be considered are those in which the frequency first appearing is also the first to disappear (transmission delay effect). The $T'_0$ and $T'_R$ time requirements are specified to ensure proper functioning of the multifrequency signalling equipment when the received multifrequency combination is affected by group delay distortion, for example. The appropriate procedure for this test depends on the design of the equipment to be tested; in many cases it will be convenient to assume that a delay of one second or more for the second frequency constitutes the most unfavourable case.
+
+When a multifrequency combination has caused the receiving part of the multifrequency signalling equipment to operate, the latter cannot release if the signal frequencies are interrupted for not more than 7 ms. A method of improving the system reliability in case of interrupted signals is described in Annex B of Section 4.
+
+###### a) *Multifrequency test combinations type A*
+
+- The multifrequency test combination consists of any 2-out-of- $n$ combination of the $n$ signalling frequencies;
+- each frequency differs from the nominal frequency by not more than $\pm 5$ Hz;
+- the absolute power level of each of the two frequencies of the multifrequency combination lies between $-5$ dBm and $-20$ dBm;
+- the difference in level between the two frequencies is not greater than 3 dB.
+
+###### b) *Multifrequency test combinations type B*
+
+- The multifrequency test combination consists of any 2-out-of- $n$ combination of the $n$ signalling frequencies;
+- each frequency differs from the nominal frequency by not more than $\pm 10$ Hz;
+- the absolute power level of each of the two frequencies of the multifrequency combination lies between $-5$ dBm and $-35$ dBm;
+- the difference in level between the two frequencies is not greater than 5 dB for adjacent frequencies and 7 dB for non-adjacent frequencies.
+
+###### c) *Disturbing frequencies*
+
+The disturbing frequencies to be applied are:
+
+- in all cases one or more of the $n$ frequencies for which the receiving part under test is designed, with a total power level of $-55$ dBm or less, when no multifrequency test combination is being applied;
+- when a multifrequency test combination is applied, one or more of the $(n - 2)$ remaining frequencies with a total power level 20 dB below the highest test combination frequency level during application of the test combination;
+- for testing the receiving part of 4-wire multifrequency signalling equipment in an outgoing international R2 register:
+
+any multifrequency combination consisting of two frequencies out of the forward group of frequencies, each of these two frequencies having a level of 13.5 dB above the lowest test-combination frequency level in the backward direction; an upper limit of $-12.5$ dBm is nevertheless specified for the level of the disturbing signal.
+
+System R2 interregister signalling may be used in the country of origin on the national links preceding the out-going international R2 register. In that case, the receiving part of 4-wire multifrequency signalling equipment connected to the forward speech path of the national 4-wire links may have to function in the presence of frequencies used in the backward direction. No general specification can be given for the level of these disturbing frequencies; it is recommended that Administrations formulate their own specifications.
+
+- for testing the receiving part of 2-wire multifrequency signalling equipment:
+
+any multifrequency combination at the highest level used in operational signalling (measured at point A, Figure 17/Q.451) by the sending part of the 2-wire multifrequency signalling equipment concerned.
+
+##### 4.4.5.3 *Non-operate and non-recognition requirements*
+
+The receiving part of the multifrequency signalling equipment must remain in the *non-operate* state when the following disturbances, singly or together, are the only signals that are applied to the terminals A or C (see Figures 17/Q.451 and 16/Q.451):
+
+- any single pure sine wave or any combination of two pure sine waves, each with a power level of $-38.5$ dBm0 within the 300-3400 Hz band;2)
+- any single pure sine wave or any combination of two pure sine waves, each with a power level of $-42$ dBm within the 300-3400 Hz band;
+- any combination of two pure sine waves, each with a power level of $-5$ dBm within the 1300-3400 Hz band for the set of frequency receivers used in the backward direction; and within the 330-1150 Hz and 2130-3400 Hz bands for the set of frequency receivers used in the forward direction.
+
+Furthermore, when signalling tones have activated the receiving part of the multifrequency signalling equipment, this must assume the *non-operate* state when the signalling tones are removed in the presence of these same disturbances, singly or together, at the above-mentioned terminals.
+
+---
+
+2) For equipments already in service, the non-operation level is $-42$ dBm.
+
+The receiving part of the multifrequency signalling equipment must not recognize a combination consisting of two signalling frequencies out of the set of frequencies normally used in the transmission direction considered, each having a level not exceeding $-5$ dBm and a duration of less than 7 ms.
+
+The receiving part of the multifrequency signalling equipment must not recognize a combination consisting of two signalling frequencies used in the transmission direction considered, having a difference in level of 20 dB or more.
+
+##### 4.4.5.4 *Influence of transient disturbances* (see also Recommendation Q.458)
+
+The recognition of faulty signals due to short-lived transient conditions can largely be avoided if a multifrequency combination is recognized only after a specified minimum time, during which two, and only two, of the individual receivers are active and if the absence of multifrequency combinations is recognized only after a minimum time, during which all individual receivers are at rest. These times are included in the operating and release times $T_0$ and $T_R$ .
+
+Typical transient disturbances, such as clicks, change of polarity, etc., generated by the switching equipment, must not change signals transferred from the receiving part of the signalling equipment to the register.
+
+It is recommended that Administrations formulate their own specification for a test method according to the type of disturbances encountered in their switching equipment.
+
+### 4.5 RANGE, SPEED AND RELIABILITY OF INTERREGISTER SIGNALLING
+
+#### Recommendation Q.457
+
+#### 4.5.1 RANGE OF INTERREGISTER SIGNALLING
+
+##### 4.5.1.1 *Number of international links*
+
+The number of international links switched in tandem for establishing an international connection using System R2 must not exceed 4 (see Recommendation Q.440).
+
+Assumptions for the transmission loss in 4-wire international links:
+
+- i) nominal transmission loss at 800 Hz: 0.5 dB (Recommendation G.101, § 5);
+- ii) standard deviation of transmission loss variations with time must not exceed 1 dB [Recommendation G.151, § 3, a)];
+- iii) the difference between the mean value and the nominal is assumed to be 0 [as in Recommendations G.122, § 1.2), and G.131, § 1].
+
+##### 4.5.1.2 *Number of national links*
+
+###### a) *Outgoing international R2 register and number of national 4-wire extension links in the country of origin*
+
+The outgoing international R2 register is always provided with 4-wire multifrequency signalling equipment and the 4-wire loop will be open during interregister signalling.
+
+The outgoing international R2 register must be placed in an exchange from where the incoming international exchange in the country of destination is reached by not more than four 4-wire links switched in tandem (see Recommendation Q.440).
+
+It is understood that the national 4-wire links in the country of origin shall have the same standard deviation of transmission loss variations with time (1 dB) as the international links and that, if these national links do not have the same nominal transmission loss as the international links (0.5 dB), appropriate compensation of the multifrequency combination levels will be made in both directions of transmission.
+
+b) *Number (k) of national 4-wire extension links in the country of destination*
+
+Not more than four national 4-wire extension links may be used.
+
+Forward transmission loss in the country of destination:
+
+- i) The standard deviation of transmission loss variations with time in the national 4-wire extension links in the country of destination must not exceed 1 dB.
+- ii) The nominal transmission loss at 800 Hz in the forward direction ( $A_f$ ) between the virtual switching point in the incoming international exchange and any incoming R2 register in the country of destination must not exceed:
+
+11.4 dB for a country using 3 national 4-wire extension links at the most
+
+or
+
+11.0 dB for a country using 4 national 4-wire extension links at the most,
+and must never be less than:
+
+$$A_{fmin} = -2.5 - 0.5 m + 2.3 \sqrt{(m+k) + (m+1)0.04} \text{ dB.}$$
+
+The values for the minimum forward transmission loss $A_{fmin}$ resulting from this formula are shown in Table 10/Q.457 (for the definitions of $m$ and $k$ see Recommendation Q.454). In practice the forward transmission loss must not fall below these values.
+
+The formula has been determined as shown in Annex C to Section 4.
+
+When System R2 end-to-end signalling is applied in a national network, the 4-wire links involved may not conform to the characteristics specified by the CCITT for international circuits. Also, national transmission plans may be based on principles different from those of the international transmission plan. Consequently, the range over which end-to-end signalling is possible must be established using calculations, e.g. as shown in Annex C to Section 4 (see also §§ 4.5.1.3 and 4.5.1.4 below).
+
+TABLE 10/Q.457
+
+###### **Minimum forward transmission loss in the country of destination**
+
+| $m \backslash k$ | 1 | 2 | 3 | 4 |
+|------------------|-----|-----|-----|-----|
+| 1 | 0.3 | 0.6 | 0.7 | 0.8 |
+| 2 | 1.1 | 1.2 | 1.3 | 1.3 |
+| 3 | 1.7 | 1.8 | 1.8 | 1.7 |
+| 4 | 2.3 | 2.3 | 2.2 | 2.2 |
+
+##### 4.5.1.3 *Total attenuation distortion*
+
+It has been assumed that at all frequencies within the 530-1990 Hz band the overall attenuation distortion relative to 800 Hz between the outgoing international R2 register and any incoming R2 register will not exceed $\pm 3$ dB. Attention is drawn to the fact that on some national connections these assumptions might not be fulfilled.
+
+As type B test signals (see Recommendation Q.455) allow for a 5 dB difference in level between two adjacent signalling frequencies, and a 7 dB difference between two non-adjacent signalling frequencies, a 4 dB attenuation distortion of the multi-link section can be allowed for two adjacent frequencies and a 6 dB distortion for two non-adjacent frequencies, provided that the level of the weakest signalling frequency is not lower than -35 dBm at the terminals of the receiving part of the multifrequency signalling equipment.
+
+The values 4 dB and 6 dB were obtained by allowing for a 1 dB difference in sending level.
+
+##### 4.5.1.4 Intermodulation
+
+A multifrequency signalling system in conformity with the above specifications will allow satisfactory working over a multi-link section introducing intermodulation products from two signalling frequencies and falling within the 520-1160 Hz and 1360-2000 Hz bands, the level of each of such products being at least 24 dB below the highest signal frequency level.
+
+#### 4.5.2 Build-up and time specification of a complete forward compelled signalling cycle
+
+Figure 18/Q.457 shows in detail the build-up and time sequence of a compelled signalling cycle.
+
+
+
+Outgoing R2 register
+Incoming R2 register
+
+The diagram illustrates the following sequence:
+1. Outgoing register sends forward multifrequency combination after delay $T_{s1}$ .
+2. Signal propagates to Incoming register (delay $T_{PF}$ ).
+3. Incoming register recognizes signal after delay $T_0$ or $T_0'$ .
+4. Incoming register sends backward multifrequency combination after internal delay $T_{int1}$ and $T_{s1}$ .
+5. Signal propagates back to Outgoing register (delay $T_{PB}$ ).
+6. Outgoing register recognizes backward signal after delay $T_0$ or $T_0'$ .
+7. Outgoing register ceases forward signal after internal delay $T_{int2}$ and $T_{s2}$ .
+8. Cessation propagates to Incoming register (delay $T_{PF}$ ).
+9. Incoming register recognizes cessation after delay $T_R$ or $T_R'$ .
+10. Incoming register ceases backward signal after internal delay $T_{int3}$ and $T_{s2}$ .
+11. Cessation propagates back to Outgoing register (delay $T_{PB}$ ).
+12. Outgoing register recognizes cessation after delay $T_R$ or $T_R'$ and prepares for next cycle after $T_{s1}$ .
+
+$T = \text{duration of a compelled signalling cycle}$
+
+CCITT-49331
+
+Timing diagram showing the sequence of a complete compelled signalling cycle between an Outgoing R2 register and an Incoming R2 register. The diagram uses vertical lines to represent the registers and horizontal/slanted arrows to represent signal transmission and propagation delays. Key time intervals include Ts1, T0, T0', Tint1, Tint2, Tint3, TPB, TPF, TR, TR', and the total cycle duration T.
+
+FIGURE 18/Q.457
+**Sequence of a complete compelled signalling cycle**
+
+In this figure:
+
+$T_{PF}$ denotes the transmission delay of the slower of the two frequencies of a forward multifrequency combination;
+
+$T_{PB}$ denotes the transmission delay of the slower of the two frequencies of a backward multifrequency combination;
+
+$T_0$ and $T'_0$ denote the operating times as defined in Recommendation Q.451;
+
+$T_R$ and $T'_R$ denote the release times as defined in Recommendation Q.451;
+
+$T_{int 1}$ , $T_{int 2}$ and $T_{int 3}$ denote the internal operation times as defined in Recommendation Q.451.
+
+If the values of $T_{int 2}$ and $T_{int 3}$ lie within certain limits, they do not contribute to the total duration of the compelled signalling cycle, as can be seen from Figure 18/Q.457.
+
+$T_{S1}$ and $T_{S2}$ denote respectively the time required for starting and stopping the sending of a multifrequency combination (switching-on or switching-off times, exclusive of logic operations).
+
+It thus appears that the total duration $T$ of a complete compelled signalling cycle is given by the formula:
+
+$$T = 2 (T_{PF} + T_{PB}) + \left\{ \begin{array}{c} (T_0 + T_R)_D + (T_0 + T_R)_A \\ \text{or} \\ (T'_0 + T'_R)_D + (T'_0 + T'_R)_A \end{array} \right\} + T_{int 1} + (T_{S1} + T_{S2})_D + (T_{S1} + T_{S2})_A$$
+
+The subscripts $D$ and $A$ apply respectively to the outgoing and the incoming registers.
+
+$T_{PF}$ and $T_{PB}$ depend on the propagation characteristics of the forward and backward speech paths respectively and therefore cannot be specified.
+
+A value of 10 ms for $T_{PF}$ and $T_{PB}$ can be considered as typical, e.g. for average terrestrial regional connections and 320 ms for circuits including a satellite link.
+
+The maximum value of $T_0 + T_R$ has been fixed at 70 ms. A value of 35 ms could be taken in a certain number of cases as representing the minimum duration of $T_0 + T_R$ .
+
+$T_{int 1}$ , $T_{int 2}$ and $T_{int 3}$ are dependent on the type of exchange and therefore cannot be specified; but their contribution to the total duration of the compelled signalling cycle must be kept as small as possible.
+
+If the influence of $T_{int 1}$ , $T_{int 2}$ and $T_{int 3}$ is ignored, and if the extreme values of $T_0 + T_R$ and for $T_{S1} + T_{S2}$ are assumed to be identical for the outgoing and the incoming register, the extreme values of $T_{S1} + T_{S2}$ being taken as $5 \text{ ms} \leq T_{S1} + T_{S2} \leq 10 \text{ ms}$ and if the value of 10 ms indicated above as typical is adopted for $T_{PF}$ and $T_{PB}$ , the probable extreme values of the compelled signalling cycle $T$ would be:
+
+for terrestrial connections: $120 \text{ ms} \leq T \leq 200 \text{ ms}$ .
+
+for circuits including a satellite link: $1080 \text{ ms} \leq T \leq 1440 \text{ ms}$ .
+
+The signalling rates would be between approximately 8 and 5 signalling cycles per second for terrestrial circuits. These values are not absolute limits; the signalling cycle could, for example, be longer on a complex connection or in the presence of noise or other conditions approaching those of type B test combinations (see Recommendation Q.455).
+
+#### **4.5.3 RELIABILITY OF INTERREGISTER SIGNALLING**
+
+##### **4.5.3.1 *General***
+
+In signal transmission, reliability and speed are to some extent conflict requirements: the slower the signalling, the more reliable it is likely to be. System R2 combines the two essential requirements of speed and reliability, since it is a compelled system, adapting its signalling speed to the working conditions with minimum loss of reliability.
+
+System R2 is protected against the acceptance of faulty information (multifrequency combinations consisting either of one frequency only or of more than two frequencies) by means of the *2-out-of-n* method of checking the number of frequencies received.
+
+This protection is inoperative in the case of disturbances (noise, clicks, etc.) activating two, and only two, of the single frequency receivers; nor does it prevent the release of all the receivers (thus wrongly indicating the end of a multifrequency combination) in the event of an interruption caused by disturbances during transmission of a multifrequency combination.
+
+Disturbances causing the operation of two single frequency receivers or the release of all the receivers are due mainly to short-lived, transient conditions. The recognition of faulty information due to such conditions can therefore largely be avoided by so designing the receiving part of the multifrequency signalling equipment that a multifrequency combination will be recognized only after a specified minimum time. During this time two, and only two, of the individual receivers are active and the absence of multifrequency combinations will be recognized only after a specified minimum time, during which all individual receivers are at rest. The degree of protection against faults due to the above-mentioned conditions is dependent on these times, which are included in the operating and release times defined for the receiving part of the multifrequency signalling equipment in Recommendation Q.451.
+
+##### **4.5.3.2 *Error rate for compelled working***
+
+The test of the multifrequency signalling equipment as a whole consists in continuous, compelled transmission of multifrequency combinations.
+
+It must be ensured that all possible combinations of the forward and backward multifrequency combinations have equal probability of occurrence during the test period.
+
+The error rate is observed at the receiving part at both ends of the link and is defined, for each end, as the number of errors divided by the number of combinations sent by the corresponding sending parts at each end of the link.
+
+It is for each Administration to define the sources of permanent and impulsive noise to be applied to the interface between the sending and receiving parts in the light of its experience and local conditions.
+
+The compelled working may be tested, on the one hand, by using test combinations of Type A (see Recommendation Q.455) in the presence of noise at a power level of $-40$ dBm and a uniform power distribution in the 300-3400 Hz band (filtered white noise) and, on the other hand, by using Type B test combinations in the presence of noise at a power level of $-45$ dBm and a uniform power distribution in the 300-3400 Hz band.
+
+The error rates in these conditions will be:
+
+- for Type A test combinations and noise at $-40$ dBm: $\leq 10^{-5}$ ;
+- for Type B test combinations and noise at $-45$ dBm: $\leq 10^{-4}$ .
+
+## ANNEX A
+
+(to Section 4)
+
+(see Recommendation Q.454)
+
+### Development of formulae for the power level of signalling frequencies
+
+The formulae (1), (2), and (3) of Recommendation Q.454 describing the nominal absolute power level $N$ of a transmitted single signalling frequency were derived as follows:
+
+1. The nominal transmission loss in the backward direction between the incoming R2 register and the outgoing international R2 register is given by (see Recommendation Q.457):
+
+$$A_b + 0.5 m \text{ dB.}$$
+
+2. On the assumption that the contribution of the national 2-wire links to transmission loss variations with time is negligible and with allowance for the standard deviation of transmission loss variations with time of the international and national 4-wire circuits and in the exchanges (see CCITT Recommendation Q.45: $\sigma = 0.2 \text{ dB}$ ), the total transmission loss variation for a 1% probability of it being exceeded is given by:
+
+$$\pm 2.3 \sqrt{(m+k) + (m+k+1)(0.2)^2} \text{ dB.}$$
+
+3. Given a total attenuation distortion of $\pm 3 \text{ dB}$ relative to 800 Hz (see Recommendation Q.457) and a tolerance of $\pm 1 \text{ dB}$ on the nominal power level $N$ , the lower and upper limits of the level received in the outgoing international R2 register will be:
+
+$$N - A_b - 0.5 m - 2.3 \sqrt{(m+k) + (m+k+1) 0.04} - 3 - 1 \text{ dBm}$$
+
+and
+
+$$N - A_b - 0.5 m + 2.3 \sqrt{(m+k) + (m+k+1) 0.04} + 3 + 1 \text{ dBm.}$$
+
+respectively.
+
+4. The receiving part of the multifrequency signalling equipment has a sensitivity range between
+
+$$-35 \text{ dBm and } -5 \text{ dBm (see Recommendation Q.455).}$$
+
+The minimum value of $N$ is thus given by:
+
+$$N - A_b - 0.5 m + 2.3 \sqrt{(m+k) + (m+k+1) 0.04} - 4 = -35 \text{ dBm}$$
+
+hence
+
+$$N \geq A_b + 0.5 m + 2.3 \sqrt{(m+k) + (m+k+1) 0.04} - 31 \text{ dBm} \quad (1)$$
+
+The maximum value of $N$ is given by:
+
+$$N - A_b - 0.5 m + 2.3 \sqrt{(m+k) + (m+k+1) 0.04} + 4 = -5 \text{ dBm}$$
+
+hence
+
+$$N \leq A_b + 0.5 m - 2.3 \sqrt{(m+k) + (m+k+1) 0.04} - 9 \text{ dBm} \quad (3)$$
+
+5. The nominal level of the backward signals at the virtual switching point of the incoming international exchange must not be higher than $-11.5 \text{ dBm}$ ; thus
+
+$$N - A_b \leq -11.5 \text{ dBm}$$
+
+hence
+
+$$N \leq A_b - 11.5 \text{ dBm.} \quad (2)$$
+
+## ANNEX B
+
+(to Section 4)
+
+(see Recommendation Q.455)
+
+### **Possible method of improving protection from interruptions**
+
+If the receivers are locked through an internal function of the registers until the times *Q* and *S* (see Figure B-1) the intervals during which there is a risk that interruptions may cause their release are reduced by *PQ* and *RS* respectively.
+
+This method can be used on both terrestrial and satellite circuits.
+
+To ensure that the duration of the compelled signalling cycle is not prolonged on terrestrial circuits (short transmission delay), *PQ* and *RS* must be calculated with:
+
+$$T_{PF} = T_{PB} \approx 0 \text{ ms: } PQ \leq T_{int1} + T_{S1} + T_0 + T_{S2}$$
+
+and
+
+$$RS \leq T_{S2} + T_R + T_{S2}$$
+
+To ensure that the duration of the compelled signalling cycle is not prolonged on satellite circuits (long transmission delay) *PQ* and *RS* must be calculated with:
+
+$$T_{PF} + T_{PB} \approx 250 \text{ ms: } PQ \leq 500 \text{ ms} + T_{int1} + T_{S1} + T_0 + T_{S2}$$
+
+and
+
+$$RS \leq 500 \text{ ms} + T_{S2} + T_R + T_{S2}$$
+
+
+
+The diagram illustrates the timing relationships between an Outgoing R2 register and an Incoming R2 register. It shows the sequence of signals: 'Sending of forward multifrequency combination', 'Receiving of forward multifrequency combination', 'Sending of backward multifrequency combination', and 'Receiving of backward multifrequency combination'. Key timing intervals are marked: *TPF* (propagation time forward), *TPB* (propagation time backward), *T0* (start time), *TS1* (start time), *TS2* (stop time), *TR* (receive time), *Tint1* (internal time 1), and *Tint2* (internal time 2). The diagram also includes labels for points *P*, *Q*, *R*, and *S* on the timing axis, and a reference code T0209430-02.
+
+Timing diagram for Outgoing and Incoming R2 registers showing signal transitions and timing intervals like T\_PF, T\_PB, T\_0, T\_S1, T\_S2, T\_R, T\_int1, and T\_int2.
+
+FIGURE B-1
+
+## ANNEX C
+
+(to Section 4)
+
+(see Recommendation Q.457)
+
+### Development of a formula for the admissible forward transmission loss in a country of destination
+
+The formula used in Recommendation Q.457 for the calculation of the minimum forward transmission loss $A_{f\min}$ a country of destination was determined as follows:
+
+1. According to Recommendation Q.454 the lowest and highest sending levels will be, respectively,
+
+$$-11.5 - 1 = -12.5 \text{ dBm}$$
+
+and
+
+$$-11.5 + 1 = -10.5 \text{ dBm}.$$
+
+2. Let $A_f$ be the nominal transmission loss at 800 Hz in the forward direction, between the virtual switching point in the incoming international exchange and the incoming R2 register concerned.
+
+The total nominal transmission loss between the outgoing international R2 register and the incoming R2 register will then be:
+
+$$A_f + 0.5 m \text{ dB}.$$
+
+3. On the assumption that the contribution of the national 2-wire links to transmission loss variations with time is negligible, and that the standard deviation of transmission loss variation in the exchange is 0.2 dB (see Recommendation Q.45), the total transmission loss variation, calculated for a 1% probability of it being exceeded will be:
+
+$$\pm 2.3 \sqrt{(m + k) + (m + k + 1) 0.2^2} \text{ dB}.$$
+
+4. With allowance for a total attenuation distortion of $\pm 3$ dB relative to 800 Hz (see Recommendation Q.457) the lower and upper limits of the level of each frequency at the input of the incoming R2 register will be respectively:
+
+$$-12.5 - A_f - 0.5 m - 2.3 \sqrt{(m + k) + (m + k + 1) 0.04} - 3 \text{ dBm}$$
+
+and
+
+$$-10.5 - A_f - 0.5 m + 2.3 \sqrt{(m + k) + (m + k + 1) 0.04} + 3 \text{ dBm}.$$
+
+5. The receiving part of the multifrequency signalling equipment has a sensitivity range of $-35$ dBm to $-5$ dBm.
+
+6. The maximum value of $A_f$ is thus given by:
+
+$$-12.5 - A_{f\max} - 0.5 m - 2.3 \sqrt{(m + k) + (m + k + 1) 0.04} - 3 = -35 \text{ dBm}$$
+
+hence
+
+$$A_{f\max} = 19.5 - 0.5 m - 2.3 \sqrt{(m + k) + (m + k + 1) 0.04} \text{ dB}.$$
+
+7. The minimum value for $A_f$ is given by:
+
+$$-10.5 - A_{f\min} - 0.5 m + 2.3 \sqrt{(m + k) + (m + k + 1) 0.04} + 3 = -5 \text{ dB}$$
+
+hence
+
+$$A_{f\min} = -2.5 - 0.5 m + 2.3 \sqrt{(m + k) + (m + k + 1) 0.04} \text{ dB}.$$
+
+According to Recommendation Q.457, the maximum number of 4-wire links with *international* characteristics is $m = 4$ .
+
+The maximum number of national 4-wire extension links is $k = 4$ .
+
+# SECTION 5
+
+## SIGNALLING PROCEDURES
+
+A major characteristic of System R2 is the inherent flexibility in the interregister signalling procedures which allow efficient signal information transfer, adapted to the particular requirements relating to different call types, traffic conditions and switching equipments. This flexibility is primarily achieved by the principle that the interregister signalling sequence is controlled by the incoming R2 register by means of backward signal.
+
+In this context the function of an outgoing R2 register is basically to respond with the forward signal requested by the incoming R2 register. At the incoming R2 register the determination of the backward signal to be sent, thus controlling the signalling sequence, is closely related to the analysis necessary to determine the routing and handling of the call.
+
+In this Section the signalling procedures are specified. Although System R2 in principle allows a high degree of freedom in the combination of these procedures within the signalling sequence for call set-up, the procedures to be used for normal international calls connected via terrestrial links are described below. These procedures may vary when a satellite link is employed in a connection because the register at the incoming end of a satellite link also acts as an outgoing R2 register (see Recommendation Q.440, § 4.1.1). For national application of System R2 the signalling sequences to be applied have to be defined in accordance with the limitations of the present specifications by the Administration concerned.
+
+###### **Recommendation Q.460**
+
+### **5.1 NORMAL CALL SET-UP PROCEDURES FOR INTERNATIONAL WORKING**
+
+#### **5.1.1 *General***
+
+During call set-up an outgoing international R2 register is connected to an international link. This register signals to at least one incoming R2 register situated in an international exchange and possibly, depending upon the routing, to as many as 4 successive incoming R2 registers in international exchanges and 4 successive incoming R2 registers situated in national exchanges in the destination country where System R2 is employed.
+
+The duration of the normal call set-up procedure can vary because different phases of the signalling sequence between the outgoing international R2 register and successive incoming R2 registers may be repeated.
+
+#### **5.1.2 SIGNALLING BETWEEN THE OUTGOING INTERNATIONAL R2 REGISTER AND AN INCOMING R2 REGISTER IN AN INTERNATIONAL EXCHANGE**
+
+The address signals from an operator or a subscriber must be stored in an outgoing international R2 register. When a sufficient number of digits is available an outgoing link is selected and a seizing (line) signal is sent. When the seizing signal is recognized an incoming R2 register is associated with the link.
+
+Immediately the outgoing link is seized the outgoing international R2 register sends the first interregister signal.
+
+##### *5.1.2.1 Signalling to an international transit exchange*
+
+When the outgoing link is to an international exchange from which a transit routing is required to the destination country, the first interregister signal sent is a country code indicator. This is one of signals I-11, I-12, I-14 depending upon the requirement for echo suppressors (see Recommendation Q.479).
+
+On recognition of a country code indicator the incoming R2 register determines that the call is to be internationally transit switched. The incoming R2 register sends signal A-1 when it requests the first digit of the country code. The outgoing international R2 register sends this address digit (a signal I-1 to I-10). The incoming R2 register may send signal A-1 to request the next digit.
+
+The incoming R2 register examines the address digit(s) and if a further digit (or digits) is required for routing, signal A-1 is sent to request the next digit.
+
+When sufficient digits are stored at the incoming exchange to permit the call to be routed to the next exchange, the backward signal is determined by the nature of the signalling system employed on the outgoing link.
+
+a) If the outgoing link employs System R2, one of two backward signals is sent immediately the outgoing link is seized:
+
+i) If the outgoing link is to another international transit exchange from which a transit routing is required to the destination country, signal A-11 is sent to request repetition of the country code indicator.
+
+On recognition of signal A-11 the outgoing international R2 register sends a country code indicator as the first signal to be received by the incoming R2 register in the next international transit exchange. This is one of signals I-12 or I-14. If signal I-11 was sent initially, signal I-14 is sent subsequently.
+
+On recognition of a country code indicator the incoming R2 register determines that the call is to be internationally transit switched. The signalling procedure which follows is identical to that described above.
+
+ii) If the outgoing link is to an incoming international exchange in the destination country, signal A-12 is sent to request a language or discriminating digit.
+
+In both these cases after the backward signal is sent and the compelled signalling sequence is complete, the transit exchange releases the incoming R2 register and through-connects the speech-path between the outgoing exchange and the next exchange.
+
+b) If the outgoing link employs a signalling system other than System R2, then the acting incoming R2 register is the last incoming R2 register. The exchange seizes an outgoing international link to a further international transit exchange or an incoming international exchange in the destination country. Signalling continues between the outgoing international R2 register and the last incoming R2 register and interworking takes place with the other signalling system.
+
+If congestion is encountered signal A-15 is sent, if necessary in pulse form. After the compelled signalling sequence is complete or after the end of the pulse signal the transit exchange dismisses the register.
+
+On recognition of signal A-15 the outgoing exchange may initiate a repeat attempt, a re-routing or cause the return of congestion information to the calling subscriber. In all cases the outgoing (multi-)link section is released.
+
+##### 5.1.2.2 *Signalling to an incoming international exchange in the destination country*
+
+When the outgoing international link is a direct link to an incoming international exchange in the destination country the first interregister signal sent is a language or discriminating digit.
+
+Alternately, if the outgoing multi-link section is routed via one, two or three international transit exchanges then on recognition of signal A-12 the outgoing international R2 register sends a language or discriminating digit as the first signal to be received by the incoming R2 register in the terminal international exchange in the destination country.
+
+The first signal A-12 received from an international transit exchange by the outgoing international R2 register informs it that an international link terminating at an incoming international exchange has been added to the (multi-)link section.
+
+In both cases, on recognition of a language or discriminating digit (a signal I-1 to I-10), the incoming R2 register determines that the call is to be routed to the national network, and selects the next backward signal:
+
+- i) The incoming R2 register may send signal A-14 to request information about the requirement for echo suppression.
+ - If an incoming half-echo suppressor is required the outgoing international R2 register sends signal I-14.
+
+In response to signal I-14 the incoming R2 register sends signal A-1 to request the first digit of the national (significant) number. In response to signal A-1 the outgoing international R2 register sends the first digit of the national (significant) number.
+ - If no echo suppressor is required the outgoing international R2 register sends the first digit of the national (significant) number.
+- ii) Alternatively, if it is known that no echo suppressor is required to be inserted the incoming R2 register may send signal A-1 to request the first digit of the national (significant) number. In response to signal A-1 the outgoing international R2 register sends the first digit of the national (significant) number.
+
+The incoming R2 register examines the first digit of the national (significant) number and if a further digit (or digits) is required for routing, signal A-1 is sent to request the next digit.
+
+When sufficient digits are stored at the incoming exchange to permit the call to be routed to the next exchange the backward signal (if any) is determined by the nature of the signalling system employed on the outgoing link and the national routing principles.
+
+- a) If the outgoing national link employs System R2 and international/national end-to-end signalling is used, a backward signal may be sent after the outgoing link is seized to request the address digit required as the first signal to be received by the incoming R2 register in the following national exchange.
+
+The appropriate signal is one of signals A-1, A-2, A-7, A-8 or A-12. These signals may be sent after any digit, and can be repeated provided they do not conflict with the logic procedure.
+
+However, if the address digit *on-line* is the digit required as the first signal to be received by the incoming R2 register in the next exchange, it is possible for the transit exchange to release the incoming R2 register and through-connect the speech-path after the outgoing link is seized without sending a backward signal.
+
+Otherwise, after the appropriate backward signal is sent and the compelled signalling sequence is complete the transit exchange releases the register and through-connects the speech path.
+
+- b) If the outgoing national link employs System R2 but end-to-end international/national signalling cannot be used, the register in the incoming international exchange relays the multifrequency signals: it acts as an outgoing R2 register. It requests the remainder of the address digits by repetitive use of signal A-1. The digits received by the outgoing R2 register are retransmitted over the outgoing national link at the request of the incoming R2 register in the following national exchange(s) (see Recommendation Q.478).
+- c) If the outgoing link employs a signalling system other than System R2 then the acting incoming R2 register is the last incoming R2 register. The exchange seizes a national link. Signalling continues between the outgoing international R2 register and the last incoming R2 register and interworking takes place with the other signalling system.
+
+If congestion is encountered, congestion signal A-4 or A-15 is transmitted (if necessary in pulse form) and the incoming R2 register is dismissed.
+
+On recognition of the congestion signal A-4 the outgoing exchange releases the outgoing link or connection and causes the return of congestion information to the calling subscriber.
+
+On recognition of the congestion signal A-15 the outgoing exchange may initiate a repeat attempt, re-routing or cause the return of congestion information to the calling subscriber. In all cases the outgoing link or connection is released.
+
+It is desirable to use the congestion signal A-15 solely in the case of incoming international terminal traffic when repeat attempt or re-routing may be expected to be successful.
+
+##### **Recommendation Q.463**
+
+#### **5.1.3 SIGNALLING BETWEEN THE OUTGOING INTERNATIONAL R2 REGISTER AND AN INCOMING R2 REGISTER IN A NATIONAL EXCHANGE IN THE DESTINATION COUNTRY**
+
+##### *5.1.3.1 Signalling to a national transit exchange*
+
+The outgoing international R2 register sends the requested address digit as the first signal to be received by the incoming R2 register in the national transit exchange in the destination country.
+
+The incoming R2 register examines the digit and if a further digit (or digits) is required for routing, signal A-1 is sent to request the next digit.
+
+When sufficient digits are stored at the incoming exchange to permit the call to be routed to the next exchange the backward signal (if any) is determined by the nature of the signalling system employed on the outgoing link and the national routing principles.
+
+- a) If the outgoing national link employs System R2 a backward signal may be sent after the outgoing link is seized to request the address digit required as the first signal to be received by the incoming R2 register in the next exchange. The signalling procedure which occurs is similar to that described in § 5.1.2.2 a) above.
+- b) If the outgoing link employs System R2 but end-to-end international/national signalling cannot be used, the register in the national exchange relays the interregister signals: it acts as an outgoing R2 register. The digits received by this outgoing R2 register are retransmitted over the outgoing link at the request of the incoming R2 register in the following exchange(s) (see Recommendation Q.478).
+- c) If the outgoing link employs a signalling system other than System R2 then the acting incoming R2 register is the last incoming R2 register. The exchange seizes an outgoing national link to the next national exchange. Signalling continues between the outgoing international R2 register and the last incoming R2 register and interworking takes place with the other signalling system.
+
+If congestion is encountered signal A-4 is sent (if necessary in pulse form) and the incoming R2 register is released.
+
+On recognition of congestion signal A-4 the outgoing exchange releases the outgoing multi-link section and causes the return of congestion information to the calling subscriber.
+
+##### *5.1.3.2 Signalling to a national exchange to which the called subscriber is connected*
+
+When the outgoing multi-link section is routed to the national exchange to which the called subscriber is connected the acting incoming R2 register is the last incoming R2 register: the outgoing international R2 register sends the requested address digit as the first signal to be received by the last incoming R2 register and signalling continues as described below.
+
+#### **5.1.4 SIGNALLING BETWEEN THE OUTGOING INTERNATIONAL R2 REGISTER AND THE LAST INCOMING R2 REGISTER**
+
+##### **5.1.4.1 *General***
+
+The usual System R2 signalling procedure is to request in succession the remainder of the address digits stored in the outgoing international R2 register by the repetitive use of signal A-1 until it is determined at the incoming end that the complete address information has been received by the incoming exchange or that the call cannot be routed.
+
+System R2 enables transmission of information concerning a large number of different conditions of called subscriber's line or reasons why call set-up has failed. But this can only be sent if the switching systems and other signalling systems employed on the remaining links of the connection offer the possibility of differentiating several line conditions. Group B-signals are provided for this purpose.
+
+Transition from Group A to Group B meanings is indicated by means of address-complete signal A-3. However, if the incoming exchange is unable to send any signals concerning the condition of the called subscriber's line it is unnecessary to send signal A-3 followed by a Group B signal. In such cases the address-complete signal A-6, provided for the purpose is used.
+
+If congestion is encountered after transmission of the address-complete signal A-3 the congestion signal B-4 is sent in place of signal A-4 or A-15.
+
+##### **5.1.4.2 *When the last incoming R2 register is able to transmit the condition of the called subscriber's line***
+
+When the condition of the called subscriber's line can be determined the incoming R2 register can send signals conveying this information after receipt of the address digits.
+
+As soon as the last address digit is received the last incoming R2 register sends the address-complete signal A-3 to announce changeover to the transmission of Group B signals. In response the outgoing international R2 register sends the appropriate calling party's category signal (II-7 to II-10). The last incoming R2 register acknowledges this with the relevant Group B signal indicating the condition of the called subscriber's line.
+
+Immediately the compelled signalling sequence is complete the incoming R2 register is released and depending upon the Group B signal sent the speech-path may be through-connected.
+
+When the condition of the called subscriber's line is determined by an electrical signal to the last incoming R2 register and if the called subscriber's line is free the address-complete signal A-6 can be sent instead of signal A-3, possibly in pulse form. This will be the last interregister signal. After signal A-6 is sent the incoming R2 register is released, the speech-path is through-connected and ringing tone returned to the calling subscriber. Outgoing inter-national R2 registers must be able to interpret all Group B signals.
+
+On recognition of the last backward signal the outgoing exchange releases the outgoing international R2 register and either through-connects the speech-path or releases the outgoing connection and causes the return of an appropriate tone or special announcement or both alternately to the calling subscriber.
+
+##### **5.1.4.3 *When the last incoming R2 register is not able to transmit the condition of the called subscriber's line***
+
+In this case the last incoming R2 register sends the address-complete signal A-6, possibly in pulse form, as the last interregister signal. After this is sent, the last incoming R2 register is released and the speech-path is through-connected.
+
+When the last incoming R2 register is in the exchange to which the called subscriber is connected, an appropriate tone is returned to the calling subscriber from this exchange.
+
+On recognition of address-complete signal A-6, the outgoing exchange releases the outgoing international R2 register and through-connects the speech-path. The calling subscriber will then hear ringing tone, busy tone, special information tone or a recorded announcement alternately with special information tone sent by the incoming equipment.
+
+#### **5.1.5 PARTICULAR CASES**
+
+##### **5.1.5.1 *Unallocated number***
+
+When, after the reception of any digit, the incoming R2 register determines that the address information corresponds to an unallocated number, the address-complete signal A-3 is sent immediately without requesting all the address digits. In response the outgoing international R2 register sends the appropriate Group II signal. This is then acknowledged by signal B-5 *unallocated number*.
+
+##### **5.1.5.2 *Congestion in the national network***
+
+If congestion is encountered in the national network the incoming R2 register sends congestion signal A-4, possibly in pulse form. However, if address-complete signal A-3 has already been sent, congestion signal B-4 is sent in acknowledgement of the Group II signal which commences the last compelled signalling sequence.
+
+##### **5.1.5.3 *Operator calls***
+
+The procedures described in Recommendations Q.462-Q.464 are also valid for a semi-automatic call. However, in this case the address information is always terminated by the end-of-pulsing signal I-15.
+
+For code 11 or code 12 calls only a limited number of backward signals can be employed as the last interregister signal (e.g. signal A-4, A-6 or B-6).
+
+##### **5.1.5.4 *Request of calling party's category***
+
+At any time calling party's category information may be requested by the incoming R2 register interrupting the normal transmission of address information. The incoming R2 register sends signal A-5 in acknowledgement of a Group I signal and the outgoing international R2 register sends the appropriate Group II signal (a signal II-7 to II-10) in reply. If this Group II signal is acknowledged by a signal different from address-complete signal A-3 or signal A-5 the next forward signal sent will be one of the Group I.
+
+#### **5.1.6 SUPERVISION AND RELEASE OF THE CALL**
+
+An answer signal is sent when the called subscriber's off-hook condition is detected. Each transit exchange in the connection, relays this line signal. At the outgoing international exchange, receipt of the answer signal normally causes call charging to take place and metering for international accounting purposes to start.
+
+When the called subscriber's on-hook condition is detected a clear-back signal is sent and relayed by each transit exchange.
+
+When the calling subscriber's on-hook condition is detected a clear-forward signal is relayed by the outgoing international exchange over the outgoing international link. On receipt of the clear-forward signal on an incoming link, release operations are initiated and the clear-forward signal is repeated forward on the outgoing link.
+
+Immediately release operations at an exchange are complete (although the outgoing circuit may still be held) a release-guard sequence is initiated on the incoming link. After recognition of the end of the release-guard sequence at the outgoing exchange the link reverts to the idle state.
+
+Supervision of a call must be in accordance with Recommendation Q.118.
+
+### **5.2 ROUTING AND NUMBERING FOR INTERNATIONAL WORKING**
+
+(See Recommendations Q.107 and Q.107 *bis*, Fascicle VI.1)
+
+### **5.3 TERMINATION OF INTERREGISTER SIGNALLING**
+
+#### **5.3.1 AT AN INCOMING R2 REGISTER SITUATED IN A TRANSIT EXCHANGE**
+
+##### **5.3.1.1 *Successful routing***
+
+Normally, interregister signalling is terminated in one of the following ways:
+
+- a)* The last forward interregister signal received by the incoming R2 register at the transit exchange is not acknowledged from that register. After an outgoing link to the next exchange is seized, the register is dismissed and the speech-path is through-connected. The forward signal remains on-line and is the first signal received by the next incoming R2 register. Provision must be made for the switching operations to be completed so as to ensure that the signal will remain on-line and be received by the succeeding register.
+- b)* The last forward interregister signal received by the incoming R2 register at the transit exchange is acknowledged by a backward signal (A-1, A-2, A-7, A-8, A-11 or A-12) requesting transmission of a clearly specified signal as the first to be received by the next incoming R2 register. When the compelled signalling sequence is complete the register is dismissed and the speech-path is through-connected.
+
+Because it is not possible to send signals A-2, A-7, A-8, A-11 or A-12 in pulse form, precautions are necessary to avoid acknowledging the last address digit (on automatic calls) until the signalling system employed on the outgoing link is known. If signal A-1 is sent in acknowledgement of the last address digit and if the outgoing link employs System R2 it may not then be possible to send one of these signals and therefore end-to-end signalling to the next exchange is no longer feasible (see also Recommendation Q.474).
+
+In international working signals A-2, A-7 and A-8 may be used to acknowledge receipt of any forward signal.
+
+Signal A-11 must be used to request a country code indicator.
+
+Signal A-12 must generally be used to request the language or discriminating digit. However, in the case where an incoming R2 register is equipped with only 5 backward signalling frequencies only one of the signals A-2, A-7 or A-8 can be used for this purpose. Attention is drawn to the fact that in this case the language or discriminating digit may not be sent by all outgoing international R2 registers.
+
+Although it is not normally necessary to request a repeat of a digit *n* because it remains on the line until acknowledged (but see Recommendation Q.476) such repetition may prove necessary after an interruption of digit transmission (e.g. to request information concerning the calling party's category) or if the completion of switching operations referred to in method *a)* above, cannot be guaranteed with a time compatible with the time-out of the outgoing (international) R2 register (see Recommendation Q.476). The procedure is then as follows:
+
+Signal A-2 is sent, eliciting the digit *n-1*; this is immediately acknowledged by signal A-1 to elicit the required digit *n*. When the digit *n* in question is the first digit in the store of the outgoing R2 register this procedure is not applicable.
+
+At an international transit exchange method *b*) above, must be used and only one of the signals A-11 or A-12 applies.
+
+When the outgoing link connects to a further international transit exchange signal A-11 must be used to request a country code indicator. On recognition of signal A-11 the outgoing international R2 register must send a country code indicator (signal I-12 or I-14, see Recommendation Q.479) as the first forward signal to be received by the next incoming R2 register.
+
+Signal I-12 or I-14 may be requested as many times as necessary by sending signal A-11.
+
+When the outgoing link connects to an incoming international terminal exchange signal A-12 must be used to request the language or discriminating digit. On recognition of signal A-12 the outgoing international R2 register must send the language or discriminating digit (a signal I-1 to I-10) as the first forward signal to be received by the next incoming R2 register.
+
+On recognition of signal A-12 (sent from an international transit exchange) an outgoing international R2 register is informed that an international link connected to an incoming international terminal exchange has been added to the (multi-)link section and that call set-up is now in progress in the national destination network. This is of importance when signal A-9 or A-10 are, in the originating country, amongst those used to set-up international calls.
+
+##### 5.3.1.2 *Congestion*
+
+If it is impossible to set-up the desired connection in the transit exchange the incoming R2 register terminates interregister signalling by transmission of the congestion signal A-4 or A-15. The backward signal may serve as acknowledgement of the last forward signal received by the incoming R2 register at the transit exchange or is sent in pulse form.
+
+The two congestion signals A-4 and A-15 are provided to enable an outgoing international R2 register to determine whether congestion is occurring in the international network or in that of the destination country so that provision for repeat attempt or re-routing can be made in the former case:
+
+- Signal A-15 is sent from an international exchange.
+- Signal A-4 is sent from a national exchange or possibly from a terminal international exchange. [See also § 5.1.2.2 c).]
+
+Because receipt of congestion signal A-15 by an outgoing international R2 register may initiate repeat attempt or re-routing it is possible to transmit congestion signal A-4 from international exchanges where repeat attempt or re-routing may be expected useless.
+
+###### **Recommendation Q.471**
+
+#### **5.3.2 AT THE LAST INCOMING R2 REGISTER SITUATED IN THE EXCHANGE TO WHICH THE CALLED SUBSCRIBER IS CONNECTED**
+
+##### *5.3.2.1 Successful routing*
+
+When a call has been completely set up by means of System R2 interregister signalling, the incoming R2 register terminates interregister signalling immediately on receipt of the entire number.
+
+The following criteria are used to determine whether the number received by the incoming R2 register is complete:
+
+- a*) analysis – to determine the last digit;
+- b*) electrical conditions given by the switching equipment succeeding the incoming R2 register;
+
+- c) receipt of the end-of-pulsing signal (I-15);
+- d) the assumption, after a specified time has elapsed, that no further digits will be sent (see Recommendation Q.476).
+
+When criterion *a*) (analysis) is applied:
+
+- if the incoming R2 register is equipped to send Group B signals to provide information about the condition of the called subscriber's line the address-complete signal A-3 is transmitted on receipt of the last digit. As soon as it is known whether the connection with the subscriber's line can be established, only the appropriate Group B signal needs to be sent. The use of the Group B signals is detailed in Recommendation Q.474;
+- if the incoming R2 register is not equipped to receive information about the condition of the called subscriber's line, the address-complete signal A-6 is sent immediately after reception, of the last digit and no Group B signal will be transmitted.
+
+In both cases the time interval between the end of a signal A-6 or a Group B signal and the start of the subsequent answer signal must not be less than 75 ms.
+
+When criterion *b*) (electrical conditions) is applied:
+
+It is recommended that, to avoid delay in sending the answer signal, no Group B signal should be sent when the called subscriber's line is free, and that the setting-up of speech conditions be ensured by sending address-complete signal A-6 immediately the electrical conditions are recognized. The time interval between the end of signal A-6 and the start of transmission of the subsequent answer signal must be not less than 75 ms (see also Recommendations Q.412 and Q.475).
+
+Criterion *c*) (end-of-pulsing) can be applied only if the incoming R2 register is equipped to receive the 6 forward signalling frequencies (see also Recommendation Q.473). When signal I-15 is received and recognized the last incoming R2 register can perform in the way described under criterion *a*).
+
+When criterion *d*) (time-out) is applied:
+
+Address-complete signal A-6 must be sent in pulse form as soon as the specified time has elapsed. The time between the end of signal A-6 and the start of transmission of the subsequent answer signal must be, as indicated above for criterion *b*), not less than 75 ms (see also Recommendations Q.412 and Q.472).
+
+It may happen, however, that the called subscriber answers before the specified time has elapsed. In such exceptional circumstances the pulse signal A-6 must be sent immediately the answer signal is recognized. In this case the time between the end of signal A-6 and the start of the transmission of the subsequent answer signal must be 75 ms or more but less than 150 ms. The calling subscriber will not hear the ringing tone.
+
+This disadvantage can be avoided by not using a received digit to set up the call until after the following digit has been received or until a certain time has elapsed. This procedure, however, may give rise to difficulties if the time-out devices provided in the switching equipment succeeding the incoming R2 register are set for too short a delay [see also Recommendation Q.120, § 1.5.5.2 b) iv)].
+
+##### 5.3.2.2 Congestion
+
+An incoming R2 register should terminate interregister signalling immediately any conditions preventing complete setting-up of a call have been recognized.
+
+If congestion is encountered congestion signal A-4 is sent, possibly in pulse form. However if address-complete signal A-3 has already been sent then congestion signal B-4 is sent in acknowledgement of the Group II signal which commences the last compelled signalling sequence.
+
+#### **5.3.3 AT THE LAST INCOMING R2 REGISTER SITUATED IN A TRANSIT EXCHANGE**
+
+##### **5.3.3.1 *Successful routing***
+
+Interregister signalling to such a register can be terminated after all the address digits are received. In order to determine that the number is complete the same criteria as described in Recommendation Q.471 are used.
+
+When criterion *a)* (analysis) is applied:
+
+- 1) if the signalling system employed on the outgoing link enables the condition of the called subscriber's line to be sent backwards within an acceptable period compared to the time-out of the outgoing international R2 register, the last incoming R2 register can react in accordance with one of the following methods:
+ - i) address-complete signal A-3 is sent in acknowledgement of the last address digit followed by the relevant Group B signal depending upon the condition of the called subscriber's line;
+ - ii) signal A-1 is sent in acknowledgement of the last address digit, and signal I-15 if received, to deliberately suspend compelled signalling and later,
+ - when the condition of the called subscriber's line is known, address-complete signal A-3 is sent in pulse form followed by the relevant Group B signal. This makes it possible to avoid maintaining on-line the Group II signal sent after reception of signal A-3,
+ - when the called subscriber's line is free, it is preferable to send the address-complete signal A-6 in pulse form,
+- 2) if the signalling system employed on the outgoing link does not enable the condition of the called subscriber's line to be transmitted backwards or if such information is only available at the last incoming R2 register after a delay incompatible with the time-out of the outgoing international R2 register, then address-complete signal A-6 is sent in acknowledgement of the last address digit.
+
+When criterion *b)* (electrical conditions) is applied:
+
+Only signal A-1 can be used to acknowledge each address digit. Upon receipt of an electrical signal on the outgoing link, the last incoming R2 register acts in one of the following ways:
+
+- if the condition of the called subscriber's line is not known or is known to be *free*, address-complete signal A-6 is sent in pulse form;
+- if the condition of the called subscriber's line is known to be other than *free*, address-complete signal A-3 is sent in pulse form, followed by the relevant Group B signal.
+
+Criterion *c)* (end-of-pulsing) is only applicable if the last incoming R2 register can receive 6 forward signalling frequencies (see also Recommendation Q.473). In this case, when end-of-pulsing signal I-15 is received and recognized, the last incoming R2 register can perform in the way described under criterion *a)*.
+
+When criterion *d)* (time-out) is applied:
+
+Address-complete signal A-6 is sent in pulse form after the specified time has elapsed (see Recommendation Q.476).
+
+##### **5.3.3.2 *Congestion***
+
+If congestion is encountered, the procedure described in Recommendation Q.470 is followed. However, if address-complete signal A-3 has already been sent then congestion signal B-4 is sent in acknowledgement of the Group II signal which commences the last compelled signalling cycle.
+
+#### **5.3.4 USE OF END-OF-PULSING SIGNAL I-15 IN INTERNATIONAL WORKING**
+
+In international working, the end-of-pulsing signal I-15 is used in accordance with Recommendation Q.468. Signal I-15 (end-of-pulsing) is sent immediately after the last digit.
+
+In national working, signal I-15 may be used too.
+
+In semi-automatic operation, calls to operators' positions are always terminated by transmission of signal I-15. This signal can only be interpreted if the incoming R2 register is equipped for reception of 6 forward frequencies. However, when an incoming R2 register is equipped for reception of only 5 forward signalling frequencies no provision can be made for recognition of signal I-15. Such an incoming R2 register will then act as though signal I-15 had not been sent. Consequently the next interregister signal is only one of the signals A-3, A-4 or A-6 sent in pulse form.
+
+##### *5.3.4.1 Procedures to be followed after receipt of end-of-pulsing signal I-15 by the last incoming R2 register (situated in a transit exchange or in the exchange to which the called subscriber is connected)*
+
+Incoming R2 registers equipped for the reception of all 6 forward signalling frequencies can acknowledge receipt of the end-of-pulsing signal I-15 by sending an appropriate backward signal to complete the compelled signalling cycle. Interregister signalling is terminated according to the procedures specified in Recommendations Q.471 or Q.472 when criterion *a*) (analysis) is applied.
+
+In particular, if the last incoming R2 register acknowledges signal I-15 with signal A-1 the outgoing international R2 register will not send any signal and the incoming R2 register can only send one of signals A-3, A-4, A-6 or A-15 in pulse form.
+
+Since there is no compulsion to equip incoming R2 registers in national exchanges with receivers for all 6 forward signalling frequencies, the signal I-15 sent by an outgoing international R2 register may not be recognized by the incoming R2 register. In such cases other criteria can be used to determine whether the number received by the incoming R2 register is complete.
+
+When the incoming R2 register determines that the number received is complete using criteria other than *c*) (end-of-pulsing) it may be that the last digit of the subscriber number is acknowledged by signal A-3, A-4, A-6 or A-15. In this case interregister signalling is terminated without request for the signal I-15, in the normal way according to the procedures specified in Recommendations Q.471 or Q.472 (a compelled signalling cycle including signal I-15 is saved).
+
+##### *5.3.4.2 Procedure to be followed after receipt of signal I-15 by an incoming R2 register situated in a transit exchange*
+
+Signal A-1, A-2, A-7, A-8, A-11 or A-12 may be sent in acknowledgement of signal I-15 (end-of-pulsing). However, at a transit exchange precautions are necessary to avoid acknowledgement of signal I-15 before the signalling system employed on the outgoing link has been identified. If signal A-1 is sent in acknowledgement of signal I-15 and if the outgoing link employs System R2, it is not then possible to send backward signal A-2, A-7, A-8, A-11 or A-12 after the end of the compelled signalling cycle because these signals cannot be sent in pulse form. Therefore end-to-end signalling to the next exchange is no longer possible.
+
+#### **5.3.5 USE OF GROUP B SIGNALS**
+
+Group B signals are used to transmit information about the condition of switching equipment in the incoming exchange or the called subscriber's line, to the outgoing international R2 register, which can then take the necessary action.
+
+The address-complete signal A-3 is sent by an incoming R2 register to announce changeover to sending Group B signals. In addition, signal A-3 indicates that the incoming R2 register has received all the Group I forward signals it requires from the outgoing international R2 register. On recognition of signal A-3 an outgoing R2 register sends a Group II signal. The incoming R2 register may interpret the Group II signal giving information about calling party's category, in order to control the switching operations accordingly (e.g. suppression of automatic ringing for operator initiated calls or to prevent subscriber access to data transmission terminals). Finally, a Group II forward signal is acknowledged by any Group B backward signal.
+
+In cases where outgoing R2 registers are able to interpret all Group B signals there is generally no need to provide equipment at the incoming end able to send, in addition to Group B signals, the tones and/or announcements corresponding to those signals, except in the case of ringing tone.
+
+In general, outgoing R2 registers must be equipped with devices permitting, after reception of signal A-3:
+
+- the exchange of an additional cycle of interregister signals before the register is released;
+- changeover from Group A to Group B meanings of backward signals.
+
+Outgoing international R2 registers, however, must be able to interpret all Group B signals.
+
+##### *5.3.5.1 Procedures to be followed by an outgoing international R2 register on receipt of Group B signals*
+
+Signal B-1 is interpreted by an outgoing international R2 register as signal B-6: the register is released and the speech-path is through-connected. A subsequent answer signal initiates call charging.
+
+Signal B-2 send special information tone is sent by the incoming R2 register:
+
+- when the number of the called party has been changed,
+- when the three following conditions are fulfilled together:
+ - i) the called party's line condition does not fit with one of the meanings of the present Group B signals,
+ - ii) it does not lead to setting up the speech path,
+ - iii) it is not incompatible with return of special information tone to the calling party.
+
+After recognizing signal B-2, the outgoing international R2 register clears forward and causes the transmission of only special information tone.
+
+The subscriber's line busy signal B-3 is sent by the incoming register when the called subscriber's line is engaged. On recognition of this signal, the outgoing register releases the connection and causes transmission of the busy tone.
+
+When the congestion condition is encountered following the changeover from Group A signals to Group B signals, the congestion signal B-4 shall be transmitted on the conditions specified for congestion signal A-4. In all cases recognition of the signal causes release of the call and transmission of congestion information.
+
+After recognizing unallocated number signal B-5, the outgoing international R2 register clears the call and causes transmission of special information tone or a recorded announcement and special information tone, alternately, to the calling party.
+
+After recognizing signal B-6, the outgoing international R2 register sets up speech conditions so that a caller may hear the ringing tone. In this case, a subsequent answer signal activates the call-charging mechanism.
+
+After recognizing signal B-7 the outgoing international R2 register sets up speech conditions, so that a caller may hear the ringing tone. In this case, a subsequent answer signal does not activate the call-charging mechanism. However, in an outgoing international R2 register signal B-7 may be interpreted as B-6 if there is no international agreement on non-chargeable calls.
+
+After recognizing signal B-8 subscriber's line out of order, the outgoing international R2 register clears forward and causes the transmission of a special information tone or recorded announcement and special information tone alternately to the calling party.
+
+Receipt of signal B-9 or B-10 by an outgoing international R2 register causes release of the outgoing connection and return of special information tone to the calling subscriber, i.e. these signals should be interpreted as signal B-2.
+
+If an outgoing international R2 register receives one of signals B-11 to B-15 the call should be released and indication of this returned to the calling subscriber or operator, i.e. this signal should be interpreted as signal B-4.
+
+##### 5.3.5.2 *Special procedures for national working*
+
+Outgoing R2 registers in national exchanges may not be able to recognize and interpret Group B signals. In such networks it is essential that the equipment at the incoming end must transmit not only the Group B signals but also the corresponding tones and/or announcements, when the incoming R2 register does not know whether the outgoing R2 register is capable of interpreting Group B signals.
+
+In the case where the incoming R2 register is able to make only two or three distinctions of conditions of the called subscriber's line the following procedure may be adopted: When the only distinction that can be made is between subscriber's line free and subscriber's line engaged,
+
+- i) signal B-3 is sent if the line is engaged;
+- ii) otherwise signal B-6, or signal A-6 alone is sent so the caller can hear the ringing tone sent by the incoming equipment.
+
+In the case where outgoing R2 registers in national exchanges are only able to interpret a limited number of Group B signals or are indeed not able to interpret any, it is essential that such equipment be able to respond to signal A-3 in the specific manner and at least to recognize the next backward signal (which is a Group B signal) as indicating the end of interregister signalling.
+
+##### 5.3.5.3 *Possible application of signal B-1 in national working*
+
+Signal B-1, for example, may be used to indicate that the call must remain under the control of the incoming equipment, insofar as this is possible (e.g. for maintenance reasons, to trace malicious calls, etc.). The incoming exchange sets up speech conditions, so that the calling subscriber can hear the ringing tone. At present such a use of signal B-1 in international working is not envisaged.
+
+##### **Recommendation Q.475**
+
+### **5.4 NORMAL RELEASE OF OUTGOING AND INCOMING R2 REGISTERS**
+
+An outgoing international R2 register must be released once it has received an appropriate backward interregister signal terminating the interregister signalling, or on receipt of a clear-forward (line) signal from the preceding link.
+
+An incoming R2 register must be released once it has accomplished the necessary switching control and terminated the interregister signalling required, or on receipt of a clear-forward (line) signal from the preceding link.
+
+The last recognized interregister signal preceding setting up of speech conditions will normally be a backward signal: e.g. address-complete signal A-6, subscriber's line free signals B-6 or B-7.
+
+The multifrequency combination receivers at the two ends must be disconnected before the switching equipment passes to the speech condition; this procedure eliminates any possibility of their operating or being held under the influence of speech or line signals. The following conditions regarding the duration of the various phases should be observed (see Figure 20/Q.475):
+
+- a) the multifrequency signalling equipment of the incoming R2 register must be disconnected within 30 ms after recognition of the end of transmission of the last backward signal;
+- b) the multifrequency signalling equipment of the outgoing R2 register must be disconnected within 30 ms after recognition of the end of the last backward signal;
+- c) at the outgoing exchange speech conditions must be set up between 30 and 60 ms after recognition of the end of the last backward signal. However, at the exchange where the outgoing international R2 register is situated, the setting-up of speech conditions depends upon the signalling system employed on the preceding link;
+- d) at the incoming exchange at least 75 ms must elapse between the end of transmission of the last backward signal and the setting up of speech conditions.
+
+
+
+Diagram illustrating the disconnection of multifrequency signalling equipment and switching to the speech position. It shows an 'Outgoing exchange' on the left and an 'Incoming exchange' on the right, connected by a line. The outgoing exchange has a switch (B) and a multifrequency signalling equipment (S) box. The incoming exchange has a switch (A) and a multifrequency signalling equipment (S) box. A timeline below the diagram shows the sequence of events: 'Reception of last backward multifrequency combination' at the outgoing exchange, followed by 'Opens B' (multifrequency signalling equipment disconnects) within <30 ms, and 'Closes C' (switching to speech position) between 30-60 ms. At the incoming exchange, 'Emission of last backward multifrequency combination' occurs, followed by 'Opens A' (multifrequency signalling equipment disconnects) within <30 ms, and 'Closes D' (switching to speech position) after >75 ms. A 'Tone' signal is shown being transmitted from the outgoing exchange to the incoming exchange. The diagram is labeled 'CCITT-49351'.
+
+T = transmission delay + recognition time for the disappearance of the last backward multifrequency combination
+ S = multifrequency signalling equipment (see Recommendation Q.451)
+
+Note – The same transmission delay is assumed for all signals.
+
+FIGURE 20/Q.475
+
+Disconnection of multifrequency signalling equipment and switching to the speech position
+
+### **5.5 ABNORMAL RELEASE OF OUTGOING AND INCOMING R2 REGISTERS**
+
+To limit the holding time of R2 registers, when interregister signalling is interrupted either by a fault or by any other cause, all R2 registers must be equipped with devices for continuous supervision of the time taken by the various phases of interregister signalling. The time-out delay of these devices must be as short as possible, but long enough not to interrupt normal operation.
+
+#### *5.5.1 Time-out of outgoing international R2 register*
+
+In an outgoing international R2 register, the intervals during which a forward multifrequency combination is transmitted and the intervals during which no such combination is transmitted are supervised separately.
+
+##### *5.5.1.1 Supervision during sending of forward multifrequency combinations*
+
+The lower limit of the time-out delay is a function of the time required for the switching procedures in a transit exchange.
+
+On this basis, the time-out delay is specified as $15 \pm 3$ seconds.
+
+The supervision device will start functioning at the beginning of the transmission of a forward multifrequency combination and be reset with the deactivation of the senders involved. It will start again at the beginning of the transmission of the next forward multifrequency combination.
+
+##### *5.5.1.2 Supervision during intervals when no forward multifrequency combination is being sent*
+
+The lower limit of the time-out delay is a function of:
+
+- a) the maximum permissible time interval between dialling of two successive digits by the subscriber;
+- b) the time-out delay specified for incoming R2 registers (see § 5.5.2 below).
+
+On this basis, the time-out delay is specified to be longer than 24 seconds (a longer delay and an upper limit may be specified by each Administration).
+
+If this specification is observed an incoming R2 register, which has acknowledged the last received digit with the signal A-1, is bound to be released before the supervision device of the outgoing international R2 register initiates the alarm condition.
+
+##### *5.5.1.3 Procedure to be followed if time-out occurs*
+
+If time-out occurs, the time supervision devices mentioned in §§ 5.5.1.1 and 5.5.1.2 above will bring about operations producing:
+
+- return of an appropriate signal and/or audible tone to inform the calling party,
+- release of the outgoing international R2 register and of the connection as far as the latter is not necessary for the above-mentioned operation.
+
+Fault recording equipment may start functioning and/or a delayed alarm may alert the technical staff.
+
+##### *5.5.1.4 Time-out of outgoing R2 register*
+
+It is recommended that the same principles outlined in §§ 5.5.1.1 to 5.5.1.3 above be applied by analogy to outgoing R2 registers.
+
+#### *5.5.2 Time-out of incoming R2 register*
+
+The time-out device shall supervise the interval elapsing between seizure of the register and recognition of the first forward multifrequency combination as well as the interval elapsing between the recognition of two successive multifrequency combinations in the forward direction.
+
+##### 5.5.2.1 Time-out delay
+
+The lower limit of the time-out delay is a function of:
+
+- a) the maximum permissible time interval between the recognition of 2 successive forward multifrequency combinations; this time interval may in certain cases be influenced by the maximum permissible time interval between dialling of 2 successive digits by the subscriber;
+- b) the maximum time required for setting-up the call under conditions which slow down the interregister signalling.
+
+In view of the desirability expressed in § 5.5.1.2 above that the incoming R2 register be released before expiry of the time-out delay specified for the outgoing international R2 register, an upper limit should be fixed as well.
+
+On this basis the time-out delay should be specified within the range of 8-24 seconds. A minimum delay of 15 seconds corresponding to the time-out delays in other CCITT standardized signalling systems is to be preferred.
+
+For incoming R2 registers using the criterion *d)* (time-out) indicated in Recommendation Q.471 to determine completion of the number, the time referred to there as the *specified time* may exceptionally be shorter than 8 seconds, but never less than 4 seconds.
+
+##### 5.5.2.2 Procedure to be followed if time-out occurs
+
+If time-out occurs, the time supervision device will bring about operations producing:
+
+- sending of a congestion signal (A-4 or A-15) in pulse form;
+- release of the incoming R2 register and other equipment in the incoming exchange;
+- on time-out of the initial digit:
+ - i) line signalling, analogue version: establishment of the blocked state on the incoming circuit until recognition of the clear-forward signal (see Recommendation Q.412, abnormal conditions);
+ - ii) line signalling, digital version: no further action required.
+
+Fault recording equipment may start functioning and/or a delayed alarm may alert the technical staff.
+
+##### Recommendation Q.478
+
+### 5.6 RELAY AND REGENERATION OF R2 INTERREGISTER SIGNALS BY AN OUTGOING R2 REGISTER IN A TRANSIT EXCHANGE
+
+When the overall multi-link connection is divided into end-to-end signalling sections, regeneration of R2 interregister signals is required by either an outgoing international R2 register or an outgoing R2 register (see Recommendation Q.440).
+
+There are three possible procedures for relaying interregister signals by an outgoing R2 register:
+
+- a) the outgoing R2 register acknowledges each signal received over the incoming link by transmitting the appropriate backward signal; this operation is independent of the operations entailed in retransmitting on the outgoing link;
+- b) the forward address signal with rank $n + 1$ is acknowledged on the incoming link as soon as the forward address signal with rank $n$ is acknowledged on the outgoing link;
+- c) as soon as a forward signal is received on the incoming link, a signal is sent on the outgoing link; the acknowledgement signal is sent on the incoming link only when such a signal has been received on the outgoing link.
+
+Methods *a*) and *b*) provide the most rapid transfer of information and are therefore the preferable methods of relaying the information necessary for setting up the call. It is essential, however, that the outgoing R2 register be provided with adequate storage capacity in the case of method *a*).
+
+Method *b*) can only be applied after method *a*).
+
+Method *c*) should be used for relaying information relating to the procedures for the termination of interregister signalling.
+
+The changeover from method *a*) or *b*) to method *c*) may require transmission of an address-complete signal A-3 in pulse form as indicated in Recommendation Q.442 (see Figure 21/Q.478).
+
+The procedure for disconnecting the multifrequency combination receivers and setting-up speech conditions for each link, incoming and outgoing, is given in Recommendation Q.475.
+
+When method *a*) or *b*) is used, the time-outs of the R2 registers associated with the first signalling section may expire if the signalling on the second signalling section is too slow. Relatively long time-outs are recommended (see Recommendation Q.476).
+
+*Note* – The use of signal A-3 on circuits with very long transmission delay, e.g. satellite circuits, for relaying such information (method *c*) may result in premature release in certain incoming local exchanges with very short time guard. The problem may be avoided if the outgoing R2 register immediately following the satellite link uses signal A-5 to obtain the calling party's category information previously to the receipt of signal A-3 from those incoming local exchanges.
+
+
+
+Diagram illustrating the sequence of interregister signals in an outgoing R2 register. The top part shows three R2 register blocks: 'Outgoing R2 register', 'Outgoing R2 register', and 'Incoming R2 register'. The bottom part is a timing diagram showing signal sequences. On the left (outgoing), signals 'Digit n', 'Digit n + 1', and 'Last digit' are shown as right-pointing arrows. Responses 'A-1' are shown as left-pointing arrows. A dashed line labeled 'A-3 (Pulse signal)' points from the outgoing side to the incoming side. Below it, 'Group II signal' and 'Group B signal' are shown as right-pointing arrows on the outgoing side, and 'Group II signal' and 'Group B signal' as left-pointing arrows on the incoming side. The diagram is labeled 'CCITT-49361'.
+
+FIGURE 21/Q.478
+
+Sequence of interregister signals in an outgoing R2 register when the incoming link employs System R2
+
+### **5.7 ECHO-SUPPRESSOR CONTROL – SIGNALLING REQUIREMENTS**
+
+#### **5.7.1 Introduction**
+
+Recommendations Q.42 and Q.115 give fundamental requirements with which the employment of echo suppressors must comply.
+
+There are two methods of connecting echo suppressors to a circuit. One method is by use of permanently connected echo suppressors and the other is by the insertion of echo suppressors from a pool, when required.
+
+In System R2 (see Recommendation Q.441) two forward signals (I-12 and I-14) and one backward signal (A-14) are provided to indicate whether or not an incoming half-echo suppressor (IHES) is required.
+
+A third forward signal (I-11) is also available for use by bilateral agreement to indicate that an outgoing half-echo suppressor (OHES) must be employed.
+
+The following principles must be taken into account.
+
+#### **5.7.2 Principles of echo-suppressor control**
+
+5.7.2.1 The outgoing international exchange may be able to determine the need for echo suppressors in the connection by analysing the received country code.
+
+5.7.2.2 In direct traffic between 2 countries the use of echo suppressors generally takes place according to fixed rules. Echo-suppressor control signalling is not, therefore, necessary in these cases unless it is applied for the sake of uniformity.
+
+5.7.2.3 In international transit traffic the outgoing half-echo suppressor (OHES) will normally be employed at the outgoing international exchange, and the incoming half-echo suppressor (IHES) at the incoming international exchange, unless other arrangements are agreed upon with the Administration of the international transit exchange(s) (see § 5.7.2.5 below).
+
+However, in cases where an outgoing satellite link is selected by a transit exchange without the knowledge of the outgoing international exchange, the signal I-12 may be sent over the satellite link. In such cases half-echo suppressors are required and will normally be permanently fitted at each end of the satellite link.
+
+5.7.2.4 An incoming international exchange, equipped for the connection of IHES, must ask the outgoing international exchange whether or not an IHES must be employed unless this is known from other criteria (e.g. line classification). It will do this by sending the backward signal A-14 as an acknowledgement of the discriminating or language digit (Z-digit).
+
+When a satellite link is used in the connection the exchange situated at the incoming end of the satellite link responds to the A-14 signal instead of the outgoing international exchange (see Recommendation Q.7).
+
+5.7.2.5 It may be agreed upon bilaterally that in international transit traffic the OHES (IHES) will not be employed in the outgoing (incoming) international exchange, but in the international transit exchange, e.g. in the case where most of the traffic on the circuit group between the outgoing exchange and the transit exchange (between the transit exchange and the incoming exchange) needs no echo-suppressor.
+
+- a) When echo suppressors are needed and the OHES must be employed at the international transit exchange the outgoing international exchange sends the signal I-11 as a country code indicator.
+
+If an international connection is routed via two or more transit exchanges, signal I-11 must not be sent beyond the first transit exchange. Therefore the outgoing exchange, after having sent the signal I-11 once, must send the signal I-14 if the country code indicator is requested again (signal A-11).
+
+- b) When echo suppressors are needed and the IHES must be employed at the international transit exchange this is known by the international transit exchange. In this case the incoming international exchange will not send signal A-14.
+
+5.7.2.6 When echo suppressors are employed they will remain disabled until the answer signal is received. This condition is necessary in order to permit compelled interregister signalling to (e.g. national) exchanges further on in the connection.
+
+Alternatively, when the ability exists to detect that interregister signalling has been completed, the echo-suppressor may be enabled at that time without awaiting the answer signal.
+
+#### 5.7.3 *Examples of echo-suppressor control signalling*
+
+The following situations may arise:
+
+##### 5.7.3.1 *Direct interregister signalling between two countries A and B.*
+
+- a) No echo-suppressor control signalling is applied.
+
+This may be for one of two reasons. Either the connection does not normally require echo suppressors or echo suppressors are required and are permanently connected to the circuit.
+
+The signalling procedure is indicated in Table 11/Q.479, column a. If echo suppressors are necessary, the OHES is employed at A and the IHES is employed at B.
+
+- b) Echo-suppressor control signalling is applied.
+
+There are two cases:
+
+- i) No echo suppressors are required (see column b of Table 11/Q.479).
+- ii) Echo suppressors are required (see column c of Table 11/Q.479). The OHES is employed at A and the IHES is employed at B.
+
+##### 5.7.3.2 *Traffic between two countries A and D via two international transit exchanges B and C*
+
+There are two cases:
+
+###### 5.7.3.2.1 The connection is via terrestrial circuits only.
+
+- a) No echo suppressors are required (see column a of Table 12/Q.479).
+- b) Echo suppressors are required (see columns b, c, d, e of Table 12/Q.479).
+
+The following examples may be mentioned:
+
+- OHES in A; IHES in D (column b);
+- OHES in B; IHES in D (column c).
+
+The country code indicator I-11 is used by bilateral agreement and indicates that B must employ the OHES. When the country code indicator is to be sent to C, B asks A to do this by sending signal A-11. A, now sends signal I-14 instead of signal I-11, because B has employed the OHES. The signal A-14, which is sent from D as an acknowledgement of the Z-digit will, of course, also be answered by signal I-14.
+
+- OHES in A; IHES in C (column d).
+
+In accordance with § 5.7.2.5 b) above, C knows that D cannot employ an IHES and C itself will therefore make the connection. D will naturally not send signal A-14.
+
+- OHES in B; IHES in C (column e).
+
+###### 5.7.3.2.2 The connection includes a satellite link.
+
+The following examples are given as typical situations that may arise:
+
+- a) The first link in the connection is via satellite.
+
+In Table 13/Q.479, P and Q both know that echo suppressors are required.
+
+If Q has a permanently connected IHES then:
+
+- OHES in P; IHES in Q (column a).
+
+When R or S is able to employ an IHES then:
+
+- OHES in P; IHES in R (column c);
+- OHES in P; IHES in S (column b).
+
+- b) A later link in the connection is via satellite.
+
+In Table 14/Q.479:
+
+When P knows that Q-R is via satellite:
+
+- OHES in P; IHES in R or S (column b or d).
+
+When P does not know that Q-R is via satellite:
+
+- OHES in Q; IHES in R or S (column a or c).
+
+TABLE 11/Q.479
+Signalling procedure on direct connections
+
+| A ————— B | a | b | c |
+|--------------------------|--------|------|------|
+| Seizing —————> | | | |
+| Z-digit —————> | | | |
+| <———— | A-1 | A-14 | A-14 |
+| —————> | N1 | N1 | I-14 |
+| <———— | A-1 | A-1 | A-1 |
+| —————> | N2 | N2 | N1 |
+| Echo suppressor employed | YES/NO | NO | YES |
+
+CCITT-49950
+
+TABLE 12/Q.479
+Signalling procedures on international transit connections via terrestrial circuits
+
+| A — B — C — D | a | b | c | d | e |
+|-------------------------------|------|------|------|------|------|
+| Seizing —————> | | | | | |
+| Country code indicator —————> | I-12 | I-14 | I-11 | I-14 | I-11 |
+| <———— A-1 | | | | | |
+| I-1 —————> | | | | | |
+| <———— A-1 | | | | | |
+| I-2 —————> | | | | | |
+| A-11 —————> Seizing —————> | | | | | |
+| Country code indicator —————> | I-12 | I-14 | I-14 | I-14 | I-14 |
+| <———— A-1 | | | | | |
+| I-1 —————> | | | | | |
+| <———— A-1 | | | | | |
+| I-2 —————> | | | | | |
+| A-12 —————> Seizing —————> | | | | | |
+| Z-digit —————> | | | | | |
+| <———— | A-14 | A-14 | A-14 | A-1 | A-1 |
+| —————> | N1 | I-14 | I-14 | N1 | N1 |
+| <———— | A-1 | A-1 | A-1 | A-1 | A-1 |
+| —————> | N2 | N1 | N1 | N2 | N2 |
+| Echo suppressors employed at | — | A,D | B,D | A,C | B,C |
+
+CCITT-49960
+
+TABLE 14/Q.479
+
+Signalling procedures on international transit connection
+when a subsequent link is via satellite
+
+
+
+The diagram illustrates the signalling sequence for an international transit connection where a subsequent link is via satellite. The network topology shows nodes P, Q, R, and S, with P connected to Q, Q connected to R, and R connected to S. The signalling sequence is as follows:
+
+| Sequence | Node | Message | Column a | Column b | Column c | Column d |
+|----------|------------------------------|------------------------|----------|----------|----------|----------|
+| 1 | P | Seizing | | | | |
+| 2 | Q | Country code indicator | I-12 | I-14 | I-12 | I-14 |
+| 3 | P | A-1 | | | | |
+| 4 | Q | I-1 | | | | |
+| 5 | P | A-1 | | | | |
+| 6 | Q | I-2 | | | | |
+| 7 | P | Seizing | | | | |
+| 8 | Q | Country code indicator | I-12 | I-14 | I-12 | I-14 |
+| 9 | P | A-1 | | | | |
+| 10 | Q | I-1 | | | | |
+| 11 | P | A-1 | | | | |
+| 12 | Q | I-2 | | | | |
+| 13 | P | A-1 | | | | |
+| 14 | Q | Seizing | | | | |
+| 15 | R | Z Digit | | | | |
+| 16 | P | | A-14 | A-14 | A-14 | A-14 |
+| 17 | Q | | N1 | N1 | I-14 | I-14 |
+| 18 | P | | A-1 | A-1 | A-1 | A-1 |
+| 19 | Q | | N2 | N2 | N1 | N1 |
+| 20 | Echo suppressors employed at | | | Q,R | P,R | Q,S |
+| 21 | | | | | | P,S |
+
+Diagram for Table 14/Q.479 showing signalling procedures on an international transit connection where a subsequent link is via satellite. It includes a network topology diagram and a sequence of signalling messages across four columns (a, b, c, d).
+
+CCITT-73460
+
+TABLE 13/Q.479
+
+Signalling procedures on international transit connection
+when the first link is via satellite
+
+
+
+The diagram illustrates the signalling sequence for an international transit connection where the first link is via satellite. The network topology shows nodes P, Q, R, and S, with P connected to Q, Q connected to R, and R connected to S. The signalling sequence is as follows:
+
+| Sequence | Node | Message | Column a | Column b | Column c |
+|----------|------------------------------|------------------------|----------|----------|----------|
+| 1 | P | Seizing | | | |
+| 2 | Q | Country code indicator | I-14 | I-14 | I-14 |
+| 3 | P | A-1 | | | |
+| 4 | Q | I-1 | | | |
+| 5 | P | A-1 | | | |
+| 6 | Q | I-2 | | | |
+| 7 | P | Seizing | | | |
+| 8 | Q | Country code indicator | I-12 | I-14 | I-14 |
+| 9 | P | A-1 | | | |
+| 10 | Q | I-1 | | | |
+| 11 | P | A-1 | | | |
+| 12 | Q | I-2 | | | |
+| 13 | P | A-12 | | | |
+| 14 | Q | Z Digit | | | |
+| 15 | P | | A-14 | A-14 | A-1 |
+| 16 | Q | | N1 | I-14 | N1 |
+| 17 | P | | A-1 | A-1 | A-1 |
+| 18 | Q | | N2 | N1 | N2 |
+| 19 | Echo suppressors employed at | | | P,Q | R,8 |
+| 20 | | | | | R,8 |
+
+Diagram for Table 13/Q.479 showing signalling procedures on an international transit connection where the first link is via satellite. It includes a network topology diagram and a sequence of signalling messages across three columns (a, b, c).
+
+CCITT-73450
+
+### **5.8 MISCELLANEOUS PROCEDURES**
+
+#### **5.8.1 *Nature of circuit procedure for international working***
+
+An incoming R2 register in an international transit exchange or in the country of destination can elicit the nature of the circuit as soon as at least one forward signal has been received from an outgoing register.
+
+The incoming R2 register requests nature of circuit by sending the backward signal A-13. The outgoing R2 register, if capable, sends the nature of the circuit indicator signal I-13 or I-14 in reply.
+
+Signal A-13 can be sent after any forward signal (Groups I and II) and particularly after any address digit, but it can only be sent prior to any transmission of signal A-3.
+
+If the outgoing R2 register does not have the capability of providing the nature of circuit, signal I-12 (request not accepted) is sent in reply to signal A-13. The incoming R2 register will then ask for the following address digit by sending signal A-1, for example. If the outgoing R2 register receives signal A-13 again it will send signal I-12 again.
+
+For existing equipment if the outgoing international R2 register does not have the capability of providing the nature of the circuit, but is capable of sending identification information as defined in the *Yellow Book*, the procedure starts with the first digit of the country code.
+
+#### **5.8.2 *Identification procedure for national working***
+
+System R2 makes provision for the signalling necessary to identify the calling subscriber's line: for example, by repetition of signal A-5 or by using one of signals A-9 or A-10. For the time being this procedure is restricted to national working only; outgoing international R2 registers prevent its use over international links (see § 5.8.4). The outgoing R2 register at the incoming end of an international satellite link must similarly prevent its use via that link.
+
+#### **5.8.3 *Processing of Group II signals reserved for national use***
+
+The Group II signals reserved for national use must be converted in the outgoing international R2 register to Group II signals used for international working.
+
+The conversion must be carried out as follows:
+
+- II-1 must be converted to II-7
+- II-2 must be converted to II-7 or II-9
+- II-3 must be converted to II-7
+- II-4 must be converted to II-7
+- II-5 must be converted to II-7 or II-10
+- II-6 must be converted to II-8
+- II-11 to II-15 must be converted to II-7.
+
+Since there are no Recommendations yet regarding handling of priority calls in automatic international working, conversion of signal II-2 to signal II-9 must be the subject of bilateral agreement.
+
+If an incoming R2 register is situated in a national exchange and because signals II-7 to II-10 are not used for national working, then analysis of Group II signals enables a distinction to be made between nationally and internationally originated calls.
+
+If an incoming R2 register knows a call is of international origin and if a Group II signal reserved for national use is received, signal A-4 or B-4 (congestion on the national network) should be sent in acknowledgement. This procedure cannot be applied if an incoming R2 register in the destination country is employed for national and international working and is not able to detect the origin of the call.
+
+#### 5.8.4 *Procedures to be followed by outgoing international R2 registers on receipt of particular backward signals*
+
+An outgoing international R2 register must send the appropriate calling party's category signal (II-7 to II-10) in reply to signals A-3 and A-5.
+
+On recognition of one of the signals A-9 or A-10 an outgoing international R2 register sends signal I-12 (request not accepted) in response. Therefore, national incoming R2 registers using these signals should be equipped to receive signal I-12.
+
+The incoming national R2 register receiving I-12 has to determine the appropriate international standardized signal to be sent in response to signal I-12 and which substitutes for signals A-9 or A-10.
+
+In reply to signal A-14 an outgoing international R2 register sends:
+
+- signal I-14 when an incoming half-echo suppressor is required;
+- the next address digit (a signal I-1 to I-10) when no incoming half-echo suppressor is required.
+
+If an outgoing international R2 register receives a backward signal requesting an impossibility in the logical procedure (e.g. receipt of signal A-8 after sending the country code indicator), the call shall be released.
+
+# SECTION 6
+
+## TESTING AND MAINTENANCE
+
+###### Recommendation Q.490
+
+## TESTING AND MAINTENANCE
+
+### 6.1 *General*
+
+In international working the guiding principles and testing arrangements for maintenance as defined in Recommendations M.700 to M.728 and Q.134 also apply to Signalling System R2. The organization of routine maintenance, tests and measurements of signalling and switching should comply with Recommendations M.716, M.718, M.719, M.728 and M.732.
+
+The analogue line signalling of System R2 differs from other CCITT signalling systems in two significant respects:
+
+- line signals are sent over out-band signalling channels;
+- an "interruption control" protects the line signalling from the consequences of interruptions of the transmission path.
+
+These two features of System R2 require special attention from a maintenance point of view.
+
+### 6.2 *Automatic procedures for transmission measurements and signalling tests*
+
+Circuits operated with System R2 require elaborate transmission measurements and signalling tests and also rapid and simple testing of transmission and signalling. Both needs are preferably met by means of automatic devices.
+
+The specification for ATME-2 as adopted by CCITT makes it applicable to the testing of international circuits using System R2. The necessary information for its use on such circuits is contained in Recommendation O.22.
+
+A description of a simplified programme for rapid testing of signalling and checking the transmission quality of a circuit is given in § 6.3. Generally speaking, the arrangements for automatic testing consist of outgoing test equipment connected at the outgoing end of the circuit and incoming test equipment connected at the incoming end.
+
+### 6.3 *Automatic test procedures for test equipments*
+
+Automatic test procedures provides a means for rapid testing of signalling and also checking the transmission quality of circuits operated with Signalling System R2.
+
+#### 6.3.1 *Numbering of access to test equipment*
+
+In international working, to set up a call to maintenance equipment via circuits operated with System R2, the following multifrequency signals must be sent:
+
+- I-13 (replacing the language digit, in accordance with Recommendation Q.133),
+- I-13,
+- two digits "XY" which will be associated with the type of test equipment and the procedure for testing to be employed (see Recommendation Q.107, Table 7),
+- I-15 (if requested by the incoming equipment).
+
+Provision is made for repetition of signal I-13 to avoid complications in the incoming R2 register in the country of destination. The second signal I-13 is stored in the place where the first digit of the routing information is normally recorded. In this way, access to the test equipment requires no analysis, for routing purpose, of the signal which takes the place of the language digit.
+
+When calls are set up to the test equipment, it is desirable to avoid repetition of the request for the access code or for any other digit. This is because the calls may come from equipment which is not normally designed to interpret signals A-2, A-7 or A-8.
+
+The address complete signal to be sent on calls to test equipment must be one of the following:
+
+- A-6 or A-3 followed by B-6 when incoming test equipment is free,
+- A-4 or A-3 followed by B-3 or B-4 when incoming test equipment is busy.
+
+Precautions should be taken that signal A-6 is only sent when it is sure that the incoming test equipment is available for that call. When receiving signal A-3, the outgoing test equipment sends signal II-7 in response.
+
+*Note* – In national working, or in international working where the language digit is omitted by bilateral agreement, the following multifrequency signals must be sent:
+
+- I-13.
+- Two digits "XY".
+- I-15 (if necessary).
+
+#### 6.3.2 *Test sequence for simplified test*
+
+The test sequence is as follows:
+
+- a) seizing of the automatic incoming test equipment;
+- b) transition to answer state;
+- c) sending backward of a composite identification signal 1020 + 1140 Hz; this signal will be acknowledged in a compelled manner by the signal mentioned under d);
+- d) recognition of a composite acknowledgement signal 1380 + 1980 Hz, sent in the forward direction;
+- e) on the disappearance of the acknowledgement signal the incoming test equipment passes to the clear-back state;
+- f) on recognition of the clear-back signal, the outgoing equipment will send in a normal manner the clear-forward signal which will clear the connection and release incoming test equipment. After release of the incoming line circuit the release-guard signal will be sent in the normal way.
+
+Detection of failure is made by timing out at the outgoing equipment.
+
+The frequencies mentioned under c) and d) are those for System R2 interregister signalling; transmission and reception of these frequencies in the incoming test equipment must be in accordance with Section 4.
+
+Attenuation pads may be inserted in the send and receive paths of the outgoing test equipment to shift the receive level at the input of the multifrequency receivers of the outgoing and incoming test equipment toward the lower operational limit. This makes it possible to diagnose abnormal loss on the circuit under test from defective multifrequency signal exchange between outgoing and incoming test equipment. For testing international System R2 circuits, the additional attenuation produced by the pads should be $10 \pm 1$ dB.
+
+#### 6.3.3 *Good/no good transmission test equipment*
+
+In addition to the tests described in §§ 6.3.1 and 6.3.2 a good/no good transmission test may be provided as a simple means for fast error localization. Such a test is described in Recommendation Q.137 for System No. 4 (i.e. and the frequency of the test signal, the tolerances and the deviation from the nominal value, the test signal generators and receivers would all be the same) but the sending level being $-10$ dBm.
+
+It is to be noted that loop transmission measurements of the kind specified in Recommendation Q.136 cannot be made on System R2 circuits.
+
+### 6.4 *Testing of analogue line signalling equipment under abnormal conditions*
+
+The specification of the analogue line signalling equipment contains clauses concerning operation under abnormal conditions, including the action to be taken in case of interruption control alarm. The testing equipment described in § 6.2 is not applicable to such conditions and therefore the functioning of the analogue line signalling equipment under abnormal conditions should be tested internally at each end of a circuit either manually or automatically with special equipment.
+
+The detailed programme for this testing will be specified by each Administration.
+
+The design and construction of the line signalling equipment should be such as to permit both operational and limit testing in normal and abnormal conditions.
+
+### 6.5 *Alarms for the technical staff*
+
+Certain abnormal conditions in the signalling equipment should cause alarms to be set off for the technical staff (see also Recommendation Q.117). The relevant requirements are found in Section 2 (line signalling equipment) and in Section 5 (time-out in multifrequency registers).
+
+As indicated in § 2.2.3, a fault occurring during release of a circuit may result in an abnormal blocking condition. In this case there is a "tone-on" condition in both signalling directions, yet the circuit is not in the idle condition since the release-guard signal has not been received. If no special action is taken, a temporary fault may therefore result in the circuit's being out of service until it is manually restored by the maintenance staff, after receipt of an alarm (see § 2.2.4).
+
+It may accordingly be desirable to arrange for automatic restoration of abnormally blocked circuits. For Administrations wishing to introduce this function, the recommended arrangement is described below.
+
+### 6.6 *Recommended method for automatic restoration of an abnormally blocked circuit*
+
+When an outgoing link is abnormally blocked, periodic sending on the outgoing link of the seizing signal, followed shortly afterwards by the clear-forward signal, is initiated.
+
+Clearance of the fault which caused the abnormal blocked condition will initiate a release-guard signal at the incoming end whereupon the outgoing end restores the link to the idle condition.
+
+The intervals, at which the periodic sequence described above is repeated, should be between 30 seconds and 2 minutes.
+
+The first operation of the automatic device should be performed as soon as possible, but not before 2-3 seconds have elapsed, after recognition of the abnormally blocked condition at T1 (see § 2.2).
+
+After a period of three to six minutes a delayed alarm should be given in accordance with Recommendation Q.412, § 2.2.4.
+
+In the event of a backward tone-off condition being detected, other than in response to a periodic clear-forward signal, the periodic sequence is suspended until the backward tone is again recognized whereupon the periodic sending sequence is restarted.
+
+If interruption control at the outgoing end occurs during the abnormally blocked condition, the periodic sending sequence is suspended until the interruption control reverts to normal, whereupon the periodic sending sequence is restarted.
+
+### 6.7 *Instructions for the maintenance of channels and circuits using System R2 line signalling system at 3825 Hz*
+
+The analogue line signalling equipment specified in Section 2 is closely associated with the channel translating equipment and its operation may be a function of the group and supergroup translating and through-connection equipments. Maintenance of the circuits and groups which support them is governed by the principles and Recommendations of Volume IV. However, the introduction of out-band signalling calls for a few complements to these Recommendations, as described below.
+
+#### 6.7.1 *Bringing into service of group, supergroup, mastergroup or supermastergroup links*
+
+##### a) *§§ 2.1 and 7.6 of Recommendation M.460*
+
+It should be noted that group and supergroup pilots placed at 140 Hz from a virtual carrier frequency are incompatible with signalling at 3825 Hz. Hence, the pilot on 84.140 kHz should not be applied to groups in which channel 6 is to be operated with this out-band signalling. Similarly, the pilot on 411.860 kHz should not be applied to supergroups in which channel 1 of the group in the group 3 position is to be operated with signalling at 3825 Hz.
+
+If the channels of a group are to be operated with System R2, each extremity of the group should be equipped, at the receiving end, with a device to give protection against faulty signalling conditions which may result from an interruption in the transmission channels (interruption control). This equipment, which is based on pilot level detection; must comply with the conditions specified in § 2.4.3 of Recommendation Q.416.
+
+*Note* – If the channels of a supergroup which are operated with System R2 have the same extremities as the supergroup, a device based on monitoring of the supergroup pilot can be used instead of one based on monitoring of the group pilot. It will have to meet the same specifications.
+
+##### b) § 7.2 of Recommendation M.460
+
+The group-translating and through-connection equipments are specified with a passband extending from 60.600 kHz to 107.700 kHz. If it is wished to use channels 12 with signalling at 3825 Hz, it is necessary to ensure when the group is set up, that the corresponding frequency (60.175 kHz) is transmitted satisfactorily from end to end of the group link.
+
+Provisionally, in view of the operating margin of the receiving part of the signalling equipment, it is desirable to check that attenuation at this frequency does not exceed the attenuation at the group pilot frequency by more than 3 dB.
+
+A similar precaution should be taken on setting up group links when signalling is to be used at 3825 Hz on channel 12 of the group transmitted in position 5 on the supergroup.
+
+#### 6.7.2 *Setting-up and lining-up the channels of an international group*
+
+##### 6.7.2.1 *Setting up the out-band signalling channel for the System R2*
+
+Testing of the sending equipment:
+
+- The sending level of the signalling frequency corresponding to 3825 Hz if the carrier is taken as the frequency of origin must be lined up at $-20 \pm 1$ dBm0. When this frequency is not to be sent, its leak transmitted to line should not exceed $-45$ dBm0.
+
+Testing of the receiving equipment:
+
+- The signalling receiver must operate in the conditions described in §§ 2.3.2.1 and 2.3.2.2. It must not function when a signal, of which the characteristics (level and frequency) are such that the representative point is below the graph in Figure 8/Q.415, is applied to the same point.
+
+This test may be replaced by the following one to check the protection against unwanted signals (impulsive noise):
+
+- The sending part of the group terminal equipment is connected to its receiving part by a closed-circuit loop at the group distribution frame, this loop introducing a slight gain (e.g. 3 dB) if possible. The standardized click generator (see Figure 7/Q.414) is applied to each speech channel successively at the point where this channel is connected to the switching equipment, and a check is made to ensure that no wrong signals are retransmitted at the receiving end to the switching equipment by the channel signalling equipment concerned or by those of the other channels in the group.
+
+##### 6.7.2.2 *Closed-circuit loop tests: response time*
+
+When the transmission-reception loop of the terminal equipment is effected at the group distribution frame or at an equivalent point, a check is made to ensure that less than 30 ms elapse between the moment when the change of condition is applied to the transmitter associated with each channel and the moment when it appears at the output of the corresponding receiver.
+
+##### 6.7.2.3 *End-to-end tests*
+
+When the terminal channel-translating equipments are normally connected to the extremities of the link, an end-to-end operating test is carried out. The level of the line-signalling frequencies transmitted and received for each channel are likewise measured, to provide a reference, at the group terminal distribution frames or at equivalent points.
+
+## ANNEX A
+
+(to Signalling System R2 Specifications)
+
+(see Recommendations Q.400 and Q.441)
+
+### Provision of a forward-transfer signalling facility
+
+### A.1 *General*
+
+The System R2 does not provide a forward-transfer line signal. However for certain relations it may be decided by bilateral or multilateral agreement to introduce the forward-transfer signalling facility into System R2.
+
+One possible procedure that has been adopted for use within Europe, is to use the PYY in-band signal of System No. 4. This solution is only economical in regions where the facility is needed for a small proportion of the calls.
+
+For international working the method as described below may be followed.
+
+*Note* – The method given in this Annex may also be adopted in national networks where the forward-transfer facility is considered necessary for trunk offering and recalling operators. However, care must be taken to see that the transmission limits applying to the forward-transfer signal specified are observed.
+
+### A.2 *Method recommended for introducing the forward-transfer signalling facility into System R2*
+
+Forward-transfer signalling will be provided by means of special equipment which uses in-band signalling and which is switched only on to those connections which may require this facility. The amount of special equipment necessary can, accordingly, be reduced to a minimum and adapted, in a flexible manner, to actual needs. The in-band signal constituting the forward-transfer signal is sent end-to-end between the outgoing and incoming international exchanges. When the special equipment receives the forward-transfer signal, it performs the necessary operations at the incoming exchange.
+
+#### A.2.1 *Access to the special equipment in an incoming international exchange*
+
+In an incoming international exchange access to the special equipment for forward-transfer signalling can be determined by the use of the following indicators:
+
+- 1) Special marking of incoming routes on which forward-transfer signalling is used.
+- 2) Language digit indicating semi-automatic traffic.
+- 3) Calls for code 11 or code 12 operator.
+- 4) Special interregister signalling sequence in which the incoming exchange sends signal A-5, *send calling party's category*. If the forward-transfer signalling facility is required the outgoing R2 register will respond to this by sending the signal II-10. This signal indicates an operator-initiated call on which special equipment for forward-transfer signalling is needed.
+
+The use of these indicators will depend on the amount of traffic for which forward-transfer signalling is employed. In some cases one or two of the indicators will be utilized. In others, combinations of all will be used to reduce to a minimum the amount of special equipment required.
+
+#### A.2.2 *In-band forward-transfer signalling*
+
+In System R2 the in-band forward-transfer signal is the same as that used in System No. 4. For the definition of this signal see Recommendation Q.120, § 1.12. The signal is the signal PYY defined in Recommendation Q.121, § 2.3. The forward-transfer signal is sent in accordance with Recommendations Q.122 and Q.124.
+
+The signal receiver and the splitting arrangements to be incorporated in the special equipment at the incoming international exchange are in accordance with Recommendations Q.123 and Q.124.
+
+Provided it creates no difficulty for incoming national network signalling, no splitting need be effected at the receiving end and the caller will then hear the entire signal PYY.
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series B | Means of expression: definitions, symbols, classification |
+| Series C | General telecommunication statistics |
+| Series D | General tariff principles |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Construction, installation and protection of cables and other elements of outside plant |
+| Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks and open system communications |
+| Series Y | Global information infrastructure and Internet protocol aspects |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426
--- /dev/null
+++ b/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d
+size 3828
diff --git a/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c941c9ec6517c60feea4c2380fb3b53584f1fa86
--- /dev/null
+++ b/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5092a834ed5c2e4f10363b8b41a667459f64b304ba483a070d49d1da601cbbf
+size 21122
diff --git a/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49f65701beef26bd00da66c55578f0d29699d2e1
--- /dev/null
+++ b/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb1f1e3536ae521cb4f4dd88f0476a983fe132209fb029e2446ee6675b62737a
+size 19911
diff --git a/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/raw.md b/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e5876dcf7bf8b6266a9276c1527043514f2d9c81
--- /dev/null
+++ b/marked/Q/T-REC-Q.4004.2-201602-I_PDF-E/raw.md
@@ -0,0 +1,1216 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+**Q.4004.2**
+
+(02/2016)
+
+SERIES Q: SWITCHING AND SIGNALLING
+
+Testing specifications – Testing specifications for SIP-IMS
+
+---
+
+**Communication diversion using IP multimedia
+core network subsystem; Conformance testing
+– Part 2: Network side; Test suite structure and
+test purposes**
+
+Recommendation ITU-T Q.4004.2
+
+# ITU-T Q-SERIES RECOMMENDATIONS
+
+## SWITCHING AND SIGNALLING
+
+| | |
+|--------------------------------------------------------------------------------|----------------------|
+| SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
+| INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
+| FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
+| CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
+| SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 | Q.120–Q.499 |
+| DIGITAL EXCHANGES | Q.500–Q.599 |
+| INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
+| SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
+| Q3 INTERFACE | Q.800–Q.849 |
+| DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
+| PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
+| INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
+| INTELLIGENT NETWORK | Q.1200–Q.1699 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 | Q.1700–Q.1799 |
+| SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
+| BROADBAND ISDN | Q.2000–Q.2999 |
+| SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN | Q.3000–Q.3899 |
+| TESTING SPECIFICATIONS | Q.3900–Q.4099 |
+| Testing specifications for next generation networks | Q.3900–Q.3999 |
+| Testing specifications for SIP-IMS | Q.4000–Q.4039 |
+| Testing specifications for Cloud computing | Q.4040–Q.4059 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# Recommendation ITU-T Q.4004.2
+
+# Communication diversion using IP multimedia core network subsystem; Conformance testing – Part 2: Network side; Test suite structure and test purposes
+
+## Summary
+
+Recommendation ITU-T Q.4004.2 v.1 (2016) is part 2 of the testing specifications for communications diversion (CDIV) service implemented on IP multimedia subsystem (IMS) basis on the network side. The Recommendation specifies the test suite structure and test purposes (TSS&TP) which can be used for testing against the Recommendation [ITU-T Q.3620 v.1].
+
+The version number, v.1, indicates that this is version one of Recommendation ITU-T Q.4004.2 and that it relates to Release 10 of the relevant 3GPP/ETSI standard.
+
+## History
+
+| Edition | Recommendation | Approval | Study Group | Unique ID* |
+|---------|--------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0 | ITU-T Q.4004.2 v.1 | 2016-02-13 | 11 | 11.1002/1000/12737 |
+
+## Keywords
+
+Communications diversion, CDIV, IP multimedia subsystem, IMS, network side session description protocol, SDP, session initiation protocol, SIP, test purposes, TP, test suite structure, TSS, testing.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID. For example, .
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Test suite structure (TSS) ..... | 2 |
+| 5.1 Configuration..... | 2 |
+| 6 Test purposes (TP)..... | 3 |
+| 6.1 Introduction ..... | 3 |
+| 6.2 Signalling requirements..... | 4 |
+| 6.3 Interaction with other services..... | 40 |
+| Bibliography..... | 48 |
+
+
+
+## Recommendation ITU-T Q.4004.2
+
+## Communication diversion using IP multimedia core network subsystem; Conformance testing – Part 2: Network side; Test suite structure and test purposes
+
+## 1 Scope
+
+The present Recommendation specifies the test suite structure and test purposes (TSS&TP) for communications diversion (CDIV) services [ITU-T Q.3620 v.1] for the network side.
+
+The communications diversion (CDIV) services enables diverting user, to divert the communications addressed to diverting user to another destination.
+
+The present Recommendation is part 2 of a multi-part deliverable covering communication diversion (CDIV), as identified below:
+
+Part 1: "Protocol implementation conformance statement (PICS)";
+
+**Part 2: "Test suite structure and test purposes; Network side (TSS&TP)";**
+
+Part 3: "Test suite structure and test purposes; User side (TSS&TP)".
+
+## 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+- [ITU-T Q.3620 v.1] Recommendation ITU-T Q.3620 v.1 (2016), *Communication diversion (CDIV) using IP multimedia core network subsystem – Protocol specification*.
+- [ITU-T Q.4004.1 v.1] Recommendation ITU-T Q.4004.1 v.1 (2016), *Communication diversion using IP multimedia core network subsystem; Conformance testing – Part 1: Network side and user side; Protocol implementation conformance statement*.
+- [ITU-T X.290] Recommendation ITU-T X.290 (1995), *OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications – General concepts*.
+- [IETF RFC 4244] IETF RFC 4244 (2005), *An Extension to the Session Initiation Protocol (SIP) for Request History Information*.
+
+# 3 Definitions
+
+For the purposes of this Recommendation, the terms and definitions given in [ITU-T Q.3620 v.1] and the following apply:
+
+- 3.1 abstract test suite (ATS):** Refer to [ITU-T X.290].
+- 3.2 implementation under test (IUT):** Refer to [ITU-T X.290].
+- 3.3 pics proforma:** Refer to [ITU-T X.290].
+
+- 3.4 **point of control and observation:** Refer to [ITU-T X.290].
+- 3.5 **protocol implementation conformance statement (PICS):** Refer to [ITU-T X.290].
+- 3.6 **system under test (SUT):** Refer to [ITU-T X.290].
+- 3.7 **test purpose (TP):** Refer to [ITU-T X.290].
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|------|-------------------------------------------------|
+| Gm | Reference Point between a UE and a P-CSCF |
+| ISC | IP Multimedia Subsystem Service Control |
+| Mg | Reference Point between an MGCF and a CSCF |
+| Mw | Reference Point between a CSCF and another CSCF |
+| Mx | Reference Point between a CSCF/BGCF and IBCF |
+| NDUB | Network Determined User Busy |
+| NNI | Network - Network Interface |
+| TSS | Test Suite Structure |
+| UDUB | User Determined User Busy |
+
+## 5 Test suite structure (TSS)
+
+**Table 1 – Test suite structure**
+
+| | |
+|-------------------------------|--------------|
+| Netw | |
+| ASdivertingUser/DivProcedures | CDIV_N01_xxx |
+| ASdivertingUser/NotOrigUser | CDIV_N02_xxx |
+| ASdivertingUser/NotTermUser | CDIV_N03_xxx |
+| ASdivertingUser/NotDivUser | CDIV_N04_xxx |
+| ASdiverted-to | CDIV_N05_xxx |
+| Interaction | |
+| TIP | CDIV_N06_xxx |
+| TIR | CDIV_N07_xxx |
+| OIR | CDIV_N08_xxx |
+| ACR-CB | CDIV_N09_xxx |
+| ECT | CDIV_N10_xxx |
+
+## 5.1 Configuration
+
+The scope of this Recommendation is to test the signalling and procedural aspects of the stage 3 requirements as described in [ITU-T Q.3620 v.1]. The stage 3 description respects the requirements to several network entities and also to requirements regarding end devices. Therefore several interfaces (reference points) are addressed to satisfy the test of the different entities.
+
+In order to test the appropriate entities the configurations below are applicable:
+
+**Testing of the Application Server:** This entity is responsible for performing the service. Hence the ISC interface is the appropriate access point as shown in Figure 1.
+
+
+
+Q.4004.2v1(16)\_F01
+
+Diagram of Figure 1: Applicable interface to test AS functionalities. It shows a central green box labeled 'Application server' and 'Implementation under test' connected to two cyan boxes labeled 'Test system' via 'ISC' interfaces.
+
+**Figure 1 – Applicable interface to test AS functionalities**
+
+If the ISC interface is not accessible it is also applicable to perform the test of the AS using any NNI (Mw, Mg, Mx) interface (see Figure 2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware that the verification of several requirements is impeded.
+
+
+
+Q.4004.2v1(16)\_F02
+
+Diagram of Figure 2: Applicable interfaces to test using the (generic) NNI interface. It shows a central green box labeled 'CSCF (and/or AS)' and 'Implementation under test' connected to two cyan boxes labeled 'Test system' via 'Mw, Mg, Mx' interfaces.
+
+**Figure 2 – Applicable interfaces to test using the (generic) NNI interface**
+
+## 6 Test purposes (TP)
+
+## 6.1 Introduction
+
+#### 6.1.1 TP naming convention
+
+Test purposes (TPs) are numbered, starting at 001, within each group. Groups are organized according to the test suite structure (TSS). Additional references are added to identify the actual test suite and whether it applies to the network or the user (see Figure 3).
+
+| | | | | | | | |
+|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|---|------|---|---------|-----|---------|
+| Identifier: __ | | | | | | | |
+| = supplementary service: | e.g. "CDIV" | | | | | | |
+| = type of IUT: | | U | User |
| N | Network |
| yyy | service |
| U | User | N | Network | yyy | service |
+| U | User | | | | | | |
+| N | Network | | | | | | |
+| yyy | service | | | | | | |
+| = group | 2 digit field representing group reference according to TSS | | | | | | |
+| = sequential number | (001-999) | | | | | | |
+
+**Figure 3 – TP identifier naming convention scheme**
+
+#### 6.1.2 Test strategy
+
+As the base standard [ITU-T Q.3620 v.1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the protocol implementation conformance statement (PICS) specification [ITU-T Q.4004.1 v.1].
+
+## 6.2 Signalling requirements
+
+#### 6.2.1 Actions at the AS of the diverting user
+
+##### 6.2.1.1 Diversion procedures
+
+| TSS
Netw/ASdivertingUser/DivProcedures | TP
CDIV_N01_001 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.1 | Selection expression
PICS 1/2 |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|----------------------------------|
+| Test purpose
Served user has activated CFB, maximum number of diversion exceeded. | | | |
+| Ensure that the 486 (Busy here) final response with a Warning header is sent to the original user if the served user has activated the CFB simulation service and the served user is busy and if the maximum number of diversions is exceeded. | | | |
+| SIP header values:
INVITE: sip:SIP#n@example.com SIP/2.0
History-Info: non significant uri value >;index=1,
Build additional entries with non significant uri values
;index=1.n.1
Warning: is present | | | |
+| NOTE: For each redirection a history-entry is added the History-Info header and the relevant index is incremented according the rules described in clause 4.5.2.6.2.3 [ITU-T Q.3620 v.1]. In short: each redirection is represented by a "." (dot) in the latest history-entry. | | | |
+| Comments: | | | |
+| SIP#1 | AS | SIP#n | SIP#n+1 |
+| INVITE 1 | → | → | INVITE 1 |
+| | | ← | 486 Busy Here |
+| 486 (Busy here) | ← | → | ACK |
+| ACK | → | | |
+
+| TSS
Netw/ASdivertingUser/DivProcedures | TP
CDIV_N01_002 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.1 | Selection expression
PICS 1/3 |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|----------------------------------|
+| Test purpose
Served user has activated CFNR, maximum number of diversion exceeded. | | | |
+| Ensure that the 480 (Temporarily unavailable) final response with a Warning header is sent to the original user if the served user does not answer the communication request and if the maximum number of diversions is exceeded. | | | |
+| SIP header values:
INVITE: sip:SIP#n@example.com SIP/2.0
History-Info: non significant uri value>;index=1,
Build additional entries with non significant uri values
;index=1.n.1
Warning: is present | | | |
+| NOTE: For each redirection a history-entry is added to the History-Info header and the relevant index is incremented according the rules described in clause 4.5.2.6.2.3 [ITU-T Q.3620 v.1]. In short: each redirection is represented by a "dot" in the latest history-entry. | | | |
+| Comments: | | | |
+| SIP#1 | AS | SIP#n | SIP#n+1 |
+| INVITE | → | → | INVITE |
+| 180 Ringing | ← | ← | 180 Ringing |
+| | | | No reply timer expires |
+| 480 (Temporarily unavailable) | ← | → | CANCEL |
+| ACK | → | ← | 200 OK CANCEL |
+| | | ← | 487 Request Terminated |
+| | | → | ACK |
+
+| TSS
Netw/ASdivertingUser/DivProcedures | TP
CDIV_N01_003 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.1 | Selection
expression
PICS 1/1 |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|-------------------------------------|
+| Test purpose
Served user has activated CFU, maximum number of diversion exceeded. | | | |
+| Ensure that the 480 (Temporarily unavailable) final response with a Warning header is sent to the original user if the served user has activated the CFU simulation service and if the maximum number of diversions is exceeded. | | | |
+| SIP header values:
INVITE: sip:SIP#n@example.com SIP/2.0
History-Info: non significant uri value >;index=1,
Build additional entries with non significant uri values
;index=1.n.1
Warning: is present | | | |
+| NOTE: For each redirection a history-entry is added the History-Info header and the relevant index is incremented according the rules described in clause 4.5.2.6.2.3 [ITU-T Q.3620 v.1]. In short: each redirection is represented by a "dot" in the latest history-entry. | | | |
+| Comments: | | | |
+| SIP#1 | AS | SIP#n | SIP#n+1 |
+| INVITE | → | | |
+| 480 (Temporarily unavailable) | ← | | |
+| ACK | → | | |
+
+| TSS
Netw/ASdivertingUser/DivProcedures | TP
CDIV_N01_004 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.1 | Selection
expression
PICS 1/4 OR
PICS 1/5 |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|----------------------------------------------------|
+| Test purpose
Served user has activated CD, maximum number of diversion exceeded. | | | |
+| Ensure that the 480 (Temporarily unavailable) final response with a Warning header is sent to the original user if the served user has activated the CD simulation service and if the maximum number of diversions is exceeded. | | | |
+| SIP header values:
INVITE: sip:SIP#n@example.com SIP/2.0
History-Info: non significant uri value >;index=1,
Build additional entries with non significant uri values
;index=1.n.1
Warning: is present | | | |
+| NOTE: For each redirection a history-entry is added the History-Info header and the relevant index is incremented according the rules described in clause 4.5.2.6.2.3 [ITU-T Q.3620 v.1]. In short: each redirection is represented by a "dot" in the latest history-entry. | | | |
+| Comments: | | | |
+| SIP#1 | AS | SIP#n | SIP#n+1 |
+| INVITE | → | → INVITE | |
+| 180 Ringing | ← | ← 180 Ringing | |
+| | ← | ← 302 Moved Temporarily | |
+| | | → ACK | |
+| 480 (Temporarily unavailable) | ← | | |
+| ACK | → | | |
+
+##### 6.2.1.2 Notification procedure of the originating terminating and diverting user
+
+###### 6.2.1.2.1 Originating user
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_001 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 3/3 AND
(PICS 1/1 OR PICS1/2 OR
PICS 1/6 OR PICS 1/7) |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|------------------------------------------------------------------------------------------|
+| Test purpose
Communication forwarding using CFU or using CFB NDUB, CFNL or CFNRc with applying diversion condition; originating user is not notified. | | | |
+| When communication diversion occurs and if the notification procedures of the originating user is supported then no 181 (Call Is Being Forwarded) response shall be sent towards the originating user if the served users subscription option is set to: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no. | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = no | | | |
+| Comments: | | | |
+| SIP#1
INVITE | → | AS | SIP#2 |
+| | | | SIP#3 |
+| | | | → INVITE |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_002 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 3/3 AND PICS 3/4
AND PICS 3/5
AND (PICS 1/1 OR
PICS1/2 OR PICS 1/6 OR
PICS 1/7) |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
Communication forwarding using CFU or using CFB NDUB, CFNL or CFNRc with applying diversion condition; originating user is notified. | | | |
+| When communication diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = CAU_VA and escaped Privacy header set to 'history', index = 1.1 | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = yes
Served user allows the presentation of his/her URI to originating user in diversion notification = yes | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
History-Info: ;index=1,
;index=1.1 | | | |
+| Comments: | | | |
+| SIP#1
INVITE | → | AS | SIP#2 |
+| | | | SIP#3 |
+| 181 Call is Being Forwarded | ← | | → INVITE |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_003 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 3/3 AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4
AND (PICS 1/1 OR
PICS1/2 OR PICS 1/6
OR PICS 1/7) | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|-----------|--------------|--------------|--------|---|--|--|--|-----------------------------|---|--|--|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CFU or using CFB NDUB, CFNL or CFNRc with applying diversion condition; originating user is notified.
When communication diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a Privacy header set to "id" and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history",
index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user with a Privacy header set to
"history", cause = CAU_VA, index = 1.1 | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = no
Served user allows the presentation of his/her URI to originating user in diversion notification = no OR
Served user has subscribed to TIR in permanent mode | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
Privacy: id
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | SIP#2 | SIP#3 |
| INVITE | → | | | |
| 181 Call is Being Forwarded | ← | | | |
| | | | → INVITE |
| | | | SIP#1 | | AS | SIP#2 | SIP#3 | INVITE | → | | | | 181 Call is Being Forwarded | ← | | | | | | | | → INVITE |
+| SIP#1 | | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | → INVITE | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_004 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 3/3 AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4
AND (PICS 1/1 OR
PICS1/2 OR PICS 1/6
OR PICS 1/7) | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|-----------|--------------|--------------|--------|---|--|--|--|-----------------------------|---|--|--|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CFU or using CFB NDUB, CFNL or CFNRc with applying diversion condition; originating user is notified.
When communication diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a Privacy header set to "id" and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = CAU_VA and escaped Privacy header set to 'history', index = 1.1 | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = yes
Served user allows the presentation of his/her URI to originating user in diversion notification = no OR
Served user has subscribed to TIR in permanent mode | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
Privacy: id
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | SIP#2 | SIP#3 |
| INVITE | ➔ | | | |
| 181 Call is Being Forwarded | ← | | | |
| | | | ➔ INVITE |
| | | | SIP#1 | | AS | SIP#2 | SIP#3 | INVITE | ➔ | | | | 181 Call is Being Forwarded | ← | | | | | | | | ➔ INVITE |
+| SIP#1 | | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | |
+| INVITE | ➔ | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | ➔ INVITE | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_005 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 3/3 AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4
AND (PICS 1/1 OR
PICS1/2 OR PICS 1/6
OR PICS 1/7) | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|-----------|--------------|--------------|--------|---|--|--|--|-----------------------------|---|--|--|----------|
+| Test purpose
Communication forwarding using CFU or using CFB NDUB, CFNL or CFNRc with applying diversion condition; originating user is notified. | | | | | | | | | | | | | | | | | | |
+| When communication diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served user, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user with a Privacy header set to "history", cause = CAU_VA, index = 1.1 | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = no
Served user allows the presentation of his/her URI to originating user in diversion notification = yes | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | SIP#2 | SIP#3 |
| INVITE | → | | | |
| 181 Call is Being Forwarded | ← | | | → INVITE |
| | | | SIP#1 | | AS | SIP#2 | SIP#3 | INVITE | → | | | | 181 Call is Being Forwarded | ← | | | → INVITE |
+| SIP#1 | | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | → INVITE | | | | | | | | | | | | | | |
+
+**Table 2 – Communication diversion cause, used in CDIV\_N02\_001-005**
+
+| CAU_VA | Communication diversion | Value |
+|--------|-------------------------|-------|
+| 1 | CFU | 302 |
+| 2 | CFB NDUB | 486 |
+| 3 | CFNL | 404 |
+| 4 | CFNRc | 503 |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_006 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 3/3
AND PICS1/2 | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|-------------------------------------------------|--------------|--|-----------|--------------|--------------|--------|---|--|----------|--|--|--|--|-----------------|--|--|--|--|-------|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CFB UDUB with applying diversion condition; originating user is not notified. | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| When communication diversion occurs (served user sends 486 response) and if the notification procedures of the originating user is supported then no 181 (Call Is Being Forwarded) response shall be sent towards the originating user if the served users subscription option is set to: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no. | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = no | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | SIP#2 | SIP#3 |
| INVITE | → | | → INVITE | |
| | | ← 486 Busy Here | |
| | | → ACK | |
| | | | → INVITE |
| | | | SIP#1 | | AS | SIP#2 | SIP#3 | INVITE | → | | → INVITE | | | | | ← 486 Busy Here | | | | | → ACK | | | | | | → INVITE |
+| SIP#1 | | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_007 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/2
AND PICS 3/3
AND PICS 3/4
AND PICS 3/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|--------------|--|-----------|--------------|--------------|--------|---|--|----------|--|--|--|--|-----------------|--|--|--|--|-------|--|-----------------------------|---|--|--|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CFB UDUB with applying diversion condition; originating user is notified. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| When communication diversion occurs (served user sends 486 response) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing: - a P-Asserted-Identity header with the URI of the served user and
- a History-Info header
including a first entry with the hi-targeted-to-URI of the served, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 486 and escaped Privacy header set to 'history', index = 1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = yes
Served user allows the presentation of his/her URI to originating user in diversion notification = yes | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
History-Info: ;index=1,
;index=1.1
NOTE: According to [ITU-T Q.3620 v.1] clause 4.5.2.6.2.2.b: "If the diversion is based on a SIP response from the served user, a Reason header in escaped form shall be included in accordance with [IETF RFC 4244] ". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | SIP#2 | SIP#3 |
| INVITE | → | | → INVITE | |
| | | ← 486 Busy Here | |
| | | → ACK | |
| 181 Call is Being Forwarded | ← | | | |
| | | | → INVITE |
| | | | SIP#1 | | AS | SIP#2 | SIP#3 | INVITE | → | | → INVITE | | | | | ← 486 Busy Here | | | | | → ACK | | 181 Call is Being Forwarded | ← | | | | | | | | → INVITE |
+| SIP#1 | | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_008 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 3/3 AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4
AND PICS1/2 |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| Test purpose
Communication forwarding using CFB UDUB with applying diversion condition; originating user is notified. | | | |
+| When communication diversion occurs (served user sends 486 response) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing: - a P-Asserted-Identity header with the URI of the served user and
- a Privacy header set to "id" and
- a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user with a Privacy header set to "history", cause = 486, index = 1.1 | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = no
Served user allows the presentation of his/her URI to originating user in diversion notification = no OR
Served user has subscribed to TIR in permanent mode | | | |
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------|-----------|---------------|--------------|--------------|--------|---|--|---|--------|--|--|--|--|---|---------------|--|--|--|--|---|-----|--|-----------------------------|---|--|--|--|----------|
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
Privacy: id
History-Info: <sip:SIP#2?Privacy=history&Reason=SIP%3Bcause%3D486>;index=1,
<sip:SIP#3;cause=486?Privacy=history>;index=1.1
NOTE: According to [ITU-T Q.3620 v.1] clause 4.5.2.6.2.2.b: "If the diversion is based on a SIP response from the served user, a Reason header in escaped form shall be included in accordance with [IETF RFC 4244]".
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | | SIP#2 | SIP#3 |
| INVITE | → | | → | INVITE | |
| | | ← | 486 Busy Here | |
| | | → | ACK | |
| 181 Call is Being Forwarded | ← | | | | → INVITE |
| SIP#1 | | AS | | SIP#2 | SIP#3 | INVITE | → | | → | INVITE | | | | | ← | 486 Busy Here | | | | | → | ACK | | 181 Call is Being Forwarded | ← | | | | → INVITE |
+| SIP#1 | | AS | | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_009 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 3/3 AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4
AND PICS1/2 |
+|------------------------------------------------|---------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------|
+|------------------------------------------------|---------------------------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------|
+
+| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------|-----------|---------------|--------------|--------------|--------|---|--|---|--------|--|--|--|--|---|---------------|--|--|--|--|---|-----|--|-----------------------------|---|--|--|--|----------|
+| Test purpose
Communication forwarding using CFB UDUB with applying diversion condition; originating user is notified.
When communication diversion occurs (served user sends 486 response) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a Privacy header set to "id" and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 486 and escaped Privacy header set to 'history', index = 1.1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = yes
Served user allows the presentation of his/her URI to originating user in diversion notification = no OR
Served user has subscribed to TIR in permanent mode
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
Privacy: id
History-Info: <sip:SIP#2?Privacy=history&Reason=SIP%3Bcause%3D486>;index=1,
<sip:SIP#3;cause=486?Privacy=history>;index=1.1
NOTE: According to [ITU-T Q.3620 v.1] clause 4.5.2.6.2.2.b: "If the diversion is based on a SIP response from the served user, a Reason header in escaped form shall be included in accordance with [IETF RFC 4244]".
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | | SIP#2 | SIP#3 |
| INVITE | → | | → | INVITE | |
| | | ← | 486 Busy Here | |
| | | → | ACK | |
| 181 Call is Being Forwarded | ← | | | | → INVITE |
| SIP#1 | | AS | | SIP#2 | SIP#3 | INVITE | → | | → | INVITE | | | | | ← | 486 Busy Here | | | | | → | ACK | | 181 Call is Being Forwarded | ← | | | | → INVITE |
+| SIP#1 | | AS | | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_011A | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/3 AND PICS 3/3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------|------------------------|---|--------------|--|--------------|--|--------------|--------|---|--|---|--------|--|--|--------------|---|--|---|--------------|--|--|--|--|--|------------------------|--|--|--|--|--|--|---|------------|--|--|--|--|--|---|-------------------|--|--|--|--|--|---|------------------------|--|--|--|--|--|---|-----|--|--|--|--|--|--|--|---|--------|
+| Test purpose
Communication forwarding using CFNR with applying diversion condition; Reason header in BYE or CANCEL
When communication diversion occurs (served user does not respond) the initial communication to the served user is terminated with a CANCEL or a BYE request with a Reason header with protocol set to SIP and the cause set to 408. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
CANCEL/BYE:
Reason: SIP; cause=408 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | | SIP#2 | | SIP#3 |
| INVITE | → | | → | INVITE | | |
| 180 Alerting | ← | | ← | 180 Alerting | | |
| | | No reply timer expires | |
| | | → | CANCEL/BYE | | |
| | | ← | 200 OK CANCEL/BYE | | |
| | | ← | 487 Request Terminated | | |
| | | → | ACK | | |
| | | | | → | INVITE |
| | | | SIP#1 | | AS | | SIP#2 | | SIP#3 | INVITE | → | | → | INVITE | | | 180 Alerting | ← | | ← | 180 Alerting | | | | | | No reply timer expires | | | | | | | → | CANCEL/BYE | | | | | | ← | 200 OK CANCEL/BYE | | | | | | ← | 487 Request Terminated | | | | | | → | ACK | | | | | | | | → | INVITE |
+| SIP#1 | | AS | | SIP#2 | | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 180 Alerting | ← | | ← | 180 Alerting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | No reply timer expires | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → | CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_012 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/3
AND PICS 3/3
AND PICS 3/4
AND PICS 3/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|------------------------|---|--------------|--|--------------|--|--------------|--------|---|--|---|--------|--|--|--------------|---|--|---|--------------|--|--|--|--|--|------------------------|--|--|--|-----------------------------|---|--|--|--|--|--|--|--|--|---|------------|--|--|--|--|--|---|-------------------|--|--|--|--|--|---|------------------------|--|--|--|--|--|---|-----|--|--|--|--|--|--|--|---|--------|
+| Test purpose
Communication forwarding using CFNR with applying diversion condition; originating user is notified.
When communication diversion occurs (served user does not respond) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing
a P-Asserted-Identity header with the URI of the served user and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 408 and escaped Privacy header set to 'history', index = 1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = yes
Served user allows the presentation of his/her URI to originating user in diversion notification = yes | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | | SIP#2 | | SIP#3 |
| INVITE | → | | → | INVITE | | |
| 180 Alerting | ← | | ← | 180 Alerting | | |
| | | No reply timer expires | |
| 181 Call is Being Forwarded | ← | | | | | |
| | | → | CANCEL/BYE | | |
| | | ← | 200 OK CANCEL/BYE | | |
| | | ← | 487 Request Terminated | | |
| | | → | ACK | | |
| | | | | → | INVITE |
| | | | SIP#1 | | AS | | SIP#2 | | SIP#3 | INVITE | → | | → | INVITE | | | 180 Alerting | ← | | ← | 180 Alerting | | | | | | No reply timer expires | | | | 181 Call is Being Forwarded | ← | | | | | | | | | → | CANCEL/BYE | | | | | | ← | 200 OK CANCEL/BYE | | | | | | ← | 487 Request Terminated | | | | | | → | ACK | | | | | | | | → | INVITE |
+| SIP#1 | | AS | | SIP#2 | | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 180 Alerting | ← | | ← | 180 Alerting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | No reply timer expires | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → | CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | → | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASNotification/Originating user | TP
CDIV_N02_013 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/3 AND PICS 3/3
AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4 | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------------------|
+| Test purpose | | | | | | | | | | |
+| Communication forwarding using CFNR with applying diversion condition; originating user is notified. | | | | | | | | | | |
+| When communication diversion occurs (served user does not respond) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
- a P-Asserted-Identity header with the URI of the served user and
- a Privacy header set to "id" and
- a History-Info header
- including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
- and
- including a second entry with the hi-targeted-to-URI of the diverted-to user, with a Privacy header set to "history", cause = 408, index = 1.1
| | | | | | | | | | |
+| Subscription options: | | | | | | | | | | |
+| Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes | | | | | | | | | | |
+| Served user allows the presentation of diverted to URI to originating user in diversion notification = no | | | | | | | | | | |
+| Served user allows the presentation of his/her URI to originating user in diversion notification = no OR | | | | | | | | | | |
+| Served user has subscribed to TIR in permanent mode | | | | | | | | | | |
+| SIP header values: | | | | | | | | | | |
+| 181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
Privacy: id
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | |
+| Comments: | | | | | | | | | | |
+| SIP#1
INVITE
180 Alerting
181 Call is Being Forwarded |
➔
⬅
⬅ | AS
No reply timer expires |
➔
⬅
➔
⬅
⬅
➔ | SIP#2
INVITE
180 Ringing
CANCEL/BYE
200 OK CANCEL/BYE
487 Request Terminated
ACK |
➔ | SIP#3
INVITE |
| | | | SIP#1
INVITE
180 Alerting
181 Call is Being Forwarded |
➔
⬅
⬅ | AS
No reply timer expires |
➔
⬅
➔
⬅
⬅
➔ | SIP#2
INVITE
180 Ringing
CANCEL/BYE
200 OK CANCEL/BYE
487 Request Terminated
ACK |
➔ | SIP#3
INVITE |
+| SIP#1
INVITE
180 Alerting
181 Call is Being Forwarded |
➔
⬅
⬅ | AS
No reply timer expires |
➔
⬅
➔
⬅
⬅
➔ | SIP#2
INVITE
180 Ringing
CANCEL/BYE
200 OK CANCEL/BYE
487 Request Terminated
ACK |
➔ | SIP#3
INVITE | | | | |
+
+| TSS
Netw/ASNotification/Originating user | TP
CDIV_N02_014 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/3 AND PICS 3/3
AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|--------------|-----------|--------------|--------------|--------|---|----------|--|--------------|---|---------------|--|--|--|------------------------|--|-----------------------------|---|--|--|--|--|--------------|--|--|--|---------------------|--|--|--|--------------------------|--|--|--|-------|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CFNR with applying diversion condition; originating user is notified.
When communication diversion occurs (served user does not respond) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a Privacy header set to "id" and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 408 and escaped Privacy header set to 'history', index = 1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = yes
Served user allows the presentation of his/her URI to originating user in diversion notification = no OR
Served user has subscribed to TIR in permanent mode | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
Privacy: id
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | → | → INVITE | |
| 180 Alerting | ← | ← 180 Ringing | |
| | No reply timer expires | |
| 181 Call is Being Forwarded | ← | | |
| | → CANCEL/BYE | |
| | ← 200 OK CANCEL/BYE | |
| | ← 487 Request Terminated | |
| | → ACK | |
| | | → INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | → | → INVITE | | 180 Alerting | ← | ← 180 Ringing | | | | No reply timer expires | | 181 Call is Being Forwarded | ← | | | | | → CANCEL/BYE | | | | ← 200 OK CANCEL/BYE | | | | ← 487 Request Terminated | | | | → ACK | | | | | → INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 180 Alerting | ← | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | No reply timer expires | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+**Rec. ITU-T Q.4004.2 (02/2016)** 15
+
+| TSS
Netw/ASNotification/Originating user | TP
CDIV_N02_015 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/3 AND PICS 3/3
AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|-----------|--------------|--------------|--------|---|--|----------|--|--------------|---|--|---------------|--|--|--|------------------------|--|--|-----------------------------|---|--|--|--|--|--|--|--------------|--|--|--|--|---------------------|--|--|--|--|--------------------------|--|--|--|--|-------|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CFNR with applying diversion condition; originating user is notified. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| When communication diversion occurs (served user does not respond) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing: - a P-Asserted-Identity header with the URI of the served user and
- a History-Info header
- including a first entry with the hi-targeted-to-URI of the served user, index = 1
- and
- including a second entry with the hi-targeted-to-URI of the diverted-to user, with a Privacy header set to "history", cause = 408, index = 1.1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = no
Served user allows the presentation of his/her URI to originating user in diversion notification = yes | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | SIP#2 | SIP#3 |
| INVITE | ➔ | | ➔ INVITE | |
| 180 Alerting | ← | | ← 180 Ringing | |
| | No reply timer expires | | |
| 181 Call is Being Forwarded | ← | | | |
| | | ➔ CANCEL/BYE | |
| | | ← 200 OK CANCEL/BYE | |
| | | ← 487 Request Terminated | |
| | | ➔ ACK | |
| | | | ➔ INVITE |
| | | | SIP#1 | | AS | SIP#2 | SIP#3 | INVITE | ➔ | | ➔ INVITE | | 180 Alerting | ← | | ← 180 Ringing | | | | No reply timer expires | | | 181 Call is Being Forwarded | ← | | | | | | | ➔ CANCEL/BYE | | | | | ← 200 OK CANCEL/BYE | | | | | ← 487 Request Terminated | | | | | ➔ ACK | | | | | | ➔ INVITE |
+| SIP#1 | | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | ➔ | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 180 Alerting | ← | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | No reply timer expires | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ➔ CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASDivertingUser/NotOrigUser | TP
CDIV_N02_016 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/4 AND PICS 3/3 | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------|--------------|--|-----------|--------------|--------------|--------|---|--|----------|--|--|--|--|-------------------------|--|--|--|--|-------|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CD (immediate response); originating user is not notified. | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| When communication diversion occurs (served user deflects call immediately) and if the notification procedures of the originating user is supported then no 181 (Call Is Being Forwarded) response shall be sent towards the originating user if the served users subscription option is set to: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no. | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = no | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | SIP#2 | SIP#3 |
| INVITE | ➔ | | ➔ INVITE | |
| | | ← 302 Moved Temporarily | |
| | | ➔ ACK | |
| | | | ➔ INVITE |
| | | | SIP#1 | | AS | SIP#2 | SIP#3 | INVITE | ➔ | | ➔ INVITE | | | | | ← 302 Moved Temporarily | | | | | ➔ ACK | | | | | | ➔ INVITE |
+| SIP#1 | | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | ➔ | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ➔ ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_017 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/4 AND
PICS 3/3
AND PICS 3/4
AND PICS 3/5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|----------------------------------------------------------------------------------|--------------|--|-----------|--------------|--------------|--------|---|--|----------|--|--|--|--|-------------------------|--|--|--|--|-------|--|-----------------------------|---|--|--|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CD (immediate response); originating user is notified.
When communication diversion occurs (served user deflects call immediately) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 480 and escaped Privacy header set to 'history', index = 1.1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = yes
Served user allows the presentation of his/her URI to originating user in diversion notification = yes
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
History-Info: <sip:SIP#2?Reason=SIP%3Bcause%3D302>;index=1,
<sip:SIP#3;cause=480?Privacy=history>;index=1.1
NOTE: According to [ITU-T Q.3620 v.1] clause 4.5.2.6.2.2.b: "If the diversion is based on a SIP response from the served user, a Reason header in escaped form shall be included in accordance with [IETF RFC 4244] ".
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | SIP#2 | SIP#3 |
| INVITE | → | | → INVITE | |
| | | ← 302 Moved Temporarily | |
| | | → ACK | |
| 181 Call is Being Forwarded | ← | | | |
| | | | → INVITE |
| | | | SIP#1 | | AS | SIP#2 | SIP#3 | INVITE | → | | → INVITE | | | | | ← 302 Moved Temporarily | | | | | → ACK | | 181 Call is Being Forwarded | ← | | | | | | | | → INVITE |
+| SIP#1 | | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_018 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/4 AND PICS 3/3
AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4 | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------|--------------|--------------|--------|---|----------|--|--|--|-------------------------|--|--|--|-------|--|--|--|--|----------|-----------------------------|---|--|--|
+| Test purpose
Communication forwarding using CD (immediate response); originating user is notified. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| When communication diversion occurs (served user deflects call immediately) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
- a P-Asserted-Identity header with the URI of the served user and
- a Privacy header set to "id" and
- a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user with a Privacy header set to "history", cause = 480, index = 1.1
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = no
Served user allows the presentation of his/her URI to originating user in diversion notification = no OR
Served user has subscribed to TIR in permanent mode | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
Privacy: id
History-Info: ;index=1,
;index=1.1
NOTE: According to [ITU-T Q.3620 v.1] clause 4.5.2.6.2.2.b: "If the diversion is based on a SIP response from the served user, a Reason header in escaped form shall be included in accordance with [IETF RFC 4244] ". | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | → | → INVITE | |
| | ← 302 Moved Temporarily | |
| | → ACK | |
| | | → INVITE |
| 181 Call is Being Forwarded | ← | | |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | → | → INVITE | | | | ← 302 Moved Temporarily | | | | → ACK | | | | | → INVITE | 181 Call is Being Forwarded | ← | | |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_019 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/4 AND PICS 3/3 AND
(PICS 3/5 OR PICS 4/3) AND PICS 3/4 | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------|--------------|-----------|--------------|--------------|--------|---|----------|--|--|--|-------------------------|--|--|--|-------|--|-----------------------------|---|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CD (immediate response); originating user is notified.
When communication diversion occurs (served user deflects call immediately) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a Privacy header set to "id" and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user with a Privacy header set to "history", cause = 480, index = 1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = yes
Served user allows the presentation of his/her URI to originating user in diversion notification = no OR
Served user has subscribed to TIR in permanent mode | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
Privacy: id
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | → | → INVITE | |
| | ← 302 Moved Temporarily | |
| | → ACK | |
| 181 Call is Being Forwarded | ← | | |
| | | → INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | → | → INVITE | | | | ← 302 Moved Temporarily | | | | → ACK | | 181 Call is Being Forwarded | ← | | | | | | → INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+
+Rec. ITU-T Q.4004.2 (02/2016) 19
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_020 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/4 AND PICS 3/3 AND (PICS 3/5 OR PICS 4/3) AND PICS 3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------|--|-----------|--------------|--------------|--------|---|--|----------|--|--|--|--|-------------------------|--|--|--|--|-------|--|-----------------------------|---|--|--|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CD (immediate response); originating user is notified.
When communication diversion occurs (served user deflects call immediately) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user with a Privacy header set to "history", cause = 480, index = 1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = no
Served user allows the presentation of his/her URI to originating user in diversion notification = yes | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | SIP#2 | SIP#3 |
| INVITE | → | | → INVITE | |
| | | ← 302 Moved Temporarily | |
| | | → ACK | |
| 181 Call is Being Forwarded | ← | | | |
| | | | → INVITE |
| | | | SIP#1 | | AS | SIP#2 | SIP#3 | INVITE | → | | → INVITE | | | | | ← 302 Moved Temporarily | | | | | → ACK | | 181 Call is Being Forwarded | ← | | | | | | | | → INVITE |
+| SIP#1 | | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_021 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/5 AND PICS 3/3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------|--------------|--|-----------|--------------|--------------|--------|---|--|----------|--|-------------|---|--|---------------|--|--|--|--|-------------------------|--|--|--|--|-------|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CD during alerting; originating user is not notified.
When communication diversion occurs (served user deflects call during alerting) and if the notification procedures of the originating user is supported then no 181 (Call Is Being Forwarded) response shall be sent towards the originating user if the served users subscription option is set to: Originating user receives notification that his communication has been diverted (forwarded or deflected) = no. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = no | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | SIP#2 | SIP#3 |
| INVITE | → | | → INVITE | |
| 180 Ringing | ← | | ← 180 Ringing | |
| | | ← 302 Moved Temporarily | |
| | | → ACK | |
| | | | → INVITE |
| | | | SIP#1 | | AS | SIP#2 | SIP#3 | INVITE | → | | → INVITE | | 180 Ringing | ← | | ← 180 Ringing | | | | | ← 302 Moved Temporarily | | | | | → ACK | | | | | | → INVITE |
+| SIP#1 | | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 180 Ringing | ← | | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_022 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/5
AND PICS 3/3
AND PICS 3/4
AND PICS 3/5 | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------|-----------|----------------------|-----------------------------------------------------------------------|------------------------------------------|
+| Test purpose
Communication forwarding using CD during alerting; originating user is notified. When communication diversion occurs (served user deflects call during alerting) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
- a P-Asserted-Identity header with the URI of the served user and
- a History-Info header
- including a first entry with the hi-targeted-to-URI of the served, index = 1
- and
- including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 487 and escaped Privacy header set to 'history', index = 1.1
| | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = yes
Served user allows the presentation of his/her URI to originating user in diversion notification = yes | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
History-Info: <sip:SIP#2>;index=1,
<sip:SIP#3; cause=487?Privacy=history>;index=1.1 | | | | | | | | | |
+| Comments: SIP#1
INVITE
180 Ringing
181 Call is Being Forwarded |
→
←
← | AS |
→
←
←
→ | SIP#2
INVITE
180 Ringing
302 Moved Temporarily
ACK | SIP#3
→ INVITE |
| | | | SIP#1
INVITE
180 Ringing
181 Call is Being Forwarded |
→
←
← | AS |
→
←
←
→ | SIP#2
INVITE
180 Ringing
302 Moved Temporarily
ACK | SIP#3
→ INVITE |
+| SIP#1
INVITE
180 Ringing
181 Call is Being Forwarded |
→
←
← | AS |
→
←
←
→ | SIP#2
INVITE
180 Ringing
302 Moved Temporarily
ACK | SIP#3
→ INVITE | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_023 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/5 AND PICS 3/3
AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|----------|----|--|-------|-------|--------|---|--|---|--------|--|-------------|---|--|---|-------------|--|--|--|--|---|-----------------------|--|--|--|--|---|-----|--|-----------------------------|---|--|--|--|----------|
+| Test purpose
Communication forwarding using CD during alerting; originating user is notified.
When communication diversion occurs (served user deflects call during alerting) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a Privacy header set to "id" and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user with a Privacy header set to "history", cause = 487, index = 1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = no
Served user allows the presentation of his/her URI to originating user in diversion notification = no OR
Served user has subscribed to TIR in permanent mode | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
Privacy: id
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | | SIP#2 | SIP#3 |
| INVITE | ➔ | | ➔ | INVITE | |
| 180 Ringing | ← | | ← | 180 Ringing | |
| | | ← | 302 Moved Temporarily | |
| | | ➔ | ACK | |
| 181 Call is Being Forwarded | ← | | | | ➔ INVITE |
| | | | SIP#1 | | AS | | SIP#2 | SIP#3 | INVITE | ➔ | | ➔ | INVITE | | 180 Ringing | ← | | ← | 180 Ringing | | | | | ← | 302 Moved Temporarily | | | | | ➔ | ACK | | 181 Call is Being Forwarded | ← | | | | ➔ INVITE |
+| SIP#1 | | AS | | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | ➔ | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 180 Ringing | ← | | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_024 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/5 AND PICS 3/3
AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4 | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-------|----|-------|-------|--------|---|----------|--|-------------|---|---------------|--|--|--|-------------------------|--|--|--|-------|--|---------------------------------|-------|--|--------------|
+| Test purpose
Communication forwarding using CD during alerting; originating user is notified.
When communication diversion occurs (served user deflects call during alerting) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a Privacy header set to "id" and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 487 and escaped Privacy header set to 'history', index = 1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = yes
Served user allows the presentation of his/her URI to originating user in diversion notification = no OR
Served user has subscribed to TIR in permanent mode | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
Privacy: id
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | → | → INVITE | |
| 180 Ringing | ← | ← 180 Ringing | |
| | ← 302 Moved Temporarily | |
| | → ACK | |
181 Call is Being Forwarded |
← | |
→ INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | → | → INVITE | | 180 Ringing | ← | ← 180 Ringing | | | | ← 302 Moved Temporarily | | | | → ACK | |
181 Call is Being Forwarded |
← | |
→ INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 180 Ringing | ← | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+|
181 Call is Being Forwarded |
← | |
→ INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotOrigUser | TP
CDIV_N02_025 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.4 | Selection expression
PICS 1/5 AND PICS 3/3
AND
(PICS 3/5
OR PICS 4/3) AND
PICS 3/4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------|-------|----|-------|-------|--------|---|----------|--|-------------|---|---------------|--|--|--|-------------------------|--|--|--|-------|--|-----------------------------|---|--|--|--|--|--|----------|
+| Test purpose
Communication forwarding using CD during alerting; originating user is notified. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| When communication diversion occurs (served user deflects call during alerting) and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user containing:
a P-Asserted-Identity header with the URI of the served user and
a History-Info header
including a first entry with the hi-targeted-to-URI of the served user, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user with a Privacy header set to "history", cause = 487, index = 1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Subscription options:
Originating user receives notification that his communication has been diverted (forwarded or deflected) = yes
Served user allows the presentation of diverted to URI to originating user in diversion notification = no
Served user allows the presentation of his/her URI to originating user in diversion notification = yes OR
Served user has subscribed to TIR in permanent mode | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
181 Call is Being Forwarded:
P-Asserted-Identity: SIP#2
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | → | → INVITE | |
| 180 Ringing | ← | ← 180 Ringing | |
| | ← 302 Moved Temporarily | |
| | → ACK | |
| 181 Call is Being Forwarded | ← | | |
| | | → INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | → | → INVITE | | 180 Ringing | ← | ← 180 Ringing | | | | ← 302 Moved Temporarily | | | | → ACK | | 181 Call is Being Forwarded | ← | | | | | | → INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 180 Ringing | ← | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 181 Call is Being Forwarded | ← | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+###### 6.2.1.2.2 Diverted-to user
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_001 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2 4.5.2.6.2.4 | Selection expression
PICS 1/1 AND PICS
4/1 AND
PICS 3/6 | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|------------------------------------------------------------|------------------------------------------------------------------|-------|----|-------|-------|--------|---|--|--|--|--|--|----------|
+| Test purpose
Communication Forwarding using CFU. | | | | | | | | | | | | | | | |
+| The served user subscribes to the CFU service. The served user does not subscribe to OIR in permanent mode and the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "yes". | | | | | | | | | | | | | | | |
+| Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user (not) including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "302" in the Request URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 302, index = 1.1. | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 302 SIP/2.0
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | → | | |
| | | → INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | → | | | | | | → INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | | | | | |
+| INVITE | → | | | | | | | | | | | | | | |
+| | | | → INVITE | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_002 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4 | Selection expression
PICS 1/2 AND PICS 4/1
AND
PICS 3/6 | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|--------------|-----------|--------------|--------------|--------|---|--|--|--|--|---|--------|
+| Test purpose
Communication Forwarding using CFB NDUB. The served user subscribes to the CFB service and is in NDUB condition. The served user does not subscribe to OIR in permanent mode and the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "yes".
Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which is NDUB (not) including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "486" in the Request URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 486, index = 1.1.
| | | | | | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 486 SIP/2.0
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | |
+| NOTE: According to [ITU-T Q.3620 v.1], clause 4.5.2.6.2.2.b: "If the diversion is based on a SIP response from the served user, a Reason header in escaped form shall be included in accordance with [IETF RFC 4244] ". | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | ➔ | | |
| | ➔ | INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | ➔ | | | | | ➔ | INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | | | | | |
+| INVITE | ➔ | | | | | | | | | | | | | | |
+| | | ➔ | INVITE | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_003 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4 | Selection expression
PICS 1/6 AND PICS 4/1
AND
PICS 3/6 | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|--------------|-----------|--------------|--------------|--------|---|--|--|--|--|---|--------|
+| Test purpose
Communication Forwarding using CFNL. The served user subscribes to the CFNL service and has not logged in. The served user does not subscribe to OIR in permanent mode and the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "yes".
Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which is not logged in (not) including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "404" in the Request URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 404, index = 1.1.
| | | | | | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 404 SIP/2.0
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | ➔ | | |
| | ➔ | INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | ➔ | | | | | ➔ | INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | | | | | |
+| INVITE | ➔ | | | | | | | | | | | | | | |
+| | | ➔ | INVITE | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_004 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4 | Selection expression
PICS 1/2 AND PICS 4/1
AND
PICS 3/6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|---------------|--------------|-----------|--|--------------|--------------|--------|---|--|---|--------|--|--|--|--|---|---------------|--|--|--|--|---|-----|--|--|--|--|--|--|----------|
+| Test purpose
Communication Forwarding using CFB UDUB.
The served user subscribes to the CFB service and is in UDUB condition. The served user does not subscribe to OIR in permanent mode and the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "yes" .
Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which is UDUB (not) including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "486" in the Request URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user and a Reason header indicating cause 486, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 486, index = 1.1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 486 SIP/2.0
History-Info: ;index=1,
;index=1.1
NOTE: According to [b-ETSI TS 124 604] clause 4.5.2.6.2.2.b: "If the diversion is based on a SIP response from the served user, a Reason header in escaped form shall be included in accordance with [IETF RFC 4244] ". | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | | SIP#2 | SIP#3 |
| INVITE | ➔ | | ➔ | INVITE | |
| | | ⬅ | 486 Busy Here | |
| | | ➔ | ACK | |
| | | | | ➔ INVITE |
| | | | SIP#1 | | AS | | SIP#2 | SIP#3 | INVITE | ➔ | | ➔ | INVITE | | | | | ⬅ | 486 Busy Here | | | | | ➔ | ACK | | | | | | | ➔ INVITE |
+| SIP#1 | | AS | | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | ➔ | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ⬅ | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | ➔ INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_005 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4 | Selection expression
PICS 1/3 AND PICS 4/1
AND
PICS 3/6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|------------------------|---|--------------|--|--------------|--|--------------|--------|---|--|---|--------|--|--|-------------|---|--|---|-------------|--|--|--|--|------------------------|--|--|--|--|--|--|--|---|------------|--|--|--|--|--|---|-------------------|--|--|--|--|--|---|------------------------|--|--|--|--|--|---|-----|--|--|--|--|--|--|--|---|--------|
+| Test purpose
Communication Forwarding using CFNR. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| The served user subscribes to the CFNR and does not reply. The served user does not subscribe to OIR in permanent mode and the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "yes".
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which does not reply (not) including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "408" in the Request URI and containing a History-Info header
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| including a first entry with the hi-targeted-to-URI of the served user, index = 1
and
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 408, index = 1.1.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| The initial communication to the served user is terminated with a CANCEL or a BYE request with a Reason header with protocol set to SIP and the cause set to 408.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE: sip:SIP#3@example.com; cause = 408 SIP/2.0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| History-Info: <sip:SIP#2;index=1,
<sip:SIP#3;cause=408>;index=1.1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CANCEL/BYE: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Reason: SIP; cause=408
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | | SIP#2 | | SIP#3 |
| INVITE | ➔ | | ➔ | INVITE | | |
| 180 Ringing | ← | | ← | 180 Ringing | | |
| | No reply timer expires | | | | |
| | | ➔ | CANCEL/BYE | | |
| | | ← | 200 OK CANCEL/BYE | | |
| | | ← | 487 Request Terminated | | |
| | | ➔ | ACK | | |
| | | | | ➔ | INVITE |
| | | | SIP#1 | | AS | | SIP#2 | | SIP#3 | INVITE | ➔ | | ➔ | INVITE | | | 180 Ringing | ← | | ← | 180 Ringing | | | | | No reply timer expires | | | | | | | | ➔ | CANCEL/BYE | | | | | | ← | 200 OK CANCEL/BYE | | | | | | ← | 487 Request Terminated | | | | | | ➔ | ACK | | | | | | | | ➔ | INVITE |
+| SIP#1 | | AS | | SIP#2 | | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | ➔ | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 180 Ringing | ← | | ← | 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | No reply timer expires | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ➔ | CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 200 OK CANCEL/BYE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 487 Request Terminated | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_006 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4
Reference
[IETF RFC 4244]
4.3.3.1.2 | Selection expression
PICS 1/4 AND PICS
4/1 AND
PICS 3/6 | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-------|----|-------|-------|--------|---|----------|--|--|--|-------------------------|--|--|--|-------|--|--|--|--|----------|
+| Test purpose
Communication Forwarding using CD (immediate response), | | | | | | | | | | | | | | | | | | | | | | | |
+| The served user subscribes to the CD service and immediately diverts the communication. The served user does not subscribe to OIR in permanent mode and the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "yes".
Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which immediately diverts the communication (not) including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "480" in the Request URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user and a Reason header indicating cause 302, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 480, index = 1.1.
| | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 480 SIP/2.0
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments: | SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | → | → INVITE | |
| | ← 302 Moved Temporarily | |
| | → ACK | |
| | | → INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | → | → INVITE | | | | ← 302 Moved Temporarily | | | | → ACK | | | | | → INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | |
+| | | | → INVITE | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_007 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4
Reference
[IETF RFC 4244]
4.3.3.1.2 | Selection expression
PICS 1/5 AND PICS
4/1 AND
PICS 3/6 | | | | | | | | | | | | | | | | | | | | | | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-------|----|-------|-------|--------|---|----------|--|-------------|---|---------------|--|--|--|-------------------------|--|--|--|-------|--|--|--|--|----------|
+| Test purpose
Communication Forwarding using CD during alerting. | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| The served user subscribes to the CD service and diverts the communication during alerting. The served user does not subscribe to OIR in permanent mode and the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "yes".
Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which diverts the communication during alerting (not) including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "487" in the Request URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user and a Reason header indicating cause 302, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 487, index = 1.1.
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 487 SIP/2.0
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments: | SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | → | → INVITE | |
| 180 Ringing | ← | ← 180 Ringing | |
| | ← 302 Moved Temporarily | |
| | → ACK | |
| | | → INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | → | → INVITE | | 180 Ringing | ← | ← 180 Ringing | | | | ← 302 Moved Temporarily | | | | → ACK | | | | | → INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | → | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | | |
+| 180 Ringing | ← | ← 180 Ringing | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | ← 302 Moved Temporarily | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | → ACK | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | → INVITE | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_008 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4 | Selection expression
PICS 1/7 AND PICS
4/1 AND
PICS 3/6 | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------------------------------------------------------|------------------------------------------------------------------|--------------|-----------|--------------|--------------|--------|---|--|----------|
+| Test purpose
Communication Forwarding using CFNRc. The served user subscribes to the CFNRc service and is not reachable. The served user does not subscribe to OIR in permanent mode and the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "yes".
Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which is not reachable (not) including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "503" in the Request URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 503, index = 1.1.
NOTE: According to [ITU-T Q.3620 v.1] clause 4.5.2.6.2.2.b: "If the diversion is based on a SIP response from the served user, a Reason header in escaped form shall be included in accordance with [IETF RFC 4244]".
| | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 503 SIP/2.0
History-Info: ;index=1.1 | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | → | | → INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | → | | → INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | |
+| INVITE | → | | → INVITE | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_009 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4 | Selection expression
PICS 1/1 AND PICS 4/1
AND
PICS 3/6 | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------------------------------------------------------|------------------------------------------------------------------|--------------|-----------|--------------|--------------|--------|---|--|----------|
+| Test purpose
Communication Forwarding using CFU. The served user subscribes to the CFU service. The served user subscribes to OIR in permanent mode or the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "no".
Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user (not) including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "302" in the Request URI, indicating in the To header the diverted-to URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 302, index = 1.1.
| | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 302 SIP/2.0
To:
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | → | | → INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | → | | → INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | |
+| INVITE | → | | → INVITE | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_010 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4 | Selection expression
PICS 1/2 AND PICS 4/1
AND
PICS 3/6 | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------------------------------------------------------|------------------------------------------------------------------|--------------|-----------|--------------|--------------|--------|---|--|----------|
+| Test purpose
Communication Forwarding using CFB NDUB. | | | | | | | | | | | |
+| The served user subscribes to the CFB service and is in NDUB condition. The served user subscribes to OIR in permanent mode or the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "no".
| | | | | | | | | | | |
+| Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which is NDUB not including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "486" in the Request URI, indicating in the To header the diverted-to URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 486, index = 1.1.
| | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 486 SIP/2.0
To:
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | ➔ | | ➔ INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | ➔ | | ➔ INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | |
+| INVITE | ➔ | | ➔ INVITE | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_011 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4 | Selection expression
PICS 1/6 AND PICS 4/1
AND
PICS 3/6 | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------------------------------------------------------|------------------------------------------------------------------|--------------|-----------|--------------|--------------|--------|---|--|----------|
+| Test purpose
Communication Forwarding using CFNL. | | | | | | | | | | | |
+| The served user subscribes to the CFNL service and has not logged in. The served user subscribes to OIR in permanent mode or the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "no".
| | | | | | | | | | | |
+| Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which is not logged in not including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "404" in the Request URI, indicating in the To header the diverted-to URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 404, index = 1.1.
| | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 404 SIP/2.0
To:
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | |
+| Comments:
| SIP#1 | AS | SIP#2 | SIP#3 |
| INVITE | ➔ | | ➔ INVITE |
| | | | SIP#1 | AS | SIP#2 | SIP#3 | INVITE | ➔ | | ➔ INVITE |
+| SIP#1 | AS | SIP#2 | SIP#3 | | | | | | | | |
+| INVITE | ➔ | | ➔ INVITE | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_012 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4 | Selection expression
PICS 1/2 AND PICS 4/1
AND
PICS 3/6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|---------------|---|--------------|--|--------------|--|--------------|--------|---|--|---|--------|--|--|--|--|--|---|---------------|--|--|--|--|--|---|-----|--|--|--|--|--|--|--|---|--------|
+| Test purpose
Communication Forwarding using CFB UDUB.
The served user subscribes to the CFB service and is in UDUB condition. The served user subscribes to OIR in permanent mode or the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "no" .
Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which is UDUB not including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "486" in the Request URI, indicating in the To header the diverted-to URI and containing a History-Info header
including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history" and a Reason header indicating cause 486, index = 1
and
including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 486, index = 1.1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values:
INVITE: sip:SIP#3@example.com; cause = 486 SIP/2.0
To:
History-Info: ;index=1,
;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments:
| SIP#1 | | AS | | SIP#2 | | SIP#3 |
| INVITE | ➔ | | ➔ | INVITE | | |
| | | ← | 486 Busy Here | | |
| | | ➔ | ACK | | |
| | | | | ➔ | INVITE |
| | | | SIP#1 | | AS | | SIP#2 | | SIP#3 | INVITE | ➔ | | ➔ | INVITE | | | | | | ← | 486 Busy Here | | | | | | ➔ | ACK | | | | | | | | ➔ | INVITE |
+| SIP#1 | | AS | | SIP#2 | | SIP#3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE | ➔ | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ← | 486 Busy Here | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | ➔ | ACK | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | | ➔ | INVITE | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| TSS
Netw/ASdivertingUser/NotTermUser | TP
CDIV_N03_013 | Reference
[ITU-T Q.3620 v.1]
4.5.2.6.2.2
4.5.2.6.2.4 | Selection expression
PICS 1/3 AND PICS 4/1
AND
PICS 3/6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------------------------------------------------------|------------------------------------------------------------------|-------------------------------|---|--------------|--|--------------|--|--------------|--------|---|--|---|--------|--|--|-------------|---|--|---|-------------|--|--|--|--|--|------------------------|--|--|--|--|--|--|---|------------|--|--|--|--|--|---|-------------------|--|--|--|--|--|---|-------------------------------|--|--|--|--|--|---|-----|--|--|--|--|--|--|--|---|--------|
+| Test purpose
Communication Forwarding using CFNR. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| The served user subscribes to the CFNR and does not reply. The served user subscribes to OIR in permanent mode or the subscription option "Served user allows the presentation of his/her URI to diverted-to user" is set to value "no".
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Ensure that the IUT, on receipt of an INVITE request (diversion status DIV_VA, see Table 3) for the served user which does not reply not including a History-Info header, applies communication diversion and forwards the INVITE request towards the diverted-to user containing the cause value "408" in the Request URI, indicating in the To header the diverted-to URI and containing a History-Info header
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| including a first entry with the hi-targeted-to-URI of the served user with a Privacy header set to "history", index = 1
and
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| including a second entry with the hi-targeted-to-URI of the diverted-to user, cause = 408, index = 1.1.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| The initial communication to the served user is terminated with a CANCEL or a BYE request with a Reason header with protocol set to SIP and the cause set to 408.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| SIP header values: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| INVITE: sip:SIP#3@example.com; cause = 408 SIP/2.0
To:
History-Info: ;index=1.1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CANCEL/BYE:
Reason: SIP; cause=408 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Comments: