1 / 14

URI As Service Indicator: Requirements

URI As Service Indicator: Requirements. Eric W m . Burger eburger@snowshore.com. Fundamental Question. Is There a Single Mechanism for Specifying Application Service Network Service Application Service Voice Mail, Unified Messaging, Pre-Paid, etc. Network Service

avian
Télécharger la présentation

URI As Service Indicator: Requirements

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. URI As Service Indicator: Requirements Eric Wm. Burger eburger@snowshore.com SIP/SIPPING Interim Meeting

  2. Fundamental Question • Is There a Single Mechanism for Specifying • Application Service • Network Service • Application Service • Voice Mail, Unified Messaging, Pre-Paid, etc. • Network Service • Announcement, Prompt & Collect, Start Script SIP/SIPPING Interim Meeting

  3. Characteristics of an Application Service (1/2) • Subscriber-Based • Provided By Proxy and Application Servers • Often Subscriber-Provisioned • Often Different Variations • Busy Greetings, Internal/External Caller By • Call Info / History (ISUP) • Selected URI (RFC 3087) • Personal Assistant:Subscriber vs. Caller Service SIP/SIPPING Interim Meeting

  4. Characteristics of an Application Service (2/2) • Number of Services Is Limitless • Bounded By Imagination • Flexibility in Scheme Has Definite Value • Interoperation Required Between • Proxy Servers • Application Servers • User Agent SIP/SIPPING Interim Meeting

  5. Examples of Application Service SIP Request-URIs • Deposit voice mail for RJS sip:deposit-sub-rjs@vm.provider.net • Deposit voice mail for RJS w/ busy greeting sip:deposit-busy-sub-rjs@vm.provider.net • Retrieve RJS’ voice mail sip:retrieve-sub-rjs@vm.provider.net • Start a prepaid call session (registered) sip:start-fancy-prepaid-outidal@pp.provider.net • Do magic application; proxy figures out where (registered) sip:do-my-magic@provider.net SIP/SIPPING Interim Meeting

  6. Characteristics of a Network Service (1/2) • Not Subscriber-Based • Provided By Media Server • Generally No Provisioning • Limited Variations • Announcement, Conference, Script, IVR • Flexible Scheme Has Limited Value and Definite Drawbacks SIP/SIPPING Interim Meeting

  7. Characteristics of a Network Service (2/2) • Interoperation Required Between • Proxy Servers and Media Servers • Application Servers and Media Servers • Possible, But Not Likely, to Expose Network Services to End Users SIP/SIPPING Interim Meeting

  8. Examples of Network Service SIP Request-URIs • Play an Announcement sip:annc@ms.provider.net;play=\http%3f//fs.provider.net/vacant-subscriber.g711 • Join Leg to a Mixer (Conference) sip:conf=asj4040j@ms.provider.net • Start an IVR Session (MSCML) sip:ivr@ms.provider.net • Start a Script sip:annc@ms.provider.net;voicexml=\http%3f//as.provider.net/prepaid.vxml SIP/SIPPING Interim Meeting

  9. Requirements for Application Services • Scheme Cannot Constrain Existing Services • Scheme Cannot Constrain New Services • Scheme Cannot Constrain Clients • Scheme Cannot Constrain Servers • Scheme Must Allow for User Defined Services (draft-campbell-pub-bind-reqs-00) • Scheme Must Allow for Interoperability • Mapping to Service Must Happen “In Human Time” (300ms – 500ms) SIP/SIPPING Interim Meeting

  10. Requirements for Network Services • Applications Must Be Able to Address Services • Services Must Be REGISTER-Friendly • Network Must Be Able to Proxy Services • Mapping to Service Must Happen “In Machine Time” (1ms – 20ms) • Often Part of Multiple Interactions With User • User Expects “Responsive Service” • Cannot Have Many Round-Trips SIP/SIPPING Interim Meeting

  11. Offering • Applications (Application Services) Have Different Requirements Than Network Services Is There Consensus On This Point? SIP/SIPPING Interim Meeting

  12. Proposal: Application Services • Naming Services Is The Name Binding Problem • End User / Proxy / Application Needs to Direct Call to Application Service Entity • Many Ways to Address Application Service Entity • No Single “Right Way”, As In History Discussion • Problem Is Bigger Than SIP • Appropriate Technologies May Be Service Registries, etc. • Considering It For My PhD Topic… SIP/SIPPING Interim Meeting

  13. Proposal: Network Services • Extremely Limited Vocabulary of Network Services • Dipping Into Service Registry Impacts Ability To Meet Lookup Constraint • Must Have Single Mapping For Interoperation • Use Fixed Service Indicators (LHS) SIP/SIPPING Interim Meeting

  14. Discussion SIP/SIPPING Interim Meeting

More Related