Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
CAN/CSA-ISO/IEC 15431-04: Personal User Mobility in Private Integrated Services Networks
Technical Overview of the Supplementary Service for PISN User Mobility and Registration
The standard CAN/CSA-ISO/IEC 15431-04 (adopted from ISO/IEC 15431:2004) defines the Personal User Mobility (PUM) supplementary service for Private Integrated Services Networks (PISN). This specification is part of the broader suite of PISN standards that enable advanced telecommunication features across private networks, including corporate intranet telephony and campus-wide communication systems. PUM allows users to maintain their identity, personal data, and subscribed services when moving between terminals or locations within the PISN environment, thereby ensuring seamless communication in dynamic work scenarios.
Scope and Application
The standard applies to the signalling protocol at the reference point between a Private Integrated Services Network (PISN) and another network (e.g., another PISN, a public ISDN, or a PSTN). It specifically addresses the PUM supplementary service, which enables a mobile user to register their presence at a terminal and temporarily associate their personal communication profile with that terminal.
Key applications include:
- Hot-desking environments where employees use different workstations daily.
- Campus or multi-site enterprises requiring consistent user profiles across branches.
- Home-office or remote work integration into corporate PISN.
The standard aligns with the functional model and information flows described in the PISN framework (ISO/IEC 15431 is part of the same series as ISO/IEC 15428 and ISO/IEC 15432). It is intended for network designers, equipment manufacturers, and service providers who need to implement interoperable mobility features.
Tip: CAN/CSA-ISO/IEC 15431-04 is the Canadian adoption of the international standard. While technically identical, certification and marking requirements may differ in Canada.
Technical Requirements and Architecture
Functional Model
The standard defines two main entities: the PUM User (the mobile subscriber) and the PUM Server (the network entity managing registration, profile retrieval, and service invocation). Communication between these entities is modelled as a series of information flows across the reference point R (between PISN and another network).
Information Flows
The following table summarises the mandatory information flows for PUM registration and deregistration as specified in the standard:
| Information Flow | Direction | Description |
|---|---|---|
| PUM_REGISTER | User → Server | Request to associate the user’s profile with a specific terminal address |
| PUM_REGISTER_ACK | Server → User | Positive acknowledgment including profile activation confirmation |
| PUM_DEREGISTER | User → Server | Request to remove the profile from the current terminal |
| PUM_DEREGISTER_ACK | Server → User | Confirmation of successful profile removal |
| PUM_INTERROGATE | User → Server | Query current registration status and profile parameters |
Signalling Protocol
The signalling uses the QSIG protocol stack at the reference point. The standard defines the message formats, data elements (e.g., user identity, terminal identity, profile ID), and control procedures. Key requirements include:
- Transport of PUM-related elements using the QSIG generic transport capability.
- Use of Supplementary Service Identifier (SSID) code points for PUM operations.
- Mandatory support for error handling (e.g., registration denied, timeout).
Important: Implementers must ensure compatibility with the underlying QSIG baseline (ISO/IEC 11582) and any applicable national amendments for CAN/CSA certification.
Implementation Highlights
Integrating PUM into a PISN requires careful attention to:
- Profile Storage: The PUM Server must maintain a secure database of user profiles, including service restrictions, forwarding numbers, and authentication credentials.
- User Authentication: The standard recommends but does not mandate authentication; however, for deployment in secure environments, implementers should add authentication mechanisms (e.g., PIN or PKI) before issuing PUM_REGISTER requests.
- Multi-Terminal Registration: While a user can register at only one terminal at a time, the standard allows for different types of registration (e.g., basic, extended) depending on network policy.
- Interworking with PSTN/ISDN: If the PISN interconnects with external networks, the PUM service must be mapped appropriately (e.g., using CLIP or forwarding indicators).
Best Practice: Test PUM registration and deregistration flows under realistic conditions, including simultaneous call scenarios, to ensure no service disruption.
Compliance and Testing Considerations
Conformance to CAN/CSA-ISO/IEC 15431-04 is evaluated through:
- Protocol conformance tests as defined in the associated test suite (ISO/IEC 15432).
- Interoperability testing between different manufacturers’ equipment (e.g., PBX, IP-PBX).
- Functional testing of PUM supplementary service features (registration, deregistration, interrogation) across the reference point.
In Canada, certification is managed by the CAN/CSA marking program. Products claiming compliance must be tested by an accredited laboratory and demonstrate full alignment with the standard’s mandatory requirements. Additionally, any deviations from the international base standard due to national regulations (e.g., numbering plan, emergency call handling) must be documented in the supplier’s declaration.
Non-Compliance Risk: Equipment that fails to handle PUM_DEREGISTER correctly can lead to persistent profile associations, causing security and billing issues. Always verify error handling routines.
Frequently Asked Questions
Q: Is CAN/CSA-ISO/IEC 15431-04 identical to the international ISO/IEC 15431:2004?
A: Yes, the Canadian adoption is technically equivalent to the international standard. Any modifications are limited to editorial changes and national references (e.g., Canadian telecom regulations).
A: Yes, the Canadian adoption is technically equivalent to the international standard. Any modifications are limited to editorial changes and national references (e.g., Canadian telecom regulations).
Q: Can PUM be used in an IP-based PISN environment?
A: Yes. The standard is transport-independent at the network layer. When QSIG is tunneled over IP (e.g., using H.323 or SIP trunks), PUM information flows are mapped accordingly. However, additional specifications (e.g., ISO/IEC 15432) may provide guidance for direct IP deployment.
A: Yes. The standard is transport-independent at the network layer. When QSIG is tunneled over IP (e.g., using H.323 or SIP trunks), PUM information flows are mapped accordingly. However, additional specifications (e.g., ISO/IEC 15432) may provide guidance for direct IP deployment.
Q: What are the main differences between PUM and user mobility in public cellular networks?
A: PUM is designed for private, enterprise-grade networks and focuses on supplementary service profile mobility rather than full handover of ongoing calls. It also uses a simpler registration model based on user identity, without the complexity of location areas or radio resource management.
A: PUM is designed for private, enterprise-grade networks and focuses on supplementary service profile mobility rather than full handover of ongoing calls. It also uses a simpler registration model based on user identity, without the complexity of location areas or radio resource management.
Q: Is authentication mandatory per the standard?
A: The standard specifies authentication as optional. In practice, most implementations include some form of user authentication (e.g., PIN entry at terminal) to prevent unauthorized use. Future versions may mandate stronger security.
A: The standard specifies authentication as optional. In practice, most implementations include some form of user authentication (e.g., PIN entry at terminal) to prevent unauthorized use. Future versions may mandate stronger security.
Document year reference: 2026 – This article is based on the original 2004 edition with all amendments up to 2026.