ETSI TS 102 302-2-2004 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 5 Emergency Priority Telecommunications Service (EPTS) Part 2 System de.pdf

《ETSI TS 102 302-2-2004 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 5 Emergency Priority Telecommunications Service (EPTS) Part 2 System de.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 302-2-2004 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 5 Emergency Priority Telecommunications Service (EPTS) Part 2 System de.pdf（29页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 102 302-2 V5.1.1 (2004-05)Technical Specification Telecommunications and Internet ProtocolHarmonization Over Networks (TIPHON) Release 5;Emergency Priority Telecommunications Service (EPTS);Part 2: System description for EPTS in TIPHON networksETSI ETSI TS 102 302-2 V5.1.1 (2004-05) 2 Refer

2、ence DTS/TISPAN-02010-2-TIPHON_R5 Keywords emergency, IP, 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 Gra

3、sse (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 versions, the

4、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 to revision or

5、 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 authorized by w

6、ritten permission. The copyright and the foregoing 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

7、 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 102 302-2 V5.1.1 (2004-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6

8、2 References 6 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .7 4 Use case examination of EPTS 7 4.1 Use case 1: Establish policy .8 4.2 Use case 2: Implement policy.9 4.3 Use case 3: Allocate EPTS users9 4.4 Use case 4: Register to EPTS .9 4.4.1 Role of user.9 4.4.2 Role of t

9、he Registrar.9 4.5 Use case 5: Make EPTS call.10 4.5.1 Role of user.10 4.5.2 Role of resource manager .10 4.5.3 Making an ETS call (terminating scenario) 11 5 New service capabilities and modifications to existing service capabilities to support EPTS.11 5.1 Profile group.11 5.1.1 Additions to data t

10、ypes .11 5.1.1.1 Service name .11 5.1.1.2 Service credentials 11 5.1.2 Modification and extension to service capabilities .11 5.1.2.1 Add service to profile11 5.1.2.2 Remove service from profile.13 5.1.2.3 Authentication.14 5.1.2.4 Interrogate location .18 5.2 Call group.19 5.2.1 Additions to data t

11、ypes .20 5.2.1.1 Call type 20 5.2.1.2 Call priority.20 5.2.2 Modification and extension to service capabilities .20 5.2.2.1 Modify call priority.20 5.2.2.2 Call set up service capability.21 5.3 Media group .21 5.3.1 Addition to data types .21 5.3.1.1 Priority type.22 5.3.2 Extension and modification

12、 to media service capabilities 22 5.3.2.1 Set media encode service capability22 5.4 Message group24 5.4.1 Addition to data types .24 5.4.2 Extension and modification to service capabilities.24 Annex A (informative): Key management considerations for confidentiality, integrity and authentication.25 A

13、.1 Duration of Authentication session 25 A.2 Authentication data management .25 A.3 Encryption of Registration and Service request data .25 Annex B (informative): Policy considerations .26 ETSI ETSI TS 102 302-2 V5.1.1 (2004-05) 4 B.1 Policy establishment.26 B.1.1 EPTS users .26 B.1.2 Network priori

14、ty levels.26 B.1.3 Priority of user/organization.26 B.1.4 Applications supported.26 B.1.5 Identity presentation.26 B.1.6 Location of registration 26 B.1.7 Registrar availability 27 B.1.8 Queue management 27 B.2 Implementation of Policy .27 B.2.1 User/Organization profile.27 B.2.2 Resource manager (S

15、poA)27 B.2.3 EPTS users .27 Annex C (informative): Impact of EPTS on existing protocols28 C.1 SIP 28 C.2 ISUP/BICC.28 History 29 ETSI ETSI TS 102 302-2 V5.1.1 (2004-05) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The

16、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 available from

17、 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 referenced in ETSI

18、 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 Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networkin

19、g (TISPAN). The present document is part 2 of a multi-part deliverable covering Emergency Priority Telecommunications Service (EPTS), as identified below: TR 102 302-1: “Requirements analysis“; TS 102 302-2: “System description for EPTS in TIPHON networks“. ETSI ETSI TS 102 302-2 V5.1.1 (2004-05) 6

20、1 Scope The present document defines the operation of the Emergency Priority Telecommunications Service (EPTS) in a generic form. It defines the provision of EPTS, the invocation of EPTS by an authorized user, the validation and authentication mechanisms used to prove the credentials of the EPTS use

21、r, the extensions required to the TIPHON generic simple call for EPTS, and the inter-domain carriage of EPTS calls. In addition the mechanisms for revocation of user authorization and of the EPTS service are defined. 2 References The following documents contain provisions which, through reference in

22、 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, the latest version applies

23、. 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 102 302-1: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Emergency Priority Telecommunications Service

24、 (EPTS); Part 1: Requirements analysis“. 2 ETSI TS 101 878 (V4.1.1): “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Service Capability Definition; Service Capabilities for TIPHON Release 4“. 3 ETSI TR 101 882: “Telecommunications and Internet Protocol Harmo

25、nization Over Networks (TIPHON) Release 5; Protocol Framework Definition and Interface Requirement Definition; General“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: authentication: property by which the correct

26、identity of an entity or party is established with a required assurance NOTE: The party being authenticated could be a user, subscriber, service provider or network provider. authorization: act of determining if a particular right, such as access to some resource, can be granted to the presenter of

27、a particular credential ETSI ETSI TS 102 302-2 V5.1.1 (2004-05) 7 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: BICC Bearer Independent Call Control CUG Closed User Group EPTS Emergency Priority Telecommunications Service ETS Emergency Telecommunicati

28、ons Service FIFO First In First Out ID IDentifier ISUP ISDN User Part QoS Quality of Service SIP Session Initiation Protocol SpoA Service point of Attachment TRM Transport Resource Manager 4 Use case examination of EPTS The use cases shown in figure 1 show the “EPTS_user“ and “EPTS_Manager“ as speci

29、alizations of the TISPAN_user, with the addition of the EPTS management use cases. Note that there is a time dependence on the use cases, and the use cases below are described following the time dependence of events. ETSI ETSI TS 102 302-2 V5.1.1 (2004-05) 8 package TISPAN-ProfileUseCases 1/6EPTS_Us

30、er:TISPAN_userRegisterForEPTSRegistrant:TISPAN_userRegisterDeRegisterDetach_from_serviceAttach_to_serviceAuthorise_use_of_serviceRegistrar:TISPAN_userEPTS_Manager:TISPAN_userEstablishPolicyAllocateEPTSUsersImplementPolicyFigure 1: Use case diagram of EPTS service 4.1 Use case 1: Establish policy The

31、 purpose of this use case is to allow the responsible authorities to develop a policy which will be enforced when dealing with circumstances that require the EPTS to be invoked. Policy establishment is a pre-requisite for the use of EPTS. Although the policy establishment is outside the scope of the

32、 present document, annex B describes some of the elements that may contribute to policy establishment to develop the EPTS service, and its use. ETSI ETSI TS 102 302-2 V5.1.1 (2004-05) 9 4.2 Use case 2: Implement policy The purpose of this use case is to allow the policies defined under use case 1 to

33、 be implemented in the system and network to which they apply. This use case is not subject to standardization but is described in annex B. 4.3 Use case 3: Allocate EPTS users The purpose of this use case is to allow management of the EPTS users. This use case is not subject to standardization but i

34、s described in annex B. An EPTS user, once identified, shall be provisioned in the user-profile by allocation of the EPTS service definitions to the profile. Once provisioned, the user shall be able to attach to the EPTS services. 4.4 Use case 4: Register to EPTS This use case describes the registra

35、tion of the EPTS user. It covers the invocation of EPTS service in the profile, allows the user to attach to EPTS SpoA, leading to the usage of EPTS service, subject to EPTS policy. This use case is split into two use cases to describe the role of user and the registrar. 4.4.1 Role of user Prior to

36、accessing the network resources (for telephony, video, data), the EPTS user shall register with the EPTS service provider. Registration involves: identifying and verifying the user, and may include authentication; identifying the user location (where applicable). The user shall provide the user iden

37、tity registered for the EPTS service, as well as the authentication credentials. Upon successful authentication, the user will receive indication if the registration has been successful or not, and if the user is allowed to use the requested services. The EPTS user may also be informed of duration o

38、f the service, which could be a default value defined in policy. If the user receives an authentication failure indication, the user shall re-register by providing the user identity and authentication credentials. If the user receives the “service not available“ indication, the user shall abort atte

39、mpt to register with the registrar. If the user receives a “re-try after“ indication, the registrar shall abort the registration request and try to register again after the specified time in the “retry after“ indicator. The EPTS user will receive the identity of the resource manager, SpoA, along wit

40、h a credential valid for SpoA, from the registrar. The SpoA will provide resources for the users required services. The user shall use these credentials in its communications requests with the SpoA. The duration of these credentials can be limited to the authentication session. The EPTS user shall r

41、e-register with the registrar, if it wants to continue receiving the required services before the registration expires. If the registration expires, i.e. the authentication session terminates, the user can re-register. After the successful registration, the user can make use of the network resources

42、, e.g. make telephone calls. Note that the communications between the registrant and the registrar may be encrypted for added security to maintain the integrity, authenticity and confidentiality of communications. 4.4.2 Role of the Registrar The registrar is responsible for authenticating and author

43、izing the EPTS users, and provide or deny them access to network resources. Upon receipt of the Registration request, the registrar shall check the identity provided by the EPTS user. If the Identity provided corresponds to an existing valid identity held in the profile, the registrar shall proceed

44、to authenticate. If the identity provided does not exist, the registrar shall notify the user that the “authorization failed“. If the authentication credentials are correct, the registrar shall check if the user is allowed to receive the requested services. This authorization may be dictated by the

45、policies such as those described in annex B. If the authentication credentials are incorrect, the registrar shall notify the user that the “authentication failed“. ETSI ETSI TS 102 302-2 V5.1.1 (2004-05) 10If the user is authorized to receive the requested services, the registrar shall identify a re

46、source manager, SpoA that can provide the EPTS user with the requested services, e.g. telephony. If the EPTS user is authenticated but not authorized to access the requested services, the registrar shall respond with “service not authorized“. If the requested service is not available, the registrar

47、shall respond with “Service Not available“. If the registrar cannot process the request because of lack of resources, it shall respond with “retry-after“ message, indicating a time period after which the registrant can attempt to register again. The registrar shall then indicate to the SpoA that it

48、has been selected to provide the requested service to the EPTS user, providing it with the identity and credentials of the EPTS user. The registrar shall respond to the registrant with the “registration successful“ indication, along with any public identity that the EPTS user can use. The registrar

49、shall provide the identity and credentials for the SpoA to the user, indicating that this SpoA will serve the EPTS user for its communications services. The credentials are valid only as long as the authentication session is valid, or per policy arrangement. 4.5 Use case 5: Make EPTS call After the successful registration, as described in use case 4, the user can make use of the EPTS services allowed in the profile, such as telephony. This use case is split into two use cases for simplicity, describing the role of user and EPTS service provider (SpoA). 4.5.