Tech-invite3GPP-SpecsReleasesFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

Top   in Index   Prev   Next

TS 24.628CT1
Common Basic Communication Procedures
using 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
V16.0.0 (Wzip)  2019/09  60 p.
V15.0.0 (PDF)  2018/06  62 p.
V14.1.0  2017/12  63 p.
V13.2.0  2016/06  62 p.
V12.4.0  2016/06  60 p.
V11.2.0  2013/03  60 p.
V10.4.0  2012/12  59 p.
V9.5.0  2012/12  53 p.
V8.6.0  2012/12  50 p.

Rapporteur:  Mr. Leis, Peter

This TS describes the stage three protocol for basic communication procedures common to several services in the IP Multimedia (IM) Core Network (CN) subsystem when at least one Application Server (AS) is included in the communication. The common procedures are based on stage three specifications for supplementary services.

full Table of Contents for  TS 24.628  Word version:   16.0.0

Here   Top
1  ScopeWord-p. 6
2  References
3  Definitions and abbreviationsWord-p. 7
4  Common basic communication proceduresWord-p. 8
4.1  Introduction
4.2  Announcement
4.3  Alternative ring tone
4.3A  Voicemail server identification [R9]Word-p. 10
4.4  Network Determined User Busy (NDUB)
4.4a  Special REFER request handling procedures
4.4b  Screening of 200 (OPTIONS) response content [R12]Word-p. 11
4.5  Operational requirements
4.6  Coding requirements
4.7  Signalling procedures
4.8  Interactions with other networks
4.9  Signalling flows
4.10  Parameter values (timers)
A  Signalling flows for announcementsWord-p. 19
A.1  Providing announcements to a user during the establishment of a communication session
A.2  Providing announcements to a user during an established communicationWord-p. 28
A.3  Communication request rejectedWord-p. 31
A.4  Providing announcements to a user during the release of a communication session
A.5  Providing announcements to a terminating user just after the call is answered and before establishing direct communication session between end users [R10]Word-p. 41
B  Signalling flows for Network Determined User Busy (NDUB)Word-p. 46
C (Normative)  Void
D (Normative)  AS establishing multiple dialogs with originating UEWord-p. 50
E  Signalling flows for 3rd party call controlWord-p. 51
G (Normative)  AS actions using gateway model [R13]Word-p. 58
H  Change historyWord-p. 59

Up   Top