1、 ETSI TS 101 882-3 V4.1.1 (2003-11)Technical Specification Telecommunications and Internet ProtocolHarmonization Over Networks (TIPHON) Release 4;Protocol Framework Definition;Part 3: TIPHON Simple Call service meta-protocol definitionfloppy3 ETSI ETSI TS 101 882-3 V4.1.1 (2003-11) 2 Reference RTS/T
2、IPHON-03016-3R4 Keywords interface, IP, meta-protocol, protocol, 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 enregistre la Sous-Prfecture de Grasse (06) N
3、 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
4、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
5、 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: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written per
6、mission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade
7、 Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 101 882-3 V4.1.1 (2003-11) 3 Contents Intellectual Property Rights6 Foreword.6 1 Scope 7 2 Referenc
8、es 7 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .8 4 TIPHON simple call service.8 4.1 Description .8 4.2 Procedures 8 4.2.1 Provision/withdrawal8 4.2.2 Normal procedures8 4.2.2.1 Activation/deactivation .8 4.2.2.2 Invocation and operation.8 4.2.3 Exceptional procedures.8 4.
9、3 Interaction with other services or service capabilities9 4.3.1 Call class service capabilities9 4.3.1.1 Redirect .9 4.3.1.2 SetPriority .9 4.3.1.3 Join9 4.3.1.4 Interrogate .9 4.3.1.5 SetCondition9 4.3.1.6 ClearCondition9 4.3.1.7 Park .9 4.3.1.8 Retrieve .9 4.3.1.9 LocationDelivery 9 4.3.2 Bearer
10、class service capabilities10 4.3.2.1 Join10 4.3.2.2 Modify.10 4.3.2.3 SetCondition10 4.3.2.4 ClearCondition10 4.3.3 Profile class service capabilities .10 4.3.3.1 Register .10 4.3.3.2 Attach10 4.3.3.3 Deregister10 4.3.3.4 Detach .10 4.3.3.5 Authenticate 10 4.3.3.6 Authorize.10 4.3.3.7 Transfer .10 4
11、.3.3.8 SetStatus10 4.3.3.9 SetCondition11 4.3.3.10 ClearCondition11 4.4 Service capabilities used in service definition11 4.5 Overall behaviour.11 5 Functional entity model and information flows .12 5.1 Functional entity model12 5.1.1 Description of model 12 5.1.2 Description of functional entities1
12、4 5.1.2.1 Calling User 14 5.1.2.2 Calling Users service agent, CFE1OTC.14 5.1.2.3 The policy control function associated with the calling users service provider, CFE2PE14 5.1.2.4 Originating network call coordination function, CFE3ONC.14 ETSI ETSI TS 101 882-3 V4.1.1 (2003-11) 4 5.1.2.5 Originating
13、network routing function, CFE4OR.15 5.1.2.6 Originating network media coordination function, CFE5ONM15 5.1.2.7 Intervening network call coordination function, CFE6INC15 5.1.2.8 Intervening network routing function, CFE7IR15 5.1.2.9 Intervening network media coordination function, CFE8INM.15 5.1.2.10
14、 Destination network call coordination function, CFE9TNC.15 5.1.2.11 Destination network media coordination function, CFE10TNM15 5.1.2.12 Called users service agent, CFE11TTC15 5.1.2.13 Called User15 5.2 Information flows.15 5.2.1 Definition of information flows15 5.2.1.1 Relationship ra 15 5.2.1.1.
15、1 TCC_OrigCallSetup 16 5.2.1.1.2 TCC_CallRelease 16 5.2.1.1.3 TCC_CallAlerting .17 5.2.1.2 Relationship rb 17 5.2.1.2.1 ServingNWPolicy17 5.2.1.3 Relationship rc 18 5.2.1.3.1 CallSetup .18 5.2.1.3.2 CallRelease18 5.2.1.3.3 CallAlerting.19 5.2.1.4 Relationship rd, rg.19 5.2.1.4.1 CallRoute.19 5.2.1.5
16、 Relationship re, rh, rj.20 5.2.1.5.1 MediaReservation20 5.2.1.5.2 MediaEstablishment 21 5.2.1.5.3 MediaRelease 22 5.2.1.6 Relationship rf, ri 22 5.2.1.6.1 NwCallSetup .22 5.2.1.6.2 NwCallRelease 23 5.2.1.6.3 NwCallAlerting .24 5.2.1.7 Relationship rk 24 5.2.1.7.1 DestCallSetup24 5.2.1.7.2 CallRelea
17、se24 5.2.1.8 Relationship rl.25 5.2.1.8.1 TCC_DestCallSetup 25 5.2.1.8.2 TCC_CallRelease 25 5.2.2 Timers.26 5.2.3 Information flow sequences26 5.2.3.1 Normal operation 26 5.2.3.1.1 Call set-up26 5.2.3.1.2 Call clear-down .29 5.2.3.2 Exceptional behaviour.30 5.3 Simple call functional entity actions
18、37 5.3.1 Actions of CFE1OTC.37 5.3.2 Actions of CFE2PE.38 5.3.3 Actions of CFE3ONC.38 5.3.4 Actions of CFE4OR39 5.3.5 Actions of CFE5ONM39 5.3.6 Actions of CFE6INC39 5.3.7 Actions of CFE7IR.40 5.3.8 Actions of CFE8INM40 5.3.9 Actions of CFE9TNC.41 5.3.10 Actions of CFE10TNM41 5.3.11 Actions of CFE11
19、TTC42 5.4 Functional entity behaviour42 ETSI ETSI TS 101 882-3 V4.1.1 (2003-11) 5 5.4.1 Behaviour of CFE1OTC.43 5.4.2 Behaviour of CFE2PE48 5.4.3 Behaviour of CFE3ONC.49 5.4.4 Behaviour of CFE4ORand CFE7IR.59 5.4.5 Behaviour of CFE5ONM, CFE8INM, and CFE10TNM60 5.4.6 Behaviour of CFE6INC65 5.4.7 Beha
20、viour of CFE9TNC.75 5.4.8 Behaviour of CFE11TTC83 5.5 Allocation of functional entities to domains.87 Annex A (normative): Complete SDL model88 Annex B (normative): ASN.1 definitions and default values 89 B.1 ASN.1 information flows definition.89 B.2 ASN.1 Default values.95 History 99 ETSI ETSI TS 1
21、01 882-3 V4.1.1 (2003-11) 6 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
22、 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 Polic
23、y, 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 Techn
24、ical Specification (TS) has been produced by ETSI Project Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON). The present document is part 3 of a multi-part deliverable. Full details of the entire series can be found in TS 101 882-1 1. ETSI ETSI TS 101 882-3 V4.1.1 (2003-1
25、1) 7 1 Scope The present document defines the stage 1 and stage 2 requirements (as defined by ITU-T Recommendation I.130 4) for the simple call service required by TIPHON. The simple call service defined, refers to a single media call only. 2 References The following documents contain provisions whi
26、ch, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, th
27、e latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI TS 101 882-1: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Protocol Framework De
28、finition; Part 1: Meta-protocol design rules, development method, and mapping guideline“. 2 ETSI TR 101 877: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); Requirements Definition Study; Scope and Requirements for a Simple call“. 3 ETSI TS 101 878: “Telecommunication
29、s and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Service Capability Definition; Service Capabilities for TIPHON Release 4“. 4 ITU-T Recommendation I.130: “Method for the characterization of telecommunications services supported by an ISDN and network capabilities of an ISDN“.
30、5 ITU-T Recommendation Z.100 (1996): “Specification and description language (SDL) with corrigendum 1“. 6 ITU-T Recommendation X.680: “Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation“. 7 ETSI TS 101 882-4: “Telecommunications and Internet Protocol Harmo
31、nization Over Networks (TIPHON) Release 4; Protocol Framework Definition; part 4: Media control meta protocol“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the definitions given in TR 101 877 2, TS 101 878 3 and the following apply: TIPHON system: collec
32、tion of inter-working communication networks in which there exists at least one TIPHON gateway connecting two of the networks together ETSI ETSI TS 101 882-3 V4.1.1 (2003-11) 8 user: entity that uses telecommunication services offered by a TIPHON system 3.2 Abbreviations For the purposes of the pres
33、ent document, the abbreviations given in TR 101 877 2, TS 101 878 3 and the following apply: CFE simple Call Functional Entity FE Functional Entity QoS Quality of Service SDL Specification and Description Language SpoA Service point of Attachment 4 TIPHON simple call service 4.1 Description A TIPHON
34、 simple call is the means by which a temporary logical association is established (and subsequently cleared) between two or more users within a TIPHON system for the purpose of conveying information. The meta-protocol carries sufficient information to allow a bearer to be established if required. 4.
35、2 Procedures 4.2.1 Provision/withdrawal TIPHON Simple Call is available on a per-name basis to all subscribers to a TIPHON system. 4.2.2 Normal procedures 4.2.2.1 Activation/deactivation TIPHON simple call shall be permanently activated. 4.2.2.2 Invocation and operation TIPHON simple call shall be i
36、nvoked by the calling user (party A) requesting a connection of defined parameters to a second party (party B). Party A may indicate a preferred carrier of the connection at invocation. Party A may indicate its own name at invocation to allow the called party to identify the calling party. Either pa
37、rty to the TIPHON simple call or the serving network shall be able to remove the temporary logical association formed on invocation of the service. During call set-up transcoding between different codecs may be performed. 4.2.3 Exceptional procedures If the network cannot complete the connection to
38、party B then party A shall be notified. If any of the following failure conditions are detected within a domain, the association shall be removed in each domain involved and any associated resource released. The domain that detects the failure shall supply a reason for failure to each other domain.
39、Failure conditions: No route found to called party; ETSI ETSI TS 101 882-3 V4.1.1 (2003-11) 9 Requested policy not supported; Required transport resources not available; Reserved media and transport resources released due to time out; No compatible codec supported by called party; Called user busy (
40、number of simultaneous calls exceeded); Call release before call set-up completed. 4.3 Interaction with other services or service capabilities The following list of service capability interactions include only the service capabilities which are not used for the definition of the simple call service.
41、 4.3.1 Call class service capabilities 4.3.1.1 Redirect No interaction. 4.3.1.2 SetPriority No interaction. 4.3.1.3 Join No interaction. 4.3.1.4 Interrogate No interaction. 4.3.1.5 SetCondition No interaction. 4.3.1.6 ClearCondition No interaction. 4.3.1.7 Park No interaction. 4.3.1.8 Retrieve No in
42、teraction. 4.3.1.9 LocationDelivery No interaction. ETSI ETSI TS 101 882-3 V4.1.1 (2003-11) 104.3.2 Bearer class service capabilities 4.3.2.1 Join No interaction. 4.3.2.2 Modify No interaction. 4.3.2.3 SetCondition No interaction. 4.3.2.4 ClearCondition No interaction. 4.3.3 Profile class service ca
43、pabilities 4.3.3.1 Register No interaction. NOTE: The QOS to be used for subsequent calls by the registered user may form part of the information supplied at registration. 4.3.3.2 Attach No interaction. 4.3.3.3 Deregister No interaction. 4.3.3.4 Detach No interaction. 4.3.3.5 Authenticate No interac
44、tion. 4.3.3.6 Authorize No interaction. 4.3.3.7 Transfer No interaction. 4.3.3.8 SetStatus No interaction. ETSI ETSI TS 101 882-3 V4.1.1 (2003-11) 114.3.3.9 SetCondition No interaction. 4.3.3.10 ClearCondition No interaction. 4.4 Service capabilities used in service definition Although not explicitl
45、y identified, aspects of the following service capabilities are used in definition of the simple call service: Call class service capabilities: Setup; IdentityDelivery; Cleardown; Route. Bearer class service capabilities: Create; Delete. Profile class service capabilities: GetStatus. The TIPHON Rele
46、ase 4 service capabilities are defined in TS 101 878 3. 4.5 Overall behaviour The UML activity diagram in figure 1 shows the dynamic simple call signalling for a TIPHON system providing simple call service. ETSI ETSI TS 101 882-3 V4.1.1 (2003-11) 12ActivatedRequest callestablishmentCall establishmen
47、trequestCall establishedActivatedCall setupresponseCall setupfailedCall releaserequestReject CallEstablishmentFigure 1: Overall behaviour of simple call service signalling NOTE: The service behaviour model in figure 1 defines global states of the simple call service, hence the same state names are n
48、ot re-used in the behaviour descriptions of the individual functional entities. 5 Functional entity model and information flows 5.1 Functional entity model 5.1.1 Description of model This functional entity model covers the signalling aspects of call control with call routing but does not include the
49、 flow of data in the media path. The functional entity model uses the following Call Functional Entities (CFE): Calling User The application at the calling users terminal which instigates the service request; CFE1OTCThe originating user service agent in the calling users terminal that instigates the service request and processes call and bearer functions (see note 3); CFE2PEThe serving network policy control function associated with the calling users service provider; CFE3ONCThe originating call and bea
