1 / 20

3GPP also covers service interactions, 3GPP2 does not 3GPP requirements more detailed

3GPP2 Supplementary Services TRANSFER to 3GPP Common IMS Gap Analysis December 5, 2007 by Liliana Dinale, Barbara Pareglio- Ericsson & Lee Valerius-Nortel. General. 3GPP also covers service interactions, 3GPP2 does not 3GPP requirements more detailed. General.

ravi
Télécharger la présentation

3GPP also covers service interactions, 3GPP2 does not 3GPP requirements more detailed

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 3GPP2 Supplementary Services TRANSFER to 3GPP Common IMSGap AnalysisDecember 5, 2007by Liliana Dinale, Barbara Pareglio- Ericsson&Lee Valerius-Nortel

  2. General • 3GPP also covers service interactions, 3GPP2 does not • 3GPP requirements more detailed

  3. General • Main services required by 3GPP2 are already covered and fully specified by 3GPP on stage 1 and stage 3 level. • The 'XCAP over Ut interface' capability is defined in 24.173, but 3GPP2 doesn't specify the Ut interface. Following services are not covered by 3GPP: • Call Waiting is not specified, but 3GPP2 only requires basic call capabilities, so it is implicitly covered • Feature codes are not covered by 3GPP • Ringback tones, work ongoing, requirements stable in 3GPP, TR started • Flexible Alerting • DTMF Support • Voice Mail Deposit (VMD) / Voice Mail Retrieval (VMR) • Directory Assistance / Short Code Dialing / Abbreviated Dialing

  4. Call Hold • Requirement: Same • 3GPP2 Implementation difference for providing announcement. No good reason to deviate though.

  5. Call Waiting • Requirement: 3GPP does not have this requirement, because it is not really needed when using SIP • TISPAN works on it in R2, because it is useful with legacy terminals • 3GPP2 Proposal: AS does nothing so not service logic needed really.

  6. Call Transfer • Requirement: Same • 3GPP2 proposal same as what is specified in 3GPP but X.P0055 has the 3pcc implementation variant whereas 24.173 does not

  7. Call Forwarding • Requirement: • Call forwarding unconditional, 3GPP has richer requirement but essence the same • Call forwarding on busy, 3GPP has richer requirement but essence the same • Call forwarding no answer, combination of 3GPP CFNoReply & CFNotLoggedIn • 3GPP has additional service forwarding on • Not Logged In, • Communication Deflection, • Not Reachable • In general 3GPP also adds the possibility for the served use to obtain a notification that the services is activated • limit the max number of diversions • 3GPP2 flows are inline with 3GPP specification • Call forwarding no answer,call flow only covers No Reply case?

  8. Caller ID Presentation • Requirement: Same (OIP/OIR in 3GPP) • 3GPP2 proposal: Call flows are unclear, might be an unwanted deviation like services being executed in wrong AS.

  9. Terminating ID Presentation • HSS Collective Requirement: Same (TIP/TIR in 3GPP) 3GPP2 hinted stage 2/3 proposal: Call flows are unclear, might be an unwanted deviation like services being executed in wrong AS.

  10. Three Way Conferencing • Requirement:Feature is covered by 3GPP CONF • 3GPP2 adds useful restrictions, like if controlling user leaves the conference is terminated. This could be a useful addition to the 3GPP CONF service, although this might already be implied by the 3GPP referred documents. • 3GPP CONF is a richer service putting no limitation on the number of participants or the way how the conference is created • 3GPP2 proposal is inline with the “Three-way session creation” procedure as specified in the 3GPP CONF service. • X.P0055 assumes that in order to invite another user to join a conference, the conference creator REFERs the other end point[s] to the conference server whereas 24.173 assumes that the conference creator REFERs the conference server to the other end point[s]

  11. Message Waiting Indication • Requirement: Same • 3GPP2 proposal: Same, except MESSAGE scenario mentions encapsulated SMS • (Message Waiting Indication (X.P0055 [actually, X.S0048] specifies the 'MESSAGE method with encapsulated SMS message' delivery method whereas 24.173 does not )

  12. DTMF Support • No 3GPP requirement • DTMF can be carried in several ways in IMS.

  13. User Provisioning • This is covered in 3GPP through Ut (XCAP) interface. • DTMF and/or feature code interaction is not covered for the 3GPP services. • Feature codes are covered as part of the services in 3GPP

  14. Ringback Tones • Being worked on in 3GPP and TISPAN. • Requirements stable, TR work started. No existing specification.

  15. Directory Assistance • Special number • No 3GPP requirement

  16. Voice Mail Deposit/Retrieval • Voice Mail Deposit • This is covered by Call Forwarding on Busy, no need for 3GPP to have a separate specification for this. • Voice Mail Retrieval • Special number, 3GPP requires no standardisation for that.

  17. Flexible Alerting • Not in 3GPP/TISPAN. • This is a Hunt Group/Paralel Alerting style service, not covered in 3GPP nor TISPAN.

  18. Outbound/Inbound Call Restriction • Requirement: 3GPP has Outgoing/Incoming Communication Barring • The required tel uri prefix matching is not covered in the current Ut configuration stage 3. • 3GPP2 proposal: Same as 3GPP • 3GPP stage 3 user configuration richer then envisioned by 3GPP2.

  19. Vanity Numbers/Short Code/Abbreviated Dialling • Not in 3GPP/TISPAN. • Special numbers, can be achieved with call forwarding. • (In 3GPP2 these are all AS-based number/address resolution features) • No need for 3GPP to specify a separate service.

  20. Conclusion • There are some 3GPP2 services that are not specified by 3GPP, there are some common services slightly differentbut the 3GPP2 specifications are under work under review and this may change.

More Related