Automatically adapting a user interface

US9898534B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9898534-B2
Application numberUS-86575407-A
CountryUS
Kind codeB2
Filing dateOct 2, 2007
Priority dateOct 2, 2006
Publication dateFeb 20, 2018
Grant dateFeb 20, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A portal server comprises memory, a profile manager, a profile selector, and a profile initiator. The profile manager is configured to manage a plurality of profile records in a profile database. The profile selector is configured to select at least one of the plurality of profile records based on context data collected at a client and context data collected at the portal server. The collected context data corresponds to particular user interaction activity with the portal server. The profile initiator is configured to adapt a user interface based on the profile selected by the profile selector.

First claim

Opening claim text (preview).

What is claimed is: 1. A method performed at a portal server, the method comprising: receiving an incoming request from a client for a user interaction with the portal server; maintaining a plurality of profile records for adapting a user interface of the portal server for at least one usage condition associated with the user interaction; collecting collected context data based, at least in part, on client-side context data from the client and server-side context data from the portal server; calculating a plurality of correspondence values for the plurality of profile records, each correspondence value representing a weighted comparison between the collected context data and profile attributes associated with each profile record, wherein the weighted comparison is calculated using different weighting factors for each profile attribute; determining a set of currently available contacts for a user of the user interface based, at least in part, on the client-side context data; selecting a profile record from among the plurality of profile records based, at least in part, on the plurality of correspondence values and further based, at least in part, on a quantity of business contacts in the set of currently available contacts or a quantity of personal contacts in the set of currently available contacts; and adapting the user interface of the portal server to the at least one usage condition based, at least in part, on the profile record. 2. The method of claim 1 , further comprising: determining the server-side context data for the user interaction based on at least one of the incoming request, portal usage history, navigational position of a user, and currently available contacts of the user; and receiving, at the portal server, the client-side context data from the client, wherein the client-side context data is based, at least in part, on a status of desktop applications of a user environment at the client. 3. The method of claim 1 , wherein the collected context data comprises at least one of date, time, time zone, geographic location, regional settings, IP-address, type of client device, markup language, currently selected user profile, a set of currently available contacts, available tasks, performed actions, navigational position, and last visited page. 4. The method of claim 1 , wherein calculating the plurality of correspondence values comprises, for each correspondence value, comparing multiple profile attributes of a profile record with the collected context data and calculating a weighted sum of comparison results. 5. The method of claim 1 , wherein the profile record comprises a profile identifier and at least one profile attribute value for a first profile attribute, wherein a first weighting factor for the first profile attribute is different from a second weighting factor for a second profile attribute. 6. The method of claim 1 , wherein adapting the user interface comprises: triggering instantiation handlers based, at least in part, on control information in the profile record, wherein the instantiation handlers adapt the user interface of the portal server to the at least one usage condition by configuring one or more of theme, default skin, available content, selected content, navigation structure, available contacts, business process filtering, current instant messaging status, page layout, available portlets, page meta data for influencing portlet content, contents of personal document folder, bookmarks, favorites, user preferences, and visible virtual team rooms. 7. A non-transitory machine-readable medium having stored therein a program product, which when executed on a set of one or more processors of a portal server, causes the set of one or more processors to perform operations that comprise: receiving an incoming request from a client for a user interaction with the portal server; maintaining a plurality of profile records for adapting a user interface of the portal server for at least one usage condition associated with the user interaction; collecting collected context data based, at least in part, on client-side context data from the client and server-side context data from the portal server; calculating a plurality of correspondence values for the plurality of profile records, each correspondence value representing a weighted comparison between the collected context data and profile attributes associated with each profile record, wherein the weighted comparison is calculated using different weighting factors for each profile attribute; determining a set of currently available contacts for a user of the user interface based, at least in part, on the client-side context data; selecting a profile record from among the plurality of profile records based, at least in part, on the plurality of correspondence values and further based, at least in part, on a quantity of business contacts in the set of currently available contacts or a quantity of personal contacts in the set of currently available contacts; and adapting the user interface of the portal server to the at least one usage condition based, at least in part, on the profile record. 8. The non-transitory machine-readable medium of claim 7 , wherein the program product causes the set of one or more processors to perform operations that comprise: determining the server-side context data for the user interaction based on at least one of the incoming request, portal usage history, navigational position of a user, and currently available contacts of the user; and receiving, at the portal server, the client-side context data from the client, wherein the client-side context data is based, at least in part, on a status of desktop applications of a user environment at the client. 9. The non-transitory machine-readable medium of claim 8 wherein the collected context data comprises at least one of date, time, time zone, geographic location, regional settings, IP-address, type of client device, markup language, currently selected user profile, a set of currently available contacts, available tasks, performed actions, navigational position, and last visited page. 10. The non-transitory machine-readable medium of claim 8 , wherein said operation of calculating the plurality of correspondence values comprises, for each correspondence value, comparing multiple data elements of a profile record with the collected context data and calculating a weighted sum of comparison results. 11. The non-transitory machine-readable medium of claim 7 , wherein the profile record comprises a profile identifier and at least one profile attribute value for a first profile attribute, wherein a first weighting factor for the first profile attribute is different from a second weighting factor for a second profile attribute. 12. The non-transitory machine-readable medium of claim 7 , wherein said operation of adapting the user interface comprises: triggering instantiation handlers based, at least in part, on control information in the profile record, wherein the instantiation handlers adapt the user interface of the portal server to the at least one usage condition by configuring one or more of theme, default skin, available content, selected content, navigation structure, available contacts, business process filtering, current instant messaging status, page layout, available portlets, page meta data for influencing portlet content, contents of personal document folder, bookmarks, favorites, user preferences, and visible virtual team rooms. 13. The non-transitory machine-readable medium of claim 7 , wherein the operations further comprise: indicating the plurality of profile records available to a user

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9898534B2 cover?
A portal server comprises memory, a profile manager, a profile selector, and a profile initiator. The profile manager is configured to manage a plurality of profile records in a profile database. The profile selector is configured to select at least one of the plurality of profile records based on context data collected at a client and context data collected at the portal server. The collected …
Who is the assignee on this patent?
Liesche Stefan, Nauerz Andreas, Schmitt Stefan, and 2 more
What technology area does this patent fall under?
Primary CPC classification G06F16/9535. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Feb 20 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).