ISO/IEC 20113:2004 PDF

Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Specification, functional model and information flows — Make call request supplementary service

Название (английский):

ISO/IEC 20113:2004

Статус документа:: Действующий
Формат:: Электронный (PDF)
Количество страниц:: 21
Дата публикации:: 21 мая 2004 г.
Издание:: ISO/IEC IS 20113 edition 1 version 1
ICS:: 33.040.35

Тип поставки:

Full version315 €Read online 24h10 €Read online 72h15 €

Язык документа:

ruen

Срок поставки:4 раб. дн. (перевод)

Цена:315 €

Описание (английский):

ISO/IEC 20113:2004 specifies supplementary service Make Call Request (SS-MCR), which is related, but not limited to, various basic services supported by Private Integrated Services Networks (PISNs). Basic services are specified in ISO/IEC 11574. The supplementary service MCR enables a Requesting User to request a Co-operating User to establish a new Requested Call to a Destination User. This new Requested Call between the Co-operating and Destination User can be either a Basic call or call independent signalling connection. Service specifications are produced in three stages, according to the method described in ETS 300 387. ISO/IEC 20113:2004 contains the stage 1 and stage 2 specifications of SS-MCR. The stage 1 specification specifies the supplementary service as seen by users of PISNs. The stage 2 specification specifies the functional entities involved in the supplementary service and the information flows between them.

Технические детали

Технический комитет: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
SKU: ISO/IEC 20113:2004

Abstract

Overview

ISO/IEC 20113:2004 defines the supplementary service Make Call Request (SS‑MCR) for Private Integrated Services Networks (PISNs). It contains the stage 1 (service description as seen by users) and stage 2 (functional model and information flows) specifications for SS‑MCR. The service enables a Requesting User to ask a Co‑operating User to establish a new Requested Call to a Destination User - either a Basic call or a call‑independent signalling connection - with the Original Call and Requested Call correlated.

Key Topics and Requirements

Scope: Applicable across basic telecommunication services supported by PISNs (basic services defined in ISO/IEC 11574).
Service stages: Stage 1 (user‑facing behavior) and Stage 2 (functional entities and information flows). A Stage 3 specification is required to define signalling protocols and equipment behavior for conformance.
Required information elements when invoking SS‑MCR:
- Destination address (e.g., party number)
- Optional Co‑operating User and Requesting User numbers
- Indication of requested Basic Service or call‑independent signalling
- Correlation ID linking Original Call and Requested Call
- Flag indicating whether the Original Call should be retained after the Requested Call is established
Functional behavior:
- Entity serving the Co‑operating User validates permissions and service availability and may inform the Co‑operating User of the request.
- If the Requested Call is established successfully, the Requesting User receives an indication; clearing/retention responsibilities are specified (Co‑operating User clears Requested Call; Requesting User clears retained Original Call).
- If validation fails, or the Co‑operating User is busy, an error indication is returned and the Requesting User must clear the Original Call.
Interactions with other services:
- No interaction with SS‑CLIP, SS‑COLP, SS‑CLIR, SS‑CNIP, SS‑CNIR, SS‑CONP.
- Call Forwarding Unconditional (SS‑CFU) and Call Forwarding Busy (SS‑CFB): if SS‑CFU/SS‑CFB is active at the Co‑operating User, the MCR request shall not be forwarded (implementation option: provide SS‑MCR or return an error). Destination forwarding remains unaffected.

Applications - Who uses this standard

Telecom equipment vendors and PISN (PINX) manufacturers implementing supplementary services.
Network architects, system integrators, and telecom software developers building PBX/PISN features that enable mediated call setup (e.g., operator assistance, message centres invoking a third‑party call).
Standards bodies and test labs creating Stage 3 signalling protocols or conformance test suites for SS‑MCR.
Useful in enterprise telephony, private branch exchanges and any environment using ISO/IEC PISN frameworks.

Related Standards

ISO/IEC 11574 - PISN basic service descriptions
ISO/IEC 11579‑1 - PINX reference configuration
ISO/IEC 11582 - Generic functional protocol for supplementary services
ETS 300 387 - Method for specifying basic and supplementary services

Keywords: ISO/IEC 20113:2004, Make Call Request, SS‑MCR, Private Integrated Services Network, PISN, supplementary service, stage 1, stage 2, functional model, information flows.

Overview

Key Topics and Requirements

Scope: Applicable across basic telecommunication services supported by PISNs (basic services defined in ISO/IEC 11574).
Service stages: Stage 1 (user‑facing behavior) and Stage 2 (functional entities and information flows). A Stage 3 specification is required to define signalling protocols and equipment behavior for conformance.
Required information elements when invoking SS‑MCR:
- Destination address (e.g., party number)
- Optional Co‑operating User and Requesting User numbers
- Indication of requested Basic Service or call‑independent signalling
- Correlation ID linking Original Call and Requested Call
- Flag indicating whether the Original Call should be retained after the Requested Call is established
Functional behavior:
- Entity serving the Co‑operating User validates permissions and service availability and may inform the Co‑operating User of the request.
- If the Requested Call is established successfully, the Requesting User receives an indication; clearing/retention responsibilities are specified (Co‑operating User clears Requested Call; Requesting User clears retained Original Call).
- If validation fails, or the Co‑operating User is busy, an error indication is returned and the Requesting User must clear the Original Call.
Interactions with other services:
- No interaction with SS‑CLIP, SS‑COLP, SS‑CLIR, SS‑CNIP, SS‑CNIR, SS‑CONP.
- Call Forwarding Unconditional (SS‑CFU) and Call Forwarding Busy (SS‑CFB): if SS‑CFU/SS‑CFB is active at the Co‑operating User, the MCR request shall not be forwarded (implementation option: provide SS‑MCR or return an error). Destination forwarding remains unaffected.

Applications - Who uses this standard

Telecom equipment vendors and PISN (PINX) manufacturers implementing supplementary services.
Network architects, system integrators, and telecom software developers building PBX/PISN features that enable mediated call setup (e.g., operator assistance, message centres invoking a third‑party call).
Standards bodies and test labs creating Stage 3 signalling protocols or conformance test suites for SS‑MCR.
Useful in enterprise telephony, private branch exchanges and any environment using ISO/IEC PISN frameworks.

Related Standards

ISO/IEC 11574 - PISN basic service descriptions
ISO/IEC 11579‑1 - PINX reference configuration
ISO/IEC 11582 - Generic functional protocol for supplementary services
ETS 300 387 - Method for specifying basic and supplementary services

Keywords: ISO/IEC 20113:2004, Make Call Request, SS‑MCR, Private Integrated Services Network, PISN, supplementary service, stage 1, stage 2, functional model, information flows.

ISO/IEC 20113:2004 PDF

Технические детали

Abstract

Overview

Key Topics and Requirements

Applications - Who uses this standard

Related Standards

Похожие стандарты

Abstract

Overview

Key Topics and Requirements

Applications - Who uses this standard

Related Standards

Похожие стандарты

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

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

Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Generic functional protocol f…