tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

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

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    66 p.
(P) V13.1.0    2016/01    67 p.
(P) V12.3.0    2015/03    64 p.
(P) V11.3.0    2015/03    58 p.
(P) V10.4.0    2015/03    53 p.
(P) V9.4.0    2015/03    53 p.
(P) V8.7.0    2015/03    53 p.


Rapporteur:  Mr. Wiehe, Ulrich
See also:  MMTel-related TS/TR    


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.


 

Here          Top          None          None          Next
part:    1     2

 

 

1   Scope [R8]   PDF-p. 8
2   References [R8]
3   Definitions, symbols and abbreviations [R8]   PDF-p. 9
4   General [R8]   PDF-p. 10
5   Architecture [R8]   PDF-p. 11
6   Specification with the binary option [R8]
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 services   PDF-p. 12      Up
6.1.2.1   Originating Identification Presentation (OIP)
6.1.2.2   Originating Identification Restriction (OIR)
6.1.2.3   Terminating Identification Presentation (TIP)   PDF-p. 13
6.1.2.4   Terminating Identification Restriction (TIR)
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)   PDF-p. 17      Up
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   PDF-p. 18
6.1.2.18   Closed User Group (CUG)
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 Indications      Up
6.3   Binary coding general
6.4   Binary coding of datasets
6.5   Compatibility mechanism   PDF-p. 35

Up          Top          ToC