IEEE Open Arch 2000 Tel Aviv Israel Lightweight

IEEE Open. Arch 2000 Tel Aviv, Israel Lightweight Policing & Charging for Packet Networks Bob Briscoe Uni College London & BT Research Mike Rizzo, Jérôme Tassel, Kostas Damianakis BT Research 27 Mar 2000 diffchar

context engineering principles implications summary context 4 multi-service, multicast, connectionless 4 can be flowless • simple open 4 no PSTN billing to rely on 4 generalised technology allows many specific business models • not trying to find best pricing algorithm 4 bandwidth will be dirt cheap, but there’ll be hell of a lot of dirt 27 Mar 2000 diffchar 2

context engineering principles implications summary against the flat rate trend 4 eat all you can extranet 50% 2001 capacity utilisation 4 all you can eat 27 Mar 2000 t diffchar 3

context engineering principles implications summary too cheap to meter? 4 if not ‘all you can eat’ dilemma – single multiservice network reduces overheads • need empty queues for real-time multimedia • elastic data always fills queues 4 cost of charging granularity mismatch • service: packet • charges: SLA / subscription / reservation 4 low utilisation again incentive for • customer to waste resources (e. g. robots) • provider to over-book resources 4 but worse: • complexity of customer state in network 27 Mar 2000 diffchar 4

diffchar engineering 27 Mar 2000 diffchar

context engineering principles implications summary active tariff distribution to customers load Internet multicast tariff marketing or network mgmt 27 Mar 2000 diffchar 6

context engineering principles implications summary demo - tariff dissemination Mike Rizzo 4 multicast • signed tariff object 2 4 on rcvr join or sndr update – modified class loader 4 3 1 • listens for object arrival • stops current tariff object • loads new tariff object 4 on sndr invoke method • reified, dereified then invoked 27 Mar 2000 diffchar 7

context engineering principles implications summary self-billing - ‘pay and display’ customer premises or storage servic Internet data path 0 2 7 8 27 Mar 2000 £ diffchar 9

context engineering principles implications summary self-billing - ‘traffic warden random sample Internet 0 2 7 8 £ evidence 27 Mar 2000 customer premises diffchar 10

customer Identity control Pac Payment VP Policing Rating Po Accounting Measurement Ctrl Measurement Access ctrl 2000 27 Mar provider I Rac control payment reconcile Pap Po VP Rap Po Actp Actc MCc host network feedback MCc Mc Mp service provision diffchar Acs Mb account sharing 11

context engineering principles implications summary demo: accounting & payment Jérôme Tassel 27 Mar 2000 diffchar 12

context engineering principles implications summary demo: price controlled Qo. S Kostas Damianakis app active tariff 27 Mar 2000 non- diffchar functional Qo. S ctrl stack 13

context engineering principles implications summary recursive - inter-provider charging Internet service provider Internet access provider corporate 27 Mar 2000 £ diffchar 14

diffchar architectural principles 27 Mar 2000 diffchar

context engineering principles implications summary commercial openness via separation charging infrastructure tariff for traffic class x? see channel y bulk usage stats RSVP tariffs? see 224. 1. 2. 3 transmission infrastructure 27 Mar 2000 diffchar 16

context engineering principles implications summary opening the comms business end-system applic’n e-commerce present’n applic’n present’n session e-commerce session transport e-commerce router network link e-commerce physical 27 Mar 2000 link e-commerce physical diffchar physical minimise then synthesise 17

context engineering principles implications summary minimise: split-edge pricing Nd Ne Nd 4 Nb 4 Wbas Wabr Na 27 Mar 2000 4 price in & out 4 4 Wbar Wabs Nc Nc diffchar 4 separately each price between boundary and remote edge price effects localised contracts localised global standards unnecessary extends edge-pricing [Shenker 96] 18

context engineering principles implications summary synthesised end-to-end pricing data flow service price end-to-end pricing role 27 Mar 2000 diffchar 19

context engineering principles implications summary synthesised adm’n control at source client full! service a) traditional admission control b) price announcements service client The price algorithm client 27 Mar 2000 client raise price c) active tariff service diffchar 20

context engineering principles implications summary sythesised stable pricing price spot 27 Mar 2000 diffchar time 22

context engineering principles implications summary minimise: optimistic access control 1 ? customer 4 single blocking credit test 4 subsequent parallel meters 27 Mar 2000 3 2 ? ? service diffchar 23

diffchar implications 27 Mar 2000 diffchar

context engineering principles implications summary customer state in the network domain’s customer policies (PDP) PEP = policy enforcement point PDP = policy decision point per-customer policy creation PEP data 3 schedule 2 police 1 classify router 27 Mar 2000 diffchar best effort 27

context engineering principles implications summary self-policing domain pricing policy price ECN long term monitoring 3 schedule 1 police 2 classify router 27 Mar 2000 diffchar best effort 28

diffchar summary 27 Mar 2000 diffchar

context engineering principles implications summary limitations / further work 4 reliability of end customer OS 4 ongoing work • user acceptance of dynamic pricing • user acceptance of dynamic provider code • hogging? 27 Mar 2000 diffchar 30

context engineering principles implications summary contributions (each independent) 4 provider flexibility • cheap generalised packet charging systems • charging for quality, multicast, mobile 4 fine-grained market- not provider-control • complete exposure of price algorithm • market control guaranteed serendipitous service 8 SLA guaranteed refund, no serendipity 4 admission control, policing & charging removed from network • commercial not just technical openness • synthesis of business models from fine grains 27 Mar 2000 diffchar 31

context engineering principles implications summary further information 4 details ]http: //www. labs. bt. com/projects/mware/ but, may not appear for some time - see. . . 4 Bob Briscoe ]http: //www. labs. bt. com/people/briscorj/ 27 Mar 2000 diffchar 32