1 / 4

3GPP2 IMS Supplementary Services: Flexible Alerting

3GPP2 IMS Supplementary Services: Flexible Alerting. Introduction to Service. 3GPP-3GPP2 Common IMS Workshop 24-25 January 2008 Puerto Vallarta, Mexico Tdoc CIMS-080012. Textual Description of Flexible Alerting.

field
Download Presentation

3GPP2 IMS Supplementary Services: Flexible Alerting

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 IMS Supplementary Services: Flexible Alerting Introduction to Service 3GPP-3GPP2 Common IMS Workshop 24-25 January 2008 Puerto Vallarta, Mexico Tdoc CIMS-080012

  2. Textual Description of Flexible Alerting • Application Server-based group termination service in which all members of the FA group are alerted in parallel. • The group is alerted by the dialing of a group identifier (i.e., a E.164 number or a SIP URI). The group identifier is referenced as the “pilot identity”. • The “pilot identity” maps to a set of public user identities (PUI), where each PUI references a member of the group • The set of PUIs can map to ANY combination of devices • For example - group of three members – T-Mobile CS device belonging to subscriber A, Verizon IMS device belonging to subscriber A, PSTN phone belonging to subscriber B • Terminating to the pilot identity results in the AS initiating a dialog with each of the group members. • The first member to answer is awarded the call – all other call ‘legs’ are abandoned • This feature is not SIP forking in IMS! See contrast and comparison on the following two slides

  3. SIP Forking in IMS – Information Flow • ‘Fan out’ occurs at S-CSCF • Per IETF RFC 3261, many alerting patterns are possible: all parallel, strict sequential, sequential alerting of groups 1. INVITE (PUI) 2a. INVITE (PUI) S-CSCF Device 1 (Subscriber-A) 2b. INVITE (PUI ) Device 2 (Subscriber-A) 2c. INVITE (PUI) Device 3 (Subscriber-A)

  4. 3GPP2 Flexible Alerting – Info Flow • ‘Fan out’ occurs at AS pointed to by the S-CSCF associated with the pilot identity 2. INVITE (PUI=Pilot) 3a. INVITE (PUI #1) S-CSCF For ‘Pilot’ # AS for FA Device 1 (Subscriber-A) 3b. INVITE (PUI # 2) Device 2 (Subscriber-B) 3c. INVITE (PUI # 3) Device 3 (Subscriber-C)

More Related