ETSI TS 102 257 V1.1.1 (2003-08)
Private Integrated Services Network (PISN); Inter-exchange Signalling Protocol; Make Call Request supplementary service
Private Integrated Services Network (PISN); Inter-exchange Signalling Protocol; Make Call Request supplementary service
DTS/ECMA-00232
Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski protokol - Dopolnilna storitev: tvorba zahteve za zvezo
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-marec-2005
Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski
protokol - Dopolnilna storitev: tvorba zahteve za zvezo
Private Integrated Services Network (PISN); Inter-exchange Signalling Protocol; Make
Call Request supplementary service
Ta slovenski standard je istoveten z: TS 102 257 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);
Inter-exchange Signalling Protocol;
Make Call Request supplementary service
2 ETSI TS 102 257 V1.1.1 (2003-08)
Reference
DTS/ECMA-00232
Keywords
PISN, QSIG, stage 3, 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 257 V1.1.1 (2003-08)
Contents
Intellectual Property Rights.6
Foreword.6
Brief History.6
1 Scope.7
2 Conformance.7
3 References (normative).7
4 Definitions.8
4.1 External definitions.8
4.2 Other definitions.8
4.2.1 Co-operating PINX.8
4.2.2 Co-operating User.8
4.2.3 Destination PINX.8
4.2.4 Destination User.9
4.2.5 Make Call Request.9
4.2.6 Original Call.9
4.2.7 Requested Call.9
4.2.8 Requesting PINX.9
4.2.9 Requesting User.9
5 List of acronyms.9
6 Signalling Protocol for the support of SS-MCR.10
6.1 SS-MCR description.10
6.2 SS-MCR operational requirements.10
6.2.1 Requirements on a Requesting PINX .10
6.2.2 Requirements on a Co-operating PINX .10
6.2.3 Requirements on a Destination PINX.11
6.2.4 Requirements on a Transit PINX.11
6.3 SS-MCR coding requirements.12
6.3.1 Operations.12
6.3.2 Information elements.15
6.3.2.1 Facility information element.15
6.3.2.2 Other information elements.15
6.3.3 Messages.15
6.4 SS-MCR state definitions.15
6.4.1 States at the Requesting PINX.15
6.4.1.1 State MCR-Idle.15
6.4.1.2 State MCR-Active.15
6.4.2 States at the Co-operating PINX.15
6.4.2.1 State MCR-Idle.15
6.4.2.2 State MCR-Active.15
6.4.3 States at the Destination PINX .16
6.5 SS-MCR signalling procedures .16
6.5.1 Actions at the Requesting PINX.16
6.5.1.1 Normal procedures.16
6.5.1.1.1 Activation/deactivation/interrogation.16
6.5.1.1.2 Invocation and operation .16
6.5.1.2 Exceptional procedures.16
6.5.1.2.1 Activation/deactivation/interrogation.16
6.5.1.2.2 Invocation and operation .16
6.5.2 Actions at the Co-operating PINX.16
6.5.2.1 Normal procedures.17
6.5.2.1.1 Activation / deactivation / interrogation.17
6.5.2.1.2 Invocation and operation .17
ETSI
4 ETSI TS 102 257 V1.1.1 (2003-08)
6.5.2.2 Exceptional procedures.17
6.5.2.2.1 Activation/deactivation/interrogation.17
6.5.2.2.2 Invocation and operation .17
6.5.3 Actions at the Destination PINX.18
6.5.3.1 Normal procedures.18
6.5.3.1.1 Activation / deactivation / interrogation.18
6.5.3.1.2 Invocation and operation .18
6.5.3.2 Exceptional procedures.18
6.5.3.2.1 Activation / deactivation / interrogation.18
6.5.3.2.2 Invocation and operation .18
6.5.4 Actions at a Transit PINX.18
6.6 SS-MCR impact of interworking with public ISDNs.18
6.7 SS-MCR impact of interworking with non-ISDNs .18
6.8 Protocol interactions between SS-MCR and other supplementary services and ANFs.18
6.8.1 Calling Line Identification Presentation (SS-CLIP) .19
6.8.2 Connected Line Identification Presentation (SS-COLP) .19
6.8.3 Calling/Connected Line Identification Restriction (SS-CLIR).19
6.8.4 Calling Name Identification Presentation (SS-CNIP).19
6.8.5 Calling Name Identification Presentation (SS-CNIR) .19
6.8.6 Connected Name Identification Presentation (SS-CONP).19
6.8.7 Completion of Call to Busy Subscriber (SS-CCBS).19
6.8.8 Completion of Call on No Reply (SS-CCNR) .19
6.8.9 Call Transfer (SS-CT).19
6.8.10 Call Forwarding Unconditional (SS-CFU) .19
6.8.11 Call Forwarding Busy (SS-CFB).19
6.8.12 Call Forwarding No Reply (SS-CFNR).20
6.8.13 Call Deflection (SS-CD).20
6.8.14 Path Replacement (ANF-PR).20
6.8.15 Call Offer (SS-CO) .20
6.8.16 Call Intrusion (SS-CI).20
6.8.17 Do not Disturb (SS-DND) .20
6.8.18 Do not Disturb Override (SS-DNDO) .20
6.8.19 Advice of Charge (SS-AOC) .20
6.8.20 Recall (SS-RE).20
6.8.21 Call Interception (ANF-CINT) .20
6.8.22 Transit Counter (ANF-TC) .21
6.8.23 Route Restriction Class (ANF-RRC).21
6.8.24 Message Waiting Indication (SS-MWI) .21
6.8.25 Wireless Terminal Location Registration (SS-WTLR).21
6.8.26 Wireless Terminal Incoming Call (ANF-WTMI).21
6.8.27 Wireless Terminal Outgoing Call (ANF-WTMO).21
6.8.28 Wireless Terminal Authentication of a WTM User (SS-WTAT) .21
6.8.29 Wireless Terminal Authentication of the PISN (SS-WTAN) .21
6.8.30 Private User Mobility Incoming Call (ANF-PUMI).21
6.8.31 Private User Mobility Outgoing Call (ANF-PUMO).21
6.8.32 Private User Mobility Registration (SS-PUMR).21
6.8.33 Common Information (ANF-CMN) .21
6.8.34 Call Priority Interruption (Protection) (SS-CPI(P)) .21
6.8.35 Single Step Call Transfer (SS-SSCT) .21
6.3.36 Simple Dialog (SS-SD).22
6.8.37 Global Call Identification and Call Linkage (ANF-CIDL).22
6.8.38 Short Message Service (SS-SMS) .22
6.8.39 Message Centre Monitoring (SS-MCM).22
6.8.40 Mailbox Identification (SS-MID) .22
6.9 SS-MCR parameter values (Timers) .22
6.9.1 Timer T1.22
Annex A (normative): Protocol Implementation Conformance Statement (PICS) Proforma .23
A.1 Introduction.23
A.2 Instructions for completing the PICS proforma .23
A.2.1 General structure of the PICS proforma .23
ETSI
5 ETSI TS 102 257 V1.1.1 (2003-08)
A.2.2 Additional information.24
A.2.3 Exception information.24
A.3 PICS proforma for ECMA-344 .24
A.3.1 Implementation identification.24
A.3.2 Protocol summary.25
A.3.3 General.25
A.3.4 Procedures.25
A.3.5 Coding.26
A.3.6 Timers.26
Annex B (informative): Examples of Message Sequences.27
B.1 Example message sequences for invocation and operation of SS-MCR.28
B.1.1 Example message sequences without prior existing connection .28
B.1.2 Example message sequences of a successful communication with a message centre .31
Annex C (informative): Specification and Description Language (SDL) Representation of
Procedures.32
C.1 SDL representation of SS-MCR at the Requesting PINX.33
C.2 SDL representation of SS-MCR at the Co-operating PINX.34
C.3 SDL representation of SS-MCR at the Destination PINX .35
History .36
ETSI
6 ETSI TS 102 257 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-00232.
The present document specifies the signalling protocol for use at the Q reference point in support of the Make Call
Request supplementary service. The protocol defined in the present document forms part of the PSS1 protocol
(informally known as QSIG).
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
7 ETSI TS 102 257 V1.1.1 (2003-08)
1 Scope
The present document specifies the signalling protocol for the support of the Supplementary Service Make Call Request
(SS-MCR) at the Q reference point between Private Integrated services Network eXchanges (PINXs) connected
together within a Private Integrated Services Network (PISN).
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 a Call Independent Signalling Connection.
The Q reference point is defined in ECMA-133 [1].
Service specifications are produced in three stages and according to the method specified in ETS 300 387 [6]. The
present document contains the stage 3 specification for the Q reference point and satisfies the requirements identified by
the stage 1 and stage 2 specifications in ECMA-343 [4].
The signalling protocol for SS-MCR operates on top of the signalling protocol for basic circuit switched call control, as
specified in ECMA-143 [2], and uses certain aspects of the generic procedures for the control of supplementary services
specified in ECMA-165 [3].
The present document also specifies additional signalling protocol requirements for the support of interactions at the
Q reference point between SS-MCR and other supplementary services and ANFs.
The present document is applicable to PINXs, which can interconnect to form a PISN.
2 Conformance
In order to conform to the present document, a PINX shall satisfy the requirements identified in the Protocol
Implementation Conformance Statement (PICS) proforma in annex A.
Conformance to the present document includes conforming to those clauses that specify protocol interactions between
SS-MCR and other supplementary services and ANFs for which signalling protocols at the Q reference point are
supported in accordance with the stage 3 standards concerned.
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-143: "Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - Inter-
Exchange Signalling Procedures and Protocol (QSIG-BC)", (International Standard
ISO/IEC 11572).
[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] ECMA-343: "Private Integrated Services Network (PISN) - Specification, Functional Model and
Information Flows - Make Call Request Supplementary Service (MCRSD)".
[5] ECMA-345: "Private Integrated Services Network (PISN) - Use of QSIG for Message Centre
Access (MCA) Profile Standard".
ETSI
8 ETSI TS 102 257 V1.1.1 (2003-08)
[6] ETSI ETS 300 387: "Private Telecommunication Network (PTN); Method for the specification of
basic and supplementary services".
[7] ITU-T Recommendation I.112: "Vocabulary of terms for ISDNs".
[8] ITU-T Recommendation I.210: "Principles of telecommunication services supported by an ISDN
and the means to describe them".
[9] ITU-T Recommendation Q.950: "Digital Subscriber Signalling System No. 1 (DSS1) -
Supplementary services protocols, structure and general principles".
[10] ITU-T Recommendation Z.100: "Specification and Description Language (SDL)".
4 Definitions
For the purposes of the present document, the following terms and definitions apply.
4.1 External definitions
The present document uses the following terms and definitions given in other documents apply:
Application Protocol Data Unit (APDU): See ECMA-165 [3].
call, basic call: See ECMA-165 [3].
Call Independent Signalling Connection (CISC): See ECMA-165 [3].
call-independent: See ECMA-165 [3].
gateway PINX: See ECMA-165 [3].
originating PINX: See ECMA-165 [3].
Private Integrated Services Network (PISN): See ECMA-133 [1].
Private Integrated services Network eXchange (PINX): See ECMA-133 [1].
signalling: See ITU-T Recommendation I.112 [7].
Supplementary Service (SS): See ITU-T Recommendation I.210 [8].
Supplementary Service Control (SSC) entity: See ECMA-165 [3].
terminating PINX: See ECMA-165 [3].
transit PINX: See ECMA-165 [3].
4.2 Other definitions
4.2.1 Co-operating PINX
The PINX where the Co-operating User is located.
4.2.2 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.3 Destination PINX
The PINX where the Destination User is located.
ETSI
9 ETSI TS 102 257 V1.1.1 (2003-08)
4.2.4 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.5 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.6 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.7 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.
4.2.8 Requesting PINX
The PINX where the Requesting User is located.
4.2.9 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-CIDL Call Identification and Call Linkage
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
APDU Application Protocol Data Unit
ASN.1 Abstract Syntax Notation One
CISC Call Independent Signalling Connection
ISDN Integrated Services Digital Network
NFE Network Facility Extension
PICS Protocol Implementation Conformance Statement
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
ETSI
10 ETSI TS 102 257 V1.1.1 (2003-08)
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-MCR Make Call Request
SS-MID Mailbox Identification
SS-MWI Message Waiting Indication
SS-PUMR Private User Mobility Registration
SS-RE REcall
SS-SD Simple Dialog
SS-SMS Short Message Service
SS-SSCT Single Step Call Transfer
SS-WTAN Wireless Terminal Authentication of the PISN
SS-WTAT Wireless Terminal Authentication of a WTM User
SS-WTLR Wireless Terminal Location Registration
SS-WTMI Wireless Terminal Incoming Call
SS-WTMO Wireless Terminal Outgoing Call
6 Signalling Protocol for the support of SS-MCR
6.1 SS-MCR description
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 User and the Destination
User can either be a Basic call or a Call Independent Signalling Connection. The new Requested Call is correlated to the
Original Call between the Requesting and Co-operating User.
6.2 SS-MCR operational requirements
6.2.1 Requirements on a Requesting PINX
Call establishment procedures for the incoming and outgoing side of an inter-PINX link and call release procedures, as
specified in ECMA-143 [2], shall apply.
Generic procedures for call-related control of supplementary services, as specified in ECMA-165 [3] for an End PINX,
shall apply.
Generic procedures for the call-independent control (connection-oriented) of supplementary services, as specified in
ECMA-165 [3] for an Originating PINX and for a Terminating PINX, shall apply.
6.2.2 Requirements on a Co-operating PINX
Call establishment procedures for the incoming and outgoing side of an inter-PINX link and call release procedures, as
specified in ECMA-143 [2], shall apply.
Generic procedures for call-related control of supplementary services, as specified in ECMA-165 [3] for an End PINX,
shall apply.
ETSI
11 ETSI TS 102 257 V1.1.1 (2003-08)
Generic procedures for the call-independent control (connection-oriented) of supplementary services, as specified in
ECMA-165 [3] for a Terminating PINX and for an Originating PINX, shall apply.
6.2.3 Requirements on a Destination PINX
Call establishment procedures for the incoming and outgoing side of an inter-PINX link and call release procedures, as
specified in ECMA-143 [2], shall apply.
Generic procedures for call-related control of supplementary services, as specified in ECMA-165 [3] for an End PINX,
shall apply.
Generic procedures for the call-independent control (connection-oriented) of supplementary services, as specified in
ECMA-165 [3] for a Terminating PINX and for an Originating PINX, shall apply.
6.2.4 Requirements on a Transit PINX
Basic call procedures specified in ECMA-143 [2] for a Transit PINX shall apply.
Generic procedures for call-related control of supplementary services, as specified in ECMA-165 [3] for a Transit
PINX, shall apply.
Generic procedures for the call-independent control (connection-oriented) of supplementary services, as specified in
ECMA-165 [3] for a Transit PINX, shall apply.
ETSI
12 ETSI TS 102 257 V1.1.1 (2003-08)
6.3 SS-MCR coding requirements
6.3.1 Operations
The operations defined in Abstract Syntax Notation number 1 (ASN.1) in table 1 shall apply.
Table 1: Operations in support of SS-MCR
SS-MCR-Operations-asn97
{iso (1) identified-organization (3) icd-ecma (12) standard (0)
qsig-make-call-request (344) make-call-request-operations (0)}
DEFINITIONS EXPLICIT TAGS ::=
BEGIN
IMPORTS
OPERATION,
ERROR
FROM Remote-Operations-Information-Objects
{ joint-iso-itu-t (2) remote-operations (4) informationObjects (5) version1 (0)
}
EXTENSION,
Extension {}
FROM Manufacturer-specific-service-extension-class-asn1-97
{ iso (1) standard (0) pss1-generic-procedures (11582) msi-class-asn1-97 (11) }
Name
FROM Name-Operations-asn1-97
{ iso (1) standard (0) pss1-name (13868) name-operations-asn1-97 (1) }
BasicService
FROM Call-Diversion-Operations-asn1-97
{ iso (1) standard (0) pss1-call-diversion (13873)
call-diversion-operations-asn1-97 (1) }
basicServiceNotProvided,
supplementaryServiceInteractionNotAllowed,
userNotSubscribed
FROM General-Error-List
{itu-t (0) recommendation (0) q (17) 950 (950) general-error-list (1)}
PresentedAddressUnscreened
FROM Addressing-Data-Elements-asn1-97
{ iso (1) standard (0) pss1-generic-procedures (11582)
addressing-data-elements-asn1-97 (20) }
CallIdentity, establishmentFailure
FROM Path-Replacement-Operations-asn1-97
{iso (1) standard (0) pss1-path-replacement (13874) pr-operations-asn1-97(1)}
;
Make-Call-Request-Operations OPERATION::= {
mCRequest | mCAlerting | mCInform }
ETSI
13 ETSI TS 102 257 V1.1.1 (2003-08)
Table 1: Operations in support of SS-MCR (continued)
mCRequest OPERATION ::= {
ARGUMENT MCRequestArg
RESULT MCRequestResult
ERRORS {userNotSubscribed|
basicServiceNotProvided|
supplementaryServiceInteractionNotAllowed|
invalidDestinationNumber|
invalidCooperationNumber|
mCRequestNotAllowed|
mCExecutionNotAllowed|
mCDestUserBusy|
mCCoopUserBusy|
mCCoopUserRejected|
establishmentFailure|
unspecified}
CODE local: 112
}
mCInform OPERATION ::= {
ARGUMENT MCInformArg
RETURN RESULT FALSE
ALWAYS RESPONDS FALSE
ERRORS {userNotSubscribed|
basicServiceNotProvided|
supplementaryServiceInteractionNotAllowed|
invalidDestinationNumber|
mCExecutionNotAllowed|
mCDestUserBusy|
unspecified}
CODE local: 113
}
mCAlerting OPERATION ::= {
ARGUMENT MCAlertingArg
RETURN RESULT FALSE
ALWAYS RESPONDS FALSE
CODE local: 114
}
MCRequestArg ::= SEQUENCE
{
callType CallType,
retainOrigCall BOOLEAN DEFAULT TRUE,
destinationAddress PresentedAddressUnscreened,
requestingAddress [0] PresentedAddressUnscreened OPTIONAL,
cooperatingAddress [1] PresentedAddressUnscreened OPTIONAL,
correlation Correlation,
extensions MCRExtensions OPTIONAL,
...
}
MCRequestResult ::= SEQUENCE
{
extensions MCRExtensions OPTIONAL,
...
}
ETSI
14 ETSI TS 102 257 V1.1.1 (2003-08)
Table 1: Operations in support of SS-MCR (concluded)
MCInformArg ::= SEQUENCE
{
requestingAddress [0] PresentedAddressUnscreened OPTIONAL,
cooperatingAddress [1] PresentedAddressUnscreened OPTIONAL,
correlation Correlation,
extensions MCRExtensions OPTIONAL,
...
}
MCAlertingArg ::= SEQUENCE
{
correlation Correlation,
extensions MCRExtensions OPTIONAL,
...
}
CallType ::= CHOICE
{
basicService BasicService,
cisc NULL
}
Correlation ::= SEQUENCE
{
correlationData CallIdentity,
correlationReason CorrelationReason OPTIONAL
}
CorrelationReason ::= INTEGER
{
unknown (0),
mCACommunication (1),
cTIApplication (2)
} (0.255)
MCRExtensions ::= CHOICE
{
none NULL,
single [0] IMPLICIT Extension
{ { MakeCallRequestExtension } } ,
multiple [1] IMPLICIT SEQUENCE OF Extension
{ { MakeCallRequestExtension } }
}
MakeCallRequestExtension EXTENSION::= {.}
invalidDestinationNumber ERROR ::= {CODE local : 1030}
invalidCooperationNumber ERROR ::= {CODE local : 1031}
mCRequestNotAllowed ERROR ::= {CODE local : 1032}
mCExecutionNotAllowed ERROR ::= {CODE local : 1033}
mCDestUserBusy ERROR ::= {CODE local : 1034}
mCCoopUserBusy ERROR ::= {CODE local : 1035}
mCCoopUserRejected ERROR ::= {CODE local : 1036}
unspecified ERROR ::= {PARAMETER Extension
{ { MakeCallRequestExtension } }
CODE local : 1008
}
END -- of SS-MCR-Operations
ETSI
15 ETSI TS 102 257 V1.1.1 (2003-08)
6.3.2 Information elements
6.3.2.1 Facility information element
The operations defined in clause 6.3.1 shall be coded in the Facility information element in accordance with
ECMA-165 [3].
When conveying the invoke APDUs of the operations defined in clause 6.3.1, the destination Entity data element of the
NFE shall contain the value endPINX.
When conveying the invoke APDU of operation mCRequest defined in clause 6.3.1, the interpretation APDU shall be
set to value rejectAnyUnrecognisedInvokePdu or shall be omitted.
When conveying the invoke APDU of operation mCInform or mCAlerting defined in clause 6.3.1, the interpretation
APDU shall be set to value discardAnyUnrecognisedInvokePdu.
6.3.2.2 Other information elements
Any other information element shall be coded in accordance with ECMA-143 [2].
6.3.3 Messages
The Facility information element shall be conveyed in messages as specified in clause 10 of ECMA-165 [3].
6.4 SS-MCR state definitions
6.4.1 States at the Requesting PINX
The procedures for the Requesting PINX are written in terms of the following conceptual states existing within the
SS-MCR Control entity in that PINX in association with a particular SS-MCR request from the Requesting User.
6.4.1.1 State MCR-Idle
SS-MCR is not operating.
6.4.1.2 State MCR-Active
SS-MCR is operating. A mCRequest invoke APDU was sent to the Co-operating PINX. The Requesting PINX awaits
the result of this operation.
6.4.2 States at the Co-operating PINX
The procedures for the Co-operating PINX are written in terms of the following conceptual states existi
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...