1. 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 IEEE OpenArch 2000 Tel Aviv, Israel

2. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar2 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

3. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar3 4 all you can eat 4 eat all you can against the flat rate trend context 2001 50% extranet t capacity utilisation

4. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar4 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 context

5. diffchar engineering

6. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar6 active tariff distribution to customers Internet multicast marketing or network mgmt tariff load engineering

7. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar7 demo - tariff dissemination 4 multicast signed tariff object 4 on rcvr join or sndr update –modified class loader listens for object arrival stops current tariff object loads new tariff object 4 on sndr invoke method reified, dereified then invoked 4 2 13 Mike Rizzo engineering

8. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar8 demo - tariff dissemination Mike Rizzo engineering

9. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar9 self-billing - ‘pay and display’ 027 8 £ Internet customer premises or storage service data path engineering

10. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar10 self-billing - ‘traffic warden 027 8 £ Internet random sample customer premises evidence engineering

11. VP control VP provider account sharing customer Identity Payment PolicingRatingAccounting Measure- ment Ctrl Measure- ment Access ctrl I network service provision control MbMb feedbackhost Acs Po reconcile payment Po Act c McMc Pa c MC c Ra c MpMp MC c Act p Pa p Ra p

12. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar12 demo: accounting & payment Jérôme Tassel engineering

13. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar13 demo: price controlled QoS Kostas Damianakis app QoS ctrl stack active tariff non- functional engineering

14. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar14 recursive - inter-provider charging Internet access provider Internet service provider corporate £ engineering

15. diffchar architectural principles

16. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar16 commercial openness via separation transmission infrastructure charging infrastructure tariff for traffic class x? see channel y RSVP tariffs? see 224.1.2.3 bulk usage stats principles

17. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar17 opening the comms business 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 e-commerce minimise then synthesise e-commerce principles

18. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar18 minimise: split-edge pricing NaNa NbNb NcNc NcNc NdNd NdNd NeNe W bas W abr W abs W bar 4 price in & out separately 4 each price between boundary and remote edge 4 price effects localised 4 contracts localised 4 global standards unnecessary 4 extends edge-pricing [Shenker96] 4 price in & out separately 4 each price between boundary and remote edge 4 price effects localised 4 contracts localised 4 global standards unnecessary 4 extends edge-pricing [Shenker96] principles

19. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar19 synthesised end-to-end pricing end-to-end pricing role price service data flow principles

20. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar20 synthesised adm’n control at source a) traditional admission control service full! client full! b) price announcements service raise price client c) active tariff service The price algorithm client principles

21. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar21 admission control is a delusion 4 probability of session blocking with CAC = probability of packet block without CAC 4 control session admission  improve intra-session utility  reduce inter-session utility 4 just moving the problem 4 mechanism to allow user to choose principles

22. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar22 sythesised stable pricing time price spot principles

23. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar23 minimise: optimistic access control service ? customer 1 2 ? 4 single blocking credit test 4 subsequent parallel meters principles ? 3

24. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar24 + ‘engaged tone’ if cost too high admission control synthesis by provider or gateway Internet access provider Internet service provider principles

25. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar25 generalisations general pre-pay + credit pay as you go pay as you fancy raise price or fine spot + stability price usage-charging modular SDP bundling specific post-pay batch payment regular billing deny logical service stable price policing SLA or RESV retail bundling principles

26. diffchar implications

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

28. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar28 router self-policing police 1 price classify schedule 2 3 best effort domain pricing policy long term monitoring ECN implications

29. diffchar summary

30. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar30 limitations / further work 4 reliability of end customer OS 4 ongoing work user acceptance of dynamic pricing user acceptance of dynamic provider code hogging? summary

31. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar31 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 8SLA  guaranteed refund, no serendipity 4 admission control, policing & charging removed from network  commercial not just technical openness synthesis of business models from fine grains summary

32. contextengineeringprinciplesimplicationssummary 27 Mar 2000diffchar32 further information 4 details  http://www.labs.bt.com/projects/mware/ but, may not appear for some time - see... http://www.labs.bt.com/projects/mware/ 4 Bob Briscoe  http://www.labs.bt.com/people/briscorj/ http://www.labs.bt.com/people/briscorj/ summary