ETSI TR 101 882-2004 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 5 Protocol Framework Definition and Interface Requirement Definition Gene_1.pdf

1、 ETSI TR 101 882 V5.1.1 (2004-05) Technical Report Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 5; Protocol Framework Definition and Interface Requirement Definition; General floppy3 ETSI ETSI TR 101 882 V5.1.1 (2004-05) 2 Reference RTR/TISPAN-02014-TIPHON_R5

2、 Keywords Interface, IP, 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 Important notice Individual co

3、pies 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 the Portable Document Format

4、 (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. Information on the current sta

5、tus 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. The copyright and the foregoin

6、g restriction extend to reproduction in all media. European Telecommunications Standards Institute 2004. 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 ET

7、SI 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 TR 101 882 V5.1.1 (2004-05) 3 Contents Intellectual Property Rights5 Foreword.5 Introduction 5 1 Scope 6 2 References 6 3 Definitions and abb

8、reviations.6 3.1 Definitions6 3.2 Abbreviations .6 4 Profile group.7 4.1 Introduction 7 4.2 Data model .9 4.3 Profile group service capabilities .10 4.3.1 Register.10 4.3.2 Attach11 4.3.3 Authenticate11 4.3.4 Get user status.15 4.3.5 Deregister15 4.3.6 Transfer.15 4.3.7 Authorize 15 4.3.8 Set user s

9、tatus .15 4.3.9 Interrogate location.17 4.3.10 Update location.18 4.3.11 Update service status 19 4.3.12 Add service to profile .20 4.3.13 Remove service from profile 21 4.3.14 Get service status 22 4.3.15 Get service descriptor .23 4.4 Typical architecture24 5 Call group.25 5.1 Introduction 25 5.2

10、Call group.25 5.3 Data definitions 28 5.4 Call group service capabilities30 5.4.1 Originating domain call group service capabilities.30 5.4.1.1 Call setup 31 5.4.1.2 Call identity delivery.33 5.4.1.3 Call redirect.34 5.4.1.4 Modify call priority.35 5.4.1.5 Call cleardown 36 5.4.1.6 Call join.37 5.4.

11、1.7 Interrogate call 38 5.4.1.8 Operation signatures39 5.4.2 Intermediate domain call group service capabilities.41 5.4.2.1 Call setup 42 5.4.2.2 Call identity delivery.44 5.4.2.3 Call redirect.45 5.4.2.4 Modify call priority.46 5.4.2.5 Call cleardown 47 5.4.2.6 Call join.48 5.4.2.7 Interrogate call

12、 49 5.4.2.8 Operation signatures50 5.4.3 Destination domain call group service capabilities.51 5.4.3.1 Call setup 52 ETSI ETSI TR 101 882 V5.1.1 (2004-05) 4 5.4.3.2 Call identity delivery.54 5.4.3.3 Call redirect.55 5.4.3.4 Modify call priority.56 5.4.3.5 Call cleardown 57 5.4.3.6 Call join.58 5.4.3

13、.7 Interrogate call 59 5.4.3.8 Operation signatures60 5.5 Typical architecture62 6 Bearer group.62 6.1 Introduction 62 6.2 Data model .63 6.3 Bearer group service capabilities70 6.3.1 Create73 6.3.1.1 Reserve Bearer 73 6.3.1.2 Allocate Bearer .74 6.3.2 Modify Bearer.75 6.3.3 Delete Bearer 77 6.3.4 O

14、peration interfaces .78 6.4 Typical architecture79 7 Media group .79 7.1 Introduction 79 7.2 Data model .80 7.3 Media group service capabilities 83 7.3.1 Set media encode 85 7.3.2 Clear media encode.86 7.3.3 Operation interfaces87 7.4 Typical architecture88 8 Message group88 8.1 Introduction 88 8.2

15、Data model .89 8.3 Message group service capabilities 91 8.3.1 Create message .93 8.3.2 Retrieve message 94 8.3.3 Set message status.95 8.3.4 Get message status97 8.3.5 Delete message .99 8.4 Typical architecture101 9 Event handler group .101 9.1 Introduction 101 9.2 Event handler group .102 9.3 Dat

16、a definitions 103 9.4 Service capability models.104 9.4.1 Set condition .105 9.4.2 Clear condition106 9.4.3 Operation signatures .107 9.5 Typical architecture108 Annex A: Derived services and capabilities.109 A.1 Derived capabilities from Profile group.109 A.1.1 Register 109 A.1.2 Deregister .109 A.

17、1.3 Attach .109 A.1.4 Detach 109 A.2 Derived capabilities from call group 110 A.2.1 Call join110 Annex B: UML model source files111 History 112 ETSI ETSI TR 101 882 V5.1.1 (2004-05) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared

18、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 potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is a

19、vailable 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 carried out by ETSI. No guarantee can be given as to the existence of other IPRs not refer

20、enced 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 Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Net

21、working (TISPAN). Introduction This version of the document differs from earlier versions in the following areas: The document status is changed from Technical Specification to Technical Report. It is presented as a single part document with one clause describing the behaviour of each group of servi

22、ce capabilities. The definition language is UML as opposed to SDL. Data is defined in UML terms and not using ASN.1 (the data can be translated to ASN.1 or any other format as appropriate). In this version of the document each group of service capabilities identified in TR 101 878 1 is presented as

23、follows: static data model; service capabilities as UML operations within the class and identification of active interfaces to the class; state-chart diagrams of the operation of each service capability identifying signals that invoke the operation and the data each operation affects. NOTE: Some ser

24、vice capabilities defined in TR 101 878 1 have been identified to be services rather than service capabilities, i.e. they can be built from combination of the specified service capabilities. In Annex A it is defined for each of these services how they can be built from the specified service capabili

25、ties. ETSI ETSI TR 101 882 V5.1.1 (2004-05) 6 1 Scope The present document specifies behavioural models in UML for each of the service capabilities defined in TR 101 878 1. The requirements expressed in the present document applies to all TIPHON compliant products. 2 References For the purposes of t

26、his Technical Report (TR), the following references apply: 1 ETSI TR 101 878: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 5; Service Capability Definition; Service Capabilities for a Multi Media Call“. 3 Definitions and abbreviations 3.1 Definitions For the

27、 purposes of the present document, the following terms and definitions apply: service capability: specified function that is used either alone or in combination with other service capabilities to realize a complete service application NOTE: A single service capability may be used in more than one se

28、rvice application. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation 1 NNI Network Network Interface QoS Quality of Service SDL Specification and Description Language UML Unified Modelling Language UNI User Network Interface

29、 ETSI ETSI TR 101 882 V5.1.1 (2004-05) 7 4 Profile group 4.1 Introduction The profile group of service capabilities is defined in TR 101 878 1 and contains the service capabilities necessary for ser profile control, including user registration and authentication. The profile is described in the pres

30、ent document as an active UML class shown in figure 1, identifying the ports and interfaces. The signals used to invoke the service capabilities are identified in figure 2. package ProfileProfile Root 1/2Profile+CurrentLocation: location+CurrentUserStatus : userStatus+Service: serviceDescriptor 1*+S

31、ecurity: securityProfileprofile() /* Run on first instantiation and sets state model for profile */User : CharstringUserIOFromUser ToUserManagerIOFromManager ToManager:Interfaces:FromUser:Interfaces:ToUser:Interfaces:FromManager:Interfaces:ToManagerFigure 1: Class diagram showing the root class for

32、profile, ports and interfaces ETSI ETSI TR 101 882 V5.1.1 (2004-05) 8 package InterfacesInterfaces 1/2FromUsersignal SetUserStatus(status:userStatus)signal GetUserStatus()signal UpdateLocation(newLocation:location)signal InterrogateLocation()signal UpdateServiceStatus(name:serviceName, status:servic

33、eStatus)signal GetServiceStatus(name:serviceName)signal GetServiceDescriptor(name:serviceName)signal AuthenticateChallenge(challenge:BitString)signal GenerateMIAC(packet:BitString)ToUsersignal ReportUserStatus(status:userStatus)signal ReportLocation(oLocation: location)signal ErrorIndication(error:C

34、harstring)signal ReportServiceStatus(sStatus:serviceStatus)signal ReportServiceDescriptor(svc:serviceDescriptor)signal ReportAuthResponse(response:BitString)signal ReportMessageAuthIntCode(miac:BitString)signal SuccessIndication(successMsg:Charstring)FromManagersignal AddServiceToProfile(serviceToAd

35、d:serviceDescriptor)signal DeleteServiceFromProfile(serviceToDelete:serviceName)signal ToggleAuthentication ()signal GetAuthenticationStatus ()ToManagersignal ErrorIndication(error:Charstring)signal ReportAuthenticationStatus(status:Boolean)signal SuccessIndication(successMsg:Charstring)Figure 2: Cl

36、ass diagram showing the signals belonging to each interface ETSI ETSI TR 101 882 V5.1.1 (2004-05) 9 4.2 Data model The data model derived from TR 101 878 1 is shown in figures 3 and 4. package DataDefinitionsDataDefinitions 1/2locationgeoDatacallerLocationserviceDescriptor+SvcName: serviceNameSvcPro

37、vider: spoANameSvcAuth: serviceCredential 01SvcStatus: serviceStatusSvcParams: serviceParametersspoANameserviceParametersCallDesc: callDescriptor 01BearerDesc: bearerDescriptor 0*serviceNameTIPHONR4SimpleCallTIPHONR4EPTSSimpleCallserviceStatusServiceOfflinecallDescriptor /* From Call model */bearerD

38、escriptor/* From bearer model */userStatusOnlineOfflineBusyAwayBeRightBackFigure 3: Data model for profile ETSI ETSI TR 101 882 V5.1.1 (2004-05) 10package DataDefinitionsSecurityData 2/2securityProfileSA_identity : Charstring+AuthenticationSupport: Boolean = true+IntegritySupport: Boolean+Encryption

39、Support: BooleanserviceCredentialauthCertificatex509CertificateFigure 4: Data model for security elements in profile 4.3 Profile group service capabilities The service capabilities act on the overall data model as defined in clause 4.2 and manipulate the data within the user profile. Some of the ser

40、vice capabilities defined in TR 101 878 1 may be generated as applications of other root capabilities and where this is the case the invocation is shown as “pseudo-code“ in Annex A. 4.3.1 Register The register service capability can be generated from application of other profile group service capabi

41、lities. Invocation of the register service capability is shown as “pseudo-code“ in Annex A. ETSI ETSI TR 101 882 V5.1.1 (2004-05) 114.3.2 Attach The attach service capability can be generated from application of other profile group service capabilities. Invocation of the attach service capability is

42、 shown as “pseudo-code“ in Annex A. 4.3.3 Authenticate The authenticate service capability is described by a set of capabilities allowing Challenge-Response authentication and Message Authentication Integrity Code authentication forms. These are shown in figures 5, 6, 7, and 8. The service capabilit

43、y supports symmetric and asymmetric keying methods, single and multi-pass protocols, and both unilateral and mutual authentication. void profile()authenticateCR 11/14IDLEInterfac es :FromUser:AuthenticateChallenge(Challenge)Security.AuthenticationSupportfalseInterfac es:ToUser:ErrorIndication(“Authe

44、ntication not supported“)IDLEtrueResponse = GenerateResponse(Challenge);Interfaces:ToUser:ReportAuthResponse(Response)IDLEFigure 5: State chart diagram for authenticate challenge response service capability ETSI ETSI TR 101 882 V5.1.1 (2004-05) 12void profile()toggleAuthentication 12/14IDLESecurity.

45、AuthenticationSupport = false;IDLEInterfaces:FromManager:ToggleAuthentication()Security.AuthenticationSupporttruefalseSecurity.AuthenticationSupport = true;IDLEInterfaces:ToManager:SuccessIndication(“Authentication set to off“)Interfaces:ToManager:SuccessIndication(“Authentication set to on“)Figure

46、6: State chart diagram for authenticate toggle service capability ETSI ETSI TR 101 882 V5.1.1 (2004-05) 13void profile()getAuthentication 13/14IDLEInterfac es :FromManager:GetAuthenticationStatus()Interfac es :ToManager:ReportAuthenticationStatus(Security.AuthenticationSupport)IDLEFigure 7: State ch

47、art diagram for get authenticate status service capability ETSI ETSI TR 101 882 V5.1.1 (2004-05) 14void profile()generateMIAC 14/14IDLEInterfaces:FromUser:GenerateMIAC(packet)miac = GenerateMessageCode(packet);Interfac es :ToUser:ReportMessageAuthIntCode(miac)IDLEFigure 8: State chart diagram for ge

48、nerate message integrity and authentication code service capability ETSI ETSI TR 101 882 V5.1.1 (2004-05) 154.3.4 Get user status The get user status service capability allows an authorized user to query the current status of a user (the requesting user or another). The service capability requiremen

49、ts are specified in figure 9. void profile()getUserStatus 3/14IDLEInterfaces:FromUser:GetUserStatus()Interfaces:ToUser:ReportUserStatus(CurrentUserStatus)IDLEFigure 9: State chart diagram for get user status service capability 4.3.5 Deregister The deregister service capability can be generated from application of other profile group service capabilities. Invocation of the deregister service capability is shown as “pseudo-code“ in Annex A. 4.3.6 Transfer The transfer service is external