1、 ETSI TS 101 882-1 V4.1.1 (2003-09)Technical Specification Telecommunications and Internet ProtocolHarmonization Over Networks (TIPHON) Release 4;Protocol Framework Definition;Part 1: Meta-protocol design rules,development method, and mapping guidelineETSI ETSI TS 101 882-1 V4.1.1 (2003-09) 2 Refere
2、nce RTS/TIPHON-03016-1R4 Keywords interface, IP, meta-protocol 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 7803/88 I
3、mportant 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
4、 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. I
5、nformation 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 permission. T
6、he 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 Marks cur
7、rently 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-1 V4.1.1 (2003-09) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 3 Def
8、initions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .7 4 What is the meta-protocol?.7 4.1 Introduction 7 4.2 Content of the requirements section .7 4.2.1 Definition7 4.2.2 Description7 4.2.3 Procedures.7 4.2.3.1 Provision/withdrawal 8 4.2.3.2 Normal procedures8 4.2.3.2.1 Activation/deact
9、ivation/registration 8 4.2.3.2.2 Invocation and operation .8 4.2.3.2.3 Interrogation/editing8 4.2.3.3 Exceptional procedures .8 4.2.4 Interaction with other services and service capabilities 9 4.2.5 Content of the dynamic definition 9 4.3 Content of the behavioural section .9 4.3.1 Derivation of a f
10、unctional model 9 4.3.2 Information flow diagrams .9 4.3.3 SDL/UML diagrams for functional entities 9 4.3.4 Functional Entity Actions .9 5 Method of mapping to the meta-protocol.10 5.1 Introduction 10 5.2 Pre-analysis of the candidate10 5.2.1 Identify Protocol Entities (PE) of candidate .10 5.2.2 Id
11、entify Protocol Data Units of candidate.10 5.3 Mapping of PE to FE10 5.3.1 Allocation of functional entities to protocol entities.10 Annex A (informative): Example 11 A.1 Description .11 A.1.1 General description.11 A.1.2 Procedures 11 A.1.2.1 Provision and withdrawal .11 A.1.2.2 Normal procedures11
12、 A.1.2.2.1 Activation, deactivation and interrogation 11 A.1.2.2.2 Invocation and operation.12 A.1.2.3 Exceptional procedures.12 A.1.2.3.1 Invocation and operation.12 A.1.3 Interactions with other TIPHON service capabilities.12 A.1.3.1 Registration service capabilities .12 A.1.3.1.1 Terminal transpo
13、rt service registration12 A.1.3.1.2 User service registration12 A.1.3.2 Call connectivity service capabilities12 A.1.3.2.1 Simple call establishment12 A.1.3.2.2 Calling user identity generation 13 A.1.4 Interworking considerations .13 A.1.5 Overall behaviour.13 ETSI ETSI TS 101 882-1 V4.1.1 (2003-09
14、) 4 A.2 Functional entity model and information flows .15 A.2.1 Functional entity model15 A.2.1.1 Description of model 15 A.2.1.2 Description of functional entities16 A.2.1.2.1 Calling user .16 A.2.1.2.2 Calling users service agent, QFE116 A.2.2 Information flows.16 A.2.2.1 Definition of information
15、 flows16 A.2.2.1.1 Relationship ra 16 A.2.2.1.1.1 OrigQoSEstab16 A.2.2.1.2 Relationships rb, rc, rd and re .17 A.2.2.1.2.1 QoSEstab.17 A.2.2.2 Information flow sequences17 A.2.2.2.1 Normal operation 17 A.2.3 QoS Functional entity actions 18 A.2.3.1 Actions of QFE1 .19 A.2.3.2 Actions of QFE2 .19 A.2
16、.4 QoS Functional Entity behaviour .19 A.2.4.1 Behaviour of QFE1.19 Annex B (informative): Messaging capability meta-protocol.23 B.1 Derivation from service capability.23 B.2 SDL model .24 B.3 ASN.1 data definitions .34 Annex C (informative): Bibliography.36 History 37 ETSI ETSI TS 101 882-1 V4.1.1
17、(2003-09) 5 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: “Intellect
18、ual 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 investigat
19、ion, 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 Specificati
20、on (TS) has been produced by ETSI Project Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON). The present document is part 1 of a multi-part deliverable covering the TIPHON meta-protocol, as identified below: Part 1: Meta-protocol design rules, development method, and mapp
21、ing guideline; Part 2: Registration and Service Attachment service meta-protocol definition; Part 3: TIPHON Simple Call; Part 4: Media control and meta-protocol; Part 5: Transport control service meta-protocol definition. ETSI ETSI TS 101 882-1 V4.1.1 (2003-09) 6 1 Scope The present document defines
22、 by means of an information model, a functional entity behavioural model, and by validated SDL a model of the abstract behaviour of each service and service capability identified as being essential in TIPHON R4. The present document defines the method of defining a meta-protocol using a worked examp
23、le for clarification. In addition the present document defines the approach to be used to identify the mapping of any candidate protocol to the meta-protocol. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
24、 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, the latest version applies. Referenced documents which are not found to be publicly
25、available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI TS 101 314: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Abstract Architecture Network Architecture and Reference Points“. 2 Void. 3 ETSI TR 101 877: “Telecommuni
26、cations and Internet Protocol Harmonization Over Networks (TIPHON); Requirements Definition Study; Scope and Requirements for a Simple call“. 4 ETSI TS 101 878 V4.1.1: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Service Capability Definition; Service Cap
27、abilities for a simple call“. 5 Void. 6 ETSI TS 102 024-2: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; End-to-end Quality of Service in TIPHON Systems; Part 2: Definition of Speech Quality of Service (QoS) Classes“. 7 ITU-T Recommendation Z.100: “Specifi
28、cation and Description Language (SDL)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 101 877 3 and TS 101 878 4 apply. ETSI ETSI TS 101 882-1 V4.1.1 (2003-09) 7 3.2 Abbreviations For the purposes of the present docume
29、nt, the abbreviations defined in TR 101 877 3 and TS 101 878 4 and the following apply: FEA Functional Entities Actions OMG Object Management Group PDU Protocol Data Units PE Protocol Entities QFE Qos Functional Entities SCN Switched Circuit Network SDL Specification and Description Language UML Uni
30、fied Modelling Language 4 What is the meta-protocol? 4.1 Introduction The meta-protocol serves as the platform for candidate protocols to map to and in which the mapping identifies exactly how the requirements are met. The description of the meta-protocol consists of 2 parts: requirements of the ser
31、vice or service capability; and functional behaviour of the service or service capability. 4.2 Content of the requirements section The requirements section of the meta-protocol for any service (or service capability) is an overall description from the users standpoint and consists of a definition an
32、d description of the service (or service capability) in prose, followed by an overall summary of the dynamic behaviour in either an SDL process diagram, or an UML activity diagram. 4.2.1 Definition This clause provides a short description of the service (or service capability) in terms of the percep
33、tions of the user receiving the service (or service capability) and any other users involved in the service (or service capability). 4.2.2 Description This clause expands on the definition and summarizes the operation of the service (or service capability) in a generic form which does not constrain
34、terminal or network design. It is intended to allow an understanding of the service (or service capability) without regard to implementation. It also includes any specific terminology used within the prose definition and description, and any qualifications. For basic services this clause details the
35、 applications which could utilize the service whilst for supplementary services this clause details their applicability to particular telecommunication services. 4.2.3 Procedures The overall operation of the service (or service capability) in its various states is described in this clause. These pro
36、cedures relate to all actions between the user(s) and the network during the period that the service (or service capability) is available. ETSI ETSI TS 101 882-1 V4.1.1 (2003-09) 8 4.2.3.1 Provision/withdrawal This clause describes the means by which the service (or service capability) is made avail
37、able by the service provider, e.g. it may be generally available to all customers, or only be available to those customers who have made a prior arrangement. 4.2.3.2 Normal procedures The clauses under this heading describe the normal procedures for activation, deactivation, registration, invocation
38、 and operation for the service (or service capability) as appropriate. This clause describes only the successful outcome of each procedure, and the procedures which are executed as a result of such successful outcomes. The procedures are described in a time-based sequence of events. They describe th
39、e interactions of the users involved in the service (or service capability) with the service provider and with each other which lead to, and are elements of, the successful operation of the service (or service capability). 4.2.3.2.1 Activation/deactivation/registration The procedures for activation,
40、 which is the operation of bringing the service into the “ready for invocation“ state, and deactivation, which is the complementary action, are described in this clause. For some services (or service capability) there may be a specific user procedure to allow activation and deactivation as necessary
41、, whilst for others the service (or service capability) is permanently activated on provision and thus no procedure is provided. Registration describes the procedures by which any specific information, necessary for the successful operation of the supplementary service, is given to the network. The
42、need to register information with the network, e.g. a forwarding number, only applies to certain services (or service capabilities). 4.2.3.2.2 Invocation and operation This clause describes the procedures for invocation, which is the action and conditions under which the service (or service capabili
43、ty) is brought into operation; in the case of some services (or service capabilities) this may only be on a particular call. It should be noted that although a service (or service capability) may be activated, it may not necessarily be invoked on all calls. (Invocation may take place either subseque
44、nt to or simultaneously with activation.) In the case of basic services this clause shall describe the events, perceived at the service access point, during the establishment, information transfer and clearing phases. Operation is the procedure which occurs once a service (or service capability) has
45、 been invoked. This description gives details of the significant actions of the network, treated in principle as a single entity, and the perception of the users involved in the service (or service capability). It includes details of the information exchanged between the network and relevant users a
46、nd the indications given to each user, by the network, concerning the states of the service (or service capability). 4.2.3.2.3 Interrogation/editing Interrogation is the facility which enables a served user to determine, from the service provider, the current status of a particular service. Whether
47、this facility is provided for the service (or service capability) being described, and if so, the procedures that accompany it, are detailed in this clause. 4.2.3.3 Exceptional procedures The clauses under this heading describe the exceptional procedures which result in an unsuccessful outcome of th
48、e service (or service capability). Included within this description are the details for such situations as invalid user action and the handling of certain network and interface conditions. For the case of basic services this includes the handling of such network conditions as congestion. ETSI ETSI T
49、S 101 882-1 V4.1.1 (2003-09) 9 4.2.4 Interaction with other services and service capabilities This clause shall describe all interactions of the service or service capability with other services or service capabilities insofar as they have been identified. For example, for some service or service capability pairs there is no interaction as the two are not permitted to be both in operation at the same time. For other pairs, one or both services (or service capabilities) may be modified whilst the pair are in operation simultaneously. 4.2.5 Conte
