ISO/IEC 19460:2003
(Main)Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Single Step Call Transfer supplementary service
Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Single Step Call Transfer supplementary service
ISO/IEC 19460:2003 specifies the signalling protocol for the support of the Single Step Call Transfer supplementary service (SS-SSCT) at the Q reference point between Private Integrated Network services eXchanges (PINXs) connected together within a Private Integrated Services Network (PISN). SS-SSCT is a supplementary service which enables a user, user A, to transform an existing call between user A and user B into a new call between user B and a user C whereby user A does not have a call established with user C prior to call transfer. The Q reference point is defined in ISO/IEC 11579-1. Service specifications are produced in three stages and according to the method specified in ETS 300 387. ISO/IEC 19460:2003 contains the stage 3 specification for the Q reference point and satisfies the requirements identified by the stage 1 and stage 2 specifications in ISO/IEC 19459. The signalling protocol for SS-SSCT operates on top of the signalling protocol for basic circuit switched call control, as specified in ISO/IEC 11572, and uses certain aspects of the generic procedures for the control of supplementary services specified in ISO/IEC 11582. ISO/IEC 19460:2003 also specifies additional signalling protocol requirements for the support of interactions at the Q reference point between Single Step Call Transfer and other supplementary services and ANFs. ISO/IEC 19460:2003 is applicable to PINXs which can interconnect to form a PISN.
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseau privé à intégration de services — Protocole de signalisation d'interéchange — Service supplémentaire de transfert d'appel à pas unique
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 19460
Second edition
2003-04-01
Information technology —
Telecommunications and information
exchange between systems — Private
Integrated Services Network —
Inter-exchange signalling protocol —
Single Step Call Transfer supplementary
service
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Réseau privé à intégration de
services — Protocole de signalisation d'interéchange — Service
supplémentaire de transfert d'appel à pas unique
Reference number
ISO/IEC 19460:2003(E)
©
ISO/IEC 2003
---------------------- Page: 1 ----------------------
ISO/IEC 19460:2003(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO/IEC 2003
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2003 — All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19460:2003(E)
Contents
Foreword v
Introduction vi
1 Scope 1
2 Conformance 1
3 Normative references 1
4 Terms and definitions 2
4.1 External definitions 2
4.2 Other definitions 3
4.2.1 Rerouting number 3
4.2.2 Rerouting PINX 3
4.2.3 Transferred PINX 3
4.2.4 Transferred-To PINX 3
4.2.5 Transferring PINX 3
5 Acronyms 3
6 Signalling protocol for the support of SS-SSCT 4
6.1 SS-SSCT description 4
SS-SSCT operational requirements
6.2 4
6.2.1 Provision/Withdrawal 4
6.2.2 Requirements on a Transferring PINX 4
6.2.3 Requirements on a Rerouting PINX 4
6.2.4 Requirements on a Transferred PINX 4
6.2.5 Requirements on a Transferred-To PINX 4
6.2.6 Requirements on a Transit PINX 4
6.3 SS-SSCT coding requirements 5
Operations
6.3.1 5
6.3.2 Information elements 7
6.3.3 Messages 7
6.4 SS-SSCT state definitions 8
6.4.1 States at a Transferring PINX 8
6.4.2 States at a Rerouting PINX 8
6.4.3 States at a Transferred PINX 8
6.4.4 States at a Transferred-To PINX 8
6.5 SS-SSCT signalling procedures 8
6.5.1 Actions at a Transferring PINX 8
6.5.2 Procedures at the Rerouting PINX 9
6.5.3 Actions at a Transferred PINX 11
6.5.4 Actions at a Transferred-To PINX 11
6.5.5 Actions at a Transit PINX 12
6.5.6 Subsequent actions at Transferred and Transferred-To PINX 12
6.6 SS-SSCT impact of interworking with public ISDNs 12
6.6.1 Actions at a Gateway PINX 12
SS-SSCT impact of interworking with non-ISDNs
6.7 12
© ISO/IEC 2003 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 19460:2003(E)
6.7.1 Actions at a Gateway PINX 12
6.8 Protocol Interactions between SS-SSCT and other supplementary services and ANFs 13
6.8.1 Calling Name Identification Presentation (SS-CNIP) 13
6.8.2 Connected Name Identification Presentation (SS-CONP) 13
6.8.3 Completion of Calls to Busy Subscribers (SS-CCBS) 13
6.8.4 Completion of Calls on No Reply (SS-CCNR) 13
6.8.5 CallForwarding Unconditional (SS-CFU) 13
6.8.6 Call Forwarding Busy (SS-CFB) 13
6.8.7 Call Forwarding No Reply (SS-CFNR) 14
6.8.8 Call Deflection (SS-CD) 14
6.8.9 Call Transfer (SS-CT) 14
6.8.10 Path Replacement (ANF-PR) 14
Advice Of Charge (SS-AOC)
6.8.11 15
6.8.12 Call Offer (SS-CO) 16
6.8.13 Do Not Disturb (SS-DND) 16
6.8.14 Do Not Disturb Override (SS-DNDO) 16
6.8.15 Recall (SS-RE) 16
6.8.16 Call Intrusion (SS-CI) 16
6.8.17 Call Interception (ANF-CINT) 16
6.8.18 Transit Counter (SS-TC) 16
Route Restriction Class (ANF-RRC)
6.8.19 17
6.8.20 Authentication of the PISN (SS-WTAN) 17
6.8.21 Authentication of a WTM user (SS-WTAT) 17
6.8.22 Wireless Terminal Location Registration (SS-WTLR) 17
6.8.23 Wireless Terminal Mobility Incoming Call (ANF-WTMI) 17
6.8.24 Wireless Terminal Mobility Outgoing Call (ANF-WTMO) 17
6.8.25 Message Waiting Indication (SS-MWI) 17
6.8.26 User Mobility Incoming Call (ANF-PUMI) 17
6.8.27 User Mobility Outgoing Call (ANF-PUMO) 17
6.8.28 Private User Mobility - Registration (SS-PUMR) 17
6.8.29 Common Information (ANF-CMN) 17
6.8.30 Call Priority Interruption (Protection) (SS-CPI(P)) 17
6.9 SS-SSCT Parameter values (Timers) 17
6.9.1 Timer T1 17
6.9.2 Timer T2 18
6.9.3 Timer T3 18
Annexes
A - Protocol Implementation Conformance Statement (PICS) proforma 19
B - Imported ASN.1 definitions 27
C - Examples of message sequences 28
D - Specification and Description Language (SDL) representation of procedures 33
E - Additional feature identifier in module Common-Information-Operations 42
F - Difference between Single Step Call Transfer and Call Transfer by Rerouting 43
- ASN.1 definitions according to ITU-T Recs. X.208 / X.209
G 44
iv © ISO/IEC 2003 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 19460:2003(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the
specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the
development of International Standards through technical committees established by the respective organization to deal with
particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In
the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by
the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires
approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and
IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 19460 was prepared by ECMA (as ECMA-300) and was adopted, under a special “fast-track procedure”, by Joint
Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of ISO and IEC.
This second edition cancels and replaces the first edition (ISO/IEC 19460:2001), which has been technically revised.
© ISO/IEC 2003 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 19460:2003(E)
Introduction
This International Standard is one of a series of 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.
This International Standard specifies the signalling protocol for use at the Q reference point in support of the Call Transfer
supplementary service. The protocol defined in this International Standard forms part of the PSS1 protocol (informally known
as QSIG).
This International Standard 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 JTC 1, ITU-T, ETSI and other international and national standardization
bodies. It represents a pragmatic and widely based consensus.
vi © ISO/IEC 2003 – All rights reserved
---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO/IEC 19460:2003(E)
Information technology — Telecommunications and information
exchange between systems — Private Integrated Services Network —
Inter-exchange signalling protocol — Single Step Call Transfer
supplementary service
1Scope
This International Standard specifies the signalling protocol for the support of the Single Step Call Transfer supplementary
service (SS-SSCT) at the Q reference point between Private Integrated Network services eXchanges (PINXs) connected
together within a Private Integrated Services Network (PISN).
SS-SSCT is a supplementary service which enables a user, user A, to transform an existing call between user A and user B into
a new call between user B and a user C whereby user A does not have a call established with user C prior to call transfer.
The Q reference point is defined in ISO/IEC 11579-1.
Service specifications are produced in three stages and according to the method specified in ETS 300 387. This International
Standard contains the stage 3 specification for the Q reference point and satisfies the requirements identified by the stage 1 and
stage 2 specifications in ISO/IEC 19459.
The signalling protocol for SS-SSCT operates on top of the signalling protocol for basic circuit switched call control, as
specified in ISO/IEC 11572, and uses certain aspects of the generic procedures for the control of supplementary services
specified in ISO/IEC 11582.
This International Standard also specifies additional signalling protocol requirements for the support of interactions at the Q
reference point between Single Step Call Transfer and other supplementary services and ANFs.
This International Standard is applicable to PINXs which can interconnect to form a PISN.
2 Conformance
In order to conform to this International Standard, a PINX shall satisfy the requirements identified in the Protocol
Implementation Conformance Statement (PICS) proforma in annex A.
Conformance to this International Standard includes conforming to those clauses that specify protocol interactions between
SS-SSCT 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 Normative references
The following referenced documents are indispensable for the application of this document. For dated references, only the
edition cited applies. For undated references, the latest edition of the referenced document (including any amendments)
applies.
ISO/IEC 11571:1998, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Networks - Addressing
ISO/IEC 11572:2000, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Circuit mode bearer services - Inter-exchange signalling procedures and protocol
ISO/IEC 11574:2000, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Circuit-mode 64 kbit/s bearer services - Service description, functional capabilities and
information flows
ISO/IEC 11579-1:1994, Information technology - Telecommunications and information exchange between systems - Private
integrated services network - Part 1: Reference configuration for PISN Exchanges (PINX)
ISO/IEC 11582:2002, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Generic functional protocol for the support of supplementary services - Inter-exchange
signalling procedures and protocol
© ISO/IEC 2003 – All rights reserved 1
---------------------- Page: 7 ----------------------
ISO/IEC 19460:2003(E)
ISO/IEC 13868:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Name identification supplementary services
ISO/IEC 13869:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Call Transfer supplementary service
ISO/IEC 13873:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Call Diversion supplementary services
ISO/IEC 13874:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Path Replacement additional network feature
ISO/IEC 15050:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Advice Of Charge supplementary services
ISO/IEC 15054:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Call Interception additional network feature
ISO/IEC 15056:1997, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Transit counter additional network feature
ISO/IEC 15772:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Common Information additional network feature
ISO/IEC 15992:2003, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Inter-exchange signalling protocol - Call Priority Interruption and Call Priority Interruption
Protection supplementary services
ISO/IEC 19459:2001, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Specification, functional model and information flows - Single Step Call Transfer Supplementary
Service
ETS 300 387:1994, Private Telecommunication Network (PTN); Method for the specification of basic and supplementary
services
ITU-T Rec. I.112:1993, Vocabulary of terms for ISDNs
ITU-T Rec. I.210:1993, Principles of telecommunication services supported by an ISDN and the means to describe them
ITU-T Rec. Q.950:2000, Supplementary services protocols, structure and general principles
ITU-T Rec. Z.100:1999, Specification and description language (SDL)
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1 External definitions
This International Standard uses the following terms defined in other documents:
− Application Protocol Data Unit (APDU) (ISO/IEC 11582)
− Basic Service (ITU-T Rec. I.210)
− Gateway PINX (ISO/IEC 11572)
− Complete Number (ISO/IEC 11571)
− Interpretation APDU (ISO/IEC 11582)
− Network Facility Extension (NFE) (ISO/IEC 11582)
− New Call, New Connection (ISO/IEC 19459)
− Original Call, Original Connection (ISO/IEC 19459)
− Originating PINX (ISO/IEC 11582)
− Private Integrated Services Network (PISN) (ISO/IEC 11579-1)
− Private Integrated services Network eXchange (PINX) (ISO/IEC 11579-1)
2 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC 19460:2003(E)
− Subsequent PINX (ISO/IEC 11582)
− Signalling (ITU-T Rec. I.112)
− Supplementary Service (ITU-T Rec. I.210)
− Supplementary Service Control Entity (ISO/IEC 11582)
− Terminating PINX (ISO/IEC 11582)
− Transit PINX (ISO/IEC 11582)
− User (ISO/IEC 11574)
− User A, Transferring user (ISO/IEC 19459)
− User B, Transferred user (ISO/IEC 19459)
− User C, Transferred-to user (ISO/IEC 19459)
4.2 Other definitions
4.2.1 Rerouting number
The number of the Transferred-to user.
4.2.2 Rerouting PINX
A PINX on the call path of the original call, that reroutes that call to user C. This can either be the Transferring, the Transferred
or a Transit PINX being capable of performing the rerouting function.
4.2.3 Transferred PINX
The End PINX which is on the end of the original call nearest to user B.
4.2.4 Transferred-To PINX
The End PINX which is on the end of the new call nearest to user C.
4.2.5 Transferring PINX
The End PINX which initiates single step call transfer procedures on behalf of user A.
5 Acronyms
APDU Application Protocol Data Unit
ASN.1 Abstract Syntax Notation no. 1
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-SSCT Supplementary Service Single Step Call Transfer
© ISO/IEC 2003 – All rights reserved 3
---------------------- Page: 9 ----------------------
ISO/IEC 19460:2003(E)
6 Signalling protocol for the support of SS-SSCT
6.1 SS-SSCT description
SS-SSCT is a supplementary service which enables a user, user A, to transform an existing call between user A and user B into
a new call between user B and a user C whereby user A does not have a call established with user C prior to call transfer.
This supplementary service is applicable to all basic services defined in ISO/IEC 11574.
6.2 SS-SSCT operational requirements
6.2.1 Provision/Withdrawal
Provision and withdrawal shall be in accordance with 6.2.1 of ISO/IEC 19459.
6.2.2 Requirements on a Transferring PINX
The basic call procedures specified in ISO/IEC 11572 shall be supported.
Generic procedures for the call-related control of supplementary services, as specified in ISO/IEC 11582 for an End PINX,
shall apply.
6.2.3 Requirements on a Rerouting PINX
The basic call procedures specified in ISO/IEC 11572 shall be supported.
Generic procedures for the call-related control of supplementary services, as specified in ISO/IEC 11582 for an End PINX,
shall apply.
6.2.4 Requirements on a Transferred PINX
The basic call procedures specified in ISO/IEC 11572 shall be supported.
Generic procedures for the call-related control of supplementary services, as specified in ISO/IEC 11582 for an End PINX,
shall apply.
6.2.5 Requirements on a Transferred-To PINX
The basic call procedures specified in ISO/IEC 11572 shall be supported.
Generic procedures for the call-related control of supplementary services, as specified in ISO/IEC 11582 for an End PINX,
shall apply.
6.2.6 Requirements on a Transit PINX
The basic call procedures specified in ISO/IEC 11572 shall be supported.
Generic procedures for the call-related control of supplementary services, as specified in ISO/IEC 11582 for a Transit PINX,
shall apply.
4 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC 19460:2003(E)
6.3 SS-SSCT coding requirements
6.3.1 Operations
The operations defined in Abstract Syntax Notation number 1 (ASN.1) in table 1 shall apply. The notation is in accordance
with ITU-T Rec. X.680 and X.690. The ITU-T Rec. X.208 and X.209 superseded version is in annex G.
Table 1 - Operations in support of SS-SSCT
Single-Step-Call-Transfer-Operations-asn1-97
{ iso(1) standard (0) pss1-single-step-call-transfer (19460)
single-step-call-transfer-operations-asn1-97 (1)}
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)}
supplementaryServiceInteractionNotAllowed, notAvailable, invalidCallState
FROM General-Error-List
{ ccitt recommendation q 950 general-error-list (1) }
PresentedAddressScreened, PartyNumber FROM Addressing-Data-Elements-asn1-97
{iso(1) standard (0) pss1-generic-procedures (11582)
addressing-data-elements-asn1-97 (20)}
PSS1InformationElement FROM PSS1-generic-parameters-definition-asn1-97
{iso(1) standard (0) pss1-generic-procedures (11582)
pss1-generic-parameters-asn1-97 (17)}
callTransferUpdate, callTransferComplete, callTransferActive, subaddressTransfer,
invalidRerouteingNumber, establishmentFailure FROM Call-Transfer-Operations-asn1-97
{iso(1) standard (0) pss1-call-transfer (13869) call-transfer-operations-asn1-97 (1)};
Single-Step-Call-Transfer-Operations OPERATION ::= { ssctInitiate | ssctSetup | ssctPostDial |
ssctDigitInfo }
ssctInitiate OPERATION ::= {
-- sent from the Transferring PINX to the Rerouting PINX
ARGUMENT SSCTInitiateArg
RESULT DummyRes
ERRORS { notAvailable | invalidCallState | invalidRerouteingNumber |
establishmentFailure | unspecified |
supplementaryServiceInteractionNotAllowed }
CODE local: 99}
© ISO/IEC 2003 – All rights reserved 5
---------------------- Page: 11 ----------------------
ISO/IEC 19460:2003(E)
Table 1 - Operations in support of SS-SSCT (continued)
ssctSetup OPERATION ::= {
-- sent from the Rerouting PINX to the Transferred-To PINX
ARGUMENT SSCTSetupArg
RETURN RESULT FALSE
ALWAYS RESPONDS FALSE
CODE local: 100}
ssctPostDial OPERATION ::= {
-- sent from the Rerouting PINX to the Transferred PINX
ARGUMENT DummyArg
RETURN RESULT FALSE
ALWAYS RESPONDS FALSE
CODE local: 101}
ssctDigitInfo OPERATION ::= {
-- sent from the Transferred PINX to the Rerouting PINX
ARGUMENT SSCTDigitInfoArg
RETURN RESULT FALSE
ALWAYS RESPONDS FALSE
CODE local: 102}
DummyArg ::= CHOICE {
null NULL,
single [1] IMPLICIT Extension{{SSCTExtSet}},
multiple [2] IMPLICIT SEQUENCE OF Extension{{SSCTExtSet}}}
DummyRes ::= CHOICE {
null NULL,
single [1] IMPLICIT Extension{{SSCTExtSet}},
multiple [2] IMPLICIT SEQUENCE OF Extension{{SSCTExtSet}}}
SSCTInitiateArg ::= SEQUENCE {
rerouteingNumber PartyNumber, -- Transferred-To Number
transferredAddress PresentedAddressScreened,
awaitConnect AwaitConnect,
transferredName [1] Name OPTIONAL,
transferringAddress [2] PresentedAddressScreened OPTIONAL,
transferringName [3] Name OPTIONAL,
argumentExtension CHOICE {
single [4] IMPLICIT Extension{{SSCTExtSet}},
multiple [5] IMPLICIT SEQUENCE OF Extension{{SSCTExtSet}}
} OPTIONAL
}
AwaitConnect ::= BOOLEAN
-- FALSE = release the original call upon ALERTING received
-- TRUE = release the original call upon CONNECT received
6 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/IEC 19460:2003(E)
Table 1 - Operations in support of SS-SSCT (concluded)
SSCTSetupArg ::= SEQUENCE {
transferringAddress [1] PresentedAddressScreened OPTIONAL,
transferringName [2] Name OPTIONAL,
argumentExtension CHOICE {
single [3] IMPLICIT Extension{{SSCTExtSet}},
multiple [4] IMPLICIT SEQUENCE OF Extension{{SSCTExtSet}}
} OPTIONAL
}
SSCTDigitInfoArg ::= SEQUENCE {
reroutingNumber[1] PartyNumber OPTIONAL,
-- remaining digits of the Transferred-To Number
sendingComplete [2] IMPLICIT NULL OPTIONAL,
argumentExtension CHOICE {
single [3] IMPLICIT Extension{{SSCTExtSet}},
multiple [4] IMPLICIT SEQUENCE OF Extension{{SSCTExtSet}}
} OPTIONAL
}
SSCTExtSet EXTENSION ::= {…}
unspecified ERROR ::= {
PARAMETER Extension{{SSCTExtSet}}
CODE local: 1008}
END -- of SSCT Operations-asn1-97
6.3.2 Information elements
6.3.2.1 Facility information element
APDUs of the operations defined in 6.3.1 shall be coded in the Facility information element in accordance with
ISO/IEC 11582.
When conveying the invoke APDU of the operations defined in 6.3.1, the destinationEntity data element of the NFE shall
contain value endPINX.
When conveying the invoke APDU of operation ssctSetup, the Interpretation APDU shall contain value
discardAnyUnrecognisedInvokePdu.
When conveying the invoke APDU of operations ssctInitiate, ssctPostDial or ssctDigitInfo the Interpretation APDU shall be
included with the value rejectAnyUnrecognisedInvokePdu or omitted.
6.3.2.2 Information elements embedded in the Facility information element
APDUs of the operations defined in 6.3.1 may contain information elements defined in and coded according to ISO/IEC 11572.
These shall be embedded in data elements of type PSS1InformationElement as specified in annex B of ISO/IEC 11582.
6.3.2.3 Other information elements
Information elements used during the establishment of the new connection shall be coded as specified in ISO/IEC 11572.
6.3.3 Messages
Except for cases where a basic call message is to be conveyed at the same time, the Facility information element shall be
conveyed in a FACILITY message as specified in ISO/IEC 11582.
Messages used during the establishment of the new connection and release of the original connection shall be as specified in
ISO/IEC 11572 and, where applicable, augmented in ISO/IEC 11582.
© ISO/IEC 2003 – All rights reserved 7
---------------------- Page: 13 ----------------------
ISO/IEC 19460:2003(E)
6.4 SS-SSCT state definitions
6.4.1 States at a Transferring PINX
The procedures at the Transferring PINX are written in terms of the following conceptual states existing within the SS-SSCT
control entity in that PINX in association with a particular SS-SSCT request from the transferring user.
6.4.1.1 SSCT-Idle
SS-SSCT is not operating.
6.4.1.2 SSCT-Await-Initiate-Response
A ssctInitiate invoke APDU has been sent to the Rerouting PINX.
6.4.2 States at a Rerouting PINX
The procedures at the Rerouting PINX are written in terms of the following conceptual states existing within the SS-SSCT
control entity in that PINX.
6.4.2.1 SSCT-Idle
SS-SSCT is not operating.
6.4.2.2 SSCT-Await-Setup-Response-Alert
A ssctInitiate invoke APDU has been received with element waitConnect set to FALSE. A ssctSetup invoke APDU has been
sent to the Transferred-To PINX.
6.4.2.3 SSCT-Await-Setup-Response-Connect
A ssctInitiate invoke APDU has been received with element waitConnect set to TRUE. A ssctSetup invoke APDU has been
sent to the Transferred-To PINX.
6.4.2.4 SSCT-Await-Info
A ssctPostDial invoke APDU has been sent to the Transferred PINX and further address information can be received in overlap
mode.
6.4.3 States at a Transferred PINX
The procedures at the Transferred PINX are written in terms of the following conceptual states existing within the SS-SSCT
control entity in that PINX in association with the original call, i.e. a particular call of the transferred user.
6.4.3.1 CT-Idle
SS-SSCT is not operating.
NOTE 1 - As the Transferred PINX acts in the same way as a SS-CT Primary PINX in case of SS-CT by join sub-clause 6.4.2.1 (States at a
Primary PINX - CT-Idle) of ISO/IEC 13869 applies accordingly.
6.4.4 States at a Transferred-To PINX
The procedures at the Transferred-To PINX are written in terms of the following conceptual states existing within the SS-SSCT
control entity in that PINX.
6.4.4.1 SSCT-Idle
SS-SSCT is not operating.
6.5 SS-SSCT signalling procedures
References in this clause to protocol control states refer to basic call protocol control states defined in ISO/IEC 11572.
NOTE 2 - The specification in this section is based on each of the End PINXs being a different PINX, but this section is also applicable to
scenarios where two or more of the four PINXs are the same. In those scenarios some of the signalling procedures and message flows
described in this section are internal to the PINX implementation and therefore outside the scope of this International Standard.
Annex C contains some examples of message sequences.
6.5.1 Actions at a Transferring PINX
The SDL representation of procedures at a Transferring PINX is shown in D.1 of annex D.
8 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 14 ----------------------
ISO/IEC 19460:2003(E)
6.5.1.1 Normal Procedures
On receipt of a valid request for SS-SSCT from user A while in state SSCT-Idle for a call between user B and user A which is
in protocol control state Active (the original call), the Transferring PINX shall
- send a ssctInitiate invoke APDU in a FACILITY message towards the Transferred PINX using the call reference of the
original call. The ssctInitiate invoke APDU shall include the following elements:
· awaitConnect set to TRUE if the original call shall be released after a CONNECT message from the Transferred-To
PINX and set to FALSE if it shall be released on receipt of an ALERTING message from the Transferred-To PINX;
· rerouteingNumber set to the party number of the transferred-to user (i.e., user C), as far as available;
· transferredAddress set to the address of the transferred user, i.e. user B;
· optionally transferredName set to the name of the transferred user, i.e. user B;
· optionally elements transferringAddress and transferringName set to the address and name of the transferring user, i.e.
user A;
- start Timer T1;
- enter state SSCT-Await-Initiate-Response.
On receipt in state SSCT-Await-Initiate-Response of a DISCONNECT message with a ssctInitiate return result APDU from the
Rerouting PINX, using the call reference of the original call, the Transferring PINX shall continue call clearing of the original
call according to basic call procedures, stop timer T1, and enter state SSCT-I
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.