BS ISO/IEC 13865:1995
Withdrawn
A Withdrawn Standard is one, which is removed from sale, and its unique number can no longer be used. The Standard can be withdrawn and not replaced, or it can be withdrawn and replaced by a Standard with a different number.
Information technology. Telecommunications and information exchange between systems. Private Integrated Services Network. Specification, functional model and information flows. Call transfer supplementary service
Hardcopy , PDF
01-12-2003
English
15-03-1996
Foreword
Introduction
1 Scope
2 Conformance
3 Normative References
4 Definitions
4.1 External definitions
4.2 Other definitions
5 List of Acronyms
6 SS-CT stage 1 specification
6.1 Description
6.1.1 General description
6.1.2 Qualifications on applicability to
telecommunications services
6.2 Procedures
6.2.1 Provision/withdrawal
6.2.2 Normal procedures
6.2.2.1 Activation/deactivation/registration/
interrogation
6.2.2.2 Invocation and operation
6.2.3 Exceptional procedures
6.2.3.1 Activation/deactivation,registration/
interrogation
6.2.3.2 Invocation and operation
6.3 Interactions with other supplementary services
and ANFs
6.3.1 Calling Line Identification Presentation (SS-CLIP)
6.3.2 Connected Line Identification Presentation
(SS-COLP)
6.3.3 Calling/Connected Line Identification
Restriction (SS-CLIR)
6.3.4 Calling Name identification Presentation
(SS-CNIP)
6.3.5 Connected Name Identification Presentation
(SS-CONP)
6.3.6 Calling/Connected Name Identification
Restriction (SS-CNIR)
6.3.7 Completion of Calls to Busy Subscribers (SS-CCBS)
6.3.8 completion of Calls on No Reply (SS-CCNR)
6.3.9 Call Forwarding Services
6.3.10 Path Replacement (ANF-PR)
6.4 Interworking considerations
6.4.1 User B and/or User C in another network
6.4.2 User A in another network
6.5 Overall SDL
7 SS-CT stage 2 specification for transfer by join
7.1 Functional model
7.1.1 Functional model description
7.1.2.1 Transfer invoke functional entity, FE1
7.1.2.2 Transfer execute functional entity, FE2
7.1.2.3 Transfer complete receive functional entity, FE3
7.1.2.4 Transfer notification receive functional
entity FE4
7.1.3 Relationship of functional model to Basic Call
functionary model
7.2 Informative flows
7.2.1 Definition of information flows
7.2.1.1 Transfer Invoke
7.2.1.2 Transfer Complete
7.2.1.3 Transfer Active
7.2.1.4 Transfer Notify
7.2.1.5 Terminal Details
7.2.1.6 Transfer Update
7.2.2 Relationship of information flows to basic
call information flows
7.2.3 Examples of information flow sequences
7.2.3.1 Successful Call Transfer (both calls answered)
7.2.3.2 Successful Call Transfer (User C alerting)
7.3 Functional entity actions
7.3.1 Functional entity actions of FE1
7.3.2 Functional entity actions of FE2
7.3.3 Functional entity actions of FE3
7.3.4 Functional entity actions of FE4
7.4 Functional entity behaviour
7.4.1 Behaviour of FE1
7.4.2 Behaviour of FE2
7.4.3 Behaviour of FE3
7.4.4 Behaviour of FE4
7.5 Allocation of functional entities to physical
locations
7.6 Interworking considerations
8 SS-CT stage 2 specification for transfer by
re routeing
8.1 Functional model
8.1.1 Functional model description
8.1.2 Description of functional entities
8.1.2.1 Transfer Invoke Functional Entity FE1
8.1.2.2 Transfer Notification Receive Functional
Entity, FE4
8.1.2.3 Transfer Co-ordinate Functional Entity FE4
8.1.2.4 Transfer Associate Functional Entity FE6
8.1.2.5 Transfer Execute Functional Entity, FE7
8.1.3 Relationship of Functional Model to Basic Call
Functional Model
8.2 Information flows
8.2.1 Definition of information flows
8.2.1.1 Transfer Invoke
8.2.1.2 Transfer Identity
8.2.1.3 Transfer Abandon
8.2.1.4 Transfer Initiate
8.2.1.5 Transfer Setup
8.2.1.6 Transfer Notify
8.2.1.7 Terminal Details
8.2.2 Relationship of information flows to basic call
information flows
8.2.3 Examples of information flow sequences
8.2.3.1 Successful Call Transfer (answered)
8.2.3.2 Successful Call Transfer (alerting)
8.2.3.3 Unsuccessful Call Transfer (setup fails)
8.3 Functional Entity actions
8.3.1 Functional Entity actions of FE1
8.3.2 Functional Entity actions of FE5
8.3.3 Functional Entity actions of FE6
8.3.4 Functional Entity actions of FE7
8.3.5 Functional Entity actions of FE4
8.4 Functional Entity behaviour
8.4.1 Behaviour of FE5
8.4.2 Behaviour of FE6
8.4.3 Behaviour of FE7
8.5 Allocation of Functional Entities to Physical
Locations
Annex A
Specifies Supplementary Service Call Transfer (SS-CT), which applies to various basic services supported by Private Integrated Services Networks (PISNs). Contains two stage 2 specifications reflecting different ways of operating the service within the network: transfer by join and transfer by rerouteing.
Committee |
IST/6
|
DocumentType |
Standard
|
Pages |
46
|
PublisherName |
British Standards Institution
|
Status |
Withdrawn
|
Supersedes |
Standards | Relationship |
ISO/IEC 13865:2003 | Identical |
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 |
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 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 |
Access your standards online with a subscription
Features
-
Simple online access to standards, technical information and regulations.
-
Critical updates of standards and customisable alerts and notifications.
-
Multi-user online standards collection: secure, flexible and cost effective.