Personalisation through the use of personal profile

Transcription

1 Personalisation through the use of personal profile Alf Sollund, Telenor IST project eperspace N

2 IST project eperspace N

3 Outline Introduction Personalisation Personal profile Architecture allowing personalisation through personal profile Conclusion and challenges IST project eperspace N

4 Personalisation definitions A set of techniques used for presenting information and services differently to different users to meet their individual needs Using information either previously obtained or provided in realtime More convenience, lower cost, or some other benefit for users Explicit personalisation Rudimentary mechanism (use of forms). Reliable, but weak on end user acceptance Also the user must know beforehand the content Success of story: interest Amazon Implicit personalisation Observable behaviour patterns, user preferences from indirect sources Inference methods based on the user s behaviour Customisation Manual change of look and feel of interface Success story: mobile phone ring-tones Explicit user driven customisation versus content or service driven personalisation IST project eperspace N

5 Personal Profile Personalised TV channel How does system know Ians preferences? Data captured in a personal profile IST project eperspace N

6 Personal Profile A set of data that contains information representing who the user entity is, and its behaviour and preferences. High level classification of user model components: Preferences (dislike Rap music) Knowledge (knows where Oslo court is located) Goals (actions) (Wants to search for Another brick in the wall ) Attribute (was born in 1962) Questions: Structure Metadata? Each service its own profile? The real world; actors and technologies to consider (standardisation fora and consortiums) 3GPP/GUP, Liberty Alliance (Federated Id), ETSI, MS Passport, OMA/UaProf, MPEG,... IST project eperspace N

7 Introduction bigger picture Traditionally Internet term Personalisation: Automated WEB tracking -> offer services/ content according to user perceived preferences (Customisation: manual by user) Personal profile: collection of data with a set of user interests based on end user behaviour in WWW by agents ( cyberspace), e.g Amazon One-to-one marketing eperspace Also taking into account the ambient surrounding the user and his context (ubiquity) Terminal capabilities, location. Availability, presence Personal profile: collection of data modelling the user including context Personalisation a service in its own! Service; not (just) a function, but a function performed by one on behalf of another entity at a cost IST project eperspace N

8 Personal Profile Different TV providers at Home and at hotel How to ensure that the same preferences are used? E.g. access to profile IST project eperspace N

9 Profile distribution Today: each service / content provider hosting own profile Tomorrow: eperspace as a Personalisation profile provider service / content providers using instances of same profile Distributed profile Access mechanisms E.g. end user having more control Personal profile: data needed by services/applications to be personalized. Who the user are, Current context, Personal preferences, Personal interests E.g. a model of user IST project eperspace N

10 Structure of the User Profile (At least) one profile per user Access control for profile and subparts of the profile Defines read, write and update rights Reuse of industry accepted metadata schemas Profile are not as such service specific, e.g. service management data held in service platform USER_PROFILE is an XML schema document defined by WP5 SERVICE_PROFILE is an XML schema document which contains relevant service dependent information in order to use the service IST project eperspace N

11 User Interests: 2 different approaches Why we chose multiple categorizations: One single categorization Because of the Interest possibility regardless of reusing of industry the accepted type of metadata content/service that the service developers are already familiar with and already using for their developments Pros: Easier for the user to register his/her interests. Cons: Capturing requirements from Service Match Providers. towards SP existing content structure Catalogue? of Interests for tailoring If a Service services. Provider is allowed to update a user interest, Captured it might during end up Service affecting registration, a whole range update of services through that Service use the Usage same interest. Might not Also provide Integrates enough industry detail for some accepted types of metadata services. (NewsML, TV-Anytime) Multiple categorization according to services: (News, TV, Music Service, Books) Pros: Different types of interests for different types of services (User Interests are not service specific, we don t support that, but at least service-type specific) Reuse of industry accepted metadata. Cons: Update mechanism to propagate the changes from one categorization standard to the other IST project eperspace N

12 Context Information Anind Dey: any information that can be used to characterise the situation of an entity References to Location and Presence Providers. Holds address to call the appropriate methods to provision Location and Presence. Also holds the Information about the current terminal. IST project eperspace N

13 Service provider usage of personal profile Device Service UpdateProfile UpdateProfile updateprofile UpdateProfile Service Manager (GSeM) API (SPoE) ProfileData ProfileData Service Registration ProfileData CSP UpdateProfileEvent 7. Personalised service Subscription Authenticated 1. Request personalised service through CSP application 2. GSeM will assign a role to the calling service 3. GSeM forwards the request to the SPOE [service s role, userid]. 6. PE returns XML string, e.g. part of profile (node) to application. 4. SPOE contacts correct Personalization Engine [service s role, userid]. profile Personalisation Engine 5. PE: Check Access rights, query/update the UserProfile. Reachability Presence Service Reachability Service Presence DataAvailable / Not Available athome / elsewhere Location Service UpdatePresence Environment UpdateLocation IST project eperspace N

14 eperspace in the big picture Standardisation / industry alliances; eperspace World Wide Web Consortium (W3C): Device capabilities CC/PP (XML-RDF) OMA / Wireless Village (old WAP): UAProf: Device profile (repository) and pointer in personal profile.. 3GPP (3rd Generation Partnership Project): GUP and LoCation Services (LCS) and Presence; General architecture master/slave copy of profile. ETSI STF 265: User Profile Management (e-inclusion); Guidelines for personal profile; Cooperation and incorporation of recommendations Liberty Alliance: Identity Federation Framework (ID-FF)- SSO; Id schema for ID part of profile (ID-SIS). And reuse of industry accepted metadata (TV-Anytime, IPTC,...) Timeline? eperspace: worldwide dominance within 2008 Test beds and pilots from 2006 (Telefonica) IST project eperspace N

15 Challenges and conclusion Service provisioning How to deploy (Personalisation Engines)? Service content providers conflict managment Management; Initiate and input data to profiles How to Initially offer a profile E.g. through service subscription (interests) Automatic profile update mechanisms More than one Personalisation Engine/Profile per user Balanced with end user control/privacy Solutions closely related to business models and roles Personalisation provider, Identity provider Personalisation through access to profile Single Point of Entry / Personalisation Engine s Profile Common set of criteria, flexible and matching SP s demands Shared by different service providers IST project eperspace N

16 Thank you! Questions? IST project eperspace N

17 Backup IST project eperspace N

18 Personalisation Context and Presence Anind Dey: any information that can be used to characterise the situation of an entity, where an entity can be a person, place, physical or computational object Environment (surroundings; temperature, humidity) Communication Device Access channel Personal: Physiological (pulse, blood pressure) Mental (mood) Social (friends, co-workers) Spatio-temperal (time, location) Presence The use of technology to establish a sense of shared presence or shared space among geographically separated members of a group IST project eperspace N

19 Single Point Of Entry Abstracts the location of the User profiles. Facade pattern which provides a unified interface to a set of interfaces in the subsystem Other components only care to know where public personalisation API is (SPOE). Ask more than one personalization engine (group request on multiple PE s) SPOE Internal Description SPOE store the link between an identity (a userid) and a Personalization Engine Personalisation Architecture Personalisation data found in various repositories and distributed through different domains All the access to the user profile are done through eperspace global service management <<access>> Personalization engine Reachability Public Interface Personalization Service Single Point of Entry Personal profile presence In the future, we can imagine to have more than one personalization engine per user e.g. one Personalization Engine per identity (a user can have several identity) IST project eperspace N Security Location

20 User Interest Important to capture requirements from Service Providers. Catalogue of Interests for tailoring services. Captured during Service registration, update through Service Usage Also Integrates industry accepted metadata (NewsML, TV-Anytime) IST project eperspace N

21 Terminal Profile Terminal manager UaProf repository: Information in UaProf are device specific, not end user specific Holds information about the terminals the user owns/has used IST project eperspace N

22 Access control in different parts of the profile Globally: Precondition: User subscribed, e.g. created specific access rights to each SP Mapping for roles/services is stored in the service platform (RBAC) 3 basic roles: owner, trusted and nontrusted Service s role and the userid passed as parameters to Access control Profile: Each basic part of the profile defines read, write and update rights for each role. This can be overwritten by some sub-parts of the profile (inheritance of RBAC). User profile is newly created: Only the owner role will have permission to perform every operation IST project eperspace N

23 Personalisation Engine A personal agent system for integrating a variety of information management services and a set of personal agents, which locate and filter information for the users Public Personalisation API Personalisation SPOE Security Personalisation Engine Provides: Access control Update of profile "Generic API for Single User/ Group of Users "Helper API for single user / group of users, with helper methods to access/update well know parts of the profile Synchronisation of profile Rules engine with actions IST project eperspace N

24 Personalisation Engine Introducing more centralised (global) intelligence "Service discovery based on user profile "Update and synchronisation of the user profile "Notification of new services based on user profile (e.g. push) "Explicit feedback mechanisms for user preferences "Monitoring user behaviour "Generic rules engine with actions "Broker (theoretical approach) IST project eperspace N Negotiating with other

25 Listeners - Synchronization of the Profile Service Providers hold a slave copy of the User Profile in their storage (following a GUP model). Allowing them to perform quick personalization of a service. Sections of the profile include "Listeners". SPs register an interest in a part of the profile and are notified of update. Notification done through the entry point specified in the URL tag. Service Providers query profile with standard management mechanisms IST project eperspace N

26 Identity Attribute: (UserId). Some user information can be imported from GSeM database (information gathered when user subscribed to the eperspace system) Based on Liberty Alliance ID-SIS Personal Profile Service management holds Global Id of user work, home, vacation IST project eperspace N

27 Information part of the Profile For Home data indexing scenarios: when user wants to access/search personal files/info held at home s digital storage outside the HAN. MyPhotos has a developed schema. Other approaches include IPTC description of digital content. IST project eperspace N

28 Personalisation deployment example IST project eperspace N

29 Personalisation Engine future work To include sets of rules in the Profile (Preferences part) and a rules engine to process actions in the Personalization Engine; to introducemore intelligence and automation in the system. Context switching, Profile switching. The User can have more than one profile and switch between them according to context. Profile Version Control and rollback; In the future if the user detects a strange behaviour in the usage of his services due to some automatic update of interests (or other profile information), he/she will be able to trace the changes and reverse them if desired. IST project eperspace N

30 Update of Interests IST project eperspace N

31 REGISTRATION OF A NEW TERMINAL IST project eperspace N

32 Synchronization of the Profile copies Service Providers hold a slave copy of the User Profile in their storage (following a GUP model) This allows them to perform quick personalization of a service (e.g: content adaptation for News) without requesting the User Profile every time. A Synchronization mechanism is required! IST project eperspace N

33 IST project eperspace N