1 / 38

Negotiating Exchanges of Private Information for Web Service Eligibility

This paper explores a negotiating service that informs users of the benefits they will receive in exchange for divulging personal information, with a focus on business policies expressed as rules. It presents an implementation based on Web Services architecture.

lolaf
Download Presentation

Negotiating Exchanges of Private Information for Web Service Eligibility

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. Negotiating Exchanges of Private Information for Web Service Eligibility Keping Jia & Bruce Spencer

  2. Outline • Introduction • Demo • Architecture overview • Conclusion

  3. Introduction • Currently and more so in the future, users are asked to divulge increasingly specialized information in exchange for higher levels of services in the electronic market, e.g. credit card company. • On the other hand, people are becoming more cautious in providing the personal information on the Web because of many obvious side effects, e.g. spam. • In fact, exchanging private information has become one currency of e-commerce that greatly affects the online businesses.

  4. Introduction • But the customer may be willing to divulge a private fact if they are informed exactly what it buys – what new, better service is guaranteed to be provided based on communicating that specific fact. • We envision that, by providing a negotiating service that tells people what they will get in exchange for divulging personal information, the customers will be more willing and more comfortable to offer their private information.

  5. Introduction • This paper will give an implementation of negotiating service that is based on the assumption that the levels of services are governed by the business policies or conventions that can be expressed by rules. • This negotiating service is built under the Web Services architecture.

  6. Policy Examples and their rule format • An elite customer can get 5% discount on decent or better cars if his payment type is “silver”. discount(X,Y,'5%')←eliteCustomer(X), decentCarOrAbove(Y), paymentType(silver). • “Silver” payment type is pay by 2 year installments with financial assistance of less than $10000. paymentType(silver)←payBy(‘2yearInstallment’), financialAssistance(lessThan$10000). • “Silver” payment type is pay by 3 year installments with financial assistance of less than $7000. paymentType(silver)←payBy(‘3yearInstallment’), financialAssistance(lessThan$7000).

  7. “Silver” payment type is pay by 5 year installments without financial assistance. paymentType(silver)←payBy(‘5yearInstallment’), financialAssistance($0). • The preferred customer who is insurance affiliated automatically becomes an elite customer. eliteCustomer(X)←preferedCustomer(X), insuranceAffiliator(X). • The customer who is older than 60 is the senior customer. senior(X)←moreThan60YearsOld(X).

  8. The customer who buys car insurance in First Rate Co. is insurance affiliated. insuranceAffiliator(P)←driverLicenceNo(P, X), insuredAt(‘First Rate Co.’, X).

  9. Demo Nancy discount(‘Nancy','Acura 3.5RL','5%')?

  10. Nancy I won’t tell you.

  11. Nancy I won’t tell you.

  12. Nancy

  13. Nancy Why cannot I get 5% discount on Acura 3.5RL?

  14. Nancy Why cannot I get 5% discount on Acura 3.5RL?

  15. Nancy

  16. Nancy

  17. Nancy

  18. Nancy

  19. Nancy

  20. Nancy

  21. Nancy

  22. Nancy

  23. Nancy

  24. Nancy

  25. Nancy

  26. Nancy

  27. Nancy

  28. Nancy

  29. Nancy

  30. Architecture Overview • Web Services Service Provider publish Bind UDDI SOAP Service Broker UDDI Service Requester Find

  31. Architecture Overview • The network of business policies and facts: • The business policies and facts of an industry are usually stored and maintained distributedly among different organizations. • A grant of a service may involve the support of policies and facts from several places. • This involvement usually takes the form of outsource the proof of some subgoals to other business rule services.

  32. Configuration rule examples • $outsource(creditChecking(Person, CreditLevel), ‘uuid:51890f8b-eac5-45fe-8aaa-59ca745f0fc3’) • $outsource(inStore(X, Amount), ‘uuid:51890f5b-ehc3-4ffe-8aeba-59ca634f0fc3’) food(X). • $outsource(inStore(X, Amount), ‘uuid:59875f8b-eac6-41fa-8aea-5945745f0fa5’) furniture(X).

  33. Dynamic bindings of business rule services

  34. The exchange of user related information • The user information agent which consists of • A repository structure to store the user related information and knowledge. • A service interface through which the user’s information can be accessed. • The interactive agent that provides a GUI interface that allows the user to exchange information with the service provider.

  35. Information given at Hand shake stage

  36. Conclusion • Formally represents business conventions and policies as rules and executes them with rule engine forms the basis of this kind of negotiation. • Rule engine proves to be effective in finding out relevant policies and the complete set of conditions on which a service request may be granted. • Implemented as web services, this negotiation protocol applies to the distributed environment as well.

  37. Questions?

More Related