SIST-TS ETSI/TS 102 256 V1.1.1:2005
(Main)Private Integrated Services Network (PISN); Specification, functional model and information flows; Make Call Request supplementary service
- Abstract
Stage 1 & 2 description.
- Status
- Published
- Publication Date
- 28-Feb-2005
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Mar-2005
- Due Date
- 01-Mar-2005
- Completion Date
- 01-Mar-2005
SIST-TS ETSI/TS 102 256 V1.1.1:2005 is the Slovenian identical adoption of ETSI TS 102 256 V1.1.1, published by ETSI for the Make Call Request supplementary service in Private Integrated Services Network (PISN) environments. It specifies the stage 1 user view and stage 2 functional model and information flows for SS-MCR, so implementers, service providers, and network engineers can see how a Requesting User asks a Co-operating User to establish a Requested Call to a Destination User.
What does SIST-TS ETSI/TS 102 256 V1.1.1:2005 specify?
SIST-TS ETSI/TS 102 256 V1.1.1:2005 specifies Supplementary Service Make Call Request (SS-MCR) for PISNs, and it is related to, but not limited to, the basic services supported by PISNs. The service lets one user request another user to set up a new call, which may be either a Basic call or a Call Independent Signalling Connection (CISC).
The document follows the three-stage service description method used for telecommunication services. Clause 6 gives the stage 1 specification, seen from the users' side, and clause 7 gives the stage 2 specification, which defines the Functional Entities (FEs) and the information flows between them.
The document is organized into clauses 1 to 7:
- Clause 1 - Scope
- Clause 2 - Conformance
- Clause 3 - Normative references
- Clause 4 - Definitions
- Clause 5 - List of acronyms
- Clause 6 - SS-MCR stage 1 specification
- Clause 7 - SS-MCR stage 2 specification
What are the key requirements of SIST-TS ETSI/TS 102 256 V1.1.1:2005?
Service purpose and applicability
SIST-TS ETSI/TS 102 256 V1.1.1:2005 defines SS-MCR as a service for asking a Co-operating User to establish a Requested Call to a Destination User, with the Requested Call correlated to the Original Call. In practice, this means the service is for call set-up coordination between two active parties, not for a direct call from the Requesting User to the Destination User.
Clause 6.1 says the service applies to all basic telecommunication services. That matters because implementers do not need to restrict it to a narrow call type when planning support.
Provision, invocation and user data
Clause 6.2 allows SS-MCR to be provided or withdrawn by prior arrangement with the service provider, or made generally available to all users. This gives operators flexibility in how they offer the service.
When a Requesting User invokes SS-MCR, the document allows use of an existing signalling connection if one is already available, or otherwise requires a call independent signalling connection to the Co-operating User. The request may carry destination address information, optional requesting and co-operating user numbers, the call type, a correlation ID, and an indication of whether the Original Call is to be retained after the Requested Call is established. In practice, this is the information a network or terminal has to gather and pass on for the service to work correctly.
Success handling and clearing responsibility
Clause 6.2 states that, if the Requested Call is established successfully, an appropriate indication is sent to the Requesting User. The Original Call is then either retained or cleared immediately, depending on the initial request.
The Co-operating User is responsible for clearing the Requested Call. If the Original Call is retained, the Requesting User is responsible for clearing the Original Call. This division of responsibility matters for call control, billing, and release handling.
Exceptional procedures
Clause 6.2 also covers failure cases. If the serving entity for the Co-operating User does not support SS-MCR, if validation fails, if the indicated service cannot be established, or if the Co-operating User is busy, an error indication is sent to the Requesting User. In those cases, the Requesting User is responsible for clearing the Original Call.
For implementers, this means the service must define a clear fallback path when the request cannot be processed, so calls are not left in an undefined state.
Interactions with other supplementary services and ANFs
Clause 6.3 identifies interactions with other supplementary services and Additional Network Features (ANFs) that were available when the document was published. The most practical points are:
- SS-CFU at the Co-operating User prevents forwarding of the request to set up the Requested Call.
- SS-CFB and SS-CFNR at the Co-operating User can stop the request from being forwarded when the user is busy or does not answer.
- SS-CD is not allowed to deflect the request to set up the Requested Call.
- SS-DND can either block SS-MCR at the Co-operating User or block presentation of the Requested Call at the Destination User, depending on implementation.
- SS-CIDL may use the same Thread ID for the call between Requesting User and Co-operating User and the call between Co-operating User and Destination User.
These rules matter because they affect how SS-MCR behaves when it meets forwarding, privacy, and call-control features in the same network.
Stage 2 model, information flows and interworking
Clause 7 turns the service into a functional model with six Functional Entities: FE1 to FE6. The model defines the Requesting User side, the Co-operating User side, and the Destination User side, and links them with relationships ra to re. This gives protocol designers a clear map of where each action happens.
Clause 7.2 defines four key information flows: MCR_CallRequest, MCR_PromptCoop, MCR_Inform, and MCR_Alerting. Their tables show which fields are mandatory or optional, including destination address, requesting address, co-operating address, call type, correlation, retain-original-call, and result. In practice, these tables are the basis for message design and interoperability testing.
Clause 7.5 and 7.6 allocate the Functional Entities to physical equipment and to interworking scenarios. That matters for real deployments because the same logical service can be mapped to a Requesting User, Message Centre, Served User, PINX, or an adjacent network depending on the scenario.
What terms does SIST-TS ETSI/TS 102 256 V1.1.1:2005 define?
- Requesting User - the user who sends a Make Call Request to ask for a specific Requested Call to be established.
- Co-operating User - the user who receives the request and sets up the Requested Call to the Destination User.
- Destination User - the called user of the Requested Call.
- Make Call Request - the request from the Requesting User for a new call between the Co-operating User and the Destination User.
- Original Call - the call between the Requesting User and the Co-operating User, which is correlated with the Requested Call.
- Requested Call - the new call established by the Co-operating User to the Destination User because of the Make Call Request.
- Call Independent Signalling Connection (CISC) - a signalling connection that can be used instead of a Basic call for the Requested Call or the Original Call.
Who uses SIST-TS ETSI/TS 102 256 V1.1.1:2005?
SIST-TS ETSI/TS 102 256 V1.1.1:2005 is used by PISN engineers, PBX and PINX vendors, protocol designers, and service providers who need to implement or support SS-MCR. It is also relevant to test and certification teams checking stage 3 signalling behavior against the stage 1 and stage 2 service model.
In practice, the document is useful when designing enterprise telephony features such as request-based call set-up, message-centre call initiation, or interworking with another network that supports an equivalent feature. Quality managers and buyers can use it to check whether a product or network supports the service model they need.
Which standards are used with SIST-TS ETSI/TS 102 256 V1.1.1:2005?
- ECMA-133 - gives the PISN reference configuration for PINX and the core PISN/PINX context.
- ECMA-142 - defines basic services and bearer services, which SS-MCR builds on.
- ECMA-165 - provides the generic functional protocol for supplementary services and the QSIG-GF context.
- ETS 300 387 - gives the method used to specify basic and supplementary services in stages.
- ITU-T I.112 - supplies vocabulary for ISDN terms used in the document.
- ITU-T I.210 - defines the principles for telecommunication services and how to describe them.
- ITU-T Z.100 - defines Specification and Description Language (SDL), which is used for the procedural figures.
What does the SIST-TS ETSI/TS 102 256 V1.1.1:2005 document contain?
SIST-TS ETSI/TS 102 256 V1.1.1:2005 contains a stage 1 service description, a stage 2 functional model, and the message and behavior model needed to support stage 3 protocol work. The document uses SDL figures to show the service logic and the interaction between Requesting, Co-operating, and Destination sides.
Clause 7 includes tables for information-flow contents, including which fields are mandatory or optional, and figures for the overall sequence and each Functional Entity behavior. It also includes tables that map the Functional Entities to physical equipment and to interworking scenarios with other networks. This makes the document useful for implementation design, protocol specification, interoperability analysis, and conformance planning.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST-TS ETSI/TS 102 256 V1.1.1:2005 is a technical specification published by the Slovenian Institute for Standardization (SIST). Its full title is "Private Integrated Services Network (PISN); Specification, functional model and information flows; Make Call Request supplementary service". This standard covers: Stage 1 & 2 description.
Stage 1 & 2 description.
SIST-TS ETSI/TS 102 256 V1.1.1:2005 is classified under the following ICS (International Classification for Standards) categories: 33.040.35 - Telephone networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST-TS ETSI/TS 102 256 V1.1.1:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-marec-2005
Zasebno omrežje z integriranimi storitvami (PISN) - Specifikacija, funkcijski model
in informacijski pretoki - Dopolnilna storitev: tvorba zahteve za zvezo
Private Integrated Services Network (PISN); Specification, functional model and
information flows; Make Call Request supplementary service
Ta slovenski standard je istoveten z: TS 102 256 Version 1.1.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
Technical Specification
Private Integrated Services Network (PISN);
Specification, functional model and information flows;
Make Call Request supplementary service
2 ETSI TS 102 256 V1.1.1 (2003-08)
Reference
DTS/ECMA-00231
Keywords
PISN, stage 1, stage 2, supplementary service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
editor@etsi.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 102 256 V1.1.1 (2003-08)
Contents
Intellectual Property Rights.5
Foreword.5
Brief History.5
1 Scope.6
2 Conformance.6
3 References (normative).6
4 Definitions.7
4.1 External definitions.7
4.2 Other definitions.7
4.2.1 Co-operating User.7
4.2.2 Destination User.7
4.2.3 Make Call Request.7
4.2.4 Original Call.7
4.2.5 Requested Call.7
4.2.6 Requesting User.8
5 List of acronyms.8
6 SS-MCR stage 1 specification.9
6.1 Description.9
6.1.1 General description.9
6.1.2 Qualifications on applicability to telecommunication services.9
6.2 Procedures.9
6.2.1 Provision / withdrawal.9
6.2.2 Normal procedures.9
6.2.2.1 Activation, deactivation and interrogation .9
6.2.2.2 Invocation and operation.9
6.2.3 Exceptional procedures.10
6.2.3.1 Activation, deactivation and interrogation .10
6.2.3.2 Invocation and operation.10
6.3 Interactions with other Supplementary Services / Additional Network Features.10
6.3.1 Calling Line Identification Presentation (SS-CLIP) .10
6.3.2 Connected Line Identification Presentation (SS-COLP) .10
6.3.3 Calling/Connected Line Identification Restriction (SS-CLIR).10
6.3.4 Calling Name Identification Presentation (SS-CNIP).10
6.3.5 Calling/Connected Name Identification Restriction (SS-CNIR) .10
6.3.6 Connected Name Identification Presentation (SS-CONP).11
6.3.7 Call Forwarding Unconditional (SS-CFU) .11
6.3.8 Call Forwarding Busy (SS-CFB).11
6.3.9 Call Forwarding No Reply (SS-CFNR).11
6.3.10 Call Deflection (SS-CD).11
6.3.11 Path Replacement (ANF-PR).11
6.3.12 Call Transfer (SS-CT).11
6.3.13 Completion of Calls to Busy Subscribers (SS-CCBS).11
6.3.14 Completion of Calls on No Reply (SS-CCNR).11
6.3.15 Call Offer (SS-CO) .11
6.3.16 Do Not Disturb (SS-DND) .12
6.3.17 Do Not Disturb Override (SS-DNDO).12
6.3.18 Call Intrusion (SS-CI).12
6.3.19 Advice of Charge (SS-AOC) .12
6.3.20 Recall (SS-RE).12
6.3.21 Call Interception (SS-CINT).12
6.3.22 Transit Counter (ANF-TC) .12
6.3.23 Route Restriction Class (ANF-RRC).12
ETSI
4 ETSI TS 102 256 V1.1.1 (2003-08)
6.3.24 Message Waiting Indication (SS-MWI) .12
6.3.25 Wireless Terminal Location Registration (SS-WTLR).12
6.3.26 Wireless Terminal Incoming Call (SS-WTMI).12
6.3.27 Wireless Terminal Outgoing Call (SS-WTMO) .12
6.3.28 Wireless Terminal Authentication of a WTM User (SS-WTAT) .12
6.3.29 Wireless Terminal Authentication of the PISN (SS-WTAN) .13
6.3.30 Common Information (SS-CMN).13
6.3.31 Call Priority Interruption (Protection) (SS-CPI(P)) .13
6.3.32 Private User Mobility Incoming Call (ANF-PUMI).13
6.3.33 Private User Mobility Outgoing Call (ANF-PUMO).13
6.3.34 Private User Mobility Registration (SS-PUMR).13
6.3.35 Single Step Call Transfer (SS-SSCT) .13
6.3.36 Simple Dialog (SS-SD).13
6.3.37 Call Identification and Call Linkage (ANF-CIDL).13
6.3.38 Short Message Service (SS-SMS) .13
6.3.39 Message Centre Monitoring (SS-MCM).13
6.3.40 Mailbox Identification (SS-MID) .13
6.4 Interworking considerations.13
6.5 Overall SDL.14
7 SS-MCR stage 2 specification.16
7.1 Functional model.16
7.1.1 Functional model description.16
7.1.2 Description of Functional Entities .16
7.1.2.1 Requesting User's User Agent, FE1 .16
7.1.2.2 Requesting User's Control entity, FE2 .17
7.1.2.3 Co-operating User's Control entity, FE3 .17
7.1.2.4 Co-operating User's User Agent, FE4 .17
7.1.2.5 Destination User's Control entity, FE5.17
7.1.2.6 Destination User's User Agent, FE6.17
7.2 Information flows.18
7.2.1 Definition of information flows.18
7.2.1.1 MCR_CallRequest.18
7.2.1.2 MCR_PromptCoop.18
7.2.1.3 MCR_Inform.19
7.2.1.4 MCR_Alerting.19
7.2.2 Relationship of information flows to Basic Call information flows .19
7.2.3 Information flow sequences.19
7.2.3.1 Make Call Request procedures of SS-MCR.20
7.3 Functional Entity actions.20
7.3.1 Functional Entity actions of FE1 .20
7.3.2 Functional Entity actions of FE2 .20
7.3.3 Functional Entity actions of FE3 .21
7.3.4 Functional Entity actions of FE4 .21
7.3.5 Functional Entity actions of FE5 .21
7.3.6 Functional Entity actions of FE6 .21
7.4 Functional Entity behaviour .21
7.4.1 Behaviour of FE1.22
7.4.2 Behaviour of FE2.23
7.4.3 Behaviour of FE3.24
7.4.4 Behaviour of FE4.25
7.4.5 Behaviour of FE5.25
7.4.6 Behaviour of FE6.26
7.5 Allocation of Functional Entities to physical equipment.26
7.6 Interworking considerations.27
History .28
ETSI
5 ETSI TS 102 256 V1.1.1 (2003-08)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ECMA on behalf of its members and those of the European
Telecommunications Standards Institute (ETSI).
Brief History
The present document is one of a series of ECMA Standards defining services and signalling protocols applicable to
Private Integrated Services Networks (PISNs). The series uses ISDN concepts as developed by ITU-T and conforms to
the framework of International Standards for Open Systems Interconnection as defined by ISO/IEC. It has been
produced under ETSI work item DTS/ECMA-00231.
The present document specifies the Make Call Request supplementary service.
The present document is based upon the practical experience of ECMA member companies and the results of their
active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national
standardization bodies. It represents a pragmatic and widely based consensus.
ETSI
6 ETSI TS 102 256 V1.1.1 (2003-08)
1 Scope
The present document 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
ECMA-142 [2].
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 [4]. The present
document contains the stage 1 and stage 2 specifications of SS-MCR. The stage 1 specification (clause 6) specifies the
supplementary service as seen by users of PISNs. The stage 2 specification (clause 7) specifies the functional entities
involved in the supplementary service and the information flows between them.
2 Conformance
In order to conform to the present document, a stage 3 standard shall specify signalling protocols and equipment
behaviour that are capable of being used in a PISN which supports the supplementary service specified in the present
document. This means that, to claim conformance, a stage 3 standard is required to be adequate for the support of those
aspects of clause 6 (stage 1) and clause 7 (stage 2) which are relevant to the interface or equipment to which the stage 3
standard applies.
3 References (normative)
The following standards contain provisions, which, through reference in this text, constitute provisions of the present
document. All standards are subject to revision, and parties to agreements based on the present document are
encouraged to investigate the possibility of applying the most recent editions of the standards indicated below.
In the case of references to ECMA Standards that are aligned with ISO/IEC International Standards, the number of the
appropriate ISO/IEC International Standard is given in brackets after the ECMA reference.
[1] ECMA-133: "Private Integrated Services Network (PISN) - Reference Configuration for PISN
Exchanges (PINX) (International Standard ISO/IEC 11579-1)".
[2] ECMA-142: "Private Integrated Services Network (PISN) - Circuit Mode 64kbit/s Bearer
Services - Service Description, Functional Capabilities and Information Flows (BCSD)
(International Standard ISO/IEC 11574)".
[3] ECMA-165: "Private Integrated Services Network (PISN) - Generic Functional Protocol for the
Support of Supplementary Services - Inter-Exchange Signalling Procedures and Protocol
(QSIG-GF) (International Standard ISO/IEC 11582)".
[4] ETSI ETS 300 387: "Private Telecommunication Network (PTN); Method for the specification of
basic and supplementary services".
[5] ITU-T Recommendation I.112: "Vocabulary of terms for ISDNs".
[6] ITU-T Recommendation I.210: "Principles of telecommunication services supported by an ISDN
and the means to describe them".
[7] ITU-T Recommendation Z.100: "Specification and Description Language (SDL)".
ETSI
7 ETSI TS 102 256 V1.1.1 (2003-08)
4 Definitions
For the purposes of the present document, the following terms and definitions apply.
4.1 External definitions
For the purposes of the present document the following terms and definitions given in other documents apply:
basic service: See ECMA-142 [2].
call, basic call: See ECMA-165 [3].
Call Independent Signalling Connection (CISC): See ECMA-165 [3].
call independent: See ECMA-165 [3].
call related: See ECMA-165 [3].
Private Integrated services Network eXchange (PINX): See ECMA-133 [1].
Private Integrated Services Network (PISN): See ECMA-133 [1].
service: See ITU-T Recommendation I.112 [5].
signalling: See ITU-T Recommendation I.112 [5].
Supplementary Service (SS): See ITU-T Recommendation I.210 [6].
user: See ECMA-142 [2].
4.2 Other definitions
4.2.1 Co-operating User
The user who receives a Make Call Request and who shall set up a new Requested Call to the Destination User.
4.2.2 Destination User
The called user of the Requested Call i.e. the user to whom the Co-operating User shall establish a Requested Call.
4.2.3 Make Call Request
A request from the Requesting User for a new call (i.e. Requested Call) between a Co-operating User and a Destination
User.
4.2.4 Original Call
The call between the Requesting User and the Co-operating User. The Original Call can be either a Basic call or a call
independent signalling connection and is correlated with the Requested Call.
4.2.5 Requested Call
The call between the Co-operating User and the Destination User that is established by the Co-operating User due to a
Make Call Request from the Requesting User. The Requested Call can either be a Basic call (with a specific Basic
Service) or a call independent signalling connection and is correlated with the Original Call.
ETSI
8 ETSI TS 102 256 V1.1.1 (2003-08)
4.2.6 Requesting User
The User who sends a Make Call Request to the Co-operating User with the request to establish a specific Requested
Call to the Destination User.
5 List of acronyms
For the purposes of the present document the following acronyms apply:
ANF Additional Network Feature
ANF-PR Path Replacement
ANF-PUMI Private User Mobility Incoming Call
ANF-PUMO Private User Mobility Outgoing Call
ANF-RRC Route Restriction Class
ANF-TC Transit Counter
CISC Call Independent Signalling Connection
FE Functional Entity
ISDN Integrated Services Digital Network
MC Message Centre
MCR Make Call Request
PINX Private Integrated services Network eXchange
PISN Private Integrated Services Network
SDL Specification and Description Language
SS Supplementary Service
SS-AOC Advice of Charge
SS-CCBS Completion of Calls to Busy Subscribers
SS-CCNR Completion of Calls on No Reply
SS-CD Call Deflection
SS-CFB Call Forwarding Busy
SS-CFNR Call Forwarding No Reply
SS-CFU Call Forwarding Unconditional
SS-CI Call Intrusion
SS-CINT Call INTerception
SS-CLIP Calling Line Identification Presentation
SS-CLIR Calling/Connected Line Identification Restriction
SS-CMN Common Information
SS-CNIP Calling Name Identification Presentation
SS-CNIR Calling/Connected Name Identification Restriction
SS-CO Call Offer
SS-COLP Connected Line Identification Presentation
SS-CONP Connected Name Identification Presentation
SS-CPI(P) Call Priority Interruption (Protection)
SS-CT Call Transfer
SS-DND Do Not Disturb
SS-DNDO Do Not Disturb Override
SS-MCM Message Centre Monitoring
SS-MID Mailbox Identification
SS-MWI Message Wa
...