Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 13872-04: Profile Mapping for Inter-Exchange Signalling in Private Integrated Services Networks
Technical requirements, implementation highlights, and compliance notes for IEC 13872-04 (ISO/IEC 13872-04) PISN inter-exchange signalling profile mapping.
Scope of IEC 13872-04
IEC 13872-04 is an international standard developed jointly by the International Electrotechnical Commission (IEC) and the International Organization for Standardization (ISO) as part of the ISO/IEC 13872 series. This part specifies the profile mapping for the inter-exchange signalling protocol within Private Integrated Services Networks (PISN). It defines how the QSIG signalling messages (basic call and call-independent supplementary services) are mapped onto the underlying signalling transport mechanisms, enabling interoperability between Private Integrated Services Network Exchanges (PINX) from different vendors. The standard applies to both analog and digital trunk interfaces commonly used in enterprise telecommunication networks.
Technical Requirements
2.1 Protocol Layering and Mapping
IEC 13872-04 mandates a strict layering model that maps the abstract QSIG protocol onto the transport elements of the ITU-T Q.931 and Q.921 recommendations. The standard defines three mapping levels:
- Layer 3 to Layer 2 mapping — message types are assigned to specific link layer frame types (I-frames, S-frames).
- Layer 2 to Layer 1 mapping — the data link layer uses the Q.921 protocol with a Service Access Point Identifier (SAPI) reserved for PISN signalling.
- Layer 3 message encoding — each information element (IE) is assigned a presence requirement (mandatory or optional) and allowed value ranges.
| QSIG Message | Call Phase | Transport Frame Type |
|---|---|---|
| SETUP | Call establishment | I-frame (Q.921) |
| CONNECT | Call acceptance | I-frame (Q.921) |
| RELEASE | Call clearing | I-frame (Q.921) |
| FACILITY | Supplementary service | I-frame or UI-frame |
| STATUS | Error handling | S-frame (RR/RNR) |
2.2 Mandatory Information Elements
For a SETUP message, the standard requires the following IEs to be present and correctly encoded:
| Information Element | Length (bytes) | Allowed Values |
|---|---|---|
| Protocol Discriminator | 1 | 0x08 (PISN) |
| Call Reference | 2–4 | Unique per call |
| Message Type | 1 | 0x05 |
| Bearer Capability | 4–6 | 64 kbps, speech/data |
| Channel Identification | 2–3 | Timeslot number |
2.3 Supplementary Service Mapping
The standard also specifies how supplementary services (e.g., Call Completion to Busy Subscriber, Call Transfer) are encapsulated within the FACILITY message. Each service is identified by an Operation Value code, and the mapping must preserve the format defined in the corresponding supplementary service standard (e.g., ISO/IEC 13872-41).
Implementation Highlights
Adopting IEC 13872-04 requires careful attention to protocol layering and state machine integration. The following tips can help streamline development and testing.
Tip: Use a dedicated signalling processor module that implements the Q.921/Q.931 lower layers. This separation allows the upper-layer QSIG logic to focus on call control and supplementary services, simplifying profile mapping compliance.
Warning: The “Connected Number” IE is optional but if used, it must exactly follow the allowed length and coding rules of clause 6.2.4. Mis-encoding can cause the remote side to reject an otherwise valid CONNECT message.
Best Practice: Implement a comprehensive PICS (Protocol Implementation Conformance Statement) early in the development cycle. Use it as a checklist during unit testing to ensure all mandatory features are present and optional features are correctly declared.
Critical: Do not assume that all IEs allowed in basic Q.931 are valid in the profile mapping. IEC 13872-04 strictly restricts the presence of certain IEs (e.g., NPI, AOC information) in specific message types. Violation can cause interoperability failures.
Compliance Notes
Conformance to IEC 13872-04 is assessed through static and dynamic testing procedures defined in the companion test standard (IEC 13872-05). The compliance framework covers three main areas:
- Static Conformance Review: Verification of the PICS against the mandatory requirements in the main standard. Any deviation from mandatory IEs or message sequences must be documented.
- Dynamic Conformance Testing: Automated test scripts emulate PINX behaviour and validate that the implementation under test (IUT) follows the correct state machine transitions and message encodings.
- Interoperability Testing: Ad-hoc tests between two PINX implementations to verify end-to-end call establishment and supplementary service execution.
| Test Group | Test Item | Reference Clause |
|---|---|---|
| Layer 3 Mapping | Correct assignment of protocol discriminator and call reference length | 5.2 |
| Signalling Procedures | Basic call SETUP → CONNECT sequence | 6.1 – 6.3 |
| Supplementary Services | CCBS FACILITY request/response mapping | 7.2 |
| Error Handling | Invalid message type reception | 8.3 |
Annex A of the standard provides a full test suite structure and is essential for laboratory conformance validation. Laboratories accredited to ISO/IEC 17025 can issue certificates of compliance based on IEC 13872-05 testing.
Frequently Asked Questions
Q: What is the main purpose of IEC 13872-04?
A: It defines the profile mapping for inter-exchange signalling in Private Integrated Services Networks (PISN). This standard ensures that PINX from different vendors can exchange call control and supplementary service signals in a consistent, interoperable manner.
A: It defines the profile mapping for inter-exchange signalling in Private Integrated Services Networks (PISN). This standard ensures that PINX from different vendors can exchange call control and supplementary service signals in a consistent, interoperable manner.
Q: Is IEC 13872-04 a standalone standard?
A: No, it is part of a larger series. It depends on the baseline protocol defined in IEC 13872-01 (Generic inter-exchange signalling) and interacts with other parts (e.g., 13872-41 for supplementary services). The test methods are provided in IEC 13872-05.
A: No, it is part of a larger series. It depends on the baseline protocol defined in IEC 13872-01 (Generic inter-exchange signalling) and interacts with other parts (e.g., 13872-41 for supplementary services). The test methods are provided in IEC 13872-05.
Q: How does IEC 13872-04 differ from the generic Q.SIG specification?
A: Q.SIG is an informal umbrella term for several standards. IEC 13872-04 is a formal, normative profile mapping that specifies exactly how Q.SIG concepts (message types, IEs, state machines) are applied to a concrete transport stack (Q.921/Q.931). It removes ambiguity and adds mandatory constraints for uniform implementation.
A: Q.SIG is an informal umbrella term for several standards. IEC 13872-04 is a formal, normative profile mapping that specifies exactly how Q.SIG concepts (message types, IEs, state machines) are applied to a concrete transport stack (Q.921/Q.931). It removes ambiguity and adds mandatory constraints for uniform implementation.
Q: What is the relationship between IEC 13872-04 and ISO/IEC 13872-04?
A: They are technically identical. The IEC and ISO jointly developed the standard; national adoption bodies (e.g., CSA, ANSI) may issue national equivalents. The number “IEC 13872-04” is used in this article for brevity.
A: They are technically identical. The IEC and ISO jointly developed the standard; national adoption bodies (e.g., CSA, ANSI) may issue national equivalents. The number “IEC 13872-04” is used in this article for brevity.
© 2026 International Electrotechnical Commission. This article is for informational purposes only and does not replace the official standard text.