Mobile device server

• US 7,277,693 B2
• Filed: 11/26/2004
• Issued: 10/02/2007
• Est. Priority Date: 11/15/2000
• Status: Active Grant

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Chen, Yih-Farn Robin, Chen, Ming-Feng, Rao, Chung-Hwa Herman
• Primary Examiner(s): Trost; William
• Assistant Examiner(s): PEREZ, JULIO R
• Application Number:
  US10/998,214
• Publication Number:
  US 20050240672A1
• Time in Patent Office: 1,040 Days
• Field of Search: 455/414, 455/502, 455/426.1, 455/442, 455/435.3, 455/455, 709/217, 709/205, 709/209
• US Class Current: 455/414.1
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/2871 Implementation details of single intermediate entities
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A mobile device server includes a flexible architecture having a plurality of components for allowing various mobile devices and protocols to communicate with each other and to receive data from various information spaces. Interface devlets send and receive messages in respective protocols. Access infolets utilize respective access methods to provide an abstract view of various information spaces. Logic applets implement service and/or application logic by processing information from one or more infolets. A further component referred to as a let engine communicates with the devlets, infolets, and applets, and maintains user and device profile information to provide a flexible framework for the mobile device server that can readily support new devices and protocols.

Claims

1. A method for adding new components to a mobile device server having a flexible architecture, comprising:

providing an engine component;

providing at least one user/device profile to the engine component,

providing a plurality of interface components communicating with the engine component in a predetermined format, each of the plurality of interface components for providing a respective interface for mobile devices sending data requests;

providing a plurality of access components communicating with the engine component, each of the plurality of access components for providing an abstract view of a respective information source based upon the data requests;

providing a plurality of logic components communicating with the engine component, each of the plurality of logic components for processing information retrieved by the plurality of access components and providing the processed information to one or more of the plurality of interface components for transmission to the mobile devices that sent the data requests;

wherein the processed information is adapted using user/device profile from the engine component, and

adding a further one of an interface component, access component and a logic component to support a respective mobile device, information source, and process without altering service logic of the mobile device server.

2. The method according to claim 1, further including formatting the data requests into text.

3. The method according to claim 1, wherein the user/device profile includes a size limitation.

4. The method according to claim 1, further including servicing data requests from devices including at least two device types selected from the group consisting of SMS mobile phones, Palm devices, AIM devices, AOL devices, two way pagers, pocket PCs, and AT&

T Pocket Net devices.

5. The method according to claim 1, further including supporting an additional type of mobile device by adding a corresponding interface component without altering service logic.