Date post: | 05-Jan-2016 |
Category: |
Documents |
Upload: | lesley-parker |
View: | 212 times |
Download: | 0 times |
The Direction of Value Flow in Multi-service Connectionless Networks
Bob Briscoe
BT Research
7 Oct 1999
7 Oct 1999 Direction of Value 3
context pricing clearing scenarios summary
why think about this?
theory of the value of communications: – connection-oriented hegemony
[ITU96, Zull97, Clark96, MacKie-Var92]
confusion is abroad in the world– junk advertising, bundling content+network
why assume multicast sender pays? alternative proposal seems obvious
– but wasn't when I started
context
7 Oct 1999 Direction of Value 4
context pricing clearing scenarios summary
context
multiservice, multicast IP (real-time apps) some services usage-charged, whether
packet, flow or even longer term granularity electronic tariff announcement buyer's market designed for bundling
– will cover in a future paper...
context
7 Oct 1999 Direction of Value 5
context pricing clearing scenarios summary
what business?
link (wholesale cost) network connection? (not supplied)
applic’n
present’n
session
transport
network
link
physical
network
link
physical
end-system
router network
link
physical
applic’n
present’n
session
transport
network
link
physical
context
e-commerce
7 Oct 1999 Direction of Value 6
context pricing clearing scenarios summary
the value of place
xmt value /leg = (value of place/time) but competition cost+ margin pricing who can know the value of place?
N: providerY: end-users apportionment
clearing grows comms market
ii
value1 = f(i, place1 , time1 )
value2 = f(i, place2 , time2 )
icontext
7 Oct 1999 Direction of Value 9
context pricing clearing scenarios summary
end to end pricing
end-to-end pricing role
price
service
data flow
pricing
7 Oct 1999 Direction of Value 11
context pricing clearing scenarios summary
end-to-end pricing role
not necessarily a business; a role taken by:– one ISP– the customer– a third party (+ bundling content?)
but…...what is the best default apportionment?...
pricing
7 Oct 1999 Direction of Value 12
context pricing clearing scenarios summary
default value apportionment proposal:
– 'sender and receiver both charged'– slight discrepancy in prices possible– every leg of every flow is part charged twice– model self-similar for inter-domain boundaries
pricing
7 Oct 1999 Direction of Value 13
context pricing clearing scenarios summary
split-edge pricing - per direction price in & out
separately each price
between boundary and remote edge
price effects localised
contracts localised
extendsedge-pricing [Shenker96]
Na
Nb
Nc
Nc
NdNdNe
WbasWabr
Wabs
Wbar
pricing
7 Oct 1999 Direction of Value 14
context pricing clearing scenarios summary
split edge pricing - per class
each class of service has a market
class mismatch effects localised
pricing
7 Oct 1999 Direction of Value 15
context pricing clearing scenarios summary
split-edge pricing - per leg
VVQQuu
QQtt
QQuu
QQuu
QQvv
QQww
QQww
Na
Nb
Nc
Nc
NdNdNe
Wabr
Wbas
Wabs
Wbar
multicast & heterogeneous QoS
pricing
7 Oct 1999 Direction of Value 17
context pricing clearing scenarios summary
default value apportionment choose default to minimise clearing 'only senders' or 'only receivers' charged
halve transaction volume require industry-wide co-operation unstable - mavericks gain and increase costs of all multicast requires trusted receiver count
'sender and receiver both charged'majority of comms between consenting partiesvalue, charge and cost congruentstable against maverick policies doesn't match blame for transmission...
pricing
7 Oct 1999 Direction of Value 18
context pricing clearing scenarios summary
blame, liability and control
but…...sender always to blame for a transmission
request-reply is irrelevant to network layer other confusions clarified:
• value of moving info transitory
• value of moving GBs is often for a few bits
• cost of xmt << cost of targeting what to xmt
clearing
7 Oct 1999 Direction of Value 19
context pricing clearing scenarios summary
dilemma & solution
'sender and receiver both charged' vs. 'sender to blame'
receiver customarily pays...but...
sender liable cf. postage stamp
• sender customarily pays, but receiver liable
clearing
7 Oct 1999 Direction of Value 21
context pricing clearing scenarios summary
clearing across edge providersthird party
100
51
55
49
clearing
2
37
46
44
service
money
clearing
7 Oct 1999 Direction of Value 22
context pricing clearing scenarios summary
clearing across edge providersiterative
37
46
44
10051
44
service
money
54
clearing
7 Oct 1999 Direction of Value 23
context pricing clearing scenarios summary
end-to-end model: justification avoids Int'l Accounting Rate System flaws:
muddling wholesale with clearing per-flow metering in backbone trusted end counting for multicast apportionment needs authentication
therefore unaggregateable acd+1 prices in system 6e26
clearing
c 20,000
d 5
a = apportionment schemes per ISP 10
a = apportionment schemes per ISP 10
7 Oct 1999 Direction of Value 24
context pricing clearing scenarios summary
end-to-end model: justification II
localised contract• jurisdiction clear
• what to meter decided locally
selective openness of clearing process ac2 prices problem still exists 4e9
clearing
7 Oct 1999 Direction of Value 27
context pricing clearing scenarios summary
scenarios
see paper for...
finding an end-to-end price sender liable but local payment customary inter-domain multicast with heterogeneous
quality of service (QoS) phone to Internet gateway (PIG)
...ie. per session accounting
scenarios
7 Oct 1999 Direction of Value 28
context pricing clearing scenarios summary
PIG - phone to Internet gatewaysservice
moneyInternetend-end
PSTNiterative
13
21
24 21
100
41
55
59
2
37
3629
25clearing
PIG
scenarios
7 Oct 1999 Direction of Value 29
context pricing clearing scenarios summary
alternative now seems obvious... per-session accounting bill=anachronism split-edge pricing scales infinitely 'sender and receiver both charged' stable
– customary - but only sender liable to pay end-to-end pricing and clearing efficient
end-to-end intermediary could take 0-50% of retail ISP and telco markets– ...and their customer relationships
summary
7 Oct 1999 Direction of Value 30
context pricing clearing scenarios summary
further information
Differential charging (diffchar) projecthttp://www.labs.bt.com/projects/mware/
Bob Briscoehttp://www.labs.bt.com/people/briscorj/
more info