URI As Service I ndicat or: Requirement s Eric W m . Burger - - PowerPoint PPT Presentation

▶
uri as service i ndicat or requirement s
SMART_READER_LITE
LIVE PREVIEW

URI As Service I ndicat or: Requirement s Eric W m . Burger - - PowerPoint PPT Presentation

Jul 09, 2023 37 likes •182 views

URI As Service I ndicat or: Requirement s Eric W m . Burger eburger@snowshore.com 6 May 2002 SIP/SIPPING Interim Meeting 1 Fundament al Quest ion Is There a Single Mechanism for Specifying Application Service Network Service

slide-1
SLIDE 1

6 May 2002 SIP/SIPPING Interim Meeting 1

URI As Service I ndicat or: Requirement s

Eric Wm. Burger eburger@snowshore.com

slide-2
SLIDE 2

6 May 2002 SIP/SIPPING Interim Meeting 2

Fundament al Quest ion

  • 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

slide-3
SLIDE 3

6 May 2002 SIP/SIPPING Interim Meeting 3

Charact erist ics of an Applicat ion Ser vice (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

slide-4
SLIDE 4

6 May 2002 SIP/SIPPING Interim Meeting 4

Charact erist ics of an Applicat ion 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

slide-5
SLIDE 5

6 May 2002 SIP/SIPPING Interim Meeting 5

Examples of Applicat ion Service SI P Request -URI s

  • 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

slide-6
SLIDE 6

6 May 2002 SIP/SIPPING Interim Meeting 6

Charact erist ics of a Net work 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

slide-7
SLIDE 7

6 May 2002 SIP/SIPPING Interim Meeting 7

Charact erist ics of a Net work 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

slide-8
SLIDE 8

6 May 2002 SIP/SIPPING Interim Meeting 8

Examples of Net work Service SI P Request -URI s

  • 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

slide-9
SLIDE 9

6 May 2002 SIP/SIPPING Interim Meeting 9

Requirement s f or Applicat ion 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)

slide-10
SLIDE 10

6 May 2002 SIP/SIPPING Interim Meeting 10

Requirement s f or Net work 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

slide-11
SLIDE 11

6 May 2002 SIP/SIPPING Interim Meeting 11

Of f ering

  • Applications (Application Services)

Have Different Requirements Than Network Services Is There Consensus On This Point?

slide-12
SLIDE 12

6 May 2002 SIP/SIPPING Interim Meeting 12

Proposal: Applicat ion 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…

slide-13
SLIDE 13

6 May 2002 SIP/SIPPING Interim Meeting 13

Proposal: Net work 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)
slide-14
SLIDE 14

6 May 2002 SIP/SIPPING Interim Meeting 14

Discussion