Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 33.838  Word version:  11.0.0

Top   Top   None   None   Next
1…   4…

 

1  ScopeWord‑p. 5

The present document studies more focussed the high-level solutions possibilities for PUCI described in the technical report (TR 33.937) on PUCI.
The scope of the study includes:
  • Study of the PUCI related information:
    • What information to be stored in the HSS.
    • Type of PUCI information to be exchanged (e.g. scoring information, contextual information) and how this information should be structured, or even between which nodes the information should be sent.
    • If and how PUCI information should be sent inside SIP.
  • Study on Invoking of 3rd party PUCI AS or Supplementary Services (SS) depending on configuration.
  • Interworking
    • with non-IMS networks.
    • with other IMS services like SRVCC, ICS, and service continuity.
  • Types of communication that should/can be covered by PUCI, and how the different types of communication affect the PUCI solution.
  • How much of PUCI that can be achieved via prevention and how much needs to be done via treatment.
  • PUCIF to PUCIF communication.
  • Use of existing methods of user notification for PUCI communication.
  • Mitigation of source identity spoofing, especially from non-IMS networks, on the effectiveness of the PUCI mechanism.
  • Illustrative use of standardized PUCI features in typical deployment scenarios.
Up

2  References

The following documents contain provisions which, through reference in this text, constitute provisions 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 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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
ETSI TR 187 009: "Feasibility study of prevention of unsolicited communications in the NGN".
[3]
TR 33.937: "Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI)".
[4]
TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1".
[5]
TS 22.101: "Service aspects; Service principles".
[6]  (void)
[7]
IETF, "SPEERMINT WG Charter 2010-04-02", http://tools.ietf.org/wg/speermint/charters?item=charter-speermint-2010-04-02.txt
[8]
RFC 5486,  "Session Peering for Multimedia Interconnect (SPEERMINT) Terminology"
[9]
IETF, "VoIP SIP Peering Use Cases", Work in progress, Internet-Draft: draft-ietf-speermint-voip-consolidated-usecases-18, April, 2010.
[10]
IETF, "SPEERMINT Security Threats and Suggested Countermeasures", Work in progress, Internet-Draft: draft-ietf-speermint-voipthreats-05, Sept, 2010.
[11]
RFC 3324,  "Short Term Requirements for Network Asserted Identity".
[12]
RFC 3325,  "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks".
[13]
RFC 3893,  "Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format".
[14]
RFC 4474,  "Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)".
[15]
RFC 5039  "The Session Initiation Protocol (SIP) and spam".
[16]
TS 29.328: "IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents".
[17]
TS 29.329: "Sh interface based on the Diameter protocol; Protocol details".
[18]
IETF draft Spam Score for SIP (draft-wing-sipping-spam-score-02) draft-wing-sipping-spam-score-02
[19]
TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[20]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
Up

3  Definitions, abbreviationsWord‑p. 6

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Unsolicited Communication:
bulk communication in IMS where the benefit is weighted in favour of the sender.
UC Score:
value that is assigned to a communication request indicating the likelihood that a given communication request is UC.
Up

3.2  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
AS
Application Server
B2BUA
Back to Back User Agent
CB
Call Barring
EU
European Union
ICS
IMS Centralized Services
iFC
initial Filter Criteria
IMR
Identify, Mark, React
IPsec
IP Security
MCID
Malicious Communication Identification
OECD
Organisation of Economic Co-operation and Development
PUCI
Protection against Unsolicited Communication for IMS
PUP
PUCI User Policy
SC
Service Continuity
SEG
Security Gateway
SIP
Session Initiation Protocol
SRVCC
Single Radio VCC
UC
Unsolicited Communication
US
United States
VCC
Voice Call Continuity
VoIP
Voice over Internet Protocol
Up

Up   Top   ToC