Data-capable network prioritization with reject code handling
Abstract
This record has no abstract on file.
Term
Term ended
Expired 12 November 2024, 1.9 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
53 claims: 5 independent, 48 dependent
- 1通信のため に 無線通信ネットワーク を選 択する際に 移動局により 使用 される 方法であって、 前記移動局は、音声サービスおよび汎用パケット無線サービス(GPRS)サービスを用いて通信するように適合されており、 前記方法は、 前記移動局が、通信のために第1の無線ネットワークを選択することを試みて、前記第1の無線ネットワークを介した前記音声サービスに対する音声接続および前記GPRSサービスに対するデータ接続の要求を伝送することと、 前記移動局が、 前記第1の無線ネットワークを介したデータ接続の要求に 応答して前記移動局によって前記第1の無線ネットワークから 拒 否が 受信された場合に、前記第1の無線ネットワークを介してデータ接続の要求を少なくとも1回再試行することと、 前記移動局が、 前記第1の無線ネットワークを介したデータ接続の要求 が成功せずに前記少なくとも1回再試行された後に 、通信のために第2の無線ネットワーク を 選択 することを試みる ことと、 前記移動局が、前記第1の無線ネットワークを介したデータ接続の要求に応答して前記移動局によって前記第1の無線ネットワークからエラー値14を有する拒否コードが受信された場合に、前記第1の無線ネットワークを介したデータ接続の要求を前記少なくとも1回再試行せずに、通信のために前記第2の無線ネットワークを選択することを試みることであって、前記エラー値14は、前記GPRSサービスが前記第1の無線ネットワークにおいて許可されていないことを示す、ことと を 含む 、方法。
- 2前記データ接続の要求が、汎用パケット無線サービス(GPRS)所属要求を 含む 、請求項1に記載の方法。
- 3前記データ接続の要求が、パケットデータプロトコル(PDP)コンテキスト要求を 含む 、請求項1に記載の方法。
- 4前記移動局が、前記移動局のエンドユーザに関連したサービス加入または前記第1の無線ネットワークに存在する永続的な問題または欠点に前記エラー値14を有する拒否コードが対応するか否かを識別することをさらに含む、請求項1に記載の方法。
- 5前記移動局が、 前記拒否コードを複数のエラー 値 のそれぞれと比較し、前記拒否コードと前記複数のエラー 値 の1つとの間の一致を識別することによって、前記拒否コードが 前記エラー値14を有していることを 識別することをさらに 含む 、請求項1に記載の方法。
- 6前記移動局は、 所定の回数まで前記要求を再試行すること によって、前記第1の無線ネットワークを介したデータ接続の要求を再試行する 、請求項1に記載の方法。
- 7前記移動局は、ユーザの介入なしで前記データ接続の要求を再試行する、請求項1に記載の方法。
- 8前記移動局は、 前記第1の無線ネットワークが、 前記 音声およびデータ接続を前記移動局に 現在 利用可能にするか否かの指示を維持 し、 前記第1の無線ネットワーク に対する 指示 は 、前記データ接続の要求が許可された場合 には 、現在利用可能なデータ接続を示し、 前記第1の無線ネットワーク に対する 指示 は 、前記 エラー値14を有する 拒否コード が 受信 された 場合 には 、現在利用不可能なデータ接続を示し、 前記第1の無線ネットワーク に対する 指示 は 、前記第1の無線ネットワーク を介した 前記データ接続の要求が成功 せずに前記 少なくとも1回再試行された後 には 、現在利用不可能なデータ接続を示す、請求項1に記載の方法。
- 9前記移動局は、 前記移動局 に対する 現在利用不可能なデータサービスネットワークのリストを維持 し、 前記現在利用不可能なデータサービスネットワークの リスト は、前記エラー値14を有する拒否コードが受信された場合には、 前記第1の無線ネットワークを含み、 前記現在利用不可能なデータサービスネットワークのリストは、 前記第1の無線ネットワーク を介した 前記データ接続の要求が成功 せずに前記 少なくとも1回再試行された場合 には、 前記第1の無線ネットワークを含み、 前記現在利用不可能なデータサービスネットワークのリストは、 前記データ接続の要求が許可された場合 には、 前記第1の無線ネットワークを含まない、請求項1に記載の方法。
- 10通信のために無線通信ネットワークを選択する際に移動局によって使用されるコンピュータプログラムであって、前記移動局は、音声サービスおよび汎用パケット無線サービス(GPRS)サービスを用いて通信するように適合されており、前記コンピュータプログラムは、プロセッサに手順を実行させ、 前記手順は、 前記プロセッサが、通信のために第1の無線ネットワークを選択することを試みて、前記第1の無線ネットワークを介した前記音声サービスに対する音声接続および前記GPRSサービスに対するデータ接続の要求をリクエストすることと、 前記プロセッサが、 前記第1の無線ネットワークを介したデータ接続の要求に 応答して前記第1の無線ネットワークから 拒 否が 受信された場合に、前記第1の無線ネットワークを介してデータ接続の要求 を再 試行 することと 、 前記プロセッサが、 前記第1の無線ネットワークを介したデータ接続の要求 が成功せずに少なく1回再試行された後に、 通信のために第2の無線ネットワーク を 選択 することを試みることと、 前記プロセッサが、前記第1の無線ネットワークを介したデータ接続の要求に応答してエラー値14を有する拒否コードが受信された場合に、前記第1の無線ネットワークを介したデータ接続の要求を再試行せずに、通信のために前記第2の無線ネットワークを選択することを試みることであって、前記エラー値14は、前記GPRSサービスが前記第1の無線ネットワークにおいて許可されていないことを示す、ことと を含む、 コンピュータプログラ ム。
- 11前記データ接続の要求が 、 汎用パケット無線サービス(GPRS)所属要求を 含む 、請求項10に記載のコンピュータプログラ ム。
- 12前記データ接続の要求が 、 パケットデータプロトコル(PDP)コンテキスト要求を 含む 、請求項10に記載のコンピュータプログラ ム。
- 13前記手順が、 前記プロセッサが、前記移動局のエンドユーザに関連したサービス加入または前記第1の無線ネットワークに存在する永続的な問題または欠点に前記エラー値14を有する拒否コードが対応するか否かを識別することをさらに含む、請求項10に記載のコンピュータプログラム。
- 14前記 手順 が、 前記プロセッサが、 前記拒否コードを複数のエラー 値 のそれぞれと比較し、前記拒否コードと前記複数のエラー 値 の1つとの間の一致を識別することによって、前記拒否コードが 前記エラー値14を有していること を識別する ことをさらに含む 、請求項10に記載のコンピュータプログラ ム。
- 15前記手順が、 前記プロセッサが、 所定の回数まで前記要求を再試行すること によって、前記第1の無線ネットワークを介したデータ接続の要求を再試行することをさらに含む 、請求項10に記載のコンピュータプログラ ム。
- 16前記手順が、 前記プロセッサが、ユーザの介入なしで前記データ接続の要求を再試行することをさらに含む、請求項10に記載のコンピュータプログラム。
- 17前記手順が、 前記プロセッサが 、前記第1の無線ネットワーク が、前記 音声およびデータ接続を前記移動局に 現在 利用可能にするか否かの指示を維持する ことをさらに含み 、 前記第1の無線ネットワーク に対する 指示 は 、前記データ接続の要求が許可された場合 には 、現在利用可能なデータ接続を示し、 前記第1の無線ネットワーク に対する 指示 は 、前記 エラー値14を有する 拒否コード が 受信 された 場合 には 、現在利用不可能なデータ接続を示し、 前記第1の無線ネットワーク に対する 指示 は 、前記第1の無線ネットワーク を介した 前記データ接続の要求が成功 せずに 再試行された後 には 、現在利用不可能なデータ接続を示す、請求項10に記載のコンピュータプログラ ム。
- 18前記 手順が、 前記プロセッサが 、前記移動局 に対する 現在利用不可能なデータサービスネットワークのリストを維持する ことをさらに含み 、 前記現在利用不可能なデータサービスネットワークの リスト は、前記エラー値14を有する拒否コードが受信された場合には、 前記第1の無線ネットワークを含み、 前記現在利用不可能なデータサービスネットワークのリストは、 前記第1の無線ネットワーク を介した 前記データ接続の要求が成功 せずに 再試行された場合 には、 前記第1の無線ネットワークを含み、 前記現在利用不可能なデータサービスネットワークのリストは、 前記データ接続の要求が許可された場合 には、 前記第1の無線ネットワークを含まない、請求項10に記載のコンピュータプログラ ム。
- 19音声サービスおよび汎用パケット無線サービス(GPRS)サービスを用いて通信するように適合された移動局であって、 前記移動局は、 1つ以上のプロセッサと、 前記1つ以上のプロセッサに結合されたメモリと、 前記1つ以上のプロセッサに結合された無線トランシーバ と を備え 、 前記1つ以上のプロセッサが、 通信のために第1の無線ネットワークを選択することを試みて、前記無線トランシーバを用いて前記第1の無線ネットワークを介した前記音声サービスに対する音声接続および前記GPRSサービスに対するデータ接続の要求を伝送することと、 前記第1の無線ネットワークを介し たデ ータ接続の要求に 応答して前記無線トランシーバを介して前記第1の無線ネットワークから 拒 否が 受信された場合に、前記第1の無線ネットワークを介してデータ接続の要求を少なくとも1回再試行する ことと、 前記第1の無線ネットワークを介し たデ ータ接続の要求 が成功せずに前記少なくとも1回再試行された後に、 通信のために第2の無線ネットワーク を 選択 することを試みることと、 前記第1の無線ネットワークを介したデータ接続の要求に応答して前記無線トランシーバを介して前記第1の無線ネットワークからエラー値14を有する拒否コードが受信された場合に、前記第1の無線ネットワークを介したデータ接続の要求を再試行せずに、通信のために前記第2の無線ネットワークを選択することを試みることであって、前記エラー値14は、前記GPRSサービスが前記第1の無線ネットワークにおいて許可されていないことを示す、ことと を実行するように 動作する、移動局。
- 20前記データ接続の要求が 、 汎用パケット無線サービス(GPRS)所属要求を 含む 、請求項19に記載の移動局。
- 21前記データ接続の要求が、パケットデータプロトコル(PDP)コンテキスト要求を 含む 、請求項19に記載の移動局。
- 22前記1つ以上のプロセッサが、 前記移動局のエンドユーザに関連したサービス加入または前記第1の無線ネットワークに存在する永続的な問題または欠点に前記拒否コードが対応するか否かを識別することによって、前記拒否コードが前記エラー値14を有するか否かを識別するようにさらに動作する、請求項19に記載の移動局。
- 23前記1つ以上のプロセッサが 、 前記拒否コードを 前記 メモリ内に格納されている複数のエラー 値 のそれぞれと比較し、前記拒否コードと前記複数のエラー 値 の1つとの間の一致を識別することによって、前記拒否コードが 前記エラー値14を有していることを 識別する よう にさらに動作する、請求項19に記載の移動局。
- 24前記 移動局 が、所定の回数まで前記要求を再試行することによって、前記第1の無線ネットワーク を介した 前記データ接続の要求を再試行する 、 請求項19に記載の移動局。
- 25前記1つ以上のプロセッサが、ユーザの介入なしで前記データ接続の要求を再試行する、請求項19に記載の移動局。
- 26前記1つ以上のプロセッサが、前記第1の無線ネットワークが 、前記 音声およびデータ接続を前記移動局に 現在 利用可能にするか否かの指示を維持 し、 前記第1の無線ネットワーク に対する 指示 は 、前記データ接続の要求が許可された場合 には 、現在利用可能なデータ接続を示し、 前記第1の無線ネットワーク に対する 指示 は 、前記 エラー値14を有する 拒否コード が 受信 された 場合 には 、現在利用不可能なデータ接続を示し、 前記第1の無線ネットワーク に対する 指示 は 、前記第1の無線ネットワーク を介した 前記データ接続の要求が成功 せずに 再試行された後 には 、現在利用不可能なデータ接続を示す、請求項19に記載の移動局。
- 27前記1つ以上のプロセッサ は 、前記移動局 に対する 現在利用不可能なデータサービスネットワークのリストを維持 し、 前記現在利用不可能なデータサービスネットワークの リスト は、前記エラー値14を有する拒否コードが受信された場合には、 前記第1の無線ネットワークを含み、 前記現在利用不可能なデータサービスネットワークのリストは、 前記第1の無線ネットワーク を介した 前記データ接続の要求が成功 せずに 再試行された場合 には、 前記第1の無線ネットワークを含み、 前記現在利用不可能なデータサービスネットワークのリストは、 前記データ接続の要求が許可された場合 には、 前記第1の無線ネットワークを含まない、請求項19に記載の移動局。
- 28第1の無線通信ネットワークと、 第2の無線通信ネットワークと、 前記第1の無線通信ネットワークおよび前記第2の通信ネットワークから通信のために1つを選択する よう に 動作 する移動局 と を備え る 、通信システムであって、 前記移動局は、音声サービスおよび汎用パケット無線サービス(GPRS)サービスを用いて通信するように適合されており、 前記移動局 は 、 1つ以上のプロセッサと、 前記1つ以上のプロセッサに結合されたメモリと、 前記1つ以上のプロセッサに結合された無線トランシーバ と を含み、 前記1つ以上のプロセッサ は 、 通信のために前記第1の無線ネットワークを選択することを試みて、前記無線トランシーバを用いて前記第1の無線ネットワークを介した前記音声サービスに対する音声接続および前記GPRSサービスに対するデータ接続の要求を伝送することと、 前記第1の無線ネットワークを介し た 前記データ接続の要求が許可された ことを 識別 することに 基づいて、通信のために 前記 第1の無線ネットワークを選択させる ことと、 前記第1の無線ネットワークを介した前記データ接続の要求に 応答して前記無線トランシーバを介して前記第1の無線ネットワークから 拒 否が 受信された場合に、前記第1の無線ネットワークを介してデータ接続の要求 を再 試行する ことと、 前記第1の無線ネットワークを介し たデ ータ接続の要求 が成功せずに少なくとも1回再試行された後に、 通信のために前記第2の無線ネットワーク を 選択 することを試みることと、 前記第1の無線ネットワークを介したデータ接続の要求に応答して前記無線トランシーバを介して前記第1の無線ネットワークからエラー値14を有する拒否コードが受信された場合に、前記第1の無線ネットワークを介したデータ接続の要求を再試行せずに、通信のために前記第2の無線ネットワークを選択することを試みることであって、前記エラー値14は、前記GPRSサービスが前記第1の無線ネットワークにおいて許可されていないことを示す、ことと を実行するように 動作する、通信システム。
- 29前記データ接続の要求が、汎用パケット無線サービス(GPRS)所属要求を 含む 、請求項28に記載の通信システム。
- 30前記データ接続の要求が、パケットデータプロトコル(PDP)コンテキスト要求を 含む 、請求項28に記載の通信システム。
- 31前記1つ以上のプロセッサが、 前記移動局のエンドユーザに関連したサービス加入または前記第1の無線ネットワークに存在する永続的な問題または欠点に前記拒否コードが対応するか否かを識別することによって、前記拒否コードが前記エラー値14を有するか否かを識別するようにさらに動作する、請求項28に記載の通信システム。
- 32前記1つ以上のプロセッサが 、 前記第1の無線ネットワークを介し た データ接続の要求が許可された ことを 識別 すること に基づいて、通信のために 前記 第1の無線ネットワークを選択させる ようにさらに動作する 、請求項28に記載の通信システム。
- 33前記 通信システム が、所定の回数まで前記要求を再試行することによって、前記第1の無線ネットワーク を介した 前記データ接続の要求を再試行す る、 請求項28に記載の通信システム。
- 34前記移動局の前記1つ以上のプロセッサが、ユーザの介入なしで前記データ接続の要求を再試行する、請求項28に記載の通信システム。
- 35前記 通信システムが、 前記第1の無線ネットワークが 、前記 音声およびデータ接続を前記移動局に 現在 利用可能にするか否かの指示を維持 し、 前記第1の無線ネットワーク に対する 指示が、前記データ接続の要求が許可された場合 には 、現在利用可能なデータ接続を示し、 前記第1の無線ネットワーク に対する 指示が、前記 エラー値14を有する 拒否コード が 受信 された 場合 には 、現在利用不可能なデータ接続を示し、 前記第1の無線ネットワーク に対する 指示が、前記第1の無線ネットワーク を介した 前記データ接続の要求が成功 せずに 再試行された後 には 、現在利用不可能なデータ接続を示す、請求項28に記載の通信システム。
- 36前記 通信システムは 、前記移動局 に対する 現在利用不可能なデータサービスネットワークのリストを維持 し 、 前記現在利用不可能なデータサービスネットワークの リスト は、前記エラー値14を有する拒否コードが受信された場合には、 前記第1の無線ネットワークを含み、 前記現在利用不可能なデータサービスネットワークのリストは、 前記第1の無線ネットワーク を介した 前記データ接続の要求が成功 せずに 再試行された場合 には、 前記第1の無線ネットワークを含み、 前記現在利用不可能なデータサービスネットワークのリストは、 前記データ接続の要求が許可された場合 には、 前記第1の無線ネットワークを含まない、請求項28に記載の通信システム。
- 37移動局との通信のために無線通信ネットワークを選択する際に使用する方法であって、前記移動局は、音声サービスおよび汎用パケット無線サービス(GPRS)サービスを用いて通信するように適合されており、 前記方法は、 前記移動局が、通信のために第1の無線ネットワークを選択することを試みて、前記第1の無線ネットワークを介した前記音声サービスに対する音声接続および前記GPRSサービスに対するデータ接続の要求を伝送することと、 前記移動局が、前記第1の無線ネットワークを介したデータ接続の要求に応答して拒否が受信された場合に、前記第1の無線ネットワークを介してデータ接続の要求を少なくとも1回再試行することと、 前記移動局が、前記第1の無線ネットワークを介したデータ接続の要求に応答して前記第1の無線ネットワークからエラー値14を有する拒否コードが受信された場合に、前記第1の無線ネットワークを介したデータ接続の要求を前記少なくとも1回再試行せずに、通信のために第2の無線ネットワークを選択することを試みることであって、前記エラー値14は、前記GPRSサービスが前記第1の無線ネットワークにおいて許可されていないことを示す、ことと を含み、 前記移動局は、前記第1の無線ネットワークが、前記音声およびデータ接続を前記移動局に現在利用可能にするか否かの指示を維持し、 前記指示は、 前記データ接続の要求が許可された場合には、現在利用可能なデータ接続を示し、 (1)重大なエラーを含む前記拒否コードが前記データ接続の要求に応答して受信された場合、および(2)前記第1の無線ネットワークを介したデータ接続の要求が成功せずに前記少なくとも1回再試行された場合のうちの1つの場合において、現在利用不可能なデータ接続を示す、方法。
- 38前記データ接続の要求が、汎用パケット無線サービス(GPRS)所属要求およびパケットデータプロトコル(PDP)コンテキスト要求のうちの1つを含む、請求項37に記載の方法。
- 39前記移動局が、前記第1の無線ネットワークを介したデータ接続の要求が成功せずに前記少なくとも1回再試行された後に、通信のために前記第2の無線ネットワークを選択することを試みることをさらに含む、請求項37に記載の方法。
- 40前記移動局は、所定の回数まで前記要求を再試行することによって、前記第1の無線ネットワークを介したデータ接続の要求を再試行する、請求項37に記載の方法。
- 41前記移動局が、前記移動局のエンドユーザに関連したサービス加入または前記第1の無線ネットワークに存在する永続的な問題または欠点に前記拒否コードが対応するか否かを識別することによって、前記拒否コードが前記エラー値14を有するか否かを識別することをさらに含む、請求項37に記載の方法。
- 42前記データ接続の要求は、ルーティングエリア更新(RAU)要求を含む、請求項1に記載の方法。
- 43前記データ接続の要求は、ルーティングエリア更新(RAU)要求を含む、請求項10に記載のコンピュータプログラム。
- 44前記データ接続の要求は、ルーティングエリア更新(RAU)要求を含む、請求項19に記載の移動局。
- 45前記データ接続の要求は、ルーティングエリア更新(RAU)要求を含む、請求項28に記載の通信システム。
- 46前記エラー値14を有する拒否コードは、データサービスが前記第1の無線ネットワークによって許可されていないことを示す、請求項1に記載の方法。
- 47前記エラー値14を有する拒否コードは、データサービスが前記第1の無線ネットワークによって許可されていないことを示す、請求項10に記載のコンピュータプログラム。
- 48前記エラー値14を有する拒否コードは、データサービスが前記第1の無線ネットワークによって許可されていないことを示す、請求項19に記載の移動局。
- 49前記エラー値14を有する拒否コードは、データサービスが前記第1の無線ネットワークによって許可されていないことを示す、請求項28に記載の通信システム。
- 50前記移動局は、前記第1の無線ネットワークが前記移動局のオペレータ制御の公衆陸上移動体ネットワーク(O-PLMN)リストまたはユーザ制御のPLMN(U-PLMN)リストにない場合にのみ、通信のために前記第2の無線ネットワークを選択することを試みる、請求項1に記載の方法。
- 51前記手順は、 前記プロセッサが、前記第1の無線ネットワークが前記移動局のオペレータ制御の公衆陸上移動体ネットワーク(O-PLMN)リストまたはユーザ制御のPLMN(U-PLMN)リストにない場合にのみ、通信のために前記第2の無線ネットワークを選択することを試みることをさらに含む、請求項10に記載のコンピュータプログラム。
- 52前記移動局は、前記第1の無線ネットワークが前記移動局のオペレータ制御の公衆陸上移動体ネットワーク(O-PLMN)リストまたはユーザ制御のPLMN(U-PLMN)リストにない場合にのみ、通信のために前記第2の無線ネットワークを選択することを試みる、請求項19に記載の移動局。
- 53前記通信システムは、前記第1の無線ネットワークが前記移動局のオペレータ制御の公衆陸上移動体ネットワーク(O-PLMN)リストまたはユーザ制御のPLMN(U-PLMN)リストにない場合にのみ、通信のために前記第2の無線ネットワークを選択することを試みる、請求項28に記載の通信システム。
Independent claims53
92 paragraphs, as filed
The present application generally relates to mobile stations and network selection methods used by mobile stations.
A mobile communication device, such as a mobile phone mobile station, can make and receive telephone calls and / or transmit and receive data on a wireless communication network. Before this becomes possible, the mobile station will select and register one of several communication networks within its geographic service area. After registering with the selected network, the mobile station operates in standby mode to monitor calls or messages on certain wireless communication channels that "camp on" the network. "Network selection" is a specific process performed by a mobile station to select a single communication network through which it registers and operates.
Mobile phone operation and network selection schemes are recorded in standard specifications that regulate the behavior of mobile mobile stations and related systems. One of the well-known mobile phone standards is the Global Standard Mobile Communication (GSM) standard. GSM 03.22 / European Communication Standards Organization (ETSI) Technical Specification (TS) 100930, 3GPP 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 23.122, and other related standards for mobile phone operation and network selection It describes a lot of things in detail. These documents are referred to as service areas with networks (public land mobile networks or PLMNs) primarily intended to provide continuous telephone services when traveling and roaming between different regions and countries. ) Is described how the mobile station behaves in order to maintain.
Traditionally, mobile stations perform network selection by scanning to first identify all available communication networks within their surrounding service area. Each network is identified by a unique set of mobile country code (MCC) and mobile network code (MNC). If a mobile station's home public land mobile network (HPLMN) or "home network" is available, the mobile station will typically select and operate a home network. If HPLMN is not available, the mobile station will typically select and operate the communication network with the highest priority from the preferred network list stored in the mobile station's memory. There may be several preferred network lists stored on the mobile station's subscriber identification module (SIM) card, commonly referred to as the preferred PLMN list (PPLMN list). For example, the PPLMN list may include a user-controlled PPLMN (U-PPLMN) list and an operator-controlled PPLMN (O-PPLMN) list.
The network selection method described above is commonly referred to as an "automatic" network selection method. As an alternative to this automatic selection method, mobile station end users may be provided with the ability to manually select from multiple available networks in a list that is visible to the mobile station. Good. This traditional network selection method is sometimes referred to as the "manual" network selection method.
Mobile data communication devices, which are known to facilitate services such as wireless e-mail and Internet access as well as voice telephone technology, are becoming more and more widespread. In addition to operating according to GSM for voice telephone technology, these mobile stations can operate according to General Line Radio Service (GPRS). GPRS is a packet-based communication protocol for mobile stations that allows the transmission and reception of data packets over wireless communication networks. To receive data services over a GPRS-enabled network, the mobile station first implements a "GPRS affiliation" to provide its identification code and availability for the wireless network. For GSM / GPRS, this code identifies the International Mobile Subscriber Identity (IMSI) or Temporary Mobile Subscriber Identity (PTMSI), which identifies the account or subscription of the communications network, and the mobile station user or subscriber. May include both mobile station ISDN / PSTN number MSISDN. After belonging to the network, the mobile station will attempt to establish a "packet data protocol (PDP) context". The PDP context targets mobile access point names (APNs) and home services. The PDP context also assigns IP addresses to mobile stations so that IP packets can be delivered.
To be fully operational as intended, these "data-capable" mobile stations must have the appropriate communication services supported and enabled by the registered communication network. .. Ideally, all communication networks around the world should be connected by roaming agreements to support and enable all heterogeneous communication services that mobile stations can provide. However, in practice, some communication networks do not have or are unable to create certain communication services (eg, data communication services) available to mobile stations. This problem can be partially mitigated in a given service area, as there may be several communication networks that the mobile station can choose from.
However, traditional network selection techniques for GSM services do not consider the availability of other services (eg, data communication services) in their decision-making process. That is, the conventional network selection technology is centered on voice services. As a result, such mobile stations can select improper communication networks. For example, a mobile station may select a communication network that can provide authorized voice services but not authorized data services, even though another legitimate and available network can provide both voice and data services. .. Such conventional behavior is not particularly desirable for mobile stations intended primarily to provide data communication services (eg, mobile email services) to end users. Specifically, GPRS / GSM-enabled networks are more preferred for these mobile stations than GSM-only networks.
Better non-conventional network selection techniques for these mobile stations will include prioritizing the selection of data-enabled communication networks (eg GPRS) by voice-only networks (eg GSM). .. In such a procedure, the mobile station may have to determine whether the data service is actually made available by its communication network. More specifically, mobile stations make requests for data services that can be allowed or denied by the network. When a data service is rejected, the mobile station receives different "rejection reason codes" from different networks associated with different causes of the service refusal. Depending on the denial code, the mobile station must wait until the data service is reclaimed, the timer expires, the network changes, or the user powers the mobile device off and on again. Sometimes. If the end user is not looking at the mobile station's display (for example, the mobile station is being carried in a holster), the user will not be aware of the unavailability of the data service and important push data (eg, for example). Push-type delivered e-mail message) cannot be received in a timely manner.
In a related issue, if a GPRS belonging or routing area update (RAU) attempt is unsuccessful on that network (for example, no network response or reception of a deny code), the mobile station will retry up to 5 times in a row. To do. If the GPRS affiliation or RAU trial counter is 5 or higher, the mobile station must put itself in the "GPRS deregistration" state and activate the timer designated as "Timer 3302". Timer 3302 is set to a value taken from the GSM timer 3212, which is a periodic position update timer. See, for example, 1997 3GPP Standard Release 4.08. Starting with 1999 3GPP standard release 24.08, the default value for the T3302 is 12 minutes if the network does not provide a value. Therefore, mobile stations typically receive the value for timer 3212 wirelessly over the network, or use the default value if the network does not provide a value. When provided wirelessly by the network, the timer can be set up to 4 hours. The mobile station cannot try the GPRS service again until timer 3302 expires. Obviously, this can cause substantial data delays (eg, delays in receiving "push-delivered" email messages).
Therefore, as a result, there is a need for network selection methods and devices that overcome the shortcomings of prior art.
<p> The present application describes methods and devices for selecting a communication network to provide one or more communication services to a mobile station. Generally, a scanning operation is performed by the mobile station to identify one or more communication networks that support voice communication services in the geographic service area. The mobile station identifies which of the identified communication networks makes the data communication service available to the mobile station. The mobile station then selects and registers a communication network that makes voice and data communication services available through a network that does not make the service available. The method is preferably performed in connection with the creation of one or more preferred network lists. In this case, the mobile station gives a high priority to the communication network that makes voice and data communication services available to it on the communication network that does not do so in the preferred network list. However, in any case, the home network is maintained as a high priority network for communicating with the mobile station.</p><p> According to this application, rejection code processing is used to select a more time-efficient data-enabled network. One specific example of the method used to select a wireless communication network for communication is to make a request for a data connection to be transmitted over the first wireless network and via the first wireless network. Retrying the data connection request over the first wireless network one or more times when a rejection code with a non-serious error is received in response to the data connection request made, and the first In response to a request for a data connection over a wireless network, if a deny code with a serious error is received, the request for a data connection over the first wireless network will not be retried more than once. Includes trying to select a second wireless network for communication. Critical errors are considered to have permanent problems or shortcomings in the network or service subscription associated with the end user, and non-critical errors are non-critical, rather pass-through or temporary to the network or service subscription. Something that has a problem or a drawback.</p><p> Instructions on whether the wireless network currently makes voice and data connections available and acceptable to the mobile station can be made in the memory of the mobile station. The instructions to the wireless network may indicate "currently available data connections" if the request for a data connection is granted to the wireless network, or if a deny code with a serious error is received or one or more. A "currently unavailable data connection" may be indicated if the data connection request is retried without success over the wireless network. Similar results may be obtained using a list of currently unavailable data connections stored in memory. If a deny code with a serious error is received or one or more data connection requests are retried without success over the wireless network, such a list includes the wireless network, but of the data connection. If the request is granted by it, the list does not include wireless networks.</p>
Methods and devices for performing network selection by mobile communication devices are described in this application. In situations where more than one wireless network is available within a given service area, choose a wireless network that provides data services (or the "best" service) over those that do not, and give it a higher priority. The method of giving ranking is used. Such methods are applicable to mobile devices operating according to any suitable communication standard, but are particularly applicable to improved General Line Radio Service (GPRS) -enabled mobile stations. In this environment, the method can prioritize the selection of GPRS-enabled networks over networks that only support World Standard Mobile Communications (GSM).
In particular, deny code processing is used to select a time-efficient data-enabled network. One specific example of the method used to select a wireless communication network for communication is to make a request for a data connection to be transmitted over the first wireless network and via the first wireless network. Retrying the data connection request over the first wireless network one or more times when a rejection code with a non-serious error is received in response to the data connection request made, and the first In response to a request for a data connection over a wireless network, if a deny code with a serious error is received, the request for a data connection over the first wireless network will not be retried more than once. Includes trying to select a second wireless network for communication. Critical errors are considered to have permanent problems or shortcomings in the network or service subscription associated with the end user, and non-critical errors are non-critical, rather pass-through or temporary to the network or service subscription. Something that has a problem or a drawback. Typically, the time between the first attempt to connect data over the first wireless network (including all retries) and the first attempt to connect data over the second wireless network is approximately 25. It can be from 1 minute to 4 hours. Obviously, the techniques of the present invention reduce this time by providing a more time-efficient selection of data-enabled networks.
In addition, instructions are made in the mobile station's memory whether the wireless network currently makes voice and data connections available to the mobile station. The instructions to the wireless network may indicate "currently available data connections" if the request for a data connection is granted to the wireless network, or if a deny code with a serious error is received or one or more. A "currently unavailable data connection" may be indicated if the data connection request is retried without success over the wireless network. Similar results may be obtained using a list of currently unavailable data connections stored in memory. If a deny code with a serious error is received or one or more data connection requests are retried without success over the wireless network, such a list includes the wireless network, but of the data connection. If the request is granted by it, the list does not include wireless networks.
Here, with reference to Figure 1, an overview of how networks around the world connect is outlined. GSM and GPRS networks are shown as examples of wireless communication networks. The voice network known as GSM is an older component that has been available since around 1992, while GPRS, a data component combined with or overlaid with GSM, has only been available since around 1999. These two networks are now common around the world and have some of the fastest deployable voice and data networks. Such combined voice and data networks include modern code division multiple access (CDMA) networks such as the Enhanced Data-rates for Global Evolution (EDGE) and Universal Mobile Communication Systems (UMTS) currently under development. Also included are 3rd generation (3G) networks.
Figure 1 shows the five GSM-only networks 10, 14, 16, 22, 26 and eight GSM / GPRS composite networks 2, 4, 8, 12, 18, 20, 24, 28 found around the world. Has been done. At some point, a country may have one or more GSM and / or GSM / GPRS networks. Each network operator makes economical and practical decisions about when to purchase and implement GPRS functionality in an existing GSM network. Therefore, GSM phone users or GPRS-enabled mobile stations may enter a country and face networks that support either GSM alone or a combination of GSM / GPRS.
These networks implement interconnection with each other to support cross-country roaming and support cross-network billing and roaming notifications. Although shown as physically separated networks in Figure 1, the 13 networks (5 GSM and 8 GSM / GPRS) are a total of 4 networks, namely 3 GSM / GPRS networks 1, 2, and N, as well as interconnect to form one GSM network 1. A GSM network may connect to one or more other GSM networks, one or more GSM / GPRS networks, or both. GSM / GPRS networks may connect to other GSM / GPRS networks, GSM networks, or both GPRS / GSM networks and GSM networks as well. The Canadian networks, designated as GSM / GPRS1 2 and GSM / GPRS2 4, connect with GSM / GPRS1 12 and GSM1 14 found in the United States, respectively. GSM / GPRS2 4 also connects to GSM / GPRS1 8 found in the UK area via communication link 6. The US GSM 1 14 also connects to the GSM 1 10 found in Central Europe. The other networks 16-28 are likewise interconnected as illustrated. These interconnects form traffic movement and roaming support between networks.
Upon entering a country or communication network service area, a mobile station can communicate with one or more wireless GSM or GSM / GPRS networks to receive data and voice signals. For example, in the United Kingdom, four GSM or GSM / GPRS networks are currently deployed and are available for connecting mobile stations. Normally, mobile phones or mobile stations sold in the UK will only work on one network. However, mobile stations entering the UK from France may have two or three networks to choose from. The selection of a particular network is currently being carried out by the mobile station, and the selection is randomly based on the strongest signal received upon arrival in the country.
Next, looking at FIG. 2, a block diagram of a mobile phone mobile station, which is a type of mobile communication device, is shown. The mobile station 115 is preferably a two-way wireless communication device having at least voice and data communication functions. The mobile station 115 preferably has a function of communicating with other computer systems on the Internet. Depending on the exact functionality provided, mobile devices may be referred to as, for example, data messaging devices, two-way pagers, wireless email devices, mobile phones with data messaging capabilities, wireless internet appliances, or data communication devices. Can be done.
If mobile station 115 is capable of bidirectional communication, processing modules such as one or more related components, preferably internal or internal antenna elements 216 and 218, local oscillator (LO) 213, and digital signal processor (DSP) 220. Together, it will incorporate a communications subsystem 211 that includes a receiver 212 and a transmitter 214. As will be apparent to technicians in the field of communications, the particular design of the communications subsystem 211 will depend on the communications network in which the device is operating. For example, mobile station 115 includes a Mobitex mobile communication system, a DataTAC mobile communication system, or a communications subsystem 211 designed to operate within a GPRS network.
Network access requests also vary depending on the type of network 219. For example, in Mobitex and DataTAC networks, mobile station 115 is registered with the network using a unique identification number associated with each mobile station. However, in a GPRS network, network access is associated with the subscriber or user of mobile station 115. The GPRS mobile station therefore requires a subscriber identification module (SIM) card to operate in the GPRS network. Without a SIM card, GPRS mobile stations wouldn't work perfectly. Local or non-network communication functions may be available as well as legally required functions (if any) such as "911" emergency calls, but mobile station 115 is on network 219. No other function, including communication, would be feasible. SIM interface 244 is typically similar to a card slot that allows you to insert and remove SIM cards. The SIM card has about 64K of memory and can hold a lot of keying, identification, and information about 250 subscribers. The O-PPLMN, U-PPLMN, and Forbidden PLMN (FPLMN) are first received from the SIM card 250. The following references to PPLMN will generally apply to both O-PPLMN and U-PPLMN.
Upon completion of the requested network registration or activation procedure, mobile station 115 can send and receive communication signals over network 219. The signal received from the antenna 216 via the communication network 219 is input to the receiver 212, which provides normal receiver functions such as signal amplification, frequency down conversion, filtering, and an example of the system shown in FIG. In, analog-to-digital (A / D) conversion can be performed. The A / D conversion of the received signal allows for more complex communication functions such as demodulation and decoding performed on the DSP 220. Similarly, the signal to be transmitted includes, for example, modulation and coding by DSP220, is processed, digital to analog conversion, frequency up conversion, filtering, amplification, and over network 219 via antenna 218. Is input to transmitter 214 for transmission. The DSP 220 not only processes the communication signal, but also provides receiver and transmitter control. For example, the gain applied to the communication signal in the receiver 212 and the transmitter 214 can be adaptively controlled by the automatic gain control algorithm implemented in the DSP 220.
The mobile station 115 preferably includes a microprocessor 238 that controls the overall operation of the device. Communication functions, including at least data and voice communication, are performed by the communication subsystem 211. Microprocessor 238 includes display 222, flash memory 224, random access memory (RAM) 226, auxiliary input / output (I / O) subsystem 228, serial port 230, keyboard 232, speaker 234, microphone 236, narrow-range communication subsystem. It also interacts with additional device subsystems, such as 240, and other device subsystems generally designated as 242.
Some of the subsystems shown in Figure 2 perform communication-related functions, while other subsystems can provide "resident" or device-embedded functions. In particular, some subsystems such as keyboard 232 and display 222 are used for both communication-related functions such as text message input for transmission over communication networks and device-resident functions such as computers or task lists. be able to.
The operating system software used by microprocessor 238 is preferably stored in persistent storage, such as flash memory 224, which may be replaced by read-only memory (ROM) or a similar storage element (not shown). .. One of ordinary skill in the art will fully understand that an operating system, a particular device application, or a portion thereof, is temporarily loaded into volatile memory such as RAM226. The received communication signal can also be stored in the RAM 226.
In addition to its operating system features, the microprocessor 238 preferably is capable of running software applications on mobile stations. A predetermined set of applications that control basic operations, including at least data and voice communication applications, are typically installed on the mobile station 115 during manufacturing. Preferred software applications are personal information management (PIM) applications that have the ability to organize and manage data items related to mobile station users, such as, but not limited to, email, calendar events, voicemail, appointments, and task items. May be. Of course, one or more memory stores will be available at the mobile station to facilitate the storage of PIM data items. Such a PIM application would preferably have the ability to send and receive data items over wireless network 219. In a preferred embodiment, the PIM data item is seamlessly integrated, synchronized, and updated with the relevant data item of the mobile station user stored or associated with the host computer system via wireless network 219. To load additional applications into mobile station 115 and run on microprocessor 238 via network 219, auxiliary I / O subsystem 228, serial port 230, narrow communication subsystem 240, or other compatible subsystem 242. It can also be installed by the user in RAM226 or preferably in a non-volatile storage (not shown). Such flexibility in installing applications can enhance the functionality of the device and provide advanced device-embedded features, communication-related features, or both. For example, secure communications applications may enable such other financial transactions performed using e-commerce capabilities and mobile stations 115.
In data communication mode, the received signal, such as a text message or downloaded web page, is processed by the communication subsystem 211, preferably further processed to output the received signal to the display 222 or an alternative I / O device 228. Will be input to the microprocessor 238. The user of mobile station 115 uses, for example, a full alphanumeric keyboard coupled with display 222 and preferably auxiliary I / O device 228 or keyboard 232, which is a telephone numeric keypad, to provide data such as e-mail messages. You can also create items. The items so created are then transmitted over the communication network via the communication subsystem 211 and stored in part 251 of flash memory 224.
With respect to voice communication, the overall operation of mobile station 115 is similar, except that the received signal will preferably be output to speaker 234 and the signal to be transmitted will be generated by microphone 236. An alternative voice or audio I / O subsystem, such as a voice message recording subsystem, can also be implemented at mobile station 115. The voice or audio signal output is preferably provided primarily by the speaker 234, but to provide caller identification instructions, voice call duration or other voice calls relating to information such as those illustrated. Display 222 can also be used.
The serial port 230 in FIG. 2 is typically implemented in a personal digital assistant (PDA) type mobile station, which is desirable because it can be synchronized with the user's desktop computer (not shown), but is an optional device component. Such ports 230 allow users to install whatever they like with external devices and software applications, by providing information and software downloads to mobile station 115, as well as over wireless communication networks. It will extend the functionality of mobile station 115. Alternative download paths can provide secure device communication, for example with the shortest, and therefore reliable and reliable connection of encryption keys.
The narrow communication subsystem 240 is an additional optional component that provides communication between the mobile station 115 and a different system or device, and does not have to be a similar device. For example, subsystem 240 includes infrared devices and related circuits and components, or Bluetooth communication modules that provide communication with systems and devices that are also available.
FIG. 3 is a block diagram showing two GSM / GPRS networks and a mobile station roaming between them. Figure 3 depicts a mobile station 115 roaming between two GSM / GPRS networks 120 and 125. This type of roaming arrangement is similar to the roaming handled by GSM-only networks, with minor differences. In a GSM / GPRS composite network, mobile stations that support voice only, data only, or voice and data combinations are treated similarly when roaming between networks. Mobile stations entering an area or country can detect GSM and GSM / GPRS networks through specialized RF radio channel interactions. The explanatory diagram in Figure 3 provides a brief overview of how the process works. Roaming relationships between operators are established primarily due to billing issues. Special interoperator tariff (IoT) deployments can be established for GSM traffic only or between operators for GSM and GPRS traffic. It is these relationships that are reflected in the PPLMN and FPLMN lists in the mobile station SIM card.
GSM / GPRS network 1 is a home network 120 for users of mobile station 115. The home network for users is called the Home Public Land Mobile Network (HPLMN), and mobile stations registered in that network are maintained within the Home Location Registry (HLR) 150. The HLR150 is used to match subscribers on the home network and identify home subscribers on another network. Each wireless network supports a range of services in which its service access point tends to be a fixed connection rather than a wireless-based connection. Fixed connections generally allow large amounts of data throughput for a large number of service subscribers supported by a single access point name (ANP). In FIG. 3, one such service appears to be the primary communication service for a certain group of mobile stations 115 and is therefore referred to as the home service provider 100. Some mobile stations 115 may have a single home service provider 100 and some services 105, 110 to access.
The main components in the GSM / GPRS network 125 are base station 145, serving GPRS support node (SGSN) 130, gateway GPRS support node (GGSN) 140, border GGSN node 135, HLR (home location registry) 150 and VLR (visitor). Location registry) 155.
Normally, when the mobile station 115 is within the service area of the home network 120, the mobile station 115 transmits the signal back to the home service provider 100 via the base station 145 via the network 120. If mobile station 115 is looking for an area, especially if some networks seem to be available, HPLMN is usually considered first. When a user roams to another country or region where the home network 120 is no longer available, the mobile station 115 uses the strength of the received signal, usually radio frequency (RF), to make all available base stations 147. to scan. Those skilled in the art will appreciate that a wide range of settings and interpretations are possible for the selection of "strong enough" RF signal strength. As an example, the GSM standard specifies that signal strengths above -85 dBm are considered appropriate levels for "strong enough" signals. However, this exact signal level is not essential for the systems and methods described in this application, and other values may be valid depending on the particular network, mobile station or type of network or mobile station.
One of ordinary skill in the art will fully understand that such a scanning process has a pre-defined pattern. In GSM or GPRS networks, for example, scanning operations are defined in standards that specify GSM mobile stations. The standard has some flexibility and allows users to participate in the choice of networks to use other than HPLMN. Each network is defined as a PLMN, and the relationships between PLMNs are defined in the table in mobile station 115. When the mobile station 115 identifies the base station 147 and then the networks within its range, it refers to the PPLMN list to see which network matches the network in the PPLMN list.
In a conventional GPRS mobile station, there are two types of PPLMN lists within the mobile station 115, namely O-PPLMN and U-PPLMN as shown in FIG. User-defined lists are a relatively new concept and are for current use only. Similarly, mobile station 115 also has a Forbidden PLMN (FPLMN) list used to make certain network connections. It is possible that the networks found during the scanning operation do not fit into any of these lists. In this case, it is preferable to continue using the network after receiving confirmation from the mobile station user as to which network should be used, for example, by a dialog box.
GPRS networks are typically linked by GPRS Routing Exchange (GRX) 160 and borders GGSN 135 and 137. The signaling involved in this exchange is described in this application to the extent necessary to illustrate aspects of the invention. The GRX160 will be more apparent to those skilled in the art and is also described in the GSM Standards document (3GPP Specification 23.122), which deals with roaming support in GRPS.
If mobile station 115 stays out of the area for an extended period of time, it begins looking for RF signals from base station 145 or 147. Upon obtaining the signal, the radio protocol informs the mobile station 115 of which network is reaching and the function of that network. Each network has a signature, and GPRS-enabled base stations have a handshake protocol that is extended over the GSM protocol to identify their data capabilities. Within the GSM / GPRS network, there is a mobile country code (MCC) and mobile network code (MNC) that include network allocation values and access technology numbers. The access technology number indicates the frequency range of the network, that is, 900 MHz, 1800 MHz, 1900 MHz, and the like.
When the mobile station 115 selects a network, it "belongs" to the network and provides the identification code. For GSM / GPRS, this code identifies the International Mobile Subscriber Identity (IMSI) or Temporary Mobile Phone Subscriber Identification Number (TMSI), which identifies the account or subscription of the communications network, and the mobile station user or subscriber. May include both mobile station ISDN / PSTN number MSISDN. If the mobile station 115 attempts to belong to a network other than its home network 120, such as network 125, the other network 125 will use the GRX network 160 to match subscriptions to the home network 120. This causes the home network 120 to refer to the HLR150 and determine if the subscription is valid. After matching, the mobile station 115 is placed in the VLR table 157 of the visited network 125. For those of skill in the art, this procedure is similar to that for GSM-only networks, except that the link between the home and visited networks will be through the Gateway Mobile Communication Exchange (MSC) component.
After belonging to network 125, mobile station 115 will attempt to expose the packet data context (PDP) to home service provider 100 via local SGSN 132 in the GSM / GPRS network within country 2 125. The PDP context targets APNs and Home Services 100. The PDP context also assigns an IP address to mobile station 115 so that IP packets can be transmitted in either direction. The SGSN132 detects the mobile station 115 as the visited mobile station 115, sends a request forward through the border GGSN137 for an accurate GRX connection in the GRX network 160, and delivers it to the corresponding border GGSN135 in the home network 120. .. As mentioned above, this determination is made by the identification information provided by the mobile station 115 during the affiliation process.
Each interface in the GSM / GPRS network is labeled to identify which protocol is being used. There is a Gb interface between all base stations 145 and SGSN130. There is a Gn interface between SGSN130 and GGSN140, which is also used between SGSN130 and border GGSN145. A Gi interface is used between the GGSN140 and all service providers, and a Gp interface is used between the border gateway 135 and the GRX network 160. From the GRX network 160, all other foreign network operator (FNO) systems 165 that would normally be linked to the GRX network are reachable.
The GSM network standard is mobile station 115 country 2 It defines the specific steps that must be taken to select base station 147 in 125 GSM / GPRS networks. First, the mobile station 115 must achieve the lowest level of signal strength connected to its base station. Once the signal strength is established and the network associated with each base station that meets the signal strength criteria is identified, the mobile station 115 determines which is the "best" network selection for its PPLMN on the SIM. And use the FPLMN list. Mobile station 115 examines the PPLMN list to see if any of the newly located networks match the network on the PPLMN list. Similarly, mobile station 115 also looks at the FPLMN list to determine which networks are forbidden. If any of the newly located networks appear in the FPLMN list, they will be excluded from any further connection behavior. If no match is found in the PPLMN list, mobile station 115 may attempt to select one of the most recently located networks based on signal strength.
FIG. 4 is a block diagram illustrating a mobile station in an area with several heterogeneous networks. In FIG. 4, mobile station 115 is shown in an area with four networks 210, 215, 220, 225 with base stations 212, 214, 216, 218, respectively. For illustration purposes, each base station 212, 214, 216, 218 has similar RF strength in terms of mobile station 115, which gives a "strong enough" signal to local network 1 210, local network 2 215. , Local network 3 220, and local network 4 225. The two networks 210 and 215 are GPRS-enabled, and the two networks 220 and 225 are GSM-only networks that are not GPRS-enabled.
According to this application, either GPRS network 210 or 215 should be selected in order to maximize the functionality of mobile station 115 as a multi-function mobile station (eg, both data and voice communication services are possible). In conventional GSM operation, the mobile station 115 compares all networks whose received signal exceeds any required signal strength level and matches them to the top-level network found within PPLMN. There will be. Since PPLMN is in priority order, GSM mobile stations must of course follow the order in this list. In Figure 4, for example, if local network 4 225 is the highest on the PPLMN list, mobile station 115 must camp on to this network. However, this process does not take into account the fact that mobile station 115 may also be data capable. Therefore, the selection of local network 4 225, which does not support data communication, is not always optimal for mobile station 115.
In order to improve the function of mobile station 115, it is preferable to take other factors into consideration in the search for a better network. Since the mobile station 115 cannot communicate effectively when the signal strength falls below a certain level, practically only the network base station having the "sufficiently strong" signal is located as described above. .. According to one aspect of the invention, data-enabled networks such as GPRS networks are then identified. The mobile station 115 determines which of the subsequently identified data-enabled networks is listed first in the preferred network list, which is the PPLMN list for GSM / GPRS mobile stations. The mobile station 115 then checks to ensure that interconnections such as the GRX network to the GPRS network are available to the home network from this highest priority data-enabled network on the preferred list. If there is no interconnect available from the highest priority data-enabled network to the home network, mobile station 115 continues to try the identified data-enabled network on the preferred list until it finds a link back to the home network.
If the mobile station 115 cannot find a link back to the home network, it can revert to choosing a non-data capable network, such as a traditional GSM network, as described above. Alternatively, the network selection method may stop after scanning all data-enabled networks to link to the home network. This may be especially desirable if the data-enabled network has more functionality than the non-data-enabled network. In some situations, the mobile station may be used more effectively on the new network, for example because it has free access to the Internet, even if the user has not reached the home network.
With reference to FIG. 4 again, the mobile station 115 can access the preferred network list, usually in the form of a PPLMN stored on the SIM card. Data-enabled networks include GSM / GPRS local networks 1 and 2, 210 and 215, while GSM local networks 3 and 4, 220 and 225 are typical examples of non-data-enabled networks.
If mobile station 115 implements the network selection method briefly described above and assumes that the PPLMN list follows the network order shown in Figure 4, the first network to be tried is local network 1210. However, local network 1 210 does not have a GRX connection back to home PLMN 205, so local network 2 2 15 will be tried next. This network will have a Gp link 240 back to home PLMN 205 and a home service provider 200 and will be selected by mobile station 115. If the last available data-enabled network, Local Network 2 215, did not have a connection back to the home PLMN 205, the first GSM network would be tried. The first GSM network to be tried is the local network 3 220, which will communicate with the HLR using link 230 to match the user's account information at home PLMN 205. If that fails, local network 4 225 will be tried over link 235.
In another embodiment of FIG. 4, the new networks 210, 215, 220, 225 are not included in the O-PPLMN list on mobile station 115. This situation is more difficult because U-PPLMN can take effect if it resides in memory such as flash memory 224 or RAM226 (Figure 2).
One common way to build a U-PPLMN list is by pre-user or "manual" network selection. As in the example above in FIG. 4, it is assumed that mobile station 115 has entered a country or region that receives signals of similar strength from the four networks 210, 215, 220 and 225. However, it is also envisioned that these networks are not found in the O-PPLMN list or FPLMN list and mobile station 115 can consider them suitable for use. In this situation, once these networks are identified, the user is prompted to select the network they want to try. In the GSM standard document, this is referred to as manual network selection. After the user selects a network, the connection back to the home network 205 is tried and, if successful, added to the U-PPLMN.
The user interface (UI) for these manual network selections can be standard dialog boxes, picklists, scroll menus, or any other UI selection model available. It will be apparent to those skilled in the art that the UI may include network functionality by showing the user the ability to identify strings such as "GPRS" or "GSM" beside each network selection. .. In another embodiment, the user may be presented with a dialog box entitled "GPRS Network Selection", followed by "GSM Network Selection" if the GPRS network fails to reach the home PLMN.
Network selection in this situation can instead be automatic without requiring user intervention. In such a method, the mobile station 115 preferably identifies a network that supports GSM and a network that supports GSM / GPRS and separates the two types of networks. GSM-only networks are included in the Discouraged PLMN list (DPLMN) and are only tried after all GSM / GPRS networks have been tried and failed. The only failure mentioned so far was the inability to reach home PLMN205. Other failures may include (1) PLMN does not tolerate, (2) roaming is not tolerated within this local area, (3) GPRS is not tolerated, or (4) home network denial. .. If it seems that the network link is not working for mobile station 115 due to these errors etc., the network may be located at FPLMN.
The manually or automatically selected network is preferably added to the U-PPLMN list, which can be stored in a writable data storage location such as flash memory 224 or RAM226 (Figure 2) in mobile station 115. The U-PPLMN list can then be viewed during the next network selection procedure. Mobile station 115 usually first checks the O-PPLMN list for new networks detected during the network selection process before browsing the U-PPLMN list. For example, depending on the regulations controlled by the home network operator, home service provider, or mobile station owner, it may be possible to configure the mobile station to check the U-PPLMN list before the O-PPLMN. ..
According to the current GSM standards document, mobile stations have only limited ability to rescan higher priority networks on the U-PPLMN list or O-PPLMN list. However, if voice-only GSM or other limited services have been established for the mobile station, it may be desirable for the mobile station to regularly check for new networks such as GSM / GPRS networks. This can be done even if the network has a low priority in the O-PPLMN and U-PPLMN lists. This situation may also occur for other types of mobile stations and networks where mobile devices can communicate on disparate networks that support different mobile station functions or services.
In Figure 4, mobile station 115 enters a new region or country and finds a service area (ie, a "strong enough" signal) with only one GSM-only base station located on local network 4 225. However, since mobile station 115 moves within the same country, local network 1 May enter the service area of another GSM / GPRS base station at 210. In the GSM standard, mobile station 115 may only camp on network 210 if it has a high priority in the PPLMN list. However, in connection with this application, Mobile Station 115 will attempt to rescan other data-enabled networks that were previously unseen or available at the time of expiration or other compatible events. This includes any low priority network in the O-PPLMN and U-PPLMN lists. This time interval may be specified or configured, for example, by a network operator, SIM maker, network standard document, mobile station maker, user of mobile station 115, and the like. The purpose of such rescanning is to improve the network functionality of mobile station 115. In this example, mobile station 115 has voice support over local network 4 225, but by changing the network connection, mobile station 115 may get data and voice support over local network 1 210. ..
The rescanning process may be triggered or initiated by any matching event. For example, in terms of time intervals, rescanning may be performed whenever the rescan timer expires. Such timers are properly reset so that rescanning is performed periodically. If the timers are set to the same value without or until the time interval is reset, rescanning will occur at regular intervals. The timing of the rescan may be repeated at different intervals by resetting the timer to a different value after several unsuccessful rescan operations where no new data-enabled network is found. It is also possible to limit rescanning several times a day to avoid rescanning during generally high network traffic. Rescanning may be performed similarly or instead when the mobile station detects a change within the region, or when the mobile station acquires a new voice-only network in the new region. When the mobile station detects an available network with both voice and data communication capabilities, the mobile station then attempts to camp on to this network, preferably. The strength of the received signal and the PPLMN list are used substantially as described above during the rescan process. Rescanning is not used if the mobile station is already operating in a network that already has data communication services available, as the primary purpose of the rescanning process is to find data communication services available to the mobile station. It is preferable that it is possible.
If the current network is on the O-PPLMN or U-PLMN list and the newly discovered network is not on the PPLMN list, the mobile station can stay on the current network without switching to the new network. Most GSM / GPRS networks are likely to be included somewhere on the O-PPLMN list or possibly the U-PPLMN list. Network changes during the rescan process may also depend on the relative signal strength to avoid switching from a strong GSM network to a significantly weaker GSM / GPRS network. Differences in allowed signal strength are stored, for example, in the memory of the mobile station.
Choosing a time-efficient data-enabled network for data-enabled mobile devices. Therefore, better non-conventional network selection techniques for data-enabled mobile stations include prioritizing the selection of data-enabled communication networks (eg, GPRS) over voice-only networks (eg, GSM). In such a procedure, the mobile station may have to determine whether the data service is actually made available by its communication network. Mobile stations typically make requests for data services that can be allowed or denied by the network. When a data service is rejected, the mobile station receives different "rejection reason codes" from different networks associated with different causes of the service refusal. Depending on the denial code, the mobile station must wait until the data service is reclaimed, the timer expires, the network changes, or the user powers the mobile device off and on again. Sometimes. If the end user is not looking at the mobile station's display (for example, the mobile station is being carried in a holster), the user will not be aware of the unavailability of the data service and important push data (eg, for example). Push-type delivered e-mail message) cannot be received in a timely manner. In a related efficiency issue, if a GPRS belonging or routing area update (RAU) attempt is unsuccessful on that network (for example, no network response or reception of a deny code), the mobile station will reissue up to 5 times in a row. Try. If the GPRS affiliation or RAU trial counter is 5 or higher, the mobile station must put itself in the "GPRS deregistration" state and activate the timer designated as "Timer 3302". Timer 3302 is set to a value taken from the GSM timer 3212, which is a periodic position update timer. For example, 1997 3GPP standard release 4. See 08. Starting with 1999 3GPP standard release 24.08, the default value for the T3302 is 12 minutes if the network does not provide a value. Mobile stations typically receive the value for timer 3212 wirelessly over the network, or use the default value if the network does not provide a value. When provided wirelessly by the network, the timer can be set up to 4 hours. The mobile station cannot try the GPRS service again until timer 3302 expires. Obviously, this can cause substantial data delays (eg, delays in receiving "push-delivered" email messages).
FIGS. 5, 6 and 7 are flowcharts illustrating a particular method of automatic network selection performed by the mobile station. This method includes the selection of the more time-efficient data-enabled networks described in this application to overcome the shortcomings of the prior art. The computer program product of the present application includes a storage medium and computer instructions stored in the storage medium, wherein the computer instructions can be executed by one or more processors of the mobile station to carry out the above method. .. The mobile station of the present application includes one or more processors and a radio transceiver coupled to the one or more processors, wherein the one or more processors operate to carry out the above method.
Starting with connector M in Figure 5, where the mobile station is powered or recovers from out-of-area conditions, scanning operations identify available networks within the mobile station's service area. From the scan list, the mobile station identifies whether it has a Registered PLMN (RPLMN) (step 502). The RPLMN is only recognized as an RPLMN if it has a data connection (eg GPRS connection), otherwise the RPLMN is not recognized as an RPLMN. If there is an RPLMN in step 502, the mobile station identifies whether there is a home PLMN and whether the HPLMN is the same as the RPLMN (step 504). If yes in step 504, the mobile station selects HPLMN if RPLMN is available and HPLMN is available and acceptable (step 506). If "No" in step 504, the mobile station selects RPLMN (step 508). After step 508 and after step 506 the mobile station selects HPLMN, the mobile station attempts to register with the selected PLMN (step 510). It should be noted here that the connector P ́ is also the point leading to step 510. "Available" means that the network is available within the service area of the mobile station, and "acceptable" means that the network is at least obtained by GSM services (eg, GSM affiliation procedures). ) Means to provide.
If registration is unsuccessful in step 510 (ie, GSM affiliation denial), the mobile station receives a denial code from the network. The deny code is verified and if the deny code has a value of 2, 3, or 6 (step 521), the mobile station proceeds to step 523. In step 523, the mobile station verifies whether the deny code has a particular value of 2. If the rejection code = 2 in step 523, the mobile station records that the network is preferred as GPRS (step 527) and continues the flow through connector O. If the deny code does not have a value of 2 when identified in step 523, the SIM is designated as invalid until the power is turned off or the SIM card is removed (step 525). If the deny code has no 2, 3, or 6 in step 521, the flow proceeds to step 522. If registration is successful in step 510 (ie, GSM affiliation permission), the selected PLMN is shown in the mobile station image display (step 512). From step 512, the mobile station identifies in step 540 whether PLMN is GSM only (ie, no data service). If yes in step 540, the mobile station remains registered and connected via this PLMN (state 542). In state 542, the mobile station may be in an out-of-area situation where the operation passes through connector R1. On the other hand, in state 542, the mobile station can receive a user manual reselection of the network and then pass through connector S (Figure 6). Further in step 542, the operation by connector P2 can reach step 528, where the mobile station identifies whether the PLMN is not HPLMN and the HPLMN timer is longer than 6 minutes. If yes in step 528, the mobile station activates the built-in timer t1 for PLMN search (step 530). If "No" in step 528, the mobile station waits for the HPLMN timer to time out (step 53). 2). During the timeout in steps 530 and 532, the mobile station identifies whether an HPLMN or data-enabled (eg GPRS-enabled) PLMN was found (step 534). If yes in step 534, the operation passes through connector Z. If "No" in step 534, the operation remains in state 542.
If "No", the operation proceeds from step 540 to step 514. At step 514, the mobile station attempts a GPRS affiliation request with the network of choice (step 514). If successful in step 514, the mobile station attempts a PDP context request with the selected network (step 516). If successful in step 516, the mobile station remains registered and connected by this PLMN (state 518). It should be noted here that the connector W also reaches the state 518. It should also be noted that connector O reaches step 514 and connector X1 reaches step 516. In step 514, the mobile station may receive a GPRS affiliation request from the network and then pass through connector T (Figure 6). On the other hand, in step 514, the T3310 timer may time out or there may be a low-rise fault in which operation passes through connector V (Figure 6). At step 516, the mobile station may receive a deny code from the network in the PDP context and then pass through connector U (Figure 7). On the other hand, in step 516, the T3380 timer may time out and the operation may pass through connector U1 (Fig. 7).
In state 518, the mobile station can receive a user manual reselection of the network and then pass through connector S (Figure 6). Also, in state 518, the mobile station can pass through the connector T after rejecting the routing area update (RAU) (Fig. 6). In state 518, the mobile station may also time out the RAU T3330 or have a low-rise fault, after which operation may pass through connector V (Figure 6). Furthermore, in state 518, if the current PLMN is not an HPLMN, the periodic HPLMN timer termination causes the mobile station to identify whether an HPLMN or data-enabled PPLMN is currently available (step 520). If HPLMN or data-enabled PPLMN is available in step 520, operation passes through connector P ́. If HPLMN or data-enabled PPLMN is not available in step 520, the mobile station remains registered and connected by PLMN in state 518. Further, in step 518, PDP inactivation from the network passes connector U2 into operation.
In state 518, the mobile station may go through an out-of-area situation by PLMN and then proceed to step 522. Step 522 is also performed if RPLMN is not identified in step 502, or GSM denial <> 2 is identified from step 521, or there is a radio service area loss from state 542 (via connector R1). .. At step 522, the mobile station identifies whether there are any available and acceptable PLMNs. If there are any available and acceptable PLMNs, the operation goes through connector R (Figure 6). If there is no available and acceptable PLMN in step 522, the mobile station will display "No acceptable network-emergency service only" (where other networks are available but acceptable). Not possible) (step 524). If no network is available in step 522, the mobile station will display "out of service area-out of service area" in step 524. It should be noted here that the connector Q also reaches step 524. After step 524, the mobile station will wait for PLMN to become available (state 526). When RPLMN becomes available and acceptable in step 526, operation passes through connector P ́. If RPLMN becomes unavailable and unacceptable in step 526, the operation passes through connector R.
Here, referring to FIG. 6, the automatic network setting is continued, and in particular, the processing of the rejection code from the network in response to the GPRS affiliation request from the mobile station is explained. Connector T is from step 514 in FIG. 5, where the network receives a GPRS affiliation request and sends a rejection code to the mobile station. If the deny code has a value of 3, 6, or 8 when identified in step 601, the SIM is designated as invalid until the power is turned off or the SIM card is removed (step 603). If it does not have any of the values 3, 6, or 8 when identified in step 601 the flow proceeds to step 602. If the denial code has a value of 7, 11, 12, 13, or 14 in step 602, the denial is considered critical and the action is generally to step 614 where the mobile station will immediately begin reselecting a different network. move on. If the denial code has no other value (ie, other than 7, 11, 12, 13, or 14) when identified in step 602, the denial is considered non-critical and the operation is generally performed by the mobile station on its network. Proceed to step 604, which will be retried at. It should be noted here that serious errors are permanent problems or shortcomings that exist in the network or end user's service subscription, and non-serious errors are not serious, but rather pass-through or temporary to the network or service subscription. It is a point that is considered to have some problems or drawbacks. A deny code with a value of 3 corresponds to an illegal mobile station, a value of 6 corresponds to an illegal mobile device, and a value of 8 corresponds to an unauthorized GPRS and non-GPRS service. A deny code with a value of 7 corresponds to an unauthorized GPRS service, a value of 11 corresponds to an unauthorized PLMN, a value of 12 corresponds to an unauthorized location area, and a value of 13 corresponds to the current location area. Corresponds to unauthorized roaming, with a value of 14 corresponding to GPRS services not permitted by the current PLMN.
In step 604, the mobile station checks the affiliation counter (or RAU counter) to see if its value is 5 or greater. It should be noted here that the connector V also reaches step 604. If the affiliation counter (RAU counter) is not 5 or more, the operation passes through connector O (if affiliation rejected / no network response) or connector W (when RAU rejected / no network response) (Figure 5). If the affiliation counter (RAU counter) is 5 or more, the mobile station begins to check whether PLMN is HPLMN (step 620). If PLMN is HPLMN in step 620, the mobile station will display "temporary data service failure" (step 622) and check if timer T3302 is set to a value greater than the value of the given built-in timer. (Step 606). The value of the built-in timer is generally set between 5 and 30 minutes, preferably longer than 12 minutes (for example, between 13 and 30 minutes). Alternatively, the value of the built-in timer is set between 5 and 10 minutes, preferably about 6 minutes. If timer T3302 is greater than the value of the built-in timer in step 606, the mobile station activates the timer based on the value of the built-in timer (step 608). If timer T3302 is greater than the value of the built-in timer in step 606, the mobile station activates the timer based on the value of timer T3302 (step 612). When either the timer in step 608 or step 612 times out, the operation passes through connector O (no affiliation / no network response) or connector W (no RAU / no network response).
At step 614, the mobile station detects whether the current PLMN is an HPLMN. If the current PLMN is HPLMN, the operation proceeds to step 616. At step 616, the mobile station displays "Data services are not available on this network-contact your service provider" (step 616). If the current PLMN is not HPLMN in step 614, the mobile station is activated to scan the new network (step 618). Step 618 is also performed following the "no" decision in step 620 above. After step 618, the mobile station identifies whether there is any available and acceptable data-enabled (ie, GPRS-enabled) PLMN (step 624). If there is any available and acceptable data-enabled PLMN, the mobile station constructs and marks the PLMN list accordingly (step 638). For example, a data-enabled PLMN may be flagged as regular in the PLMN list. It should be noted here that the connector Z also reaches step 638. Then move the previously selected PLMN to the previous position in the PLMN list (step 640) (with the execution of the HPLMN located "second" in the list). It should be noted here that the connector S also reaches step 640. The first PLMN in the PLMN list is then selected by the mobile station (step 642). It should be noted here that the connector R also reaches step 642. The mobile station then identifies whether the SIM is invalid for the GSM service (step 643). If SIM is disabled for GSM service in step 643, the operation goes through connector O (Figure 5). If the SIM is not disabled for the GSM service in step 643, the operation goes through the connector P ́ (Figure 5).
If there is no data-enabled PLMN available in step 624, the mobile station will display "Data services are not available on this network" (step 654) and proceed to step 628. At step 628, the mobile station checks to see if the HPLMN timer is longer than 6 minutes. If the HPLMN timer is longer than 6 minutes, the mobile station activates the built-in timer t1 for PLMN search (step 632). If the HPLMN timer is not longer than 6 minutes, the mobile station waits for the HPLMN timer to time out (step 630). When a timeout occurs from either step 630 or 632, the mobile station identifies whether HPLMN or GPRS PLMN was found (step 634). This PLMN must not have been previously rejected by rejection code 7, 12, 13, or 14. If yes in step 634, the operation passes through connector Z. If "No" in step 634, the mobile station activates the HPLMN timer or built-in timer t1 (step 636).
Here, referring to FIG. 7, the automatic network setting is continued, and in particular, the processing of the rejection code from the network in response to the PDP context request from the mobile station is explained. Connector U2 is from step 518, where the network sends a PDP deactivation to the mobile station. Connector U is from step 516 of Figure 5, where the network receives a PDP context request and sends a deny code to the mobile station. From connectors U and U2, the mobile station verifies that the current APN is not an "X.net" type APN (ie, a given address) or does not support email services (step 700). If yes in step 700, the mobile station remains on the current network (step 701). If "No" in step 700, the flow proceeds to step 702 to verify the rejection code received by the mobile station from the network. The deny code indicates that the network has rejected the data connection request for some reason. If the deny code is deemed non-critical (step 702), the operation proceeds to step 704, where the mobile station will generally retry on that network. If the deny code is considered critical in step 702, the operation proceeds to step 706, where the mobile station will generally reselect a different network.
In this embodiment, the rejection codes that are considered non-critical are 26, 31, 34, 102, 38, 36, 39, and 35. Deny code 26 corresponds to an inadequate resource, deny code 31 corresponds to an unspecified boot deny, deny code 34 corresponds to a temporarily failed service option, and deny code 102 corresponds to a response from the network. No timeout, deny code 38 corresponds to network failure, deny code 36 usually corresponds to PDP context inactivation, deny code 39 corresponds to reactivation request, deny code 35 has already been used Corresponds to the NSAPI. On the other hand, the deny codes that are considered serious are 27, 29, 30, 32, 33, and 25. Deny code 27 corresponds to a missing or unknown APN, deny code 29 corresponds to a user authentication failure, deny code 30 corresponds to a boot denied by the GGSN, and deny code 32 corresponds to an unsupported service option. Corresponding, deny code 33 corresponds to an unsubscribed service option, and deny code 25 corresponds to an LLC or SNDCP failure.
In step 704, the mobile station checks to see if the PDP trial counter is 5 or greater. It should be noted here that the connector U1 also reaches step 704. If the PDP trial counter is not greater than or equal to 5, the operation passes through connector X1. If the PDP trial counter is 5 or greater, the mobile station verifies whether the deny code has the value "102" (step 705). If the deny code has the value "102", the mobile station sends a removal request to the network (step 707) and passes through connector O. If the deny code does not have the value "102" in step 705, the mobile station checks to see if the current PLMN is HPLMN (step 706). Step 706 is also performed if the mobile station identifies that the deny code from step 702 is indeed a serious error. If "yes" in step 706, the operation proceeds to step 708. In step 708, the mobile station displays "Data connection temporarily failed" if the error is not critical, or "Data connection refused on the network" if the error is severe- Please contact your service provider (step 708). If "No" in step 706, the mobile station scans to identify available networks (step 710). The mobile station then identifies whether there is any data-enabled (eg GPRS-enabled) PLMN that has no acceptable and unsuccessful PDP context (step 712). If there is a data-enabled PLMN available, the operation goes through connector Z. If there is no data-enabled PLMN available, the mobile station will display "Data connection refused" if the error is not severe, and "Data connection refused-to the service provider" if the error is severe. Please contact us "(step 714).
The mobile station then checks to see if the HPLMN timer is longer than 6 minutes (step 720). If the HPLMN timer is longer than 6 minutes, the mobile station activates the built-in timer t1 for PLMN search (step 718). From step 720, if the HPLMN timer is not longer than 6 minutes, the mobile station waits for the HPLMN timer to time out (step 722). It should be noted here that the connector W1 also reaches step 722. If a timeout occurs, the mobile station identifies whether an HPLMN or data-enabled (eg GPRS-enabled) PLMN was found (step 724). If an HPLMN or data-enabled PLMN is found, the operation goes through connector Z. If neither the HPLMN nor the data-enabled PLMN is found, the mobile station activates the HPLMN timer or the built-in timer t1 (step 726).
Preferably, an indication as to whether the wireless network currently makes voice and data connections available to the mobile station is made in the memory of the mobile station. The instructions to the wireless network may indicate "currently available data connections" if the request for a data connection is granted to the wireless network, or if a deny code with a serious error is received or one or more. A "currently unavailable data connection" may be indicated if the data connection request is retried without success over the wireless network. Similar results may be obtained using a list of currently unavailable data connections stored in memory. If a deny code with a serious error is received or one or more data connection requests are retried without success over the wireless network, such a list includes the wireless network, but of the data connection. If the request is granted by it, the list does not include wireless networks.
Figures 8, 9, and 10 form a flowchart illustrating a particular method of manual network selection provided by the mobile station to the end user. This method also includes the selection of the more time-efficient data-enabled networks described in this application to overcome the shortcomings of the prior art. The computer program product of the present application includes a storage medium and computer instructions stored in the storage medium, wherein the computer instructions can be executed by one or more processors of the mobile station to carry out the above method. .. The mobile station of the present application includes one or more processors and a radio transceiver coupled to the one or more processors, wherein the one or more processors operate to carry out the above method.
The mobile station is powered or recovers from out-of-area conditions Starting with connector A in Figure 8, scanning operations identify available networks within the mobile station's service area. From the scan list, the mobile station identifies whether it has a Registered PLMN (RPLMN) (step 802). The RPLMN is only recognized as an RPLMN if it has a data connection (eg GPRS connection), otherwise the RPLMN is not recognized as an RPLMN. If there is an RPLMN in step 802, the mobile station identifies whether there is a home PLMN and whether the HPLMN is the same as the RPLMN (step 804). If yes in step 804, the mobile station will display "Please select HPLMN" if RPLMN is available and HPLMN is available and acceptable (step 806). If "No" in step 804, the mobile station selects RPLMN (step 808) and attempts to register with it ("GSM affiliation") (step 810). If the end user selects "Yes" in step 806 to select the HPLMN, the flow passes through connector F and proceeds to step 810. If the end user selects "No" in step 806, the flow proceeds to step 808.
If GSM affiliation is allowed in step 810, the selected PLMN is shown in the mobile station image display (step 812). Step 812 is also performed via connector G. The mobile station then identifies whether the PLMN is GSM only (ie, no data service) (step 850). If "No" in step 850, the operation leads to step 814, which will be described later. If yes in step 850, the mobile station operates as registered on this PLMN (state 852). It should be noted here that the connector G2 reaches state 852. In state 852, the mobile station can receive a user manual reselection of the network and then pass through connector C. Also, in state 852, the current PLMN is GSM only and any GPRS. If the mobile station identifies that PLMN is available, the operation proceeds to step 854, where the mobile station displays "Select GPRS network?". If the end user selects Yes for this option, the action goes through connector G1, otherwise the action goes through connector G2. In state 852, the mobile station may also go through the out-of-area situation by PLMN and then through connector C1.
If GSM affiliation is denied in step 810, the mobile station receives a rejection code from the network. The deny code is validated and if the deny code has a value of 2, 3 or 6 (step 855), the flow continues to step 857. If the deny code has a particular value of 2 when identified in step 857, the flow continues through connector B2. If the deny code does not have the specific value "2" in step 857, the SIM is designated as invalid until the power is turned off or the SIM card is removed (step 859). If the deny code does not have the values 2, 3, or 6 when identified in step 855, the mobile station displays "emergency service only" (step 856) and continues to step 821. It should be noted here that the connector H1 also reaches step 856. The mobile station then identifies whether any PLMN is available (step 821). If no PLMN is available in step 821, the mobile station waits for any PLMN to appear (step 858) and passes through connector H when it does. If one or more PLMNs are available in step 821, the mobile station proceeds to step 828 described below.
In step 850, if the mobile station identifies that PLMN is not GSM only (ie, can provide data services), the mobile station attempts a GPRS affiliation request with its network of choice (step 814). It should be noted here that the connector B2 also reaches step 814. If successful in step 814, the mobile station attempts a PDP context request with the selected network (step 816). If successful in step 816, the mobile station remains registered and connected via this PLMN (state 818). It should be noted here that the connector B3 also reaches step 818.
At step 814, the mobile station may receive a GPRS affiliation request from the network and then pass through connector B (Figure 9). On the other hand, in step 814, the T3310 timer may time out and the operation may pass through connector B ́ (Fig. 9). At step 816, the mobile station may receive a deny code from the network in the PDP context and then pass through connector X (Figure 10). Also, in step 816, the T3380 may time out and operation may pass through connector X2. It should be noted here that the connector X3 also reaches step 816. In state 818, the mobile station may receive a user manual reselection of the network and then pass through connector C. Also, in state 818, the mobile station may go through a routing area update (RAU) and then pass through connector B (Figure 9). In state 818, the mobile station also goes through the RAU T3330 timeout and then connector B. It may pass through ́ (Fig. 9). In state 818, the mobile station may also receive PDP inactivity from the network and then pass through connector C2. Further in state 818, the mobile station may go through an out-of-area situation by PLMN and then proceed to step 820. Step 820 is also performed if the RPLMN is not identified in step 802.
At step 820, the mobile station identifies whether there is any PLMN available. If no PLMN is available in step 820, the mobile station will display "out of service" (step 826). The mobile station will then wait for any PLMN to appear (step 862). The operation passes through connector F when the previously selected PLMN becomes available in step 862, and otherwise the operation passes through connector H when any other PLMN becomes available. If there is any PLMN available in step 820, the mobile station will display "Please select a network" to let the user choose whether to manually select the network (step 828). It should be noted here that the connector H also reaches step 828. If the user selects "Yes" in step 828, the mobile station displays all available PLMNs in sequence and gives the user the option to select one of those PLMNs (step 830). It should be noted here that the connector C also reaches step 830. When the user selects a network in step 830, the mobile station attempts to register with the selected PLMN. The mobile station then identifies whether the selected PLMN is a Forbidden PLMN (FPLMN), has a GPRS affiliation denial, or has a PDP context denial (step 834). If "yes" in step 834, the operation proceeds to step 838. If PLMN is FPLMN in step 838, the mobile station will display "Emergency services only. Select'Save'or'Cancel'" (step 838). If the PLMN has a GPRS affiliation denial or a PDP context denial, the mobile station will display "Voice service only. Select'Save'or'Cancel'" (step 838). If the end user selects "Cancel" after step 838, the operation returns to step 828. At step 834 If no, the mobile station attempts to register with PLMN (GSM affiliation) (step 860). It should be noted here that the connector G1 also reaches step 860. If GSM affiliation is allowed in step 860, the operation passes through connector G. If GSM affiliation is denied in step 860, the operation passes through connector B4. If the end user selects "No" in step 828, the mobile station displays "emergency services only" and waits for the previously selected PLMN to become available again (step 832). The mobile station either tries the previously selected PLMN or waits for the previously selected PLMN to become available, where operation passes through connector F.
Here, with reference to FIG. 9, the manual network is continued, and in particular, the processing of the rejection code from the network in response to the GPRS affiliation request from the mobile station is explained. Connector B is from step 814 of FIG. 8, where the network receives the GPRS affiliation request and sends a rejection code to the mobile station. The denial code indicates that the network has refused the data connection for some reason. If the deny code has a value of 3, 6, or 8 when identified in step 901, the SIM is designated as invalid until the power is turned off or the SIM card is removed (step 903). If the deny code has no values 3, 6, or 8 when identified in step 901, the flow proceeds to step 902. If the denial code has a value of 7, 11, 12, 13, or 14 as identified in step 902, the denial is considered critical and the action is that the mobile station generally immediately begins reselecting a different network. Proceed to Deaf Step 914. If the denial code has no other value (ie, other than 7, 11, 12, 13, or 14) when identified in step 902, the denial is considered non-critical and the operation is generally performed by the mobile station on its network. Proceed to step 904, which will be retried at. It should be noted here that serious errors are permanent problems or shortcomings that exist in the network or end user's service subscription, and non-serious errors are not serious, but rather pass-through or temporary to the network or service subscription. It is a point that is considered to have some problems or drawbacks. A deny code with a value of 3 corresponds to an illegal mobile station, a value of 6 corresponds to an illegal mobile device, and a value of 8 corresponds to an unauthorized GPRS and non-GPRS service. A deny code with a value of 7 corresponds to an unauthorized GPRS service, a value of 11 corresponds to an unauthorized PLMN, a value of 12 corresponds to an unauthorized location area, and a value of 13 corresponds to the current location area. Corresponds to unauthorized roaming, with a value of 14Hit.
In step 904, the mobile station checks the affiliation / RAU counter to see if its value is 5 or greater. It should be noted here that connector B ́ is also the point leading to step 904. If the affiliation / RAU counter is not greater than or equal to 5, the operation passes through connector B2 (rejected affiliation / no network response) or connector B3 (rejected RAU / no network response) (Figure 8). If the affiliation / RAU counter is 5 or higher, the mobile station immediately displays "Data services are not available on this network" (step 906). Next, the mobile station begins to check whether the timer T3302 is set to a value larger than the predetermined built-in timer value t2 (step 908). The built-in timer value t2 is generally set between 5 and 30 minutes, preferably longer than 12 minutes (for example, between 13 and 30 minutes). Alternatively, the value of the built-in timer is set between 5 and 10 minutes, preferably about 6 minutes. If the timer T3302 is greater than the built-in timer value t2 in step 908, the mobile station activates the timer based on the built-in timer value t2 (step 912). If timer T3302 is greater than the value of the built-in timer in step 908, the mobile station activates the timer based on the value of timer T3302 (step 910). When either the timer in step 910 or step 912 times out, the operation passes through connector B2 (if affiliation denied / no network response) or connector B3 (if RAU denied / no network response). After steps 910 and 912, the mobile station displays "Select a network?" To let the user choose whether to manually select the network (step 916). If the user selects "yes" in step 916, the action passes through connector C. If the user selects "No" in step 916, the mobile station will display "Data services are not available on this network" (step 918). In steps 902 to 914 above, the mobile station states, "Data services are not available on this network." Show and encourage end users to choose a network. In step 914, the operation proceeds to step 916 described above.
Here, referring to FIG. 10, the manual network setting is continued, and the processing of the deny code from the network is described in particular in response to the PDP context request from the mobile station. Connector C2 is from step 818 of Figure 8, where the network sends the PDP inactivation to the mobile station. Connector X is from step 816 of Figure 8, where the network receives a PDP context request and sends a deny code to the mobile station. If the deny code is considered non-critical (step 1002), the operation proceeds to step 1012, where the mobile station will generally retry on that network. It should be noted here that the connector X2 also reaches step 1012. If the deny code is considered critical in step 1002, the action proceeds to step 1004, where the mobile station will generally prompt for manual reselection of a different network.
In this embodiment, the rejection codes that are considered non-critical are 26, 31, 34, 102, 38, 36, 39, and 35. Deny code 26 corresponds to an inadequate resource, deny code 31 corresponds to an unspecified boot deny, deny code 34 corresponds to a temporarily failed service option, and deny code 102 corresponds to a response from the network. No timeout, deny code 38 corresponds to network failure, deny code 36 usually corresponds to PDP context inactivation, deny code 39 corresponds to reactivation request, deny code 35 has already been used Corresponds to the NSAPI. On the other hand, the deny codes that are considered serious are 27, 29, 30, 32, 33, and 25. Deny code 27 corresponds to a missing or unknown APN, deny code 29 corresponds to a user authentication failure, deny code 30 corresponds to a boot denied by the GGSN, and deny code 32 corresponds to an unsupported service option. Corresponding, deny code 33 corresponds to an unsubscribed service option, and deny code 25 corresponds to an LLC or SNDCP failure.
In step 1012, the mobile station checks to see if the PDP trial counter is 5 or greater. If the PDP trial counter is not greater than or equal to 5, the operation passes through connector X3. If the PDP trial counter is 5 or higher, the mobile station displays "Data services are not available on this network" and prompts the user to manually "select a network" (step 1004). If the user selects "yes" to manually select the network in step 1006, the operation passes through connector C. If the user chooses "No" to manually select the network in step 1006, the mobile station will display "Data connection refused" (step 1008). Then, if the error is not severe, the mobile station activates timer t1, otherwise the mobile station waits for the user to manually select the network (step 1010). When timer t1 expires in step 1010, operation continues through connector X3.
So far, the methods and devices for selecting a communication network that provides one or more communication services to a mobile station have been described in detail. Generally, a scanning operation is performed by the mobile station to identify one or more communication networks that support voice communication services in the geographic service area. The mobile station identifies which of the identified communication networks makes the data communication service available to the mobile station. The mobile station then selects and registers a communication network that enables voice and data communication services over a network that does not enable services. Preferably, the method is performed in connection with the creation of one or more preferred network lists. In this case, the mobile station gives higher priority in the preferred network list to the communication networks that make voice and data communication services available and acceptable to them than those that do not. However, in any case, the home network is maintained as a high priority network for communicating with the mobile station.
Conveniently, the particular technology of this application allows data-enabled mobile stations to select a time-efficient data-enabled network. One specific method of the present application is non-critical, depending on the step of making a request for a data connection to be transmitted over the first wireless network and the request for a data connection over the first wireless network. In response to the step of retrying the data connection request via the first wireless network one or more times and the data connection request via the first wireless network when a rejection code with an error is received. Then, when a deny code with a serious error is received, a second wireless network is selected for communication without having to retry the data connection request over the first wireless network more than once. Includes steps to try and. A serious error is considered to have a permanent problem or flaw in the network or service subscription associated with the end user. Typically, the time between the first attempt to connect data over the first wireless network (including all retries) and the first attempt to connect data over the second wireless network is approximately 25. It can be from 1 minute to 4 hours. Obviously, the techniques of the present invention reduce this time by providing a more time-efficient selection of data-enabled networks. It should be noted here that the computer program product of the present application includes a storage medium and computer instructions stored in the storage medium, wherein the computer instructions perform the above method by one or more processors of a mobile station. It is a point that can be done to do.
Instructions on whether the wireless network currently makes data connections available to the mobile station are made in the mobile station's memory. The instructions to the wireless network may indicate "currently available data connections" if the request for a data connection is granted to the wireless network, or if a deny code with a serious error is received or one or more. A "currently unavailable data connection" may be indicated if the data connection request is retried without success over the wireless network. Instructions on whether the wireless network currently makes voice and data connections available and acceptable to the mobile station can be made in the memory of the mobile station. The instructions to the wireless network may indicate "currently available data connections" if the request for a data connection is granted to the wireless network, or if a deny code with a serious error is received or one or more. A "currently unavailable data connection" may be indicated if the data connection request is retried without success over the wireless network. Similar results may be obtained using a list of currently unavailable data connections stored in memory. If a deny code with a serious error is received or one or more data connection requests are retried without success over the wireless network, such a list includes the wireless network, but of the data connection. If the request is granted by it, the list does not include wireless networks. However, in any case, the home network is maintained as a high priority network for communicating with the mobile station.
The mobile station of the present application includes one or more processors, a memory coupled to the one or more processors, and a radio transceiver coupled to the one or more processors. The one or more processors make a request for a data connection to be transmitted over the first wireless network and, in response to the request for a data connection over the first wireless network, reject with a non-serious error. When the code is received, it retries the data connection request over the first wireless network one or more times and makes a serious error in response to the data connection request over the first wireless network. Function to try to select a second wireless network for communication when a deny code is received, without having to retry the data connection request over the first wireless network more than once. To do. The communication system of the present application is for selecting one from the first wireless communication network and the second wireless communication network for communicating with the first wireless communication network and the second wireless communication network. Includes working mobile stations. The mobile station of the communication system includes the above-mentioned components.
It will be appreciated that the above description relates to just one example of a preferred embodiment. Many variations of the present invention will be apparent to those skilled in the art, and such modifications, whether explicitly stated or not, are within the claims of the invention, as described and claimed. For example, although the detailed description uses the term "network" rigorously in the context of the methods of the invention (assuming they are substantially homogeneous within each network), the present invention presents the network subnets and individual. It also includes a wide range of choices between subsections of the network, including cells. As another example, embodiments of the present invention focus on GSM and GSM / GPRS networks, as well as voice and data capable mobile stations, but the present invention is limited to those networks, mobile stations, and services. Please understand that it is not. The present invention can also be applied to other systems effective for communication services in which mobile stations can be used to different extents. Finally, mobile devices often identify multiple communication networks available within their geographic service area, but may identify only one available network that acts on it, and this understanding is never understood. The interpretation of the claims should not be limited.
<figref num="1">FIG. 1 is a block diagram illustrating global network interconnection.</figref><figref num="2">FIG. 2 is a block diagram of a mobile communication device which is a mobile phone mobile station.</figref><figref num="3">FIG. 3 is a block diagram showing two GSM / GPRS networks and a mobile station roaming between them.</figref><figref num="4">FIG. 4 is a block diagram illustrating a mobile station in an area where there are several different types of communication networks.</figref><figref num="5">FIG. 5 is a flowchart of automatic network selection according to the present application.</figref><figref num="6">FIG. 6 is a flowchart of automatic network selection according to the present application.</figref><figref num="7">FIG. 7 is a flowchart of automatic network selection according to the present application.</figref><figref num="8">FIG. 8 is a flowchart of manual network selection according to the present application.</figref><figref num="9">FIG. 9 is a flowchart of manual network selection according to the present application.</figref><figref num="10">FIG. 10 is a flowchart of manual network selection according to the present application.</figref>
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP10336737A | Cites | Japan |
| JP10004585A | Cites | Japan |
| JP2002186051A | Cites | Japan |
| JP2001268616A | Cites | Japan |
| JP2000514267A | Cites | Japan |
81 members in 13 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 51915003 | United States of America | P | |
| 51915003 | United States of America | P | |
| 60519150 | United States of America | – | |
| 2004001952 | Canada | W | |
| 2004001952 | Canada | W | |
| 2003519150 | – | – | – |
| 2004001952 | – | – | – |
| US20030519150P | – | – | – |
| WO2004CA01952 | – | – | – |
Members81
| Document | Office | Kind | |
|---|---|---|---|
| AU2004310098A1 | Australia | A1 | |
| AU2004310099A1 | Australia | A1 | |
| CA2545861A1 | Canada | A1 | |
| CA2545864A1 | Canada | A1 | |
| WO2005048630A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2005048631A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2005048631A8 | World Intellectual Property Organization (WIPO) | A8 | |
| US2005227719A1 | United States of America | A1 | |
| US2005227720A1 | United States of America | A1 | |
| EP1690433A1 | European Patent Office (EPO) | A1 | |
| EP1690434A1 | European Patent Office (EPO) | A1 | |
| KR20060103328A | Republic of Korea | A | |
| KR20060103329A | Republic of Korea | A | |
| EP1690434A4 | European Patent Office (EPO) | A4 | |
| CN1902976A | China | A | |
| CN1902977A | China | A | |
| EP1690433A4 | European Patent Office (EPO) | A4 | |
| US7197312B2 | United States of America | B2 | |
| HK1094498A1 | Hong Kong, China | A1 | |
| HK1094499A1 | Hong Kong, China | A1 | |
| JP2007511142A | Japan | A | |
| JP2007511143A | Japan | A | |
| US2008081622A1 | United States of America | A1 | |
| EP1690433B1 | European Patent Office (EPO) | B1 | |
| AT394014T | Austria | T | |
| ATE394014T1 | Austria | T1 | |
| KR100830914B1 | Republic of Korea | B1 | |
| DE602004013461D1 | Germany | D1 | |
| BRPI0416330A | Brazil | A | |
| BRPI0418542A | Brazil | A | |
| AU2004310098B2 | Australia | B2 | |
| US7398089B2 | United States of America | B2 | |
| US2008220800A1 | United States of America | A1 | |
| ES2304627T3 | Spain | T3 | |
| KR100869982B1 | Republic of Korea | B1 | |
| AU2004310099B2 | Australia | B2 | |
| AU2009201805A1 | Australia | A1 | |
| DE602004013461T2 | Germany | T2 | |
| JP2009239918A | Japan | A | |
| US2010048208A9 | United States of America | A9 | |
| JP4429319B2This record | Japan | B2 | |
| JP4435786B2 | Japan | B2 | |
| US7689219B2 | United States of America | B2 | |
| EP2190244A1 | European Patent Office (EPO) | A1 | |
| CN1902976B | China | B | |
| US7747266B2 | United States of America | B2 | |
| US2010203888A1 | United States of America | A1 | |
| CN1902977B | China | B | |
| CN101951670A | China | A | |
| EP1690434B1 | European Patent Office (EPO) | B1 | |
| AT496505T | Austria | T | |
| ATE496505T1 | Austria | T1 | |
| DE602004031146D1 | Germany | D1 | |
| USRE42392E | United States of America | E | |
| US2011134815A1 | United States of America | A1 | |
| EP2343929A1 | European Patent Office (EPO) | A1 | |
| EP2346287A1 | European Patent Office (EPO) | A1 | |
| EP2375825A1 | European Patent Office (EPO) | A1 | |
| JP4856212B2 | Japan | B2 | |
| HK1151159A1 | Hong Kong, China | A1 | |
| US8107985B2 | United States of America | B2 | |
| AU2009201805B2 | Australia | B2 | |
| US2012115478A1 | United States of America | A1 | |
| AU2012202545A1 | Australia | A1 | |
| USRE43523E | United States of America | E | |
| CN101951670B | China | B | |
| HK1163426A1 | Hong Kong, China | A1 | |
| US8275401B2 | United States of America | B2 | |
| AU2009201805C1 | Australia | C1 | |
| CA2545861C | Canada | C | |
| AU2012202545B2 | Australia | B2 | |
| EP2190244B1 | European Patent Office (EPO) | B1 | |
| BRPI0418542A8 | Brazil | A8 | |
| EP2375825B1 | European Patent Office (EPO) | B1 | |
| CA2545864C | Canada | C | |
| US9326227B2 | United States of America | B2 | |
| EP2346287B1 | European Patent Office (EPO) | B1 | |
| BRPI0416330B1 | Brazil | B1 | |
| BRPI0416330B8 | Brazil | B8 | |
| BRPI0418542B1 | Brazil | B1 | |
| EP2343929B1 | European Patent Office (EPO) | B1 |
28 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 | |
| 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 | |
| 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 | |
| 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 | |
| Notification of acceptance of power of attorneyJAPANESE INTERMEDIATE CODE: A7422RD02 | RD02 | |
| Notification of resignation of power of attorneyJAPANESE INTERMEDIATE CODE: A7424RD04 | RD04 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 |
Numbers
- Publication
- 4429319
- Publication, DOCDB
- 4429319
- Publication, EPODOC
- JP4429319B
- Application
- 2006538620
- Application, DOCDB
- 2006538620
- Application, EPODOC
- JP20060538620
Titles2
- Japanese
- 拒否コード処理による、データ対応ネットワーク優先化
- English
- Data-enabled network priority by deny code processing
Classification
- CPC, 4
- H04W48/18
- H04L69/40
- H04W80/04
- H04W76/18
- IPC, 7
- H04W48 16
- H04W48 18
- H04W88 06
- H04L69 40
- H04W28 04
- H04W76 02
- H04W80 04