Overview

ISO/IEC 17877:2000 defines call-handling additional network features for Private User Mobility (PUM) in Private Integrated Services Networks (PISN). The standard specifies two ANFs:

ANF‑PUMI (Incoming Call): directs incoming calls to a PUM user anywhere within a PISN if the user's current location is known.
ANF‑PUMO (Outgoing Call): allows a PUM user’s outgoing call to be processed at the user’s home location when required.

This International Standard contains the stage 1 (general principles and capabilities - clauses 6 and 7) and stage 2 (functional model and information flows - clauses 8 and 9) specifications. Stage 3 (signalling protocols and equipment behaviour) is required for formal conformance.

Key Topics

Functional model and FEs: stage 2 identifies Functional Entities (FEs) involved in PUMI and PUMO and how they map to physical equipment (e.g., Home PINX, Visitor PINX, Home Data Base (HDB), Visitor Data Base (VDB)).
Information flows: definitions and sequences for information exchange needed to locate users and route calls correctly within a PISN.
Service definitions: clear definitions for PUM concepts-PUM registration, PUM user identity (PISN number or alternative identifier), hosting address, incoming/outgoing PUM call.
Interactions with other services: specifies how PUMI/PUMO interact with supplementary services such as CLIP/ COLP/ CLIR, Call Forwarding (CFU/CFB/CFNR), Call Transfer, Message Waiting Indication (MWI) and more.
Conformance model: to claim conformance, stage 3 specifications must implement signalling and equipment behaviour adequate to support the stage 1 and 2 features described.

Applications

ISO/IEC 17877 is practical for organizations designing, deploying or testing private telecommunication networks where users may move between terminals:

PISN equipment manufacturers - to design switches, PINX devices, and databases that support PUM features.
Enterprise network architects and operators - to enable seamless call continuity for roaming employees across a private network.
Protocol and signalling engineers - to map stage 2 functional models into stage 3 signalling protocols and implementations.
Test labs and certification bodies - to validate functional conformance of PUM features against stage 1/2 requirements.

Deploying PUMI and PUMO improves user mobility, consistent call routing, and centralized policy control in campus, corporate or carrier-managed private networks.

Related Standards

Key referenced documents include:

ISO/IEC 11574 (basic call services and functional capabilities)
ISO/IEC 11571 (PISN addressing)
ISO/IEC 11579‑1 (PISN exchange reference configuration)
ISO/IEC 17875 (PUM registration supplementary service)

Keywords: ISO/IEC 17877, Private User Mobility, PUMI, PUMO, PISN, ANF, functional model, information flows, Home PINX, Home Data Base, visitor database.

Overview

ISO/IEC 17877:2000 defines call-handling additional network features for Private User Mobility (PUM) in Private Integrated Services Networks (PISN). The standard specifies two ANFs:

ANF‑PUMI (Incoming Call): directs incoming calls to a PUM user anywhere within a PISN if the user's current location is known.
ANF‑PUMO (Outgoing Call): allows a PUM user’s outgoing call to be processed at the user’s home location when required.

Key Topics

Functional model and FEs: stage 2 identifies Functional Entities (FEs) involved in PUMI and PUMO and how they map to physical equipment (e.g., Home PINX, Visitor PINX, Home Data Base (HDB), Visitor Data Base (VDB)).
Information flows: definitions and sequences for information exchange needed to locate users and route calls correctly within a PISN.
Service definitions: clear definitions for PUM concepts-PUM registration, PUM user identity (PISN number or alternative identifier), hosting address, incoming/outgoing PUM call.
Interactions with other services: specifies how PUMI/PUMO interact with supplementary services such as CLIP/ COLP/ CLIR, Call Forwarding (CFU/CFB/CFNR), Call Transfer, Message Waiting Indication (MWI) and more.
Conformance model: to claim conformance, stage 3 specifications must implement signalling and equipment behaviour adequate to support the stage 1 and 2 features described.

Applications

ISO/IEC 17877 is practical for organizations designing, deploying or testing private telecommunication networks where users may move between terminals:

PISN equipment manufacturers - to design switches, PINX devices, and databases that support PUM features.
Enterprise network architects and operators - to enable seamless call continuity for roaming employees across a private network.
Protocol and signalling engineers - to map stage 2 functional models into stage 3 signalling protocols and implementations.
Test labs and certification bodies - to validate functional conformance of PUM features against stage 1/2 requirements.

Deploying PUMI and PUMO improves user mobility, consistent call routing, and centralized policy control in campus, corporate or carrier-managed private networks.

Related Standards

Key referenced documents include:

ISO/IEC 11574 (basic call services and functional capabilities)
ISO/IEC 11571 (PISN addressing)
ISO/IEC 11579‑1 (PISN exchange reference configuration)
ISO/IEC 17875 (PUM registration supplementary service)

Keywords: ISO/IEC 17877, Private User Mobility, PUMI, PUMO, PISN, ANF, functional model, information flows, Home PINX, Home Data Base, visitor database.

ISO/IEC 17877:2000 PDF

Technical details

Abstract

Overview

Key Topics

Applications

Related Standards

Related standards

Abstract

Overview

Key Topics

Applications

Related Standards

Related standards

Private Integrated Services Network (PISN); Specification, functional models and information flows; Private U…

Private Integrated Services Network (PISN); Specification, functional models and information flows; Control a…

Private Integrated Services Network (PISN); Addressing [ISO/IEC 11571 (1998), modified]

Information technology — Telecommunications and information exchange between systems — Private integrated ser…

Private Integrated Services Network (PISN); Specification, functional models and information flows; Private U…