WO2001052016A2 - Architecture logicielle pour donnees sans fil, et son procede d'exploitation - Google Patents

Architecture logicielle pour donnees sans fil, et son procede d'exploitation Download PDF

Info

Publication number
WO2001052016A2
WO2001052016A2 PCT/US2001/000946 US0100946W WO0152016A2 WO 2001052016 A2 WO2001052016 A2 WO 2001052016A2 US 0100946 W US0100946 W US 0100946W WO 0152016 A2 WO0152016 A2 WO 0152016A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
server
message
wireless
connector
Prior art date
Application number
PCT/US2001/000946
Other languages
English (en)
Other versions
WO2001052016A3 (fr
Inventor
Shane Connely
Nathanial X. Freitas
Will Meyer
Jonathan Oakes
James Venturi
Original Assignee
Thin Air Apps
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Thin Air Apps filed Critical Thin Air Apps
Priority to AU2001229376A priority Critical patent/AU2001229376A1/en
Publication of WO2001052016A2 publication Critical patent/WO2001052016A2/fr
Publication of WO2001052016A3 publication Critical patent/WO2001052016A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access

Definitions

  • the present invention relates to a system and method for accessing server-based
  • the present invention relates to a
  • HTML HyperText Markup
  • WML Wireless Markup Language
  • Groupware includes essentially any application or
  • Microsoft's Outlook® client and Microsoft Exchange Server® allow a user to
  • the present invention satisfies the foregoing need by providing, in one aspect, a
  • the software architecture includes a wireless data receiving and transmitting
  • FIG. 1 is a block diagram representation of a system in accordance with a
  • FIG. 2 is a block diagram representation of protocols, gateways, and devices that
  • FIG. 3 is a flowchart representing the request handling process of the system of the
  • FIG. 4 is a flowchart representing the wireless device recognition process.
  • FIG. 5 is a UML diagram of the core classes m a preferred embodiment of the
  • FIG. 6 is a UML diagram representing the message subclasses in a preferred embodiment
  • FIG. 7 is a block diagram representing the communication protocol for an
  • FIG. 8 is a block diagram representation of server communication protocol
  • FIG 9 is a block diagram representation the use of server communication protocol
  • FIGS. 10A- 10H is a flowchart of a wireless groupware application in accordance
  • FIG 1 there is a shown a block diagram representation of a system in
  • the system includes Client devices, e.g , WAP phone 20, RIM
  • gateway e.g., VoxML, WAP, etc.
  • protocol e.g., HTTP
  • AIM. SMTP. SMS, etc.. can also be supported by the system. Referring back to FIG. 1,
  • the Connector server 30 acts as a secure access point from the outside world into a
  • the network 32 will be a
  • server refers to a software application running on a hardware
  • the complete chain of wireless communication usualh. but not necessa ⁇ ly, includes a number of gateways, base stations, receivers, and antennas
  • Communication may also take place over public or p ⁇ vate networks using a va ⁇ ety of
  • Connector server 30 is a Pentium II class or Unix equivalent server with 128MB RAM,
  • the data stores 34-40 are connected to Providers 42-44 which provide an access
  • Providers 42-44 can be located in the same LAN as the
  • Provider availability allows them to reside behind firewalls 48 if needed. Providers can
  • Providers 42-46 manage access to their assigned data
  • the system may also
  • Client specific Connectors 52 to provide device specific application
  • Palm VII organizers include Palm VII organizers, Palm DI/V organizers with wireless connectivity RIM
  • the Connectors 52 are dynamically loaded modules of the Connector Server 30
  • Connector 52 resembles a Java Servlet in form and function. Connectors are supported by the Connector Access class which provides standard service such as Session
  • a Connector 52 handles requests from wireless devices and generates responses.
  • Connectors can share the core functionality that makes up the application logic
  • an HTTP request 58 is
  • a device detection process 60 is
  • the HTTP request is routed
  • the Connector(s) 52 may be modula ⁇ zed further by moving the data-access
  • Server application framework makes Providers available to Connectors, whether they are
  • the Connector Server 30 When a Connector 52 receives a request from a device, the Connector Server 30
  • Device objects are an abstraction of the actual
  • a Device Profile represents a template or prototype for a particular class of
  • Device class membership may be
  • a Connector can
  • the UP Browser may have screens with ten lines of text while others may only support
  • Connector Server 30 When the Connector Server 30 receives an HTTP request, it quenes each of its
  • the chosen DeviceProfile then acts as a factory, generating a Device instance,
  • Connector Server 30 When the Connector Server 30 routes a request to your Connector, it constructs a
  • Dat can also be encrypted at the device level and at the Connector server 30 so that at no point in the chain of communication between device and data store is data in an
  • the network communication layers employ up-to-date encryption and
  • Connector server 30 is performed using 40 or 128-bit Secure Socket Layer (SSL)
  • 30 can also be encrypted using a va ⁇ ety of methods, including SSL and other Public key
  • PKI Infrastructure
  • the Connector server 30 facilitates access by the Client devices 20-24 to a host of
  • the data stores 34-40 can also
  • Providers 42-46 enable disparate data sources to interact with the
  • Connector server 30 Connectors 52 handle the va ⁇ ous protocols and pecuha ⁇ ties of
  • wireless handheld devices supporting, in p ⁇ nciple, even those devices that do not yet
  • Connectors 52 can also transform data store objects into HTML. XML, WML, or
  • a connector 52 can also be used to link
  • Connector server 30 external applications and data sources to a Connector server 30.
  • p ⁇ ma ⁇ ly provided to support wireless Client devices 20-24, hardwired
  • access devices 54 e.g., network terminals, can also access the data stores 34-40 through
  • Connector 52 to the Connector Server 30 can access a remote data stores 56
  • server 30 component that routes traffic between them. Since the modules can be installed
  • the component-based architecture provides users with their choice of multiple
  • Connector server 30 When installed on separate machines, both the Connector server 30 and Providers
  • groupware refers to a software application paradigm which
  • Each user has the
  • the architecture of a groupware product includes server software, or a
  • ASS NAME DESCRIPTION ⁇ tor Vogelm The core representation of an item within a groupware store. It contains an item's identifier string and location path. All other groupware item types extend this class.
  • Event IA representation of an appointment, reminder, or meeting The event has one organizer and one or more attendees.
  • the class l also contains the location, date, time, and description of the bvent.
  • AddNewGroupwareltem The basic "put" action for a groupware store. This represents actions such as composing email, adding an entry to a date book, or adding a new person to an address book.
  • _ oveGroupwareltem The action for modifying the location of an item within a groupware store. This represents actions such as filing an email, moving an appointment to a shared group calendar, or organizing an address book into categories.
  • UpdateGroupwareltem The action for modifying an existing item kvithin a groupware store. This represents lactions such as editing an email draft, changing Ithe time of a meeting, or modifying the completion status of a task on a To Do list.
  • DeleteGroupwareltem The action for removing an existing item from a groupware store. This represents actions such as deleting an email, canceling a meeting, or removing a post from a message board.
  • Countltems, CountltemsResponse The action for obtaining a count of total items in a specified groupware store location. This is used to obtain status or overview information [for the user.
  • the second component of the wireless groupware system is the client-server
  • SIRF Simple Inbox Return Format
  • HTTP HyperText Protocol
  • SMTP Send Mail Transfer Protocol
  • the SIRF protocol is best understood by reference to the wire protocol specification
  • -GUIDs are globally unique identifiers, stored as valid ANSI NULL-terminated st ⁇ ngs
  • time is 24-hour format.
  • the client and Server will agree upon a number of e ⁇ or and status codes to communicate
  • the "API" is a set of routines that the Connector 52,
  • FIG. 1 routes from a Client device through to the session management layers.
  • the Inet Library 78 which controls the
  • Palm hardware for sending data and the Network Stack 80. which is the lower level portion of the Inet software, all run on the Palm device Communication of the Palm
  • the Connector Server 84 communicates tot he Message Store 88
  • Messaging Connector 86 which may also have as part of it a Provider as
  • the Messaging Connector 86 will communicate over HTTP with the Client device
  • Palm.net proxy server to pass it through to the Client device.
  • the Palm Connector 52 will
  • the framework is designed to allow developers to
  • asynchronous communication protocols can be hidden from the level at which the
  • Actions such as Fetch Messages or Delete
  • the client uses the services of a server supporting this framework to carry out
  • a Request which contains a set of Actions and a MetaData object
  • the server-side of the framework consists of three distinct
  • Transport 90 Transport 90, Router 92, and Executor 94
  • the Router 92 is responsible for maintaining resource
  • the Transport 90 assembles the Actions 100-104 using services of the Router 92, then
  • the Transport 90 receives the Response 98 from the Executor 94 and
  • Transport piece 90 of the architecture could be implemented as a stand alone
  • server application could in fact be the execution environment that hosts the
  • Transport component 90 could be plugged into some other
  • the Transport 90 must know how to interpret incoming Requests 64 and build
  • Actions 100-104 from some network layer protocol This implies that a Transport
  • va ⁇ ous Actions 100-104 Action Responses 98
  • MetaData Metadata
  • the Executor 94 is the component that understands how to "execute" Actions 100-
  • Transport 90 to some degree, in that they both have the notion of a set of "supported" Actions, on which they must agree. This does not mean that an Executor 94 and
  • Transport 90 are only usable with a certain predefined set of Actions 100-104. As we will
  • the Router 92 manages coordination between the Transport 90 and the Executor
  • the Router 92 is an intermediary, and though implementations may be complex, the
  • the framework can be implemented in a number of
  • NSYNC Java implementation provides an HTTP Transport Core component 106. This
  • the module is designed to take incoming HTTP requests and output HTTP responses, and
  • the module is the runtime environment for the Router and an Executor.
  • the module includes a Java
  • WAP Wireless Application Protocol
  • a welcome screen will appear 114
  • the PIN is blank, the user will be provided with a message indicating that a password must
  • e-mail/groupware providers include Microsoft Exchange,
  • the server is then entered 138.
  • the server's hostname can be obtained from the administrator
  • the user may not have the option to save the
  • the user will then be prompted to enter their Display Name 144.
  • Name is the name that will be used when messages are sent by the user using the
  • the Display Name field is not required for Microsoft Exchange or
  • the Mailbox Manager allows a user to logon to a particular mailbox that has been
  • the mailbox is selected from the list and a Sign In
  • a search is then performed to determine if the user elected to have the
  • the default view screen will contain a list of headers for the five most recently
  • the default screen will also provide the user with the options of
  • view screen 160 the user can browse through the list of message headers in the mailbox
  • Messages received in the mailbox can be standard e-mail
  • selected message is an invitation or an e-mail 174. If it is an invitation, the details of the
  • the user can then select the response option desired and this will be sent to the invitation sender 178. Rather than selecting a response, the user can also select
  • the message contents are sent in one kilobyte chunks so only a
  • portion of the message may be displayed in the default vie .
  • the user can enter the data or select back to back up and change the
  • the user selects the send option and, if the recipient list matches with the o ⁇ gmal message 186, the message is sent
  • the user can search through their entire mbox based upon search c ⁇ te ⁇ a
  • the list of found messages can be
  • Calendars As depicted in FIG IOC, the user has the option of accessing their groupware
  • server will determine if the calendar is empty 202 and, if so, deliver a message to the user
  • the OK option returns the user to the previous screen or, if it is already at the first
  • Connector Server 218 As will be desc ⁇ bed below, to view notes a user
  • the session idle time can be configured by the system administrator.
  • This application allows a user to access contact lists stored on the connector server.
  • the server will determine first if there are any contacts in the user's list
  • the Search option permits the user to search for a contact by ente ⁇ ng the contact's
  • infonnation 246 or let the user know that no contact has been found with that name 244
  • the recipient list is blank 252 the user will be returned to the prompt to enter an e-mail
  • recipient's e-mail addresses can be
  • the Mam Menu screen as depicted m FIG. 10F, provides the user with the
  • the user can also view messages that are stored in folders other than the inbox
  • the user is then presented with a message requesting the user select the type of message
  • the Mailbox Manager can also be used to create, edit, or delete a mailbox
  • the user is provided a message indicating that the provider could not be found and the user

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Communication Control (AREA)

Abstract

L'invention concerne une architecture logicielle, un modèle de données et un protocole d'accès pour faciliter l'accès par session, en temps réel, à des données serveur en provenance de dispositifs de calcul sans fil à bande passante étroite.
PCT/US2001/000946 2000-01-14 2001-01-16 Architecture logicielle pour donnees sans fil, et son procede d'exploitation WO2001052016A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001229376A AU2001229376A1 (en) 2000-01-14 2001-01-16 Software architecture for wireless data and method of operation thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US17601400P 2000-01-14 2000-01-14
US60/176,014 2000-01-14

Publications (2)

Publication Number Publication Date
WO2001052016A2 true WO2001052016A2 (fr) 2001-07-19
WO2001052016A3 WO2001052016A3 (fr) 2002-04-25

Family

ID=22642621

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/000946 WO2001052016A2 (fr) 2000-01-14 2001-01-16 Architecture logicielle pour donnees sans fil, et son procede d'exploitation

Country Status (2)

Country Link
AU (1) AU2001229376A1 (fr)
WO (1) WO2001052016A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002015617A1 (fr) * 2000-08-11 2002-02-21 Nokia Mobile Phones Limited Service de donnees de telecommunications pour mobiles

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5758088A (en) * 1995-05-08 1998-05-26 Compuserve Incorporated System for transmitting messages, between an installed network and wireless device
US6107944A (en) * 1994-06-24 2000-08-22 Navigation Technologies Corporation Electronic navigation system and method
US6151628A (en) * 1997-07-03 2000-11-21 3Com Corporation Network access methods, including direct wireless to internet access
US6167426A (en) * 1996-11-15 2000-12-26 Wireless Internet, Inc. Contact alerts for unconnected users

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6107944A (en) * 1994-06-24 2000-08-22 Navigation Technologies Corporation Electronic navigation system and method
US5758088A (en) * 1995-05-08 1998-05-26 Compuserve Incorporated System for transmitting messages, between an installed network and wireless device
US6167426A (en) * 1996-11-15 2000-12-26 Wireless Internet, Inc. Contact alerts for unconnected users
US6151628A (en) * 1997-07-03 2000-11-21 3Com Corporation Network access methods, including direct wireless to internet access

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002015617A1 (fr) * 2000-08-11 2002-02-21 Nokia Mobile Phones Limited Service de donnees de telecommunications pour mobiles
US7274927B2 (en) 2000-08-11 2007-09-25 Nokia Corporation Mobile telecommunications data service

Also Published As

Publication number Publication date
AU2001229376A1 (en) 2001-07-24
WO2001052016A3 (fr) 2002-04-25

Similar Documents

Publication Publication Date Title
US7092998B2 (en) Software architecture for wireless data and method of operation thereof
US6360252B1 (en) Managing the transfer of e-mail attachments to rendering devices other than an original e-mail recipient
US7293074B1 (en) Performing server actions using template with field that can be completed without obtaining information from a user
US7117245B1 (en) Global communication method and system
US8271535B2 (en) Contact management update protocols
US8301711B2 (en) Electronic mail communications system with client email internet service provider (ISP) polling application and related methods
US20060235945A1 (en) Software architecture for wireless data and method of operation thereof
US9479638B2 (en) Methods and systems for dispatching messages to mobile devices
KR100436551B1 (ko) 휴대전화번호를 이용한 메일주소정보 제공시스템 및 그 방법
US20030105812A1 (en) Hybrid system architecture for secure peer-to-peer-communications
US20050038863A1 (en) Device message management system
US20020035607A1 (en) E-mail gateway system
US20080294729A1 (en) Email object for open mobile alliance data synchronization usage
US20100333181A1 (en) System and method for remotely configuring a desktop mailbox
US20020091775A1 (en) System and method for universal email
KR20060050342A (ko) 팩스 메시지를 나타내기 위해 메시지 스키마를 확장하는시스템 및 방법
WO2001052016A2 (fr) Architecture logicielle pour donnees sans fil, et son procede d'exploitation
WO2007111596A1 (fr) Système et méthode pour assurer la migration des données d'un compte utilisateur
EP1931092B1 (fr) Procédé et dispositif pour pousser des courriels vers des dispositifs de communication sans fil
US20020147794A1 (en) Service allocation and assigning method and program therefor
CN101563897A (zh) 用于统一特号映射电话簿存在服务的方法和设备
US20030030681A1 (en) Enhanced text entry system for wireless devices
CN100524299C (zh) 用于配置访问电子邮箱的系统和方法
EP1569396A1 (fr) Configuration à distance d'un système de redirection de courrier électronique par un dispositif mobile
EP1999913A1 (fr) Système et méthode d'approvisionnement d'un dispositif de communication mobile sans fil, comportant des indicateurs représentant les données image et son

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: COMMUNICATION PURSUANT TO RULE 69 EPC (EPO FORM 1205A OF 301002)

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP