U.S. patent application number 13/792785 was filed with the patent office on 2013-07-25 for system and method for supporting multiple certificate status providers on a mobile communication device.
This patent application is currently assigned to Research In Motion Limited. The applicant listed for this patent is Research In Motion Limited. Invention is credited to Dale J. Hobbs, Stefan Erik Janhunen, Herbert Anthony Little.
Application Number | 20130191633 13/792785 |
Document ID | / |
Family ID | 43757642 |
Filed Date | 2013-07-25 |
United States Patent
Application |
20130191633 |
Kind Code |
A1 |
Little; Herbert Anthony ; et
al. |
July 25, 2013 |
SYSTEM AND METHOD FOR SUPPORTING MULTIPLE CERTIFICATE STATUS
PROVIDERS ON A MOBILE COMMUNICATION DEVICE
Abstract
A method and system for supporting multiple digital certificate
status information providers are disclosed. An initial service
request is prepared at a proxy system client module and sent to as
proxy system service module operating at a proxy system. The proxy
system prepares multiple service requests and sends the service
requests to respective multiple digital certificate status
information providers. One of the responses to the service requests
received from the status information providers is selected, and a
response to the initial service request is prepared and returned to
the proxy system client module based on the selected response.
Inventors: |
Little; Herbert Anthony;
(Waterloo, CA) ; Janhunen; Stefan Erik; (Waterloo,
CA) ; Hobbs; Dale J.; (Woodstock, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Research In Motion Limited; |
Waterloo |
|
CA |
|
|
Assignee: |
Research In Motion Limited
Waterloo
CA
|
Family ID: |
43757642 |
Appl. No.: |
13/792785 |
Filed: |
March 11, 2013 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
12954731 |
Nov 26, 2010 |
8423763 |
|
|
13792785 |
|
|
|
|
10508631 |
Sep 17, 2004 |
7865720 |
|
|
12954731 |
|
|
|
|
Current U.S.
Class: |
713/158 |
Current CPC
Class: |
H04L 63/045 20130101;
H04L 63/0823 20130101; H04L 12/66 20130101; H04L 63/0281 20130101;
H04L 9/3268 20130101; H04L 63/126 20130101 |
Class at
Publication: |
713/158 |
International
Class: |
H04L 9/32 20060101
H04L009/32 |
Foreign Application Data
Date |
Code |
Application Number |
Mar 20, 2003 |
CA |
PCT/CA2003/000404 |
Claims
1. A method, executed in a processor of a proxy system
communication device, of obtaining status information of a digital
certificate comprising: providing a mapping table for maintaining a
correspondence between a plurality of digital certificate issuers
and at least one of a serial number and a subject name associated
with the digital certificate; upon receiving a request for the
status information from a mobile device comprising one of: the at
least one serial number and subject name, generating a plurality of
service requests, each of the plurality of service requests
associated with a respective status information provider and
formatted according to at least one of a communication protocol and
content for the respective status information provider, the content
being generated based on data extracted from the mapping table, the
respective status information provider maintaining revocation
status information of the digital certificate; sending the
generated plurality of service requests to the respective status
information providers associated therewith; receiving a plurality
of responses from the respective status information providers, the
responses including the revocation status information of the
digital certificate; and generating as the status information the
revocation status information included in at least one of the
received responses.
2. The method of claim 1, wherein the request includes a list of
status information providers to which the service request is to be
sent.
3. The method of claim 2, wherein the list of status information
providers is arranged in order of preference between subsequent
responses from the status information providers.
4. The method of claim 1 wherein the request includes a ranking
list that specifies an order of preference between subsequent
responses from the status information providers.
5. The method of claim 1, wherein the generated digital certificate
status response is utilized in processing a secure message at the
communication device.
6. The method of claim 5, wherein the secure message comprises a
digital signature.
7. The method of claim 1, wherein the request comprises
identification information identifying a target digital certificate
for which digital certificate status information is requested,
wherein the response from the at least one of the digital
certificate status information providers comprises status
information for the target digital certificate, and wherein the
generated digital certificate status response comprises a status
indicator for the target digital certificate.
8. The method of claim 1, wherein a request for a digital
certificate status information for a digital certificate in a
secure message is received after the communication has received the
secure message comprising the digital certificate and generated the
request for digital certificate status information.
9. The method of claim 1, wherein the request for digital
certificate status information is generated at predetermined time
intervals.
10. The method of claim 1, wherein the request for digital
certificate status information is generated based on a validity
period of the digital certificate.
11. The method of claim 1, wherein the request comprises a
revocation status request for a digital certificate stored at the
communication device.
12. The method of claim 1, wherein status information for a
plurality of digital certificates is requested in the request, and
wherein the generated digital certificate status response comprises
a status indicator for each of the plurality of digital
certificates.
13. The method of claim 12, wherein each of the plurality of
service requests comprises a status information request for at
least one of the plurality of digital certificates.
14. The method of claim 1, wherein the plurality of service
requests and each response from the digital certificate status
information providers conform to Online Certificate Status Protocol
(OCSP).
15. The method of claim 1, wherein generating the response further
comprises formatting each response from the digital certificate
status information providers to conform to a format for the mobile
device.
16. A communication device for obtaining status information of a
digital certificate the communication device comprising; a
processor; a memory encoded with instructions for commanding the
processor to perform acts including: providing a mapping table for
maintaining a correspondence between a plurality of digital
certificate issuers and at least one of a serial number and a
subject name associated with the digital certificate; upon
receiving a request for the status information from a mobile device
comprising one of the at least one serial number and subject name,
generating a plurality of service requests, each of the plurality
of service requests associated with a respective status information
provider and formatted according to at least one of a communication
protocol and content for the respective status information
provider, the content being generated based on data extracted from
the mapping table, the respective status information provider
maintaining revocation status information of the digital
certificate; sending the generated plurality of service requests to
the respective status information providers associated therewith;
receiving a plurality of responses from the respective status
information providers, the responses including the revocation
status information of the digital certificate; and generating as
the status information the revocation status information included
in at least one of the received responses.
17. The communication device of claim 16, wherein the communication
device is selected from the group consisting of a handheld
communication device, a data communication device, a voice
communication device, a dual-mode communication device, a mobile
telephone with data communication capabilities, a personal digital
assistant (PDA) enabled for wireless communications, a two-way
pager, and a wireless modern.
18. The communication device of claim 16, wherein the request is
generated at predetermined time intervals.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of earlier filed
nonprovisional applications having U.S. application Ser. No
12/954,731 filed 26 Nov. 2010, which in turn is a continuation of
U.S. application Ser. No. 10/508,631 filed Sep. 17, 2004, now U.S.
Pat. No. 7,865,720, granted on Jan. 4, 2011, which in turn is a
National Entry of International Application No. PCT/CA2003/000404
filed Mar. 20, 2003, which in turn claims priority to U.S.
Provisional Patent Application No. 60/365,534 filed Mar. 20, 2002.
This application claims priority under 35 U.S.C. 120 to
aforementioned application Ser. No. 12/954,731 filed 26Nov. 2010
and said application Ser. No. 10/506,631 filed Sep. 17, 2004,
National Entry of International Application No PCT/CA20031000404
filed Mar. 20, 2003, and said Application No. 60/365,534 filed Mar.
20, 2002, and incorporates by reference the disclosures of both
said applications in their entirety.
BACKGROUND
[0002] 1. Technical Field
[0003] This invention relates generally to the field of secure
electronic messaging and in particular to checking the status of
digital certificates.
[0004] 2. Description of the State of the Art
[0005] Known secure messaging clients including, for example,
e-mail software applications operating on desktop computer systems,
maintain a data store, or at least a dedicated data storage area,
for secure messaging information such as digital certificates. A
digital certificate normally includes the public key of an entity
as well as identity information that is bound to the public key
with one or more digital signatures. In Secure Multipurpose
Internet Mail Extensions (S/MIME) messaging for example, a public
key is used to verify a digital signature on a received secure
message and to encrypt a session key that was used to encrypt a
message to be sent. In other secure messaging schemes, public keys
may be used to encrypt data or messages. If a public key is not
available at the messaging client when required for encryption or
digital signature verification, then the digital certificate, or at
least the public key, must be loaded onto the messaging client
before these operations can be performed.
[0006] Typically, a digital certificate is checked against a
Certificate Revocation List (CRL) to determine if the digital
certificate has been revoked by its issuer. This check is typically
performed when a digital certificate is first received and
periodically thereafter, for example when a new CRL is received.
However, CRLs tend to be relatively bulky, so that transfer of CRLs
to messaging clients consume considerable communication resources,
and storage of CRLs at a messaging client may consume significant
memory space. CRL-based revocation status checks are also
processor-intensive and time consuming. These effects can be
particularly pronounced in messaging clients operating on wireless
mobile communication devices, which operate within
bandwidth-limited wireless communication networks and may have
limited processing and memory resources. In addition, revocation
status is updated in CRL-based systems only when a new CRL is
distributed.
[0007] Another scheme for digital certificate revocation status
checking involves querying remote systems which maintain digital
certificate revocation status information. A difficulty with this
scheme is that it requires a separate request-response exchange for
each remote system to be queried. These exchanges may cause
significant time delays and consume significant amounts of
available communication bandwidth, particularly for secure
messaging clients operating on wireless mobile communication
devices.
[0008] Digital certificate validity checks may similarly be
processor intensive and time consuming for messaging clients
operating on constrained devices. Digital certificate validity
checks may similarly be performed by remote systems and may be
useful for such devices, but as described above, typical schemes
are not particularly suitable when multiple remote systems are to
be queried.
SUMMARY
[0009] According to an aspect of the invention, a method of
accessing multiple digital certificate status information providers
to obtain digital certificate status information comprises the
steps of receiving a request for digital certificate status
information from a communication device, generating multiple
service requests based upon the received request, each of the
multiple service requests corresponding to a digital certificate
status information provider, sending the generated multiple service
requests to their corresponding digital certificate status
information providers, receiving a response comprising digital
certificate status information from at least one of the digital
certificate status information providers, generating a response to
the request for digital certificate status information using at
least a portion of the received digital certificate status
information, and sending the generated response to the request to
the communication device.
[0010] An apparatus for accessing multiple digital certificate
status information providers to obtain digital certificate status
information for a communication device, according to another aspect
of the invention, comprises means for receiving a request regarding
digital certificate status information from the communication
device, means for generating multiple service requests based upon
the received request, each generated service request corresponding
to a digital certificate status information provider, means for
sending the generated multiple service requests to their
corresponding status information providers over a computer network,
and means for receiving over a computer network a response
containing digital certificate status information from at least one
of the status information providers, wherein at least a portion of
the received digital certificate status information is used in
providing a status information response to the communication
device.
BRIEF DESCRIPTION OF THE DRAWINGS
[0011] FIG. 1 is a block diagram of a messaging system
[0012] FIG. 2 is a block diagram illustrating a secure e-mail
message exchange in a messaging system.
[0013] FIG. 3 is a block diagram of a system which supports
multiple digital certificate status information providers.
[0014] FIG. 4 is a flow diagram illustrating a method of supporting
multiple digital certificate status information providers.
[0015] FIG. 5 is a block diagram of a system having multiple proxy
system client modules which support multiple digital certificate
status information providers.
[0016] FIG. 6 is a block diagram of a wireless mobile communication
device.
[0017] FIG. 7 is a block diagram illustrating a multiple messaging
scheme utilizing an intermediate computer system.
[0018] FIG. 8 is a block diagram showing an example communication
system.
[0019] FIG. 9 is a block diagram of an alternative example
communication system.
[0020] FIG. 10 is a block diagram of another alternative
communication system.
DETAILED DESCRIPTION
[0021] A secure message is a message that has been processed by a
message sender, or possibly by an intermediate system between a
message sender and a message receiver, to ensure one or more of
data confidentiality, data integrity and user authentication.
Common techniques for secure messaging include signing a message
with a digital signature and/or encrypting a message. For example,
a secure message may be a message that has been signed, or
encrypted, or encrypted and then signed, or signed and then
encrypted according to variants of Secure Multipurpose Internet
Mail Extensions (S/MIME).
[0022] A messaging client allows a system on which it operates to
receive and possibly also send messages, Messaging clients may
operate on a computer system, a handheld device, or any other
system or device with communications capabilities. Many messaging
clients also have additional non-messaging functions.
[0023] FIG. 1 is a block diagram of an exemplary messaging system.
There are many different messaging system topologies, and the
system shown in FIG. 1 is but one of many that may be used with the
systems and methods disclosed herein.
[0024] The system 10 includes a Wide Area Network (WAN) 12, coupled
to a computer system 14, a wireless network gateway 16 and a
corporate Local Area Network (LAN) 18. The wireless network gateway
16 is also connected to a wireless communication network 20 in
which a wireless mobile communication device 22 ("mobile device"),
is configured to operate. An exemplary mobile device 22 may be of
the type disclosed in U.S. Pat. No, 6,278,442, entitled "HAND-HELD
ELECTRONIC DEVICE WITH A KEYBOARD OPTIMIZED FOR USE WITH THE
THUMBS," the entire disclosure of which is incorporated herein by
reference.
[0025] The computer system 14 represents a desktop or laptop PC
that is configured for connection to the WAN 12. The WAN 12 can be
a private network, or a larger publicly accessible network, such as
the Internet. PCs such as the computer system 14 normally access
the Internet through an Internet Service Provider (ISP),
Application Service Provider (ASP) or the like.
[0026] The corporate LAN 18 is an example of a network-based
messaging client. As shown, a corporate LAN 18 is normally located
behind a security firewall 24. Within the corporate LAN 30 is a
message server 26, running on a computer within the firewall 24,
that functions as the main interface for the corporation to
exchange messages both within the LAN 18 and with other external
messaging clients via the WAN 20. Two of the most common message
servers 26 are the Microsoft.TM. Exchange and Lotus Domino.TM.
server products. These servers are often used in conjunction with
Internet mail routers that route and deliver mail. A message server
26 may extend beyond just message sending and receiving, providing
such functionality as dynamic database storage engines that have
predefined database formats for data like calendars, to-do lists,
task lists, e-mail and documentation.
[0027] The message server 26 provides messaging capabilities to one
or more network computer systems 28 in the LAN 18. A typical LAN
includes multiple computer systems shown generally as computer
systems 28, each of which implements a messaging client, most often
as a software application such as Microsoft Outlook.TM., for
messaging functions. In the network 18, messages are received by
the message server 26, distributed to the appropriate mailboxes for
user accounts addressed in the received message, and can be
accessed by a user through a computer in the one or more computer
systems 28. Although messaging clients in the LAN 18 operate on the
computer systems 28, there are also known messaging clients that
operate in conjunction with handheld devices and other systems or
devices with electronic messaging capabilities. Like the message
server 26, a messaging client may also have additional
non-messaging functions.
[0028] The wireless network gateway 16 provides an interface to a
wireless network 20, through which messages may be exchanged with a
mobile device 22. Such functions as addressing of a mobile device
22, encoding or otherwise transforming messages for wireless
transmission, and any other required interface functions are
performed by the wireless network gateway 16. Where the wireless
network gateway 16 is configured for operation in conjunction with
more than one wireless network 20, the wireless network gateway 16
may also determine a most likely network for locating a given user
and track users as they roam between countries or networks.
[0029] Any computer system with access to the WAN 12 may exchange
messages with a mobile device 22 through the wireless network
gateway 16. Alternatively, private wireless network gateways such
as wireless Virtual Private Network (VPN) routers could also be
implemented to provide a private interface to a wireless network
such as 20. For example, a wireless VPN implemented in the LAN 18
provides a private interface from the LAN 18 to one or more mobile
devices through the wireless network 20.
[0030] Such a private interface to wireless devices via the
wireless network gateway 16 and/or the wireless network 20 can
effectively be extended to entities outside the LAN 18 by providing
a message forwarding or redirection system which operates with the
message server 26. In this type of system, incoming messages
received by the message server 26 and addressed to a user that has
a mobile device 22 are redirected through the wireless network
interface, either a wireless VPN router, the gateway 16 or another
interface, for example, to the wireless network 20 and to the
user's mobile device 22. An exemplary redirector system operating
on the message server 26 may be of the type disclosed in U.S. Pat.
No. 6,219,694, entitled "SYSTEM AND METHOD FOR PUSHING INFORMATION
FROM A HOST SYSTEM TO A MOBILE DATA COMMUNICATION DEVICE HAVING A
SHARED ELECTRONIC ADDRESS," the entire disclosure of which is
incorporated herein by reference.
[0031] In wireless networks such as 20, messages are normally
delivered to and from mobile devices such as the mobile device 22
via RF transmissions between base stations in the wireless network
20 and mobile devices. Modern wireless networks typically serve
thousands of subscribers, each subscriber having a mobile device.
The wireless network 20 may be one of many different types of
wireless network, such as a data-centric wireless network, a
voice-centric wireless network or and a dual-mode networks that can
support both voice and data communications over the same physical
base stations. Dual-mode networks include, but are not limited to
recently-developed Code Division Multiple Access (COMA) networks,
the Groupe Special Mobile or the Global System for Mobile
Communications (GSM) and the General Packet Radio Service (GPRS),
and future third-generation (3G) networks like Enhanced Data rates
for Global Evolution (EDGE) and Universal Mobile Telecommunications
Systems (UMTS). GPRS is a data overlay on the GSM wireless network,
operating in virtually every country in Europe. In addition to
these illustrative wireless networks, other wireless networks may
also be used.
[0032] Other examples of data-centric networks include, but are not
limited to the Mobitex.TM. Radio Network ("Mobitex") and the
DataTACT.TM. Radio Network ("DataTAC"). Examples of older
voice-centric data networks include Personal Communication Systems
(PCS) networks like CDMA, GSM, and Time Division Multiple Access
(TDMA).
[0033] The mobile device 22 may be a data communication device, a
voice communication device, or a multiple-mode device capable of
voice, data and other types of communications. An exemplary mobile
device 22 is described in further detail below and with reference
to FIG. 6.
[0034] Perhaps the most common We of messaging currently in use is
e-mail. In a standard e-mail system, an e-mail message is sent by
an e-mail sender, possibly through a message server and/or a
service provider system, and typically routed through the Internet
to one or more message receivers. E-mail messages are normally sent
unencrypted and use traditional Simple Mail Transfer Protocol
(SMTP), RFC822 headers and MIME body parts to define the format of
the e-mail message. As described briefly above, a message that is
routed to an addressed message receiver can be redirected to a
mobile device. Since a wireless link cannot be physically secured
in the same way as a wired connection, messages are often encrypted
for transfer through a wireless network. Overall message security
can be further enhanced if a secure transfer mechanism is also used
between the message sender and each recipient.
[0035] In recent years, secure messaging techniques have evolved to
protect both the content and integrity of messages such as e-mail
messages. S/MIME and Pretty Good Privacy.TM. (PGP.TM.) are two
public key secure e-mail messaging protocols that provide for both
encryption, to protect data content, and signing, which both
protects the integrity of a message and provides for sender
authentication by a message receiver. Secure messages may also be
encoded, compressed or otherwise processed in addition to being
encrypted and/or signed.
[0036] FIG. 2 is a block diagram illustrating a secure e-mail
message exchange in a messaging system. The system includes an
e-mail sender 30, coupled to a WAN 32 and a wireless gateway 34,
which provides an interface between the WAN 32 and a wireless
network 36. A mobile device 38 is adapted to operate within the
wireless network 36. Also shown in FIG. 2 are digital certificate
status information providers 35 and 37 and a proxy system 39, both
coupled to the WAN 32.
[0037] The e-mail sender 30 may be a PC, such as the system 14 in
FIG. 1, or may be a network-connected computer, such as a computer
system 28 in FIG. 1. The e-mail sender 30 may also be another
mobile device on which e-mail messages may be composed and sent.
The WAN 32, the wireless gateway 34, the wireless network 36, and
the mobile device 38 are substantially the same as similarly
labelled components in FIG. 1.
[0038] According to secure messaging schemes such as S/MIME and
PGP, a message is encrypted using a one-time session key chosen by
the e-mail sender 30. The session key is used to encrypt the
message body and is then itself encrypted using the public key of
each addressed message receiver to which the message is to be sent.
As shown at 40, a message encrypted in this way includes an
encrypted message body 44 and an encrypted session key 46. In this
type of message encryption scheme, a message sender such as e-mail
sender 30 must have access to the public key of each entity to
which an encrypted message is to be sent.
[0039] A secure e-mail message sender such as 30 normally signs a
message by taking a digest of the message and signing the digest
using the sender's private key. A digest may for example, be
generated by performing a check-sum, a Cyclic Redundancy Check
(CRC), a digest algorithm such as Message Digest Algorithm 5 (MD5),
a hash algorithm such as Secure Hashing Algorithm 1 (SHA-1), or
some other preferably non-reversible operation on the message. In
the example shown in FIG. 2, both the encrypted message body 44 and
the encrypted session key 46 are used to generate a digest. This
digest is then signed by the sender 30 using the sender's private
key. The signature private key is used for example to perform an
encryption or other transformation operation on the digest to
generate the digest signature. A digital signature, including the
digest and the digest signature, is then appended to the outgoing
message, as shown at 42. A digital certificate of the sender, which
includes the sender's public key and sender identity information
that is bound to the public key with one or more digital
signatures, and possibly any chained digital certificates and CRLs
associated with the sender's digital certificate and any chained
digital certificates, may also be attached to the secure message
40.
[0040] The secure e-mail message 40 sent by the e-mail sender 30
includes the digital signature 42, as well as the encrypted message
body 44 and the encrypted session key 46, both of which are signed.
In the MIME secure messaging technique, digital certificates, CRLs
and digital signatures are normally placed at the beginning of a
message, and the message body is included in a file attachment.
Messages generated by other secure messaging schemes may place
message components in a different order than shown or include
additional and/or different components. For example, a secure
message such as 40 may include addressing information, such as
"To:" and "From:" email addresses, and other header
information.
[0041] When the secure e-mail message 40 is sent from the e-mail
sender 30, it is routed through the WAN 32 to the wireless network
36 and the mobile device 38. The transmission path between the
e-mail sender 30 and the mobile device 38 may also include
additional or different components than those shown in FIG. 2. For
example, the secure e-mail message 40 may be addressed to a mailbox
or data store associated with a message server or data server which
has been wirelessly enabled to forward or send received messages
and data to the mobile device 38. Further intermediate systems may
also store and/or route the secure message to the mobile device 38.
The exemplary system as previously described and as disclosed in
U.S. Pat. No. 6,219,694 is an example of one such system.
[0042] In addition, the secure message 40 maybe routed or forwarded
to the mobile device 38 through other transport mechanisms than the
wireless gateway 34. For example, routing to the wireless network
36 may be accomplished using a wireless VPN router associated with
the e-mail sender 30, or, in the case of a message being received
at an intermediate computer system or server and then forwarded to
the mobile device 38, with the computer system or server.
[0043] Regardless of whether a signed message is sent directly to
the mobile device 38 or forwarded to the mobile device 38 by
intermediate systems or components, when a signed message is
received, the mobile device 38 may verify the digital signature 42.
In order to verify the digital signature 42, the mobile device 38
uses a digital signature check algorithm corresponding to the
signature generation algorithm used by the message sender, which
may be specified in a message header or in the digital signature
42, and the sender's public key. If a secure message includes the
sender's digital certificate, then the sender's public key may be
extracted from the digital certificate. The sender's public key may
instead be retrieved from a local store, for example, where the
public key was extracted from an earlier message from the sender
and stored in a key store in the receivers local store or the
sender's digital certificate is stored in the local store, or from
a Public Key Server (PKS). A PKS is a server that is normally
associated with a Certificate Authority (CA) from which a digital
certificate for an entity, including the entity's public key, is
available. A PKS might reside within a corporate LAN such as LAN 18
of FIG. 1, or anywhere on the WAN 32, Internet or other network or
system through which message receivers may establish communications
with the PKS.
[0044] Although digital signature algorithms and digest algorithms
may be publicly known, a sender signs an original message using its
own private key. Therefore, an entity that alters an original
message cannot generate a digital signature that can be verified
with the sender's public key. If a sent message is altered by an
attacker after it has been signed by a sender, then the digital
signature verification based on the sender's public key fails.
These mathematical operations do not prevent anyone from seeing the
contents of the secure message, but do ensure that the message has
not been tampered with because it was signed by the sender, and
that the message was signed by the person as indicated in the
"From" field of the message.
[0045] When the digital signature 42 has been verified, or
sometimes even if digital signature versification fails, the
encrypted message body 44 is then decrypted before it can be
displayed or further processed by a receiving messaging client
operating on the mobile device 38 in FIG. 2. A receiving messaging
client uses its private key to decrypt the encrypted session key 46
and then uses the decrypted session key to decrypt the encrypted
message body 44 and thereby recover the original message. Those
skilled in the art will appreciate that an entity may have more
than one associated cryptographic key pair, such as a signature
private/public key pair and an encryption private/public key pair.
Thus, the mobile device 38 may use one private key to decrypt the
encrypted message body 44, and a different private key to digitally
sign an outgoing secure message.
[0046] An encrypted message that is addressed to more than one
receiver includes an encrypted version of the session key, for each
receiver, that was encrypted using the public key of the receiver.
Each receiver performs the same digital signature verification
operations, but decrypts a different one of the encrypted session
keys using its own private key.
[0047] Therefore, in a secure messaging system, a sending messaging
client should have access to the public key of any receiver to
which an encrypted message is to be sent. A receiving messaging
client should be able to retrieve the senders public key, which may
be available to a messaging client through various mechanisms, in
order to verify a digital signature in a signed message. Although
the mobile device 38 is a receiver of the secure message 40, the
mobile device 38 may be enabled for two-way communications, and may
therefore access public keys for both message sending and message
receiving operations.
[0048] Public keys are commonly provided in digital certificates.
As described above, a digital certificate for any particular entity
typically includes the entity's public key and identification
information that is bound to the public key with a digital
signature. Several types of digital certificates are currently in
widespread use, including for example X.509 digital certificates
which are typically used in S/MIME. PGP uses digital certificates
with a slightly different format. Systems and methods discussed
herein may be used with any of these types of digital certificate,
as well as other types of digital certificates, both currently
known types as well as others that may be developed in the future.
The digital signature in a digital certificate is generated by the
issuer of the digital certificate, and can be checked by a message
receiver substantially as described above. A digital certificate
sometimes includes an expiry time or validity period from which a
messaging client may determine if the digital certificate has
expired. Verification of the validity of a digital certificate may
also involve tracing a certification path through a digital
certificate chain, which includes a user's digital certificate as
well as other digital certificates to verity that the user's
digital certificate is authentic.
[0049] A digital certificate may also be checked to ensure that it
has not been revoked. As described above, digital certificate
revocation status may be checked by consulting a CRL or by
requesting digital certificate status information from a digital
certificate revocation status information source. In the system of
FIG. 2, a user of the mobile device 38 may submit a revocation
status request for any digital certificate stored at the mobile
device 38 to one of the status information providers 35 and 37. The
provider 35 or 37 then returns revocation status information for
that digital certificate to the mobile device 38. In order to query
both of the status providers 35 and 37, a separate request is sent
to each status provider.
[0050] Online Certificate Status Protocol (OCSP) is one scheme that
provides for determination of digital certificate revocation status
without requiring CRLs. Versions of OCSP have been defined, for
example, in RFC 2560 and in the Internet Draft "Online Digital
Certificate Status Protocol, version 2", both available from the
Internet Engineering Task Force (IETF). OCSP is one of the most
widely used digital certificate revocation status check protocols
and is therefore used herein as an illustrative example of such
schemes. The systems and methods described herein, however, may
also be applicable to other types of digital certificate revocation
status checking schemes involving retrieval of revocation status
information from remote sources.
[0051] According to OCSP, a request is submitted to a status
information provider, generally referred to as an OCSP responder.
Upon receipt of a properly formatted request, an OCSP responder
returns a response to the requestor. An OCSP request includes at
least an OCSP protocol version number, a service request, and an
identification of a target digital certificate to which the request
is related.
[0052] The version number identifies the version of OCSP with which
the request complies. The service request specifies the type of
service being requested. For OCSP version 2, Online Revocation
Status (ORS), Delegated Path Validation (DPV) and Delegated Path
Discovery (DPD) services have been defined. Through the ORS
service, a messaging client may obtain revocation status
information for digital certificates. The DPV and DPD services
effectively delegate digital certificate validation path-related
processing to a remote system.
[0053] Normally, a target digital certificate is identified in an
OCSP request using a hash of the distinguished name (ON) of the
issuer of the digital certificate, as well as the serial number of
the digital certificate. However, since multiple digital
certificate issuers may use the same ON further identification
information, in the form of a hash of the issuer's public key, is
also included in the request. Therefore, target digital certificate
information in an OCSP request includes a hash algorithm
identifier, a hash of the ON of the digital certificate issuer
generated using the hash algorithm, a hash of the issuer's public
key, also generated using the hash algorithm, and the serial number
of the target digital certificate.
[0054] The request may or may not be signed by a requester. Further
optional information may also be included in a request and
processed by an OCSP responder.
[0055] When a messaging client is operating on a mobile device,
OCSP may be desirable in that it reduces the processing and memory
resources necessary to check revocation status of a digital
certificate relative to CRL-based revocation status checking.
However, OCSP requests can be relatively long and thereby consume
limited wireless communication resources. Request overhead can be
particularly large when requests are submitted to more than one
status provider, for example when an error message is returned in
response to a request to a status provider. The proxy system 39, in
conjunction with an appropriately enabled mobile device 38, or
possibly any other system on which a messaging client operates, may
be used to optimize OCSP and similar protocols for multiple remote
systems, as described in further detail below.
[0056] FIG. 3 is a block diagram of a system which supports
multiple digital certificate status information providers. The
mobile device 38 includes a memory 52, a messaging system 60, a
proxy system client module 62, a user interface (UI) 64, and a
wireless transceiver 65. The memory 52 includes a storage area for
a digital certificate store 54, as well as data stores such as an
address book 56 in which messaging contact information is stored,
and an application data store 58 which stores data associated with
software applications on the mobile device 38. Data stores 56 and
58 are illustrative examples of stores that may be implemented in a
memory 52 on mobile device 38. The memory 52 may also be used by
other device systems in addition to those shown in FIG. 3 to store
other types of data.
[0057] The memory 52 is illustratively a writable store such as a
RAM into which other device components may write data. The digital
certificate store 54 is a storage area that is dedicated to storage
of digital certificates on the mobile device 38. Digital
certificates may be stored in the digital certificate store 54 in
the format in which they are received, or may alternatively be
parsed or otherwise translated into a storage format before being
written to the store 54.
[0058] The messaging system 60 is connected to the wireless
transceiver 65 and is thus enabled for communications via a
wireless network. The messaging system 60 may be a messaging client
embodied in a software application.
[0059] The proxy system client module 62, which may be implemented
as a software application or component, may be coupled to the
messaging system 60, the digital certificate store 54, and the
mobile device's UI 64, as shown. Revocation status for any of the
digital certificates stored in the digital certificate store 54, or
those received by the messaging system 60 but not yet stored in the
digital certificate store 54, may be checked using the proxy system
client module 62.
[0060] The UI 64 may include such UI components as a keyboard or
keypad, a display, or other components which accept inputs from or
provide outputs to a user of the mobile device 38. Although shown
as a single block in FIG. 3, a mobile device 38 typically includes
more than one UI, and the UI 64 therefore represents one or more
user interfaces.
[0061] The wireless network 36, the wireless gateway 34, the WAN
32, and the status information providers 35 and 37 are
substantially the same as similarly-labelled components in FIG.
2.
[0062] The proxy system 39 includes a proxy system service module
or component 68 and status provider client modules 66 and 67. The
proxy system service component 68 is configured to exchange
information with the proxy system client module 62, and the status
provider client modules 66 and 67 are respectively adapted to
exchange information with the status information providers 35 and
37. The status provider client modules 66 and 67 and the proxy
system service module 68 are preferably software applications or
modules operating at the proxy system 39. These software
applications may be a single program, or may alternatively be
separate programs executed independently.
[0063] In operation, the messaging system 60 on the mobile device
38 receives and possibly sends secure messages via the wireless
network 36 as described above. When a signature on a received
secure message is to be verified or a message is to be sent with an
encrypted session key, the messaging system 60 may retrieve a
public key for an entity (i.e., a sender of a received message or a
recipient of a message to be sent) from a digital certificate or a
key store on the mobile device 38. Before the public key is used,
however, the messaging system 60 or a user thereof may wish to
check that a digital certificate containing the public key is valid
and has not been revoked.
[0064] Digital certificate checking operations may be performed
automatically, when a digital certificate is received, for example,
periodically, at predetermined or user-configurable intervals, or
when invoked by a user through a UI 64. Different types of digital
certificate checking operations may also be dependent upon
different controls. For instance, where the validity and revocation
status of a digital certificate is checked when the digital
certificate is first loaded onto the mobile device 38, the digital
certificate may be assumed to be valid until an expiry time or
during a validity period specified in the digital certificate.
However, its revocation status may thereafter be checked once every
week.
[0065] As described above, digital certificate status information
requests to a remote information provider such as 35 or 37 may be
relatively long and are therefore not optimal for implementation in
a mobile device 38 or other bandwidth-limited communication
systems. Time delays and data transfers involved in submitting
requests to each of multiple status information providers can be
undesirable even for less constrained systems. The proxy system
client module 62 and service module 68 are preferably adapted to
gather digital certificate status request information which is used
to request status information for a digital certificate from all
known status information providers.
[0066] When a user of the mobile device 38 wishes to check the
revocation status of a digital certificate, for example, the proxy
system client module 62, or possibly a software application which
operates in conjunction with the proxy system client module 62, may
be invoked, by entering an appropriate command on a UI 64 such as a
keyboard. The user may also specify the particular digital
certificate to be checked, for instance using the serial number or
subject name of the digital certificate. Alternatively, the proxy
system client module 62 may access the digital certificate store 54
to display to the user a list of currently stored digital
certificates, from which the user may select one or more digital
certificates to be checked.
[0067] The proxy system client module 62 then preferably either
extracts from the selected digital certificates) or obtains from
the user through a UI 64, any information required by the proxy
system service module 68 for a digital certificate revocation
status check. Since the proxy system 39 provides an interface
between the mobile device 38 and the status information providers
35 and 37, requests and responses between the proxy system client
module 62 and proxy system service module 68 need not conform to
the protocol used between the status provider client modules 66 and
67 and the respective status information providers 35 and 37.
Therefore, although the status providers 35 and 37 and client
modules 66 and 67 may support OCSP or a similar protocol, the proxy
system service module 68 and client module 62 may support a more
compact protocol involving less data exchange.
[0068] The particular information extracted or obtained by the
proxy system client module 62 is dependent upon the communication
protocol implemented between the proxy system client module 62 and
service module 68. The proxy system client module 62 can preferably
extract a digital certificate subject name, serial number, issuer
name, and other digital certificate information from a digital
certificate in the digital certificate store 54. If digital
certificates are first parsed and then parsed data is stored in the
digital certificate store 54, then such information may be
extracted from the parsed data in the digital certificate store 54
by the proxy system client module 62. If further information is
required, a user may be prompted to enter the information. For
example, if the proxy system 39 is configured to store a mapping
table or like element which maintains a correspondence between
digital certificate issuers and serial numbers and/or subject
names, then the status provider client modules 66 and 67 may format
requests for the status information providers 35 and 37 based on
only a serial number or subject name received by the proxy system
service module 68 from the proxy system client module 62.
[0069] The proxy system client module 62 preferably gathers all
information that is required for requests to any of the status
information providers 35 and 37. When all required information has
been extracted or otherwise obtained by the proxy system client
module 62, a request is formatted and sent to the proxy system
service module 68. The content of this request is also dependent
upon the communication protocol used between the proxy system
service module 68 and client module 62. If more than one type of
service is supported, then the request may specify which type of
service is requested. In some implementations, only a single
service may be supported, such that no service type need be
specified.
[0070] Information received by the proxy system service module 68
is preferably passed to each status provider client module 66 and
67. This information is then used by the status provider client
modules 66 and 67 to format a request for the respective status
information providers 35 and 37. If the revocation status
information providers 35 and 37 and status provider client modules
66 and 67 support OCSP for example, information provided by the
proxy system service module 68, as well as any further required
information, are formatted into an OCSP requests. In some cases,
the information provided by the proxy system service module 68 may
include all required information, whereas in other cases, further
information may be extracted from other sources, such as the above
example mapping table and included in the requests to the status
information providers 35 and 37.
[0071] Since the status provider client modules 66 and 67 may
support different protocols or require different information for
service requests, each provider may extract or use different
information provided in the initial service request received by the
proxy system service module 68. For example, if the provider client
module 66 requires only a subset of the information required by the
provider client module 67, then each status provider client module
66, 67 preferably extracts the information it requires from the
initial request or retrieves the information it requires from the
initial request, or from a version of the initial request, or
parsed data extracted therefrom, stored to a data store at the
proxy system 39. Alternatively, the proxy system service module 68
is configured to pass any required information to each provider
client module 66 and 67. The length of the initial request may then
be further reduced by configuring the proxy system client module 62
to include any information required by the provider client modules
66 and 67 in the initial request only once. Redundancy in, and thus
the length of the initial request is thereby reduced, since common
information required by more than one provider client module
appears in the initial request only once, but can be extracted or
retrieved by, or passed to, each provider client module 66 and
67.
[0072] Thus, the proxy system 39 requests digital certificate
status information from multiple status information providers for
which a provider client module has been implemented, responsive to
a single initial request to the proxy system 39. According to known
techniques, separate requests are submitted to each status
information provider 35 and 37 by the mobile device 38
[0073] A determination of the particular status information
providers to which a request will be sent in response to an initial
request from the mobile device 38 may be made in any of several
ways. A proxy system 39 may send a request to every status
information provider for which a provider client module has been
implemented, or possibly to each status information provider in a
default list stored at the proxy system 39. Similarly, a default,
possibly user-configurable, list of status information providers
may be stored at the mobile device 38 and included in the initial
request sent from the mobile device 38. In this case, the proxy
system 39 may store the default list received in an initial request
from the mobile device 38, and then use the default list for
subsequent initial requests from the mobile device 38, until a new
default list for the mobile device 38 is received. Alternatively, a
user may select or specify status information providers to be used
to provide the requested service. User-selected or specified status
information providers in an initial request may over-ride any
default list of status information providers. Preferred status
information providers may also be included in each digital
certificate stored in the digital certificate store 54 or received
by the mobile device 38 and submitted to the proxy system service
module 68 when such a digital certificate is a target digital
certificate in an initial request.
[0074] In FIG. 3, the status provider 37 may support an ORS or like
service. Upon receiving a request, each status information provider
35 and 37, which will be OCSP responders when the providers 35 and
37 and client modules 66 and 67 support OCSP, checks the request to
ensure that it is formatted properly, that the requested service is
a service that it is configured to provide, and that the request
includes all of the information required for the requested service.
If these conditions are not met, then a provider 35 or 37 may
return an error message to its client module 66 or 67. Each client
module 66 and 67 may then perform error processing if it is so
configured, including such operations as providing any missing
required information, requesting missing information from the
mobile device 38 through the proxy system service module 68, or
returning an error message to the proxy system service module 68.
Responsive to an error message from a client module 66 or 67, the
proxy system service module 68 preferably formats and sends an
error message to the proxy system client module 62 as a response to
its initial service request. Other conditions, such as when a
provider 35 or 37 receives an unsigned request but is configured to
expect signed requests, or when a provider service is unable to
respond, may also result in an error message being returned to a
provider client module 66 or 67. Since digital certificate status
information is requested from multiple status information providers
35 and 37 however, error processing may possibly be invoked only
when all status information providers 35 and 37 to which requests
have been sent return an error message.
[0075] If the request meets the above conditions, then a so-called
"definitive" response is returned to the corresponding provider
client module 66 or 67. A definitive response typically includes
one of a plurality of status indications, such as a "valid" or like
indication when a target digital certificate has not been revoked,
a "revoked" indication when the target digital certificate has been
revoked, or an "unknown" indication if the status provider 35 or 37
has no record or knowledge of the target digital certificate.
[0076] Since a request is sent to each status information, provider
35 and 37, responses may be received by more than one of the
provider client modules 66 and 67. Any responses are preferably
passed to the proxy system client module 68, which selects one of
the responses to be used in preparing a response that will be
returned to the proxy system client module 62 on the mobile device
38. In this configuration, the proxy system service module 68 uses
the first definitive response to prepare a response to the proxy
system client module 62. If no definitive response is received,
then an error or similar response may be prepared by the proxy
system service module 68 and returned to the proxy system client
module 62 to indicate this result. Other selection criteria,
including a status information provider ranking list, for example,
may also be used to control which one of multiple responses will be
returned to the proxy system client module 62 or used to prepare a
response to the proxy system client module 62. Such a ranking may
be established at the proxy system 39 or at the mobile device 38,
or specified in a digital certificate. Relative ranking may also be
inherent in the ordering of status information providers in a list
that is used to control the particular status information providers
to which requests will be sent by the proxy system 39, as described
above.
[0077] When a selected response from one of the status information
providers 35 and 37 is signed, and the proxy system client module
62 or another component on the mobile device 38 is configured to
verify digital signatures on status responses, then the entire
selected response, or possibly only the signed portions thereof,
may be forwarded to the proxy system client module 62 substantially
unchanged. If only portions of a response are signed, then unsigned
portions of the response are preferably removed by the proxy system
service module 68 to reduce the size of the response sent to the
proxy system client module 62 via the wireless network 36. However,
if the proxy system service module 68 or the status provider client
module 66 checks status response signatures on behalf of the mobile
device 38, then certain parts of the response, for example the
status indication and the digital certificate serial number or
subject name, may be extracted by the proxy system service module
68 and formatted into a response that is then sent to the proxy
system client module 62. The response from the proxy system service
module 68 is then processed by the proxy system client module 62 or
possibly another component on the mobile device 38 to determine
whether or not the digital certificate has been revoked.
[0078] The presence of a proxy system client module 62 preferably
does not preclude digital certificate validity and revocation
status checks according to known techniques. Thus, digital
certificate status checks involving remote systems such as the
status information providers 35 and 37 may be complementary to
other status check operations.
[0079] FIG. 4 is a flow diagram illustrating a method of supporting
multiple digital certificate status information providers. At step
80, any digital certificates for which a status check is to be
performed are identified. As described above, this step could be
performed automatically or the digital certificates could be
selected by a user. An initial request is then prepared and sent to
the proxy system at step 82. In some instances, the initial request
includes a list of status information providers to which a request
should be sent, and possibly a ranking list that specifies an order
of preference between subsequent responses from different status
providers. As described above, a list of status information
providers may be arranged in order of preference to provide both
status information provider information and preference
information.
[0080] At step 84, status information provider client modules at
the proxy system prepare and send service requests to each status
information provider, such as an OCSP responder. Each status
information provider then checks its request to ensure that it is
formatted properly, that the requested service, digital certificate
revocation status in this example, is supported by the provider,
and that all required information is included in the request. These
checks are performed by each status information provider at step
86.
[0081] If the request does not satisfy these conditions, then an
error message is returned to the proxy system at step 88. Error
processing may then be executed at step 90, to obtain further
information when the request does not include all required
information, for example, after which a new service request may be
prepared and sent to the provider at step 84.
[0082] When the request satisfies the conditions in step 86, the
status information provider returns a status indication to the
proxy system at step 92, in response to the service request from
the proxy system. The steps 86, 88 and 92 are preferably performed
by each status information provider to which a request has been
sent at step 84.
[0083] At step 94, the proxy system selects one of the responses to
be used in preparing a response to the requestor, the mobile device
38 in FIG. 3, for example. As described above, the first definitive
response is selected, or other selection criteria may be applied.
The selected response, or at least parts thereof, is then returned
to the requestor, as a response to the initial service request, at
step 96.
[0084] Although the system and method described above relate to the
illustrative example of digital certificate revocation status
checking, digital certificate validity checks, according to the DPV
and DPD services of OCSP or other protocols, for example, may
similarly be optimized for multiple status information providers
through a proxy system client module and service module. A proxy
system may also be enabled to provide its proxy service to multiple
mobile devices, and a mobile device may be configured to
communicate with more than one proxy system.
[0085] In another embodiment, a mobile device 100 and proxy system
128 include multiple client and service modules, FIG. 5 is a block
diagram of a system having multiple proxy system client modules
which support multiple digital certificate status information
providers. In FIG. 5, the memory 102, the data stores 104, 106, and
108, the messaging system 110, the UI 114, the wireless transceiver
116, the wireless network 118, the wireless gateway 120, and the
WAN 122 are substantially the same as similarly labelled components
in FIG. 3.
[0086] The mobile device 100 includes N client modules 112,
including the proxy system client module A 113 and the proxy system
client module N 111. The proxy system 128 includes corresponding
proxy system service modules A and N, 132 and 136. It should be
appreciated that other proxy system client modules on the mobile
device 100 may be supported by other proxy system service modules
in the proxy system 128, or by proxy system service modules in
other proxy systems. The proxy system 128 also includes status
provider client modules A and N, 130 and 134, which are configured
for communications with the status information provider A 126 and
the status information provider N 124, respectively.
[0087] The system shown in FIG. 5 operates substantially as
described above. When the status of one or more digital
certificates, such as revocation status for example, is to be
checked, each proxy system client module 113 and 111 preferably
extracts or otherwise obtains information required in a service
request to its respective proxy system service module 132 and 136.
The status provider client modules 130 and 134 then use the
information from the service request from the mobile device 100,
and possibly information available at the proxy system 128, to
prepare a service request to status information providers 126 and
124. The proxy system service modules 132 and 136, or possibly
another component of the proxy system 128 are preferably configured
such that only one of the responses returned by the status
information providers 126 and 124, or at least portions thereof, is
reformatted if necessary and returned to the proxy system client
modules 113 and 111 at the mobile device 100. One of the responses
may be selected according to any of the schemes described
above.
[0088] Each proxy system client module 113 and 111 may be adapted
to collect request information and process response information for
a different remote digital certificate status check protocol.
However, the information collected by both proxy system client
modules 113 and 111 may be combined into a single initial request
to the proxy system 128. Each proxy system service module 132 and
136 then extracts information from the service request required for
a service request to its associated status information provider 126
and 124.
[0089] A multiple-client module system such as shown in FIG. 5 is
particularly useful when a user wishes to check validity and/or
revocation status of an entire digital certificate chain which
includes digital certificates for which status information is
available from different status information providers. In known
systems, separate requests for each digital certificate in the
chain must be sent to the status information providers. In the
system of FIG. 5 however, only a single request need be sent from
the mobile device 100 to obtain status information from any number
of status information providers.
[0090] FIG. 6 is a block diagram of a wireless mobile communication
device. The mobile device 600 is preferably a two-way communication
device having at least voice and data communication capabilities.
The mobile device 600 preferably has the capability to communicate
with other computer systems on the Internet. Depending on the
functionality provided by the mobile device, the mobile device may
be referred to as a data messaging device, a two-way pager, a
mobile telephone with data messaging capabilities, a wireless
Internet appliance, or a data communication device (with or without
telephony capabilities). As mentioned above, such devices are
referred to generally herein simply as mobile devices.
[0091] The mobile device 600 includes a transceiver 611, a
microprocessor 638, a display 622, a Flash memory 624, a random
access memory (RAM) 626, auxiliary input/output (I/O) devices 628,
a serial port 630, a keyboard 632, a speaker 634, a microphone 636,
a short-range wireless communications sub-system 640, and other
device sub-systems 642. The transceiver 611 includes transmit and
receive antennas 616, 618, a receiver (Rx) 612, a transmitter (Tx)
614, one or more local oscillators (LOs) 613, and a digital signal
processor (DSP) 620. Within the Flash memory 624, the mobile device
600 includes a plurality of software modules 624A-624N that can be
executed by the microprocessor 638 (and/or the DSP 620), including
a voice communication module 624A, a data communication module
6248, and a plurality of other operational modules 624N for
carrying out a plurality of other functions.
[0092] The mobile device 600 is preferably a two-way communication
device having voice and data communication capabilities. Thus, for
example, the mobile device 600 may communicate over a voice
network, such as any of the analog or digital cellular networks,
and may also communicate over a data network. The voice and data
networks are depicted in FIG. 6 by the communication tower 619.
These voice and data networks may be separate communication
networks using separate infrastructure, such as base stations,
network controllers, etc., or they may be integrated into a single
wireless network, References to the network 619 should therefore be
interpreted as encompassing both a single voice and data network
and separate networks.
[0093] The communication subsystem 611 is used to communicate with
the network 619. The DSP 620 is used to send and receive
communication signals to and from the transmitter 614 and receiver
612, and may also exchange control information with the transmitter
614 and receiver 612. If the voice and data communications occur at
a single frequency, or closely-spaced set of frequencies, then a
single LO 613 may be used in conjunction with the transmitter 614
and receiver 612. Alternatively, if different frequencies are
utilized for voice communications versus data communications, then
a plurality of LOs 613 can be used to generate a plurality of
frequencies corresponding to the network 619. Although two antennas
616, 618 are depicted in FIG. 6, the mobile device 600 could be
used with a single antenna structure. Information, which includes
both voice and data information, is communicated to and from the
communication module 611 via a link between the DSP 620 and the
microprocessor 638.
[0094] The detailed design of the communication subsystem 611, such
as frequency band, component selection, power level, etc., will be
dependent upon the communication network 619 in which the mobile
device 600 is intended to operate. Far example, a mobile device 600
intended to operate in a North American market may include a
communication subsystem 611 designed to operate with the Mobitex or
DataTAC mobile data communication networks and also designed to
operated with any of a variety of voice communication networks,
such as AMPS, TDMA, CDMA, PCS, etc. a mobile device 600 intended
for use in Europe may be configured to operate with the GPRS data
communication network and the GSM voice communication network.
Other types of data and voice networks, both separate and
integrated, may also be utilized with the mobile device 600.
[0095] Depending upon the type of network 619, the access
requirements for the mobile device 600 may also vary. For example,
in the Mobitex and DataTAC data networks, mobile devices are
registered on the network using a unique identification number
associated with each device. In GPRS data networks, however,
network access is associated with a subscriber or user of the
mobile device 600, A GPRS device typically requires a subscriber
identity module ("SIM"), which is required in order to operate the
mobile device 600 on a GPRS network. Local or non-network
communication functions (if any) may be operable, without the SIM,
but the mobile device 600 will be unable to carry out any functions
involving communications over the network 619, other than any
legally required operations, such as `911` emergency calling.
[0096] After any required network registration or activation
procedures have been completed, the mobile device 600 may send and
receive communication signals, preferably including both voice and
data signals, over the network 619. Signals received by the antenna
616 from the communication network 619 are routed to the receiver
612, which provides for such operations as signal amplification,
frequency down conversion, filtering, channel selection, and analog
to digital conversion. Analog to digital conversion of the received
signal allows more complex communication functions, such as digital
demodulation and decoding to be performed using the DSP 620. In a
similar manner, signals to be transmitted to the network 619 are
processed, including modulation and encoding, for example, by the
DSP 620 and are then provided to the transmitter 614 for digital to
analog conversion, frequency up conversion, filtering,
amplification and transmission to the communication network 619 via
the antenna 618. Although a single transceiver 611 is shown in FIG.
6 for both voice and data communications, it is possible that the
mobile device 600 may include two distinct transceivers, a first
transceiver for transmitting and receiving voice signals, and a
second transceiver for transmitting and receiving data signals.
Multiple transceiver may also be provided in a mobile device
adapted to operate within more than one communication network or
multiple frequency bands.
[0097] In addition to processing the communication signals, the DSP
620 also provides for receiver and transmitter control. For
example, the gain levels applied to communication signals in the
receiver 612 and transmitter 614 may be adaptively controlled
through automatic gain control algorithms implemented in the DSP
620. Other transceiver control algorithms could also be implemented
in the DSP 620 in order to provide more sophisticated control of
the transceiver 611.
[0098] The microprocessor 638 preferably manages and controls the
overall operation of the mobile device 600. Many types of
microprocessors or microcontrollers could be used here, or
alternatively, a single DSP 620 could be used to carry out the
functions of the microprocessor 638. Low-level communication
functions, including at least data and voice communications, are
performed through the DSP 620 in the transceiver 611. Other,
high-level communication applications, such as a voice
communication application 624A, and a data communication
application 624B are stored in the Flash memory 624 for execution
by the microprocessor 638. For example, the voice communication
module 624A may provide a high-level user interface operable to
transmit and receive voice calls between the mobile device 600 and
a plurality of other voice devices via the network 619. Similarly,
the data communication module 624B may provide a high-level user
interface operable for sending and receiving data such as e-mail
messages, files, organizer information, short text messages, etc.,
between the mobile device 600 and a plurality of other data devices
via the network 619. On the mobile device 600, a secure messaging
software application, incorporating software modules corresponding
to the messaging system 60 and the proxy system client module 62 or
client modules 113 and 111, for example, may operate in conjunction
with the data communication module 624B in order to implement the
techniques described above.
[0099] The microprocessor 638 also interacts with other device
subsystems, such as the display 622, the Flash memory 624, the RAM
626, the auxiliary input/output (I/O) subsystems 628 the serial
port 630, the keyboard 632, the speaker 634, the microphone 636,
the short-range communications subsystem 640, and any of the other
device subsystems generally designated as 642. For example, the
modules 624A-N are executed by the microprocessor 638 and may
provide a high-level interface between a user and the mobile device
600. This interface typically includes a graphical component
provided through the display 622, and an input/output component
provided through the auxiliary I/O 628, the keyboard 632, the
speaker 634, or the microphone 636. Such interfaces are designated
generally as UI 64 and 114 in FIGS. 3 and 5, respectively.
[0100] Some of the subsystems shown in FIG. 6 perform
communication-related functions, whereas other subsystems may
provide "resident" or on-device functions. Notably, some
subsystems, such as the keyboard 632 and the display 622 are used
for both communication-related functions such as entering a text
message for transmission over a data communication network, and
device-resident functions such as a calculator or task list or
other PDA type functions.
[0101] Operating system software used by the microprocessor 638 is
preferably stored in a non-volatile store such as Flash memory 624.
In addition to the operating system and communication modules
624A-N, the Flash memory 624 may also include a file system for
storing data. A storage area is also preferably provided in the
Flash memory 624 to store digital certificates, address book
entries and possibly other information required for messaging,
shown as data stores 54, 56, and 58 in FIG. 3 or the data stores
104, 106, and 108 in FIG. 5. The operating system, specific device
applications or modules, or parts thereof, may be temporarily
loaded into a volatile store, such as RAM 626 for faster operation.
Moreover, received communication signals may also be temporarily
stored to RAM 626, before permanently writing them to a file system
located in the Flash memory 624.
[0102] An exemplary application module 624N that may be loaded onto
the mobile device 600 is a personal information manager (PIM)
application providing PDA functionality, such as calendar events,
appointments, and task items. This module 624N may also interact
with the voice communication module 624A for managing phone calls,
voice mails, etc., and may also interact with the data
communication module 624B for managing e-mail communications and
other data transmissions. Alternatively, all of the functionality
of the voice communication module 624A and the data communication
module 6248 may be integrated into the PIM module.
[0103] The Flash memory 624 preferably provides a file system to
facilitate storage of PIM data items on the device. The PIM
application preferably includes the ability to send and receive
data items, either by itself, or in conjunction with the voice and
data communication modules 624A and 624B, via the wireless network
619. The PIM data items are preferably seamlessly integrated,
synchronized and updated, via the wireless network 619, with a
corresponding set of data items stored or associated with a host
computer system, thereby creating a mirrored system for data items
associated with a particular user.
[0104] Although shown as a Flash memory 624, those skilled in the
art will appreciate that other types of non-volatile store, such as
a battery backed-up RAM, for example, could be used in addition to
or instead of the Flash memory 624.
[0105] The mobile device 600 may also be manually synchronized with
a computer system by placing the mobile device 600 in an interface
cradle, which couples the serial port 630 of the mobile device 600
to the serial port of the computer system. The serial port 630 may
also be used to enable a user to set preferences through an
external device or software application, to download other
application modules 624N for installation, and possibly to load
digital certificates onto a mobile device. This wired download path
may further be used to load an encryption key onto the device,
which is a more secure method than exchanging encryption
information via the wireless network 619.
[0106] Additional application modules 624N may be loaded onto the
mobile device 600 through the network 619, through an auxiliary I/O
subsystem 628, through the serial port 630, through the short-range
communications subsystem 640, or through any other suitable
subsystem 642, and installed by a user in the Flash memory 624 or
RAM 626. Such flexibility in application installation increases the
functionality of the mobile device 600 and may provide enhanced
on-device functions, communication-related functions, or both. For
example, secure communication applications may enable electronic
commerce functions and other such financial transactions to be
performed using the mobile device 600.
[0107] When the mobile device 600 is operating in a data
communication mode, a received signal, such as a text message or a
web page download, is processed by the transceiver 611 and provided
to the microprocessor 638, which preferably further processes the
received signal for output to the display 622, or, alternatively,
to an auxiliary I/O device 628. A digital certificate received by
the transceiver 611, in response to a request to a PKS or attached
to a secure message, for example, may be added to a digital
certificate store in the Flash memory 624 if it has not already
been stored. Validity and/or revocation status of such a digital
certificate may also be checked as described above. A user of
mobile device 600 may also compose data items, such as e-mail
messages, using the keyboard 632, which is preferably a complete
alphanumeric keyboard laid out in the QWERTY style, although other
styles of complete alphanumeric keyboards such as the known DVORAK
style may also be used. User input to the mobile device 600 is
further enhanced with a plurality of auxiliary I/O devices 628,
which may include a thumbwheel input device, a touchpad, a variety
of switches, a rocker input switch, etc. The composed data items
input by the user may then be transmitted over the communication
network 619 via the transceiver 611.
[0108] When the mobile device 600 is operating in a voice
communication mode, the overall operation of the mobile device 600
is substantially similar to the data mode, except that received
signals are preferably output to the speaker 634 and voice signals
for transmission are generated by a microphone 636. In addition,
the secure messaging techniques described above might not
necessarily be applied to voice communications. Alternative voice
or audio I/O subsystems, such as a voice message recording
subsystem, may also be implemented on the mobile device 600.
Although voice or audio signal output is preferably accomplished
primarily through the speaker 634, the display 622 may also be used
to provide an indication of the identity of a calling party, the
duration of a voice call, or other voice call related information.
For example, the microprocessor 638, in conjunction with the voice
communication module 624A and the operating system software, may
detect the caller identification information of an incoming voice
call and display it on the display 622.
[0109] The short-range communications subsystem 640 may include an
infrared device and associated circuits and components, or a
short-range wireless communication module such as a Bluetooth.TM.
module or an 802.11 module to provide for communication with
similarly-enabled systems and devices. Those skilled in the art
will appreciate that "Bluetooth" and "802.11" refer to sets of
specifications, available from the Institute of Electrical and
Electronics Engineers, relating to wireless personal area networks
and wireless LANs, respectively.
[0110] It will be appreciated that the above description relates to
preferred embodiments by way of example only, as many other
variations and examples may occur to those skilled in the art. For
example, although digital certificate status checking according to
aspects of the system and method are described primarily in the
context of a wireless mobile communication device, the system and
method are also applicable to messaging clients operating on other
platforms, including those operating on desktop and laptop computer
systems, networked computer workstations and other types of
messaging clients for which digital certificate checks involving
remote systems may be desired.
[0111] The above description also relates primarily to OCSP,
although other protocols may similar be optimized through an
intermediate proxy system which operates in conjunction with both
remote systems and proxy system client modules. Such other
protocols are not limited to digital certificate status check
protocols. A proxy system and proxy system client modules may be
configured to provide other services than digital certificate
status check services.
[0112] FIG. 7 is a block diagram illustrating a multiple messaging
scheme utilizing an intermediate computer system. As shown in FIG.
7, the proxy system may in general be an intermediate computer
system 700 disposed between the mobile device 702 and status
information providers (704, 706, 708). The intermediate computer
system 700 exchanges data with the mobile device 702 and status
information providers (704, 706, 708) via network connections 710,
712. In addition to data communications, the intermediate computer
system 700 may perform proxy server functions, such as security,
administrative control, and caching.
[0113] The intermediate computer system 700 uses a status
information provider data structure 720 in determining which status
information providers are to receive a service request. A service
request asks a status information provider to provide the status
information. The data structure 720 may be populated with provider
information that was sent by the mobile device 702. There are many
other ways for populating the data structure 720 with provider
information. For example, a mapping table may be stored in the data
structure 720 which maintains a correspondence between digital
certificate issuers and serial numbers and/or subject names. In
this example, the intermediate computer system 700 may format
requests for the status information providers based on only a
serial number or subject name sent from the mobile device 702.
[0114] A service message handler 730 is used by the intermediate
computer system 700 to generate multiple service requests 732 based
upon a request received from the mobile device 702. Each of the
generated service requests corresponds to a status information
provider and asks for status information from a provider. At least
one of the responses from the status information providers (704,
706, 708) is used in reply to the mobile device's request for
status information.
[0115] Still further examples of the wide scope of the systems and
methods disclosed herein are illustrated in FIGS. 8-10. FIGS. 8-10
describe additional uses of the systems and methods within
different exemplary communication systems.
[0116] FIG. 8 is a block diagram showing a communication system. In
FIG. 8, there is shown a computer system 802, a WAN 804, corporate
LAN 806 behind a security firewall 808, wireless infrastructure
810, wireless networks 812 and 814, and mobile devices 816 and 818.
The corporate-LAN 806 includes a message server 820, a wireless
connector system 828, a data store 817 including at least a
plurality of mailboxes 819, a desktop computer system 822 having a
communication link directly to a mobile device such as through
physical connection 824 to an interface or connector 826, and a
wireless VPN router 832. Operation of the system in FIG. 8 is
described below with reference to the messages 833, 834 and
836.
[0117] The computer system 802 is for example, a laptop, desktop or
palmtop computer system configured for connection to the WAN 804.
Such a computer system may connect to the WAN 804 via an ISP or
ASP. Alternatively, the computer system 802 may be a
network-connected computer system that like the computer system 822
for example, accesses the WAN 804 through a LAN or other network,
Many modem mobile devices are enabled for connection to a WAN
through various infrastructure and gateway arrangements, so that
the computer system 802 may also be a mobile device.
[0118] The corporate LAN 806 is an illustrative example of a
central, server-based messaging system that has been enabled for
wireless communications. The corporate LAN 806 may be referred to
as a `host system`, in that it hosts both a data store 817 with
mailboxes 819 for messages, as well as possibly further data stores
(not shown) for other data items, that may be sent to or received
from mobile devices 816 and 818, and the wireless connector system
828, the wireless VPN router 832, or possibly other components
enabling communications between the corporate LAN 806 and one or
more mobile devices 816 and 818. In more general terms, a host
system is one or more computers at, with, or in association with
which a wireless connector system is operating. The corporate LAN
806 is one preferred embodiment of a host system in which the host
system is a server computer running within a corporate network
environment operating behind and protected by at least one security
communications firewall 808. Other possible central host systems
include ISP, ASP and other service provider or mail systems.
Although the desktop computer system 824 and interface/connector
826 may be located outside such host systems, wireless
communication operations may be similar to those described
below.
[0119] The corporate LAN 806 implements the wireless connector
system 828 as an associated wireless communications enabling
component, which will normally be a software program, a software
application, or a software component built to work with at least
one message server 820. The wireless connector system 828 is used
to send user-selected information to, and to receive information
from, one or more mobile devices 816 and 818, via one or more
wireless networks 812 and 814. The wireless connector system 828
may be a separate component of a messaging system, as shown in FIG.
8, or may instead be partially or entirely incorporated into other
communication system components. For example, the message server
820 may incorporate a software program, application, or component
implementing the wireless connector system 828, portions thereof,
or some or all of its functionality.
[0120] The message server 820, running on a computer behind the
firewall 808, acts as the main interface for the corporation to
exchange messages, including for example electronic mail,
calendaring data, voice mail, electronic documents, and other PIM
data with a WAN 804, such as the Internet, The particular
intermediate operations and computers are dependent upon the
specific type of message delivery mechanisms and networks via which
messages are exchanged, and therefore have not been shown in FIG.
8. The functionality of the message server 820 may extend beyond
message sending and receiving, providing such features as dynamic
database storage for data like calendars, to-do lists, task lists,
e-mail, and documentation, as described above.
[0121] Message servers such as 820 normally maintain a plurality of
mailboxes 819 in one or more data stores such as 817 for each user
having an account on the server. The data store 817 includes
mailboxes 819 for a number ("n") of user accounts. Messages
received by the message server 820 that identify a user, a user
account, a mailbox, or possibly another address associated with a
user, account or mailbox 819, as a message recipient is typically
stored in the corresponding mailbox 819. If a message is addressed
to multiple recipients or a distribution list, then copies of the
same message may be stored to more than one mailbox 819.
Alternatively, the message server 820 may store a single copy of
such a message in a data store accessible to all of the users
having an account on the message server 820, and store a pointer or
other identifier in each recipient's mailbox 819. In typical
messaging systems, each user then accesses his or her mailbox 819
and its contents using a messaging client such as Microsoft Outlook
or Lotus Notes, which normally operates on a PC, such as the
desktop computer system 822, connected in the LAN 806. Although
only one desktop computer system 822 is shown in FIG. 8, those
skilled in the art will appreciate that a LAN typically contains
many desktop, notebook, and laptop computer systems. Each messaging
client normally accesses a mailbox 819 through the message server
820, although in some systems, a messaging client may enable direct
access to the data store 817 and a mailbox 819 stored thereon by
the desktop computer system 822. Messages may also be downloaded
from the data store 817 to a local data store on the desktop
computer system 822.
[0122] Within the corporate LAN 806, the wireless connector system
828 operates in conjunction with the message server 820. The
wireless connector system 828 may reside on the same computer
system as the message server 820, or may instead be implemented on
a different computer system. Software implementing the wireless
connector system 828 may also be partially or entirely integrated
with the message server 820. The wireless connector system 828 and
the message server 820 are preferably designed to cooperate and
interact to allow the pushing of information to the mobile devices
816, 818. In such an installation, the wireless connector system
828 is preferably configured to send information that is stored in
one or more data stores associated with the corporate LAN 806 to
one or more of the mobile devices 816, 818, through the corporate
firewall 808 and via the WAN 804 and one of the wireless networks
812, 814. For example, a user that has an account and associated
mailbox 819 in the data store 817 may also have a mobile device,
such as 816. As described above, messages received by the message
server 820 that identify a user, account, or mailbox 819 are stored
to a corresponding mailbox 819 by the message server 820. If a user
has a mobile device, such as 816, messages received by the message
server 820 and stored to the user's mailbox 819 are preferably
detected by the wireless connector system 828 and sent to the
user's mobile device 816. This type of functionality represents a
"push" message sending technique. The wireless connector system 828
may instead employ a "pull" technique, in which items stored in a
mailbox 819 are sent to a mobile device 816 or 818 responsive to a
request or access operation made using the mobile device, or some
combination of both techniques.
[0123] The use of a wireless connector 828 thereby enables a
messaging system including a message server 520 to be extended so
that each user's mobile device 816, 818 has access to stored
messages of the message server 820. Although the systems and
methods described herein are not restricted solely to a push-based
technique, a more detailed description of push-based messaging may
be found in the United States Patent and incorporated by reference
above. This push technique uses a wireless friendly encoding,
compression and encryption technique to deliver all information to
a mobile device, thus effectively extending the company firewall
808 to include the mobile devices 816 and 818.
[0124] As shown in FIG. 8, there are several paths for exchanging
information with a mobile device 816, 818 from the corporate LAN
806. One possible information transfer path is through the physical
connection 824 such as a serial port, using an interface or
connector 826. This path is useful for example for bulk information
updates often performed at initialization of a mobile device 816,
818 or periodically when a user of a mobile device 816, 818 is
working at a computer system in the LAN 806, such as the computer
system 822. For example, as described above, PIM data is commonly
exchanged over a such a connection as a serial port connected to a
cradle in or upon which a mobile device 816, 818 may be placed. The
physical connection 824 may also be used to transfer other
information from a desktop computer system 822 to a mobile device
816, 818, including private security keys ("private keys") such as
private encryption or digital signature keys associated with the
desktop computer system 822, or other relatively bulky information
such as digital certificates and CRLs.
[0125] Private key exchange using the physical connection 824 and
the connector or interface 826 allows a user's desktop computer
system 822 and mobile device 816 or 818 to share at least one
identity for accessing all encrypted and/or signed mail. The user's
desktop computer system 822 and mobile device 816 or 818 can also
thereby share private keys so that either the host system 822 or
the mobile device 816 or 818 can process secure messages addressed
to the user's mailbox or account on the message server 820. The
transfer of digital certificates and CRLs over such a physical
connection is desirable in that they represent a large amount of
the data that is required for S/MIME, PGP and other public key
security methods. A user's own digital certificate, a chain of
digital certificates used to verify the user's digital certificate,
and a CRL, as well as digital certificates, digital certificate
chains and CRLs for other users, may be loaded onto a mobile device
816, 818 from the user's desktop computer system 822. This loading
of other user's digital certificates and CRLs onto a mobile device
816, 818 allows a mobile device user to select other entities or
users with whom they might be exchanging secure messages; and to
pre-load the bulky information onto the mobile device through a
physical connection instead of over the air, thus saving time and
wireless bandwidth when a secure message is received from or to be
sent to such other users, or when the status of a digital
certificate is to be determined based on one or more CRLs,
CRL-based status checks can also be avoided where the systems and
methods described herein are employed.
[0126] In known "synchronization" type wireless messaging systems,
a physical path has also been used to transfer messages from
mailboxes 819 associated with a message server 820 to mobile
devices 816 and 818.
[0127] Another method for data exchange with the mobile devices 816
and 818 is over-the-air, through the wireless connector system 828
and using the wireless networks 812 and 814. As shown in FIG. 8,
this could involve a Wireless VPN router 832, if available in the
network 806, or alternatively, a traditional WAN connection to
wireless infrastructure 810 that provides an interface to one or
more wireless networks such as 814. The Wireless VPN router 832
provides for creation of a VPN connection directly through a
specific wireless network 812 to a wireless device 816. Such a
Wireless VPN router 832 may be used in conjunction with a static
addressing scheme. For example, if the wireless network 812 is an
IP-based wireless network, then IPV6 would provide enough IP
addresses to dedicate an IP address to every mobile device 816
configured to operate within the network 812 and thus make it
possible to push information to a mobile device 816 at-any time. A
primary advantage of using a wireless VPN router 832 is that it
could be an off-the-shelf VPN component which would not require
wireless infrastructure 810. A VPN connection may use a TCP/IP or
UDP/IP connection to deliver messages directly to and from a mobile
device 816.
[0128] If a wireless VPN router 832 is not available, then a link
to a WAN 804, normally the Internet, is a commonly used connection
mechanism that may be employed by the wireless connector system
828. To handle the addressing of the mobile device 816 and any
other required interface functions, wireless infrastructure 810 is
preferably used. The wireless infrastructure 810 may also determine
a most likely wireless network for locating a given user, and track
users as they roam between countries or networks. In wireless
networks such as 812 and 814, messages are normally delivered to
and from mobile devices via RF transmissions between base stations
and the mobile devices.
[0129] A plurality of connections to wireless networks 812 and 814
may be provided, including, for example, ISDN, Frame Relay or T1
connections using the TCP/IP protocol used throughout the Internet.
The wireless networks 812 and 814 could represent distinct, unique
and unrelated networks, or they could represent the same network
indifferent countries, and may be any of different types of
networks, including but not limited to, data-centric wireless
networks, voice-centric wireless networks, and dual-mode networks
that can support both voice and data communications over the same
or similar infrastructure, such as any of those described
above.
[0130] In some implementations, more than one over-the-air
information exchange mechanism may be provided in the corporate LAN
806. In FIG. 8 for example, the mobile devices 816 and 818
associated with users having mailboxes 819 associated with user
accounts on the message server 820 are configured to operate on
different wireless networks 812 and 814. If the wireless network
812 supports IPv6 addressing, then the wireless VPN router 832 may
be used by the wireless connector system 828 to exchange data with
any mobile device 816 operating within the wireless network 812.
The wireless network 814 may be a different type of wireless
network, however, such as the Mobitex network, in which case
information is instead exchanged with the mobile device 818
operating within the wireless network 814 via a connection to the
WAN 804 and the wireless infrastructure 810.
[0131] Operation of the system in FIG. 8 will now be described
using an example of an e-mail message 833 sent from the computer
system 802 and addressed to at least one recipient having both an
account and mailbox 819 or like data store associated with the
message server 820 and a mobile device 816 or 818. However, the
e-mail message 833 is intended for illustrative purposes only. The
exchange of other types of information between the corporate LAN
806 is preferably also enabled by the wireless connector system
828.
[0132] The e-mail message 833, sent from the computer system 802
via the WAN 804, may be fully in the clear, or signed with a
digital signature and/or encrypted, depending upon the particular
messaging scheme used. For example, if the computer system 802 is
enabled for secure messaging using S/MIME, then the e-mail message
833 may be signed, encrypted, or both.
[0133] E-mail messages such as 833 normally use traditional SMTP,
RFC822 headers and MIME body parts to define the format of the
e-mail message. These techniques are all well known to one in the
art. The e-mail message 833 arrives at the message server 820,
which determines into which mailboxes 819 the e-mail message 833
should be stored. As described above, a message such as the e-mail
message 833 may include a user name, a user account, a mailbox
identifier, or other type of identifier that is mapped to a
particular account or associated mailbox 819 by the message server
820. For an e-mail message 833, recipients are typically identified
using e-mail addresses corresponding to a user account and thus a
mailbox 819.
[0134] The wireless connector system 828 sends or mirrors, via the
wireless network 812 or 814, certain user-selected data items or
parts of data items from the corporate LAN 806 to the user's mobile
device 816 or 818, preferably upon detecting that one or more
triggering events has occurred. A triggering event includes, but is
not limited to, one or more of the following: screen saver
activation at a user's networked computer system 822, disconnection
of the user's mobile device 816 or 818 from the interface 826, or
receipt of a command sent from a mobile device 816 or 818 to the
host system to start sending one or more messages stored at the
host system. Thus, the wireless connector system 828 may detect
triggering events associated with the message server 820, such as
receipt of a command, or with one or more networked computer
systems 822, including the screen saver and disconnection events
described above. When wireless access to corporate data for a
mobile device 816 or 818 has been activated at the LAN 806, for
example when the wireless connector system 828 detects the
occurrence of a triggering event for a mobile device user, data
items selected by the user are preferably sent to the user's mobile
device. In the example of the e-mail message 833, assuming that a
triggering event has been detected, the arrival of the message 833
at the message server 820 is detected by the wireless connector
system 828. This may be accomplished, for example, by monitoring or
querying mailboxes 819 associated with the message server 820, or,
if the message server 820 is a Microsoft Exchange server, then the
wireless connector system 828 may register for advise syncs
provided by the Microsoft Messaging Application Programming
Interface (MAR) to thereby receive notifications when a new message
is stored to a mailbox 819.
[0135] When a data item such as the e-mail message 833 is to be
sent to a mobile device 816 or 818, the wireless connector system
828 preferably repackages the data item in a manner that is
transparent to the mobile device 816 or 818, so that information
sent to and received by the mobile device 816 or 818 appears
similar to the information as stored on and accessible at the host
system, LAN 806 in FIG. 8. One preferred repackaging method
includes wrapping received messages to be sent via a wireless
network 812 or 814 in an electronic envelope that corresponds to
the wireless network address of the mobile device 816 or 818 to
which the message is to be sent. Alternatively, other repackaging
methods could be used, such as special-purpose TCP/IP wrapping
techniques. Such repackaging preferably also results in e-mail
messages sent from a mobile device 816 or 818 appearing to come
from a corresponding host system account or mailbox 819 even though
they are composed and sent from a mobile device. A user of a mobile
device 816 or 818 may thereby effectively share a single e-mail
address between a host system account or mailbox 819 and the mobile
device.
[0136] Repackaging of the e-mail message 833 is indicated at 834
and 836. Repackaging techniques may be similar for any available
transfer paths or may be dependent upon the particular transfer
path, either the wireless infrastructure 810 or the wireless VPN
router 832. For example, the e-mail message 833 is preferably
compressed and encrypted, either before or after being repackaged
at 834, to thereby provide for secure transfer to the mobile device
818. Compression reduces the bandwidth required to send the
message, whereas encryption ensures confidentiality of any messages
or other information sent to the mobile devices 816 and 818. In
contrast, messages transferred via a VPN router 832 might only be
compressed and not encrypted, since a VPN connection established by
the VPN router 832 is inherently secure. Messages are thereby
securely sent, via either encryption at the wireless connector
system 828, which may be considered a non-standard VPN tunnel or a
VPN-like connection, for example, or the VPN router 832, to mobile
devices 816 and 818. Accessing messages using a mobile device 816
or 818 is thus no less secure than accessing mailboxes at the LAN
806 using the desktop computer system 822.
[0137] When a repackaged message 834 or 836 arrives at a mobile
device 816 or 818, via the wireless infrastructure 810, or via the
wireless VPN router 832, the mobile device 816 or 818 removes the
outer electronic envelope from the repackaged message 834 or 836,
and performs any required decompression and decryption operations.
Messages sent from a mobile device 816 or 818 and addressed to one
or more recipients are preferably similarly repackaged, and
possibly compressed and encrypted, and sent to a host system such
as the LAN 806. The host system may then remove the electronic
envelope from the repackaged message, decrypt and decompress the
message if desired, and route the message to the addressed
recipients.
[0138] Another goal of using an outer envelope is to maintain at
least some of the addressing information in the original e-mail
message 833. Although the outer envelope used to route information
to mobile devices 816, 818 is addressed using a network address of
one or more mobile devices, the outer envelope preferably
encapsulates the entire original e-mail message 833, including at
least one address field, possibly in compressed and/or encrypted
form. This allows original "To", "From" and "CC" addresses of the
e-mail message 833 to be displayed when the outer envelope is
removed and the message is displayed on a mobile device 816 or 818.
The repackaging also allows reply messages to be delivered to
addressed recipients, with the "From" field reflecting an address
of the mobile device user's account or mailbox on the host system,
when the outer envelope of a repackaged outgoing message sent from
a mobile device is removed by the wireless connector system 828.
Using the users account or mailbox address from the mobile device
816 or 818 allows a message sent from a mobile device to appear as
though the message originated from the users mailbox 819 or account
at the host system rather than the mobile device.
[0139] FIG. 9 is a block diagram of an alternative communication
system, in which wireless communications are enabled by a component
associated with an operator of a wireless network. As shown in FIG.
9, the system includes a computer system 802, WAN 804, a corporate
LAN 807 located behind a security firewall 808, network operator
infrastructure 840, a wireless network 811, and mobile devices 813
and 815. The computer system 802, the WAN 804, the security
firewall 808, the message server 820, the data store 817, the
mailboxes 819, and the VPN router 835 are substantially the same as
the similarly-labelled components in FIG. 8. However, since the VPN
router 835 communicates with the network operator infrastructure
840, it need not necessarily be a wireless VPN router in the system
of FIG. 9. The network operator infrastructure 840 enables wireless
information exchange between the LAN 807 and the mobile devices 813
and 815, respectively associated with the computer systems 842 and
852 and configured to operate within the wireless network 811. In
the LAN 807, a plurality of desktop computer systems 842 and 852
are shown, each having a physical connection 846 or 856 to an
interface or connector 848 or 858. A wireless connector system 844
or 854 is operating on or in conjunction with each computer system
842 and 852.
[0140] The wireless connector systems 844 and 854 are similar to
the wireless connector system 828 described above, in that they
enable data items, such as e-mail messages and other items that are
stored in mailboxes 819, and possibly data items stored in a local
or network data store, to be sent from the LAN 807 to one or more
of the mobile devices 813 and 815. In FIG. 9 however, the network
operator infrastructure 840 provides an interface between the
mobile devices 813 and 815 and the LAN 807. As above, operation of
the system shown in FIG. 9 is described below in the context of an
e-mail message as an illustrative example of a data item that may
be sent to a mobile device 813 or 815.
[0141] When an e-mail message 833, addressed to one or more
recipients having an account on the message server 820, is received
by the message server 820, the message, or possibly a pointer to a
single copy of the message stored in a central mailbox or data
store, is stored in the mailbox 819 of each such recipient. Once
the e-mail message 833 or pointer has been stored to a mailbox 819,
it may preferably be accessed using a mobile device 813 or 815. In
the example shown in FIG. 9, the e-mail message 833 has been
addressed to the mailboxes 819 associated with both desktop
computer systems 842 and 852 and thus both mobile devices 813 and
815.
[0142] As those skilled in the art will appreciate, communication
network protocols commonly used in wired networks such as the LAN
807 and/or the WAN 804 are not suitable or compatible with wireless
network communication protocols used within wireless networks such
as 811. For example, communication bandwidth, protocol overhead,
and network latency, which are primary concerns in wireless network
communications, are less significant in wired networks, which
typically have much higher capacity and speed than wireless
networks. Therefore, mobile devices 813 and 815 cannot normally
access the data store 817 directly. The network operator
infrastructure 840 provides a bridge between the wireless network
811 and the LAN 807.
[0143] The network operator infrastructure 840 enables a mobile
device 813 or 815 to establish a connection to the LAN 807 through
the WAN 804, and may, for example, be operated by an operator of
the wireless network 811 or a service provider that provides
wireless communication service for mobile devices 813 and 815. In a
pull-based system, a mobile device 813 or 815 establishes a
communication session with the network operator infrastructure 840
using a wireless network compatible communication scheme,
preferably a secure scheme such as Wireless Transport Layer
Security (WTLS) when information should remain confidential, and a
wireless web browser such as a Wireless Application Protocol (WAP)
browser. A user then requests, through manual selection or
pre-selected defaults in the software residing in the mobile
device, any or all information, or just new information, for
example, stored in a mailbox 819 in the data store 817 at the LAN
807. The network operator infrastructure 840 establishes a
connection or session with a wireless connector system 844, 854,
using Secure Hypertext Transfer Protocol (HTTPS), for example, if
no session has already been established. As above, a session
between the network operator infrastructure 840 and a wireless
connector system 844 or 854 may be made via a typical WAN
connection or through the VPN router 835 if available. When time
delays between receiving a request from a mobile device 813 or 815
and delivering requested information back to the device are to be
minimized, the network operator infrastructure 840 and the wireless
connector systems 844 and 854 may be configured so that a
communication connection remains open once established.
[0144] In the system of FIG. 9, requests originating from mobile
device A 813 and B 815 would be sent to the wireless connector
systems 844 and 854, respectively. Upon receiving a request for
information from the network operator infrastructure 840, a
wireless connector system 844 or 854 retrieves requested
information from a data store. For the e-mail message 833, the
wireless connector system 844 or 854 retrieves the e-mail message
833 from the appropriate mailbox 819, typically through a messaging
client operating in conjunction with the computer system 842 or
852, which may access a mailbox 819 either via the message server
820 or directly. Alternatively, a wireless connector system 844 or
854 may be configured to access mailboxes 819 itself, directly or
through the message server 820. Also, other data stores, both
network data stores similar to the data store 817 and local data
stores associated with each computer system 842 and 852, may be
accessible to a wireless connector system 844 or 854, and thus to a
mobile device 813 or 815.
[0145] If the e-mail message 833 is addressed to the message server
accounts or mailboxes 819 associated with both computer systems 842
and 852 and devices 813 and 815, then the e-mail message 833 is
sent to the network operator infrastructure 840 as shown at 860 and
862, which then sends a copy of the e-mail message to each mobile
device 813 and 815, as indicated at 864 and 866. Information is
transferred between the wireless connector systems 844 and 854 and
the network operator infrastructure 840 via either a connection to
the WAN 804 or the VPN router 835. When the network operator
infrastructure 840 communicates with the wireless connector systems
844 and 854 and the mobile devices 813 and 815 via different
protocols, translation operations may be performed by the network
operator infrastructure 840. Repackaging techniques may also be
used between the wireless connector systems 844 and 854 and the
network operator infrastructure 840, and between each mobile device
813 and 815 and the network operator infrastructure 840.
[0146] Messages or other information to be sent from a mobile
device 813 or 815 may be processed in a similar manner, with such
information first being transferred from a mobile device 813 or 815
to the network operator infrastructure 840. The network operator
infrastructure 840 then sends the information to a wireless
connector system 844 or 854 for storage in a mailbox 819 and
delivery to any addressed recipients by the message server 820, for
example, or may alternatively deliver the information to the
addressed recipients.
[0147] The above description of the system in FIG. 9 relates to
pull-based operations. The wireless connector systems 844 and 854
and the network operator infrastructure may instead be configured
to push data items to mobile devices 813 and 815. A combined
push/pull system is also possible. For example, a notification of a
new message or a list of data items currently stored in a data
store at the LAN 807 could be pushed to a mobile device 813 or 815,
which may then be used to request messages or data items from the
LAN 807 via the network operator infrastructure 840.
[0148] If mobile devices associated with user accounts on the LAN
807 are configured to operate within different wireless networks,
then each wireless network may have an associated wireless network
infrastructure component similar to 840.
[0149] Although separate, dedicated wireless connector systems 844
and 854 are shown for each computer system 842 and 852 in the
system of FIG. 9, one or more of the wireless connector systems 844
and 854 is preferably configured to operate in conjunction with
more than one of the computer systems 842 and 852, or to access a
data store or mailbox 819 associated with more than one computer
system. For example, the wireless connector system 844 may be
granted access to the mailboxes 819 associated with both the
computer system 842 and the computer system 852. Requests for data
items from either mobile device A 813 or B 815 are then processed
by the wireless connector system 844. This configuration is useful
to enable wireless communications between the LAN 807 and the
mobile devices 813 and 815 without requiring a desktop computer
system 842 and 852 to be running for each mobile device user. A
wireless connector system may instead be implemented in conjunction
with the message server 820 to enable wireless communications.
[0150] FIG. 10 is a block diagram of another alternative
communication system. The system includes a computer system 802,
WAN 804, a corporate LAN 809 located behind a security firewall
808, an access gateway 880, a data store 882, wireless networks 884
and 886, and mobile devices 888 and 890. The computer system 802,
the WAN 804, the security firewall 808, the message server 820, the
data store 817, the mailboxes 819, the desktop computer system 822,
the physical connection 824, the interface or connector 826 and the
VPN router 835 are substantially the same as the corresponding
components described above. The access gateway 880 and data store
882 provide mobile devices 888 and 890 with access to data items
stored at the LAN 809. In FIG. 10, a wireless connector system 878
operates on or in conjunction with the message server 820, although
a wireless connector system may instead operate on or in
conjunction with one or more desktop computer systems 822 in the
LAN 809.
[0151] The wireless connector system 878 provides for transfer of
data items stored at the LAN 809 to one or more of the mobile
devices 888 and 890. These data items preferably include e-mail
messages stored in mailboxes 819 in the data store 817, as well as
possibly other items stared in the data store 817 or another
network data store or a local data store of a computer system such
as 822.
[0152] As described above, an e-mail message 833 addressed to one
or more recipients having an account on the message server 820 and
received by the message server 820 are stored into the mailbox 819
of each such recipient. In the system of FIG. 10, the external data
store 882 preferably has a similar structure to, and remains
synchronized with, the data store 817. PIM information or data
stored at data store 882 preferably is independently modifiable to
the PIM information or data stored at the host system. In this
particular configuration the independently modifiable information
at the external data store 882 may maintain synchronization of a
plurality of data stores associated with a user (i.e., data on a
mobile device, data on a personal computer at home, data at the
corporate LAN, etc.). This synchronization may be accomplished, for
example, through updates sent to the data store 882 by the wireless
connector system 878 at certain time intervals, each time an entry
in the data store 817 is added or changed, at certain times of day,
or when initiated at the LAN 809, by the message server 820 or a
computer system 822, at the data store 882, or possibly by a mobile
device 888 or 890 through the access gateway 880.
[0153] In the case of the e-mail message 833, for example, an
update sent to the data store 882 some time after the e-mail
message 833 is received indicates that the message 833 has been
stored in a certain mailbox 819 in the store 817, and a copy of the
e-mail message is stored to a corresponding storage area in the
data store 882. When the e-mail message 833 has been stored in the
mailboxes 819 corresponding to the mobile devices 888 and 890, one
or more copies of the e-mail message, indicated at 892 and 894 in
FIG. 10, will be sent to and stored in corresponding storage areas
or mailboxes in the data store 882. As shown, updates or copies of
stored information in the data store 817 may be sent to the data
store 882 via a connection to the WAN 804 or the VPN router 835.
For example, the wireless connector system 878 may post updates or
stored information to a resource in the data store 882 via an HTTP
post request. Alternatively, a secure protocol such as HTTPS or
Secure Sockets Layer (SSL) may be used. Those skilled in the art
will appreciate that a single copy of a data item stored in more
than one location in a data store at the LAN 809 may instead be
sent to the data store 882. This copy of the data item could then
be stored either in more than one corresponding location in the
data store 882, or a single copy may be stored in the data store
882, with a pointer or other identifier of the stored data item
being stored in each corresponding location in the data store
882.
[0154] The access gateway 880 is effectively an access platform, in
that it provides mobile devices 888 and 890 with access to the data
store 882. The data store 882 may be configured as a resource
accessible on the WAN 804, and the access gateway 880 may be an ISP
system or WAP gateway through which mobile devices 888 and 890
connect to the WAN 804. A WAP browser or other browser compatible
with the wireless networks 884 and 886 may then be used to access
the data store 882, which is synchronized with the data store 817,
and download stored data items either automatically or responsive
to a request from a mobile device 888 or 890. As shown at 896 and
898, copies of the e-mail message 833, which was stored in the data
store 817, are sent to the mobile devices 888 and 890. A data store
on each mobile device 888 and 890 is thereby synchronized with a
portion, such as a mailbox 819, of a data store 817 on a corporate
LAN 809. Changes to a mobile device data store are similarly
reflected in the data stores 882 and 817.
[0155] The embodiments described herein are examples of structures,
systems or methods having elements corresponding to the elements of
the invention recited in the claims. This written description may
enable those of ordinary skill in the art to make and use
embodiments having alternative elements that likewise correspond to
the elements of the invention recited in the claims. The intended
scope of the invention thus includes other structures, systems or
methods that do not differ from the literal language of the claims,
and further includes other structures, systems or methods with
insubstantial differences from the literal language of the
claims.
* * * * *