Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 17875-04: Private Integrated Services Network – Inter-exchange Signalling Protocol for Synchronous Bearer Services
A comprehensive technical overview of the signalling protocol for synchronous bearer services in PISN environments
Scope of ISO/IEC 17875-04
ISO/IEC 17875-04 is part of the ISO/IEC 17874-17876 series that defines the architecture, service description, and signalling protocol for Private Integrated Services Networks (PISNs). Specifically, this standard specifies the inter-exchange signalling protocol for synchronous bearer services. Synchronous bearer services are characterized by constant bit rate, timing information transfer, and low delay, making them ideal for voice and high-quality audio/video applications over circuit-switched connections. The protocol provides the means to establish, maintain, and release synchronous bearer connections between PISN exchanges. It also supports the activation, deactivation, and operation of supplementary services such as call transfer, call hold, and conference calling. The protocol operates between two PISN nodes that communicate via an inter-exchange interface using the QSIG signalling system defined in the broader PISN framework. The standard addresses both basic call control and the functional procedures necessary for seamless, reliable operation in multi-vendor environments.
The scope encompasses the following aspects:
- Definition of the message format, information elements, and parameter semantics for synchronous bearer call control.
- Protocol procedures for call establishment (including direct access, by-pass, and overlap sending), call clearing (normal and abnormal), and supplementary service invocation.
- State definitions and state transition tables for both the source and destination PISN exchanges.
- Timer specifications to ensure network reliability and avoidance of call hang-ups.
- Conformance requirements and test structures as described in the associated reference standard ISO/IEC 17876.
Technical Requirements
Message Categories and Functions
The protocol defines a set of messages grouped into three categories: call establishment, call clearing, and supplementary services. The table below summarizes key messages, their direction, and functions.
| Message | Direction | Function | Associated Timers |
|---|---|---|---|
| SETUP | Forward | Initiates a call; includes bearer capability, called party number, and optional supplementary service indicators. | T301 (call establishment timeout) |
| CONNECT | Backward | Indicates that the called party has answered the call. | T302 (connect timer) |
| ALERTING | Backward | Indicates that the called device is ringing. | None |
| DISCONNECT | Both | Clears a call; includes cause diagnostic information. | T305 (disconnect timeout) |
| RELEASE | Both | Confirms call clearing; triggers release of resources. | T308 (release timeout) |
| FACILITY | Both | Transports supplementary service control information (e.g., call transfer request). | T304 (facility timeout) |
Protocol Procedures and State Machines
The protocol is formally defined using SDL (Specification and Description Language) and state transition diagrams. Each PISN exchange implements a finite state machine for each call instance. The states include Null, Call Initiated, Incoming Call Proceeding, Active, Disconnect Request, etc. Procedures are defined for normal operations and exceptional conditions (e.g., timeouts, resource unavailable). The standard mandates specific actions for each stimulus.
Synchronous Bearer Capabilities
To ensure synchronous operation, the protocol requires explicit negotiation of bearer capabilities during call setup. Parameters such as information transfer capability (speech, 64 kbit/s unrestricted digital), transfer mode (circuit), transfer rate, and synchronization attributes are encoded in the SETUP message. The receiving exchange must verify compatibility with its resources and respond accordingly.
Timers and Error Handling
Several timers are specified to regulate protocol behavior. For example, T301 is used to supervise the call establishment phase from when the SETUP is sent until a response is received. Default values and allowable ranges are provided to accommodate different network configurations. Improper timer settings can lead to premature call clearing or excessive delay; therefore the standard provides guidelines for selection based on network propagation and processing delays.
Caution: When adapting the protocol to IP-based backbones (e.g., using T1/E1 trunking over packet networks), the default timer values may need adjustment to account for additional jitter and latency. Always refer to Annex C of the standard for guidance on modifying timers for non-ISDN transport.
Implementation Highlights
Implementing ISO/IEC 17875-04 typically involves a layered architecture: the protocol stack sits above the physical/link layer (e.g., Q.921 for ISDN D-channel) and uses the services provided by the network layer. The implementation must support the state machine and message processing logic. Application Program Interfaces (APIs) abstract the protocol from the call control application.
Key implementation considerations include:
- Multi-vendor interoperability: Adherence to the protocol as specified is essential. Early participation in interoperability workshops helps detect ambiguities.
- Supplementary service integration: The protocol supports generic procedures (FACILITY, REGISTER messages) for supplementary services. Design the protocol handler to be extensible without modifying core call control logic.
- Performance: Minimize message processing delay and ensure sufficient timer resolution. Use real-time operating system techniques if needed.
- PICS creation: Provide a Protocol Implementation Conformance Statement per ISO/IEC 17876. This document declares which optional features are implemented and which timers have been modified.
Best practice: A standardized PICS simplifies the certification process and helps end-users verify capability. Many procurement contracts require a PICS, and its accuracy directly impacts project timelines and acceptance testing.
Warning: Skipping conformance testing or failing to document deviations from the standard can lead to serious operational issues, such as calls being dropped across PBX boundaries and unavailability of supplementary services. This may result in breach of service level agreements and costly remediation.
Compliance and Certification Notes
ISO/IEC 17875-04 has been adopted nationally by many countries. For instance, Canada has issued CAN/CSA-ISO/IEC 17875-04, which is identical to the international standard. In Europe, the standard is integrated into the EN series (e.g., EN 301 298 for PISN). Compliance is typically verified through independent testing laboratories that execute a conformance test suite derived from the standard’s test specification (usually described in ISO/IEC 17876).
Certification process involves:
- Submission of PICS and protocol implementation details.
- Execution of automated test cases covering basic call, clearing, and supplementary service procedures.
- Negative testing: verifying behavior under error conditions (invalid messages, illegal states).
- Performance test: determining if timer values meet requirements.
- Documentation of test results and issuance of conformance report.
It is important to note that while conformance to the protocol specification is essential for interoperability, it does not guarantee functional correctness of all supplementary services. Some services require additional specifications (e.g., call transfer is defined in ISO/IEC 17878). Vendors are encouraged to test complete service bundles in multi-vendor environments.
Tip: If your organisation is developing a PISN product, consider engaging a certified test laboratory early in the design phase to identify compliance gaps before final production. This reduces rework and speeds time-to-market.
Frequently Asked Questions
Q: What distinguishes synchronous bearer services from other PISN bearer services?
A: Synchronous bearer services provide constant bit rate and timing preservation, which are essential for voice and circuit-switched video. They are defined using circuit transfer mode and 64 kbit/s (or multiples) unrestricted digital rates. In contrast, packet-based services (as defined in other parts) handle variable bit rate streams with relaxed timing requirements. The protocol for synchronous services uses stricter timer and state machine rules to ensure connection integrity.
A: Synchronous bearer services provide constant bit rate and timing preservation, which are essential for voice and circuit-switched video. They are defined using circuit transfer mode and 64 kbit/s (or multiples) unrestricted digital rates. In contrast, packet-based services (as defined in other parts) handle variable bit rate streams with relaxed timing requirements. The protocol for synchronous services uses stricter timer and state machine rules to ensure connection integrity.
Q: Is ISO/IEC 17875-04 still relevant in modern VoIP-centric networks?
A: While many PISN installations are transitioning to IP telephony (based on SIP or H.323), the standard remains relevant for interconnecting with legacy PBXs and for ensuring backward compatibility. Many TDM trunks still use circuit-switched technology. Furthermore, the signalling concepts in ISO/IEC 17875-04 influence the design of interworking functions between TDM and packet-switched domains.
A: While many PISN installations are transitioning to IP telephony (based on SIP or H.323), the standard remains relevant for interconnecting with legacy PBXs and for ensuring backward compatibility. Many TDM trunks still use circuit-switched technology. Furthermore, the signalling concepts in ISO/IEC 17875-04 influence the design of interworking functions between TDM and packet-switched domains.
Q: How often is the standard updated, and what revision is current?
A: The standard is maintained by ISO/IEC JTC 1/SC 6. The current version is Edition 2:2004 (as indicated by the “04” suffix), which remains stable. Users should monitor the ISO and CSA websites for corrigenda and amendments. No major revision is currently under development, but the technical committee accepts feedback for future editions.
A: The standard is maintained by ISO/IEC JTC 1/SC 6. The current version is Edition 2:2004 (as indicated by the “04” suffix), which remains stable. Users should monitor the ISO and CSA websites for corrigenda and amendments. No major revision is currently under development, but the technical committee accepts feedback for future editions.
Q: What role does CAN/CSA play in this standard?
A: The Canadian Standards Association (CSA) adopts international standards as national standards of Canada. CAN/CSA-ISO/IEC 17875-04 is identical to the ISO/IEC edition. It carries the force of a Canadian national standard, which may be referenced in contracts, regulations, and procurement for telecommunications equipment in Canada.
A: The Canadian Standards Association (CSA) adopts international standards as national standards of Canada. CAN/CSA-ISO/IEC 17875-04 is identical to the ISO/IEC edition. It carries the force of a Canadian national standard, which may be referenced in contracts, regulations, and procurement for telecommunications equipment in Canada.
Understanding and implementing ISO/IEC 17875-04 is essential for any organization involved in private