ETSI TS 101 882-2-2003 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4 Protocol Framework Definition Part 2 Registration and Service Attachm.pdf

《ETSI TS 101 882-2-2003 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4 Protocol Framework Definition Part 2 Registration and Service Attachm.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 101 882-2-2003 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4 Protocol Framework Definition Part 2 Registration and Service Attachm.pdf（54页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 101 882-2 V4.1.1 (2003-09)Technical Specification Telecommunications and Internet ProtocolHarmonization Over Networks (TIPHON) Release 4;Protocol Framework Definition;Part 2: Registration and Service Attachment service meta-protocol definitionfloppy3 ETSI ETSI TS 101 882-2 V4.1.1 (2003-09)

2、2 Reference RTS/TIPHON-03016-2R4 Keywords interface, IP, meta-protocol, protocol, service, 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-Prf

3、ecture de Grasse (06) N 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 v

4、ersions, the reference 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 t

5、o revision or change of 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 au

6、thorized by written permission. 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 th

7、e TIPHON logo are Trade 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-2 V4.1.1 (2003-09) 3 Contents Intellectual Property Rights5 Foreword

8、.5 Introduction 5 1 Scope 6 2 References 6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 Registration service7 4.1 Purpose.7 4.2 Description .7 4.3 Procedures 8 4.3.1 Provision/withdrawal8 4.3.2 Normal procedures8 4.3.2.1 Activation/deactivation .8 4.3.2.2 Invocation and

9、operation.8 4.3.3 Exceptional procedures.9 4.4 Interaction with other services or service capabilities9 4.5 Overall behaviour.10 5 Functional entity model and information flows .12 5.1 Functional entity model12 5.1.1 Description of model 12 5.2 Information flows.13 5.2.1 Relationship ra13 5.2.1.1 Re

10、gister .13 5.2.1.2 DeRegister.14 5.2.2 Relationship rb14 5.2.2.1 Authorize.14 5.2.2.2 Detach .15 5.2.3 Relationship rc15 5.2.3.1 Attach15 5.2.4 Relationship rd15 5.2.4.1 Detach .15 5.2.5 Summary of information element definitions .16 5.2.6 Information flow sequences16 5.2.6.1 Normal operation 17 5.2

11、.6.1.1 Initial registration 17 5.2.6.1.2 Change of SpoA (location update) 18 5.2.6.1.3 DeRegistration.19 5.2.6.2 Exceptional operation20 5.2.6.2.1 Invalid identity 20 5.2.6.2.2 Service not available21 5.3 Registration functional entity actions.21 5.3.1 Actions of RFE1 .22 5.3.2 Actions of RFE2 .22 5

12、.3.3 Actions of RFE3 .23 5.3.4 Actions of RFE4 .23 5.4 Registration functional entity behaviour 23 5.4.1 Behaviour of RFE1 .23 5.4.2 Behaviour of RFE2 .28 5.4.3 Behaviour of RFE3 .34 5.4.4 Behaviour of RFE4 .37 5.5 ASN.1 data definitions .39 ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 4 5.6 Allocation o

13、f functional entities to domains.41 Annex A (informative): Additional SDL used in modelling .42 Annex B (informative): SDL model 52 Annex C (informative): Bibliography.53 History 54 ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 5 Intellectual Property Rights IPRs essential or potentially essential to the

14、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 potentially Essential, IPRs notified to ETSI i

15、n 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 carried out by ETSI. No guarantee can be given as

16、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 Telecommunications and Internet Protocol Harmo

17、nization Over Networks (TIPHON). The present document is part 2 of a multi-part deliverable. Full details of the entire series can be found in part 1 9. Introduction The present document is a product in TIPHON Release 4 (see TR 101 301 8) of step C of the TIPHON development process described in ETSI

18、 TR 101 835 7. ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 6 1 Scope The present document defines 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

19、 Release 4. The present document defines the meta-protocol requirement for the registration and service attachment services in TIPHON. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either s

20、pecific (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 available in the expecte

21、d location might be found at http:/docbox.etsi.org/Reference. 1 Void. 2 Void. 3 ETSI TR 101 877: “Telecommunications 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

22、 Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Service Capability Definition; Service Capabilities for TIPHON Release 4“. 5 ITU-T Recommendation I.130: “Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN“. 6 ETSI

23、 TS 102 165-1 V4.1.1: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Protocol Framework Definition; Methods and Protocols for Security; Part 1: Threat Analysis“. 7 ETSI TR 101 835: “Telecommunications and Internet Protocol Harmonization over Networks (TIPHO

24、N); Project method definition“. 8 ETSI TR 101 301: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Release Definition; TIPHON Release 3 Definition“. 9 ETSI TS 101 882-1: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4

25、; Protocol Framework Definition; Part 1: Meta-protocol design rules, development method, and mapping guideline“. ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 7 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions given in TR 101 877

26、 3 and TS 101 878 4 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 101 877 3, TS 101 878 4 and the following apply: FE Functional Entity IMSI International Mobile Subscriber Identity MSC Message Sequence Chart RFE Registration Functional Entities Spo

27、A Service provider point of attachment UML Unified Modelling Language 4 Registration service 4.1 Purpose The purpose of the registration and service attachment service is to provide authorization of users to access services. In addition the registration and service attachment service provides a mech

28、anism for security countermeasure C1 as identified in TS 102 165-1 6. 4.2 Description The registration service enables a user (the registrant) to seek and gain authority to invoke service in a domain for which access is strictly controlled. The service applications to be offered are determined, in p

29、art, by data held in the user profile. Figure 1 shows the relationship of the core elements in registration. Registrant RegistrarSpoAUser registrationService preparationService attachmentFigure 1: Relationship of registration entities The registrar maintains a record of the location of the registran

30、t and acts as an arbitrator on the provision of individual services to the registrant. Figure 2 shows by means of an UML class diagram the ordinality of the relationships to be considered in the registration and service attachment service. ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 8 User RegistrantReg

31、istrarServiceProviderService11.*1*1*1*NOTE 1: A single user may be associated with many registrants. NOTE 2: A registrant shall be associated with only one user. NOTE 3: A registrant shall be associated with only one registrar. NOTE 4: A registrar may be associated with many registrants. NOTE 5: A s

32、ervice may be associated with many service providers. NOTE 6: In any registration instance a service shall be associated with only one service provider. NOTE 7: A service provider shall be associated with only one Service. NOTE 8: A registrant may be associated with many Services. Figure 2: Ordinal

33、relations in TIPHON The registrar authorizes access to service applications in the domain in which the registrant is located or in another domain in which the entity controlling the service application is located. If the registrar determines that the user is no longer authorized for a service applic

34、ation or set of service applications, e.g. if a pre-paid account has been depleted, the registrar shall inform the registrant and the service provider. The registration service is offered across a network or set of networks (parts of which may be under different administrative control). 4.3 Procedur

35、es 4.3.1 Provision/withdrawal Registration is available on a per-name/per service basis to all customers of a TIPHON system. 4.3.2 Normal procedures 4.3.2.1 Activation/deactivation Registration shall be activated at provision and deactivated at withdrawal. 4.3.2.2 Invocation and operation Registrati

36、on shall be invoked by at least one of the following events: on power-up of the user equipment; on change of physical point of attachment; on change of logical point of attachment; ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 9 on demand by the user; and on demand by the network. A user shall indicate in

37、 a registration request those services to be registered to and shall be informed by the registrar where those services can be provided. If a registrant registers from a new location to a service it is already registered to and a new service provider is allocated the registrar shall be able to delete

38、 the registrants details from the old serving service provider. 4.3.3 Exceptional procedures If the registrar is unable to determine where the requested service can be provided it shall inform the registrant with an indication of the reason for the rejection of the registration request. Possible rej

39、ection causes include inadequate capacity at an available service provider to maintain the required level of service. 4.4 Interaction with other services or service capabilities The registration and service attachment service described in the present document implements the following service capabil

40、ities defined within the Profile class of TS 101 878 4 for TIPHON Release 4: attach; authorize; deregister; detach; and register. In addition the service capability authenticate may be invoked during registration. In such cases any failure of authentication shall terminate registration without the a

41、uthorization of service to the registrant. Some capabilities of the call and bearer classes may, depending on the overall service definition, be dependent upon the use of service capabilities which are described in the present document. The interaction with services and service capabilities implemen

42、ted in such services is outside the scope of the present document. ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 104.5 Overall behaviour The overall behaviour is shown in figures 3 and 4 for the registration service. ServiceattachedActivatedRegistration requestRegisteredAttachment requestRegistration acce

43、pted and SpoA identifiedRegistration rejectedAttachment acceptedAttachment rejectedFigure 3: Overall behaviour for registration service expressed as an UML activity diagram ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 11Registrant :NGNUserRegistrar :ProfileSpoA : Profileregister( )deregister( )authorise(

44、 )attach( )detach( )Figure 4: Overall behaviour in terms of TIPHON service capabilities ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 125 Functional entity model and information flows 5.1 Functional entity model 5.1.1 Description of model The functional model shall comprise the following Registration Func

45、tional Entities (RFE): Table 1: Registration functional elements Identity Description Registering user RFE1 Registrant, the logical entity being registered RFE2 Registrar, holder of user profile of the registrant RFE3 Serving service provider point of Attachment (SpoA) RFE4 Previous SpoA FE1FE2FE3ra

46、rbrcFE4rdFigure 5: Relationships between functional entities for registration ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 13system RegistrationRFE4RFE1 RFE2RFE3RegUserru_d ru_urara_ura_drdrd_drd_urbrb_urb_drcrc_urc_dFigure 6: Relationships between functional entities for registration as SDL system diagr

47、am 5.2 Information flows The following conventions are used to identify information flows: an information flow is referred to as a “request“ at the FE that sends it and as an “indication“ at the FE that receives it, this is shown in the tables defining each information flow as “req_ind“; the corresp

48、onding confirmation is referred to as a “response“ at the FE that sends it and as a “confirmation“ at the FE that receives it, this is shown in the tables defining each information flow as “resp_conf“. 5.2.1 Relationship ra 5.2.1.1 Register Register is a confirmed information flow used by RFE1 to re

49、quest the RFE2 to open the users profile. ETSI ETSI TS 101 882-2 V4.1.1 (2003-09) 14Table 2: Register information flow Information element Value Req_ind Resp_conf TIPHON-reg-id Any M M RegistrationMode Initial registration Location update M -Location Any M - ServiceName TIPHONSimpleCall M O (see note 2) Result Registration successfulRegistration-Id invalid Service unavailable - M ServiceProviderName Any - O (see note 1) ClientAuthorisationToken Any - O (see note 1) NOTE 1: Provided if Result = “Registratio