Mobile device server

• US 20020086706A1
• Filed: 11/09/2001
• Published: 07/04/2002
• Est. Priority Date: 11/15/2000
• Status: Abandoned Application

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Chen, Ming-Feng, Chen, Yih-Farn Robin, Rao, Chung-Hwa Herman
• Application Number:
  US10/037,570
• Publication Number:
  US 20020086706A1
• Time in Patent Office: Days
• US Class Current: 455/560
• 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 mobile device server system for processing data requests from a variety of mobile device types, comprising:

an engine component;

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;

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 type based upon the data requests; and

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.

2. The system according to claim 1, further including a proxy interface for providing a communication interface to the mobile device server.

3. The system according to claim 1, wherein the plurality of interface components includes components for supporting protocols selected from the group consisting of supporting interfaces to AIM, ICQ, SMS, XMS, Telnet, HTTP, WAP, SMTP, IMAP, POP3, and IVR.

4. The system according to claim 1, wherein the plurality of access components includes components for providing access to information spaces selected from the group of access components consisting of ODBC, JDBC, CORBA, http, X10, email, and XML.

5. The system according to claim 1, wherein the predetermined format includes text for transfers from the plurality of interface components to the engine component.

6. The system according to claim 5, wherein the predetermined format includes MIME for transfers from the engine component to the plurality of interface components.

7. The system according to claim 1, wherein the variety of mobile device types include devices selected from the group consisting of SMS mobile phones, PDA devices, Instant Messaging devices, Email devices, two way pagers, pocket PCs, and AT&

T Pocket Net devices.

8. The system according to claim 1, wherein the mobile devices can communicate with one or more of CDPD, TDMA, GSM, two way paging, Internet, and email networks.

9. The system according to claim 1, further including a logic component for re-directing the processed information to a further device associated with the first mobile device.

10. The system according to claim 1, further including a logic component for scheduling an activation and/or response to a data request.

11. A method for enabling communication between a variety of mobile device types, comprising:

receiving a first data request from a first mobile device utilizing a first protocol;

receiving a second data request from a second mobile device utilizing a second protocol;

formatting the first and second data requests into a predetermined format;

processing the first data request to initiate an information exchange between the first mobile device and a first information space associated with a first information source;

retrieving requested data for the first data request from the first information source;

formatting the retrieved data based upon parameters associated with the first mobile device; and

sending the formatted data to the first mobile device using the first protocol.

12. The method according to claim 11, further including supporting an additional type of mobile device by adding an interface component supporting the additional mobile device type.

13. The method according to claim 11, further including supporting an additional type of information space by adding an access component supporting a protocol for accessing the additional type of information space.

14. The method according to claim 11, further including supporting an additional service function by adding a logic component supporting the additional service.

17. The method according to claim 16, further including formatting the data request into text.

18. The method according to claim 16, further including formatting the raw data into MIME.

19. The method according to claim 16, wherein the characteristics of the recipient device include a size limitation.

20. The method according to claim 16, 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.

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

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

providing an 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 device that sent the data request; 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.

16. A method for servicing data requests by a plurality of mobile device types, comprising:

receiving a data request from a first mobile device via a respective one of a plurality of interface devlets;

formatting the data request to a predetermined format;

passing the formatted data request to a let engine;

invoking at least one of a plurality of logic applets based upon the data request;

invoking a respective one of a plurality of access infolets based upon an information space type associated with the data request;

retrieving raw data from a device corresponding to the information space type;

formatting the raw data based upon characteristics of a recipient device specified in the data request; and

passing the formatted the data to the recipient device via an interface devlet supporting the recipient device.