Connection architecture for a mobile network
19 claims: 9 independent, 10 dependent
- 1ローカルネットワークにあるクライアントとモバイル機器との間で複数のトランザクションを交換することにより 、データを転送するための方法であって、 前記 クライアントから、1以上のファイアウォールを介して 前記ローカルネットワークとは独立して稼働し、前記ローカルネットワークの外部にある 一般にアクセス可能なネットワークにあるサーバへ の送 信を行うことにより 、前 記クライアントから 、前 記サーバへの第1の接続を開始し、前記第1の接続を確立するステップと、 前記 モバイル機器か ら前 記サーバへの、前記ローカルネットワークの外部にあり、かつ前記ローカルネットワークから独立して稼働するモバイルネットワークを介した、第2の接続を確立するステップと、 前記 第1の接続と、 前記 第2の接続との両方の接続を用いて、前記モバイル機器と前記クライアントとの間で 前記 複数のトランザクションを送信するステップと、 前記第2の接続が終了した後に、その後前記クライアントと通信することが必要な同一又は他の前記モバイル機器について前記一般にアクセス可能なネットワークか ら前 記ローカルネットワークへの通信のしやすさを維持するために 、前 記第1の接続を継続して維持するステップと、 前記第2の接続が終了した後に、前記モバイルネットワークと前記一般にアクセス可能なネットワークとの両方を介して前記同一又は他のモバイル機器から前記サーバへの新規の第3の接続を確立し、新しく確立された前記第3の接続を介して当該モバイル機器か ら前 記サーバへ新しい 前記 複数のトランザクションを送信し、また、以前に確立され、継続して維持されている前記第1の接続を用い て前 記サーバか ら前 記クライアントへ前記新しい複数のトランザクションを 、前 記クライアントか ら前 記サーバへの新しい外部への接続を確立することなく、転送するステップとを有し、 前記第1の接続は、継続的に維持された通信についての論理的な接続であり、 前記ローカルネットワークは、前記一般にアクセス可能なネットワークから、前記1以上のファイアウォールを介してのみ接続可能であり、 前記複数のトランザクションは、前記モバイル機器から前記モバイルネットワークと前記一般にアクセス可能なネットワークとの両方を経由して前記サーバへ、また、前記サーバから前記一般にアクセス可能なネットワークと前記ローカルネットワーク上の前記1以上のファイアウォールを介した前記ローカルネットワーク上で稼働している前記クライアントへ、渡るトランザクションパス上で交換されることを特徴とする前記方法。
- 2前記第1の接続は、前記第2の接続の終了とは独立し、更に前記サーバと他のモバイル機器との間での他の通信とは独立して、前記サーバによって継続的に維持されるトランスミッションコントロールプロトコル(TCP)接続であり、 前記第2の接続は、前記モバイル機器と前記クライアントとの間での前記複数のトランザクションが完了するのに応じて、前記モバイル機器により終了し、 前記第2の接続が前記モバイル機器により終了した時から、前記第3の接続が前記モバイル機器により確立するまでの時間の長さとは独立して、前記新しい複数のトランザクションが自動的に前記第1の接続を介して転送される請求項1に記載の方法。
- 3前記第1の接続の切断に応じて前記第1の接続を自動的に再確立し、前記モバイルネットワークを介して前記同一又は他のモバイル機器による前記第2の接続が確立するか又は完了するかに関わらず、前記同一又は他のモバイル機器から前記モバイルネットワークを介して受信される複数のトランザクションを前記クライアントに、前記1以上のファイアウォールを通過して前記第1の接続を介して転送することにより前記第1の接続を維持する請求項1に記載の方法。
- 4前記 クライアント におけるデータの表示を前記モバイル機器に格納するステップと、 前記第1の接続および前記第2の接続を介して、前記データの更新された表示を要求する同期要求を前記モバイル機器から前記 クライアント に送信するステップと、 前記同期要求に応じて、前記第1の接続および前記第2の接続を介して、前記モバイル機器に前記データの更新された表示を送り返すステップとを更に有する請求項1に記載の方法。
- 5特定の形式のデータを識別するフィルタを前記 クライアント に格納するステップと、 前記フィルタに関連した特定の形式のデータの一つを受信すると、前記 サーバ にメッセージ識別名を送信するステップと、 前記メッセージ識別名を前記モバイル機器に中継するために、ショートメッセージサービス又は他の通知プロトコルを用いるステップとを更に有する請求項1に記載の方法。
- 6前記フィルタの少なくとも一つは、優先度の高いデータを識別する請求項 5 に記載の方法。
- 7モバイル機器バッテリの充電量を確認するステップと、 前記バッテリの充電量に応じて、異なる時間間隔で前記モバイル機器と前記 クライアント とを自動的に同期するステップとを更に有する請求項1に記載の方法。
- 8前記モバイル機器が最初に前記サーバと前記第2の接続を確立する前に、前記 クライアント から前記サーバに認証トークンを送信して、当該認証トークンが前記サーバによって認証されるときに前 記第 1の接続を確立するステップと、 前記モバイル機器が前記第2の接続を終了した後にも、前記サーバと前記 クライアント との間での認証された前 記第 1の接続を維持するステップとを更に有する請求項1に記載の方法。
- 9前記サーバにある前記トランザクションと関連したデータを常には格納しないことにより、前記モバイル機器は、前記 クライアント へのリアルタイムでのアクセスができる請求項1に記載の方法。
- 10前記サーバと任意のモバイル機器との間で任意の接続が確立されたか否かに関わらず、前記第1の接続は、事前にネゴシエーションが行われた論理的な通信状態にある請求項1に記載の方法。
- 11前記第1の接続は、継続して維持されたTCP接続である請求項1に記載の方法。
- 12異なるモバイル機器から複数の独立したトランザクションを 前記サーバが 受信するステップと、 前記複数の独立したトランザクションのそれぞれを、前記サーバから前記 クライアント に前記継続して維持されたTCP接続を介して転送するステップとを更に有する請求項 11 に記載の方法。
- 13前記サーバからのファイルの要求に応じて、前記 クライアント は、前記サーバにファイルを供給する請求項 12 に記載の方法。
- 14前記第2の接続が終了した後に、前記第1の接続を維持することにより、モバイル機器からの前記 クライアント へのリアルタイムのアクセスを提供する請求項1に記載の方法。
- 15モバイル機器とローカルネットワークにあるクライアントとの間で 複数のトランザクションを送信することにより データを転送する方法であって、 前記ローカルネットワークにある前記クライアントから 前記ローカルネットワークの外部の一般にアクセス可能なネットワークにあるサーバ に 第1の 接続を開始するステップと、 前記モバイル機器から前記 サーバ に前記 第2の接続 を確立するステップと、 前記 第1の 接続および前記 第2の 接続を介して前記モバイル機器 と前 記クライアントとの間で複数のトランザクションを送信するステップと、 前記 第2の 接続が終了した後に 、前 記クライアントと前記 サーバ との間での 第1の 接続を継続して維持するステップと、 前記モバイル機器と前記 サーバ との間で新しい 第2の 接続を確立し、前記モバイル機器 と前 記クライアントとの間で前記新しい 第2の 接続および前もって確立している前記 第1の 接続を介して複数のトランザクションを送信するステップと、 前 記クライアントにあるデータの表示を前記モバイル機器に格納するステップと、 前記 第2の 接続および前記 第1の 接続を介して、前記データの更新された表示を要求する同期要求を、前記モバイル機器か ら前 記クライアントに送信するステップと、 前記同期要求に応じて、前記 第1の 接続および前記 第2の 接続を介して、前記モバイル機器に前記データの更新された表示を送り返すステップと、 前記モバイル機器と前記 サーバ との間での前記 第2の 接続を終了するステップと、 モバイル機器ユーザに関連する新しいデータについ て前 記クライアントを監視するステップと、 前記新しいデータが検出されると、前記 第1の 接続を介して前記 クライアント から前記 サーバ に同期トリガを送信するステップと、 前記 サーバ から前記モバイル機器に前記同期トリガを転送するステップと、 前記同期トリガが前記モバイル機器によって受信されると、前記モバイル機器と前記 サーバ の間の 第2の 接続を自動的に再確立するステップと、 前記再確立した 第2の 接続及び前記 第1の 接続を介して、前記モバイル機器から前記 クライアント に同期要求を送信するステップとを有し、 前記第1の接続は、継続的に維持された通信についての論理的な接続であることを特徴とする前記方法。
- 16一 般にアクセス可能 なネ ットワークから ローカル ネットワークを分離するファイアウォールを通過して、前記 ローカル ネットワーク からク ライアントによって開始される永続的に常設された処理状態が維持される 第1の 接続を介して、前 記ク ライアントと通信する、前 記一 般にアクセス可能 なネ ットワークに接続されたサーバを有し、 前記サーバは、更に、前記 ローカル ネットワークの外部に設置されたモバイル機器から開始される 第2の 接続を介して、モバイルネットワークと前記 一 般にアクセス可能 なネ ットワークとに渡って、通信するものであり、 前記ファイアウォールによって前記 ローカル ネットワークに直接アクセスすることが防止されており、したがって、前記 第2の 接続を介し、前記 第1の 接続を用いて前記ファイアウォールを通過して、モバイル機器と前 記ク ライアントの間のトランザクションを送る前記モバイル機器を更に有し、 前記サーバは、前記モバイル機器との前記 第2の 接続の接続状態とは独立して、かつ任意の前 記ク ライアント、前記モバイル機器および前記サーバの間でのファイルトランザクションの休止に関わらず、前記 第1の 接続を継続し、新規の 第2の 接続が前記モバイル機器と前記サーバとの間で確立したときにはいつでも接続が開始され、前記モバイル機器と前 記ク ライアントとの間での処理状態が維持される通信経路が完成されることを特徴とするコンピュータシステム。
- 17モバイルネットワークに配置されたモバイル機器であって、 1以上のファイアウォールによって一般に アクセス 可能なネットワークから隔てられた ローカルネットワーク に対するアクセスを提供する 第1の 接続を介して 、ク ライアントと複数のファイルアクセストランザクションを交換するように構成されたプロセッサを有し、 前記 第1の 接続は、前記プロセッサがモバイルネットワークに接続されたか否かに関わらず、任意のモバイル機器と前記イントラネット上に配置された任意のネットワーク機器との間での任意の通信中にどれだけ時間が経過したかに関わらず、かつ、いかなるタイムアウトに関わらず、状態が維持されたままであり、前記プロセッサとサーバとの間で繰り返し確立される 第2の 接続は、前記 第1の 接続と繰り返し連結して、前記プロセッサと前 記ク ライアントとの間の一時的な状態が維持された通信パスを完成するものであり、 前記プロセッサは、同期トリガを受信すると、前記 第2の 接続の一つおよび前記 第1の 接続を介して、前記モバイル機器から同期要求を前記 クライアント に送信するように構成されており、 前記プロセッサは、前記同期要求を送信した後に、前記 第2の 接続の一つおよび前記 第1の 接続を介して、前記 クライアント と同期通信を交換するように構成されていることを特徴とする前記モバイル機器。
- 18モバイル機器とローカルネットワークにあるクライアントとの間で 複数のトランザクションを交換することにより、 データを転送する方法であって、 前記クライアントから 前記ローカルネットワークの外部の一般にアクセス可能なネットワークにあるサーバ への第1の接続を開始するステップと、 前記モバイル機器から前記 サーバ への 第2の接続 を確立するステップと、 前記第1の接続および前記 第2の接続 を介して、前記モバイル機器 と前 記クライアントとの間で 前記 複数のトランザクションを送信するステップと、 前記 第2の接続 が終了した後に 、前 記クライアントと前記 サーバ との間の前記第1の接続を維持するステップと、 新規の 第2の接続 および以前に確立した前記第1の接続を介して、同期トリガを受信した後に、前記モバイル機器か ら前 記クライアントに同期要求を送信するステップと、 前記新規の 第2の接続 および以前に確立した前記第1の接続を介して、前記モバイル機器 と前 記クライアントとの間で 前記 複数のトランザクションを送信するステップと、を有することを特徴とする前記方法。
- 19ロ ーカルネットワークの外部にある 一 般にアクセス可能なネットワークに配置されたサーバ、およびモバイル機器を前記サーバに接続する前記 ロ ーカルネットワークの外部で稼働する モバイル ネットワークを介して、前記モバイル機器と複数のトランザクションを行う ことによりデータの転送を行う 、前記 ロ ーカルネットワークに設置された ク ライアントを稼働するコンピュータを有し、 前記モバイル機器と前記 ク ライアントとの間で論理的な第1の接続を介して複数のトランザクションを交換するよう に前 記コンピュータ と前 記サーバとの両方を設定する前記サーバへ、前記 ク ライアントは、 論 理的な 前記 第1の接続を前記 ロ ーカルネットワークおよび前記 一 般にアクセス可能なネットワークを通じて、 開始 するものであり、 前記モバイル機器 の前 記サーバとのすべての接続が終了した後において 、前記第 1の接続は、継続して開放されており、前記モバイル機器は、すでに確立された前 記第 1の接続を介して前記 クライアント へ再接続されることができ、その結果、前記モバイル機器が前記サーバ と前 記コンピュータとの両方のすべての通信を終了していることとは独立し 、かつ 以前に確立した前 記第 1の接続を介して、前記モバイル機器か ら前 記コンピュータへの、連続的な、かつ事前にネゴシエーションが行われた論理的な再接続性を提供することを特徴とするコンピュータシステム。
Independent claims19
65 paragraphs, as filed
Mobile email message exchange systems typically use storage devices and advanced architectures. The email redirector software is running on either a corporate email server or a desktop computer. The redirector software monitors the user mailbox. When a new email message is received in the mailbox, the redirector makes a copy of the email message, wraps this copy in an encrypted envelope, and summarizes the copy for delivery to the mobile device. The redirector may optionally encrypt and / or sign the summarized email message.
The encrypted summary email message is sent over the Internet to route to the mobile device associated with the user mailbox. Once encrypted, the email message is decrypted by the mobile device before being stored on the mobile device and then displayed and stored on the mobile device. The same process is repeated for each new email received in the user's mailbox.
And in this architecture, there are two versions of the same mailbox. They are the primary mailboxes on email servers or desktop PCs and duplicated mailboxes on mobile devices. Consistency between the primary mailbox and the duplicated mailbox can be maintained to some extent with synchronous messages back and forth between the redirector and the mobile device. For example, an email message deleted from a mobile device results in a sync message to the desktop redirector, which also directs the message to be deleted from the primary mailbox. In some versions of this architecture, no effort has been made to ensure the consistency of mailbox state between the main instance and the replicated instance. This storage device and forward-looking architecture are cumbersome, do not work in real time, and require sending large numbers of email messages over the Internet. The present invention deals with this and other issues related to the prior art.
<p> The real-time communication architecture establishes a continuous connection between the corporate network and the communication management system. Allows mobile devices to access corporate data sources such as email systems in real time, keeping the connection continuously open. The real-time communication architecture can support corporate email systems or the entire personal email user.</p><p> The aforementioned and other objects, features and advantages of the present invention will be more readily apparent from the detailed description of preferred embodiments of the present invention, which will proceed with reference to the accompanying drawings.</p>
For ease of description, data, databases, files, and data transactions are also commonly referred to as emails, email transactions, mailboxes, and so on. However, any type of email data or email transaction described below may need to be transferred between calendars, contacts, tasks, notes, electronic documents, files, or between local networks and mobile devices. It can be executed in the same way as data.
FIG. 1 shows an embodiment of the real-time communication architecture 12. The real-time communication architecture 12 includes a mobile network 14, a corporate network 18, and a communication management system 16 that manages communication between the mobile network 14 and the corporate network 18.
The corporate network 18 in the example is a private network including the firewall 31. Firewall 31 is a set of related programs that can be located on a network gateway server that protects the resources of corporate network 18 from users on other networks. The term "firewall" means the security policy used in firewall programs.
The mobile network 14 includes a plurality of mobile devices 21 that communicate via the Internet through a wireless or terrestrial communication mobile network 14. Since the mobile network 14 is well known, no further details will be given here.
The corporate network 18 can be any business network, personal user network, or local computer system that holds local email and other personal data for one or more users. In the embodiment shown in FIG. 1, the corporate network 18 includes an e-mail server 34 accessed by a large number of personal computers (PCs) 38. In one example, the e-mail server 34 may be a Microsoft Exchange server, and the PC 38 may access the e-mail of the e-mail server 34 through a Microsoft Outlook software application. (Here, "Microsoft", "Exchange", and "outlook" are registered trademarks.) The e-mail server 34 can store e-mail mailboxes, contact lists (communication lists), calendars, tasks, notes, or any other type of local data or electronic document.
The PC 38 is connected to the email server 34 via a local area network (LAN) 35. The PC 38, along with all other types of electronic documents, includes a memory 39 for storing local files containing personal e-mail data. The personal client software 40 is executed by the processor in the PC38. The personal client 40 exchanges transactions on the mobile device 21 to access local files and browse e-mail, calendars, and communication information.
The communication management system 16 includes at least one management server 28 that manages transactions between the mobile device 21 and the corporate network 18. The user database 42 contains configuration information for different users. For example, the user database 42 may include login data for users of the corporate network 18.
<u style="single">Enterprise Version</u> Figure 2 shows the enterprise version of Communication Architecture 12. The corporate network 18 includes a corporate server 34 that connects to a plurality of PC 38s via a LAN connection 35. In addition, the corporate server 34 includes a corporate client 41 that can directly communicate with the management server 28.
The communication management system 16 of FIG. 2 includes a management server 28 as well as one or more smart device servers (SDS) 30 and one or more personal client servers (PCS) 32. The SDS30 handles communication with a particular smart mobile device 24. PCS32 manages communication with the personal client 40.
The mobile device 21 of FIG. 2 is shown as more specific and includes a mobile phone 20 having a WAP interface that communicates with the management server 28 via the WAP gateway 26. The other mobile device 21 may include a PC, PDA, Internet terminal 22, or any other smart mobile device 24 that acts as a communication endpoint.
The mobile connection 23 in FIG. 1 and the mobile connections 45, 46 and 44 in FIG. 2 may be via terrestrial communication lines, cellular channels, 802.11 radio channels, satellite channels and the like.
<u style="single">Continuous real-time connection</u> In particular, in FIG. 1, the personal client 40 automatically establishes a continuous connection 25 between the PC 38 and the management server 28. The personal client 40 initiates an outbound connection 25 authenticated by the management server 28. For example, the personal client 40 provides the authentication token 29 to the management server 28. Then, the management server 28 tries to match the information of the authentication token 29 with the information of the user database 42.
If the authentication token 29 is authenticated, connections 25, 48 are established through the firewall 31 to achieve access to the management server 28 outside the private corporate network 18. The management server 28 then sends the personal client 40 connection authentication and all other necessary information. For example, the management server 28 may (or may) send back (or reply to) connection sharing information, email notification filters, and other mobile communication configuration parameters related to a particular user.
Then, the management server 28 and the personal client 40 enter the hibernate mode until a transaction such as a data query is transferred between the mobile device 21 and the personal client 40. If the connection 25 is disconnected for some reason, the personal client 40 automatically establishes another connection 25 with the management server 28.
It is important to note that the connection 25 is maintained continuously, even when the connection 23 is generally absent between the mobile device 21 and the management server 28. In one embodiment, connection 25 is a transmission control protocol / internet protocol (TCP / IP) connection. However, any connection protocol that allows a continuous connection between the corporate network 18 and the communication management system 16 can be used.
In an alternative embodiment, the connection 25 may be established within the corporate network 18 via a proxy server (not shown). For example, messages sent by Personal Client 40 may be encrypted by a proxy server at the Secure Sockets Layer (SSL).
After the connection 25 is established by the personal client 40, the mobile connection 23 can be established at any time between the mobile device 21 and the management server 28. After the mobile connection 23 is established, the mobile device 21 can access the e-mail and other information in the e-mail server 34 or the memory 39 via the personal client 40. Then, after the connection 25 is established, the personal client 40 effectively functions for the mobile device 21 as an email server.
In FIG. 2, in a manner similar to the personal client 40, the corporate client 41 establishes a continuous connection 48 with the management server 28, similar to the connection 25 established between the personal client 40 and the management server 28. .. Connection 48 is used to simultaneously relay transactions between a large number of mobile devices 21 and a large number of email users within the corporate server 34.
In the version of the communication architecture shown in FIG. 2, the personal client 40 may establish a connection 25 with the management server 28 via the PC 32, and a mobile device 24 establishes a mobile connection 44 via the SDS 30. You may.
<u style="single">Mobile device login</u> In FIGS. 1 and 2, management server 28 authenticates mobile connections 23, 44, 45 and 46 initiated by mobile device 21. When a user applies for a mobile account, a copy of the user's username and password on the corporate network 18 is stored in the user database 42. After the mobile device 21 is turned on, the user is required to log in to the communication management system 16 by entering another user name and password. If the mobile device 21 accesses the e-mail via the corporate server 34, a corporate identification name (eg, name) may also be requested, as opposed to doing so via the PC 38.
The mobile device 21 transmits the authentication token 27 directly to the management server 28 or to the SDS 30 that transfers the authentication token 27 to the management server 28. The management server 28 collates the information of the authentication token 27 with the information of the user database 42. If the authentication token 27 is verified, the management server 28 sends the authentication authorization to the mobile device 21 directly or via the SDS 30.
When the mobile device 21 successfully logs in, the management server 28 unlocks the user's corporate user name and password. This allows the mobile device 21 to access email and other local files on corporate network 18 via either connection 25 or connection 48.
The management server 28 also performs translation and viewing functions required to provide e-mail and other data to different mobile devices 21. For example, the management server 28 reformatts the local data retrieved from the corporate network 18 according to the particular mobile device 21 requesting information. The management server 28 also functions as a transaction routing engine for determining the route of transactions between the mobile device 21 and the corporate network 18.
<u style="single">Connections that do not know the processing status and do not repeat</u> In FIG. 3, when the mobile device 21 succeeds in logging in, a connection whose processing status is not known exists between the mobile device 21 and the personal client 40 via the connections 23 and 25. For example, the mobile device 21 may send a transaction request 62 to the personal client 40 to view the email in the user mailbox 60.
The transaction request 62 is transmitted from the mobile device 21 to the management server 28 via the mobile connection 23. The management server 28 locates the personal client 40 associated with the transaction request 62 and forwards the transaction request 62 over the appropriate connection 25. The personal client 40 accesses the data in the user mailbox 60 in response to the transaction request 62. For example, if transaction request 62 requests to see the user's latest e-mail, personal client 40 generates an e-mail list 64 containing the e-mail received in user mailbox 60. Then, the personal client 40 sends the e-mail list 64 back to the mobile device 21 via the connection 25.
If the mobile device 21 has limited memory and viewing ability, only the latest portion of the email in the user mailbox 60 may be included in the email list 64. Alternatively, the personal client 40 may send all e-mail in the user mailbox 60 to the management server 28. Then, the management server 28 distributes a part of the e-mail list 64 to the mobile device 21 according to the type of the electronic platform used in the mobile device 21.
These transactions allow the mobile device 21 to view user mailbox 60 information in real time without having to maintain a second version of user mailbox 60 email. Upon termination of connection 23, the email list 64 received by mobile device 21 may be deleted. If the user mailbox 60 needs to be viewed again, the mobile device 21 sends a new transaction request 62 to the personal client 40.
If the items requested in transaction request 62 are too many or too large to be viewed on mobile device 21, personal client 40 sends only enough information to identify the items in email list 64. You may. For example, the personal client 40 may pick up e-mail sender information and subject from the e-mail when the e-mail is sent. The personal client 40 may send only this picked up information in the latest e-mail received in the user mailbox 60.
The mobile device 21 receives the picked up partial email list 64 and can select one or more of the items in this list 64 for viewing. Depending on the type of data requested for viewing, another transaction request 62 may be sent from the mobile device 21 to the personal client 40 to view the selected email as is. The personal client 40 then sends the rest of the selected email to the mobile device 21. Instead, the mobile device 21 is the second of the emails contained in the user mailbox 60, if the partial email list 64 from which the emails the mobile device user wants to view are not included. Another transaction request 62 can be sent to the personal client 40 to see the part.
After the transaction between mobile device 21 and management server 28 is completed, there is no need to leave emails from user mailbox 60 or any other file from PC38 on mobile device 21. That is if the mobile device 21 does not store a copy of the data. Therefore, the servers 28, 30 and 32 shown in FIGS. 1 and 2 and the mobile device 21 do not need to maintain the second version of the email data in the user mailbox 60.
This unaware connection does not require many transactions typically required by storage devices and forwarding architectures, it copies emails and mobile devices each time they receive an email in a user mailbox. Eliminate having to send a copy of it to.
<u style="single">Local data file access</u> FIG. 4 shows how the mobile device 21 accesses the local files contained in the PC 38 and attaches an e-mail message to those local files. The personal client 40 running on the PC38 is configured to first point to the root directory 80. The root directory 80 may include a number of subfolders 82, including files 84 and 86. The other files 88 and 90 may be located at the top level (top level) of the root directory 80, or may be located in other subfolders.
Some mobile devices 21 do not have to have the ability to actually open or read files in the root directory 80, even if there is a lot of data in a file stored by the mobile device 21. Good. Even in these states, the mobile device 21 can still view, navigate, and select folders and files located under the root directory 80.
Email message 70 can be opened on mobile device 21. You may then select the Internet file option in your email application running on your mobile device 21. Send view file transaction 76 from mobile device 21 to management server 28 by selecting the internet file option.
The management server 28 sends the view file transaction 76 to the personal client 40 over the appropriate connection 25. The personal client 40 receives the view file transaction 76 and determines that the mobile device 21 has requested a list of files in the root directory 80. The personal client 40 generates a response containing a subfolder 82 in the root directory 80 and a file list 78 identifying files 84-90. Then, the response message including the file list 78 is sent back to the mobile device 21 via the connection 25.
All or part of file list 78 may be sent to mobile device 21. For example, the management server 28 may determine that the mobile device 21 has insufficient memory to view the entire file list 78. The management server 28 can also determine that it takes a lot of time to send the entire file list 78 to the mobile device 21. In these cases, the management server 28 may send only a part of the file list 78 to the mobile device 21.
The mobile device 21 displays the file list 78 received from the management server 28 and selects either the listed files or subfolders. You may select subfolders in File List 78 that contain files that are not included in File List 78. This causes the mobile device 21 to send out another view file transaction 76 requesting a list of files contained in the selected subfolder. The management server 28 or personal client 40 then sends back another file list 78 containing the files in the selected subfolder.
Selecting one or more files from the file list 78 inserts the file identifier 72 associated with email message 70. In one example, selecting a file is equivalent to sending in hypertext markup language (HTML) format, where the item is selected from the website. When the send email command of the mobile device 21 is selected, an email transaction 74 including the email message 70 and the file identifier 72 is sent to the management server 28.
The management server 28 sends this email transaction 74 to the personal client 40 over the connection 25. In the corporate network 18 shown in FIG. 2, the email transaction 74 may be moved from the SDS 30 to the management server 28 and to the personal client 40 via the PC 32 and the connection 25.
The personal client 40 opens the email transaction 74 and extracts the email message 70 containing the file identifier 72. The personal client 40 also reformatts the email message 70 into an email message 92 and attaches the file in the root directory 80 corresponding to the file identifier 72. The e-mail message 92 with the attached file is sent by the personal client 40 to the e-mail server 34. A copy of the e-mail message 92 may also be copied to the Sent Items folder in the user's mailbox.
<u style="single">Query storage</u> In FIG. 5, some mobile devices 21, referred to as smart mobile devices, may include software that activates a mobile client 98 that sends and receives data. The mobile device 21 can store another version of the local data of the email server 34. The stored data can include contact information stored in the memory unit 100, e-mail stored in the memory unit 102, and calendar information stored in the memory section 104. The mobile device 21 can view and generate e-mails, and can generally handle data in memory units 100 to 104 offline.
The mobile client 98 can maintain the latest version of the query data of the memory units 100 to 104 by using the connection architecture that does not know the processing state described above. For example, when the mobile device 21 starts the view contact process, the mobile client 98 sends the view contact transaction to the personal client 40. The mobile device 21 may request a contact list 114 for the entire corporate network 18. If the contact list 114 is too large to send to the mobile device 21, the personal client 40 may send only the first portion 108 of the contact list 114. For example, a list of contacts (contacts, communications) with the first few letters of the alphabet.
If the contact the user is looking for is not in the first part 108 of the contact list 114, the user can send a second view contact transaction 110 to the personal client 40. The second view contact transaction 110 may identify a particular alphabetic character of the personal client 40 for the query. Alternatively, the second view contact transaction 110 may instruct the personal client 40 to send back the next part of the corporate contact list 114 that immediately follows the first part 108 of the contact list. The personal client 40 sends back the second part 112 of the contact list 114 in response to the second view contact transaction 110. If the contact the user is looking for is in the second part 112 of the contact list 114, the mobile device 21 will not send further queries.
The mobile client 98 can store the last received contact list portion 112 in the memory 100. Depending on the amount of memory available on the mobile device 21, the mobile client 98 may save the last few contact list parts 112 to memory 100. Then, even if the mobile device 21 goes offline, the user can still see the latest information received from the personal client 40. The mobile client 98 can also save most up-to-date email queries in memory space 102 and most up-to-date calendar queries in memory space 104.
<u style="single">Sync</u> In FIG. 6, the mobile device 21 may store a second version 122 of the user's local data. It is occasionally needed to synchronize the second version 122 of mobile device 21 with the local version 136 of mail server 34. In one embodiment, the mobile device 21 periodically sends a synchronization request 134 to the personal client 40. The personal client 40 generates a response 133 in response to a synchronization request 134 that includes the latest email or other local user data. The response 133 is sent back to the mobile device 21 and used to update the second version data 122.
When a new email arrives at the email server 34, a trigger can be used to notify the mobile device 21 of it. The personal client 40 is configured with a filter 138 that identifies the type of email and other types of events that the mobile device 21 causes the trigger 132 to send.
For example, the filter 138 may notify the personal client 40 to send a trigger 132 each time a new email arrives at the user's mailbox. The personal client 40 monitors the user's mailbox on the e-mail server 34 for new e-mail. Upon detecting a new email, the personal client 40 sends a trigger 132 to the mobile device 21 via the management server 28. The trigger 132 may be a message without a payload that simply informs the mobile device 21 that something new has happened to the user's mailbox. By the trigger 132, the mobile device 21 establishes a mobile connection 23 with the management server 28 and sends a synchronization request transaction 134 to the personal client 40.
In one implementation, the short message service (SMS) message 126 is used to establish a mobile connection 23 on the mobile device 21 and send a synchronization request transaction 134. The management server 28 is connected to the short message service controller (SMSC) 128 operated by the mobile communication service carrier via the notification gateway 130. In other practices, other notification protocols, such as Wireless Application Protocol (WAP) push, are used to provoke mobile device 21.
The personal client 40 generates trigger message 132 whenever the event associated with the user's mailbox 136 matches the event identified by filter 138. The trigger message 132 causes the management server 28 to send a message to the SMSC 128 via the notification gateway 130. Therefore, the SMSC128 sends an SMS message 126 to the mobile device 24.
The mobile device 21 serves as a monitor for a particular SMS message with a particular content that can be read by a computer. Upon receiving the SMS message 126 having the specific content, the mobile device 21 initiates a mobile connection with the management server 28. The mobile device 21 may extract the SMS message 126 from the user column before the user has a chance to see the SMS message 126.
The mobile device 21 starts the authentication process on the management server 28. After successful authentication, a synchronization request 134 is sent from the mobile device 21 to the management server 28. The management server 28 forwards its synchronization request 134 to the personal client 40 over the previously established connection 25. Upon receiving the synchronization request 134, the personal client 40 sends back a response 133 containing a list of the latest emails in the user's mailbox 136.
<u style="single">High priority (high priority) email</u> Also, in FIG. 6, the connection architecture shown above can be used to provide high priority email notifications. The personal client 40 may be configured to monitor the email server 34 for a particular type of email message. For example, filter 138 may allow the personal client 40 to look for email sent from a particular originator email address. For example, an email sent by a user's boss.
Whenever an email sent from a boss's email address arrives at the user's mailbox 136, the personal client 40 sends the minimum required version of the email to SMSC128 via the management server 28. For example, the minimum required version may identify only the originator, time, date, and subject of an email message. The SMSC128 then sends an SMS high priority message 124 to the mobile device 24.
The minimum required high priority message 124 may be slightly different from the SMS message 126 used to trigger synchronization of mobile devices. For example, SMS message 126 may not include some email content, while priority message 124 contains some portion of the actual email content received in the mailbox. The high priority message 124 can be sent to any SMS-enabled mobile device.
<u style="single">Power management</u> The mobile device 21 can periodically start synchronization according to the amount of charge remaining in the battery 123. For example, when the battery 123 has a relatively large amount of remaining charge, the mobile device 21 may synchronize more often than when the battery 123 has a relatively small amount of remaining charge. Systems for determining the remaining charge of a battery are well known and therefore are not described in detail here.
Different charge gradient levels can be used to change how well the mobile device 21 synchronizes with the personal client 40. For example, the mobile device 21 may synchronize every 5 minutes when the battery 123 has a remaining charge of 75% or more, and may synchronize every 10 minutes when the battery 123 has a remaining charge of 50 to 75%. .. Also, when the battery 123 is 25-50% charged, the mobile device 21 may only synchronize with the personal client 40 every 30 minutes. Other charge / sync ratios can also be used.
In order to save more power and use it, the synchronization rate can be changed according to the day of the week. For example, the mobile device 21 may be less synchronized on weekends than on weekdays.
<u style="single">wrap up</u> The system described above can use a dedicated processor system, a microcontroller, a programmable logic circuit, or a microprocessor that performs some or all of the processing. Some of the above processes may be executed by software, and other processes may be executed by hardware.
For convenience, such processing is described as various correlated functional blocks, or separate software modules. However, this is not necessary and may be the case when these functional blocks or modules do not have clear boundaries and are equally integrated into a single logic circuit, program or process. In any case, functional blocks and software modules, or features of adaptable interfaces, can be performed by themselves or in combination with other processing, either in hardware and software.
Although the principles of the invention have been described using preferred embodiments thereof, it is clear that the invention can be modified in its arrangement and details without departing from such principles. Therefore, we request all modifications and changes contained within the spirit and scope of the appended claims.
<figref num="1">It is a block diagram of the mobile communication architecture in one Embodiment of this invention.</figref><figref num="2">It is a block diagram of the enterprise version of the communication architecture.</figref><figref num="3">It is a block diagram which shows how the transaction is transferred in the communication architecture shown in FIG. 1 and FIG.</figref><figref num="4">It is a block diagram showing how a local network file is shown and selected by a mobile device.</figref><figref num="5">It is a block diagram which shows how data is stored in a mobile device.</figref><figref num="6">It is a block diagram which shows how to synchronize a mobile device.</figref>
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US9712986B2 | Cited by | United States of America | Applicant |
| US10263899B2 | Cited by | United States of America | Applicant |
| US9832095B2 | Cited by | United States of America | Applicant |
| JP2001356973A | Cites | Japan | – |
| JP2001350718A | Cites | Japan | – |
| JP10336372A | Cites | Japan | – |
124 members in 5 offices
Priority claims14
| Document | Office | Kind | Date |
|---|---|---|---|
| 34688102 | United States of America | P | |
| 34688102 | United States of America | P | |
| 60346881 | United States of America | – | |
| 40324902 | United States of America | P | |
| 40324902 | United States of America | P | |
| 60403249 | United States of America | – | |
| 0300618 | United States of America | W | |
| 0300618 | United States of America | W | |
| 2002346881 | – | – | – |
| 2002403249 | – | – | – |
| 2003000618 | – | – | – |
| US20020346881P | – | – | – |
| US20020403249P | – | – | – |
| WO2003US00618 | – | – | – |
Members124
| Document | Office | Kind | |
|---|---|---|---|
| WO03058483A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO03058879A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU2003207495A1 | Australia | A1 | |
| AU2003209194A1 | Australia | A1 | |
| US2003157947A1 | United States of America | A1 | |
| US2003235308A1 | United States of America | A1 | |
| EP1466261A1 | European Patent Office (EPO) | A1 | |
| EP1466435A1 | European Patent Office (EPO) | A1 | |
| JP2005515660A | Japan | A | |
| JP2005515664A | Japan | A | |
| US7139565B2 | United States of America | B2 | |
| US2007027832A1 | United States of America | A1 | |
| US2007027886A1 | United States of America | A1 | |
| US2007027917A1 | United States of America | A1 | |
| US2007027920A1 | United States of America | A1 | |
| US2007027921A1 | United States of America | A1 | |
| US2007027930A1 | United States of America | A1 | |
| WO2007015725A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007015726A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007015725A3 | World Intellectual Property Organization (WIPO) | A3 | |
| US7305700B2 | United States of America | B2 | |
| US2007290787A1 | United States of America | A1 | |
| US2007293238A1 | United States of America | A1 | |
| WO2007149526A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007149540A2 | World Intellectual Property Organization (WIPO) | A2 | |
| US2008001717A1 | United States of America | A1 | |
| US2008037787A1 | United States of America | A1 | |
| US2008133641A1 | United States of America | A1 | |
| US2008133708A1 | United States of America | A1 | |
| US2008134292A1 | United States of America | A1 | |
| US2008140665A1 | United States of America | A1 | |
| WO2007149526A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2007149540A3 | World Intellectual Property Organization (WIPO) | A3 | |
| JP4386732B2This record | Japan | B2 | |
| EP1466261A4 | European Patent Office (EPO) | A4 | |
| US7769395B2 | United States of America | B2 | |
| US7827597B2 | United States of America | B2 | |
| US7853563B2 | United States of America | B2 | |
| US7917468B2 | United States of America | B2 | |
| US7917505B2 | United States of America | B2 | |
| US2011099363A1 | United States of America | A1 | |
| EP1466435A4 | European Patent Office (EPO) | A4 | |
| US2011165889A1 | United States of America | A1 | |
| US2011207436A1 | United States of America | A1 | |
| US2011213898A1 | United States of America | A1 | |
| US8069166B2 | United States of America | B2 | |
| US8127342B2 | United States of America | B2 | |
| US2012210121A1 | United States of America | A1 | |
| US8412675B2 | United States of America | B2 | |
| US8468126B2 | United States of America | B2 | |
| US8549587B2 | United States of America | B2 | |
| US8811952B2 | United States of America | B2 | |
| US8989728B2 | United States of America | B2 | |
| US9055102B2 | United States of America | B2 | |
| US2015161190A1 | United States of America | A1 | |
| US2015163180A1 | United States of America | A1 | |
| US2015264522A1 | United States of America | A1 | |
| US2015372987A1 | United States of America | A1 | |
| US9251193B2 | United States of America | B2 | |
| US2016036753A1 | United States of America | A1 | |
| US2016036760A1 | United States of America | A1 | |
| US9344393B2 | United States of America | B2 | |
| US9369424B2 | United States of America | B2 | |
| US2016234146A1 | United States of America | A1 | |
| US9438550B2 | United States of America | B2 | |
| US2016330159A1 | United States of America | A1 | |
| US2016337463A1 | United States of America | A1 | |
| US2016352691A1 | United States of America | A1 | |
| US2017006122A1 | United States of America | A1 | |
| US2017048182A1 | United States of America | A1 | |
| US9602457B2 | United States of America | B2 | |
| US9608968B2 | United States of America | B2 | |
| US9712476B2 | United States of America | B2 | |
| US2017302636A1 | United States of America | A1 | |
| EP1466261B1 | European Patent Office (EPO) | B1 | |
| US9930478B2 | United States of America | B2 | |
| US2018160275A1 | United States of America | A1 | |
| US2018176722A1 | United States of America | A1 | |
| US10084739B2 | United States of America | B2 | |
| US10110534B2 | United States of America | B2 | |
| US2018324704A1 | United States of America | A1 | |
| EP3401794A1 | European Patent Office (EPO) | A1 | |
| US10135771B2 | United States of America | B2 | |
| US2019068538A1 | United States of America | A1 | |
| US2019149503A1 | United States of America | A1 | |
| US10298708B2 | United States of America | B2 | |
| EP1466435B1 | European Patent Office (EPO) | B1 | |
| US10313464B2 | United States of America | B2 | |
| US2019268430A1 | United States of America | A1 | |
| US10474660B2 | United States of America | B2 | |
| EP3570178A1 | European Patent Office (EPO) | A1 | |
| US2020081878A1 | United States of America | A1 | |
| EP3570178B1 | European Patent Office (EPO) | B1 | |
| US10693531B2 | United States of America | B2 | |
| US10720974B2 | United States of America | B2 | |
| US2020274584A1 | United States of America | A1 | |
| US2020313734A1 | United States of America | A1 | |
| US2020313735A1 | United States of America | A1 | |
| US10804976B2 | United States of America | B2 | |
| US10804980B1 | United States of America | B1 |
35 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of completion of termEXPY | EXPY | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Transfer to examiner for re-examination before appeal (zenchi)AppealJAPANESE INTERMEDIATE CODE: A911A911 | A911 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A821A521 | A521 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Decision of refusalJAPANESE INTERMEDIATE CODE: A02A02 | A02 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 4386732
- Publication, DOCDB
- 4386732
- Publication, EPODOC
- JP4386732B
- Application
- 558726
- Application, DOCDB
- 2003558726
- Application, EPODOC
- JP20030558726
Titles2
- Japanese
- モバイルネットワークの接続アーキテクチャ
- English
- Mobile network connection architecture
Classification
- CPC, 25
- H04L63/0281
- H04L63/0428
- H04L63/029
- H04L63/0464
- H04L63/08
- H04L63/0807
- H04W4/12
- H04W88/06
- H04L67/1095
- H04L67/14
- H04L67/04
- H04L69/329
- H04L63/0272
- H04W76/10
- H04W12/04
- H04L63/0471
- H04W52/0261
- H04L9/3226
- H04L2209/80
- Y02D30/70
- H04W12/03
- H04L51/58
- H04B7/0617
- H04B7/0417
- Y02D10/00
- IPC, 12
- H04L12 46
- G06F12 00
- G06F13 00
- H04L9 08
- H04L9 14
- H04L12 22
- H04L12 58
- H04L29 06
- H04L29 08
- H04W4 12
- H04W76 02
- H04W88 06
