# US 2001/0034771 A1 · Network portal system and methods

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2001/0034771 A1
- Document ID: US20010034771A1
- Status: Published application
- Kind: A1
- Application number: 09/759,740
- Filed: 2001-01-12
- Published: 2001-10-25
- Earliest claimed: 2000-01-14
- Assignees: Sun Microsystems, Inc.
- Inventors: Matthias Hütsch; Ralf Hofmann; Kai Sommerfeld
- Web page: https://patentgrep.com/patent/US20010034771A1

## CPC

- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 40/10: Text processing (natural language analysis G06F40/20; semantic analysis G06F40/30; processing or translation of natural language G06F40/40)
- G06F 40/151: Transformation
- H04L 61/00: Network arrangements, protocols or services for addressing or naming
- H04L 61/30: Managing network names, e.g. use of aliases or nicknames (name-to-address mapping H04L61/45)
- H04L 61/35: {involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function}
- H04L 61/45: Network directories; Name-to-address mapping
- H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- H04L 67/567: Integrating service provisioning from a plurality of service providers
- H04L 67/289: Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
- H04L 67/5682: Policies or rules for updating, deleting or replacing the stored data
- H04L 69/08: Protocols for interworking; Protocol conversion
- H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L 69/329: in the application layer [OSI layer 7]
- Y10S 707/99933: Query processing, i.e. searching
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

A network portal system includes a web-top manager and a universal content broker system. The web-top manager is configured to receive a content request from a user device, where the content request includes a content provider identifier. The universal content broker system is coupled to the web-top manager. The universal content broker system includes a plurality of content providers. Each content provider in the plurality of content providers is associated with a different content provider identifier. Also, each content provider accesses content having a different raw data format. A universal content broker is coupled to the web-top manager and to the plurality of content providers. Upon the receipt of the content request from the web-top manager, the universal content broker passes the request to a content provider in the plurality of content providers that is associated with the content provider identifier.

## Claims

### Claim 1

A network portal system comprising:
a web-top manager, wherein said web-top manager is configured to receive a content request from a user device wherein said content request includes a content provider identifier; and
a universal content broker system coupled to said web-top manager, said universal content broker system comprising:
a plurality of content providers, wherein each content provider in said plurality of content providers is associated with a different content provider identifier, and each content provider accesses content having a different raw data format;
a universal content broker coupled to said web-top manager and to said plurality of content providers wherein upon said receipt of said content request from said web-top manager, said universal content broker passes said request to a content provider in said plurality of content providers that is associated with said content provider identifier.

### Claim 2 (depends on 1)

The system of claim 1 wherein said web-top manager further comprises a plurality of remote applications.

### Claim 3 (depends on 1)

The system of claim 1 wherein said web-top manager further comprises:
a web server;
a main servlet executing on said web server, wherein said main servlet receives a user device content request; and
a presentation and logic system coupled to said main servlet, and configured to receive raw data content in a plurality of different raw data formats from said universal content broker system, wherein said presentation and logic system converts raw data content irrespective of said raw data format, based upon characteristics of said user device, into a page displayable on said user device.

### Claim 4 (depends on 3)

The system of claim 3 wherein said presentation and logic system includes a plurality of templates.

### Claim 5 (depends on 4)

The system of claim 4 wherein said plurality of templates includes a first set of template sets wherein said first set of template sets is for a first type of user device page format.

### Claim 6 (depends on 5)

The system of claim 5 wherein said first set of template sets includes a set of content format template sets wherein each content format template set is for a different one of said plurality of different raw data formats.

### Claim 7 (depends on 6)

The system of claim 6 wherein said set of content format templates comprise a set of device capability specific templates.

### Claim 8 (depends on 4)

The system of claim 4 wherein said plurality of templates includes a second set of template sets wherein said second set of template sets is for a second type of user device page format.

### Claim 9 (depends on 8)

The system of claim 8 wherein said second set of template sets includes a set of content format template sets wherein each content format template set is for a different one of said plurality of different raw data formats.

### Claim 10 (depends on 9)

The system of claim 9 wherein said set of content format templates comprise a set of device capability specific templates.

### Claim 11 (depends on 3)

The system of claim 3 wherein said presentation and logic system comprises a plurality of provider objects wherein each provider object is associated with a different content provider identifier.

### Claim 12 (depends on 11)

The system of claim 11 wherein said presentation and logic system comprises a plurality of adapter objects coupled to said plurality of provider objects wherein each adapter object is associated with a different content provider identifier, and further wherein said adapter object receives content from said content provider associated with said different content provider identifier and provides said content to the provider object associated with said different content provider identifier.

### Claim 13 (depends on 3)

The system of claim 3 wherein said presentation and logic system comprises a plurality of adapter objects wherein each adapter object is associated with a different content provider identifier, and further wherein said adapter object receives content from said content provider associated with said different content provider identifier and provides said content to a provider object associated with said different content provider identifier.

### Claim 14 (depends on 3)

The system of claim 3 wherein said presentation and logic system comprises:
a profiling service.

### Claim 15 (depends on 14)

The system of claim 14 wherein said presentation and logic system comprises:
a profiling service configuration file coupled to said profiling service.

### Claim 16 (depends on 15)

The system of claim 15 wherein said profiling service configuration file includes a decision tree wherein said decision tree performs actions.

### Claim 17 (depends on 16)

The system of claim 16 wherein said decision tree is a XML decision tree.

### Claim 18 (depends on 16)

The system of claim 16 wherein said actions include an action based upon request parameters.

### Claim 19 (depends on 16)

The system of claim 16 wherein said actions include an action based upon request header parameters.

### Claim 20 (depends on 16)

The system of claim 16 wherein said actions include an action based upon user device properties.

### Claim 21 (depends on 16)

The system of claim 16 wherein said actions include an action based upon resource properties.

### Claim 22 (depends on 14)

The system of claim 14 wherein said presentation and logic system comprises a plurality of screen templates.

### Claim 23 (depends on 22)

The system of claim 22 wherein one screen template in said plurality of screen templates is a default screen template for a HTML page.

### Claim 24 (depends on 22)

The system of claim 22 wherein one screen template in said plurality of screen templates is a default screen template for a mobile telephone.

### Claim 25 (depends on 22)

The system of claim 22 wherein one screen template in said plurality of screen templates is a default screen template for a personal digital assistant.

### Claim 26 (depends on 16)

The system of claim 16 wherein said presentation and logic system comprises a plurality of screen templates.

### Claim 27 (depends on 26)

The system of claim 26 wherein one screen template in a plurality of said screen templates comprises a default screen template.

### Claim 28 (depends on 27)

The system of claim 27 wherein said default screen template includes a header region having at least one place holder and a body region having at least one place holder.

### Claim 29 (depends on 28)

The system of claim 28 wherein said action of said decision tree determines a component that is used for said at least one placeholder in said body region.

### Claim 30 (depends on 29)

The system of claim 29 wherein said component provides information that is taken from said raw data content.

### Claim 31 (depends on 1)

The system of claim 1 wherein said universal content broker system further comprises:
a registry of content providers coupled to said universal content broker wherein said universal content broker selects said content provider from said registry based upon said content provider identifier.

### Claim 32 (depends on 1)

The system of claim 1, wherein said universal content broker system includes at least one interface adapted to associate property values with content.

### Claim 33 (depends on 1)

The system of claim 1, wherein said universal content broker system includes at least one interface adapted to set a property value of content.

### Claim 34 (depends on 1)

The system of claim 1, wherein said universal content broker system includes at least one interface adapted to read a property value of content.

### Claim 35 (depends on 1)

The system of claim 1, wherein said universal content broker system includes an interface adapted to notify registered client systems when content of interest to said registered client systems is processed by said universal content broker system.

### Claim 36 (depends on 1)

The system of claim 1 wherein said universal content broker system includes an interface adapted to notify registered client systems when new content is created by said universal content broker system.

### Claim 37 (depends on 1)

The system of claim 1 wherein said universal content broker system further comprises a hierarchy content provider.

### Claim 38 (depends on 37)

The system of claim 37 wherein said hierarchy content provider generates a virtual hierarchy of content of said universal content broker system.

### Claim 39 (depends on 1)

The system of claim 1 wherein said universal content broker system further comprises a configuration server.

### Claim 40 (depends on 39)

The system of claim 39 further comprising a configuration proxy coupled to said configuration server.

### Claim 41 (depends on 40)

The system of claim 40 wherein said configuration server further comprises a first DOM tree.

### Claim 42 (depends on 41)

The system of claim 41 wherein said DOM tree includes user profiles.

### Claim 43 (depends on 41)

The system of claim 41 wherein said DOM tree includes application profiles.

### Claim 44 (depends on 40)

The system of claim 40 wherein said configuration proxy further comprises a second DOM tree wherein said second DOM tree includes a subset of data in said first DOM tree.

### Claim 45 (depends on 1)

The system of claim 1 further comprising a client system coupled to said network portal system.

### Claim 46 (depends on 45)

The system of claim 45 wherein said client system includes a client universal content broker system.

### Claim 47 (depends on 46)

The system of claim 46 wherein said client universal content broker system includes a synchronization component for synchronizing content of said client universal content broker system with content of said universal content broker system.

### Claim 48

A network portal system comprising:
a web-top manager, wherein said web-top manager is configured to receive a content request from a user device wherein said content request includes an identifier for content having a raw data format wherein said web-top manager further comprises:
a web server;
a main servlet executing on said web server, wherein said main servlet receives a user device content request; and
a presentation and logic system coupled to said main servlet, and configured to receive raw data content in a plurality of different raw data formats from said universal content broker system, wherein said presentation and logic system converts raw data content irrespective of said raw data format, based upon characteristics of said user device, into a page displayable on said user device; and
a universal content broker system coupled to said web-top manager, said universal content broker system comprising:
a plurality of content providers, wherein each content provider in said plurality of content providers is associated with a different content provider identifier, and each content provider accesses content having a different raw data format;
a hierarchy content provider; and
a universal content broker coupled to said web-top manager and to said plurality of content providers wherein upon said receipt of said content request from said web-top manager, said universal content broker passes said request to a content provider in said plurality of content providers that is associated with said content provider identifier.

### Claim 49 (depends on 48)

The system of claim 48 wherein said universal content broker system further comprises a configuration server.

### Claim 50 (depends on 48)

The system of claim 48 wherein said web-top manager further comprises:
a plurality of portlets; and
a presentation manager coupled to said plurality of portlets upon receipt of said user request, said presentation manager send said user request to one of said plurality of portlets.

### Claim 51

A system comprising:
a web server;
a main servlet executing on said web server, wherein said main servlet receives a user device content request; and
a presentation and logic system coupled to said main servlet, and configured to receive raw data content in a plurality of different raw data formats, wherein said presentation and logic system converts raw data content irrespective of said raw data format, based upon characteristics of said user device, into a page displayable on said user device.

### Claim 52 (depends on 51)

The system of claim 51 wherein said presentation and logic system includes a plurality of templates.

### Claim 53 (depends on 52)

The system of claim 52 wherein said plurality of templates includes a first set of template sets wherein said first set of template sets is for a first type of user device page format.

### Claim 54 (depends on 53)

The system of claim 53 wherein said first set of template sets includes a set of content format template sets wherein each content format template set is for a different one of said plurality of different raw data formats.

### Claim 55 (depends on 54)

The system of claim 54 wherein said set of content format templates comprise a set of device capability specific templates.

### Claim 56 (depends on 52)

The system of claim 52 wherein said plurality of templates includes a second set of template sets wherein said second set of template sets is for a second type of user device page format.

### Claim 57 (depends on 56)

The system of claim 56 wherein said second set of template sets includes a set of content format template sets wherein each content format template set is for a different one of said plurality of different raw data formats.

### Claim 58 (depends on 57)

The system of claim 57 wherein said set of content format templates comprise a set of device capability specific templates.

### Claim 59 (depends on 51)

The system of claim 51 wherein said presentation and logic system comprises a plurality of provider objects wherein each provider object is associated with a different content provider identifier.

### Claim 60 (depends on 59)

The system of claim 59 wherein said presentation and logic system comprises a plurality of adapter objects coupled to said plurality of provider objects wherein each adapter object is associated with a different content provider identifier, and further wherein said adapter object receives content associated with said different content provider identifier and provides said content to the provider object associated with said different content provider identifier.

### Claim 61 (depends on 51)

The system of claim 51 wherein said presentation and logic system comprises a plurality of adapter objects wherein each adapter object is associated with a different content provider identifier, and further wherein said adapter object receives content associated with said different content provider identifier and provides said content to a provider object associated with said different content provider identifier.

### Claim 62 (depends on 51)

The system of claim 51 wherein said presentation and logic system comprises:
a profiling service.

### Claim 63 (depends on 62)

The system of claim 62 wherein said presentation and logic system comprises:
a profiling service configuration file coupled to said profiling service.

### Claim 64 (depends on 63)

The system of claim 63 wherein said profiling service configuration file includes a decision tree wherein said decision tree performs actions.

### Claim 65 (depends on 64)

The system of claim 64 wherein said decision tree is a XML decision tree.

### Claim 66 (depends on 64)

The system of claim 64 wherein said actions include an action based upon request parameters.

### Claim 67 (depends on 64)

The system of claim 64 wherein said actions include an action based upon request header parameters.

### Claim 68 (depends on 64)

The system of claim 64 wherein said actions include an action based upon user device properties.

### Claim 69 (depends on 64)

The system of claim 64 wherein said actions include an action based upon resource properties.

### Claim 70 (depends on 64)

The system of claim 64 wherein said presentation and logic system comprises a plurality of screen templates.

### Claim 71 (depends on 70)

The system of claim 70 wherein one screen template in said plurality of screen templates is a default screen template for a HTML page.

### Claim 72 (depends on 70)

The system of claim 70 wherein one screen template in said plurality of screen templates is a default screen template for a mobile telephone.

### Claim 73 (depends on 70)

The system of claim 70 wherein one screen template in said plurality of screen templates is a default screen template for a personal device assistant.

### Claim 74 (depends on 64)

The system of claim 64 wherein said presentation and logic system comprises a plurality of screen templates.

### Claim 75 (depends on 74)

The system of claim 74 wherein one screen template in a plurality of said screen templates comprises a default screen template.

### Claim 76 (depends on 75)

The system of claim 75 wherein said default screen template includes a header region having at least one place holder and a body region having at least one place holder.

### Claim 77 (depends on 76)

The system of claim 76 wherein said action of said decision tree determines a component that is used for said at least one placeholder in said body region.

### Claim 78 (depends on 77)

The system of claim 77 wherein said component provides information that is taken from said raw data content.

### Claim 79

A system comprising:
a plurality of content providers, wherein each content provider in said plurality of content providers is associated with a different content provider identifier, and each content provider accesses content having a different raw data format;
a universal content broker coupled to said plurality of content providers wherein upon said receipt of a content request including a content provider identifier, said universal content broker passes said request to a content provider in said plurality of content providers that is associated with said content provider identifier.

### Claim 80 (depends on 79)

The system of claim 79 further comprising:
a registry of content providers coupled to said universal content broker wherein said universal content broker selects said content provider from said registry based upon said content provider identifier.

### Claim 81 (depends on 79)

The system of claim 79 further comprising at least one interface adapted to associate property values with content.

### Claim 82 (depends on 79)

The system of claim 79, further comprising at least one interface adapted to set a property value of content.

### Claim 83 (depends on 79)

The system of claim 79, further comprising at least one interface adapted to read a property value of content.

### Claim 84 (depends on 79)

The system of claim 79, further comprising an interface adapted to notify registered client systems when content of interest to said registered client systems is processed by said universal content broker system.

### Claim 85 (depends on 79)

The system of claim 79, further comprising an interface adapted to notify registered client systems when new content is created by said universal content broker system.

### Claim 86 (depends on 79)

The system of claim 79 further comprising a hierarchy content provider.

### Claim 87 (depends on 86)

The system of claim 86 wherein said hierarchy content provider generates a virtual hierarchy of content of said universal content broker system.

### Claim 88 (depends on 79)

The system of claim 79 further comprising a configuration server.

### Claim 89 (depends on 88)

The system of claim 88 further comprising a configuration proxy coupled to said configuration server.

### Claim 90 (depends on 89)

The system of claim 89 wherein said configuration server further comprises a first DOM tree.

### Claim 91 (depends on 90)

The system of claim 90 wherein said DOM tree includes user profiles.

### Claim 92 (depends on 90)

The system of claim 90 wherein said DOM tree includes application profiles.

### Claim 93 (depends on 89)

The system of claim 89 wherein said configuration proxy further comprises a second DOM tree wherein said second DOM tree includes a subset of data in said first DOM tree.

### Claim 94

A computer program product comprising computer program code for a universal content provider service comprising:
a component interface; and
a content provider interface.

### Claim 95 (depends on 94)

A computer program product of claim 94 further comprising:
a content identifier factory interface.

### Claim 96

A computer program product comprising computer program code for a universal content broker service comprising:
a component interface; and
a content provider manager interface.

### Claim 97 (depends on 96)

The computer program product of claim 96 further comprising:
a content provider interface.

### Claim 98 (depends on 96)

A computer program product of claim 96 further comprising:
a content identifier factory interface.

### Claim 99

A computer program product comprising computer program code for a configuration and logic service comprising:
a profiling service; and
a plurality of screen templates.

### Claim 100 (depends on 99)

The computer program product of claim 99 further comprising a decision tree.

### Claim 101

A method for providing a plurality of content having different types and different protocols to a single user interface comprising:
receiving a content request from a client system wherein said content request comprises a content identifier;
selecting a content provider associated with said content identifier from a plurality of content providers wherein each of said content providers provides access to content having a different raw data format;
retrieving said requested content from said selected content provider; and
using said requested content to generate a page displayable on said client system.

### Claim 102 (depends on 101)

The method of claim 101 wherein said selecting a content provider comprises:
searching a registry including said plurality of content providers.
