1、 ETSI TS 132 373 V9.0.0 (2010-02)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Security services for Integration Reference Point (IRP);Common Object Request Broker Architecture (CORBA)
2、solution (3GPP TS 32.373 version 9.0.0 Release 9)ETSI ETSI TS 132 373 V9.0.0 (2010-02)13GPP TS 32.373 version 9.0.0 Release 9Reference RTS/TSGS-0532373v900 Keywords GSM, LTE, UMTS 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
3、 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 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
4、in print. In any case of existing or perceived difference in contents between such versions, 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 Secretari
5、at. 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 this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send yo
6、ur comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Stand
7、ards Institute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered 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. LTE
8、is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 373 V9.0.0 (2010-02)23GPP TS 32.373 version 9.0.0 Release 9Intellectual Proper
9、ty 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: “Intellectual Property Rights (IPRs); Ess
10、ential, 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 investigation, including IPR searches, ha
11、s 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 Specification (TS) has been produced by ET
12、SI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM,
13、 UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 373 V9.0.0 (2010-02)33GPP TS 32.373 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and ab
14、breviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Architectural features . 7g34.1 Principles of IRP Security Services 7g34.2 Request Interceptor. 8g34.2.1 Client-side Interceptor 9g34.2.2 Server-side Interceptor 9g34.2.3 Request Interceptor Security Attributes 10g34.3 Security Attributes
15、Service Protocol 10g34.3.1 Security Attribute Service context element 10g34.3.2 CORBA Security Service . 11g35 Mapping . 11g35.1 RI Solution Mapping 11g35.1.1 Security Attribute Mapping 11g35.2 SAS Solution Mapping . 12g35.2.1 Security Attribute Mapping 12g36 Itf-N Security Service Behaviour . 13g36
16、.1 Request Interceptor Solution 13g36.1.1 Authentication . 13g36.1.2 Authorization 13g36.1.3 Activity Log 13g36.2 Security Attributes Service Solution 14g36.2.1 Authentication . 14g36.2.2 Authorization 14g36.2.3 Activity Log 14g3Annex A (normative): IDL specifications 15g3A.1 IDL specification (file
17、 name “SecurityServiceConstDefs.idl“) 15g3A.2 IDL specification (file name “SecurityServiceSystem.idl“) . 16g3Annex B (informative): Authentication mechanism 17g3B.1 Basic authentication . 17g3B.2 Digest authentication 17g3B.3 Kerberos and SPKM . 17g3B.4 OMG CORBA CSIv2 Conformance Level 0 of Securi
18、ty 17g3Annex C (normative): Use of OMG specified security service . 18g3C.1 General . 18g3C.2 Authentication 18g3C.2.1 Transport Layer based method . 18g3ETSI ETSI TS 132 373 V9.0.0 (2010-02)43GPP TS 32.373 version 9.0.0 Release 9C.2.2 Client Authentication layer based method 19g3C.3 Authorization a
19、nd Access Control . 20g3C.4 (Message) Integrity and Confidentiality Protection . 20g3C.5 Quotation from OMG CORBA CSIv2 3 Conformance Levels of Security . 20g3Annex D (informative): Change history . 23g3History 24g3ETSI ETSI TS 132 373 V9.0.0 (2010-02)53GPP TS 32.373 version 9.0.0 Release 9Foreword
20、This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be
21、 re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where:x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second
22、 digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partner
23、ship Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.371: “Security Management concept and requirements“. 32.372: “Security services for Integration Reference Point (IRP); Information Service (IS)“. 32.373: “Security services
24、for Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) solution“. 32.375 “Security services for Integration Reference Point (IRP); File integrity solution“. In 3GPP SA5 context, IRPs are introduced to address process interfaces at the Itf-N interface. The Itf-N inte
25、rface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 1 and 3GPP TS 32.102 2. IRP consists of IRPManager and IRPAgent. Usually the
26、re are three types of transaction between IRPManager and IRPAgent, which are operation invocation, notification, and file transfer. However, there are different types of intentional threats against the transaction between IRPManagers and IRPAgents. All the threats are potential risks of damage or de
27、gradation of telecommunication services, which operators should take measures to reduce or eliminate to secure the telecommunication service, network, and data. The present document is applicable to the Interface IRP specifications. That is to say, it is only concerned with the security aspects of o
28、perations/notifications/file deployed across the Itf-N. The present document introduces security mechanisms in CORBA context to address IRP security requirements defined in 3GPP TS 32.371 4. ETSI ETSI TS 132 373 V9.0.0 (2010-02)63GPP TS 32.373 version 9.0.0 Release 91 Scope The present document spec
29、ifies the CORBA Solution for the IRP whose semantics is specified in 3GPP TS 32.372 5 Security Service for IRP Information Service. This Solution Set specification is related to 3GPP TS 32.372 5. Note that within the present document there are several alternate solutions. Specific choices will to be
30、 made to counter identified security threats , and to consider performance and cost criteria, i.e. an implementation is not expected to have to support every option for every deployment. 2 References The following documents contain provisions which, through reference in this text, constitute provisi
31、ons of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to
32、a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication ma
33、nagement; Architecture“. 3 3GPP TS 32.301: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements“. 4 3GPP TS 32.371 “Telecommunication management; Security Management concept and requirements“. 5 3GPP TS 32.372: “Telecommunication
34、management; Security services Integration Reference Point (IRP); Information Service (IS)“. 6 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements“. 7 OMG CORBA Specification 02-12-06 8 OMG CORBA Security Service Specification 02-03-11 htt
35、p:/www.omg.org/technology/documents/corbaservices_spec_catalog.htm 9 SECP Security Service Protocol http:/www.omg.org/technology/documents/formal/omg_security.htm#SECP 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS
36、 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.301 3 and the following apply: IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311 6. ETSI ETSI TS 132 373 V9.0.0 (2010-02)73GPP TS 32.373 version 9.0.0 Release 93.2 Abbreviations For the purposes of the present document, the following abb
37、reviations apply: CM Configuration Management CORBA Common Object Request Broker Architecture (OMG) EM Element Manager IDL Interface Definition Language (OMG) IOR Interoperable Object Reference IS Information Service NC Notification Channel (OMG) NE Network Element NV Name and Value pair OMG Object
38、Management Group ORB Object Request Broker (OMG) RI Request Interceptor QoS Quality of Service SAS Security Attributes Service (OMG) SECP Security Protocol SS Solution Set UML Unified Modelling Language (OMG) TII Time-Independent Invocation CSS Client Security Service TSS Target Security Service CA
39、Certificate Authority4 Architectural features The overall architectural feature of Security Services is specified in 3GPP TS 32.372 5. This clause specifies features that are specific to the CORBA Solution. 4.1 Principles of IRP Security Services As shown in figure 4.1, the Security Services are bet
40、ween IRP Application layer and Transport layer. Security Attributes which are attached to network management information are transferred between IRPManager and IRPAgent to address Authentication, Authorization, Activity Log and file integrity requirements. IRPManager ApplicationSecurity ServicesTran
41、sport layerIRPAgent ApplicationSecurity ServicesTransport layernetwork managementinformationattached Security AttributesFigure 4.1: Principles of IRP Security Services The basic idea of these Security Services is as follows: Security Services on IRPManager side and Security Services on IRPAgent side
42、 cooperate to secure the Itf-N. ETSI ETSI TS 132 373 V9.0.0 (2010-02)83GPP TS 32.373 version 9.0.0 Release 9When IRPManager and IRPAgent exchange network management information in a secured manner, the sender Security Service attaches Security Attributes to the network management information. The re
43、ceiver analyses the received Security Attributes to determine if the received network management information is authentic and authorized. The present document specifies two alternative CORBA solutions for attaching Security Attributes over Itf-N. They use different CORBA mechanisms to transfer the S
44、ecurity Attributes. One uses The CORBA Request Interceptor while the other uses the CORBA Security Attributes Service (SAS) protocol. Both solutions need to define their respective Security Attributes. The Security Attributes used by the Interceptor mechanism and the mechanism itself are defined by
45、the present document. The ones used by the CORBA SAS protocol are defined in CORBA SAS 7. In addition to the above two alternate mechanisms, the present document also specify a third alternative called Virtual Private Network (VPN) to secure the network management information exchanged between IRPMa
46、nager and IRPAgent. Such mechanism is defined in annex A of 3GPP TS 32.371 4. Table 4.1 identifies the use of the three alternatives to realize the Security Service such as Authentication Security Service, Authorization Security Service, Activity Log Security Service and File Integrity Security Serv
47、ice. Table 4.1: Alternate solutions and Security Service relationship Authentication Security Service Authorization Security Service Activity Log Security Service File Integrity Security Service Request Interceptor solution X X X SAS solution X X X VPN X X NOTE: “X“ means that “The Security Service
48、identified by the column name is realised by the use of Security Attributes in the solution identified by the row name. IRPManager and IRPAgent should decide to use one of the two alternative solutions to provide Authentication, Authorization and Activity Log Security Service at configuration/deploy
49、ment time, and it is not changeable at run time. IRP Manager and IRP Agents should both support VPN. In case CORBA-based security services are used to provide Authentication, Authorization and Activity Log Security Service, IRP Managers shall support SAS Solution and Request Interceptor Solution, while IRP Agents may support either SAS Solution or Request Interceptor Solution (it shall be noted that usage is determined at configuration/deployment time, and it is not changeable at run time). 4.2 Request Interceptor This clause
