ETSI TR 187 015-2011 Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) Prevention of Unsolicited Communication in the NGN (V3 1 1)《电_1.pdf

1、 ETSI TR 187 015 V3.1.1 (2011-05)Technical Report Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);Prevention of Unsolicited Communication in the NGNETSI ETSI TR 187 015 V3.1.1 (2011-05) 2Reference DTR/TISPAN-07034-NGN-R3 Keywords architecture, securit

2、y 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 the present document can

3、 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). In case of dispute, the

4、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 this and other ETSI docum

5、ents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your 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 perm

6、ission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. 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 Membe

7、rs. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE 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 own

8、ed by the GSM Association. ETSI ETSI TR 187 015 V3.1.1 (2011-05) 3Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Abbreviations . 6g34 PUC requirements (stage 1) . 7g34.1 PUC objectives . 7g34.1.1 Basic o

9、bjectives 7g34.1.2 Interoperability with existing services 7g34.2 NGN service requirements for PUC . 7g35 PUC functional architecture (stage 2) 8g35.1 PUC Functional Elements and Elementary Functions 8g35.1.1 PUC Personalization Functional (PPF) . 8g35.1.2 PUC Setting Database (PSD) 9g35.1.3 PUC Han

10、dling Functional (PHF) 9g35.1.4 PUC Identification and Marking Function (PIMF) . 9g35.1.4.1 PUC Identification elementary Functional (PIF) 9g35.1.4.2 PUC Marking elementary Functional (PMF) 9g35.2 Functionality mapping on networks . 10g35.2.1 Mapped to a single NGN / single user scenario 10g35.2.2 M

11、apped to multi NGN / single user scenario 10g35.2.3 Mapped to home networks 11g35.2.4 Mapped to enterprise networks . 11g36 PUC information mitigation (stage 3) 12g36.1 PUC information propagation differentiation: 13g36.1.1 PUC information: downstream . 13g36.1.2 PUC information: upstream 13g36.2 In

12、terfaces for PUC information mitigation . 13g36.2.1 The PUC service mapped to subsystems: Isc 13g36.2.2 PUC internal functionalities mapped to NGN: Isc 14g36.2.3 PUC service mapped to UE: GM Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available

13、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 referenced in

14、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 Networking (

15、TISPAN). ETSI ETSI TR 187 015 V3.1.1 (2011-05) 51 Scope The present document describes a Prevention of Unsolicited Communications (PUC) service for use in the NGN. The present document defines the method by which a terminating party is prevented from receiving UC. The present document addresses the

16、NGN objectives (including the legal implications) that are met by the PUC service and identifies the requirements to be met by the NGN for PUC. The present document derives from TR 187 009 i.11. The present document covers deployment of the NGN in the following scenarios: Home networks, focusing on

17、interconnection from the CNG with the NGN and interaction between the CNG and CND. And proposing UC detection NGN SECurity (SEC); Requirements“. i.2 ETSI ES 282 001: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture“. i.3

18、ETSI TS 181 005 (V3.2.0): “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service and Capability Requirements“. i.4 ETSI TS 124 604 (V8.2.0): “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS);

19、 LTE; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.604 version 8.2.0 Release 8)“. ETSI ETSI TR 187 015 V3.1.1 (2011-05) 6i.5 ETSI TS 124 607 (V8.2.0): “Digital cellular telecommunications system (Phase 2+); Universal Mobile T

20、elecommunications System (UMTS); LTE; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.607 version 8.2.0 Release 8)“. i.6 ETSI TS 124 608 (V8.2.0): “Digital cellular

21、 telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR)using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 version 8.2.0 Rele

22、ase 8)“. i.7 ETSI TS 124 611 (V8.2.0): “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Anonymous Communication Rejection (ACR) and Communication Barring (CB)using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3

23、GPP TS 24.611 version 8.2.0 Release 8)“. i.8 ETSI TS 124 616 (V8.2.0): “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specific

24、ation (3GPP TS 24.616 version 8.2.0 Release 8)“. i.9 ETSI TS 124 654 (V8.2.0): “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification (3GPP TS

25、 24.654 version 8.2.0 Release 8)“. i.10 ETSI TR 187 002: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); TISPAN NGN Security (NGN-SEC); Threat, Vulnerability and Risk Analysis“. i.11 ETSI TR 187 009 (V2.1.1): “Telecommunications and Internet Conver

26、ged Services and Protocols for Advanced Networking (TISPAN); Feasibility study of prevention of unsolicited communication in the NGN“. i.12 ETSI TR 133 937: “Universal Mobile Telecommunications System (UMTS); LTE; Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI) (3

27、GPP TR 33.937)“. 3 Abbreviations For the purposes of the present document, the following abbreviations apply: AS Application Server CB Communication Barring CND Customer Network Device CNG Customer Network Gateway FE Functional Entity ICB Incoming Communication Barring IMS IP Multimdia Subsystem IMS

28、 IP Multimedia Subsystem NASS Network Access SubSystem NGN New Generation Networks PES PSTN/ISDN Emulation Subsystem PHF PUC Handling Functional PIF PUC Identification Function PIMF PUC Identification and Marking Function PMF PUC Marking Function PPF PUC Personalization Functional PSD PUC Setting Da

29、tabase PUC Prevention of Unsolicited Communication PUCI Prevention of Unsolicited Communication in IMS RACS Resource Admission Control Subsystem SDO Standard Development Organization ETSI ETSI TR 187 015 V3.1.1 (2011-05) 7SDT Session Duration Time SIP Session Initiation Protocol SS SoftSwitch UC Uns

30、olicited Communications UDP Use Datagram Protocol UE User Equipment UPSF/HSS User Profile Server Function / Home Subscriber Server 4 PUC requirements (stage 1) The PUC requirements were elaborated in the feasibility study on prevention of unsolicited communication in the NGN TR 187 009 i.11. The bas

31、ic PUC service requirements can also be found in the TISPAN service requirements document for Release 3 (TS 181 005 i.3), but the full set of requirements will be available in the NGN security requirements document (TS 187 001 i.1). 4.1 PUC objectives 4.1.1 Basic objectives OBJ 1 The NGN should prov

32、ide the ability for users to identify specific communication instances as UC. OBJ 2 The NGN should provide the ability to mark UC. OBJ 3 The NGN should provide the ability to react to UC. OBJ 4 The NGN should provide the ability to a user to personalize the UC profile. 4.1.2 Interoperability with ex

33、isting services OBJ 5 The NGN should provide Interoperability with existing solutions in the NGN. PUC should be interoperable with following existing supplementary services: Incoming Call Barring (White and Black list) - TS 124 611 i.7. Anonymous Call Rejection - TS 124 611 i.7. Closed User Groups -

34、 TS 124 654 i.9. Call Diversion on Originating Identity - TS 124 604 i.4. Malicious Communication Identification - TS 124 616 i.8. Originating Identity Restriction - TS 124 607 i.5. Terminating Identity Restriction - TS 124 608 i.6. 4.2 NGN service requirements for PUC The full set of requirements f

35、or PUC are listed in the TS 187 001 i.1. ETSI ETSI TR 187 015 V3.1.1 (2011-05) 85 PUC functional architecture (stage 2) Figure 1: PUC functional architecture 5.1 PUC Functional Elements and Elementary Functions 5.1.1 PUC Personalization Functional (PPF) The PUC Personalization Functional Entity (PPF

36、) provides the customization of the preferences of the PUC filtering and routing-criteria, both for end-user customization and operator wide settings. It directly interacts with the PSD where this information is stored. The PPF has two interfaces: To the end-user, for personalization of his profile

37、and the operator to configure global settings. To the database, to store the PUC related information. This functionality can be integrated in existing interfaces (e.g. for the IMS case: Ut). ETSI ETSI TR 187 015 V3.1.1 (2011-05) 95.1.2 PUC Setting Database (PSD) The PUC Setting Database (PSD) contai

38、ns the settings for the PUC service for the UC identification and the UC handling. The PSD serves the PIMF for personalized identification and the PHF for routing decisions. The PSD has three interfaces: To the PPF for configuring the settings for PUC. To the PIMF to configure the personalized setti

39、ngs for UC identification. To the PHF for configure personal and global routing decisions. This FE can reuse existing functionalities (e.g. by reusing the UPSF/HSS). 5.1.3 PUC Handling Functional (PHF) The PUC Handling Functional Entity (PHF) deals as service-broker for the PIMF. It receives the com

40、munication requests from every configured interface to the underlying networks, gets the customized and personalized PUC configuration and deals with the communication between the PIMFs. Furthermore, it administrates the ratings delivered by the PIMF and takes routing decisions based on their result

41、s of the UC likelihood and customized / personalized preferences. The PHF has several interfaces: to one or several PIMF FE for identifying UC; to each supported underlying network: - e.g. in case of IMS, it could be the Isc interface. 5.1.4 PUC Identification and Marking Function (PIMF) The PUC Ide

42、ntification and Marking Function (PIMF) deals on a technical level to identify and mark UC within the PUC service. A single PIMF consists of two elementary functions for identifying and marking of the communication as unsolicited. To serve existing services, the PIF can serve as interface to existin

43、g services (e.g. supplementary subsystems) which just need a PMF to form a full PIMF. The PIMF has one interface: to the PHF to serve the request from the PUC. 5.1.4.1 PUC Identification elementary Functional (PIF) The PUC Identification Function (PIF) is by technical mean the functionality which id

44、entifies unsolicited communication (e.g. call-rate limiter). 5.1.4.2 PUC Marking elementary Functional (PMF) The PUC Marking Function (PMF) provides, in conjunction with the PIF, the marking of the identified UC. The marking is highly dependent on the PIF and is used by the PHF to calculate the risk

45、 of an incoming communication attempt as unsolicited. ETSI ETSI TR 187 015 V3.1.1 (2011-05) 105.2 Functionality mapping on networks 5.2.1 Mapped to a single NGN / single user scenario Figure 2: PUC in a single deployment scenario 5.2.2 Mapped to multi NGN / single user scenario Figure 3: PUC in tran

46、sit NGN scenario Within this scenario, the user is connected via a transit network which has access to the communication path from the user to the service of his home NGN. The Transit NGN can apply PUC filtering by requesting his PUC service, the PHF addresses according to the routing rules the conf

47、igured PIMF modules which identify and mark the transiting communication request during its passes by. The home NGN can take the results from the signalling from the transit PUC service into account and apply additionally PIMF modules and apply a personalized handling for this UC request. A policy c

48、ooperation agreement is needed to provide a shared PUC service among these networks. ETSI ETSI TR 187 015 V3.1.1 (2011-05) 115.2.3 Mapped to home networks Figure 4: PUC in home network Within this scenario the user (CND) has a PUC service on his CNG and defines there his personalized filtering and h

49、andling of the identified unsolicited communication. The serving NGN can provide additional “pre-filtering“ of the communication and deliver the results as additional input to the PUC service hosted on the CNG. 5.2.4 Mapped to enterprise networks Figure 5: PUC in enterprise networks Within this deployment scenario, the PUC service provided by the NGN is additional. ETSI ETSI TR 187 015 V3.1.1 (2011-05) 126 PUC information mitigation (stage 3) To identify the related interfaces, a typical ca