TS 22.228
SA1
★
Service Requirements for IMS
use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V17.0.0 (Wzip)
2019/12 51 p.
V16.1.0 (Wzip)
2018/09 51 p.
V15.3.0 (PDF)
2018/06 52 p.
V14.1.0
2016/12 52 p.
V13.3.0
2015/06 51 p.
V12.10.0
2015/06 49 p.
V11.6.0
2012/12 40 p.
V10.5.0
2012/12 34 p.
V9.4.0
2012/12 33 p.
V8.7.0
2012/12 31 p.
V7.6.0
2007/10 21 p.
V6.11.0
2006/03 20 p.
V5.7.0
2006/03 16 p.
Rapporteur: Dr. Swetina, Joerg NEC Europe Ltd
This TS defines the service requirements from users' and operators' perspective for the support of IP multimedia applications through the IMS.
IP multimedia applications are supported by IP multimedia sessions in the IM CN Subsystem. IP multimedia sessions use IP connectivity bearers (e.g. GPRS as a bearer). Examples of IP multimedia applications include speech communication, real time multimedia applications, shared online whiteboards etc.
full Table of Contents for TS 22.228 Word version: 17.0.0
1 Scope Word-p. 7
2 References
3 Definitions and abbreviations
4 Introduction Word-p. 11
5 High level requirements
6 Standardised service capability approach Word-p. 13
7 User service requirements 
7.1 Identifying IP multimedia application subscriptions Word-p. 14
7.2 Access to the IM CN subsystem
7.3 Capability negotiation
7.4 Redirecting of IP Multimedia sessions Word-p. 15
7.5 Invoking an IP multimedia session
8 Interworking requirements [R6]
7.5.0 General [R11]
7.5.1 Identification and addressing
7.5.2 Negotiation at IM session invocation Word-p. 16
7.5.3 Emergency communications [R6]
7.5.4 Information of a Called Party [R10]
7.5.5 IMS Network-Independent Public User Identities (INIPUI) [R12] Word-p. 17
7.5.6 Void
7.5.7 Restricted local operator services [R16]
7.6 Handling of an incoming session (by the terminating entity) Word-p. 18
7.5.2 Negotiation at IM session invocation Word-p. 16
7.5.3 Emergency communications [R6]
7.5.4 Information of a Called Party [R10]
7.5.5 IMS Network-Independent Public User Identities (INIPUI) [R12] Word-p. 17
7.5.6 Void
7.5.7 Restricted local operator services [R16]
7.6.1 Automatic re-routing
7.6.2 Presentation of session originator identity
7.6.3 Negotiation of an incoming session
7.6.4 Accepting or rejecting an incoming session [R8]
7.6.5 Handling of an incoming session addressed to an unallocated identity [R10]
7.6.6 Differentiated paging for voice over E-UTRAN termination attempts [R13]
7.7 Handling of an ongoing session
7.6.5 Handling of an incoming session addressed to an unallocated identity [R10]
7.6.6 Differentiated paging for voice over E-UTRAN termination attempts [R13]
7.7.1 User modification of media in an ongoing session
7.7.2 Suspending and resuming of an ongoing session Word-p. 19
7.7.3 Presentation of identity of connected-to party of a session
7.8 Ending a session
7.9 Void
7.10 Handling of conferences [R6]
7.11 Handling of multicast services [R7]
7.12 Support for Local Numbers in the IMS [R7] Word-p. 21
7.13 User determined user busy [R8]
7.14 IMS Inter-UE Transfer [R9]
7.15 Prevention of Unsolicited Communication in IMS (PUCI) [R9] Word-p. 23
7.15.1 High level requirements
7.15.2 Detection of Unsolicited Communication
7.15.3 Prevention of Unsolicited Communication to the terminating party
7.15.4 Notification of UC to the originating party
7.15.5 Conveying information on UC to other networks
7.16 Support for Push Notification Service in IMS [R12]
7.15.2 Detection of Unsolicited Communication
7.15.3 Prevention of Unsolicited Communication to the terminating party
7.15.4 Notification of UC to the originating party
7.15.5 Conveying information on UC to other networks
8.1 General [R8]
8.2 Interworking with PLMN CS Domain [R8] Word-p. 24
8.3 Interworking with PSTN/ISDN networks [R8]
9 IP Addressing [R8]
10 Interconnection requirements [R8]
11 Support of WebRTC IMS Client access to IMS [R12] Word-p. 29
8.3.0 General
8.3.1 Overlap Signalling Word-p. 25
8.3.2 Subaddressing (SUB)
8.3.3 User-to-User Signalling (UUS)
8.4 Void
8.5 Interworking with Packet Cable [R8]
8.6 Interworking with Internet [R8] Word-p. 26
8.7 Voice Interworking with Enterprise IP-PBX [R11]
8.8 Interworking of Telepresence [R12]
8.9 Void
8.3.1 Overlap Signalling Word-p. 25
8.3.2 Subaddressing (SUB)
8.3.3 User-to-User Signalling (UUS)
11.1 Service description (informative)
11.2 Requirements
11.3 Protocol Conversion Minimization Requirements [R13] Word-p. 30
A Example IP multimedia application scenarios Word-p. 31
B Business models use cases [R8] Word-p. 35
C Basic communication cases for IMS networks [R8] Word-p. 37
D (Normative) Access to IMS via non-3GPP access [R8] Word-p. 39
E Example use cases for IMS Inter UE Transfer (i.e. transfer/replication/sharing) [R10] Word-p. 40
F Void
G Example use cases for IMS-Based Telepresence [R12] Word-p. 41
H Support of WebRTC client access to IMS [R12] Word-p. 42
H.1 General
H.2 WebRTC-based application supports broad IMS client capabilities
H.3 User gets their IMS service via third-party WebRTC-based application
H.4 User gets third-party IMS service via WebRTC-based application [R13]
H.5 Anonymous user gets IMS service via third-party WebRTC-based application
H.6 End to end WebRTC bearer support over IMS [R13]
I Change history Word-p. 48
H.6.1 Description
H.6.2 Pre-conditions Word-p. 46
H.6.3 Service flows
H.6.4 Post-conditions Word-p. 47
H.6.4 Post-conditions Word-p. 47
