ETSI TS 101 878-2003 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4 Service Capability Definition Service Capabilities for TIPHON Release 4_1.pdf

1、 ETSI TS 101 878 V4.1.1 (2003-11) Technical Specification Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Service Capability Definition; Service Capabilities for TIPHON Release 4 ETSI ETSI TS 101 878 V4.1.1 (2003-11) 2 Reference RTS/TIPHON-01009R4 Keywords IP

2、, service, telephony, VoIP 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 Important notice Individual copies of

3、 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 the Portable Document Format (PDF).

4、 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. Information on the current status of

5、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. The copyright and the foregoing restr

6、iction 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 currently being registered by ETSI for

7、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 878 V4.1.1 (2003-11) 3 Contents Intellectual Property Rights5 Foreword.5 Introduction 5 1 Scope 6 2 References 6 3 Definitions and abbreviati

8、ons.6 3.1 Definitions6 3.2 Abbreviations .7 4 Services and service capabilities 7 5 Naming.7 6 Overall UML class model 7 6.1 Other entities in the TIPHON SC Model9 6.1.1 TIPHON User .9 6.2 Scope of service capabilities with respect to user and network9 7 Bearer class service capabilities.10 7.1 Bear

9、er attribute (data element) definitions .11 7.2 Service capabilities.12 7.2.1 Create12 7.2.2 Modify 12 7.2.3 Delete12 7.2.4 Join12 7.2.5 setCondition12 7.2.6 clearCondition.13 8 Call class service capabilities.13 8.1 Call attribute (data element) definitions .14 8.2 Service capabilities.14 8.2.1 Set

10、up .14 8.2.2 identityDelivery 14 8.2.3 Redirect.15 8.2.4 setPriority15 8.2.5 cleardown15 8.2.6 Join15 8.2.7 Interrogate.15 8.2.8 setCondition15 8.2.9 clearCondition.16 8.2.10 locationDelivery .16 8.2.11 Route.16 9 Profile class service capabilities.17 9.1 Service capabilities.17 9.1.1 Register.17 9.

11、1.2 Attach18 9.1.3 Authenticate18 9.1.4 getStatus18 9.1.5 Deregister18 9.1.6 Transfer.18 9.1.7 Authorize 18 9.1.8 setStatus 19 9.1.9 setCondition19 9.1.10 clearCondition.19 10 Message class service capabilities20 ETSI ETSI TS 101 878 V4.1.1 (2003-11) 4 10.1 Message attributes 21 10.2 Service capabil

12、ities.21 10.2.1 Create21 10.2.2 Retrieve.21 10.2.3 setStatus 21 10.2.4 getStatus21 10.2.5 Delete22 11 Media class service capabilities .22 11.1 Data attributes 22 11.2 Service capabilities.22 11.2.1 setMediaEncode22 11.2.2 clearMediaEncode 23 11.2.3 createTransport .23 11.2.4 clearTransport.23 Annex

13、 A: (informative) Method of developing meta-protocols from service capabilities .24 A.1 Overview 24 A.2 Service capability model 24 A.3 From SC to Meta-protocol .25 Annex B: (informative) Interconnection agreements26 History 27 ETSI ETSI TS 101 878 V4.1.1 (2003-11) 5 Intellectual Property Rights IPR

14、s 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: “Intellectual Property Rights (IPRs); Essential, or po

15、tentially 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 investigation, including IPR searches, has been carrie

16、d 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 Specification (TS) has been produced by ETSI Project Te

17、lecommunications and Internet Protocol Harmonization Over Networks (TIPHON). Introduction The present document uses the Universal Modelling Language (UML) to model the TIPHON Release 4 service capabilities in an object oriented approach. The advantages of such an approach include: the ability to exp

18、ress service capabilities in a semi-formal modelling language; inheritance of the Object Oriented Design paradigm and with it concepts of reuse, inheritance, polymorphism, and extensibility. NOTE: The approach to the definition of service capabilities in TIPHON Release 3 (v1.1.1 of the present docum

19、ent) has been modified in this edition. The approach in v1.1.1 did not specify object-based design methods to develop the service capability model and instead used text to define the service capabilities where those service capabilities were derived from and abstracted from the capabilities and supp

20、lementary services of ISDN. The service capabilities described in the present document exist in the control plane of TIPHON, where this application plane may be vertically apportioned as shown in the figure below: Transport Point to point, Point to multipoint, Multipoint to multipoint Services Telep

21、hone Services Data Services (WWW, e-mail, etc) Video Services (TV, movie, etc) Point to point, Point to multipoint, Multipoint to multipoint Transport plane Application plane NOTE: Some of the application plane services will only be available in TIPHON R5 or later. Figure 0: TIPHON application and t

22、ransport planes ETSI ETSI TS 101 878 V4.1.1 (2003-11) 6 1 Scope The present document specifies those service capabilities sufficient to implement the services in the scope of TIPHON Release 4 defined in ETSI TR 101 301 1 and examples of which are given in ETSI TS 101 315 4. 2 References The followin

23、g documents contain provisions which, 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

24、. For a non-specific reference, the 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 TR 101 301: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON)

25、Release 4; Release Definition“. 2 Void. 3 ETSI TS 101 329-2: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; End-to-end Quality of Service in TIPHON Systems; Part 2: Definition of Speech Quality of Service (QoS) Classes“. 4 ETSI TS 101 315: “Telecommunicatio

26、ns and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Flow and Reference Point Definitions; Guidelines for application of TIPHON functional architecture to inter-domain services“. 5 ITU-T Recommendation E.164: “The international public telecommunication numbering plan“. 6 IETF RFC

27、 2543: “SIP: Session Initiation Protocol“. 7 ITU-T Recommendation H.323: “Packet-based multimedia communications systems“. 8 ETSI TS 101 882 (all parts): “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Protocol Framework Definition“. 9 ITU-T Recommendation Z

28、.120: “Message sequence chart (MSC)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: bearer: logical association of the entities in an IP streamed media application and corresponding transport network which, togeth

29、er, create an appropriate end-to-end media flow for no longer than the duration of a particular call service: set of telecommunication-related tasks performed for a customer by a Service Provider and supplied in a business context user identifier: information that enables an end user or access to be

30、 uniquely known user profile: service specific information about a user of a service application ETSI ETSI TS 101 878 V4.1.1 (2003-11) 7 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: HMSC High-level Message Sequence Chart ICF Inter-Connect Function IS

31、DN Integrated Services Digital Network ITU International Telecommunications Union MSC Message Sequence Chart NGN Next Generation Network SC Service Capability SDL Specification and Description Language SIP Session Initiation Protocol TIPHON Telecommunications and Internet Protocol Harmonization Over

32、 Networks UML Unified Modelling Language 4 Services and service capabilities TIPHON standardizes modules of technical functionality that can be implemented using different technologies and terms these as Service Capabilities. A service application is the technical description which, when combined wi

33、th a commercial arrangement, specifies a service. A service capability is a specified set of functionalities that is used to provide a component part of a service application. A single service capability may be used in more than one service application. A service capability is further defined (for t

34、he purposes of the present document) as an operation within one of these root classes or any derived class. 5 Naming TIPHON Release 4 for the support of Public Telephony shall use naming based on the use of numbering plans derived from the application of ITU-T Recommendation E.164 5. EXCEPTION: Numb

35、ering schemes used in private networks. EXCEPTION: Service invocation codes, e.g. emergency number. 6 Overall UML class model Analysis of the suite of services required in TIPHON Release 4 and any current provision of those services in the ISDN or in the Internet (for SIP 6 and ITU-T Recommendation

36、H.323 7), suggest that the following set of UML classes can be used to define TIPHON. Profile: - The profile class specifies the attributes and operations required to support operations on the user profile or service profile (e.g. registration, authentication). Call: - The call class specifies the a

37、ttributes and operations required for the establishment, modification and clearing of a multi-media connection between two users. ETSI ETSI TS 101 878 V4.1.1 (2003-11) 8 Bearer: - The bearer class specifies the attributes and operations required for control of connection based service domain operati

38、ons. Media: - The media class specifies the attributes and operations required to enable communications payload encoding and characterization. Message: - The message class specifies those attributes and operations required for control of message handling including storage, retrieval and maintenance,

39、 in the service domain. In addition the following object types are defined for TIPHON: Transport: - The transport object is manipulated by the media and bearer classes. Two stereotypes are defined in TIPHON: = Service capability; = Notification or return message. It is noted that the stereotypes are

40、 typically invoked and run asynchronously and many operations may be invoked prior to completion of a single operation. The identified classes are shown in figure 1. Call- call : CallDescriptor- cdr : CallDataRecord + setup() + cleardown() + redirect() + join() + identityDelivery() + setPriority() +

41、 interrogate() + locationDelivery() + setCondition() + clearCondition() + route() + condition_Return() + setup_Return()Bearer- bearer : BearerDescriptor + optimise() + create() + delete() + modify() + join() + setCondition() + clearCondition() + condition_Return() + create_Return()Profile- profile :

42、 RegistrationProfile + register() + attach() + deregister() + detac h() + authenticate() + authorise() + transfer() + setSt atus () + getStatus() + setCondition() + clearCondition() + register_Return() + attac h_Return() + status_Return() + transfer_Return() + condition_Return() + authorise_Return()

43、Mess age + create() + retrieve() + delete() + setStatus() + getStatus() + message_Report() + message_Response() + message_Return() + message_Status()Media- media : MediaDescriptor- transport : Transport + clearMediaEncode() + createTransport() + clearTransport() + setMediaEncode() + setMedia_Return(

44、) + createTransport_Return()Figure 1: Overall UML class model for TIPHON (NGN) Service Capabilities ETSI ETSI TS 101 878 V4.1.1 (2003-11) 9 6.1 Other entities in the TIPHON SC Model 6.1.1 TIPHON User The TIPHON user is that entity, generally outside of the TIPHON model and whose state is not recorde

45、d in the model, that initializes and terminates transactions such as telephone calls. NOTE: Although there are signals required to be sent to the user these do not form capabilities as defined in other parts of the present document. Therefore other than recognizing the existence of the TIPHON user a

46、s an element in the system that uses service capabilities no specification of the TIPHON user is given. A stereotype may be required to allow notification of the user of the state of operations in the other parts of the service capability model. 6.2 Scope of service capabilities with respect to user

47、 and network The figures that follow show, for a network connection between two users, the scope of each of the classes defined in the present document. call bearer transport ICF ICF ICF media NOTE 1: Call is defined end-to-end. NOTE 2: Bearer is the abstraction of all transport and media encoding s

48、een by the call. NOTE 3: Media objects are carried nominally end-to-end but a single call may have many media objects serially concatenated across transcoding points. NOTE 4: Transport objects exist within a single transport domain between terminal points (either user-terminals or Inter-Connect Func

49、tions (ICFs). Figure 2: Scope of classes with respect to operations ETSI ETSI TS 101 878 V4.1.1 (2003-11) 10Call IP Network ATM Network User A User B Media Media Media IP Addressing QoS signaling audio ATM Addressing QoS signaling audio Bearer Audio stream (with properties) Figure 3: Scope of classes with respect to operations, alternative view 7 Bearer class service capabilities The bearer service capability suite contains those capabilities required to manage a transport plane connection, or set of transport plane conne