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.
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.
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.
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