Tech-invite   3GPPspecs   RFCs   SIP   Search in Tech-invite

21   22   23   24   25   26   27   28   29   30   31   32   33   34   35   36   37   38   41   42   43   44   45   46   48   49   50   51   52   55   Intro   TBs   RELs   Ref‑Points   IDs   ?  
in Index   Prev   Next

TS 29.364 (CT4)
IMS Application Server (AS) Service Data Descriptions
for AS Interoperability

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
V15.0.0 (PDF)  2018/06  64 p.
V14.0.0  2017/03  66 p.
V13.1.0  2016/01  67 p.
V12.3.0  2015/03  64 p.
V11.3.0  2015/03  58 p.
V10.4.0  2015/03  53 p.
V9.4.0  2015/03  53 p.
V8.7.0  2015/03  53 p.


Rapporteur:  Mr. Wiehe, Ulrich

Application Servers can store their service data on the HSS through the Sh interface as transparent data, meaning that the HSS may not be aware of the structure and the semantics of this data, only the Application Server has this knowledge. Standardizing the data formats would facilitate interoperation among Application Servers supplied by the same, or different, vendors. These Application Server vendors may be primary and secondary suppliers of the same service provider within a service provider's IMS network. This is especially true for the Multimedia Telephony supplementary services that can achieve a wide deployment and are here addressed by this specification.

This specification standardizes the structure and the coding of the service data that are transported over the Sh interface between an Application Server supporting Multimedia Telephony supplementary services as defined in TS 22.173 and the HSS. Two optional formats are specified. One is based on a binary coding of the service data and supports the subset of MMTEL services corresponding to PSTN/ISDN and CS supplementary services. The other uses an XML format and supports the full set of MMTEL Services.

full Table of Contents for  TS 29.364  Word version:   15.0.0

 

Here   Top

 

 

1  Scope [R8]Word-p. 7
2  References [R8]Word-p. 8
3  Definitions, symbols and abbreviations [R8]Word-p. 9
4  General [R8]Word-p. 10
5  Architecture [R8]
6  Specification with the binary option [R8]Word-p. 11
6.1  MMTEL service sontent with the binary option
6.1.1  List of IMS Multimedia Telephony supplementary services
6.1.2  Subset of MMTEL services matching PSTN/ISDN and CS supplementary servicesWord-p. 12
6.1.2.1  Originating Identification Presentation (OIP)
6.1.2.2  Originating Identification Restriction (OIR)
6.1.2.3  Terminating Identification Presentation (TIP)
6.1.2.4  Terminating Identification Restriction (TIR)Word-p. 13
6.1.2.5  Malicious Communication IDentification (MCID)
6.1.2.6  Anonymous Communication Rejection (ACR)
6.1.2.7  Communication DIVersion (CDIV)
6.1.2.8  Communication Waiting (CW)
6.1.2.9  Communication HOLD (HOLD)
6.1.2.10  Communication Barring (CB)
6.1.2.11  Completion of Communications to Busy Subscriber (CCBS)
6.1.2.12  Completion of Communications on No Reply (CCNR)Word-p. 17
6.1.2.13  Message Waiting Indication (MWI)
6.1.2.14  CONFerence (CONF)
6.1.2.15  Advice Of Charge (AOC)
6.1.2.16  Explicit Communication Transfer (ECT)
6.1.2.17  Reverse Charging
6.1.2.18  Closed User Group (CUG)Word-p. 18
6.1.2.19  Three-Party (3PTY)
6.1.2.20  Flexible Alerting (FA)
6.1.2.21  Customized Alerting Tones (CAT)
6.2  Datasets and Service IndicationsUp
6.3  Binary coding general
6.4  Binary coding of datasetsWord-p. 21
6.5  Compatibility mechanismWord-p. 35
7  MMTEL service data definition based on XML [R8]
7.1  General principlesUp
7.2  MMTEL services specification
7.2.0  Service Indications
7.2.1  MMTEL services schemaWord-p. 36
7.2.2  OIP serviceWord-p. 38
7.2.3  OIR service
7.2.4  TIP serviceWord-p. 39
7.2.5  TIR service
7.2.6  MCID serviceWord-p. 40
7.2.7  ACR serviceWord-p. 41
7.2.8  CDIV service
7.2.9  CW serviceWord-p. 42
7.2.10  HOLD service
7.2.11  CB service
7.2.12  CCBS/CCNR service
7.2.13  MWI service
7.2.14  CONF service
7.2.15  AOC service
7.2.16  ECT serviceWord-p. 46
7.2.17  Reverse charging serviceWord-p. 47
7.2.18  CUG service
7.2.19  3PTY service
7.2.20  FA service
7.2.21Void
7.2.22  CAT serviceWord-p. 48
8  Mechanisms for transfer of Service Data between Application Server and the HSS for AS interoperability [R8]Word-p. 50
9  IMS user group [R11]
10  ODB Information for IMS Oriented Services [R11]
11  IMS CAMEL Services [R12]Word-p. 56
12  Shared Repository Data identification [R13]Word-p. 62
A  Dataset example with variable length data [R8]Word-p. 65
B  Change historyWord-p. 66

Up   Top