ISO/IEC 13865:2003
(Main)Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Specification, functional model and information flows — Call Transfer supplementary service
Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Specification, functional model and information flows — Call Transfer supplementary service
ISO/IEC 13865:2003 specifies Supplementary Service Call Transfer (SS-CT), which is applicable to various basic services supported by Private Integrated Services Networks (PISNs). Basic services are specified in ISO/IEC 11574. SS-CT is a supplementary service which enables a user to transform two of that user's calls (of which one must be answered) into a new call between the other two users of the two calls. Supplementary service specifications are produced in three stages, according to the method described in ETS 300 387. ISO/IEC 13865:2003 contains the stage 1 and stage 2 specifications of SS-CT. The stage 1 specification (clause 6) specifies the supplementary service as seen by users of PISNs. The stage 2 specification (clauses 7 and 8) identifies the functional entities involved in the supplementary service and the information flows between them. ISO/IEC 13865:2003 contains two stage 2 specifications reflecting different ways of operating the service within the network: transfer by join and transfer by rerouteing.
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseau privé à intégration de services — Spécification, modèle fonctionnel et flux d'informations — Service supplémentaire de transfert d'appel
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 13865
Second edition
2003-04-01
Information technology —
Telecommunications and information
exchange between systems — Private
Integrated Services Network —
Specification, functional model and
information flows — 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 — Spécification, modèle fonctionnel et flux d'informations —
Service supplémentaire de transfert d'appel
Reference number
ISO/IEC 13865:2003(E)
©
ISO/IEC 2003
---------------------- Page: 1 ----------------------
ISO/IEC 13865: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 13865: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 2
4.2.1 Additional network feature 2
4.2.2 Alerting 2
4.2.3 Answered 3
4.2.4 Call, basic call 3
4.2.5 Primary call 3
4.2.6 Secondary call 3
4.2.7 Transfer by Join 3
4.2.8 Transfer by rerouteing 3
User A
4.2.9 3
4.2.10 User B 3
4.2.11 User C 3
5 Acronyms 3
6 SS-CT stage 1 specification 4
6.1 Description 4
6.1.1 General description 4
6.1.2 Qualifications on applicability to telecommunications services 4
Procedures
6.2 4
6.2.1 Provision/withdrawal 4
6.2.2 Normal procedures 4
6.2.3 Exceptional procedures 5
6.3 Interactions with other supplementary services and ANFs 5
6.3.1 Calling Line Identification Presentation (SS-CLIP) 5
6.3.2 Connected Line Identification Presentation (SS-COLP) 5
6.3.3 Calling/Connected Line Identification Restriction (SS-CLIR) 5
6.3.4 Calling Name Identification Presentation (SS-CNIP) 5
6.3.5 Connected Name Identification Presentation (SS-CONP) 5
6.3.6 Calling/connected Name Identification Restriction (SS-CNIR) 5
6.3.7 Completion of Calls to Busy Subscribers (SS-CCBS) 5
6.3.8 Completion of Calls on No Reply (SS-CCNR) 5
6.3.9 Call Forwarding Services 6
6.3.10 Path Replacement (ANF-PR) 6
6.4 Interworking considerations 6
6.4.1 User B and/or User C in another network 6
User A in another network
6.4.2 6
6.5 Overall SDL 6
© ISO/IEC 2003 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 13865:2003(E)
7 SS-CT stage 2 specification for transfer by join 8
7.1 Functional model 8
7.1.1 Functional model description 8
7.1.2 Description of functional entities 8
7.1.3 Relationship of functional model to Basic Call functional model 9
7.2 Information flows 10
7.2.1 Definition of information flows 10
7.2.2 Relationship of information flows to basic call information flows 12
7.2.3 Examples of information flow sequences 12
7.3 Functional Entity actions 15
7.3.1 Functional Entity actions of FE1 15
7.3.2 Functional Entity actions of FE2 15
Functional Entity actions of FE3
7.3.3 15
7.3.4 Functional Entity actions of FE4 15
7.4 Functional Entity behaviour 15
7.4.1 Behaviour of FE1 15
7.4.2 Behaviour of FE2 16
7.4.3 Behaviour of FE3 18
7.4.4 Behaviour of FE4 19
7.5 Allocation of functional entities to physical locations 20
Interworking considerations
7.6 20
8 SS-CT stage 2 specification for transfer by rerouteing 21
8.1 Functional model 21
8.1.1 Functional model description 21
8.1.2 Description of functional entities 22
8.1.3 Relationship of functional model to Basic Call functional model 22
8.2 Information flows 23
8.2.1 Definition of information flows 23
8.2.2 Relationship of information flows to basic call information flows 25
8.2.3 Examples of information flow sequences 25
8.3 Functional Entity actions 29
8.3.1 Functional Entity actions of FE1 29
8.3.2 Functional Entity actions of FE5 29
8.3.3 Functional Entity actions of FE6 29
8.3.4 Functional Entity actions of FE7 29
8.3.5 Functional Entity actions of FE4 29
8.4 Functional Entity behaviour 29
Behaviour of FE5
8.4.1 30
8.4.2 Behaviour of FE6 31
8.4.3 Behaviour of FE7 32
8.5 Allocation of functional entities to physical locations 33
Annex A - Bibliography 34
iv © ISO/IEC 2003 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 13865: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 13865 was prepared by ECMA (as ECMA-177) 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 13865:1995), which has been technically revised.
© ISO/IEC 2003 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 13865: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 Call Transfer supplementary service.
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 13865:2003(E)
Information technology — Telecommunications and information exchange
between systems — Private Integrated Services Network — Specification,
functional model and information flows — Call Transfer supplementary
service
1Scope
This International Standard specifies Supplementary Service Call Transfer (SS-CT), which is applicable to various basic
services supported by Private Integrated Services Networks (PISNs). Basic services are specified in ISO/IEC 11574.
SS-CT is a supplementary service which enables a user to transform two of that user's calls (of which one must be answered)
into a new call between the other two users of the two calls.
Supplementary service specifications are produced in three stages, according to the method described in ETS 300 387. This
International Standard contains the stage 1 and stage 2 specifications of SS-CT. The stage 1 specification (clause 6) specifies
the supplementary service as seen by users of PISNs. The stage 2 specification (clauses 7 and 8) identifies the functional
entities involved in the supplementary service and the information flows between them.
This International Standard contains two stage 2 specifications reflecting different ways of operating the service within the
network: transfer by join and transfer by rerouteing.
2 Conformance
In order to conform to this International Standard, a stage 3 standard shall specify signalling protocols and equipment
behaviour that are capable of being used in a PISN which supports the supplementary services specified in this International
Standard. 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 clauses 7 and 8 (stage 2) which are relevant to the interface or equipment to which the stage 3 standard
applies.
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 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 13864:1995, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Specification, functional model and information flows - Name identification supplementary
services
ISO/IEC 14136:1995, Information technology - Telecommunications and information exchange between systems - Private
Integrated Services Network - Specification, functional model and information flows - Identification supplementary services
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. Z.100:1999, Specification and description language (SDL)
© ISO/IEC 2003 – All rights reserved 1
---------------------- Page: 7 ----------------------
ISO/IEC 13865:2003(E)
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:
− Basic Service (ITU-T Rec. I.210)
− Connection (ITU-T Rec. I.112)
− Private Integrated Services Network (PISN) (ISO/IEC 11579-1)
− Private Integrated services Network eXchange (PINX) (ISO/IEC 11579-1)
− Service (ITU-T Rec. I.112)
− Signalling (ITU-T Rec. I.112)
− Supplementary Service (ITU-T Rec. I.210)
− User (ISO/IEC 11574)
This International Standard refers to the following basic call functional entities (FEs) defined in ISO/IEC 11574:
− Call Control (CC)
− Call Control Agent (CCA)
This International Standard refers to the following basic call inter-FE relationships defined in ISO/IEC 11574:
− r1
− r2
− r3
This International Standard refers to the following basic call information flows defined in ISO/IEC 11574:
− Channel_Acknowledge request/indication
− Release request/indication
− Release response/confirmation
− Setup request/indication
− Setup response/confirmation
This International Standard refers to the following basic call information flow elements defined in ISO/IEC 11574:
− Call History (CH)
− Connected Number (CN)
− Connected Subaddress (CS)
This International Standard refers to the following Connected Line Identification Presentation information flow elements
defined in ISO/IEC 14136:
− Connected Number (CN)
− Connected Subaddress (CS)
4.2 Other definitions
4.2.1 Additional network feature
A capability, over and above that of a basic service, provided by a PISN, but not directly to a PISN user.
4.2.2 Alerting
The state of the secondary call when the called user is being alerted but has not yet answered.
2 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC 13865:2003(E)
4.2.3 Answered
The state of the primary or secondary call after the called user has answered.
4.2.4 Call, basic call
An instance of the use of a basic service.
4.2.5 Primary call
One of the calls involved in the transfer. In the case of a transfer involving an unanswered call, the primary call is the answered
call. In the case where both calls are already answered, the primary call is chosen arbitrarily by the network.
4.2.6 Secondary call
The other call involved in the transfer.
4.2.7 Transfer by Join
The effecting of transfer by joining together the connections of the primary and secondary calls at User A's PINX.
4.2.8 Transfer by rerouteing
The effecting of transfer by establishing a new connection to replace all or part of the connections of the primary and secondary
calls.
4.2.9 User A
The served user, i.e. the user requesting Call Transfer.
4.2.10 User B
The other user in User A's primary call.
4.2.11 User C
The other user in User A's secondary call.
5 Acronyms
AI Alerting Indication
CC Call Control (functional entity)
CCA Call Control Agent (functional entity)
cfm confirmation
CH Call History (information flow element)
CID Call Identity (information flow element)
CN Connected Number (information flow element)
CS Connected Subaddress (information flow element)
CUG Closed User Group
ED End Designation (information flow element)
FE Functional Entity
ind indication
ISDN Integrated Services Digital Network
LCI Local Call Identities
PINX Private Integrated services Network eXchange
PISN Private Integrated Services Network
req request
resp response
RN Rerouteing Number (information flow element)
© ISO/IEC 2003 – All rights reserved 3
---------------------- Page: 9 ----------------------
ISO/IEC 13865:2003(E)
SDL Specification and Description Language
SS-CT Supplementary Service Call Transfer
TDR Terminal Detail Request
TE Terminal Equipment
TIDR Transfer Identity Result (information flow element)
TINR Transfer Initiate Result (information flow element)
TIVR Transfer Invoke Result (information flow element)
6 SS-CT stage 1 specification
6.1 Description
6.1.1 General description
SS-CT is a supplementary service which enables a served user (User A) to transform two of that users calls into a new call
between the other two users of the two calls (User B and User C). Each call can either be an incoming call to User A or an
outgoing call from User A. After successful invocation of SS-CT, User B and User C will no longer be able to communicate
with User A.
One of the calls may be an outgoing call that has not been answered by the other user (User C). After successful invocation of
SS-CT User A will no longer be able to communicate with User B. User B and User C will be in a position to communicate
with each other as soon as User C has answered.
NOTE - The establishment of either call as part of a request for transfer is outside the scope of this International Standard. This International
Standard assumes that both calls have already been established when the request for call transfer is made. This does not preclude an
implementation whereby a single user request causes the establishment of a call and its subsequent transfer.
6.1.2 Qualifications on applicability to telecommunications services
SS-CT is applicable to all basic services defined in ISO/IEC 11574.
6.2 Procedures
6.2.1 Provision/withdrawal
SS-CT shall be generally available to all PISN users with the ability to invoke it.
6.2.2 Normal procedures
6.2.2.1 Activation/deactivation/registration/interrogation
Not applicable.
6.2.2.2 Invocation and operation
A Call Transfer request from a user (User A) shall be accepted only if it identifies two of that user's calls where:
- both calls (to/from User B and to/from User C) have been answered; or
- one call (to/from User B) has been answered and the other is an outgoing call which is alerting User C; or
- one call (to/from User B) has been answered and the other is an unanswered outgoing call to User C in a non-ISDN.
It shall not be necessary for User A to place either call on hold prior to invocation, although either or both calls may be held.
The network shall ensure that the transfer attempt does not allow an illegal connection to be made, for example one which
would infringe CUG restrictions between User B and User C, or one which would result in a connection with a mixture of
incompatible bearer capabilities.
NOTE 1 - It is User A's responsibility to ensure that the two calls are otherwise compatible.
Bearer capabilities shall be considered compatible if they are the same. Bearer capabilities shall also be considered compatible
if the only attribute that differs is Information Transfer Capability and if one call has the value "Speech" and the other call is
interworking with a non-ISDN and has the value " 3,1 kHz audio."
NOTE 2 - The provision of interworking functions between different bearer capabilities is outside the scope of this International Standard.
4 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC 13865:2003(E)
The result of successful Call Transfer shall be a new call between users B and C, at which point the original connections to
User A shall be released. Both users B and C shall be informed of the transfer and the name and number of the other user (if
available and not subject to restriction), and whether the other user is still being alerted.
The network shall permit subaddresses to be exchanged between User B and User C after transfer.
If User C is being alerted at the time of completion of transfer, it shall continue to be alerted, and on answer shall be connected
to User B.
NOTE 3 - If the call resulting from the invocation of Call Transfer before answer fails to progress to the answered state within a certain time
other actions can be taken e.g., User A can be recalled and on answer be connected to User B. The definition of procedures to support recall
is outside the scope of this International Standard.
6.2.3 Exceptional procedures
6.2.3.1 Activation/deactivation/registration/interrogation
Not applicable.
6.2.3.2 Invocation and operation
Call Transfer shall be rejected under the following circumstances:
- if invalid call identities are specified;
- if neither of the calls is answered;
- if only one call is answered and the other is not an outgoing call which is either alerting a distant user or interworking with a
non-ISDN;
- if the two calls have incompatible bearer capabilities;
- if interconnection of User B and User C is not permitted.
If transfer is rejected, User A shall be informed of the reason and the existing calls shall be unaffected.
6.3 Interactions with other supplementary services and ANFs
Interactions with other supplementary services and ANFs for which PISN standards were available at the time of publication of
this International Standard are specified below.
6.3.1 Calling Line Identification Presentation (SS-CLIP)
No interaction.
6.3.2 Connected Line Identification Presentation (SS-COLP)
No interaction.
6.3.3 Calling/Connected Line Identification Restriction (SS-CLIR)
User B's and C's restriction requirements from the original call shall be used to restrict the presentation of that user's number to
the other user in a transferred call.
6.3.4 Calling Name Identification Presentation (SS-CNIP)
No interaction.
6.3.5 Connected Name Identification Presentation (SS-CONP)
No interaction.
6.3.6 Calling/connected Name Identification Restriction (SS-CNIR)
User B's and C's restriction requirements from the original call shall be used to restrict the presentation of that user's name to
the other user in a transferred call.
6.3.7 Completion of Calls to Busy Subscribers (SS-CCBS)
No interaction.
6.3.8 Completion of Calls on No Reply (SS-CCNR)
No interaction.
© ISO/IEC 2003 – All rights reserved 5
---------------------- Page: 11 ----------------------
ISO/IEC 13865:2003(E)
6.3.9 Call Forwarding Services
If Call Transfer occurs while User C is being alerted, the resulting call can subsequently undergo Call Forwarding on No Reply.
Call Transfer shall not affect the way in which chains of forwarding are controlled. Thus any hop counter value maintained in
order to determine whether a forwarding may occur shall have the same value after transfer as it had prior to the transfer. The
fact that a transfer has taken place shall not affect the way in which the counter value is subsequently modified due to
forwarding.
6.3.10 Path Replacement (ANF-PR)
No interaction.
NOTE - Path Replacement may be invoked as a direct consequence of performing transfer if the transfer is achieved by joining as opposed to
rerouteing.
6.4 Interworking considerations
Call Transfer may take place when one or both of the calls involves interworking with a public ISDN or a public or private non-
ISDN.
6.4.1 User B and/or User C in another network
Since the execution of the Call Transfer service need only involve the interconnection within the PISN of one end of each of
two established connections, the nature of the network (ISDN or non-ISDN) containing User B or User C makes no difference
to the operation of the service as seen by User A.
The PISN shall pass on any notifications associated with the transfer to the other network if the other network is capable of
receiving this information, the possibilities being the notifications that transfer has taken place, whether the transfer has taken
place prior to answer, the name and number (if appropriate) of the other User And the other user's subaddress and compatibility
information.
In the case where User B and User C are in the same network, the PISN may be able to cooperate with that network in order to
effect Call Transfer in that network.
6.4.2 User A in another network
The PISN shall accept transfer notifications from another network and pass them on to the PISN user. Transfer notifications
include notifications that transfer has taken place, whether the transfer has taken place prior to answer, the name and number of
the other user and the other user's subaddress and compatibility information. Where this information is not provided, a PISN
user will have to rely on in-band information.
6.5 Overall SDL
Figure 1 contains the dynamic description of SS-CT using the Specification and Description Language (SDL) defined in ITU-T
Rec. Z.100. The SDL process represents the behaviour of the network in providing SS-CT. The relationship of this process to
the basic call process is indicated in the annotations.
Input signals from the left and output signals to the left represent primitives from and to User A.
Input signals from the right and output signals to the right represent primitives from and to users B and C.
6 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/IEC 13865:2003(E)
Idle
A call transfer request is made
Transfer
with respect to the calls. One
request
(involving User B) should be
answered. The other (involving
Attempt to
User C) should be answered, alerting
connect User B
or have encountered interworking
to User C
with a non-ISDN
NO
Transfer
successful
The result is a call between User B
?
and User C. The call is an answered
YES
call, an alerting call, or a call which
has encountered interworking with a
Transfer
non-ISDN
successful
Get cause
Clear redundent
transfer
connections
reject
towards User A
Transfer notify
to User B
Transfer notify
to User C
Idle
Figure 1 - SS-CT, Overall SDL
© ISO/IEC 2003 – All rights reserved 7
---------------------- Page: 13 ----------------------
ISO/IEC 13865:2003(E)
7 SS-CT stage 2 specification for transfer by join
7.1 Functional model
7.1.1 Functional model description
The functional model shall comprise the following Functional Entities:
FE1 Transfer Invoke
FE2 Transfer Execute
FE3 Transfer Complete Receive
FE4 Transfer Notification Receive
There shall be two instances of FE3 and FE4, one of each associated with User B and User C.
The following functional relationships shall exist between these FEs:
rr between FE1 and FE2
rs between FE2 and FE3
rt between FE3 and the FE4 associated with the same user
ru between User B's FE4 and User C's FE4
rv between User B's FE3 and User C's FE3
Figure 2 shows these FEs and relationships.
User A
FE 1
rr
FE 2
rs rs
rv
FE3 FE 3
rt rt
User B
User C
FE4 FE4
ru
Figure 2 - Functional Model for SS-CT
7.1.2 Description of functional entities
7.1.2.1 Transfer invoke Functional Entity, FE1
This FE acts on behalf of User A. It is responsible for recognising User A's decision to effect Call Transfer, and for identifying
the two calls.
7.1.2.2 Transfer execute Functional Entity, FE2
This FE checks that details known concerning the primary and secondary calls do not preclude the interconnection of User B
and User C and creates the new connection between User B and User C by joining together the two existing connections.
8 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 14 ----------------------
ISO/IEC 13865:2003(E)
7.1.2.3 Transfer complete receive Functional Entity, FE3
This FE acts on behalf of User B or User C, and notifies the respective FE that a transfer has occurred, along with the details of
the new call. Two FE3s exist, one for User B and one for User C. This FE also passes to the other FE3 details about the
associated user.
7.1.2.4 Transfer notification receive Functional Entity FE4
This FE receives on behalf of User B or User C the indication that a transfer has occurred, and the details of the new call. Two
FE4s exist, one for User B and one for user C. This FE also passes to the other FE4 details relevant to the transfer which are not
provided by the networks.
7.1.3 Relationship of functional model to Basic Call functional model
Functional Entity FE1 shall be collocated with User A's CCAs for the two calls, except where User A's terminal is stimulus with
respect to SS-CT but functional with respect to the basic call, in which case FE1 shall be collocated with User A's CCs for the
two calls.
Functional Entity FE2 shall be collocated with User A's CCs for the two calls.
A functional Entity FE3 shall be collocated with each of User B's and User C's CCs.
A functional Entity FE4 shall be collocated with each of User B's and User C's CCAs, except where either or both of User B's
and User C's terminals are stimulus with respect to SS-CT but functional with respect to the basic call, in which case the FE4 in
question shall be collocated with the user's CC.
An example of a relationship between the FEs for SS-CT and FEs for the basic call is shown in figure 3.
In this example, User A is the called user for the primary call, and the calling user of the secondary call.
User A
CCA FE1
CCA
r1
rr
r1
CC FE2 CC
r2
r2
CC CC
rs rs
r2
r2
rv
FE3
CC FE3 CC
r3
r3
rt rt
ru
FE4
FE4
CCA
CCA
User C
User B
Figure 3 - Example relationship between model for SS-CT and Basic Call
© ISO/IEC 2003 – All rights reserved 9
---------------------- Page: 15 ----------------------
ISO/IEC 13865:2003(E)
7.2 Information flows
7.2.1 Definition of information flows
In the tables listing the elements in information flows, the column headed "Request" indicates which of these elements are
mandatory (M) and which are optional (O) in a request/indication information flow, and the column headed "Confirm"
indicates which of these elements are mandatory (M) and which are optional (O) in a response/confirmation information flow.
7.2.1.1 Transfer Invoke
This is a confirmed information flow across rr from FE1 to FE2 which initiates a transfer. The request contains the identities of
the calls involving users B and C.
Table 1 lists the service elements within the Transfer Invoke information flow.
Table 1 - Content of Transfer Invoke
Service element Request Confirm
Local Call Identities (LCI) M -
Transfer Invoke Result (TIVR) - M
Service element LCI shall contains the identities of the two calls to be transferred.
Service element TIVR contains the result of the transfer invoke request and, if it indicates rejection, identifies the reason for
rejection. An indication of rejection means that the primary and secondary calls have not been affected by the invocation
request. An indication of acceptance means that the
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.